Learn how to use the Boeing 787 autopilot in MSFS 2020, including FMC setup, LNAV/VNAV, descent, ILS capture and common mode fixes.
In Microsoft Flight Simulator 2020 (MSFS 2020), programme and activate the Boeing 787-10 FMC route, switch on both flight directors, arm the autothrottle, set the MCP altitude, and arm LNAV and VNAV. After take-off, engage one autopilot channel when stable, then verify every active mode on the PFD flight-mode annunciator.
These instructions apply to the updated default Boeing 787-10 supplied with the Premium Deluxe edition. Older aircraft content and third-party 787 add-ons may use different controls or simulate fewer functions.
What must be set before engaging the 787 autopilot?
LNAV and VNAV only work reliably when the FMC contains a valid route and performance data. Enter the departure, route, arrival, cruise altitude and take-off data, then activate the route and remove unintended discontinuities.
Our airliner FMC programming guide covers that process in detail. The critical point is that a route shown on the navigation display is not necessarily active; inspect the LEGS pages and confirm the first waypoint sequence before departure.
- Prepare the flight guidance. Switch on both flight directors and move the autothrottle switch to A/T ARM.
- Set the MCP. Select the first cleared altitude rather than automatically entering cruise altitude. Set the departure heading or confirm that LNAV has a valid route to follow.
- Arm the take-off modes. LNAV and VNAV may be armed before take-off when the FMC route and performance pages are valid. Otherwise, plan to use HDG SEL and FLCH after becoming airborne.
- Use TO/GA for departure. Apply the cockpit TO/GA control or its assigned binding, rotate normally and establish a stable climb.
- Engage the autopilot. Press one autopilot engage switch once the aircraft is stable and safely above the applicable engagement height. Waiting until roughly 400 to 1,000 feet above the runway is a practical simulator technique.
- Read the FMA. Check the flight-mode annunciator across the top of the primary flight display. Active modes normally appear in green and armed modes in white; the FMA, not the button light, tells you what the aircraft is actually doing.
Which Boeing 787 autopilot mode should I use?
Choose the mode according to the clearance and the phase of flight, rather than leaving LNAV and VNAV engaged for every situation.
| Mode | Use it for | Main caution |
|---|---|---|
| LNAV | Following the active FMC route laterally | Needs a valid active leg and a sensible intercept path |
| VNAV | Following FMC climb, cruise and descent profiles | Needs performance data and is limited by the selected MCP altitude |
| HDG SEL | ATC vectors, route interception and manual headings | The aircraft follows the selected heading, not the FMC route |
| FLCH | Direct climbs or descents to a selected altitude | Uses pitch to maintain speed, so monitor thrust and terrain |
| V/S | Small, controlled altitude changes | It holds vertical speed even if airspeed becomes unsafe |
| ALT HOLD | Maintaining the present altitude | It can override the vertical profile you expected VNAV to follow |
| APP | Arming localiser and glideslope capture for an ILS | The ILS must be valid and intercepted from a suitable position |
For a closer explanation of mode selection, captures and overrides, see our guide to Boeing-style airliner autopilot logic.
How do you make VNAV climb and descend?
VNAV follows the FMC profile only within the altitude permitted by the MCP selector. During climb, it levels at the selected altitude even if the FMC cruise altitude is higher.
Before the top of descent, select a lower cleared altitude on the MCP. If the altitude window still contains the cruise altitude, VNAV will not begin descending. Once a valid lower altitude is selected, VNAV should follow the calculated path and respect programmed constraints.
If the aircraft is already high, use FLCH or V/S to regain the profile while watching airspeed, then reselect VNAV when appropriate. Use speedbrake if the FMC requests additional drag. Avoid pressing altitude intervention without understanding the result, because it can remove a programmed altitude constraint.
How do you use the 787 autopilot for an ILS approach?
The 787 captures an ILS when the approach is loaded, its frequency is valid, and the aircraft reaches the localiser and glideslope from a suitable intercept.
- Load and verify the approach. Select the correct runway and transition in the FMC, then inspect the LEGS page for gaps or incorrect altitude constraints.
- Confirm the ILS. Check the tuned frequency, inbound course and displayed localiser information rather than assuming automatic tuning has worked.
- Intercept from below. Use LNAV or HDG SEL to approach the localiser at a moderate angle while remaining below the glideslope.
- Press APP. Confirm that LOC and G/S first arm and then become active on the FMA. Pressing APP alone does not prove that either signal has captured.
- Monitor the approach. Keep checking speed, flap configuration, landing gear, altitude and FMA changes. Disconnect and go around if the aircraft captures an unsafe or unstable path.
An automatic landing requires additional conditions and correct channel status; APP mode by itself is not an autoland guarantee. Our 787 ILS and autoland procedure explains the remaining approach and landing steps.
Why will LNAV, VNAV or the autopilot not engage?
Most Boeing 787 autopilot failures in MSFS 2020 come from incomplete FMC data, an incorrect active mode or conflicting controller inputs.
- Autopilot disconnects immediately: release control pressure, check for duplicate pitch or roll bindings, disable AI piloting assistance and make sure the aircraft is not in an extreme attitude.
- LNAV remains armed: check that the route is activated, the next leg is valid and the aircraft has a practical intercept. Use HDG SEL to intercept the active leg if necessary.
- VNAV will not descend: select a lower MCP altitude, verify descent data and look for an altitude constraint or route discontinuity blocking the profile.
- The aircraft levels unexpectedly: read the FMA and MCP altitude. ALT HOLD or altitude capture may have replaced VNAV.
- APP will not capture: verify the ILS frequency and course, approach the localiser from a reasonable angle and intercept the glideslope from below.
- The aircraft oscillates: return the simulator to normal simulation rate, check controller calibration and remove duplicate control assignments.
If the engage switch still refuses to hold, work through our autopilot engagement troubleshooting checklist.
How do you disconnect the 787 autopilot safely?
Use the autopilot disconnect switch on the control column or an assigned autopilot-disconnect binding, then confirm that the A/P indication disappears from the FMA. A second press normally silences the disconnect warning.
The autothrottle is a separate system and may remain active after the autopilot is disconnected. If taking manual control of thrust, disconnect it deliberately and match any physical throttle levers to the commanded thrust first; otherwise, the thrust can jump when the hardware axis becomes active.