Fix a FlyByWire A32NX overhead panel that will not respond in MSFS. Check EXT PWR, mouse input, controller bindings and duplicate installs.
The FlyByWire A32NX overhead panel in Microsoft Flight Simulator usually fails for one of four reasons: the aircraft is unpowered, MSFS is not accepting cockpit mouse input, a controller binding is overriding the switches, or the A32NX package is duplicated or damaged. Start on a runway, then isolate power, input and installation in that order.
Match what appears on the MSFS overhead panel to the fault
The failure pattern usually identifies the cause faster than reinstalling the aircraft.
| What appears | Probable cause | First action |
|---|---|---|
| The panel cannot be found in a menu | It is part of the 3D cockpit, not a separate toolbar panel | Use a cockpit camera view and look above the pilots |
| Controls do not highlight or react | Mouse profile, interaction mode or menu input focus | Resume the flight, reset the mouse profile and test another interaction mode |
| A switch moves and immediately returns | A controller or assistance feature is overriding it | Disconnect external controllers |
| Switches move, but annunciators and displays remain dark | No aircraft electrical power | Start on a runway or connect external power |
EXT PWR shows AVAIL | Ground power is ready but not connected to the aircraft | Press the EXT PWR pushbutton once |
| Status lights work, but panel lettering is dark | Overhead integral or flood lighting is turned down | Increase the overhead lighting |
| The flyPad and several other A32NX systems also fail | Incomplete, misplaced or duplicate aircraft package | Test one clean A32NX installation |
| Only one guarded switch has no effect | Closed guard, unmet system condition or an unimplemented function | Check the guard and system prerequisites before reinstalling |
How do I fix the A32NX overhead panel?
The most reliable sequence is to prove that the aircraft works when powered, then remove input conflicts before touching its installation.
- Confirm that this is the FlyByWire aircraft. Check the aircraft name on the selection screen rather than relying on the livery. The stock A320neo and other Airbus add-ons have different systems even though their overhead panels look similar. Community-folder repairs in this article apply to PC installations.
- Load a powered runway state. Select a runway departure and confirm that the engines are already running. Try several overhead pushbuttons. If they work here but not at a parking stand, the package is functioning and the problem is the cold-and-dark power sequence.
- Supply electrical power at the stand. Turn on both batteries. Connect a ground-power unit from the flyPad’s ground-services controls, wait for
EXT PWRto showAVAIL, then press it so that it indicatesON. Starting the APU is the alternative when external power is unavailable. - Restore cockpit mouse input. Close any open menu or text field, resume the flight and click inside the cockpit. In MSFS 2020, test both Legacy and Lock under the Cockpit Interaction System setting. In the controls settings, return the mouse to its default profile or create a fresh profile if reset will not work.
- Disconnect conflicting hardware. Unplug the yoke, throttle, gamepad and switch panels, leaving only the mouse and keyboard. Temporarily turn off piloting assistance. If the overhead now works, reconnect devices individually and remove assignments for battery, avionics, generator, alternator or APU controls that continually send an on/off state.
- Run a clean add-on test. Fully quit MSFS, then disable or move every Community add-on except one complete A32NX package. Restart the simulator rather than merely returning to the main menu. If this fixes the panel, restore liveries and other add-ons in small groups until the conflict returns.
- Clean-install only after those tests. Remove every old A32NX copy and install one release channel without merging it into existing files. For MSFS 2020, follow our clean A32NX installation and Community-folder checks. MSFS 2024 users should follow the MSFS 2024-specific package and path instructions instead of reusing an assumed MSFS 2020 location.
How should EXT PWR work on the A32NX?
AVAIL means that an external electrical source is available; it does not mean that the aircraft is using it.
With the batteries on, connect ground power through the flyPad and watch the overhead EXT PWR pushbutton. Press it once after AVAIL appears. The indication should change to ON, and the aircraft’s electrical buses and displays should begin receiving power.
- If
AVAILnever appears, the ground-power unit has not been connected or is unavailable at that position. Use the APU or perform the runway test. - If
AVAILappears but clicking does nothing, treat it as a mouse-input problem. - If it changes to
ONbut only the displays remain black, check each display’s brightness control. - If the status lights work but the overhead labels remain dark, turn up the separate integral or flood lighting.
The overhead annunciator-light test is another useful distinction. If the annunciators illuminate during the test, the panel has power; a dark label or an inactive system is then more likely to be a lighting or aircraft-state issue.
Why do switches move, snap back or refuse to reset?
A switch that moves and immediately returns is usually receiving a second command from connected hardware or an assistance feature.
Physical switch panels often transmit a continuous SET command. An on-screen click therefore lasts only until the hardware sends its state again. Generic avionics-master, alternator and generator assignments can also conflict with the A32NX’s Airbus-specific electrical logic. Physically disconnecting controllers is a better test than merely changing profiles.
Not every Airbus pushbutton visibly latches, and a FAULT indication may remain until the underlying system condition is corrected. If just one control will not reset, open any guard, check the relevant power or pneumatic source and judge the result by the annunciation rather than button movement alone.
I don’t have that option in my menu
Menu names and available settings differ between MSFS 2020, MSFS 2024, localised interfaces and console editions.
In MSFS 2020, Cockpit Interaction System is found in the general accessibility options, while mouse assignments and profiles are in the controls settings. If your menu does not use those words, search the settings for interaction or reset the mouse from its device profile instead. Return to the live cockpit before testing because a menu can retain input focus.
The A32NX overhead itself does not open from the simulator toolbar. It is mounted above the crew in the virtual cockpit; use mouse look or a cockpit camera preset to bring it into view.
PC Community-folder instructions do not apply to Xbox or PlayStation 5, which do not expose a PC-style Community folder. If a similar Airbus appears on a console, confirm its exact aircraft and developer name before following FlyByWire-specific steps.
The reset didn’t do anything — what do I do?
If a profile reset made no difference and nothing is working, perform one controlled isolation test rather than changing several settings at once.
- Quit MSFS completely. A flight restart alone does not reload every aircraft package or release a stuck hardware input.
- Disconnect all external controllers. Start with only the default mouse and keyboard profiles.
- Remove other Community packages. Keep one clean A32NX installation and no legacy liveries or aircraft-system modifications.
- Start the A32NX on a runway. Confirm that the engines and cockpit displays are powered before testing the overhead.
- Compare another aircraft. If no cockpit in MSFS accepts clicks, the fault is global mouse input or interaction settings. If other aircraft work but the powered A32NX does not, its package is the likely cause.
A common installation mistake we see is an A32NX package placed inside an extra folder. The active package root should directly contain its package manifest and layout files, not another identically named folder. Duplicate release channels, an installer aimed at the wrong Community path and restricted folder permissions produce similar symptoms; our installer path, nested-folder and permissions checks cover those faults.
If the overhead works but only the flyPad remains blank or unresponsive, do not keep reinstalling the whole aircraft. Use the separate flyPad power, focus and package-conflict diagnosis instead.