How do I use SimBrief with the iFly 737 MAX in MSFS 2024?

To use SimBrief with the iFly 737 MAX in Microsoft Flight Simulator 2024, generate a 737 MAX flight in SimBrief, save your SimBrief Pilot ID in the iFly tablet, retrieve the operational flight plan, then load its route into the FMC. Check procedures, fuel, payload and route discontinuities before execution.

How do I connect SimBrief to the iFly tablet?

Enter the SimBrief identifier requested by your installed iFly build in the aircraft tablet—usually the numeric Pilot ID, not your email address. The location and wording can move between iFly updates, but it will be within the tablet's account, integration or SimBrief settings.

In SimBrief, select an iFly-specific 737 MAX 8 airframe profile if one is available; otherwise use the standard 737 MAX 8 profile, normally identified as B38M. Confirm the units, passenger load, cargo, departure and destination before generating the flight. Our explanation of building the dispatch and choosing the correct aircraft profile covers that preparation in detail.

The flight must be generated, not merely saved or edited. Aircraft integrations normally retrieve the latest generated operational flight plan associated with that account.

How do I import the SimBrief route into the iFly FMC?

Retrieve the generated flight through the iFly tablet first, then use the aircraft's route-loading function to place it in the FMC.

1. Generate the final SimBrief OFP. Regenerate it after changing the route, fuel, payload, runway or cruise level; the iFly cannot retrieve unsaved edits.
2. Power the aircraft and avionics. The tablet may operate before the FMC is fully ready, but route transfer requires the aircraft systems and CDU to be powered.
3. Retrieve the SimBrief flight. Open the tablet's dispatch or SimBrief area and use its retrieval control. Check that the displayed origin, destination and flight number belong to the intended flight.
4. Send or load the route into the FMC. Some iFly builds provide a direct tablet-to-FMC control. Others stage the flight as a company route or route request that is accepted through the CDU after the origin and destination have been entered.
5. Load fuel and payload separately. Retrieving an OFP does not necessarily place the planned fuel, passengers and cargo aboard. Use the iFly tablet's own apply or loading controls and check that kilograms or pounds match your SimBrief plan.
6. Inspect the RTE and LEGS pages. Confirm the first and last fixes, airway joins, altitude constraints and arrival transition. Select or verify the runway, SID and STAR through DEP/ARR rather than assuming they transferred correctly.
7. Activate and execute the route. Resolve genuine breaks before pressing EXEC, but do not automatically close every discontinuity: a vector leg or an ATC-directed segment may be intentional.
8. Complete performance setup. Enter or verify cruise altitude, cost index, reserves, take-off configuration, centre of gravity, trim and V-speeds before departure.

If the CDU workflow is unfamiliar, follow our Boeing CDU route-and-performance sequence after the SimBrief route has been retrieved.

Should I use the MSFS 2024 EFB or the iFly EFB?

Use the iFly EFB and FMC integration for the aircraft's route, fuel and payload; importing a plan into the MSFS 2024 EFB does not guarantee that the custom iFly FMC will receive it.

If you also want the simulator plan or built-in ATC to follow the same route, use our MSFS 2024 EFB import and transfer procedure. Avoid importing procedures independently into both systems without checking them, as this can produce doubled SIDs, STARs or approach fixes.

What must still be entered manually?

SimBrief supplies dispatch data, but it does not finish the Boeing's pre-flight setup or certify that the route is flyable.

• PERF INIT: Verify zero-fuel weight, reserves, cost index and cruise altitude. Planned block fuel is not the value to enter as reserves.
• Departure and arrival: Confirm the active runway, SID, STAR, transition and approach against the conditions in the simulator.
• Take-off data: Set flaps, thrust reduction or assumed temperature where appropriate, centre of gravity, stabiliser trim and V-speeds using the aircraft's performance tools.
• LEGS review: Check discontinuities, repeated fixes, sharp turns and constraints. An AIRAC mismatch can change or remove waypoints even when the import succeeds.
• Aircraft preparation: Route import does not initialise the IRS, configure the overhead panel, start the engines or arm LNAV and VNAV.

Why is the SimBrief flight plan missing or wrong?

Most iFly SimBrief failures come from an ungenerated plan, the wrong account identifier, a route that was downloaded but not sent to the FMC, or different navdata cycles.

• “Flight not found” or no OFP: Generate the plan again, confirm the Pilot ID or username requested by the tablet, and make sure the aircraft has an internet connection.
• The tablet has the OFP but the FMC is empty: The dispatch has only been retrieved. Use the separate FMC load, send or route-request function and confirm that the CDU is powered.
• The SID, STAR or approach is absent: Select it manually in DEP/ARR. Procedure availability may differ when SimBrief and the aircraft use different AIRAC cycles.
• The route contains a loop or repeated waypoint: A procedure was probably included in the imported route and selected a second time in the CDU. Compare the RTE and LEGS pages with the OFP and remove only the duplicated segment.
• Fuel or payload does not change: Retrieve and physical loading are separate actions. Apply the values through the iFly tablet, then avoid overwriting them with the MSFS weight-and-balance screen.
• The route is correct but LNAV will not engage: Confirm that the route is activated and executed, the active leg is sensible and the aircraft can intercept it. Use our iFly MAX LNAV checks if the mode still refuses to arm or command the route.