In may be an difficult idea to implement-but it certainly is not stupid. The default navdata is already obsolete, and that makes it hard to use the sim realistically.In my state of Michigan the faa has been renaming designators for airports for the last couple of years (changing from alpha numeric designators to k-all letter designators)-therefore quite a few aiports I fly to regularly for real have completely obsolete and incorrect designators in the fsx gps database (I counted quite a few this summer though I don't remember the exact number I think it was about 15-and has increased since then). It makes it quite hard to use the sim in a realistic fashion when the designators fsx requires no longer exist and don't match the charts/real world at all.e.g. Troy Oakland ( a popular business jet destination) is not 7d2 but has been changed to kvll, owosso is not 5d3 but has been changed to krnp. If you try putting those correct designators in your Level D as wayponts/destinations (though the runways are too short) you will be in a heap of trouble! :-) http://mywebpages.comcast.net/geofa/pages/rxp-pilot.jpg

>That's not what I meant by that...LOL.Huh? Meant by what? :)I was just saying that updating the navdata is not enough--it also would have to be coupled with scenery updates in some instances.I don't know how workable that is...RhettAMD 3700+ (@2585 mhz), eVGA 7800GT 256 (Guru3D 93.71), ASUS A8N-E, PC Power 510 SLI, 2gb Corsair XMS 3-3-3-8 (1T), WD 150 gig 10000rpm Raptor, WD 250gig 7200rpm SATA2, Seagate 120gb 5400 rpm external HD, CoolerMaster Praetorian