How do I import a SimBrief plan into MSFS 2024?

Generate your operational flight plan in SimBrief, open Microsoft Flight Simulator 2024’s EFB or the aircraft’s supported tablet/FMS, connect the account that owns the plan, and select Import or Request. Then transfer the route to the avionics if supported and check procedures, discontinuities and the active first leg.

How do I link SimBrief to MSFS 2024?

You link SimBrief from the EFB, tablet or FMS that will request the plan; there is no universal account link that automatically supplies every aircraft in MSFS 2024.

SimBrief uses the Navigraph account system. The stock EFB may present an account-authorisation prompt, while an aircraft-specific integration may ask for a SimBrief username or numerical Pilot ID instead. Enter the identifier named by that field—an email address will not necessarily work in a username or Pilot ID box.

• Use the account that generated the plan: a valid login to a different account will return no flight or the wrong flight.
• Generate the OFP: integrations normally fetch the latest completed operational flight plan, not a route still being edited.
• Expect separate aircraft settings: authorising the main EFB does not guarantee that a third-party tablet or FMS has inherited the same credentials.
• No paid subscription is required for the basic SimBrief plan: chart and current-navdata services are separate, although differing AIRAC cycles can affect the imported route.

How do I get SimBrief in the MSFS 2024 EFB?

You do not normally install a separate SimBrief panel in MSFS 2024. Use the SimBrief import offered by the built-in EFB Planner, or the tablet, MCDU, CDU or FMS supplied with a supported aircraft.

There is no single panel that adds direct SimBrief loading to every cockpit. If an aircraft has no import function, keep the OFP open in the main EFB and enter the route manually, or recreate it with the simulator’s planner.

How do I import a flight plan from SimBrief to MSFS 2024?

The most reliable method is to generate the OFP, import it through one chosen route source, and then verify the result inside the aircraft before filing with ATC or departing.

1. Create the flight in SimBrief. Select the correct aircraft profile, origin, destination, route, cruise level and planning assumptions. Generate the operational flight plan and wait for the completed OFP; saving an unfinished route is not enough.
2. Decide which system will own the route. Use the aircraft’s own integration for a complex airliner when available. The MSFS 2024 EFB is a sensible choice for default aircraft and simpler avionics. Avoid testing this workflow inside a career or activity flight that already supplies its own route; Free Flight gives you control of the plan.
3. Open the appropriate EFB, panel or FMS. Find the SimBrief, dispatch, flight-planning or company-route page. Labels differ by aircraft, but the relevant command will usually be described as Import, Load, Fetch or Request.
4. Authorise the account or enter the requested identifier. Use the same account that owns the generated OFP. If the interface asks specifically for a username or Pilot ID, do not substitute another account field.
5. Fetch the latest generated flight. Confirm that the origin, destination, flight number and aircraft match the flight you intend to fly. Most integrations retrieve the newest OFP, so generating another dispatch can replace the plan they find.
6. Review the plan before transferring it. Check the route, cruise level, alternate, departure runway, SID, arrival, STAR and approach. SimBrief may leave a procedure open for later selection, and live weather or built-in ATC may favour a different runway.
7. Send or load the route into the avionics. Use Send to Avionics where the MSFS EFB and aircraft support it, or use the aircraft’s own FMS request. An OFP appearing in the EFB does not by itself prove that the cockpit flight plan has been programmed.
8. Inspect the LEGS or flight-plan page. Look for missing waypoints, doubled procedures, route gaps and an invalid first leg. Do not automatically delete every discontinuity: one associated with radar vectors or a manual segment may be intentional.
9. Handle ATC and the starting position separately. Sending a route to the avionics does not always file it with the simulator’s ATC, and filing with ATC does not always programme the FMS. Choose the required gate or parking stand and use a separate ATC filing command where offered.

Should I load SimBrief through the EFB, aircraft panel or FMS?

Use the aircraft’s own SimBrief integration when it directly programmes that aircraft’s avionics; otherwise use the MSFS 2024 EFB as the main planning source.

For a route without direct SimBrief support, our guide to using the built-in MSFS flight planner without SimBrief covers the alternative workflow. It is fine to display the OFP in more than one place; the mistake is programming the lateral route through two different import paths.

