Use SimBrief with the Fenix A320 in MSFS 2024: link your Pilot ID, import the route, load fuel and payload, and fix common MCDU errors.
To use SimBrief with the Fenix A320 in MSFS 2024, generate an OFP for the correct Fenix airframe, enter your SimBrief Pilot ID in the Fenix EFB, import the plan, then use INIT REQUEST in the MCDU. Verify the route, load fuel and payload, and enter performance data before departure.
This procedure is for the PC version of Microsoft Flight Simulator 2024. The Fenix A320 relies on its companion software and is not a console aircraft.
How do I import a SimBrief plan into the Fenix A320?
The dependable method is to connect SimBrief to the Fenix EFB first, then request the generated flight through the aircraft's MCDU.
- Build and generate the flight in SimBrief. Select the correct Fenix A320 airframe and engine variant, then confirm the departure, destination, alternate, cruise level, payload and planned fuel. You must generate the operational flight plan; merely editing or saving a draft will not make it available to the aircraft. Our complete SimBrief planning workflow for MSFS explains the planning stage in more detail.
- Find your SimBrief Pilot ID. This is the account identifier used by aircraft integrations. If the Fenix field specifically requests a Pilot ID, enter the numeric ID rather than your display name or email address.
- Connect the Fenix EFB. Open the tablet's settings or account-integration area, enter the SimBrief identifier and use its import or synchronisation control. Menu wording can change between Fenix builds, but the imported plan should show the correct callsign, origin, destination and aircraft.
- Import payload and fuel. Open the Fenix mass-and-balance and fuelling pages, check the imported passenger, cargo and block-fuel figures, then command the aircraft to load them. Importing an OFP does not necessarily place the planned mass or fuel physically aboard the aircraft.
- Request the route through the MCDU. With the aircraft powered and the Fenix companion application running, open the MCDU's
INIT Apage and pressINIT REQUEST. Allow the uplink to finish. If the software presents a received AOC message or asks for confirmation, review and insert it. - Review the flight plan. Open the
F-PLNpage and work through every leg. Select or confirm the departure runway, SID, arrival, STAR and approach against the expected clearance and weather rather than accepting them blindly. - Complete the FMGS setup. Check the cost index and cruise level, enter or confirm ZFW, ZFWCG and block fuel, request wind data where supported, and calculate take-off performance in the Fenix EFB. Enter or transfer the resulting V-speeds, flap setting and thrust data to the
PERF TOpage.
What does SimBrief import into the Fenix A320?
SimBrief supplies planning data, but it does not finish every part of the Fenix A320 setup.
| Item | What to expect |
|---|---|
| Route and cruise data | Imported through the MCDU request, but every waypoint and airway still needs checking. |
| SID, STAR and approach | They may be imported, omitted or differ from the clearance. Select the applicable procedures in the MCDU. |
| Payload and block fuel | The EFB can read the planned values, but you must command loading and refuelling. |
| Forecast winds | These may require a separate wind request after the route has loaded. |
| Take-off performance | Calculate it in the Fenix EFB using the actual runway, weather, mass and configuration. SimBrief planning figures are not a substitute. |
| MSFS 2024 ATC route | The Fenix MCDU uplink does not guarantee that the simulator's EFB or built-in ATC has received the same plan. |
Why is INIT REQUEST missing or not working?
INIT REQUEST usually fails because the wrong account identifier is stored, no new OFP has been generated, or the aircraft cannot reach the SimBrief service.
- Confirm the account: remove spaces and check that the Pilot ID belongs to the account that generated the flight.
- Generate a fresh OFP: the integration normally retrieves the latest generated plan, not unsaved edits or an older flight selected elsewhere.
- Check aircraft power: the MCDU and FMGC must be powered, and the Fenix companion application must be open and signed in.
- Use the correct page: look for the request on
INIT Aduring pre-flight. Do not repeatedly press it while an uplink is still in progress. - Remove an old flight: a route already active in the FMGS can interfere with a new request. Start from a clean pre-flight state rather than replacing the route during an active flight.
If those checks do not restore the request, follow our Fenix INIT REQUEST troubleshooting checks.
A route that imports but contains missing waypoints, rejected airways or unavailable procedures usually points to a navigation-data mismatch. The SimBrief plan and aircraft should use compatible cycles; see our guidance on matching the Fenix and SimBrief AIRAC cycles.
Do I also need to import SimBrief into the MSFS 2024 EFB?
Only import the plan separately into the MSFS 2024 EFB if you want the simulator's flight-planning functions or built-in ATC to know about it.
The MSFS EFB and Fenix FMGS are separate systems, so loading one does not prove that the other contains the same route. Follow the separate MSFS 2024 EFB import process, then compare the origin, destination and first few route legs before starting the flight.
Pre-pushback checks
Before pushback, compare the MCDU route, EFB loadsheet and generated OFP rather than assuming the uplink filled everything correctly.
- Confirm the departure and arrival runways, procedures and transitions.
- Inspect every flight-plan discontinuity. Some are mistakes, while one associated with radar vectors or a manual leg may be intentional.
- Check ZFW, ZFWCG, block fuel, reserve fuel, cost index and cruise level.
- Verify that the aircraft has finished loading passengers, cargo and fuel.
- Enter take-off speeds, flap configuration, trim and thrust data from the Fenix performance calculation.
- If using built-in ATC, confirm that its route agrees with the active MCDU flight plan.