Learn to use the FlyByWire A32NX tablet for SimBrief plans, fuel, payload, ground services, performance data and common troubleshooting fixes.
In Microsoft Flight Simulator, use the FlyByWire A32NX tablet, called the flyPad, by switching it on in the cockpit, configuring units and integrations, then opening its pages for flight-plan import, fuel, payload, ground services, checklists and performance calculations. It supports the aircraft workflow but does not replace checking and programming the MCDU.
How do I switch on and set up the A32NX tablet?
Switch on the flyPad with its bezel power control, then configure its settings before loading the aircraft.
- Power on the tablet: press the power control on the flyPad bezel rather than repeatedly clicking the dark display. Allow a few moments for its operating system to load.
- Open Settings: select your preferred units, brightness, sound and loading behaviour. Available options vary slightly between the stable, development and experimental aircraft builds.
- Configure integrations: enter the account identifier requested for SimBrief if you intend to import an operational flight plan. The field may ask for a username or pilot identifier, depending on the installed build.
- Choose one loading method: use the flyPad for A32NX fuel and payload rather than changing the same values simultaneously through the simulator's Weight and Balance panel.
The interface changes as the aircraft develops, but the main functions remain recognisable. Our A32NX package and flyPad feature breakdown covers the tablet's principal aircraft, dispatch, ground and performance tools.
How do I import a SimBrief flight plan into the flyPad?
Configure your SimBrief identifier in the flyPad, generate a fresh operational flight plan, then import it from the Dashboard or Dispatch area.
- Generate the flight: prepare the route and generate its operational flight plan before attempting an import. Editing an ungenerated plan is not enough.
- Check the account identifier: confirm that the flyPad integration field matches the account used to create the plan.
- Import the latest plan: use the import or refresh control on the Dashboard or Dispatch page. Verify the origin, destination, flight number and plan date so that an older flight is not loaded by mistake.
- Apply fuel and payload: open the Ground, Fuel or Payload area and use the imported figures. Depending on your loading settings, the aircraft may update immediately or board passengers, cargo and fuel over time.
- Import into the MCDU: on the MCDU INIT page, use the available INIT REQUEST function to retrieve the route. Inspect every leg rather than assuming the flyPad import has configured the flight-management system.
Importing the OFP into the tablet downloads the briefing data; it does not guarantee that the route, procedures and performance figures have populated the MCDU. A mistake we see constantly is loading one route through the MSFS World Map, another through SimBrief and then trying to diagnose the resulting disagreement. Pick one authoritative plan and verify it in the cockpit.
What can you control from the flyPad?
The flyPad manages A32NX-specific dispatch, loading, ground and performance tasks through several page groups.
| flyPad area | Main use | Common gotcha |
|---|---|---|
| Dashboard or Dispatch | Review the imported flight, operational flight plan and relevant briefing information. | A displayed OFP does not prove that the MCDU route was imported. |
| Ground, Fuel or Payload | Set passengers, cargo, fuel and weight-and-balance targets; request supported ground equipment. | The simulator's Weight and Balance panel or another ground-loading tool can overwrite these values. |
| Performance | Calculate take-off data and, where provided by the installed build, landing performance. | Runway, condition, wind, temperature, pressure and aircraft configuration must be entered correctly. |
| Checklists | Follow the A32NX workflow and mark items complete. | A checklist does not operate switches or confirm that the underlying system is correctly configured. |
| Aircraft Presets | Load broad cockpit states such as Cold and Dark or Turnaround. | A preset can move many switches and undo manual setup already performed. Our worked procedure for Cold and Dark and Turnaround presets explains when to apply them. |
| Settings and Integrations | Configure units, loading behaviour, realism options and supported account connections. | Settings may need checking again after changing aircraft branches or replacing an old installation. |
Ground-service controls depend on the aircraft's state. Doors, chocks, external power and pushback equipment may be unavailable while the aircraft is moving, an engine is running or another service is already active. Simulated boarding and refuelling also take time unless an instant loading option is selected.
Treat performance results as data to verify and enter into the appropriate MCDU PERF page. Never assume V-speeds, flap configuration or thrust settings were transferred merely because the flyPad completed a calculation.
Does the A32NX tablet program the MCDU?
No, the flyPad assists with planning and data entry, while the MCDU remains the interface for the aircraft's flight-management and guidance system.
After importing a plan or completing the load, check at least the following in the MCDU:
- origin, destination and alternate;
- route legs, discontinuities and duplicate waypoints;
- departure runway, SID, arrival, STAR and approach;
- cost index and cruise level;
- zero-fuel weight, centre of gravity and block fuel;
- take-off configuration, thrust setting and V-speeds.
If the flyPad shows the correct flight but the MCDU is empty, the tablet import succeeded and the MCDU request did not. Recheck the integration identifier, confirm that a generated plan exists, then repeat the INIT request.
Is the flyPad the same as the MSFS 2024 EFB?
No, the A32NX flyPad is an aircraft-specific tablet, while Microsoft Flight Simulator 2024 also has a simulator-wide EFB.
A route loaded into one does not necessarily appear in the other or in the MCDU. Use the flyPad for A32NX loading, aircraft states and performance work; use the universal EFB for simulator-level planning functions. Our comparison of the MSFS 2024 EFB and aircraft-specific tablets explains how their roles and route handling differ.
Why is the A32NX tablet black or not responding?
A black or unresponsive flyPad is usually powered off, blocked by cockpit interaction, affected by a stale installation or waiting on an integration that has not returned data.
- Black screen: use the bezel power control and wait for the boot sequence. Clicking the centre of an unpowered display does nothing.
- Visible but unclickable: return focus to the cockpit, close any overlapping toolbar window and test the alternative cockpit interaction mode. The same input and focus checks are covered in our tablet input and route-transfer troubleshooting steps.
- Pages missing or behaving strangely: remove duplicate or obsolete A32NX folders and keep only one aircraft build in the Community folder. Restart the simulator after replacing the package.
- SimBrief import returns no flight: generate the plan again, verify the account identifier and confirm that the tablet has online access. An old imported flight usually means the newest plan was not generated.
- Fuel or payload does not change: check whether timed loading is enabled, keep the aircraft stationary and avoid altering fuel or weight through a second interface.
- Route absent from the MCDU: use the MCDU's INIT request and inspect the flight-plan pages. Importing an OFP into the flyPad alone is not an MCDU route transfer.