Runway Excursion

A runway excursion occurs when an aircraft leaves the runway surface during the takeoff or landing roll. It takes two forms. A veer-off is a lateral departure — the aircraft runs off the side of the runway, typically after a directional-control loss in a crosswind, on a contaminated surface, or during aerodynamic braking. An overrun is a longitudinal departure — the aircraft runs off the far end because it could not be stopped, or could not accelerate-stop, within the available distance. The CAST/ICAO Common Taxonomy Team (CICTT) captures these events under the Runway Excursion (RE) occurrence category, which is one of the five Global High-Risk Categories of Occurrence in the ICAO Global Aviation Safety Plan, alongside Loss of Control In-Flight, Controlled Flight Into Terrain, Mid-Air Collision, and Runway Incursion.

A runway excursion is not the same event as a runway incursion, and the two are frequently confused. A runway incursion is the incorrect presence of an aircraft, vehicle, or person on the protected surface used for landing and takeoff — a separation and surface-conflict problem. A runway excursion is a single aircraft leaving the runway it is legitimately using — a control, energy, and stopping-distance problem. They share the word 'runway' and little else in mechanism. Runway excursions are, by frequency, the most common runway-safety accident category, and the large majority occur on landing rather than takeoff — reflecting the reality that landing concentrates the highest-workload combination of energy dissipation, directional control, and surface condition into a few seconds.

The contributing factors cluster around energy and surface state. An unstable approach — too fast, too high, or not configured by the stabilization gate — arrives at the threshold with excess energy that translates into a long landing, a fast touchdown, or both, consuming runway that was needed for stopping. A long flare or float, a tailwind component, and a failure to go around when the approach or landing is not working compound the problem. Surface condition is the other half: a wet, contaminated, or snow- or slush-covered runway reduces braking action, and standing water introduces the risk of hydroplaning, where a film of water lifts the tire off the surface and directional control and braking are lost. Reported braking action, the crosswind component relative to the aircraft's demonstrated limit, and the accuracy of the landing-distance assessment all feed directly into excursion risk.

Prevention is largely the mirror image of the causes. Flying a stabilized approach to defined criteria ensures the aircraft crosses the threshold at the correct speed, on the correct path, in the correct configuration, so the touchdown point and energy are as planned. Go-around discipline — treating a go-around as a normal, expected outcome whenever the approach or landing is not stabilized or the touchdown is long or fast — removes the pressure to salvage a landing that should be abandoned. A realistic landing-distance assessment that accounts for the actual runway length available, surface condition, wind, and any tailwind, rather than the still-air dry-runway figure, ensures the aircraft is only committed to runways it can actually stop on. The Flight Safety Foundation's Approach and Landing Accident Reduction (ALAR) work addresses runway excursions directly, since the unstable approach that causes many excursions is the same precursor implicated in approach-and-landing accidents generally.

Runway excursions are a training-environment reality, not an airline-only concern. Flight schools operate light aircraft with modest crosswind capability, often from shorter runways, flown by students who are still building the crosswind technique, speed control, and go-around judgment that prevent excursions. Base-to-final speed control, the decision to go around from a bounced or long landing, and honest assessment of a wet or gusty crosswind day against personal and aircraft limits are exactly the competencies at issue — and they are being learned, sometimes for the first time, in the school's aircraft. A school's willingness to set and enforce sensible crosswind and runway-condition limits for solo students directly determines how much excursion risk it carries.

Operationally, excursions and their precursors carry both a safety-data and a maintenance dimension. A veer-off or overrun, even a minor one onto a grass shoulder, can produce a propeller strike, gear or tire damage, or FOD that grounds the aircraft and requires inspection before return to service. Capturing hard landings, long landings, and excursions as reported occurrences lets a school see whether a particular runway, wind condition, or stage of training is generating a cluster of events — and connect the occurrence to the maintenance action it triggers, so the aircraft is not dispatched again before the required check is complete.

Aviatize's Safety Management module lets a school record runway excursions and their precursors — unstable approaches, long or hard landings, loss of directional control in a crosswind — as structured occurrence reports feeding a hazard log and risk assessment. Trends surface in KPI Reporting & Dashboards, so a recurring pattern on a particular runway, in particular wind conditions, or at a particular training stage becomes visible and actionable rather than anecdotal.

When an excursion causes damage, Aviatize connects the safety and engineering sides: the occurrence can drive a defect and inspection requirement in Maintenance Control, so the aircraft's return to service depends on the required check being signed off, with the whole chain preserved in Digital Data & Records for audit. Smart Planning & Booking then keeps the affected aircraft out of the schedule until it is released, so a damaged aircraft is not inadvertently dispatched.