FMC problem for ORD

[rrwhaley]

Hi All

Need help with this!

Flying the 772 (PMDG :-) ) to ORD, in the FMC, I kept getting  "KORD ERR: 10C RWY N/A" I am using FSDT KORD V2. No Stars, or RWY shows up, for ORD in the FMC. Not sure what causing this problems! This is not a issue flying the all the PMDG 737 NGX 9/8/7/6 version. Just this AC. Any help would be a great help!

Ron Whaley
AAL652

[StumpJumper]

Similar problem just noticed after installation of PMDG777 SP1.  The error I receive upon entering KORD as the destination airport in FMC is:
KORD ERR: 04L RWY N/A

Help please...

Darrell Morrison
UAL1146

[srcooke]

If your using Navigraph 1408 there is an error in the data, a workaround is posted here: http://www.navigraph.com/forum/viewtopic.php?f=30&t=1624

Also make sure that you run makerwys where the PMDG 777 is in use available from Pete Dowson : http://forum.simflight.com/topic/66136-useful-additional-programs/

[StumpJumper]

Thanks for the reply!!  Outstanding response...works!!

[boilerbill]

Ron:

The error relating to runway 10C is probably because there wasn't a runway with that designation when FSDT's software was released. If you look at the Airport Diagram on p. 6 of the OHareX_Manual.pdf document included with your installation, you'll see that it was current between February 14 and March 13 of 2008. The only east-west runways at that time were 9R/27L and 10/28. Since that time, runway 10/28 has been renamed 10L/28R. (Runway 9R/27L has been joined by 9L/28R on the north side of the field, and 9C/27C is under development. On the south side of the field, 10L/28R has been joined by 10C/28C, and next year 10R/28L will be commissioned. That means KORD will eventually have 6 east-west runways! And that's not all of the changes. More details here.) 

So if you're going to continue using the FSDT software, you'll have to remember to use the runways that existed when it was released. I don't know if/when they plan to update it.

[virtuali]

If you look at the Airport Diagram on p. 6 of the OHareX_Manual.pdf document included with your installation, you'll see that it was current between February 14 and March 13 of 2008. The only east-west runways at that time were 9R/27L and 10/28.

That's not entirely correct. While is true the manual we have in the installer dates 2008, we had an update in 2011, which added runway 9L/27R:

http://www.fsdreamteam.com/forum/index.php/topic,4991.0.html

At THAT time (2011), the scenery was current with the airport situation, runway 10C/28C was still named 10/28, because the other runways were still in construction back then.

In fact, even today, both Google and Bing Maps haven't updated the images, and the runways are still displayed as being under construction:

https://www.google.com/maps/@41.9693691,-87.9212016,1744m/data=!3m1!1e3

So, the scenery is accurate not only to its own original release date, but to the current images you can find on Google/Bing. This airport is undergoing a very long update process that will last for many years, and we already updated it once.

[boilerbill]

Thanks for the correction, although I'm a bit surprised the pdf in the manual wasn't updated during the 2011 update. That would have shown the runway(s) under construction, as the FAA's current Airport Diagram shows for runway 10R/28L and various taxiways. It's important for pilots to know about such construction; in addition to avoiding work sites and equipment, a nearly-finished runway might easily be mistaken for the real thing. As for current conditions, I wouldn't think of using Google, Bing, or any other source when the latest official charts are always available on the FAA site. After all, we pay for them with our tax dollars. (Some of us do, anyway.

[virtuali]

Thanks for the correction, although I'm a bit surprised the pdf in the manual wasn't updated during the 2011 update.

I'm surprised too...it was an oversight...

As for current conditions, I wouldn't think of using Google, Bing, or any other source when the latest official charts are always available on the FAA site. After all, we pay for them with our tax dollars. (Some of us do, anyway.

That's not the point. The point is that, right now, if somebody goes to Google/Bing to check the scenery, they would see they match. And, without having a least those images as a *reference* (we don't take the images as they are, but we use them as a reference to start texturing), we can't obviously remade the background just using the maps.