How do you fly the Boeing 747-8 in MSFS 2020?

To fly the Boeing 747-8 in Microsoft Flight Simulator 2020, load and verify the FMC route, calculate take-off data, set the MCP, use TO/GA for departure, follow LNAV/VNAV while monitoring the flight-mode annunciator, programme the arrival before top of descent, then fly a stabilised approach at the FMC’s calculated VREF.

This workflow applies to the fully updated default Boeing 747-8 Intercontinental. Third-party 747 add-ons may use different systems and procedures. Use the Modern flight model, disable any assistance that moves the controls for you, and confirm that your throttle, rudder and brake axes are not duplicated.

What should I set up before take-off?

Before taxi, the 747 needs a valid route, complete performance data and MCP selections that agree with the planned departure.

1. Load fuel and payload first. Avoid filling every tank unless the flight requires it. An unnecessarily heavy 747 accelerates slowly, needs more runway and is harder to manage on approach. If you change the payload afterwards, recalculate the take-off speeds and trim.
2. Power and initialise the aircraft. A runway start handles most of this automatically. For a gate departure, follow our complete 747-8 cold-and-dark start sequence for electrical power, IRS alignment, the APU and all four engines.
3. Build and inspect the FMC route. Enter the origin, destination, runway, SID, en-route waypoints, STAR and approach. A route imported from the MSFS World Map can still contain a discontinuity or the wrong runway, so inspect every LEGS page and execute pending changes. Our airliner FMC setup guide explains route entry, performance initialisation and procedure selection in detail.
4. Complete the performance pages. Enter or confirm gross weight, reserves, cost index and cruise altitude. On the take-off pages, select the intended flap setting, calculate V1, VR and V2, and set the displayed stabiliser trim. Do not invent V-speeds or reuse values from a previous flight.
5. Set the MCP. Set the cleared initial altitude, V2 in the speed window and the assigned heading or runway track. Switch on both flight directors, arm the autothrottle and arm LNAV or VNAV only when the programmed route and departure support them.
6. Finish the runway checks. Set local QNH, select take-off flaps, choose RTO autobrake, confirm the trim and verify that the PFD shows all three take-off speeds. Do not depart with a take-off configuration warning.

Taxi slowly and anticipate turns. The 747’s length and mass make late steering inputs and repeated heavy braking particularly noticeable.

How do I take off and climb the 747-8?

Take off by stabilising the engines, selecting TO/GA, rotating smoothly at VR and following the flight director while retracting the flaps on schedule.

1. Line up accurately. Centre the aircraft on the runway, release the brakes and advance the thrust enough for all four engines to stabilise.
2. Select TO/GA. Verify take-off thrust and check the flight-mode annunciator at the top of the PFD. If the cockpit switch is awkward to operate, assign the simulator’s TO/GA command to a convenient control.
3. Monitor the take-off roll. Keep the aircraft on the centreline with small rudder inputs. At V1, continue unless the simulator presents a failure serious enough to prevent flight. Begin a smooth rotation at VR rather than pulling abruptly.
4. Follow the flight director. Raise the nose at roughly two to three degrees per second and avoid chasing a fixed pitch angle. When the aircraft has a positive climb rate, retract the landing gear.
5. Accelerate and clean up. At the programmed acceleration point, let VNAV command acceleration or select a safe speed manually. Retract each flap stage only after passing its corresponding indication on the speed tape; retracting everything immediately can remove the lift margin.
6. Engage the autopilot when stable. A practical simulator technique is to hand-fly through the initial departure and engage one CMD channel between about 400 and 1,000 feet above ground, once the aircraft is trimmed, climbing and following the intended lateral path.

The flight-mode annunciator is the authority. A mistake we see constantly is assuming that an illuminated MCP button proves a mode is controlling the aircraft. Check what is actually annunciated after every selection. For the full mode sequence, see our 747-8 autopilot and FMC guidance for MSFS 2020.

Choosing the right 747 autopilot mode

