Learn to use the FlyByWire A32NX flyPad EFB in MSFS for flight imports, fuel, payload, ground services, performance and common fixes.
To use the FlyByWire A32NX flyPad EFB in Microsoft Flight Simulator, power on the tablet, import or enter your flight data, then use its payload, fuel, ground, performance, chart and checklist tools. The flyPad prepares and services the aircraft, but it does not replace programming the MCDU or operating the overhead panel.
What should I set up before using the flyPad?
The flyPad appears only in the FlyByWire A32NX; it is not the tablet in the stock A320neo or the native MSFS 2024 EFB. If it is missing, follow our PC installation procedure for MSFS 2020 or the corresponding A32NX package instructions for MSFS 2024.
After loading the cockpit, operate the tablet's power control and open Settings. Choose your units, boarding and refuelling speeds, aircraft options and any flight-planning integrations. Exact tab names can change between A32NX builds, but the underlying workflow remains the same.
If you want a repeatable starting configuration, use the aircraft-presets area. Our explanation of loading Cold and Dark or Turnaround with the flyPad covers the difference between those states.
A practical gate-to-pushback flyPad workflow
The simplest method is to treat the flyPad as the control centre for dispatch and ground preparation, while using the cockpit controls for the actual aircraft systems.
- Power the tablet and select an aircraft state. A cold cockpit still needs its normal battery or external-power procedure before the aircraft systems will operate, even if the tablet itself has booted.
- Import or enter the flight. If using SimBrief, enter the account name or Pilot ID accepted by your installed build, generate an operational flight plan, then use the import control on the dashboard or dispatch page. Regenerate and re-import after changing the route, runway, payload or fuel.
- Load passengers and cargo. Open the payload page, enter the passenger and cargo figures, then start boarding. Choose instant loading for testing and a timed rate when simulating a normal turnaround. Wait for boarding to finish before relying on the final weight and centre-of-gravity figures.
- Load the planned fuel. Set the block-fuel target and begin refuelling. Avoid changing fuel or payload afterwards through the MSFS weight-and-balance panel, because the two systems can overwrite one another and leave the EFB, ECAM and MCDU showing different figures.
- Prepare ground equipment. Use the Ground page for chocks, doors, external power and available services. Connecting the GPU only makes external power available; you must still select
EXT PWRon the overhead panel. - Program and verify the MCDU. Use
INIT REQUESTwhere available or enter the route manually. Check the departure, arrival, discontinuities, fuel, zero-fuel weight and centre of gravity rather than assuming the EFB has inserted everything. - Calculate performance last. Enter the actual runway, weather, aircraft weight, configuration and anti-ice choices in the performance tool. Transfer or manually enter the resulting V-speeds, FLEX temperature and trim data as supported by the installed build. Recalculate after a runway, weather or weight change.
- Finish the checklist and pushback setup. Close the doors, remove ground equipment and connect the tug from the Ground page where that control is provided. Release the parking brake only when prompted, then stop and disconnect the tug before taxiing.
Does the flyPad program the MCDU automatically?
No. Importing a flight into the flyPad does not guarantee that the same route is active and valid in the MCDU.
| Task | What the flyPad does | What you must still do |
|---|---|---|
| Flight plan | Reads and displays imported dispatch data | Request or enter the route in the MCDU and inspect every leg |
| Fuel and payload | Loads targets and calculates aircraft weights | Verify the values on the ECAM and MCDU |
| Ground services | Commands doors and available equipment | Operate overhead switches, brakes and engine controls |
| Performance | Calculates take-off data from the supplied conditions | Check and insert the figures required by the MCDU |
| Checklists | Tracks checklist items | Perform and confirm the actual cockpit actions |
A common mistake is loading one route from the MSFS World Map and a different route from SimBrief. Use one as the master source, or ensure both plans match, then inspect the MCDU flight-plan page for duplicate waypoints and unresolved discontinuities.
Can I use the A32NX flyPad without SimBrief or Navigraph?
Yes. SimBrief and Navigraph are optional integrations, not requirements for operating the flyPad or flying the A32NX.
You can enter payload, fuel, airports and performance inputs manually. Navigraph adds integrated chart access; if you use it, our A32NX account and chart-connection steps explain the authorisation process.
Why is the A32NX flyPad EFB not working?
Most flyPad faults come from loading the wrong aircraft, retaining two A32NX installations or expecting an imported plan to control systems that still require cockpit input.
- The flyPad is completely absent: confirm that the aircraft selector shows the FlyByWire A32NX rather than the default Airbus. A mistake we see constantly is an old manually installed A32NX folder left beside the installer-managed package.
- The screen is black: try the tablet power control and brightness setting. If the other cockpit displays are also dark, establish battery or external power and check that the aircraft has not loaded in an unintended state.
- SimBrief import fails: generate a flight plan first, check the saved username or numeric Pilot ID, confirm the simulator has an internet connection, then import again. A World Map route is not a substitute for a generated SimBrief plan.
- Fuel or payload does not change: start the boarding or refuelling process rather than only entering a target. Keep the aircraft stationary and avoid making competing changes through the MSFS toolbar.
- Ground-service controls are unavailable: ensure the aircraft is on the ground and stopped. Individual services may also require the engines off, parking brake set or the appropriate door open.
- The EFB freezes after an update: fully close Microsoft Flight Simulator, remove the obsolete A32NX copy and let the installer repair or reinstall the selected build. Do not merge a new package over files from an older build.