Stop runway overshoots in flight simulators by fixing approach speed, touchdown point, spoilers, reverse thrust, brakes and go-around decisions.
To stop overshooting runways in a flight simulator, stabilise at the calculated approach speed and glide path, land within the planned touchdown zone, then use spoilers, reverse thrust and wheel brakes as fitted. Our Aviation & Real-World Flying rule is simple: if a safe touchdown is no longer assured, go around rather than force it.
Most landing overruns begin before the wheels touch. Excess height, speed, tailwind or an extended flare leaves too little runway, and no amount of last-second braking can reliably recover that lost margin.
What does it mean when a plane overshoots the runway?
A runway overrun occurs when an aircraft passes beyond the departure end of the runway during landing or a rejected take-off. People also call this overshooting the runway, although several different events are often grouped under that informal description.
- Long landing: the aircraft touches down beyond the planned touchdown zone but still stops on the runway.
- Landing overrun: the aircraft cannot stop before the end of the runway.
- Take-off overrun: the aircraft passes the runway end during a rejected or unsuccessful take-off. This involves take-off performance and decision-speed planning rather than landing technique.
- Centreline overshoot: the aircraft flies through the extended runway centreline while turning from base to final. That is an approach-path error, not a runway overrun.
- Go-around: the aircraft deliberately flies over the runway without landing. That is a normal safety manoeuvre, not an overrun.
Why does the aircraft run off the end of the runway?
A plane usually overruns the runway because it crosses the threshold with too much energy, touches down too late or fails to use its stopping systems correctly.
| What you see | Likely cause | Correction for the next attempt |
|---|---|---|
| Crossing the threshold high | Late descent, poor glide-path control or an unstabilised approach | Intercept the required path earlier and use the available visual or instrument guidance |
| Floating above the runway | Excess approach speed, added power or an exaggerated flare | Fly the calculated approach speed and make a normal flare without trying to hold off for an exceptionally soft touchdown |
| Touching down far beyond the aiming point | Late flare, long float or reluctance to accept a firm landing | Prioritise the touchdown zone and go around if it will be missed |
| Good touchdown but weak deceleration | Spoilers not deployed, autobrake disarmed, reverse unavailable or brake controls misconfigured | Check cockpit indications and controller assignments before repeating the approach |
| Correct technique but insufficient runway | Unsuitable runway length, tailwind, excessive landing mass, slope or reduced surface friction | Select a runway with more landing margin or remove the limiting condition |
Speed deserves particular attention because kinetic energy rises with the square of velocity. A seemingly small speed excess can produce more float and substantially more energy for the brakes to absorb.
How do I prevent a runway overrun?
Preventing a runway overrun means planning sufficient landing distance, removing excess energy before the threshold and committing to a go-around before the remaining runway becomes the only option.
- Check the usable landing distance. Use the landing distance available rather than assuming the entire paved strip is usable. A displaced threshold reduces the landing length, while a stopway or runway-end safety area is not extra landing distance. Account for aircraft mass, flap configuration, wind, runway slope and surface condition using the simulated aircraft’s performance information where provided.
- Choose the favourable runway. Prefer a runway with adequate length and a headwind component. A tailwind raises groundspeed for the same indicated airspeed and normally increases both float and stopping distance, even when it remains within the aircraft’s stated limit.
- Configure early enough to become stable. Extend the landing gear and required flap without exceeding their limits. Arm the ground spoilers and select an appropriate autobrake setting where the aircraft is equipped with them. Rushing the configuration close to the threshold encourages large power, pitch and trim changes.
- Stabilise the approach. Hold the required speed, descent path, configuration and alignment. A common airline-style gate is approximately 1,000 feet above touchdown in instrument conditions and 500 feet in visual conditions, but the simulated aircraft or operator procedure takes priority. On a three-degree path, groundspeed multiplied by roughly five gives a useful starting estimate for descent rate in feet per minute; do not chase that estimate at the expense of the actual glide-path indication.
- Fly the calculated speed. Use VREF or VAPP from the aircraft’s performance system, electronic flight bag or documentation where available. Add only the specified gust or wind correction. An arbitrary speed buffer is one of the mistakes we see constantly because the extra speed turns directly into float.
- Keep the aiming point steady. If the aiming point moves upwards in the windscreen, the aircraft is likely undershooting; if it moves downwards, the aircraft is likely overshooting. Correct early with coordinated pitch and power changes rather than diving at the runway near the threshold.
- Flare normally and accept a positive touchdown. The aiming point is a reference for the approach, not necessarily the exact wheel-contact point. Do not keep the aircraft airborne to produce a greaser when runway length is limited. Our guidance on controlling the flare without creating a long float covers this phase in more detail.
- Decelerate immediately. Close the thrust, verify spoiler deployment, lower the nose as the aircraft procedure requires, select reverse only where fitted and apply the wheel brakes. For demanding runways, practise our short-field touchdown and braking discipline rather than trying to rescue a long landing with maximum braking.
When should I go around?
Go around when the aircraft is unstable, badly positioned or unlikely to touch down within the intended touchdown zone with a safe stopping margin.
- The speed, descent rate or configuration remains outside the aircraft’s stable-approach criteria.
- The aircraft is high, not aligned or requires aggressive manoeuvring close to the ground.
- A bounce or prolonged float consumes the planned touchdown zone.
- A runway change, tailwind or braking warning removes the calculated margin.
- You feel compelled to force the nose down, land sideways or brake before the main wheels are firmly on the surface.
Apply go-around thrust, control the pitch and retract drag devices in the prescribed sequence; do not retract all flap or the landing gear reflexively. A rejected landing after touchdown is aircraft-specific. Once reverse thrust has been selected, many transport-aircraft procedures require the crew to continue stopping rather than attempt another take-off.
Which braking controls should I use?
Use the systems fitted to the simulated aircraft: wheel brakes normally provide the main stopping force, spoilers place more weight on the wheels, and reverse thrust supplements braking most effectively at higher rollout speeds.
| Aircraft type | Normal stopping methods | Common mistake |
|---|---|---|
| Light piston aircraft | Idle power, aerodynamic drag and progressive wheel braking | Holding the aircraft off too long or locking an unprotected wheel |
| Turboprop | Wheel brakes plus ground fine or reverse where fitted and permitted | Moving the power levers into the wrong range or expecting reverse to recover a late touchdown |
| Jet airliner | Ground spoilers, reverse thrust and autobrake or manual wheel braking | Failing to arm the spoilers, disarming autobrake or delaying brake application |
With anti-skid operating, firm continuous pedal pressure is generally better than pumping the brakes. Aircraft without anti-skid need careful modulation to prevent wheel lock. Autobrake behaviour also varies: it may target a deceleration rate rather than apply a fixed brake pressure, and manual pedal input can disarm it.
Jet pilots should review jet-specific approach energy, spoiler, reverse-thrust and braking technique. For the complete sequence after wheel contact, use our post-touchdown rollout and stopping procedure.
Why does the aircraft still not stop after a good touchdown?
If the touchdown point and speed are correct but deceleration remains weak, the likely cause is an aircraft-system state, controller assignment or simulation-modelling issue.
- Confirm that the physical throttles and cockpit levers reach idle. Some simulated reversers will not unlock until the throttles enter the idle detent.
- Check that the ground spoilers were armed and actually extended after touchdown. Spoiler logic may depend on weight-on-wheels, wheel spin or thrust-lever position.
- Inspect both toe-brake axes for reversed input, excessive dead zones, incomplete travel or duplicate assignments on another controller.
- Watch for small pedal inputs disarming the autobrake. Noisy potentiometers can create input even when your feet are off the pedals.
- Check for brake overheating, failures or wear if the aircraft add-on models them.
- Verify the selected runway state and weather. Wet or contaminated surfaces can lengthen the rollout considerably in aircraft that model reduced friction.
If the game is otherwise good but only one aircraft has implausible stopping performance, compare that aircraft with another type on the same dry runway and calm-weather scenario. A problem that follows one aircraft suggests its configuration or systems; a problem affecting every aircraft points more strongly to control bindings, assistance settings or the simulator’s surface-friction model.
Stopping physics, tyre friction and runway contamination are not modelled equally across all simulators or aircraft add-ons. Simulation is useful for practising judgement and procedures, but its stopping distances must never be used for real-world performance planning.
What if I overshoot the runway centreline while turning final?
Flying through the extended centreline during the base-to-final turn requires an earlier, better-planned turn—not a steep or skidding correction close to the ground.
Higher groundspeed increases the turn radius, while a tailwind on the base leg can carry the aircraft through final sooner than expected. Start the turn earlier, keep it coordinated and use a normal bank angle. If safe alignment cannot be regained, go around; excessive rudder with opposite aileron can create a low-altitude stall-and-spin risk.
What should I prioritise when choosing flights to match a pro-inspired set?
For a pro-inspired runway-overrun practice set, prioritise repeatable aircraft procedures and progressively harder landing conditions rather than route length, destination or livery.
- Begin with one aircraft type. Learn its VREF or VAPP calculation, flap schedule, spoiler logic, reverse operation and brake indications before changing aircraft.
- Start with generous margins. Use a long, dry runway in light wind until the touchdown point and stopping sequence are consistent.
- Add one challenge at a time. Progress to higher landing mass, shorter runways, crosswinds, tailwinds or reduced braking action separately. Changing every variable at once makes errors difficult to diagnose.
- Repeat the approach rather than the entire flight. A saved approach scenario gives more useful landing practice than repeating a long cruise merely to reach the runway.
- Judge the attempt by professional criteria. Record stabilisation, threshold speed, touchdown zone and correct system use. Touchdown smoothness alone is a poor measure of a safe landing.