How do I set up a FlyByWire SimBrief airframe in MSFS?

In Microsoft Flight Simulator, create a separate SimBrief My Fleet airframe from the FlyByWire-supplied profile for the A32NX or A380X, save it, and select that airframe before generating the operational flight plan (OFP). Avoid generic A20N or A388 profiles because their weights, capacity and fuel-burn assumptions may differ from FlyByWire’s model.

A SimBrief airframe is a saved set of aircraft performance and loading data. It is separate from the SimBrief account identity entered in the aircraft’s EFB: the account finds your latest OFP, while the selected airframe determines how that OFP was calculated.

Set up the airframe in SimBrief

The safest method is to import the profile supplied for the exact FlyByWire aircraft rather than building one from a blank generic airframe.

1. Open the supplied SimBrief profile. Use the airframe import provided with the FlyByWire aircraft documentation, sign in to SimBrief, and choose the option to add or save it to My Fleet.
2. Verify the aircraft type. The A32NX must show A20N; the A380X must show A388. The profile name should clearly identify FlyByWire rather than another developer or a generic aircraft.
3. Give it an unmistakable name. Names such as FBW A32NX and FBW A380X prevent the common mistake of selecting an old generic profile. You may also enter the registration used by your preferred livery.
4. Keep the supplied performance figures. Do not casually change operating weight, maximum weights, passenger capacity, fuel capacity, fuel factor or climb, cruise and descent data.
5. Save and select the airframe. Return to the dispatch form, choose this saved airframe, complete the flight and generate the OFP. Changing the selection afterwards does not recalculate an existing plan; generate it again.

For the surrounding dispatch process, our SimBrief OFP workflow for Microsoft Flight Simulator covers aircraft selection, route generation and importing the finished plan.

Which FlyByWire profile should I use?

Use the dedicated A32NX profile for the A32NX and the dedicated A380X profile for the A380X; the two airframes are not interchangeable.

The ICAO code alone is not enough. Two profiles can share the same code while using different empty weights, payload limits and fuel factors.

What can I safely customise?

Identity fields are generally safe to customise, while performance and structural fields should remain at FlyByWire’s supplied values.

• Safe changes: airframe name, registration, operator identity and other descriptive fields.
• Change only for a modelled configuration: passenger count, cabin layout or operating weight. A livery showing a different airline does not by itself justify different performance data.
• Leave alone unless instructed: maximum take-off, landing and zero-fuel weights; maximum fuel; cargo limits; fuel factor; and climb, cruise or descent profiles.

Do imported airframes update automatically?

Do not assume that a saved copy will inherit later profile revisions. If FlyByWire supplies revised airframe data, import it again, label the new copy clearly and use that profile for newly generated OFPs.

How do I use the saved airframe in the aircraft?

The saved airframe is used in SimBrief before the flight; nothing needs to be copied into the MSFS Community folder.

Select the airframe, generate the OFP, then configure the flyPad or A380X EFB with your SimBrief account identity and request the latest flight. Our FlyByWire account-linking and OFP-import procedure explains that connection.

Importing the route does not always load passengers, cargo and fuel automatically. Those are separate EFB actions; the flyPad flight-data and loading workflow shows where they fit into the cockpit setup.

Why do the imported fuel or weights not match?

Most mismatches come from selecting the wrong airframe, importing an older OFP or comparing different types of weight and fuel figures.

• Wrong saved profile: confirm that the dispatch form shows your FlyByWire airframe, not merely A20N or A388.
• OFP generated too early: selecting a new airframe does not alter an already generated plan. Regenerate the flight.
• Wrong SimBrief account: the EFB imports the latest OFP belonging to the configured Pilot ID or account, regardless of which browser account is open elsewhere.
• Route imported without loading: use the EFB’s separate payload and fuel actions after retrieving the flight.
• Unlike figures compared: compare zero-fuel weight with zero-fuel weight and block fuel with loaded fuel. Trip fuel is only one part of block fuel.
• Units or cabin settings differ: check kilograms versus pounds, passenger weights and the selected cabin configuration before changing the airframe itself.