Skip to content
View in the app

A better way to browse. Learn more.

The AVSIM Community

A full-screen app on your home screen with push notifications, badges and more.

To install this app on iOS and iPadOS
  1. Tap the Share icon in Safari
  2. Scroll the menu and tap Add to Home Screen.
  3. Tap Add in the top-right corner.
To install this app on Android
  1. Tap the 3-dot menu (⋮) in the top-right corner of the browser.
  2. Tap Add to Home screen or Install app.
  3. Confirm by tapping Install.

FMC warning, '36 RNW load error'

Featured Replies

When I enter the company route, that appears, ive tried a few routes, all the same message, ive tired routes with different origin, same message but different runway, I think thats why I cant arm LNAV and VNAV.ThanksConstantine V EDIT: Opps sorry, didnt see how bad this post was.When I enter a route, into the FMC, the warning 36 RNW load error, usually accompanied buy another/the corresponding runway shows up, I can easily clear the message, but LNAV and VNAV wont arm, I think I maybe doing somthing else wrong. The route I'm entering is a route PMDG provides from the Flightplan folder, and I am entering it in the Company route section in the FMC.I have the 747-400X.ThanksConstantine V.

I think that You should be much more specific. And maybe posting in thread regarding Your aircraft would be more helpful.

What it means is that the route you are loading is telling the FMC to land/lift-off from runway 36, but the FMC does not recognize it. It might be that between FSX's release and PMDG's release, there are discrepencies. These might be as little as adding another parallel runway so they are now "36L" and "36R", or as complex as a total error between the route and the airport, which has runway 9-27.If you open the route using a text editor like notepad, you can change around the runways to use, or create the runway in the airport's file.

Eric Vander

Pilot and Controller Boston Virtual ATC

KATL - The plural form of cow.

KORD - Something you put in a power socket.

UNIT - Something of measure

My 747 Fuel Calculator

The solution is to make sure your navdata is the same cycle as the sidstar file. Current data is obtained from navigraph.comThe error occurs when there has been a runway renumbered, happens fairly often.

Dan Downs KCRP

So could you please tell me what I have to do to fix it? And what do you mean by a renumbered runway?Thanks.,Constantine V Edit: Oh I see, I just open the FP in the notepad and change the runway, But this happens with every airport for me, do I need to change all the runways?Thanks all, Kind regardsConstantine V.

Another thing that I have noticed is that all the departing runways/destination runways are the same, and there is only one flight plan that works, that is AAYBBNYSSY, it is set out differently when I open it and it works, is says its generated by FS build 2.2 and the others arnt, the others are all set out differently and have different names such as SYDSIN001, JFKLAX001.Constantine V

The most recent AIRAC cycle included changes to many airports magnetic deviation and as a result can have changed runway numbers due to said magnetic heading change as seen on the Houston Hobby (HOU) compare airport diagram. If you downloaded the most recent AIRAC cycle, your saved FPs may need to be changed if you intend to fly them again.   

ng_driver.jpg

Supporter GhostRecon.net | AGgReSsion

 

WhiteKnight77's Place

 

Mike Shannon

 

 

Create an account or sign in to comment

Account

Navigation

Search

Search

Configure browser push notifications

Chrome (Android)
  1. Tap the lock icon next to the address bar.
  2. Tap Permissions → Notifications.
  3. Adjust your preference.
Chrome (Desktop)
  1. Click the padlock icon in the address bar.
  2. Select Site settings.
  3. Find Notifications and adjust your preference.