Skip to content
Microsoft Flight Simulator 9 min read 365 views

Why is the FlyByWire flyPad not working in MSFS?

Ian Stephens
In short

FlyByWire flyPad not working in MSFS? Fix a missing, blank, frozen or unclickable EFB with mouse, Installer and clean-package checks.

The flyPad is the cockpit EFB — the “iPad” — fitted only to the FlyByWire A32NX in Microsoft Flight Simulator. If it is absent, confirm the aircraft and installation; if blank, test aircraft power; if frozen, test the package; if visible but unclickable, fix mouse focus or the Cockpit Interaction System.

What does each flyPad symptom tell you?

The symptom identifies which part of the aircraft is working and prevents an unnecessary reinstall.

What you seeWhat it usually provesNext action
The iPad is not thereThe wrong Airbus is loaded, the camera is not looking towards it, or A32NX did not loadSelect the official FlyByWire A32NX and check the installation target
The flyPad is present but blankThe aircraft may be unpowered; if other displays work, the flyPad application has failedTry an engines-running start, then update and isolate the package
It is stuck on loadingThe tablet model loaded but its application did not finish startingCheck for stale, incomplete, duplicate or conflicting files
The screen works but has no clickable controlsThe local flyPad loaded, but mouse focus or cockpit interaction is failingUse a physical mouse and test the simulator interaction setting
Only charts, imports or another online page failsThe local flyPad works; its account or network integration does notReconnect or reauthorise that service rather than reinstalling A32NX

Where is “the iPad” in game?

If you mean in game, the flyPad is mounted beside the cockpit side window in the FlyByWire A32NX. Pan towards the captain’s left window or the first officer’s right window; a narrow field of view or custom camera can leave it outside the initial view.

It is not part of the stock Airbus A320neo, the A320neo V2 or another developer’s Airbus. If someone says “não aparece”, “yok burda” or “netu takogo” — it does not appear or is not there — the first check is the aircraft name in the selection screen. A livery assigned to a different A320 base model does not turn that aircraft into the FlyByWire A32NX.

If the FlyByWire aircraft itself is missing from the aircraft selector, this is an installation-path problem rather than a tablet problem. If the correct A32NX loads but the flyPad body is absent, continue with the clean-package test below. For its normal location and local functions, see our guide to using the A32NX flyPad in the cockpit.

“It is blank”: is the A32NX powered?

A blank flyPad should first be tested in an engines-running flight, not diagnosed as a discharged virtual tablet. FlyByWire branches can change tablet behaviour, so battery or bezel assumptions are not a reliable starting point.

  • All cockpit displays are dark: load from a runway or choose an engines-running state. If the flyPad then starts, the installation works and the original issue was the aircraft’s cold-and-dark state or start-up procedure.
  • Other cockpit displays work but the flyPad remains black: the aircraft has electrical power, so update A32NX and test without other Community packages.
  • The screen briefly appears and then goes black: restart the flight once. If it repeats with an updated, isolated installation, perform the clean reinstall below.

Do not reinstall Microsoft Flight Simulator merely because an unpowered cold-and-dark aircraft has dark displays.

Why is the flyPad visible but not clickable?

A rendered flyPad that ignores clicks has already loaded enough of the aircraft to display its interface, making an input or focus fault more likely than missing aircraft files.

  1. Use a physical mouse. Disconnect controller input temporarily and test the screen with the left mouse button. This separates flyPad behaviour from gamepad, VR-pointer and custom controller profiles.
  2. Restore cockpit focus. Close toolbar panels and pop-outs, press Escape if a window has captured input, return to the cockpit and click an empty cockpit area before trying the flyPad again.
  3. Change the Cockpit Interaction System. In MSFS 2024, use Settings > General > Accessibility > Cockpit Interaction System. In MSFS 2020, use Options > General Options > Accessibility > Cockpit Interaction System. Test Legacy interaction if the present mode does not register mouse clicks.
  4. Check the mouse profile. In MSFS 2024, open Settings > Controls > Mouse. In MSFS 2020, open Options > Controls Options > Mouse. Test a default mouse profile if a custom profile has removed or continuously captured cockpit interactions.
  5. Try another cockpit display. If the MCDU and other interactive displays also ignore the mouse, fix the simulator’s focus or control profile. Reinstalling only A32NX will not correct a simulator-wide input problem.

“It is stuck on loading”: what should I do?

A flyPad stuck on its logo or loading screen proves that the tablet model loaded, but not that all of its application files started correctly. Readers often describe this simply as “it stuck on loading”; waiting indefinitely rarely changes the result.

Close Microsoft Flight Simulator fully, update A32NX through the FlyByWire Installer and relaunch the simulator. Returning to the main menu is not the same test because aircraft code can remain loaded for the session.

