KORD ERR: 27R RWY UNKNOWN

[yos233 1]

I am hoping someone can help me here. On my FMC, when I upload KORD (and KIAD) to my DEP/ARR page, I get the error message as follows in the topic. I have cycle 1007, and an updated KORD AFCAD to include the new northern runway. I also added the new runway(s) to the file. Could someone help me here. BTW, Im not completely new to editing this stuff, I have added the WYLY7 DEP to my BOS file.

[downscc 1,327]

The error is caused when the navdata file wpNavAPT.txt file has runway information that is different from the sidstar file kord.txt.If you want to investigate, search within the navdata file for KORD and there should be one record for each numbered runway where in the sidstar file there is a section that starts with the keyword RNWS and the runway numbers are listed followed by keyword END RNWS. You should be able to spot the problem.

[yos233 1]

Thank You for that. I found the error, it was in the wpNavAPT like you said (I had already added the new runways to my KORD file). But now I cant figure something else out. Below is a line of text from the file. I understand everything except the number sequence that is bolded and underlined. There appears to be no pattern to it with regards to the other runways around it. Could you help me here / tell me what to do for 27R/9L?CHICAGO OHARE INTERNATIOKORD04L07500042 41.981656 -87.913917111.3004200656

[yos233 1]

I fixed it. I got my runways at O'hare all figured out and I can load it up no problem. I still have no idea what those first four digits are for, but the last three are runway heading. Now to fix IAD.ADDITION: Once again, Eric is confused. I went into both folders and found the runways in their correct spots, but I continue getting the error, "KIAD ERR: 19C RWY UNKNOWN." Can anyone help me here?

Edited September 24, 2010 by yos233

[downscc 1,327]

I think that is length and altitude, there is a decode key for these files in the pmdg knowledge base, it's a little hard to follow because formatting was blown when moving from the wiki ops section to the knowledge base... better yet try to find the wiki section. I think it's still on the pmdg server.KIAD had a runway renumbering recently, however I don't understand why if you are using the same cycle for both sidstars and navdata why this is happening. Current cycle is 1010, try that.

[yos233 1]

Actually now that you bring it up, my Nav cycle says 805, the one that came with the 744 (I know I got a newer cycle but regardless). My runway numbers are the same as real life in both files though.

[yos233 1]

Dan you were right. The key is LENG/HDG. But I still cannot find the root of my problem at IAD. If you need any text I can post it, or maybe a PMDG guy could step in and help.

[downscc 1,327]

Sometimes I loose track of the original problem, which I belive is now you get an error message at KIAD runway 19C but you have checked both files (wpNavAPT.txt and KIAD.txt) and they both contain entries for 19C. Is this correct? If so, then you can email a copy of both of these files to me at downscc@swbell.net and I will try to reproduce the problem.

[yos233 1]

Sent, Thanks!This is the text from select parts,-----------SidStars-----------------------ENDFIXESRNWSRNW 01CRNW 01LRNW 01RRNW 12RNW 19CRNW 19LRNW 19RRNW 30ENDRNWSSIDS-------------NavData-------------------------WASHINGTON DULLES INTL KIAD01C11501011 38.939067 -77.459781111.3001100286WASHINGTON DULLES INTL KIAD01L11501011 38.939067 -77.459781111.3001100286WASHINGTON DULLES INTL KIAD01R11500011 38.923758 -77.436450110.1001100312WASHINGTON DULLES INTL KIAD12 10501121 38.943772 -77.490444109.3012100309WASHINGTON DULLES INTL KIAD19c11500191 38.955331 -77.435981110.1019100293WASHINGTON DULLES INTL KIAD19L11500191 38.955331 -77.435981110.1019100293WASHINGTON DULLES INTL KIAD19R11501191 38.970639 -77.459325111.3019100267WASHINGTON DULLES INTL KIAD30 10501301 38.933611 -77.455897000.0030100288

[downscc 1,327]

The problem jumped right out for me, but I've dug pretty deep into this stuff:WASHINGTON DULLES INTL KIAD19c11500191 38.955331 -77.435981110.1019100293Notice the lower case 'c' for runway 19C. That's the problem. I checked cycle 1010 where it is correct. Either get the current cycle or edit to change the lower case to upper case and you should be good to go.

[yos233 1]

Wow. Um, that was sad. Why does c have to look like C? I dont get it :(. A very anticlamatic solution, but arent they all. Thanks!