Hello all,I have a problem with NavData/FMC for PMDG 737NG in FS9/CoF.Yesterday I was to land at LFBO (Toulouse, France) and ATC instructed me to land at Runway 15L.However, on the Arrival page of the FMC there were no Runway 15L. Instead there was a runway 14L. Of course ATC was right; there is a Runway 15L at LFBO, but there are no such thing as a Runway 14L.LFBO is NOT replaced by an add-on airport. It is only one of the standard default airports.I triple-checked that I had indeed entered LFBO as the destination airport in the FMC.I have downloaded and installed the AIRAC-Cycle: 0310 (Oct/02/2003 - Oct/29/2003)Revision #3 (Oct/03/2003) from www.navdata.atHow do I fix any incorrect runway data that appears in the FMC? The NavData files seem to contain only the longitude/latitude coordinates.Would appreciate any help.Kind regards,Nico

NICO,It seems that there is a lot of errors in regards to FMC DATA,There are some airports that have arrival/STARS that belong to another airport and same goes for the SIDS.I cant program a flight out of KGEG because I get a line error and then there is no runway info to choose from.Theses error are not as a result of anything from NAVDATA they are at the hands of the FMC data programers....I hope these fixes are part of the SU2 fix.Randy

Nico/Randy,There are no errors here! What you see is a result of something very simple. The nav-databases built into FS9 were frozen sometime in 2002 and at that time RWY15L was one of the runways at Toulouse. Since the inbound course, however is listed as 142 my guess is that it (and the other Toulouse runways) have been named more correctly to 14/32 instead of 15/33 sometime in the meantime.Now, since FS9 ATC uses the built-in FS9 navdata whereas your PMDG 737NG uses Richard's up-to-date Navdata, you simply cannot avoid this problem as long as the maggnetic variation plyes games with us all.

I have to agree that the FMC is having trouble with the data. I have yet to plan a flight where I have sids and stars for departure and arrival airport. With the same data I have no trouble at all building flight plans in the DF 734 fmc...

Hi all,I think Soren gave you guys a very clear description of the inherent problems we will always have to face when using MSFS and addons relying on more accurate databases. I would like to add only one point to Soren's message. The Sids and Stars database has nothing to do with the database published by Richard at http://www.navdata.at/. You can have the most accurate database of runways, fixes and vors, if there is one single syntax error in one line of the Sids and Stars of the airport you want to use it will not work. This is a complicated matter and I would strongly recommend to edit and double check the Sids and Stars file in question before incriminating Richard's database.There is hope that when SU2 is released and the improved syntax for programing Sids and Stars is published we will be able to write more accurate sids and stars.As to editing a runway in the wpNavAPT.txt file of your FMCWPNavdata folder I would only recommend it if you know exactly what you are doing. The format of one runway is:Airportname-ICAO-RWY-Length of RWY-Magnetic heading of RWY-LAT coordinate-Long coordinate-Localizer frequency-Localizer course-Elevation of runway.Michael

Thanks for providing me with the syntax of the airport database.Although the database is correct, I have to make it incorrect on purpose, so that the data in the FMC will match the data from ATC.Yes, indeed the runway heading is 144/324 rather than 146/326 for LFBO (which it also says in FS Navigator); yet the runway is still present as runway 15/33 in Flight Simulator.It sounds funny that an airport has to change its runway names because they find out that the headings are not what they thought they were. So much technical work must have preceeded the building of the runways when they were originally made. And then they find out that oops - it should be 2 degrees to the left.Nico

Hi Nico,The differences in the databases are probably due to the different times they were compiled at. Every runways magnetic headings are always changing due to magnetic variation over time. This is why you see the 2

Hi John,Thanks for your reply. That was a natural explaination.Regards,Nico

>The differences in the databases are probably due to the>different times they were compiled at. Every runways magnetic>headings are always changing due to magnetic variation over>time. This is why you see the 2

Hi tg272,Don't know if your reply was an attempt at homour :( ? If not, you may want to check out what magnetic variation is before responding.BTW, forum rules state you have to sign your real name with your posts.Cheers,JohnBoeing 727/737 Mechanic