Aircraft not moving in MSFS 2024? Release brakes and chocks, verify engine power, fix control bindings and solve pushback faults.
An aircraft that will not move in Microsoft Flight Simulator 2024 is usually being held by the parking brake, wheel chocks or a misbound brake axis. Release all ground restraints, confirm the engines produce thrust, then check for duplicate controls. If it is parked at a gate, pushback may be required first.
Get the aircraft moving: checks in the right order
Work through these checks in order rather than applying more power, which can make the aircraft lurch forwards when the restraint finally releases.
- Exit every pause state. Resume from the pause menu and turn off Active Pause. Active Pause can freeze the aircraft while cockpit controls, engines and instruments continue responding, making the problem look like a brake or throttle fault.
- Remove chocks and ground equipment. During the MSFS 2024 walkaround, inspect each wheel and remove any available chocks or tiedowns. Some aircraft instead control these through their EFB, cockpit tablet or ground-services page; add-on aircraft may use their own system rather than the simulator's general controls.
- Release both types of brake. Disengage the parking-brake lever, then make sure the left and right wheel-brake inputs return fully to their resting positions. The parking brake can be off while an inverted toe-brake axis continues holding the aircraft. If the binding is unclear, use our control reference for brakes, throttle and engine-start commands and check the active preset for your device.
- Confirm that the engine is producing power. Watch RPM, torque or jet-engine indications as the throttle advances; cockpit lever movement alone does not prove that thrust is increasing. Check the mixture, propeller or condition lever, fuel selector, fuel cutoff and ignition as applicable. If the lever moves but the gauges do not respond correctly, diagnose the throttle axis and duplicate bindings.
- Isolate unwanted controller inputs. Centre the pedals and analogue triggers, then disconnect additional controllers one at a time. Search the controls settings for
brake,parking brakeandthrottle; remove duplicate assignments and invert an axis only when its input meter runs backwards. Our guide to tracing brakes triggered by other flight controls covers noisy hardware and misassigned axes. - Use pushback at a nose-in stand. Do not attempt to taxi forwards through a terminal stand. Disconnect the jetway and any modelled ground connections, request a tug, then release the parking brake only when instructed.
- Test another ramp. If the aircraft remains stuck, load the same model at a clear runway or ramp. Movement there points to a gate, terrain or scenery collision rather than an aircraft-control fault.
How can I tell whether the brakes or throttle are at fault?
Engine-gauge response is the quickest way to separate a power problem from a restraint or brake problem.
| Symptom | Likely cause | What to check |
|---|---|---|
| Throttle moves but engine indications do not rise | Engine configuration or throttle binding | Fuel controls, mixture or condition lever, ignition and throttle-axis assignments |
| Power rises normally but the aircraft stays still | Parking brake, chocks or toe brakes | Ground equipment and both left and right brake inputs |
| Aircraft moves only at unusually high power | Partial brake input or steep/soft ground | Axis resting positions, inversion and the parking surface |
| Aircraft turns sharply as it begins moving | One wheel brake remains applied | Separate left and right toe-brake axes |
| Everything responds but position never changes | Active Pause | Pause state and simulation controls |
| Problem occurs at one parking stand only | Scenery or spawn-point collision | A nearby ramp using the same aircraft |
Why will the tug not push the aircraft back?
A connected tug will not move the aircraft if the parking brake, wheel chocks or another pushback system is still active.
Keep the brake set while the tug attaches, remove chocks, then release the brake when the ground crew requests it. Avoid running the simulator's tug and an aircraft-specific pushback tool together. If the tug connects but nothing happens, follow the correct ground-services and pushback sequence.
Why does it happen with only one aircraft or airport?
A fault limited to one aircraft usually comes from that model's ground configuration; a fault limited to one stand usually comes from the scenery or spawn point.
- One aircraft: open its EFB or tablet and remove chocks, covers and external equipment. If offered, load a ready-to-taxi state as a diagnostic test.
- Every aircraft: inspect the common controller preset, brake axes and pause state.
- One airport or stand: move to another ramp. If the landing gear appears sunk into the surface or the aircraft rocks without rolling, reload away from that spawn point.
- Only an add-on aircraft or scenery: test without that add-on enabled. This distinguishes aircraft logic from a surface or collision problem.
When should I restart the flight?
Restart only after checking pause, chocks, parking brake, wheel-brake axes and engine power.
A reload is justified when the landing gear has spawned inside the pavement, a ground-service process is stuck, or control input meters no longer respond. Choose a clear runway for the test: if a default aircraft moves there, the simulator itself is working and the remaining fault is specific to the original aircraft, control preset or parking position.