i have a question, I recently downloaded and installed a series of high-altitude airports like the Courcheval Airport(altiports.zip) in the French Alps which are not part of the default FS2002 db. I recompiled Nav 3.1 which now reads the 4 small airports so I can create flight plans with it. Can I use such plan for RC flights? I haven't bothered using afcad to add the airports as I don't care about default ATc nor AI.

You might wish to look at my post regarding synching NAV 3.1 with RC fix data. The process should be similar but in reverse and using relavent airport data in the RC file a.txt. which is a text file about airport properties. Here is a sample line:KMSP,Minneapolis-St Paul Intl,n44:52:49.965,w093:13:00.920,-3,839,11006The first numerics are lattitude and logititude. I think the three is the number of runways but not sure about the negative -- JD, WHERE ARE YOU -- 839 is the airport elevation. 11006 is the longest runway.The file r.txt has individual runway info. Here's the excerpt for the same airport.KMSP,8200,150,12L,121,110.7KMSP,10000,200,12R,121,110.3KMSP,11006,150,22,224,110.5KMSP,10000,200,30L,301,110.3KMSP,8200,150,30R,301,110.7KMSP,11006,150,4,44,109.3In order, ICAO, runway length, runway width, runway designation, not sure about the next but looks like displaced threshold, localizer frequency.Just for fun look at fixes.txt and nsavs.txt as well.As usual, keep a copy of these files in another created folder for backup-restore.I did not check to see if the AIRAC updates from www.navdata.at include airport data, but I don't think so but it would not hurt to check. For just a few airports, using an editor is text mode might be easier.

Thank you for your help, I will try it out tonight.

As explained in Scott's reply to me if you did not catch it, the "mystery" value of -3 in the example is the magnetic variation. In Minneapolis it is 3 degrees east hence the negative value.