Learn to fly the Boeing 737 MAX in MSFS 2024, from EFB and FMC setup to take-off, VNAV descent, ILS landing and autopilot fixes.
To fly the Boeing 737 MAX in Microsoft Flight Simulator 2024, load a route and performance data into the FMC, set the MCP, use TO/GA for take-off, follow LNAV/VNAV while checking the flight-mode annunciator, then configure early for the approach and land using the FMC-calculated reference speed.
MSFS 2024 includes a Boeing 737 MAX 8, while third-party versions such as the iFly MAX offer their own systems depth. The basic Boeing workflow is the same, but EFB integration, switch logic, ground services and automated functions can differ. Follow the checklist supplied inside your installed aircraft where it conflicts with a generic procedure.
Boeing 737 MAX flight from gate to landing
The most reliable way to fly the 737 MAX is to prepare the route and performance data before moving, then confirm every automation change on the primary flight display.
- Create a short practice flight. Choose familiar airports, fair weather and an arrival with an ILS. Load realistic fuel and payload rather than filling every tank. Our MSFS 2024 EFB route and loading guide explains how to prepare the flight, but route transfer support depends on the aircraft version.
- Establish electrical and pneumatic power. A runway start normally provides running engines and configured essential systems. From a gate, the usual flow covers battery and standby power, ground power or APU, IRS alignment, fuel pumps, bleed air and engine start. iFly users should follow the aircraft-specific iFly MAX cold-and-dark procedure because its start logic is more detailed.
- Programme and verify the FMC. Enter the origin, destination, route, runway and departure, then complete the performance, thrust-limit and take-off pages. Confirm gross weight, centre of gravity, flap setting, trim and V-speeds rather than guessing them. Use our step-by-step 737 FMC setup if the route contains discontinuities or LNAV will not arm.
- Set the mode control panel. Enter the cleared initial altitude, heading or course as required, turn on both flight directors and arm the autothrottle. Arm
LNAVandVNAVon the ground only when the FMC route and performance data are valid. Do not set the cruise altitude when ATC has assigned a lower initial restriction. - Configure for take-off. Set the calculated flap position and stabiliser trim, select
RTOautobrake, place the speedbrake lever down and complete a flight-control check. Confirm that the runway, initial route and MCP altitude agree with the clearance. - Apply take-off thrust. Line up, stabilise the engines at an intermediate thrust setting, then activate
TO/GA. Check the flight-mode annunciator and engine indications before continuing. At rotation speed, raise the nose smoothly towards the flight-director command; after a positive climb, retract the landing gear. - Clean up and engage the autopilot. At the acceleration altitude, lower the nose as commanded and retract the flaps according to the speed schedule. Engage a
CMDautopilot only after the aircraft is stable and correctly trimmed. The selected autopilot does not guarantee that LNAV or VNAV is active, so read the annunciator. - Prepare the descent before top of descent. Enter the arrival, approach, landing runway, forecast winds and landing reference speed. Resolve any new route discontinuity and set a lower MCP altitude when cleared. VNAV normally remains level if the MCP altitude has not been lowered.
- Configure early for the approach. Reduce speed in stages, extend flaps on schedule, arm the speedbrake, select landing autobrake and lower the gear before final landing flap. For an ILS, verify the frequency and course, intercept the localiser from a sensible angle and below the glideslope, then arm
APP. Our 737 ILS procedure covers capture, configuration and mode monitoring in detail. - Land and decelerate. Disconnect the automation at a height suitable for your experience, maintain the approach speed with the required wind correction, flare gently and close the thrust levers. After touchdown, confirm spoiler deployment, use reverse thrust and braking, then stow the reversers as the aircraft slows.
What should the flight-mode annunciator show?
The flight-mode annunciator, or FMA, shows what the 737 is actually doing; the illuminated MCP button only shows what you requested.
After TO/GA selection, expect take-off thrust and pitch modes. During an automated climb, the roll mode may become LNAV while the pitch mode changes between VNAV speed and path commands. An ILS should produce localiser and glideslope capture indications such as VOR/LOC and G/S.
Active modes normally appear in green and armed modes in white. If the aeroplane is not doing what you expect, inspect the FMA before pressing more buttons. A mistake we see constantly is treating the Boeing MCP like an Airbus managed-mode panel; the 737 has different logic.
Why will LNAV, VNAV or the autopilot not work?
Most 737 MAX automation failures in MSFS 2024 come from incomplete FMC data, an invalid active leg, the wrong MCP altitude or conflicting controller inputs.
| Problem | Likely cause | Fix |
|---|---|---|
| LNAV will not arm | A route discontinuity, no valid active leg or the aircraft is not positioned to intercept the route | Check the FMC legs, resolve the gap correctly and use heading select to establish an intercept if necessary. |
| VNAV will not engage | Missing performance, thrust-limit, take-off or speed data | Complete the required FMC pages, correct scratchpad warnings and execute the changes. |
| VNAV stays level at top of descent | The MCP altitude is still above the aircraft or the descent path has not been reached | Set the cleared lower altitude and monitor the path indication. Use descent intervention only if the installed model supports it and the clearance permits it. |
| CMD disconnects immediately | The aircraft is badly out of trim, a control is being held or a noisy axis is sending inputs | Stabilise and trim the aircraft, centre the controls and add a small dead zone where needed. |
| Autothrottle fights the hardware throttle | Duplicate throttle bindings, assistance features or an unexpected autothrottle mode | Remove duplicate assignments, disable piloting assistance that moves the controls and inspect the FMA before overriding the thrust levers. |
| ILS does not capture | Incorrect tuning, excessive intercept angle, approach mode armed too late or interception from above the glideslope | Verify the approach data, establish a shallow localiser intercept below the glideslope and arm APP before capture. |
Can I learn the 737 MAX from a runway start?
Yes; a runway start is the quickest way to practise take-off, flight-director use, autopilot modes and landing without first learning the full electrical and engine-start sequence.
Do not assume the aircraft is fully programmed just because its engines are running. Verify the route, V-speeds, trim, flap setting, MCP altitude and active modes before releasing the brakes. Once that flight is repeatable, move to a gate start.
Can the Boeing 737 MAX autoland in MSFS 2024?
Use autoland only when the installed aircraft model supports the required dual-channel operation and the selected ILS is suitable; pressing APP by itself does not guarantee an autoland.
For normal practice, allow the autopilot to capture the localiser and glideslope, confirm the FMA, then disconnect and land manually. If the expected second autopilot channel, flare or rollout mode never arms, treat it as a manual landing rather than trying to force the automation.
Does the 737 MAX fly differently from an older 737?
The cockpit technique remains recognisably Boeing 737, but performance figures, engine behaviour, displays and some systems depend on the MAX model being flown.
Always use the MAX aircraft's own calculated thrust, trim and V-speeds instead of copying numbers from an older 737. MCAS is not a normal cockpit mode to select or manage; where it is modelled, it operates in the background under the aircraft's system logic.