Posted a while back that I had problems compiling flight plans to certain airports in RC after exporting the flight plan from Nav 3.1. The error message from RC when compiling is to the effect "....the number of arrival runways in your flight plan exceed the allowed number of 16. Reduce the number of arrival runways and try again."The first time this error message occurred it was for an airport located in an area where I had downloaded mesh scenery (PHNL). Scott Campbell was nice enough to point out that compiling my Nav 3.1 scenery database subsequent to adding mesh scenery may be the cause of the problem. I also e-mailed Ted Wright to confirm, etc. but did not receive a response.Today, I prepared a flight plan from KBUR to KDEN. I have not downloaded any mesh / landclass scenery for Colorado. I again received the error message regarding arrival runways at KDEN.Needless to say I am frustrated that when selecting arrival airports with numerous runways (albeit less than 16) I apparently cannot utilize RC for the flight.Any further insight or help would be appreciated, I really do not want to go back to FS2K2 ATC.Thanks.

as far as i know, there are no airports that have more than 16 runways. when nav3.1 compiles it's database, it scans all of your scenery files. if you have third party scenery along with fs200x/fs98 scenery, the number of runways double. i have several beta testers that fly into denver, so i know it works.try rebuilding your nav database, and exclude all third party sceneryjd

>The first time this error message occurred it was for an >airport located in an area where I had downloaded mesh >scenery (PHNL). Scott Campbell was nice enough to point out >that compiling my Nav 3.1 scenery database subsequent to >adding mesh scenery may be the cause of the problem. I don't think mesh scenery contains airports and navaids, so it should not cause this problem.>I also e-mailed Ted Wright to confirm, etc. but did not receive a >response.I did not receive your email.>Today, I prepared a flight plan from KBUR to KDEN. I have >not downloaded any mesh / landclass scenery for Colorado. I >again received the error message regarding arrival runways >at KDEN. To find out where the extra runways are coming from, zoom in on KDEN in Nav so that just that airport is showing, then click the "database" button. That will bring up a list of everything Nav knows about in the current view. If you double-click on a runway, it will tell you which file it came from. For FS2002, they scould all be the same file, which on my computer is:c:gamesfs2002scenedbafdfilessceneryusncaf02.bgl(a few extra runways from other airports may show up due to their close proximity to KDEN, but there should be no double entries).Ted

JD and Ted,Thanks very much for your replies. I re-compiled the database and solved the runway problem at KDEN but not at PHNL. I still have FS2K on my hard drive, it appears that when I first compiled the NAV 3.1 database both FS2K2 and FS2K airport / navaid info was included in effect doubling the data for each type of facility. I must have made a mistake when initially compiling the database.However, the Hawaiian airports still look funny, especially PHNL. Indicated below is the database detail for PHNL. I did re-install the mesh scenery after the database re-compile, however do not understand the Runway ID: 0H, entries. All the hawaiian airports have at least one Runway 0H, is it possible to edit the data and delete these runways?Thanks again JD and Ted.Airport Full name: Honolulu Intl Nearest ICAO ID: PHNL Latitude: 21.318691 N (21 19' 7.29" N) Longitude: 157.922408 W (157 55' 20.67" W) Altitude: 9 ft ATIS Frequency: 127.90 MHz Runway ID: 8R, Magnetic Heading: 79 (True: 90) Length: 12000 ft, Width: 200 ft, Asphalt Runway ID: 8L, Magnetic Heading: 79 (True: 90) Length: 12357 ft, Width: 150 ft, Asphalt ILS on heading 79: 111.70 MHz Runway ID: 4R, Magnetic Heading: 42 (True: 52) Length: 9000 ft, Width: 150 ft, Asphalt ILS on heading 42: 110.50 MHz Runway ID: 4L, Magnetic Heading: 42 (True: 52) Length: 6952 ft, Width: 150 ft, Asphalt Runway ID: 8 , Magnetic Heading: 79 (True: 90) Length: 5000 ft, Width: 300 ft, Surface type: 10 Runway ID: 4 , Magnetic Heading: 42 (True: 53) Length: 3000 ft, Width: 150 ft, Surface type: 10 Runway ID: 0H, Magnetic Heading: -10 (True: 360) Length: 112 ft, Width: 112 ft, Surface type: 0 Runway ID: 0H, Magnetic Heading: -10 (True: 360) Length: 112 ft, Width: 112 ft, Surface type: 0 Runway ID: 0H, Magnetic Heading: -10 (True: 360) Length: 112 ft, Width: 112 ft, Surface type: 0 Runway ID: 0H, Magnetic Heading: -10 (True: 360) Length: 112 ft, Width: 112 ft, Surface type: 0 Runway ID: 0H, Magnetic Heading: -10 (True: 360) Length: 112 ft, Width: 112 ft, Surface type: 0File: c:program filesmicrosoft gamesfs2002scenedbafdfilessceneryhawafd.bgl

>... however do not understand the Runway ID: 0H, >entries. All the hawaiian airports have at least one Runway >0H, is it possible to edit the data and delete these runways? >...> Runway ID: 0H, Magnetic Heading: -10 (True: 360) > Length: 112 ft, Width: 112 ft, Surface type: 0 Those are Microsoft's idea of how a "helipad" should appear in a BGL file: a 112' by 112' square runway with an ID of '0H'.They are not exported to RC, so you don't need to delete them for that reason.There is, in general, no good way to edit Nav's database. The 3.1 pre-release can export the database as a text file, and I plan to finish loading the text file back in (after editing) before I call 3.1 finished, but it is not there yet.Ted Wright

Thanks very much for the explanation Ted. I really enjoy using NAV 3.1.