Sign in to follow this  
Lokieagle62

FMC CYYC, KORD RWY N/A

Recommended Posts

Good Day, 

 

Since I updated my fleet from the PMDG ops center when the 747 QOS II was released, I have been receiving "RWY N/A" for both CYYC and KORD. I did some research and the other forums suggest deleting  "ARPT_RWY" and the plane will create a new one. This did not work. I downloaded Peter Dowson`s Make Runways program and ran it. This did not work either. Finally I attempted to go into the sids/stars folder and manually enter runways which provided no joy. This is a problem on my MD-11, 737, 747v3 and 777

 

Here are the forums I found on the subject.

 

http://www.avsim.com/topic/467054-fms-error-message-cyvr-err-12-rwy-na/

http://www.avsim.com/topic/503221-fmc-error-for-kord-10c-rwy-na/

http://forum.aerosoft.com/index.php?/topic/83618-rwy-na-issues-with-pmdg/

 

Note: I do not subscribe to Navigraph. I am running AIRAC 1309 which came out in 2013. I have been flying around with "nav data out of date" since buying the 777. It has not become a problem until now. Also, I do use scenery for these airports which I downloaded from the avsim freeware library. These airports are the only ones I have encountered problems with. Hopefully no more show up

 

Dylan L

Share this post


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

Dylan,

 

The panel reads for runways/sids/stars/apps what is in the files.

Share this post


Link to post
Share on other sites

You may want to delete the NAVDATA folder and the SIDSTARS folder, then re-install the 747, as the 747 installs AIRAC 1702 unless it detects an older one is already on there, in your case 1309.

Share this post


Link to post
Share on other sites

You may want to delete the NAVDATA folder and the SIDSTARS folder, then re-install the 747, as the 747 installs AIRAC 1702 unless it detects an older one is already on there, in your case 1309.

Please don't do this.

 

99% of the time, the reason for RNW N/A message is something is wrong with the ARPT_RWY.dat file located in the PMDG\NAVDATA folder.  Delete the file, the next time you load either the 777 or 747 it will be rebuilt. Got nothing to do with airac navdata.  This file is a cache used by those two products to speed up processing and reduce VAS.

Share this post


Link to post
Share on other sites

I did try deleting the ARPT_RWY folder and letting the plane rebuild one but it still was not working. Would it make a difference installing the add-ons before or after installing the aircraft?

Share this post


Link to post
Share on other sites

Please don't do this.

 

99% of the time, the reason for RNW N/A message is something is wrong with the ARPT_RWY.dat file located in the PMDG\NAVDATA folder.  Delete the file, the next time you load either the 777 or 747 it will be rebuilt. Got nothing to do with airac navdata.  This file is a cache used by those two products to speed up processing and reduce VAS.

I had only recommended it because he said the one that was showing up was 1309, and the 747 installs an updated 1702. Guess that ultimately depends on if you wanted the updated data or not because the installer will not update it if it sees an older version.

Share this post


Link to post
Share on other sites

 

 


I did try deleting the ARPT_RWY folder and letting the plane rebuild one but it still was not working. Would it make a difference installing the add-ons before or after installing the aircraft?

 

I don't know about CYYC, but KORD has certainly been modified since 2013, and often causes such error messages.  So I am wondering if you have an updated KORD AFCAD but are still using Airac data that has old runway information?  Or the stock KORD with more up-to-date runways even in Airac 1309?

 

Mike

Share this post


Link to post
Share on other sites

I just reinstalled the QOS II and it had AIRAC 1309 in the aircraft. Would it be wise to buying a 30 day subscription to FMS DATA if it should resolve it? Also, if you do recommend that would the data stay after the 30 days or would it revert back to the old AIRAC?

 

Dylan

Share this post


Link to post
Share on other sites

I just reinstalled the QOS II and it had AIRAC 1309 in the aircraft. Would it be wise to buying a 30 day subscription to FMS DATA if it should resolve it? Also, if you do recommend that would the data stay after the 30 days or would it revert back to the old AIRAC?

 

If you rename the PMDG/Navdata and PMDG/SIDSTARS  folders to something else and run repair (or reinstall if repair doesn't work) you should get Airac 1702 without having to go to Navigraph or another Airac distributor.  Once you have Airac 1702 in your ... /Navdata and .../SIDSTAR folders it will not revert to 1309 after 30 days no matter where you got the more up-to-date Airac from.  I don't update from Navigraph every month but I always have my most recent update available.

 

The reason your reinstall didn't produce the 1702 Airac is that it detected your 1309 Airac in the above two folders and didn't want to mess with them.

 

Mike

Share this post


Link to post
Share on other sites

PMDG FMC does not read the AFCADs, the only source for the runway data is the wpnavapt.txt navdata file, which the sidstar file refers to. Changing the runway info in the sidstar without changing the airport data file guarantees errors.  I think you broke it trying to fix it.  Try Mikes idea.

Share this post


Link to post
Share on other sites

I just reinstalled the QOS II and it had AIRAC 1309 in the aircraft. Would it be wise to buying a 30 day subscription to FMS DATA if it should resolve it? Also, if you do recommend that would the data stay after the 30 days or would it revert back to the old AIRAC?

You'd have to make sure you removed the navigation data BEFORE you did the re-install, as it won't install the new 1702 if the old 1309 is still there. When you uninstalled the 747, it wouldn't have deleted the navigation data since you might still have planes on your computer that might need it, which you did (the 737, 777, and I guess the MD-11). There would be no point in buying the subscription if the 747 already came with it. As for the data, once the data's installed, it stays on your computer.

  • Upvote 1

Share this post


Link to post
Share on other sites

 

 


PMDG FMC does not read the AFCADs, the only source for the runway data is the wpnavapt.txt navdata file, which the sidstar file refers to. Changing the runway info in the sidstar without changing the airport data file guarantees errors. I think you broke it trying to fix it. Try Mikes idea.

 

Just to add to Dan's point, starting over with a fresh .../Navdata folder will also cause the 747 to build a new ARPT_RWY.dat file, using the new Airac info.

 

Do you have a recent modified AFCAD file installed for KORD (or CYYC) that has correct runway information?

 

Mike

Share this post


Link to post
Share on other sites

Mike, I'm using the old FSDT KORD AFCAD slightly modified at certain parking spots..., the runways in the AFCAD are not looked at by PMDG.  I land 28R even if it is 28 in the AFCAD, means nothing.

Share this post


Link to post
Share on other sites

 

 


Mike, I'm using the old FSDT KORD AFCAD slightly modified at certain parking spots..., the runways in the AFCAD are not looked at by PMDG. I land 28R even if it is 28 in the AFCAD, means nothing.

Hi Dan,

 

I see your point.  The O.P. could have an AFCAD from 1967 and it wouldn't affect the FMC display or ARPT_RWY.dat.  Just looked at an ARPT_RWY.dat file from 2013 (still had since I no longer use FSX Box), there were separate entries for the FSX runways in addition to the info from the navdata in the navdata file.  But now the FSX runway info is no longer there!

 

From 2013 (they agree because I already had the new runway at IAD installed):

AP;KIAD;WASHINGTON DULLES INTL  ;38.947445;-77.459945;286
RW;01C;38.939067;-77.459778;286;11130;011;011;11500
RW;01L;38.944967;-77.474811;296;11075;011;011;9400
RW;01R;38.923759;-77.436450;312;11010;011;011;11500
RW;12;38.943772;-77.490445;310;10930;121;121;10501
RW;19C;38.970642;-77.459320;269;11130;191;191;11500
RW;19L;38.955328;-77.435981;293;11010;191;191;11500
RW;19R;38.970772;-77.474439;277;11075;191;191;9400
RW;30;38.933611;-77.455897;288;0;301;301;10501
FS;01L;38.944046;-77.475174;313;11075;011;011;9465
FS;01R;38.923721;-77.436432;313;11010;011;011;11511
FS;01C;38.939060;-77.459785;313;11130;011;011;11512
FS;12;38.943779;-77.490471;313;10930;121;121;10489
FS;19L;38.955292;-77.435959;313;11010;191;191;11511
FS;19R;38.970009;-77.474808;313;11075;191;191;9465
FS;19C;38.970638;-77.459312;313;11130;191;191;11512
FS;30;38.933578;-77.455879;313;0;301;301;10489

 

Mike

Share this post


Link to post
Share on other sites
I don't know about CYYC, but KORD has certainly been modified since 2013, and often causes such error messages.  So I am wondering if you have an updated KORD AFCAD but are still using Airac data that has old runway information?  Or the stock KORD with more up-to-date runways even in Airac 1309?

 

Mike

 

I'm from Calgary, and in April 2014, they finished constructing a new parallel runway (17L/35R), so that might have something to do with it. The old runway was dubbed 16/34 back when FSX SP2 was released. Revised to 17R/35L after the new runway opened.

 

You might also want to try updating the magdec table here.

Share this post


Link to post
Share on other sites

Create an account or sign in to comment

You need to be a member in order to leave a comment

Create an account

Sign up for a new account in our community. It's easy!

Register a new account

Sign in

Already have an account? Sign in here.

Sign In Now
Sign in to follow this