During the climb, observe speed restrictions, set standard pressure at the applicable transition altitude and check that the aircraft captures each cleared altitude. At cruise, monitor fuel, route progress and the LEGS page rather than leaving the automation unattended.

How do I descend and land the 747-8?

Programme and verify the arrival before top of descent, set a lower cleared altitude on the MCP, manage the aircraft’s energy early and establish a stable landing configuration before final approach.

Cruise and descent preparation

1. Select the arrival. Load the expected STAR, runway and approach, then inspect the resulting legs and altitude constraints. Changing the runway can replace part of the route, so check it again after every modification.
2. Prepare the landing data. Set the destination QNH, landing flap, calculated VREF, wind correction, minima, autobrake and any required navigation data.
3. Set the cleared altitude. VNAV normally will not descend through the altitude displayed on the MCP. Before top of descent, set the next altitude authorised by ATC or the procedure.
4. Watch the vertical path. If the aircraft remains high, reduce speed early or use the speedbrake as required. A useful cross-check is approximately three nautical miles for every 1,000 feet to lose, plus extra distance for slowing and configuring.

If VNAV passes top of descent without descending, first check the MCP altitude, the active route leg and the FMC descent profile. Do not force a very high aircraft down with an extreme vertical speed; extend the path or level temporarily to reduce speed.

ILS approach and landing

1. Intercept the localiser sensibly. Use LNAV or HDG SEL to approach the final course at a modest angle. Verify the ILS identifier and approach data, remain below the glideslope during capture, then arm APP.
2. Configure in stages. Reduce speed before selecting each flap setting. Extend the landing gear with enough time to stabilise, select the planned landing flap and fly the FMC’s VREF plus the required wind additive.
3. Complete the landing setup. Arm the speedbrake, select an appropriate autobrake setting and confirm the gear, flaps and landing checklist. By about 1,000 feet above the runway, the aircraft should be on course, on glidepath, correctly configured and at a stable speed.
4. Flare gently. Disconnect the automation at a height that leaves enough time to settle into manual flight. Reduce thrust and make a small flare rather than holding the aircraft far above the runway.
5. Decelerate after touchdown. Lower the nose smoothly, verify spoiler deployment, apply reverse thrust and monitor the autobrakes. Reduce reverse as the aircraft slows and take manual braking before leaving the runway.

APP capture alone is not proof that the aircraft is configured for autoland. Unless the PFD shows the required multi-channel status and you understand the system, plan to disconnect and land manually. Our detailed 747 landing workflow covers VREF, flare technique, spoilers, reverse thrust and braking.

If the approach becomes unstable, press TO/GA, follow the flight director, confirm positive climb, retract the gear and clean up the flaps in stages. A go-around is safer and usually quicker than trying to rescue a high, fast or badly aligned 747.

Why will LNAV, VNAV or the autopilot not work?

Most 747 automation failures in MSFS 2020 come from incomplete FMC data, a blocked MCP altitude, an invalid route leg or conflicting controller inputs.

• LNAV will not engage: activate and execute the route, remove unintended discontinuities, select a valid active leg and use HDG SEL to establish an intercept if the aircraft is too far from the route.
• VNAV is unavailable: complete the PERF INIT and take-off data, enter a cruise altitude and confirm that the FMC has a valid vertical profile.
• The aircraft will not descend: set the MCP below the present altitude, verify that the next constraint permits descent and check that the arrival remains connected to the active route.
• APP does not capture: confirm that an ILS approach is selected, verify the navigation data, intercept the localiser from a reasonable angle and approach the glideslope from below.
• The autopilot disconnects: centre the controls, reduce excessive bank or pitch, check trim and remove duplicate autopilot-disconnect or control-axis bindings. Noisy joystick inputs can continually override the automation.
• Thrust changes unexpectedly: check the autothrottle arm switch and the active thrust mode. When disconnecting autothrottle, match the physical throttle levers to the commanded position first to prevent a sudden thrust jump.
• The aircraft oscillates: return the simulator to normal simulation rate, verify weight and centre of gravity, and avoid rapid control corrections. The 747 responds slowly; repeatedly chasing the flight director usually makes the deviation worse.