I have a suspicion it may be the default FSX windsocks... I'm working on Guam right now and discovered it appears the problem is the windsock... Will do more testing and see what happens...

Please explain a bit more, how do the windsocks cause this problem and what are you using to check it out.? Thanks for your input, I'd really like to fix this issue if possible without turning off crash detection. Cheers Martin

Hi Martin, I edited my post above, user error in my case, but I basically switched off all default scenery files to see if they were the cause of the error... In tmfviewer I loaded in some of my changed data near the airport such as vector scenery or photoscenery and that gives a scenery directory location to be able to figure out which default folder to turn off. In my case 1003. I also turned off Oceania as well. That allowed me to see that a building was being placed where it shouldn't be, in my case a custom scenery building I had placed. If you're using a custom scenery or AFCAD over the airport I'd suggest manually renaming the .bgl's to .bak one by one until you find the BGL file which is placing a building where it shouldn't be, then you can create an exclude for that GUID object to eliminate it completely or just add a generic AFX/ADE/AFCAD exclude over the area causing the crash and making sure your new airport AFX/AFCAD/ADE is in the same directory as your scenery for the airport. Hope this helps...