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.

LNAV light on MCP extinguishes during takeoff

Featured Replies

Hopefully someone can give some advice regarding two issues that I have. These are during the tutorial flight from EGKK to EHAM.1. When taking off the LNAV light extinguishes during takeoff on the MCP but is still present on thet top of the PFD. The aircraft is configured as per the tutorial. When I engage CMD A I have to then push the LNAV button on the MCP again. The light then comes on as normal.2.Plane configured for final 18R. When I select flaps 30 the warning horn starts and doesn't stop. I can't work out why? Everything configured as per the tutorial.I have tried this flight 15 times and everytime the same issues arise.Need some advice about what I am possibly doing incorrectly.Thanks in advance

Andrew Dixon
"If common sense was compulsory everyone would have it but I am afraid this is not the case"
 

I am sure someone here can answer to your question. I am a newbie myself, but I think that LNAV and VNAV both extinguish during takeoff and turn on again automatically as you reach 400 feet.

Antonio H.

 

pmdg_j41_banner.jpg

Config warning horn. Make sure you put your gear down before you go to F15.

Matt Cee

  • Author

Another flight same damn warning horn noise on landing. Plane configured all annunciations correct (LAND 3). As soon as I select flaps 30 from flaps 25 away it goes. Speed set in MCP 147 as per tutorial for flaps 30. As soon as the plane hits the gound silence. Both flight Directors active. This is driving me nuts!

Andrew Dixon
"If common sense was compulsory everyone would have it but I am afraid this is not the case"
 

  • Author

anyone any ideas

Andrew Dixon
"If common sense was compulsory everyone would have it but I am afraid this is not the case"
 

As Spin737 suggested, are you lowering the landing gear before extending flaps to 15?

FS2024 • PMDG 738, 77F • FSL A321 • A2A Comanche, Aerostar • BS Baron, Bonanza, Caravan Pro • JF Tomahawk • TAOG H500C
BeyondATC • GSX Pro • ChasePlane & Flow Pro • TDS GTNXi • FSUIPC • AutoFPS • RealTurb

9800X3D B650E • ROG OC RTX 5090 • 64GB DDR5-6000 • VKB Gladiator, STECS, T-Rudder • Tobii 5 • ISP 1 Gbps

  • Commercial Member
Hopefully someone can give some advice regarding two issues that I have. These are during the tutorial flight from EGKK to EHAM.1. When taking off the LNAV light extinguishes during takeoff on the MCP but is still present on thet top of the PFD. The aircraft is configured as per the tutorial. When I engage CMD A I have to then push the LNAV button on the MCP again. The light then comes on as normal.2.Plane configured for final 18R. When I select flaps 30 the warning horn starts and doesn't stop. I can't work out why? Everything configured as per the tutorial.I have tried this flight 15 times and everytime the same issues arise.Need some advice about what I am possibly doing incorrectly.Thanks in advance
1. On TOGA press the LNAV (and VNAV if armed) lights extinguish meaning that the mode cannot be disarmed anymore by pressing the respective button. The armed mode is locked unless both FD's are reset.2. GEAR DOWN !

====================================

E M V

Precision Manuals Development Group

====================================

  • Author
As Spin737 suggested, are you lowering the landing gear before extending flaps to 15?
I've checked and tried everything. As soon as I select flaps 30 the horn sounds.I've already tried the landing gear lowering before flaps 15. Just about had enough! Next step will be to uninstall permanently and stick with the MD11.
1. On TOGA press the LNAV (and VNAV if armed) lights extinguish meaning that the mode cannot be disarmed anymore by pressing the respective button. The armed mode is locked unless both FD's are reset.2. GEAR DOWN !
The plane is configured and lands perfectly, the only issue is the racket on the way down. As soon as the wheels hit the ground the horn stops.

Andrew Dixon
"If common sense was compulsory everyone would have it but I am afraid this is not the case"
 

  • Commercial Member

Read above. Do it slowly. Gear down before setting the flap lever to F15. Gear down and locked then F15. One step at a time to begin with. You 'll burn 10 kilos of fuel extra. We then take it from there. OK ?

====================================

E M V

Precision Manuals Development Group

====================================

I can recall, that I experienced the same problem at the beginning but I believe that the error (in my own case) was sitting in front of the yoke.

Regards,
Axel

I have the same problem also every time i fly it. But i was waiting to see if the new Service pack would solve it but i guess not if your having the same problem. I didn't want to post it here cause i fiqured 'you know what, this thing is way above a lot of ours heads' and really i think it's me doing some thing wrong but i'll keep reading the post here ha

Louis Massicotte

Caroline Alberta 

 

  • Author
Read above. Do it slowly. Gear down before setting the flap lever to F15. Gear down and locked then F15. One step at a time to begin with. You 'll burn 10 kilos of fuel extra. We then take it from there. OK ?
OK as usuual the problem is holding the yoke. Had a nights sleep and tried again.........slowly. I also deleted the FSUIPC assignment for gear up and down. What do you know and landing with no warning horn. Thanks for your patience.One other query, Before LAND 3 is announced on the PFD I get SGL CHN in yellow in the upper PFD. If the two autopilots are engaged (both CMD 1 and CMD 2) and both NAV radios are tuned to the ILS frequency should the announciation be DUAL CHN as it is using the 2 NAV Radios or landing systems. Single Channel indicates only one is operational not the two.Also worth noting : When the Captain's EFIS Control Panel is set to 10 feet or less, the decision height callouts will not sound. Once a decision height callout has sounded, it will not function again until after the airplane climbs above 1000 feet RA.

Andrew Dixon
"If common sense was compulsory everyone would have it but I am afraid this is not the case"
 

  • Commercial Member
OK as usuual the problem is holding the yoke. Had a nights sleep and tried again.........slowly. I also deleted the FSUIPC assignment for gear up and down. What do you know and landing with no warning horn. Thanks for your patience.One other query, Before LAND 3 is announced on the PFD I get SGL CHN in yellow in the upper PFD. If the two autopilots are engaged (both CMD 1 and CMD 2) and both NAV radios are tuned to the ILS frequency should the announciation be DUAL CHN as it is using the 2 NAV Radios or landing systems. Single Channel indicates only one is operational not the two.Also worth noting : When the Captain's EFIS Control Panel is set to 10 feet or less, the decision height callouts will not sound. Once a decision height callout has sounded, it will not function again until after the airplane climbs above 1000 feet RA.
Happy it worked for you !No. When you press the second CMD button then you arm not activate the second autopilot. You can actually do this even when the glideslope mode is armed not active. The second autopilot will engage once you go below 1500ft (radio altitude) for approximately 3 seconds and all internal tests pass (you can see the error check test by the flashing yellow markers on the PFD, first the master side and then the second side). The second AP will not engage if all conditions are not satisfied by 800 ft radio altitude. If all is correct LAND3 (or CMD in FAIL PASS) will be annunciated.

====================================

E M V

Precision Manuals Development Group

====================================

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.