MSFS ATC cannot read a route stored only in the PMDG 737 FMC. Learn how to file the same IFR plan, fix mismatches and handle ATC vectors.
Microsoft Flight Simulator’s built-in ATC does not read a route entered or imported only into the PMDG 737 FMC. The aircraft’s FMC and the simulator’s ATC flight-plan system are separate. File the same IFR route through the World Map or MSFS 2024 EFB, then load and activate it independently in the PMDG CDU.
Why can't MSFS ATC see the PMDG route?
The PMDG FMC controls aircraft guidance; it does not file a flight plan with MSFS ATC. Pressing EXEC activates the route for the 737’s LNAV and VNAV systems, but it does not transmit that route to the simulator.
| System | What its flight plan controls | What it does not control |
|---|---|---|
| PMDG 737 FMC | LNAV route, VNAV profile, performance calculations and navigation display | MSFS ATC clearance, routing or runway assignment |
| MSFS World Map or EFB | Built-in ATC’s filed route, destination and expected procedures | The PMDG FMC’s active route |
For example, importing a PMDG .rte file and loading an MSFS .pln file feed different systems. A mistake we see constantly is importing a SimBrief route into the CDU and assuming that ATC received it too.
How do I make ATC use the same flight plan?
You must place matching copies of the route in the MSFS planning system and the PMDG FMC.
- Create one master route. Build it in the simulator or with SimBrief, including the correct origin, destination, cruise altitude and intended procedures. Our SimBrief planning and import workflow explains how to avoid creating conflicting copies.
- File it with Microsoft Flight Simulator. In MSFS 2020, create or load an IFR plan on the World Map before starting the flight. In MSFS 2024, create or import it in the EFB and use the option that sends or files the route with ATC. Merely displaying a route in the EFB is not enough. See our explanation of how MSFS stores and passes an IFR flight plan if the planner, EFB and aircraft disagree.
- Load the PMDG FMC separately. Enter or request the route through the CDU, complete the departure and arrival pages, resolve route discontinuities and press EXEC. Do not rely on a generic “send to avionics” function to configure every part of the PMDG FMC.
- Compare both copies. Check the departure runway, SID and transition, en-route fixes, STAR, approach and destination runway. Editing one copy does not update the other.
- Request and read the IFR clearance. “Cleared as filed” refers to the route held by MSFS, not necessarily the one displayed on the PMDG LEGS page. Our guide to using built-in ATC and reading its instructions covers the clearance and hand-off sequence.
If MSFS 2020 does not offer the expected IFR clearance after the flight has loaded, the dependable fix is to return to the World Map and load the IFR plan before starting again. Changing the PMDG FMC alone will not create an ATC flight plan.
Why does ATC still change my runway or route?
A matching filed route does not stop ATC from issuing vectors, direct clearances, altitude restrictions or a different runway. ATC may modify the terminal part of the route for its own traffic and runway logic, while the FMC continues displaying the originally programmed procedure.
- Runway mismatch: ATC has assigned a different departure or arrival runway from the one selected in the FMC.
- Procedure mismatch: the World Map or EFB contains a SID or STAR that was omitted or changed in the CDU.
- Navdata mismatch: the simulator and PMDG navigation databases interpret a procedure or waypoint differently.
- Vectors segment: a departure or arrival expects radar vectors rather than continuous LNAV guidance.
- Route edited after filing: changes made in the FMC were not repeated in the simulator’s filed plan.
When ATC assigns a heading, use HDG SEL rather than forcing LNAV to follow the magenta line. When cleared direct to a waypoint or told to resume own navigation, select the appropriate direct-to leg and re-engage LNAV. Likewise, set the MCP to the altitude ATC actually cleared; the FMC’s VNAV profile does not override an ATC restriction.
Is it an ATC problem or a PMDG LNAV problem?
If ATC clears the expected route but the aircraft does not follow it, the fault is in the FMC or autopilot setup rather than ATC.
- No IFR clearance, the wrong destination or references to an old route indicate an MSFS filing problem.
- A lit EXEC key, an inactive route, a route discontinuity or the wrong active leg indicates an FMC setup problem.
- A correct active leg but no turn towards it indicates an LNAV or autopilot mode problem.
- An explicit ATC heading or “expect vectors” instruction is normally intentional vectoring, not a missing FMC waypoint.
If the aircraft is the part going off-route, use our checklist for diagnosing inactive routes and LNAV/VNAV problems. If built-in ATC persistently departs from a correctly filed plan, choose between following its headings manually or cancelling IFR services and flying the FMC route without expecting ATC guidance.