Fix a FlyByWire A320neo that will not move in MSFS by checking chocks, parking brakes, brake axes, engine thrust and pushback conflicts.
The FlyByWire A320neo usually will not move in Microsoft Flight Simulator because its parking brake or wheel chocks are still set, a toe-brake axis is continuously applied, pushback is waiting for brake release, or the engines are not producing thrust. Check the flyPad ground equipment, brake inputs and engine N1 before reinstalling the A32NX.
FlyByWire calls its aircraft the A32NX. Confirm that this is the aircraft selected on the world map rather than the stock A320neo, because their systems and electronic flight bags are different.
What should I check first?
Release every physical and simulated restraint before adding thrust.
- Exit Active Pause. Active Pause can freeze the aircraft while its engines and cockpit continue operating. Make sure the simulation itself is running, not merely the aircraft systems.
- Remove the wheel chocks. Open the flyPad ground or ground-services page and remove the chocks if they are shown as fitted. Do not try to overcome them with extra thrust.
- Release the parking brake. Move the cockpit handle to OFF and confirm the parking-brake indication clears. If it was operated through a keyboard or controller toggle, set it ON and then OFF once to synchronise the binding.
- Check the tug. Complete or cancel pushback and wait until the tug has fully disconnected before attempting to taxi.
- Verify the engines. The engine display should show stable idle and respond with increasing N1 when thrust is applied. If the aircraft was started cold and dark, follow our A32NX electrical, fuel, pneumatic and engine-start sequence.
- Apply modest breakaway thrust. A loaded A320neo may need slightly more than idle thrust to begin rolling. Increase thrust gradually while watching N1; never hold high power against an aircraft that may still be restrained.
Is the problem braking or engine thrust?
The N1 indication separates a braking problem from a throttle or engine problem.
| What you observe | Most likely cause | Next check |
|---|---|---|
| N1 increases, but the aircraft remains fixed | Chocks, parking brake, toe brakes or Active Pause | Inspect ground equipment and every brake binding |
| N1 remains at idle when the throttle moves | Throttle assignment, calibration or incomplete engine start | Check engine availability and throttle input |
| The aircraft moves after pedals or another controller are disconnected | Reversed or duplicated brake axis | Correct that device’s brake assignments |
| The tug connects but does not move | Pushback sequence or conflicting pushback systems | Follow the tug prompt and use only one provider |
| The aircraft rolls but will not turn | Nosewheel steering disconnect or tiller setup | Finish pushback and inspect steering controls |
If N1 rises but the aircraft stays still
A brake input is often being applied without an obvious cockpit warning. Open the Microsoft Flight Simulator control settings for every connected device and search for brake assignments. Rudder pedals, throttles, gamepads and joysticks can all carry duplicate bindings.
Move each toe brake and watch its input indicator. A reversed axis can register full braking when the pedal is released; change the inversion setting only if the displayed response proves it is backwards. Clear duplicate brake-axis and parking-brake assignments, add a small dead zone if the input flickers, and temporarily disable assisted braking or AI taxi controls while testing.
Do not recalibrate the throttle when N1 already rises normally. Throttle calibration cannot release chocks or brakes, and the aircraft may lurch forward when the actual restraint is removed.
If N1 does not rise above idle
If N1 does not respond, check engine state and throttle control rather than the wheels. Confirm the engines have completed their start and show the expected available indication, then compare the physical throttle with the cockpit thrust levers.
Remove conflicting throttle assignments and use the A32NX flyPad calibration only when the physical lever positions do not match the simulated detents. If the levers move but an engine has not reached stable idle, return to the start procedure instead of adding more throttle.
Why won’t pushback move the A32NX?
A connected tug normally fails to move because the chocks remain fitted, the brake was not released when requested, or two pushback systems are trying to control the aircraft.
Remove the chocks before requesting service. Keep the parking brake set while the tug attaches, then release it only when the pushback prompt tells you to do so. Our built-in Ground Services pushback sequence covers the normal order.
If GSX is installed, do not start native pushback at the same time. A GSX message that remains stuck while the tug is attached usually points back to the parking brake, chocks or a continuously applied brake axis; use these specific GSX brake and tug checks before restarting the flight.
Why does the A320neo move but not steer?
If the aircraft rolls but will not turn, the problem is nosewheel steering rather than brakes or thrust. After pushback, wait for the tug and steering bypass pin to be removed; the NW STRG DISC indication should clear.
If it remains disconnected, finish or cancel the active pushback service. Otherwise, inspect the tiller and rudder-to-tiller configuration in the A32NX controls, checking again for duplicated or permanently deflected axes.
When should I reinstall the A32NX?
Reinstall only when aircraft systems are also missing, unresponsive or loading incorrectly. A normal engine response combined with a stationary aircraft is almost always a restraint or controller problem, not damaged add-on files.
If the flyPad or overhead panel is dead, confirm that the FlyByWire A32NX was selected, update or reinstall it into the package location used by the simulator, and remove any duplicate old A32NX copy. Temporarily disable unrelated aircraft modifications rather than deleting the entire Community folder; our diagnostic steps for an unresponsive A32NX overhead panel cover the electrical, controller and installation checks.