If updating does not help, look for an old manual installation, a second A32NX folder or another add-on interfering with the aircraft. Do not merge fresh files into an existing package directory, and do not keep several branches or copied installations active at once.

How should I install the A32NX in MSFS 2024?

On Windows PC, install and update the A32NX with the FlyByWire Installer, selecting the correct simulator before installing the aircraft.

  • For MSFS 2024: choose Microsoft Flight Simulator 2024 in the Installer’s simulator selector, open its Settings and confirm that the installation path is the active MSFS 2024 Community folder. Then use Install or Update for A32NX.
  • For MSFS 2020: select Microsoft Flight Simulator 2020 and verify its separate installation path. Do not copy a package from the 2020 Community folder into the 2024 folder.
  • For a custom content location: trust the path configured for the selected simulator rather than assuming a default Microsoft Store or Steam directory. Cleaning an unused Community folder changes nothing.

If the Installer reports an invalid path, incomplete download or failed update, follow our FlyByWire Installer path and download checks before changing aircraft files manually.

Does the flyPad work on Xbox or PlayStation?

The FlyByWire Installer and its A32NX package are supported on Windows PC, not on Xbox Series X|S, PlayStation 5 or PS5 Pro. MSFS 2024 is available on those consoles, but they cannot run the PC Installer or accept a PC package copied into a Community folder. A tablet in a console Airbus is therefore not necessarily the FlyByWire flyPad.

“Nothing working / rien ne fonctionne / no funciona”: run this clean test

If every quick check still ends in “nope”, use this sequence without skipping steps. Each result narrows the fault before files are removed.

  1. Load the official aircraft. In the aircraft selector, choose the FlyByWire A32NX itself, not the stock A320neo, A320neo V2 or a livery tied to another base aircraft. If A32NX is not listed, correct the Installer’s simulator and package path first.
  2. Start with engines running. Load from a runway or select an engines-running state. If the flyPad now works, the package is sound; troubleshoot the cold-and-dark start rather than reinstalling it.
  3. Use a physical mouse. Test the flyPad and another cockpit display with a default mouse profile. If neither accepts clicks, correct the simulator interaction setting or focus.
  4. Isolate the active Community folder. Close MSFS completely. Move every other third-party package outside the active Community folder, leaving only the Installer-managed A32NX files. Renaming add-ons while leaving them in that folder is not a clean test. If the flyPad works now, restore packages in small groups until the conflict returns.
  5. Update through the Installer. Select the correct simulator in the FlyByWire Installer and update A32NX. Stable is the clearest diagnostic branch unless the fault is known to affect that branch. Start MSFS again only after the update completes.
  6. Perform a genuinely clean reinstall. Uninstall A32NX through the Installer, then inspect the active Community folder and remove any remaining old or manually copied A32NX directories. Install one fresh copy through the Installer. Do not merge it with old files or place it inside an extra nested folder.

A duplicate or nested package can stop much more than the flyPad. If the aircraft hangs, returns to the menu or is missing altogether, use our A32NX aircraft-loading and duplicate-folder checks.

Why can I not disconnect, import a plan or load charts?

SimBridge, chart accounts, flight-plan imports and network services are separate from the local flyPad interface. If the home screen, settings and aircraft controls work, one failed online feature is not an A32NX tablet failure.

  • SimBridge: quit the companion application completely, start it again and then reopen the relevant flyPad page. Closing a page inside the tablet does not itself stop the separate desktop process.
  • Charts or account authorisation: use the integration’s sign-out or unlink control where it is offered, then authorise it again and complete any browser approval. A wrong account, expired authorisation or blocked approval window can leave that page disconnected while the rest of the flyPad remains usable.
  • Flight-plan import: verify that the saved pilot ID or username belongs to the account containing the generated plan. An import returning no plan does not mean the local EFB failed to load.
  • Cannot disconnect: remove the saved account or integration entry where the flyPad provides that control, restart the flight and reconnect. If only that service remains stuck, troubleshoot its authorisation or network session rather than reinstalling the aircraft.

Should I reinstall Microsoft Flight Simulator?

A complete simulator reinstall is rarely justified for a FlyByWire-only flyPad fault. Reinstall A32NX when the correct aircraft still has a missing, black or permanently frozen tablet after an engines-running start, an isolated Community-folder test and an Installer update.

Do not reinstall the simulator when changing the power state fixes the screen, every aircraft has unclickable cockpit controls, or only one chart, account or import service fails. Those results point to aircraft operation, simulator input or an online integration respectively.

AI Assistant New

Still stuck? Ask Fly Away

Ask Fly Away is our AI flight-sim assistant. Ask your exact question and get a direct, step-by-step answer in seconds — free to try.

Ask Fly Away Free preview · unlimited for PRO members