How do I import a SimBrief plan into the PMDG 737 in MSFS?

On PC, import a SimBrief flight plan into the PMDG 737 in Microsoft Flight Simulator by exporting the PMDG 737 MSFS .rte file to the aircraft's work\Flightplans folder. Enter its base filename in the CDU's CO ROUTE field, then activate, execute and verify the route. Xbox cannot use this file method.

How to load a SimBrief .rte file into the PMDG 737

The most dependable PC workflow is to export PMDG's company-route format and call that file from the CDU's RTE page.

1. Generate a fresh SimBrief OFP. Select the correct 737 variant or a suitably configured aircraft profile, then check the origin, destination, route, cruise level and fuel. The importer uses the generated plan, not unsaved changes. Our SimBrief planning and MSFS transfer checklist covers that preparation in more detail.
2. Download the PMDG route format. Choose the PMDG 737 export intended for MSFS; its filename must end in .rte. Do not select the standard MSFS .pln format for the CDU, because that file belongs to the simulator's pre-flight planner.
3. Place it in the Flightplans folder. The export destination must end in work\Flightplans inside the PMDG aircraft's writable package data. The full path differs between Microsoft Store, Steam and simulator installations, so verify the destination rather than copying a path intended for somebody else's system. If using SimBrief Downloader, check that its PMDG 737 MSFS target ends in this folder.
4. Note the route's base filename. For a file named EGLLLEMD01.rte, enter only EGLLLEMD01 in the CDU. Do not enter the extension, a folder path or the SimBrief flight number unless it is also the actual filename.
5. Load it on the RTE page. Enter the origin and destination shown on the OFP. Type the route's base filename into the scratchpad, then press the line-select key beside CO ROUTE.
6. Activate and execute the route. Review the RTE pages before selecting ACTIVATE and pressing EXEC. Then inspect the LEGS page waypoint by waypoint.
7. Add the procedures and performance data. Select the runway, SID, STAR, approach and transitions through DEP/ARR. Resolve genuine route discontinuities, then complete PERF INIT, N1 LIMIT and TAKEOFF REF rather than assuming the route import has configured the whole aircraft.

A mistake we see constantly is treating a successful CO ROUTE message as proof that the plan is ready to fly. Check the first en-route fix, airway exits, arrival connection and final approach. Do not automatically remove a discontinuity associated with radar vectors; it may be intentional.

Can the PMDG tablet import SimBrief directly?

The PMDG tablet can retrieve SimBrief data, but displaying the operational flight plan does not necessarily mean that the FMC route has been loaded.

Enter the SimBrief username or Pilot ID requested by the installed tablet version, then retrieve the latest generated OFP. If that build explicitly provides an Import, Route Request or Send to FMC command, use it and verify the result on the CDU's RTE and LEGS pages. If the tablet only displays the OFP or offers fuel and payload functions, use the .rte company-route method instead.

Why won't the PMDG 737 load my SimBrief route?

A PMDG 737 SimBrief route usually fails because the file is in the wrong folder, the wrong export format was used, or the SimBrief and FMC navigation databases do not match.

Why is the CO ROUTE file rejected?

A company-route rejection normally means the FMC cannot find or interpret the requested file.

• Confirm that the file is an .rte export, not an MSFS .pln file.
• Check that it is inside the active PMDG package's work\Flightplans folder, not Downloads or the Community root.
• Enter the exact base filename without .rte. Windows may hide known extensions, so also check that the file has not accidentally become name.rte.rte.
• Make sure the CDU origin and destination agree with the route file.
• Regenerate and re-export the OFP after changing the route; direct integrations normally retrieve the most recently generated plan.

Why are airways, waypoints or procedures missing?

Missing fixes and invalid airways usually indicate an AIRAC mismatch between SimBrief and the PMDG FMC, although a renamed waypoint or typing error can cause the same message.

Use the same navigation cycle on both sides where possible. If the CDU reports NOT IN DATABASE, do not force the route past the error: compare the affected airway entry and exit points with the FMC database and select available procedures through DEP/ARR. We have separate diagnostic steps for missing PMDG airways and waypoints.

Does the import include fuel, payload and performance?

No: a company-route file should be treated primarily as the lateral route, not a completed aircraft setup.

The tablet may offer separate fuel and payload loading controls, but confirm the resulting zero-fuel weight, reserves and block fuel against the OFP. Enter or verify the cruise altitude, cost index, reserves, centre of gravity, take-off speeds and thrust settings in the CDU. SimBrief figures are planning data; runway, weather and aircraft-loading changes can alter the final take-off calculation.

Will the SimBrief route also work with MSFS ATC?

No: loading an .rte route into the PMDG FMC does not by itself give Microsoft Flight Simulator's native ATC the same flight plan.

If you want built-in ATC to clear the planned route, load the corresponding MSFS .pln file into the simulator's pre-flight planner, or recreate the same route there before starting the flight. Keep that plan consistent with the PMDG route, especially the departure, arrival and cruising altitude. Our explanation of how native MSFS ATC uses flight-plan data covers the consequences of flying without one.