Fix an aircraft that will not slow down in MSFS 2024 by checking autothrottle, descent energy, spoilers, brakes, assistance and control bindings.
An aircraft that will not slow down in MSFS 2024 usually has excess energy, thrust still commanded by autothrottle or a misbound axis, or ineffective spoilers and wheel brakes. Retard the throttle, reduce the descent rate, use drag devices within their limits, then check assistance options and duplicate controller bindings.
Match the symptom to the likely cause
Where the speed problem occurs is the quickest way to identify its cause.
| What you see | Likely cause | First action |
|---|---|---|
| Airspeed rises during descent with idle thrust | The descent is too steep, or the autopilot is exchanging altitude for speed | Reduce the descent rate or level off, then add approved drag |
| Engine power remains above idle | Autothrottle, an assistance option or a conflicting throttle binding is commanding thrust | Check the cockpit levers and engine indications rather than relying on the hardware position |
| The aircraft floats along the runway | Excess approach speed, a tailwind or late landing configuration | Go around if the approach is unstable and correct the speed earlier next time |
| Little deceleration after touchdown | Ground spoilers, brakes, autobrake or reverse thrust are not operating as expected | Confirm idle thrust, spoiler deployment and actual brake input |
| Indicated airspeed is normal but groundspeed is high | Tailwind or the normal difference between indicated and true airspeed | Compare IAS, TAS and groundspeed before changing the aircraft configuration |
| The airspeed indication appears frozen | An air-data, pitot-icing or simulated-failure issue may be involved | Compare other instruments and check the aircraft's pitot heat and failure settings |
How do I make the aircraft slow down?
A controlled reduction in thrust and descent energy should make a correctly configured aircraft decelerate.
- Return to normal simulation rate. Accelerated time shortens the apparent response window and can make a heavy aircraft seem uncontrollable.
- Check the cockpit thrust indication. Move the physical throttle to idle and verify that the on-screen lever and relevant engine indication also decrease. Turbine engines do not lose thrust instantly.
- Remove unintended automation. At a safe altitude, disconnect autothrottle or autothrust using the aircraft's normal procedure and disable any AI assistance that operates the controls. Match the physical throttle to the cockpit lever first to prevent a sudden power jump.
- Reduce the descent rate. Level off temporarily if terrain and traffic permit. An idle-power aircraft can still accelerate in a steep descent because gravity is adding energy faster than drag removes it.
- Add drag within the aircraft's limits. Use speed brakes or spoilers where permitted, then extend flaps and landing gear according to the published speed limits and normal sequence.
- Inspect the control assignments. Search each connected device for throttle, spoiler and brake inputs. Remove duplicate axes or buttons, confirm the axes reach both ends, and correct any reversed response.
Do not extend flaps or landing gear above their limiting speeds simply to rescue a fast approach. If there is not enough distance or altitude to stabilise the aircraft, go around.
Why does it accelerate with the throttle at idle?
Idle thrust does not guarantee deceleration when the aircraft is descending steeply or the autopilot is commanding a nose-down flight path.
Vertical-speed and path modes can demand a descent that the aircraft cannot maintain without gaining speed. Autothrottle may already be at idle and have no further authority to help. Reduce the commanded descent, level briefly or use permitted speed brake; our explanation of how MSFS 2024 autopilot modes hold speed and altitude covers the difference between pitch-controlled and thrust-controlled speed modes.
Clean jets retain energy particularly well. Lowering the nose to chase the descent path usually makes the problem worse. Plan the descent earlier and configure progressively rather than attempting to lose height and speed at the same time.
Why won't the aircraft slow down on approach?
An aircraft that refuses to slow on approach is normally too high, too fast or configured too late.
Use the correct indicated approach speed for the aircraft's weight and configuration, account for wind, and allow enough distance for idle thrust and drag to work. Flaps are not emergency brakes, and their extension limits still apply. For the wider sequence, see our landing and braking fault checklist; airliner pilots will also benefit from the linked jet approach-speed and energy-management advice.
A common mistake we see is concentrating on the selected speed while ignoring the flight-mode annunciator. The displayed target does not prove the aircraft is actively controlling speed, nor does it guarantee enough drag to meet that target during a steep descent.
Why does it keep rolling after touchdown?
Poor runway deceleration usually means the spoilers or brakes have not activated, even if autobrake was selected before landing.
- Confirm the thrust levers have reached idle.
- Check that the ground spoilers deploy fully rather than remaining armed.
- Verify that toe brakes, triggers or buttons produce actual left and right brake input.
- Use reverse thrust only as the aircraft permits; it supplements wheel braking rather than replacing it.
- Do not use the parking brake as a normal high-speed braking control.
Autobrake logic varies between aircraft and may disarm after manual braking, thrust application or an incorrect landing configuration. A tailwind, downslope or reduced runway grip also raises groundspeed and extends the stopping distance.
Can Airbus autothrust cause this problem?
Yes. In an Airbus, autothrust can continue commanding power while the physical levers remain in a fixed detent.
The climb detent is normal during much of the flight, but a poorly calibrated throttle axis or an incorrect detent can cause unexpected thrust changes. Watch the flight-mode annunciator and commanded engine power, use the proper landing configuration, and move the levers to idle when required during the flare. Our A320 throttle-detent and landing procedure explains the Airbus-specific sequence.
Is this an MSFS 2024 bug or a control problem?
A control or configuration problem is more likely if every aircraft behaves the same way; an aircraft-specific problem is more likely if only one model is affected.
- All aircraft affected: inspect shared throttle bindings, assistance options, simulation rate and controller calibration.
- Only one aircraft affected: check its aircraft-specific control profile, automation logic and throttle-detent calibration.
- Only one controller affected: disconnect that device and test with a keyboard or another saved profile.
- Only add-on aircraft affected: disable the add-on where the platform permits and compare it with an included aircraft in a clean flight.
Preserve your customised profiles before resetting anything. A genuine flight-model or systems fault becomes more plausible only after an included aircraft, a clean control profile and manual thrust control behave normally under the same conditions.