Quick summary
An EasyJet Airbus A320 carrying 180 passengers cleared the end of London Luton Airport’s runway at just 65 feet (19 meters) above the ground on June 13, 2025, after the crew departed from intersection Alpha without updating takeoff performance calculations set for the full 1,982-meter runway. The Air Accidents Investigation Branch (AAIB) published its bulletin on June 15, 2026, identifying habit patterns and confirmation bias as the primary causes. EasyJet has since changed its takeoff calculation procedures.
This is not an isolated error — near-identical intersection confusion caused a separate EasyJet A320 to liftoff with only 110 meters of runway remaining at Lisbon. The AAIB’s findings now form a documented pattern regulators cannot ignore.
An EasyJet flight bound for Malaga came within a razor-thin margin of catastrophe at London Luton Airport last June — and the crew had no idea anything was wrong until a phone call later that day.
The AAIB bulletin, published June 15, 2026, describes how the A320’s crew had specifically recalculated takeoff performance for the full runway length because the aircraft was heavier than usual. Then, during taxi, air traffic control offered a shortcut: departure from intersection Alpha, which cuts 211 meters off the available runway. The captain accepted. The crew lined up, ran their checks, and rolled — using performance data that no longer matched the ground beneath them.
The aircraft cleared the runway end at 65 feet. On a normal departure, that number should be considerably higher. Neither pilot realized the error until the airline’s Flight Data Monitoring system flagged a post-flight alert and the captain received a call from his supervisor asking about the “questionable runway length remaining.”
Airbus ran the numbers at investigators’ request. Even with a single engine failure during that takeoff roll, the aircraft would still have cleared obstacles beyond the runway end. That conclusion is the only reason this story does not end differently.
What the AAIB found — and what it means for Luton departures
The AAIB bulletin identifies the core failure as a breakdown between two separate crew decisions that were never reconciled. The crew initially planned to use intersection Alpha — their habitual departure point at Luton — then switched to a full-length calculation because of the heavier load. When ATC offered the intersection back during taxi, the captain accepted without connecting that offer to the earlier conversation with his first officer. Habit, in effect, overwrote procedure.
Investigators noted that ATC was never informed of the crew’s revised intent to use the full-length position. That single gap removed the one external check that might have caught the mismatch before the aircraft moved onto the runway. The AAIB’s published bulletin attributes the error to high workload, limited attention, suboptimal situational awareness, and confirmation bias — the same cluster of factors cited in earlier EasyJet intersection incidents.
Before this incident, EasyJet did not require pilots to formally record which intersection they intended to use when calculating takeoff performance. Crews relied on memory. That policy has since changed.
| Incident | Date | Runway shortfall | Height at runway end | Outcome |
|---|---|---|---|---|
| London Luton to Malaga | 13 June 2025 | 211 m less than calculated | 65 ft (19 m) | Safe departure; FDM alert triggered post-flight |
| Lisbon to Manchester | 2019 | Approximately 1,400 m less than calculated | ~110 m runway remaining at liftoff | Safe departure; EasyJet issued crew notices on intersection designations |
| Lisbon (earlier case) | 2017 | Full-length data used; intersection departure taken | ~110 m runway remaining at liftoff | AAIB linked to workload and confirmation bias; EasyJet adjusted guidance |
For travelers on flights from Europe to Spain routing through Luton, the practical effect of reinforced procedures is likely to be minor — slightly longer lineup times and more deliberate pre-departure checks — rather than significant disruption.
The AAIB bulletin also connects this event to a broader pattern. Investigators noted that Airbus is developing a system for the A320 family intended to protect against incorrectly calculated takeoff performance, though it would not have triggered in the earlier Lisbon cases because runway remaining still exceeded the forecast liftoff distance. The Luton case may change that calculus.
ATC’s role in the Luton incident is worth noting separately. The offer of an intersection departure during taxi is routine and operationally efficient — controllers do it constantly. The problem was not the offer; it was that no mechanism existed to ensure the crew’s acceptance was cross-checked against their performance data. That gap is now visible to regulators.
For a fuller picture of the AAIB’s findings across multiple EasyJet runway-position errors in 2025, including a second incident at Manchester Airport in July of that year, the AAIB’s findings on EasyJet A320 runway departures covers all three cases in detail.
Flight deals
most people never see
Our AI monitors 150+ airlines for pricing anomalies that traditional search engines miss. Air Traveler Club members save $650 per trip per person on average: see how it works.
Each deal saves 40–80% vs. regular fares:
Why this keeps happening — and what the pattern tells us
Intersection departures are not inherently dangerous. Airlines use them constantly to improve runway throughput and reduce taxi times. The risk emerges specifically when a crew has already committed to one configuration — full-length, in this case — and then accepts a change without formally resetting their calculations. That cognitive gap is well-documented in aviation human factors research, and it is exactly what the AAIB found here.
The Lisbon precedent is instructive. In that case, the crew used performance data for the full length of runway 21 while actually departing from a shorter intersection, leaving the aircraft with roughly 110 meters of tarmac at liftoff — about one second from the end of the runway. EasyJet revised its guidance afterward and raised pilot awareness of intersection-related risks. The Luton incident suggests those fixes did not fully close the vulnerability.
What has changed this time is the procedural fix: EasyJet now requires pilots to formally record the intended intersection when calculating takeoff performance, removing the reliance on memory that allowed both errors to occur. Whether the CAA will mandate additional changes — to ATC phraseology, crew briefing requirements, or both — depends on what the AAIB’s final report recommends.
What Luton passengers should do now
EasyJet has already changed its takeoff calculation procedures, and the AAIB investigation is ongoing — but travelers with upcoming Luton departures should account for the possibility of slightly longer pre-departure sequences while reinforced checks bed in.
- Add buffer to your airport arrival time. Build an extra 15–20 minutes into your schedule for EasyJet departures from Luton. Enhanced intersection-verification procedures and more deliberate lineup checks may add a few minutes to taxi and lineup sequences, particularly during busy morning banks.
- Monitor your flight status directly. Use the EasyJet app or easyjet.com flight-status tool for real-time updates. If a short delay appears, it is more likely procedural than mechanical — no need to escalate unless it extends beyond 30 minutes.
- Keep self-connection windows generous at LTN. If you are connecting at Luton between two separate bookings, allow at least 2–3 hours landside. Luton’s single terminal and limited airside facilities mean any departure delay compounds quickly. Gatwick and Stansted offer more buffer for tight connections.
- Understand your rights if delays extend. Under UK261 (the retained EU261 regulation), delays of three hours or more at departure entitle passengers to compensation depending on route distance. A 15-minute procedural delay does not trigger this — but knowing the threshold is useful if a minor delay cascades.
Watch: The AAIB’s final report on the Luton incident — expected within the next several months — will indicate whether formal safety recommendations are issued to the CAA. If they are, expect the CAA to require documented changes to EasyJet’s SOPs or Luton ATC procedures. If recommendations are minimal, EasyJet’s internal procedural fix may be the primary outcome.
Questions? Answers.
Was the EasyJet Luton flight actually in danger of crashing?
Airbus ran a performance analysis at investigators’ request and concluded that even with a single engine failure during the takeoff roll, the aircraft would still have cleared obstacles beyond the runway end. The margin was uncomfortably thin — 65 feet at the runway threshold — but the aircraft was not in immediate danger of an overrun under the conditions that existed. The concern is what would have happened had conditions been slightly different: higher temperature, a wet runway, or a mechanical issue.
Has EasyJet fixed the problem that caused this incident?
EasyJet has changed its takeoff calculation procedures so that pilots must now formally record the intended departure intersection when computing performance data, rather than relying on memory. This directly addresses the mechanism that caused both the Luton and earlier Lisbon incidents. Whether the UK CAA will mandate additional changes — to crew briefing requirements or ATC phraseology — depends on the AAIB’s final report and any formal safety recommendations it contains.
Is London Luton Airport safe to fly from?
Yes. The AAIB investigation is a standard safety process — its purpose is to identify causes and prevent recurrence, not to indicate that an airport or airline is unsafe to use. Luton handles millions of passengers annually without incident. The procedural changes EasyJet has already implemented reduce the specific risk identified in this case. Travelers should have no reason to avoid Luton on safety grounds.
Were there other similar EasyJet incidents beyond the Luton and Lisbon cases?
The AAIB has also published findings on a second EasyJet A320 runway-position error at Manchester Airport in July 2025, and a separate incident at London Southend Airport in April 2026 where five passengers were offloaded because the aircraft exceeded safe takeoff weight limits on that airport’s constrained runway. The pattern across multiple airports and aircraft suggests a systemic vulnerability in how intersection departures were being managed — one that EasyJet’s procedural update is intended to close.
