Fix SimBrief not working in MSFS 2020, including Pilot ID errors, stale OFPs, blank panels, bad imports, navdata mismatches and Xbox limits.
SimBrief usually stops working in Microsoft Flight Simulator 2020 because the aircraft has the wrong SimBrief Pilot ID, no fresh operational flight plan has been generated, the chosen aircraft lacks integration, or the route and simulator use different navdata. Reconnect the account, generate a new OFP, then import it using the aircraft's supported method.
Which SimBrief import method works in MSFS 2020?
MSFS 2020 has no universal SimBrief connection: the correct method depends on the aircraft, platform and type of information you want to import.
| Method | Use it when | Critical limitation |
|---|---|---|
| Aircraft EFB or FMS integration | The aircraft explicitly supports SimBrief | The route, fuel, payload and weather may require separate import actions. Support varies by aircraft. |
MSFS 2020 .pln file | You want the route in the World Map on PC | Export the MSFS 2020 flight-plan format and load it before starting the flight. A PDF OFP cannot be loaded as a route. |
| Toolbar panel | You want to view SimBrief data inside the simulator | A panel does not necessarily programme the aircraft's avionics. |
| SimBrief Dispatch | Not applicable to MSFS 2020 | Dispatch is not an MSFS 2020 integration. Use an aircraft connection, toolbar panel or .pln import instead. |
For the normal planning and import sequence, see our guide to choosing between aircraft integration and an MSFS flight-plan file. If you installed Dispatch expecting it to connect to MSFS 2020, our explanation of the compatible SimBrief alternatives covers that specific mistake.
How do I fix SimBrief not importing?
Most SimBrief import failures can be isolated by checking the generated OFP, account identity and import destination in that order.
- Generate an OFP in SimBrief. Building or editing a route is not enough. Press the option that generates the operational flight plan, because most integrations fetch the latest generated OFP rather than an unsaved route.
- Check the requested account identifier. If the aircraft asks for a Pilot ID or User ID, enter the numeric identifier shown by the SimBrief account, not an email address or display name. If it uses account authorisation instead, sign in with the same account that generated the OFP.
- Generate the plan again after every important edit. Changing the aircraft, route, runway, fuel or payload does not automatically replace the previously generated OFP. An old plan appearing in the cockpit almost always means the revised plan was never generated.
- Import it in the correct place. A World Map
.plnfile does not guarantee that a complex add-on aircraft will populate its EFB or FMS. Likewise, importing through an aircraft EFB may not place the route in the World Map or make it available to default ATC. - Avoid loading the route twice. Do not combine a World Map plan with a second aircraft import unless that aircraft's instructions call for both. Two independent imports can produce duplicated procedures, different runways or a route that changes when the avionics initialise.
- Refresh the connection. Sign out or remove the stored Pilot ID, restart the aircraft session, reconnect the account and fetch the OFP again. This clears expired authorisation and cached account details.
- Test the network separately. If SimBrief can generate an OFP in a browser but the aircraft cannot retrieve it, temporarily test without a VPN, proxy or network-level filter. If no SimBrief function works outside the simulator either, reinstalling MSFS will not solve the underlying account, connection or service problem.
The message No flight plan found normally means there is no generated OFP under the supplied account, the wrong Pilot ID was entered, or the integration is signed into a different account. Reinstalling the whole simulator and clearing scenery caches do not address those causes.
Why does the SimBrief route import with missing waypoints?
A route that imports but contains missing fixes, rejected airways or unavailable procedures usually indicates a navigation-data mismatch rather than a broken SimBrief connection.
SimBrief, MSFS 2020 and a third-party aircraft can each be using a different AIRAC cycle. A waypoint may therefore exist in the generated plan but not in the aircraft database. Our navdata troubleshooting guide explains how to identify and align those databases.
- Missing SID or STAR: confirm that the procedure exists in the aircraft database and matches the selected runway.
- Duplicate departure or arrival: remove the second procedure or use one import workflow rather than loading both the World Map and aircraft versions.
- Unexpected discontinuity: inspect the legs around it before deleting it. Vector and manual legs can legitimately create a discontinuity.
- Route changed by the World Map: selecting a different runway or procedure after loading the file can cause MSFS to recalculate part of the route.
Why is the SimBrief toolbar panel blank?
A blank or missing toolbar panel is usually a panel installation, account or package-version problem, not evidence that the generated flight plan is invalid.
On PC, verify that the panel package is in the active Community folder without an extra nested directory, remove obsolete duplicate copies and restart MSFS after changing it. Then enter the correct Pilot ID and generate a fresh OFP. Our targeted fixes for missing and blank SimBrief panels cover the package and authorisation checks in detail.
Can SimBrief work with MSFS 2020 on Xbox?
SimBrief works on Xbox only where the aircraft provides its own supported account or Pilot ID integration.
Xbox does not expose the normal PC downloads or Community folders, so manual toolbar-panel installation and PC-style .pln file handling are not equivalent options. If an Xbox aircraft has no built-in SimBrief import, use the generated OFP as a reference and enter the route manually into the available avionics.