Fix the MSFS 2024 flight planner when it will not open, build, transfer or follow a route, with checks for the EFB, avionics, NAV source and add-ons.
The MSFS 2024 flight planner usually appears not to work because the EFB route has not been transferred to the aircraft, the chosen aircraft lacks full planner integration, or the avionics have no active leg or correct NAV source. Planner freezes can instead come from input focus, a lost online session or conflicting add-ons.
Match the flight planner problem to its cause
The fastest diagnosis is to separate a planner interface fault from a route-transfer or autopilot fault.
| Symptom | Likely cause | First check |
|---|---|---|
| Planner is blank, frozen or ignores input | EFB focus, online-session or interface problem | Reopen the panel, restore pointer focus and restart the simulator |
| Route will not calculate or a procedure is missing | Incompatible runway, SID, STAR or airport data | Build a direct route without procedures |
| Route exists in the EFB but not in the cockpit | It was not transferred, or the aircraft does not support transfer | Use the transfer command and inspect the aircraft FMS |
| Route is visible but the aircraft ignores it | Wrong NAV source, no active leg, a discontinuity or the wrong autopilot mode | Activate a valid leg and select GPS or FMS navigation |
MSFS 2024 treats the planner route, the aircraft avionics route and the ATC flight plan as related but separate items. Creating or filing one does not guarantee that the other two have updated. Our explanation of how the built-in planner hands routes to the cockpit covers that workflow in more detail.
How do I fix the MSFS 2024 flight planner?
A simple route in an unmodified aircraft will reveal whether the fault is in the simulator, the aircraft or the chosen route.
- Run a clean baseline test. Choose a default aircraft with a route-capable GPS or FMS, two unmodified airports and a direct route with no SID, STAR or approach. If this works, the core planner is functioning and the original aircraft, airport or procedure needs attention.
- Reset the planner interface. Close and reopen the EFB or World Map panel, make sure the simulator is signed in and online, then restart it if the map or controls remain frozen. If the entire tablet will not open or accept input, use our specific EFB display and input checks.
- Rebuild the route in a stable order. Select the departure, arrival and runways before adding procedures. If changing a runway leaves odd transitions or duplicate legs, delete the route and calculate it again rather than repeatedly editing the broken version.
- Transfer the route explicitly. Use the command that sends or loads the route into the aircraft avionics; its wording can vary. Filing with ATC is not the same operation.
- Inspect the cockpit flight plan. Power and initialise the avionics, confirm that the waypoints arrived, and complete any aircraft-specific activate or execute step. Select a valid leg ahead of the aircraft.
- Set the correct navigation source. A glass cockpit normally needs GPS or FMS selected rather than VOR or LOC. Use NAV or the aircraft's LNAV mode only after the route is active and the aircraft is positioned to intercept it.
- Remove conflicts. Temporarily disable aircraft, airport, avionics and planner-related add-ons. On PC, test with third-party Community packages moved out; on consoles, disable the relevant installed add-on and restart the simulator.
If the clean route works only in one aircraft, the issue is aircraft integration. If it fails only at one airport, suspect that airport or its procedure data. Failure across every default aircraft and unmodified airport points instead to the simulator session, online services or installed files.
Why will the flight plan not transfer to the avionics?
An EFB route will not appear in every cockpit because route import support depends on the aircraft and its avionics implementation.
Some aircraft accept the complete route, while others import only basic waypoints or require the route to be entered through their own FMS. A vintage aircraft without a route-capable navigator cannot display a magenta GPS route at all. More complex airliners may also require departure and arrival procedures to be selected or confirmed inside the cockpit.
Transfer the route again after making EFB changes; edits are not guaranteed to synchronise continuously. Then check for an active leg, an unexecuted modification or a discontinuity in the cockpit flight plan.
Why are SIDs, STARs or waypoints missing?
Missing procedures usually indicate incompatible route choices or a mismatch between the planner, airport and aircraft navigation data.
- Remove the SID, STAR and approach, calculate a direct route, then add each procedure back separately.
- Confirm that the procedure belongs to the selected runway and that its transition connects sensibly to the en-route section.
- Test without a custom airport. An add-on can retain an obsolete runway designation or conflict with the navigation data used by the planner.
- Replace imported or custom waypoints that the aircraft FMS does not recognise.
A VECTOR leg or route discontinuity is not always an error. It may require heading mode and pilot intervention before the next leg can be activated; deleting it blindly can produce an unrealistic turn.
Why does autopilot ignore a valid flight plan?
A visible route does not mean the autopilot has the correct navigation source, active leg or capture geometry.
Confirm that the CDI or navigation source shows GPS or FMS, not VOR or LOC. Activate a forward leg, clear accidental direct-to selections, and use heading mode to establish a reasonable intercept if the aircraft is far from the route. NAV or LNAV may remain armed without capturing when the course angle is excessive or a discontinuity blocks the sequence.
If the planner and cockpit route are correct but the aircraft still will not follow them, work through our NAV source, active-leg and autopilot mode checks.
Should I reinstall MSFS 2024?
Reinstallation is a last resort because it will not fix unsupported aircraft integration, a malformed route or a temporary online-service fault.
First restart the platform, confirm the simulator update completed, remove third-party content and retest with the clean baseline route. If the failure began after an update and affects default aircraft everywhere, follow our post-update repair and add-on isolation process before downloading the entire simulator again. Avoid deleting cloud saves or controller profiles merely to repair the planner.