EU261 Extraordinary Circumstances: Airlines' Denial Guide
EU Regulation 261/2004 lets airlines deny compensation by invoking extraordinary circumstances. Learn what courts rule qualifies — and what doesn't.
When a flight arrives more than three hours late, passengers are generally entitled to the same compensation as for cancellation — €250, €400, or €600 depending on route distance. That three-hour delay entitlement was established by the CJEU in Sturgeon and Others (C-402/07) interpreting Regulation (EC) No 261/2004 — the regulation’s own text (Article 7) sets the amounts but grants them expressly for cancellation and denied boarding — and was affirmed in Nelson (C-581/10). Yet airlines routinely deny that compensation by invoking “extraordinary circumstances.” Understanding what that phrase actually means in law — and what the Court of Justice of the European Union (CJEU) has consistently ruled it does not mean — is the difference between accepting a standard denial letter and successfully disputing it.
This guide examines the legal framework, the case law that has progressively narrowed how airlines can use the exemption, and what the distinction means for both EU261 disputes and for market participants holding event contract positions on flight delay outcomes.
What “Extraordinary Circumstances” Means Under EU Regulation 261/2004
Article 5(3) of Regulation (EC) No 261/2004 states that an operating carrier is not obliged to pay compensation if it proves the delay or cancellation was caused by extraordinary circumstances which could not have been avoided even if all reasonable measures had been taken.
The regulation does not define “extraordinary circumstances” precisely. Recital 14 offers examples — political instability, meteorological conditions incompatible with flight operations, security risks, unexpected flight safety shortcomings, and strikes affecting the carrier’s operations — but that list is illustrative, not exhaustive. The CJEU has developed the framework through case law.
Two threshold conditions must both be satisfied:
- Extrinsic and non-inherent: The event must not be inherent in the normal exercise of the airline’s activity and must lie genuinely outside the carrier’s control.
- Unavoidable despite all reasonable measures: Even when an event qualifies as extraordinary, the airline must prove that the resulting delay could not have been avoided by any reasonable operational measure.
Both conditions must hold simultaneously. An event that is extrinsic but avoidable — or inherent but severe — does not satisfy the exemption. Airlines frequently conflate the conditions by asserting that severity or unexpectedness alone is sufficient. That conflation is the root of most contestable denials.
The CJEU’s Two-Part Test in Practice
Courts across the EU apply the CJEU’s framework consistently: first, determine whether the event was genuinely external to the airline’s normal sphere of operations; second, assess whether the airline exhausted every reasonable option to limit or avoid the resulting delay.
The first limb does most of the work. Airlines have argued — and courts have repeatedly rejected — that technical failures, maintenance issues, and operational disruptions arising from their own activities are extraordinary. The CJEU has held that risks inherent in running an airline cannot, by definition, be extraordinary: they are part of the foreseeable operating environment that carriers accept when they enter the industry.
Passengers who understand this framework are better positioned to assess whether a denial letter actually meets the legal standard. For a broader overview of EU261 coverage and threshold conditions, see the EU261 flight compensation rights guide.
Three CJEU Rulings That Define Where the Line Sits
Wallentin-Hermann (C-549/07) — Technical Faults Are Not Extraordinary
In Wallentin-Hermann v Alitalia, the CJEU held that a turbine fault discovered during pre-flight checks did not constitute extraordinary circumstances. Technical problems are inherent in the normal exercise of an air carrier’s activity. Unless a technical fault stems from a cause that is itself extraordinary — the Court cited sabotage or a hidden manufacturing defect affecting an entire fleet as examples — the fault falls within the ordinary risk profile of airline operations.
The practical consequence is significant. A substantial share of EU261 compensation denials cite “technical fault” or “aircraft defect.” Under Wallentin-Hermann, those categories, standing alone, are legally insufficient to invoke the exemption.
Van der Lans (C-257/14) — Hidden Defects Remain Ordinary
In van der Lans v KLM, KLM argued that a fuel regulator malfunction — undetectable through standard maintenance procedures — constituted an extraordinary circumstance because it was genuinely unforeseen. The CJEU rejected this argument. The unforeseeability of a specific component failure does not transform it into an event external to the airline’s control. The statistical risk that components fail unexpectedly is inherent in operating an airline; it does not become extraordinary by virtue of being surprising.
Van der Lans closed a gap that airlines attempted to exploit after Wallentin-Hermann: the argument that “we couldn’t have anticipated this particular failure” is not equivalent to “this was extraordinary.” Both knowledge and control matter, but the decisive question remains whether the event was inherent in normal operations — and random component failures are.
Pešková (C-315/15) — Bird Strikes Can Qualify
Pešková and Pešek v Travel Service provides the clearest example of what does qualify. The CJEU held that a bird strike during flight operations can constitute an extraordinary circumstance: birds are external agents entirely outside the airline’s control, and no standard operational measure can eliminate the risk of collision.
The ruling is not a blanket exemption, however. Even where a bird strike is confirmed, the airline must demonstrate it took all reasonable measures to avoid the resulting delay — prompt damage inspection, assessment of substitute aircraft availability, rerouting alternatives considered. The extraordinary nature of the event satisfies only the first condition; unavoidability of the delay is assessed independently.
What Airlines Argue vs What Courts Have Ruled
| Claimed Cause | Airlines’ Argument | CJEU / Enforcement Position |
|---|---|---|
| Engine or turbine technical fault | ”Unforeseeable mechanical failure” | Generally not extraordinary (Wallentin-Hermann) |
| Hidden component failure | ”Undetectable in standard maintenance” | Generally not extraordinary (van der Lans) |
| Bird strike | ”External, uncontrollable collision” | Can qualify; unavoidability of delay must still be proven (Pešková) |
| Severe weather (storm, dense fog, heavy snow) | “Meteorological force majeure” | Generally extraordinary if directly and specifically causing the delay |
| Air traffic control restrictions | ”ATC decision outside airline’s sphere” | Generally extraordinary when ATC imposes binding operational restrictions |
| Own-staff strike | ”Industrial action beyond our control” | Own-staff strikes generally not extraordinary; third-party strikes may qualify |
| Airport closure (security event, runway contamination) | “Authority decision, not ours” | Generally extraordinary when genuinely external to airline operations |
General guidance based on CJEU jurisprudence. Individual outcomes depend on specific facts; consult the relevant national enforcement body for case-specific advice.
Burden of Proof: Why the Airline Must Demonstrate, Not Just Assert
Under Article 5(3) of the regulation, the burden of proof lies entirely with the operating carrier. A denial letter stating only that “your flight was disrupted by extraordinary circumstances” — without specifying what those circumstances were or what measures were taken to avoid the delay — has not met that burden.
To successfully invoke the exemption, an airline must establish three distinct points:
- What the extraordinary event was — with specifics, not a generic category such as “technical fault” or “operational disruption.”
- Why it was inherently external to normal operations — not merely unexpected, severe, or operationally costly.
- What measures were taken to avoid the delay — substitute aircraft assessed, rerouting alternatives considered, crew adjustments made where possible.
National enforcement bodies — including the UK Civil Aviation Authority, Germany’s Luftfahrt-Bundesamt, and France’s Direction Générale de l’Aviation Civile — require airlines to substantiate denials with documentary evidence when a formal dispute is raised. Passengers can request the IATA delay code assigned to their flight and ask the airline in writing for documentation of the extraordinary event and the measures attempted. Airlines are not required to include this detail in initial denial letters.
If the airline cannot produce adequate documentation — or if the documentation shows the disruption arose from a cause inherent in normal operations — the exemption fails and compensation is owed.
What This Means When Challenging a Denial
Several practical steps follow from the legal framework:
Request the delay code. IATA delay codes are assigned to every flight disruption. Asking the airline for the delay code and supporting incident documentation is a legitimate first step. A technical fault code, without additional evidence of an extraordinary external cause, is unlikely to support the exemption under Wallentin-Hermann.
Challenge vague assertions. If a denial letter cites “technical reasons,” “operational disruption,” or “unforeseen circumstances” without specifying what happened and why it qualifies as extraordinary, that vagueness is grounds to escalate to the national enforcement body.
Examine the “all reasonable measures” step. Even where a confirmed extraordinary event exists — a bird strike, a severe storm — the question of whether the airline exhausted all reasonable options is assessed separately. Was a substitute aircraft available? Were passengers offered rerouting on competing carriers? If those options existed and were not pursued, the second condition may not be satisfied even if the first is.
Understand that severity does not equal extraordinary. A long, costly delay caused by a complex technical fault is not more extraordinary than a short delay from the same category. The classification turns on the nature of the event and its relationship to normal operations, not its operational or financial severity.
Why Event Contract Settlement Is Independent of This Classification
Event contracts on flight arrival outcomes — such as those available on GADUIN’s flight delay markets — settle on objective, third-party-verified delay data: the measured difference between scheduled and actual arrival time as reported by official sources. The contract resolves to an On Time, Delayed, or Cancelled outcome based on reported arrival minutes — not on the airline’s internal classification of the disruption’s cause.
The two mechanisms operate on fundamentally different logic. EU261 asks why the delay happened and whether that cause meets the extraordinary circumstances test. An event contract asks only how long the delay lasted relative to the contract’s threshold.
A position on a flight that arrives beyond the contract threshold settles at the Delayed outcome whether the disruption arose from a bird strike, an ATC ground stop, or a technical fault — regardless of whether the airline invokes the extraordinary circumstances exemption for EU261 purposes. GADUIN’s oracle-based settlement process verifies arrival time against official reporting and resolves accordingly. The airline’s legal characterisation of the disruption has no bearing on that process.
For travellers and institutional participants using event contract positions to maintain financial exposure to travel disruption, this separation is material. The position covers the measurable cost of the delay as a time event. EU261 compensation — where applicable and successfully pursued — addresses the separate dimension of regulatory passenger rights.
This article is for informational purposes only and does not constitute financial or legal advice. Event contracts carry market risk; positions may resolve at any outcome including On Time or Cancelled. For EU261 disputes, consult your national enforcement body or a qualified legal professional. Not available to US persons.