Archived

This topic is now archived and is closed to further replies.

sho69607

Airport data problems in Alaska

Recommended Posts

I have used the iFly 737ng and the PMDG 737ngx and the runaway assignments from fsx dont match the ones in the fmc. This happened on approach to PANC when ATC gave me a runaway that did not exist in the FMC.How do I fix this?

Share this post


Link to post
Share on other sites
Help AVSIM continue to serve you!
Please donate today!

How far off were they? I fly (sim) out of Halifax, Nova Scotia, and CYHZ has runways 24/06 and 34/14 in FSX. All my addon aircraft data bases show as 23/05 and 33/15. I asked my boss who is a pilot which was correct, and he informed me that the runway designations were changed a few years ago to reflex the magnetic variations. If I recall correctly FSX was published before the new designations took affect.

Share this post


Link to post
Share on other sites

I have come across this with the Eaglesoft CX2 as well, a bit of a pain, but the FSX world and the real world do not match and over time get further and further apart!Shame you can't get navdata to reflect FSX......G

Share this post


Link to post
Share on other sites

There are a couple of programs out there that allow you to change your airport information. I use Flight1's Airport Facilitator X (AFX). With that, you can change runway headings and designations, magvar's, nav aids and lots more.

Share this post


Link to post
Share on other sites
I have used the iFly 737ng and the PMDG 737ngx and the runaway assignments from fsx dont match the ones in the fmc. This happened on approach to PANC when ATC gave me a runaway that did not exist in the FMC.How do I fix this?
Basicly, don't worry about it. FSX uses 6 year old data and the real worlds magnetic field has shifted, so some numbers will be different if you are using a plane with a navdata based FMC. They are still the same runways, for example KPBI used to be 27/09, now it is 28/10

Share this post


Link to post
Share on other sites