Learn the Boeing 747 autopilot in MSFS 2020: FMC and MCP setup, LNAV/VNAV, climb, descent, ILS approach and fixes for failed modes.
To use the Boeing 747 autopilot in Microsoft Flight Simulator 2020, programme the FMC, switch on both flight directors, arm the autothrottle, set the MCP speed, heading and cleared altitude, then engage one CMD channel after take-off. Select LNAV/VNAV or heading and vertical modes, and confirm every mode on the PFD’s flight-mode annunciator.
These instructions apply to the default Boeing 747-8 Intercontinental. Add-on 747s may model extra checks or use different CDU pages, but the Boeing mode logic is broadly the same. MSFS AI piloting assistance is a separate system and should be disabled if it conflicts with your inputs.
Set up the 747 before engaging autopilot
The autopilot follows the route, performance data and targets you give it; it does not repair an incomplete flight plan. A route imported from the MSFS World Map should still be checked in the CDU before departure. Our Boeing-oriented MCP and flight-mode workflow provides more background on how these controls interact.
- Prepare the FMC route. Enter or verify the origin, destination, runway, departure and route, then activate and execute it. Check the LEGS pages for discontinuities, but do not connect across an intentional ATC-vector segment without understanding where the new leg will send the aircraft.
- Complete the performance pages. Enter the required weight, cruise altitude and take-off data. VNAV may refuse to activate or produce unsuitable targets when essential performance information is missing.
- Configure the MCP. Switch both flight directors on, move the autothrottle switch to ARM, set the take-off speed target, select the initial heading and enter the first cleared altitude. Do not enter cruise altitude if ATC or the departure procedure initially limits you to a lower level.
- Take off manually. Use TO/GA when the aircraft is correctly configured, or set take-off thrust manually. Rotate, establish a positive climb, retract the gear and follow the flight director.
- Engage one CMD channel. Once the aircraft is trimmed, stable and at least about 400 feet above the ground, select one available CMD channel. Waiting until roughly 1,000 feet gives beginners more time to stabilise the aircraft. Multiple CMD channels are not needed during ordinary climb or cruise.
- Verify the FMA. Check the flight-mode annunciator across the top of the primary flight display after every selection. The FMA, not merely an illuminated MCP button, tells you which autothrottle, roll and pitch modes are active or armed.
Which 747 autopilot mode should I use?
Choose modes according to whether you want the FMC or the MCP to control the aircraft. For the underlying selected-mode concepts, see our explanation of heading, navigation, altitude, vertical-speed and flight-level-change modes.
| Mode | Use it for | Main limitation |
|---|---|---|
| LNAV | Following the active FMC route laterally | Needs a valid active leg and a sensible intercept; it will not fix a route discontinuity |
| HDG SEL | ATC vectors, runway heading or intercepting the route | Continues towards the selected heading until another lateral mode captures |
| VNAV | FMC-managed climb, cruise and descent | Depends on complete performance data, route constraints and a permissive MCP altitude |
| FLCH | Prompt climbs or descents while protecting selected airspeed | Does not follow an FMC vertical path or automatically honour every route constraint |
| V/S | Small, controlled vertical corrections | Prioritises the selected rate and can produce low or excessive airspeed if poorly monitored |
| ALT HOLD | Maintaining the present or captured altitude | Changing the altitude window alone does not command a climb or descent |
| APP | Capturing an ILS localiser and glideslope | Requires the correct ILS setup and a suitable intercept |
For a routine climb, LNAV and VNAV are the simplest combination when the FMC route is correct. If ATC gives a vector, use HDG SEL; if it gives an immediate altitude change that does not fit the VNAV profile, set the cleared altitude and use FLCH. Retract the flaps on schedule because the autopilot does not operate the gear, flaps or speedbrakes for you.
How do I make the 747 descend with VNAV?
Enter and execute the arrival, check its altitude constraints, then lower the MCP altitude before top of descent when cleared. VNAV should remain at cruise altitude until the calculated descent point and then follow the vertical path, provided the route is valid and the selected altitude permits descent.
If an immediate descent is required before the calculated point, FLCH is usually clearer and more predictable. Where altitude intervention is modelled, pressing the altitude selector can initiate an early VNAV descent or remove a constraint; check the LEGS page first rather than pressing it repeatedly. Use speedbrakes cautiously if the aircraft is above profile, and retract them before adding substantial thrust.
Why won’t LNAV, VNAV or CMD engage?
Most 747 autopilot failures come from an invalid route, missing FMC data, unsuitable MCP targets or a controller input that keeps disconnecting CMD. Work through the symptom rather than repeatedly pressing the same mode button.
- CMD will not engage: make sure the autopilot-disengage bar is not pulled down, the aircraft is airborne and stable, and the controls are close to neutral. Check for duplicate or noisy pitch, roll and autopilot-disconnect bindings.
- LNAV will not activate: confirm that the route was executed, an active leg exists and there is no discontinuity ahead. Use HDG SEL to establish a reasonable intercept angle if the aircraft is too far from the active leg.
- VNAV will not activate: complete the FMC performance data, check the active route and verify that the MCP altitude allows movement in the required direction.
- The altitude does not change: setting a new number in the altitude window is only permission. Select VNAV, FLCH or V/S to command vertical movement.
- The aircraft turns unexpectedly: inspect the active FMC leg. A direct-to selection, route discontinuity or vector leg can produce a turn that is correct for the data but wrong for your intention; use HDG SEL while correcting it.
- The aircraft hunts or oscillates: return simulation rate to normal, remove conflicting controller inputs and confirm sensible airspeed, weight and trim. Disconnect the autopilot and stabilise manually if the motion continues.
- Speed appears uncontrolled: the autothrottle and autopilot are separate systems. Check the A/T switch and the autothrottle mode shown on the FMA; disconnecting CMD does not automatically disconnect A/T.
If CMD still refuses to remain connected, use our autopilot engagement troubleshooting checklist to isolate assistance settings, bindings and aircraft-state problems.
Can the MSFS 2020 Boeing 747 autoland?
Yes, the default 747 can fly a coupled ILS approach and model an autoland when the runway, ILS signal and aircraft configuration are suitable. Verify the ILS frequency and front course, intercept the localiser from a shallow angle while below the glideslope, press APP, and confirm that LOC and G/S arm and capture on the FMA.
You must still manage speed, flaps, landing gear and the approach checklist. One CMD channel can fly a coupled approach, while an autoland requires the additional autopilot channels and the correct landing-status indication. Our complete 747 ILS autoland procedure covers the capture geometry, channel engagement and status checks.
Disconnecting the autopilot for a manual landing
Stabilise the aircraft, take the controls and use the yoke autopilot-disconnect switch or its assigned control. A second press normally silences the disconnect warning. Decide separately whether to retain or disconnect the autothrottle, because A/T remains active after CMD is disengaged.