Find why your aircraft slows too quickly after landing and fix brake axes, autobrake, reverse thrust, spoilers, assists and add-on faults.
Across Microsoft Flight Simulator, X-Plane, FSX and Prepar3D, an aircraft that slows too quickly after landing usually has unwanted wheel braking, aggressive autobrake, reverse thrust left engaged, or a brake axis applying input continuously. Spoilers and aerodynamic drag also cause normal deceleration, so first identify when the speed loss begins.
What usually causes excessive deceleration after landing?
The timing and behaviour of the slowdown usually reveal its cause. A sudden stop at touchdown points towards wheel brakes or parking brake input; strong but controlled deceleration is more likely to be autobrake, reverse thrust or normal aircraft drag.
| What you observe | Likely cause |
|---|---|
| The aircraft nearly stops as soon as the wheels touch | Parking brake set, inverted toe-brake axis or full brake command |
| Fast, straight deceleration after spoilers deploy | High autobrake setting combined with reverse thrust |
| Deceleration continues below normal taxi speed | Reverse thrust, propeller beta or wheel brakes remain engaged |
| The aircraft slows and pulls to one side | One toe brake is applied, miscalibrated or bound incorrectly |
| Only grass or soft surfaces cause the problem | High simulated rolling resistance rather than a brake fault |
| Every aircraft is affected | Controller binding, assistance option or hardware calibration |
| Only one add-on aircraft is affected | Aircraft configuration, flight-model compatibility or add-on fault |
How do I find what is slowing the aircraft?
Use a controlled landing test and remove one possible source of deceleration at a time. Choose a long, dry, paved runway, calm weather and a normal landing weight so runway conditions do not obscure the result.
- Check the parking brake before landing. Confirm that it is fully released, not merely showing a released cockpit lever while a separate hardware switch remains active.
- Watch the control inputs. With your feet off the pedals, both toe-brake axes should display zero input. An axis showing full or partial input at rest is probably inverted, noisy or incorrectly calibrated.
- Search every brake binding. Check normal brakes, left and right brakes, parking brake and any combined brake command. Remove duplicate assignments from throttles, pedals, joysticks and gamepads. A button held by a switch can apply continuous braking even when the cockpit pedals appear normal.
- Test without automatic braking. On the long test runway, select autobrake off and avoid manual braking until the aircraft has slowed naturally. Do not use
RTOfor landing; it is a rejected-take-off mode, and its activation logic varies by aircraft. - Stow reverse thrust deliberately. Make sure the reverser command returns to idle rather than remaining in a reverse detent. On turboprops, verify that a throttle calibration problem is not commanding beta or reverse range.
- Disable piloting assistance for the test. Landing assistance, automated braking or an AI copilot may apply brakes independently of your controls. Setting names differ between simulators, so inspect both assistance options and aircraft-specific tablet or menu settings.
- Compare a default aircraft. Repeat the test with a standard aircraft of a similar type. If every aircraft stops too quickly, concentrate on global controls and assistance settings. If only one aircraft does it, investigate that aircraft rather than changing the whole simulator.
If the brake axes flicker around neutral, add a small dead zone after calibration. If they move in the wrong direction, invert the axis first; a large dead zone will not correct a reversed brake input.
Is rapid deceleration after touchdown normal?
Some rapid slowing is normal, especially in a light aircraft or an airliner using spoilers, autobrake and reverse thrust together. The relevant test is whether the stopping distance suits the aircraft, weight, touchdown speed, runway and selected braking configuration—not whether the visual motion merely feels abrupt.
- Spoilers increase drag and dump wing lift, placing more weight on the wheels so the brakes become effective. Their automatic deployment after touchdown is normally desirable.
- Reverse thrust has its greatest effect at higher ground speeds and becomes less useful as the aircraft slows.
- Propeller drag can decelerate piston and turboprop aircraft strongly at idle, especially with fine pitch, beta or reverse selected.
- Low landing weight means less kinetic energy and often a much shorter rollout than the same aircraft at a heavy landing weight.
- Headwind and uphill slope reduce the ground distance needed, while grass and soft-ground modelling can add substantial rolling resistance.
At low speed, judge the rollout using elapsed time, ground speed and distance rather than cockpit airspeed alone. Camera field of view and a low external viewpoint can make perfectly reasonable deceleration look excessive. Our guide to the brakes, anti-skid, weight-on-wheels logic and spoilers explains how these systems interact after touchdown.
Which autobrake and reverse-thrust settings should I use?
Choose the lowest braking level that safely meets the available runway and intended exit, following the simulated aircraft's procedures. A low autobrake setting suits an unhurried rollout on a long, dry runway; a higher setting is appropriate when landing performance requires stronger deceleration.
Autobrake is generally a target deceleration system rather than a fixed brake pressure. Reverse thrust and aerodynamic drag contribute to that target, so the system may reduce wheel-brake pressure when they are effective. Implementation varies between default and add-on aircraft.
Do not disable spoilers simply to obtain a longer rollout. Leave them configured correctly and reduce excessive autobrake or reverse thrust instead. Apply manual braking progressively, with anti-skid enabled where the aircraft is equipped with it. For the complete sequence, see our safe rollout and stopping procedure.
Airbus users should also distinguish a genuinely unrealistic stop from a short but valid landing distance. Our A320 landing-distance checks cover touchdown speed, runway condition, spoilers, autobrake and reverse thrust together.
Why does this happen with only one aircraft?
If only one aircraft slows too quickly, its own systems or flight model are the likely cause. Confirm that the aircraft is loaded in a normal state, that its brakes and reversers are calibrated through any aircraft-specific controls, and that the simulator's selected flight model matches the add-on developer's guidance.
Remove conflicting modifications, reload the aircraft and compare it with an unmodified aircraft on the same runway. Also check landing weight: an almost empty jet can stop far sooner than expected. Edit configuration files only after ruling out controls, autobrake, assistance settings and operating technique, because those account for most excessive-deceleration reports.