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.

FO doesn´t operate the MCP sometimes right

Featured Replies

Hi!I recently hav had the issue that the FO won´t set the MCP accordingly on Takeoff. When I call for Heading Select, he says it, but it won´t activate. The same happens with LNAV or Command A on some occasions.Don´t know what is causing this.I reinstalled the NGX and FS2Crew, but the problem is still there.

Banner_FS2Crew_Line_Pilot.jpg

Oliver Donner
 

The call is "Select Heading Select"

Banner_FS2Crew_Tech_Team.jpg
Damien Weekes
Captain 737NG / A319/20/21

  • Author
The call is "Select Heading Select"
I am using the Button Version.I believe that the aircraft was configured properly Byork, it worked most of the time, but then sometimes not. I will check if the problem persists with SP1, which is absolutely mindblowing!

Banner_FS2Crew_Line_Pilot.jpg

Oliver Donner
 

FO sometimes for me doesn't engage COMMAND A nor LNAV or VNAV, nearly crashed into a mountain tonight because I thought the FO turned on LNAV!Plane's configured properly.

Running i5-9600K @ 4.8ghz - 32GB DDR4 3200mhz - GTX 3070.

FO sometimes for me doesn't engage COMMAND A nor LNAV or VNAV, nearly crashed into a mountain tonight because I thought the FO turned on LNAV!Plane's configured properly.
The correct commands are "Select Lnav" "Select Vnav" "Select Command A"

Banner_FS2Crew_Tech_Team.jpg
Damien Weekes
Captain 737NG / A319/20/21

  • Commercial Member

Also remember that the control column needs to be centered before the autopilot will engage.So if you're applying pressure, the autopilot won't engage even though you ask the FO to turn it on.LNAV/VNAV... you probably weren't configured properly... the test is to try to turn LNAV/VNAV on manually.If it doesn't engage, the plane is not setup properly to accept a VNAV/LNAV engagement.Was your FMC setup properly?Best,

I only use the button control version and yes once again everything is set up properly.I follow the F/D upon take off and press the COMMAND A button and the FO says "COMMAND A", it's a hit and miss, it's either on or hasn't worked.I'll just physically do it myself from now on I don't trust it.

Running i5-9600K @ 4.8ghz - 32GB DDR4 3200mhz - GTX 3070.

  • 3 weeks later...

From memory, I believe that if you have PMDG option set to "Heading Select" after take off (as opposed to "Wings Leveled"), Heading select will be automatically selected shortly after take off. If so, maybe FS2Crew is "pressing" Heading select a second time, deactivating it...

As I said, this is something that occurred to me as a possibility, but I am not able to test it right now. Maybe something you could have a look.

Sergio Silva

If you arm Lnav and Vnav before runway entry, everything should work as published,

System: MSFS2024, ASUS Rog Stryx Z790-A,  Intel i9-14900KF,  Asus ROG Ryujin III 360 , Asus Hyperion Case,Rog Stryx 4090 OC, Samsung 970 EVO M.2 SSD, 1Tb Samsung 860 EVO SSD,64Gb G Skill Memory, Asus Aura 1200W Gold PSU,Win 11 ,LG C4 48" 4K OLED Screen., Airbus TCA Full Kit, Stream Deck XL. WinWing FCU, EFIS, MCDU

 

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.