Why won't my aircraft move in Microsoft Flight Simulator?
Fix an aircraft that won’t move in Microsoft Flight Simulator 2020 or 2024: check brakes, chocks, engine thrust, pushback and control bindings.
An aircraft that will not move in Microsoft Flight Simulator 2020 or 2024 is usually being held by the parking brake, wheel chocks, a brake-axis binding or an active pushback state. If the engine is running, confirm thrust rises, release every restraint, then check for unwanted controller inputs.
Which fault is stopping the aircraft?
The aircraft’s response to throttle is the quickest way to separate an engine problem from a brake or ground-state problem.
| What you see | Most likely cause | What to check |
|---|---|---|
| Throttle moves, but RPM or N1 does not rise | Engine or throttle-control problem | Engine state, fuel controls and throttle bindings |
| RPM or N1 rises, but the aircraft remains fixed | Parking brake, chocks, tie-downs, tug or pause | Physical restraints and simulation state |
| Aircraft creeps only at very high power | Partially applied wheel brakes | Toe-brake axes, reversed axes and duplicate bindings |
| Aircraft works from a runway but not a parking stand | Cold-and-dark state, chocks, pushback or scenery | Aircraft ground options and the selected stand |
| Keyboard control works but hardware does not | Controller profile conflict | Throttle and brake assignments on every connected device |
How do I get the aircraft moving again?
Release every physical restraint first, then prove that the engines and control axes are responding correctly.
- Exit pause or Active Pause. Active Pause can freeze the aircraft’s position while cockpit controls and engine instruments continue responding. Return the simulation to normal running speed before testing anything else.
- Run a controlled test. Load a default light aircraft directly onto a runway in its ready-to-fly state. If it moves there, Microsoft Flight Simulator itself is working; the original problem is the aircraft’s start-up state, controller profile, parking position or add-on.
- Release the parking brake and toe brakes. Use the cockpit handle or the assigned command, then watch the handle or annunciation to confirm it changed. Keep your feet completely off physical pedals. MSFS 2024 users can use our reference for the default brake, throttle and engine keyboard commands when testing without flight hardware.
- Remove chocks and tie-downs. Detailed aircraft may manage these through an EFB, cockpit tablet, aircraft options page or ground-services menu. MSFS 2024 aircraft with walkaround features may also require you to remove external equipment before departure.
- Confirm that the engine is producing power. Watch RPM in a piston aircraft or the appropriate turbine indication, such as N1, rather than relying on throttle-lever movement. If the indication does not rise, check the mixture or condition lever, fuel selector, fuel controls and engine state. Our engine-start and fuel-control checks cover failures that leave an apparently ready aircraft without usable thrust.
- Inspect every brake and throttle binding. Open the controls screen for each connected joystick, quadrant, gamepad and pedal set. Search for brake, parking brake and throttle assignments, then remove duplicates. A common mistake we see is both toe brakes resting partially applied because their axes are reversed or never return fully to zero. Reverse the affected axis if its input shows applied with the pedal released, and add only enough dead zone to stop a noisy signal.
- Test without external controllers. Disconnect or switch off flight hardware, then try the keyboard or gamepad. If the aircraft now moves, create a clean controller profile rather than changing aircraft systems. If commands keep reappearing, use our checks for phantom and duplicate control inputs.
- Finish or cancel pushback. A connected tug, active pushback process or incomplete ground-service state can hold the aircraft. Disconnect the tug and verify that chocks and brakes are released; our pushback troubleshooting covers brake, chock and ground-equipment conflicts.
- Try another stand or runway. If only one parking position is affected, the tyres may be caught against scenery geometry or the aircraft may have spawned incorrectly. Restarting at another stand distinguishes that from an aircraft-wide fault.
Why does the aircraft need full throttle before moving?
Needing near take-off thrust to begin taxiing on level pavement usually means the wheel brakes are dragging or a restraint is still fitted.
Do not keep adding power to force the aircraft forward. Check both toe-brake input bars, the parking-brake position, chocks and the tug. A heavy jet may need modest breakaway thrust and a moment for its engines to spool up, but it should not require take-off power for an ordinary taxi.
Why does it move from a runway but not from the gate?
A runway start normally loads the aircraft ready to fly, while a gate start may be cold and dark, chocked or waiting for pushback.
That result rules out a damaged simulator installation. Concentrate on the aircraft’s ground configuration, engine start, EFB or tablet options and the parking stand. If the same aircraft fails only after adding a third-party aircraft or ground-service package, temporarily disable that add-on and repeat the runway-versus-gate test.
Should I reset the controls or reinstall the simulator?
Reinstallation is rarely justified when the aircraft loads normally and its cockpit controls respond.
Reset only the affected controller profile after proving that keyboard or gamepad input works. If every aircraft remains fixed even on a runway with all external controllers disconnected, restart the flight and simulator, test a different default aircraft and airport, and temporarily disable add-ons before considering a broader repair.