When executing a flight plan, at some point the init page will be replaced by an "approach" page that gives the frequency and orientation of the destination runway that you chose when making the flight plan. This information is not always correct, because FSX and NGX apparently do not always use the same database. For example, for Frankfurt runway 25L NGX gives 248 degrees an ILS frequency of 111.55 (not sure about the first 3 numbers), but the FSX map gives the ILS frequency as 111.35 and 248 degrees as well. The first time I flew Hamburg (FDDH) to Frankfurt (EDDF), everything worked fine and the plane autolanded beside the runway on a catIII autoland using the NGX frequency. I thought I had misread the frequency or orientation, but today on my second attempt I found that the difference was real and once more, this time with the FSX frequency, the plane made a perfect landing next to the runway. The good news is that the plane did not crash nor take any damage both times, so apparently there is an invisible "virtual" runway where the plane went next to the real runway. The FSX frequency seemed to give a landng somewhat closer to the runway, so next time there is a disagreement I will use the FSX one or land my hand. The lesson here is to always check the runway orientation and frequency on the FSX map and if it disagrees with the one given on the approach page, take whatever action you deem appropriate. Another flight plan problem is that often just when entering the STAR, the FMC will suddewnly warn you that the plan is not achievable (this is usually due to an altitude forced to be "above" some value at some point too close to the runway to make the descent. So far I have always been able to alleviate this and to land safely by changing the say "/5000A" to "/5000B" in the legs page some time before the plane gets there, which allows the plane to go below 5000. Henri

The NGx is receiving its information from the NAV DATA Base which reflects the current real world situation. On the other hand what works in your FSX installation is the AFCAD (a .bgl library type data file) of the scenery (airport) installed. A lot of them are not updated or simply coded wrong compared to current real world values. Sorry but cannot do much there. PS. Some airports in the FMC database do not even exist in FSX ! E.g. an airport in SA with ICAO FALE.

I understand that and I understand that it is not PMDG's fault. I do have some updated airports installed by some scenery like Ultimte scenery and FS Scenery, but I also understand that due to magnetic deviation changes and other considerations, airport numbers change all the time, so players have to be careful when choosing an unfamiliar airport. Henri