Why is Boeing 737 MAX LNAV not working in MSFS 2024?
Fix Boeing 737 MAX LNAV in MSFS 2024 by checking FMC execution, route gaps, IRS alignment, intercept geometry and flight-mode annunciations.
LNAV fails in the Boeing 737 MAX in Microsoft Flight Simulator 2024 when the FMC route is inactive, a leg is broken or behind the aircraft, the IRS is not ready, or the jet cannot intercept the magenta path. Execute the route, select a valid leg, establish an intercept and confirm LNAV on the FMA.
How to fix 737 MAX LNAV in MSFS 2024
The quickest method is to inspect the Flight Mode Annunciator first, then work backwards through the FMC route and aircraft position.
- Read the FMA, not just the LNAV button. The FMA at the top of the Primary Flight Display shows what the aircraft is actually doing. An illuminated MCP button may mean LNAV has only been selected or armed. Depending on the aircraft implementation, an active mode is normally green and an armed mode white.
- Confirm that the IRS is ready. After a cold-and-dark start, place the IRS selectors in NAV, initialise the aircraft position if the model requires it, and wait for alignment to complete. An unreliable aircraft position prevents the FMC from calculating usable lateral guidance.
- Activate and execute the FMC route. Check the RTE and LEGS pages for the correct origin, destination and departure. If the CDU still shows a modified route or the
EXEClight is illuminated, pressEXEC. A route visible in the MSFS 2024 EFB, World Map or Navigation Display is not proof that the FMC route has been activated. Our complete Boeing FMC route-entry sequence covers this process without duplicating it here. - Inspect the active leg. The first active waypoint on the LEGS page should be ahead of the aircraft and correspond to the magenta route. If it is behind the aircraft, select a suitable waypoint ahead and activate a direct-to leg using the CDU, then execute the change.
- Resolve the correct discontinuities. A normal route discontinuity can be closed by moving the following waypoint over the gap and executing the modification. Do not automatically remove a
VECTORor manual leg: these often mean ATC or the pilot must use HDG SEL before intercepting the next route segment. - Create an intercept LNAV can capture. If the aircraft is well away from the route, use HDG SEL to approach the active magenta leg at a sensible angle. Select LNAV again before reaching it. Choosing a waypoint behind the aircraft, or trying to capture a leg from the wrong side at a steep angle, commonly leaves LNAV armed without engaging.
- Check the flight directors and autopilot. Normal departure configuration has both flight directors on. LNAV can supply flight-director guidance without CMD engaged, but the aircraft will not fly that guidance automatically until the autopilot is engaged; otherwise, follow the command bars manually.
What does the LNAV indication mean?
The FMA distinguishes an armed mode from an active one, which makes it the best clue to the fault.
| Symptom | Likely meaning | Action |
|---|---|---|
| LNAV button lit, but no LNAV on FMA | The mode was selected but its engagement conditions are not satisfied | Check the active route, IRS and flight-director state |
| LNAV armed on FMA | The route exists, but capture geometry is not yet suitable | Use HDG SEL to intercept the active leg |
| LNAV active, but aircraft does not turn | The flight director is commanding the turn, but the autopilot is not controlling the aircraft | Engage CMD when permitted or hand-fly the command bars |
| LNAV commands a turn back | The active waypoint or leg is behind the aircraft | Activate a waypoint ahead and execute the new leg |
| No magenta route appears | The route is inactive, unexecuted or the aircraft position is unavailable | Check RTE, LEGS, EXEC and IRS status |
Can LNAV be armed before take-off?
LNAV can normally be armed on the ground when the FMC route is active and the first route leg is valid for the departure.
It should become active after take-off once the model's engagement conditions are met. If the departure begins with a vector, an unusual runway transition or a leg that does not align with the runway, fly the initial heading in HDG SEL and intercept the first usable leg later. Do not make low-level turns merely to force an immediate LNAV capture.
Does incomplete VNAV setup stop LNAV working?
Missing performance data normally affects VNAV rather than LNAV, because lateral guidance mainly needs a valid aircraft position and an active route.
If both LNAV and VNAV refuse to engage, check IRS alignment, route activation, discontinuities and pending FMC modifications before changing autopilot settings. Our 737 lateral and vertical mode fault tree covers combined LNAV and VNAV failures.
Is the fix different for the included 737 MAX and iFly MAX 8?
The core logic is the same, but route importing, EFB synchronisation and avionics modelling differ between the included Boeing 737 MAX and the iFly 737 MAX 8.
Do not assume that an EFB import used by one aircraft will produce an executed FMC route in the other. For the add-on, follow our iFly-specific MCP, FMC and LNAV procedure.
Why does LNAV disconnect after it engages?
If LNAV becomes active and then drops out, the problem is more likely an autopilot disconnect, a conflicting control input or a changed lateral mode than an invalid route.
- Check whether CMD has disconnected and whether the FMA has changed to HDG SEL, CWS or another mode.
- Look for duplicate aileron, elevator, autopilot-disconnect or trim bindings across every connected controller.
- Return to HDG SEL, stabilise the aircraft, establish a clean intercept and arm LNAV again.
- If the entire autopilot keeps disconnecting, use our broader MSFS autopilot and controller checks.