EU261 Extraordinary Circumstances: Airlines' Denial Guide

When a flight arrives more than three hours late, passengers are generally entitled to the same compensation as for a cancellation: €250, €400, or €600 depending on route distance. The CJEU established that entitlement for three-hour delays in Sturgeon and Others (C-402/07), interpreting Regulation (EC) No 261/2004, and affirmed it in Nelson (C-581/10). The regulation’s own text (Article 7) sets the amounts but grants them expressly for cancellation and denied boarding. Airlines still routinely refuse to pay by citing “extraordinary circumstances.” If you know what that phrase means in law, and what the Court of Justice of the European Union (CJEU) has consistently ruled it does not mean, you can tell whether to accept a standard denial letter or dispute it.

Below are the legal framework, the case law that has steadily narrowed the exemption, and what it means for EU261 disputes and for anyone holding event contract positions on flight delays.

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 doesn’t define “extraordinary circumstances” precisely. Recital 14 gives examples: political instability, meteorological conditions incompatible with flight operations, security risks, unexpected flight safety shortcomings and strikes affecting the carrier’s operations. That list is only a set of examples. The CJEU has built the framework through case law.

Two conditions must both be met:

• Extrinsic and non-inherent: The event must not be inherent in the normal exercise of the airline’s activity and must be genuinely outside the carrier’s control.
• Unavoidable despite all reasonable measures: Even when an event counts as extraordinary, the airline must prove that no reasonable operational measure could have avoided the resulting delay.

Both conditions must hold at the same time. An event that is external but avoidable, or inherent but severe, doesn’t meet the exemption. Airlines often blur the two by claiming that severity or surprise alone is enough. Most denials you can challenge come from that blurring.

The CJEU’s Two-Part Test in Practice

Courts across the EU apply the CJEU’s framework the same way. First, they decide whether the event was genuinely outside the airline’s normal operations. Second, they check whether the airline used every reasonable option to limit or avoid the delay.

Most cases turn on the first part. Airlines have argued that technical failures, maintenance issues and operational disruptions from their own activities are extraordinary, and courts have rejected that again and again. The CJEU has held that risks inherent in running an airline can’t be extraordinary by definition. They’re part of the foreseeable operating environment carriers accept when they enter the industry.

If you understand this framework, you’re in a better position to judge whether a denial letter meets the legal standard. For a broader overview of EU261 coverage and thresholds, 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 found during pre-flight checks was not an extraordinary circumstance. Technical problems are inherent in the normal exercise of an air carrier’s activity. A technical fault counts as part of normal airline risk unless the cause behind it is itself extraordinary. The Court gave sabotage and a hidden manufacturing defect affecting a whole fleet as examples.

This matters in practice. A large share of EU261 denials cite “technical fault” or “aircraft defect.” Under Wallentin-Hermann, those reasons on their own aren’t enough to use 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, which standard maintenance couldn’t detect, was an extraordinary circumstance because nobody could have foreseen it. The CJEU rejected this. A component failure being unforeseeable doesn’t make it external to the airline’s control. The risk that parts fail unexpectedly is inherent in running an airline, and a surprising failure is still an ordinary one.

Van der Lans closed a gap airlines tried to use after Wallentin-Hermann. “We couldn’t have anticipated this particular failure” doesn’t mean “this was extraordinary.” Knowledge and control both matter, but the deciding question is still whether the event was inherent in normal operations. Random component failures are.

Pešková (C-315/15): Bird Strikes Can Qualify

Pešková and Pešek v Travel Service is the clearest example of what does qualify. The CJEU held that a bird strike during flight operations can be an extraordinary circumstance. Birds are entirely outside the airline’s control, and no standard operational measure can remove the risk of hitting one.

The ruling doesn’t exempt every bird strike. Even when one is confirmed, the airline must show it took all reasonable measures to avoid the resulting delay: a prompt damage inspection, a check for substitute aircraft and a look at rerouting options. An extraordinary event meets only the first condition. Whether the delay was unavoidable is assessed separately.

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 Prove Its Case

Under Article 5(3) of the regulation, the burden of proof lies entirely with the operating carrier. A denial letter that only says “your flight was disrupted by extraordinary circumstances,” without saying what those circumstances were or what was done to avoid the delay, hasn’t met that burden.

To use the exemption, an airline has to establish three things:

1. What the extraordinary event was, in specific terms. A general category such as “technical fault” or “operational disruption” isn’t enough.
2. Why it was external to normal operations. Being unexpected, severe or expensive doesn’t count.
3. What it did to avoid the delay, such as checking for substitute aircraft, looking at rerouting options and adjusting crew 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 back up denials with documents when a formal dispute is raised. You can ask for the IATA delay code assigned to your flight and ask the airline in writing for records of the extraordinary event and the measures it tried. Airlines don’t have to include this detail in their first denial letter.

If the airline can’t produce enough documentation, or the documents show the disruption came from a cause inherent in normal operations, the exemption fails and compensation is owed.

What This Means When Challenging a Denial

The legal framework leads to a few practical steps:

Request the delay code. Every flight disruption is assigned an IATA delay code. Asking the airline for the code and the incident records is a legitimate first step. Under Wallentin-Hermann, a technical fault code without further evidence of an extraordinary external cause is unlikely to support the exemption.

Challenge vague assertions. If a denial letter cites “technical reasons,” “operational disruption” or “unforeseen circumstances” without saying what happened and why it counts as extraordinary, you have grounds to escalate to the national enforcement body.

Check the “all reasonable measures” step. Even when there was a real extraordinary event, such as a bird strike or a severe storm, whether the airline used all reasonable options is assessed separately. Was a substitute aircraft available? Were passengers offered rerouting on other carriers? If those options existed and the airline didn’t use them, the second condition may fail even if the first is met.

Severity doesn’t make an event extraordinary. A long, expensive delay from a complex technical fault isn’t more extraordinary than a short delay from the same kind of fault. The test is about the nature of the event and how it relates to normal operations. How much disruption or cost it caused doesn’t matter.

Why Event Contract Settlement Is Independent of This Classification

Event contracts on flight arrivals, such as GADUIN’s flight delay markets, settle on the destination airport operator’s published arrival time against its published schedule, both taken from the same board. A flight’s status page shows those scheduled and reported times. The market settles on On time, Delayed or Cancelled by that arithmetic. The airline’s own classification of the cause plays no part. Every share of the outcome that happened pays $1, and every other share pays $0.

The two work on different logic. EU261 asks why the delay happened and whether that cause passes the extraordinary circumstances test. An event contract asks only how late the flight was against the market’s threshold.

A position on a flight that arrives past the threshold settles as Delayed whether the cause was a bird strike, an ATC ground stop or a technical fault, and whether or not the airline claims extraordinary circumstances for EU261. How GADUIN settles a flight market sets out every step: the threshold and the scheduled arrival are fixed when the market opens and never change, and the published arrival decides the rest. How the airline describes the disruption legally has no effect on any of it.

That separation matters if you use event contract positions to offset the cost of travel disruption. The position pays on how late the flight was. EU261 compensation, where it applies and you claim it successfully, is a separate passenger right.

This article is for informational purposes only and does not constitute financial or legal advice. Event contracts carry market risk; a market may settle on any of its three outcomes, and a Delayed position pays nothing if the flight arrives on time or is cancelled. For EU261 disputes, consult your national enforcement body or a qualified legal professional. Not available to US persons.