Rather than "abuse" the MAIW Tyndall package thread... Also because a friend who lurks in these forums sent me a rather scathing (though somewhat tongue-in-cheek, I hope) email ranting about my "arrogance discussing (my)your afcad without bothering to show what the h*** you're talking about"....
Here's a modified-for-FS9 version of my highly-personalized-fit-only-for-my-setup afcad for KPAM. It's important to note that
I did not match up/modify the wingspan/aircraft parking radius entries with FS9-standards. I leave that up to you.
What I've done is strictly limited to showing parking areas, accurate taxi-apron-runway layouts according to the available satellite pics (Google Earth/Yahoo sat/MS Virtual Earth). I did throw in 3 MIL_CARGO parking spots not shown on any satellite photo -
for the stray transient humongous mother. 
There's room left to add maybe 20 more parking spots if you want to be accurate according to the pics. I leave that up to you.
You also might want to take a look at/modifying/coordinating your aircraft.cfg atc_parking_codes and atc_parking_types entries with this afcad for best results. I use QF4 rather than ATRS, for example. Without coordinating that, parking looks a bit "rough" in terms of "grouping".
As mentioned in the MAIW Tyndall package thread, I think that any afcad for Tyndall works best if you download the freeware update for the Alphasim Tyndall scenery package on avsim.com, decompile it and create an object library using the included models, then place them yourself using something like Instant Scenery/Whisplacer. Definitely makes a world of difference, looks-wise.
Offered "as-is" without support. Modify to your heart's content.
If modified for further distribution, PLEASE do not give any public attribution to me. (Yeah, I know - I'm weird.)
Ford