What does a SimBrief import actually load?

A SimBrief import supplies dispatch data, but it is not a complete aircraft setup.

• Usually available: origin, destination, en-route waypoints, airways, cruise level and other OFP details.
• Dependent on the importer: runways, SIDs, STARs, transitions, approaches, alternate, fuel figures and payload data.
• Usually still required: FMS initialisation, performance entries, take-off flap setting, thrust data, V-speeds, reserves and the initial cleared altitude.
• Separate simulator tasks: loading fuel or payload into the aircraft, selecting a parking stand and filing the route with built-in ATC.

Never assume that figures visible on the OFP have changed the aircraft’s actual fuel or weight. Confirm them on the aircraft’s loading and performance pages.

Why will SimBrief not load into MSFS 2024?

Most failed imports come from an ungenerated plan, the wrong account identifier, incompatible navdata or an EFB route that was never transferred to the avionics.

No flight appears, or an old flight is loaded

Confirm that the intended OFP was fully generated and is the newest plan on the linked account. Check whether the integration wants an account authorisation, username or Pilot ID, then sign out and reconnect if stored credentials belong to another account.

If other add-ons also fail to find the plan, the account, identifier and stale-plan checks in our SimBrief synchronisation guide for GSX Pro apply to many of the same detection faults.

The plan is in the EFB but not in the cockpit

The EFB has imported the OFP but has not programmed the aircraft’s avionics. Use Send to Avionics if that aircraft supports it, request the flight through the aircraft’s own FMS, or enter the route manually.

Some aircraft deliberately keep their navigation system separate from the generic EFB. Repeatedly importing the plan into the EFB will not overcome that design.

The SID, STAR or approach is missing

Compare the AIRAC cycle printed on the SimBrief OFP with the cycle reported by the aircraft’s navigation database. If a planned procedure or waypoint does not exist in the cockpit database, the importer may omit it, substitute another fix or leave a discontinuity.

A procedure can also be absent because no runway was selected during planning, or because the importer expects you to choose the arrival after receiving weather. Select a valid procedure from the aircraft database and amend the route rather than forcing an obsolete one.

The route contains duplicate waypoints or a loop

Clear the cockpit flight plan and import it once through the method you intend to use. Duplicates commonly appear after loading through both the World Map and aircraft tablet, or after importing a route that already contains a procedure and then adding that procedure again in the FMS.

Inspect the transition before deleting a repeated fix. Some procedures legitimately revisit a waypoint; the map and leg sequence will show whether it is a real loop or part of the published route.

ATC assigns a different runway or route

Built-in ATC can choose a runway from its own wind and traffic logic, independently of the SimBrief dispatch. Either update the procedures in the avionics and recheck the route, or keep the dispatch route and accept that the simulator’s ATC plan may not match it.

If you use built-in ATC, file only after settling the final route where practical. Filing and then replacing the avionics plan is a common source of conflicting clearances.

NAV or LNAV will not follow the imported route

A successful import does not activate the correct leg or navigation mode automatically. Check that the flight plan is active, the first usable leg is selected, the CDI source is GPS/FMS rather than VLOC, and the aircraft is positioned to intercept the path.

Airliners may require heading mode before NAV or LNAV can capture the departure. Once lateral tracking is established, our guide to setting the initial altitude and speed modes in MSFS 2024 covers the next part of the automation setup.

How do I start the imported SimBrief plan correctly?

Before taxi, verify the route in the cockpit rather than relying solely on the magenta line shown in the EFB.

• Check the route ends: confirm the correct departure and destination airports and ensure the first leg makes sense from your runway or SID.
• Review every procedure join: inspect the SID-to-route and route-to-STAR transitions for gaps, sharp reversals or doubled fixes.
• Load the aircraft: set the actual fuel and payload, then complete the required performance pages and take-off data.
• Set the departure controls: enter the initial altitude, select the correct navigation source and arm the appropriate flight-director modes.
• Recheck the arrival later: weather and runway use can change during the flight, so confirm the STAR, transition and approach before descent.

If the imported route ends with an instrument approach, follow the aircraft’s normal approach programming rather than expecting SimBrief to tune and capture it automatically. Our MSFS 2024 ILS setup and capture procedure explains that final stage.