What Extraordinary Circumstances Actually Means Under EU261: A Complete Reference
The extraordinary circumstances defense is the single most common reason airlines cite when rejecting compensation claims. It is also one of the most misapplied. This article walks through what actually qualifies, what does not, and why the distinction matters.
Why this defense matters
Under EU Regulation 261/2004, passengers are entitled to fixed compensation for delays of three hours or more, cancellations, and denied boarding, calculated by flight distance. Airlines can escape this liability in only one way: by proving that the disruption was caused by extraordinary circumstances that could not have been avoided even if all reasonable measures had been taken.
This exception was written narrowly. It was designed to protect airlines from liability for events genuinely outside their control, not to provide a general escape from compensation obligations. In practice, however, extraordinary circumstances has become the default rejection basis for a large share of EU261 claims. Airlines invoke it frequently, often generically, and rely on the fact that most passengers cannot easily evaluate whether the defense actually applies.
Understanding what the exception covers, and just as importantly what it does not cover, is the difference between accepting a rejection at face value and successfully challenging it.
The legal framework
The extraordinary circumstances exception is set out in Article 5(3) of EU261. The Court of Justice of the European Union has interpreted this provision in a substantial body of case law that has clarified how it applies in specific factual scenarios.
Three principles run through all of it.
The event must be genuinely outside the airline's control. Events that arise from the airline's own operations, decisions, or workforce do not qualify, even when they are unexpected or disruptive. The exception is for external events, not internal ones.
The event must have actually caused the specific disruption. Generic references to broader events are not sufficient. The airline must show that the specific flight was affected by the specific circumstance claimed, and it must produce primary, flight-specific evidence to support this.
Reasonable measures must have been taken. Even where extraordinary circumstances genuinely apply, the airline is still liable if the disruption could have been avoided or mitigated through reasonable operational responses. This is the reasonable measures test, and airlines almost never address it in initial rejections. It is a separate analytical requirement that has to be satisfied on top of establishing the extraordinary event itself.
These three principles determine whether any given rejection actually holds up. The categories that follow examine how they apply across the specific circumstances airlines most commonly cite.
See: How Airline Compensation Works
Weather
Weather is the most frequently cited extraordinary circumstance and the most frequently misapplied.
When it qualifies. Severe weather that makes flight operations physically impossible or unsafe can qualify as extraordinary. Confirmed thunderstorms directly over the airport, dense fog reducing visibility below operational minimums, icing conditions requiring extended de-icing beyond normal ranges, or high winds outside the aircraft's certified limits are the clearest cases. The weather has to be at the flight's actual origin, destination, or route, not general regional conditions, and it has to be severe enough to actually prevent operation.
When it does not qualify. Routine bad weather that most flights operate through, weather at other airports that did not directly affect the flight in question, weather that ended before the disruption began, and mild conditions that would normally not affect operations do not qualify. Airlines sometimes cite weather from a previous sector of the aircraft's rotation as justification for a later disruption. This can qualify as a ripple effect in narrow cases but usually fails because the airline cannot prove that reasonable measures could not have restored operations.
Evidence required. Airlines invoking weather must reference METAR (current weather observations) and TAF (terminal aerodrome forecasts) for the affected airport during the relevant timeframe. Vague references to "adverse weather conditions" without specific meteorological reports are not primary evidence. Weather data is publicly available and can be verified independently.
Real-world example. In the Iberia case discussed in a previous article, the airline cited weather affecting a previous flight as the cause of a subsequent delay. The claim was challenged on the basis that the reasoning did not meet the required legal standard, and the case was resolved in the passenger's favor after litigation.
See: When Airlines Blame Weather to Deny Compensation
Technical and mechanical issues
This is one of the most misapplied defenses. Airlines frequently cite technical faults as extraordinary, and this claim almost never holds up.
When it qualifies. In very narrow circumstances, a hidden manufacturing defect that could not have been detected through normal maintenance and that is subsequently addressed by a manufacturer safety directive or airworthiness directive can qualify. These cases are rare, and the airline must produce specific documentation identifying the defect and the corrective action.
When it does not qualify. Routine mechanical issues, component failures during normal operation, maintenance-related delays, aircraft rotation problems, and any technical fault that could reasonably have been anticipated or addressed through standard maintenance do not qualify. This is the settled position under the seminal CJEU case Wallentin-Hermann v. Alitalia (C-549/07), which established that technical problems inherent to the normal exercise of an airline's activity are not extraordinary circumstances.
Evidence required. For a technical defense to succeed, the airline must produce specific evidence identifying the fault, showing that it fell outside normal maintenance responsibility, and demonstrating that no reasonable measures could have prevented or mitigated the resulting disruption. Generic references to "technical issues" are not sufficient.
Why airlines keep trying. The technical defense is used frequently precisely because it sounds authoritative to passengers who do not know the legal position. In practice, an initial rejection citing "technical issues" is one of the most reliably challengeable rejections in EU261.
Air traffic control restrictions
ATC restrictions are frequently cited, and their treatment depends heavily on the specific nature of the restriction.
When it qualifies. Genuine airspace closures issued by aviation authorities, unforeseeable ATC-imposed flow restrictions caused by external factors, and safety-related traffic management measures outside the airline's control can qualify. These are typically documented in NOTAMs and can be verified independently.
When it does not qualify. Routine ATC delays caused by ordinary traffic volumes, restrictions attributable to normal seasonal or operational patterns, and delays caused by the airline's own scheduling or slot management do not qualify. A general "ATC restrictions" citation without specific NOTAM evidence is not primary evidence.
Evidence required. Airlines must produce specific NOTAM references identifying the restriction, its geographic scope, its effective timeframe, and its applicability to the specific flight. Reduced arrival rate restrictions require evidence of the underlying cause, not just the restriction itself.
Reasonable measures overlay. Even where an ATC restriction qualifies as extraordinary, the airline must show that reasonable measures could not have avoided or mitigated the impact. Repositioning aircraft, adjusting crew schedules, or using alternative routing are all measures airlines are expected to consider.
See: What NOTAMs Are and Why Airlines Misrepresent Them
Strikes
Strike-related defenses require careful attention to the specific nature of the strike and the airline's relationship to the striking workforce.
When it qualifies. Strikes by third parties who are not under the airline's employment or contractual authority can qualify. This includes strikes by air traffic controllers, airport security staff, fueling crews not directly employed by the airline, and other third-party workers whose actions are outside the airline's sphere of influence.
When it does not qualify. Strikes by the airline's own staff do not qualify. This is well-established under CJEU case law. Cabin crew strikes, pilot strikes, and strikes by ground staff directly employed by the airline are treated as internal matters within the airline's sphere of responsibility. The airline is expected to have ongoing labor relations with its own workforce and cannot escape compensation obligations by pointing to disputes it has failed to resolve.
Mixed strikes and ripple effects. A strike that involves both airline staff and third-party workers becomes fact-specific. The airline must isolate the third-party element and prove it caused the disruption. A strike that has ended but whose effects extend into subsequent days requires specific evidence that reasonable measures could not have restored operations.
Real-world example. The TAP Air Portugal case discussed in a previous article involved a cancellation the day after a Portuguese general strike ended. TAP's own cabin crew union had participated in the strike, and the cancellation was operational rather than directly caused by the strike itself. The defense did not survive analysis on either ground.
See: When Airlines Extend Strike Defenses Beyond the Actual Strike
Security incidents
Security-related defenses cover a wide range of events, and their treatment varies significantly.
When it qualifies. Genuine security incidents including bomb threats, terrorist events, unauthorized intrusions requiring airport closure, and state-imposed security responses to specific external events can qualify. The event must be documented, and the connection to the specific flight must be established.
When it does not qualify. Routine security screening delays, general security atmosphere without a specific triggering event, and security responses to internal or airline-related matters do not qualify. A public announcement referring to a security incident is not the same as flight-specific primary evidence that the incident affected the flight in question.
Evidence required. Airlines must produce specific documentation, typically NOTAMs, airspace authority orders, or binding operational directives from aviation regulators. Press releases, ministry announcements, and news coverage establish that an event occurred but do not establish that the specific flight was affected.
Real-world example. The Garuda Indonesia case discussed in a previous article involved a cancellation cited as extraordinary due to a security incident and airspace closure in the region. The airline referenced a public event but failed to produce flight-specific primary evidence that the incident actually prevented the specific flight from operating. The case is currently pending judgment.
See: When Airlines Use Real Events to Justify Inadequate Evidence
Medical emergencies
Medical emergencies are treated more permissively than most other categories.
When it qualifies. A genuine medical emergency requiring diversion, unscheduled landing, or extended ground time for passenger care can qualify. The emergency must have actually occurred on the flight or immediately affected its operation.
When it does not qualify. Medical events on other flights, general medical concerns without a specific incident, and delays caused by the airline's own response inefficiency rather than the emergency itself do not qualify.
Evidence required. Airlines should be able to produce records of the specific medical event, including any diversion or extended ground time attributable to passenger care. Vague references to "a medical emergency" without documentation are not sufficient.
Reasonable measures overlay. Where a medical emergency causes a delay to a subsequent flight through aircraft or crew impact, the airline must show that reasonable measures could not have prevented the ripple effect.
Bird strikes and wildlife incidents
Bird strikes occupy a specific position in EU261 case law.
When it qualifies. Confirmed bird strikes affecting the airworthiness of the aircraft or requiring inspection that delays operations can qualify. The CJEU established in Pešková v. Travel Service (C-315/15) that bird strikes are extraordinary circumstances.
When it does not qualify. Reactionary delays from a bird strike on a previous sector require the airline to prove that reasonable measures could not have prevented the follow-on impact. Simply pointing to an earlier bird strike is not sufficient. Airlines must also produce specific documentation of the strike, the aircraft affected, the inspection or repair required, and the operational response.
Evidence required. Tail number of the affected aircraft, maintenance log entries, bird strike report, and rotation history are the standard evidence. Airlines that fail to produce this documentation are relying on the general acceptance of the defense category rather than on flight-specific proof.
Volcanic ash and natural events
Widespread natural events affecting entire regions of airspace are among the clearest extraordinary circumstances.
When it qualifies. Volcanic ash clouds requiring airspace closure, major seismic events affecting airport operations, and comparable large-scale natural disruptions qualify. These are typically documented by aviation authorities through region-wide restrictions.
When it does not qualify. Localized natural events that did not affect the specific route, events that ended before the disruption, and general references to regional weather patterns without specific documentation do not qualify.
Reasonable measures: the overarching test
Every category above is subject to the same additional requirement. Even where an event genuinely qualifies as extraordinary, the airline is only exempt from compensation if it can show that all reasonable measures were taken to avoid or mitigate the disruption.
Reasonable measures include repositioning aircraft, adjusting crew schedules, arranging alternative routing, using spare aircraft where available, and coordinating with other carriers or handlers. What counts as reasonable depends on the specific circumstances, but the airline bears the burden of showing what measures were considered and why they were insufficient.
Airlines almost never address reasonable measures in initial rejections. They cite the extraordinary event and treat that as sufficient. This is one of the most reliable ways to challenge extraordinary circumstances rejections. Even in cases where the underlying event genuinely qualifies, the reasonable measures analysis often reveals gaps in the airline's response that keep the compensation obligation in place.
A separate reference article covers the reasonable measures test in detail. For present purposes, the key point is that the extraordinary circumstances taxonomy is only half of the analysis. The reasonable measures overlay applies to every category and is often the more decisive factor in whether a defense actually succeeds.
See: How Claim Catalyst Handles Airline Resistance, Why Escalation Is Sometimes Required
Why airlines rely on this defense so heavily
The extraordinary circumstances exception is invoked far more often than it actually applies. This pattern is not accidental.
The defense produces a rejection that sounds technical and authoritative. It references a real regulatory provision. It cites events that are often real, even when the specific application to the flight is weak. And it exploits the significant knowledge gap between airlines, which have entire departments processing these defenses, and individual passengers, who typically encounter the regulation for the first time when their claim is rejected.
The result is that a substantial share of extraordinary circumstances rejections do not actually meet the legal standard. They rely on general acceptance rather than specific proof. Passengers who accept these rejections at face value abandon claims that would very likely succeed if pursued.
Bigger picture
The extraordinary circumstances exception is a narrow protection, not a broad shield. It was written to prevent airlines from bearing liability for genuinely unforeseeable events outside their control, not to provide a general defense against operational disruptions.
The taxonomy above shows how narrowly the exception actually operates when applied correctly. Weather has to be severe and specifically affect the flight. Technical issues almost never qualify. ATC restrictions require documentation. Strikes by the airline's own staff do not qualify. Security incidents require flight-specific evidence. Medical emergencies must actually affect the specific operation. Bird strikes require documented proof. Volcanic and regional natural events must specifically affect the route.
Across every category, the pattern is the same. The exception exists. It applies in limited, specific circumstances. It requires primary evidence, not general assertions. And it is subject to the reasonable measures overlay in every case.
Airlines that invoke the defense generically, without specific evidence and without addressing reasonable measures, are relying on passenger acceptance rather than on legal sufficiency. Understanding what the defense actually requires is often all it takes to see through a rejection that does not survive scrutiny.
See: What Claim Catalyst Actually Does For You
Frequently asked questions
What does extraordinary circumstances mean under EU261?
Extraordinary circumstances are events genuinely outside an airline's control that could not have been avoided even if all reasonable measures had been taken. The exception is set out in Article 5(3) of EU Regulation 261/2004 and has been interpreted narrowly by the Court of Justice of the European Union. Common categories include severe weather, air traffic control restrictions, third-party strikes, security incidents, and specific hidden mechanical defects. The event must actually affect the specific flight, be documented with primary evidence, and be paired with proof that reasonable measures were taken.
Do technical or mechanical issues count as extraordinary circumstances?
Almost never. The Court of Justice of the European Union established in Wallentin-Hermann v. Alitalia (C-549/07) that technical problems inherent to the normal exercise of an airline's activity are not extraordinary circumstances. This includes routine mechanical failures, component issues during normal operation, and maintenance-related delays. Very narrow exceptions exist for hidden manufacturing defects addressed by manufacturer safety directives, but these are rare and require specific documentation.
Are strikes always extraordinary circumstances?
No. Strikes by an airline's own staff, including pilots, cabin crew, and directly employed ground staff, do not qualify. Strikes by third parties such as air traffic controllers, airport security, or independent ground handlers can qualify, but the airline must still show that reasonable measures were taken. Mixed strikes involving both airline staff and third parties require fact-specific analysis.
What if the airline just cites the regulation without giving details?
A generic reference to Article 5(3) without specific evidence is not sufficient. Under EU261 case law, the airline must produce flight-specific primary evidence establishing that the extraordinary circumstance actually caused the disruption to the specific flight. Vague references to weather, technical issues, or operational restrictions without documentation are legally inadequate and can be challenged directly.
If you have received a rejection citing extraordinary circumstances, the taxonomy above provides a starting point for evaluating whether the defense actually holds up under the legal standard. Claim Catalyst evaluates extraordinary circumstances defenses against the specific evidentiary requirements of EU261 and the reasonable measures test. Start a claim or learn more about how airline defenses are challenged at every stage.