| Takeaway | Detail |
|---|---|
| A technical fault is not automatically an extraordinary circumstance. | Under CJEU C-411/23, the carrier must prove the defect was a hidden manufacturing fault, not a maintenance failure, before a delay past 3 hours triggers compensation. |
| You need maintenance logs and component history as proof. | Submit records showing the defective part was within its normal service life and routine checks followed manufacturer requirements to support a claim when arrival is more than 3 hours late. |
| Defective maintenance defeats the airline's excuse. | If the airline's own upkeep caused the fault, the extraordinary-circumstances exemption does not apply; passengers delayed more than 3 hours should request the repair and inspection records. |
| Build an evidence package before filing. | Gather error codes, manufacturer bulletins, and pre-flight inspection reports; if your flight landed more than 3 hours behind schedule, these documents can shift the burden back to the airline. |
Three hours is the threshold that transforms a delayed flight into a compensable claim under EU law. But after CJEU C-411/23, a technical breakdown does not automatically meet that bar. Most passengers—and many airlines—assume that any mechanical failure counts as an extraordinary circumstance. The Court's guidance says otherwise: a tech fault excuses delay only if the carrier proves it came from a hidden manufacturing defect, not from poor maintenance.
The practical consequence is about evidence. To win a delay claim after a technical fault, you need to submit the maintenance schedule, component logs, and manufacturer information showing the part had no known defect before departure. If the airline claims extraordinary circumstances, ask for their technical investigation. If the defect appeared during normal operation and the part was within its expected lifetime, the carrier remains liable after three hours.
Do not let the airline reframe an avoidable breakdown as an act of God. CJEU C-411/23 clarifies that the exemption is narrow. Collect the proof package early: inspection reports, error codes, and records of prior checks. That documentation is what turns a three-hour delay into a paid claim.
How It Works
CJEU C-411/23 is best understood as a burden-shifting engine operating on top of the Van Der Lans v KLM framework (Irish Legal News): a technical defect is an extraordinary circumstance only if it was unexpected and not detectable through routine maintenance. The practical consequence for travelers is that your submitted proofs do not need to diagnose the engine failure. They need to force the airline to open its maintenance records, because the airline—not you—carries the burden of proving the defect was unforeseeable. The conventional approach of filing first with the airline is not wasted money; the denial letter it produces becomes the document that pins the airline to its "technical fault" defense.
The mechanism runs in five steps. First, confirm the trigger: arrival at your final destination was delayed by more than 3 hours, since eligibility is measured on arrival delay, not departure time (Bobby Storke/Medium). Second, confirm jurisdiction: the flight was intra-EU, operated by an EU carrier, or, for a non-EU airline, departed from the EU (Bobby Storke/Medium). Third, calculate the bracket: an intra-EU flight between 1,500 km and 3,500 km delayed over 3 hours is worth 400 (Mighty Travels). Fourth, submit the delay certificate, booking confirmation, and a written request for the airline's maintenance log for the affected aircraft. Fifth, wait for the defense—if the airline invokes a tech fault, it must verify the total delay length (Mighty Travels) and show that the defect escaped routine maintenance. If the log shows a recurring issue, the defense collapses.
Key terms:
| Term | Definition | Why it decides C-411/23 outcomes |
|---|---|---|
| Refund vs. compensation | Refund returns the ticket price; compensation is a separate indemnity up to €600 (delayflight24) | An airline can refund and still owe compensation—they never offset |
| Extraordinary circumstances | Events outside the airline's control: political unrest (Norse Atlantic Airways), unruly passenger behavior, or a tech defect only if unexpected and not detectable in routine maintenance (Van Der Lans v KLM, Irish Legal News) | The airline must prove it; the passenger never disproves it |
| Arrival delay at final destination | The clock runs until you physically arrive at the final destination, including missed connections (Mighty Travels) | Sets whether the 3-hour threshold is crossed |
| Routine maintenance | The scheduled inspection baseline from Van Der Lans v KLM (Irish Legal News) | A defect a scheduled check would have caught is not extraordinary |
The edge case that sinks most claims is the missed connection. The airline must verify the length of the total delay to the final destination before computing compensation (Mighty Travels). If you reached your final destination less than 3 hours late, no claim exists regardless of the first leg's departure delay. File on the final arrival, not the departure board.
Concrete next action: when you file, add one sentence—"Please provide the maintenance log and technical records for the aircraft operating [flight number] on [date]." Under the Van Der Lans framework (Irish Legal News), the airline must demonstrate the defect was unexpected. A maintenance record showing a known or recurring issue converts your claim from a dispute into a formality, and that is the practical payoff of understanding the mechanism: you submit proof of where you arrived, and the airline must prove why its plane was unserviceable.
Key Factors to Consider
Consider a passenger traveling from Paris Charles de Gaulle to New York JFK, a route exceeding 3,500 km. The flight arrives at its final destination 4 hours and 20 minutes late due to a technical fault discovered just before departure. Under Regulation EC 261/2004, this arrival delay triggers the right to flat-rate compensation because it surpasses the 3-hour threshold for routes over 3,500 km.
The airline attempts to avoid payment by classifying the fault as an “extraordinary circumstance.” However, under the CJEU’s ruling in C-411/23 and the prior Wallentin-Hermann decision, technical defects stemming from defective maintenance do not qualify as extraordinary circumstances. Evidence shows the part had known wear and had not been replaced according to the maintenance schedule. Therefore, the airline is liable.
Applying Article 7’s distance bands, the compensation is 600 per passenger. That is the fixed amount for flights over 3,500 km when the delay exceeds 3 hours. The passenger receives this indemnity in addition to any retained ticket value, and the airline must pay within the EU261 timeframe. This outcome reflects the core principle: only truly unpreventable external events relieve the carrier.
Once C-411/23 is read alongside the Van Der Lans framework, a tech-fault claim collapses into three screens: component service life, root-cause control, and the airline's own diagnosis. The 600 payout for flights over 3,500 km that trip the 3-hour threshold covered above (Mighty Travels) is won or lost at those screens, not in the volume of documents you submit.
First screen: where the failed component sat in its service life. In Van Der Lans v KLM, the delay was caused by two defective components — a fuel pump and a hydro-mechanical unit — that had not exceeded their average lifetime (Irish Legal News). That detail is the boundary line for C-411/23: a part that fails inside its design life fits the profile of an unexpected technical defect, while a part that fails after its average lifetime points to a maintenance failure the airline controls. Pull the component's lifetime record before you file, because it decides the first screen.
Second screen: what the first cause actually was. Extraordinary circumstances are events outside the airline's control that are unpredictable and uncontrollable (Airlines & Extraordinary Circumstances: Compensation Guide). Extreme weather is a recognized extraordinary circumstance for Norse Atlantic Airways (Norse Atlantic Airways Delay and Cancellation Compensation), and weather delays, air traffic control ground delays, airport faults such as closed runways, and a passenger's own schedule mishaps generally do not qualify for compensation (Angelina Travels). If the airline's "tech fault" traces back to an ATC ground stop or a closed runway, the exemption survives and the claim dies at this screen.
Third screen: whose label is driving the denial. Passengers need to be aware that airlines may use extraordinary circumstances as a reason to deny a compensation claim (Mighty Travels). The status-quo myth to drop is that the airline's denial letter is final and that contesting it is a costly, unnecessary step. Under C-411/23, the denial letter is merely the airline's first label; what decides the case is whether the airline's own maintenance log corroborates that label. If the log shows the part failed inside service limits with no external trigger, you have the evidence path.
As for the numbers that matter, the table below keeps every figure tied to its named source.
| Figure | Role in the decision | Source |
|---|---|---|
| €600 | Compensation for flights over 3,500 km delayed past the 3-hour threshold covered above | Mighty Travels |
| 3,500 km | Distance band that triggers the €600 tier | Mighty Travels |
| 2 defective components | Fuel pump and hydro-mechanical unit in Van Der Lans, both within average lifetime | Irish Legal News |
| €0 | Monetary compensation owed when extraordinary circumstances are established | Airlines & Extraordinary Circumstances: Compensation Guide |
| 2 payments | Ticket reimbursement plus compensation on a cancelled flight | delayflight24 |
Run every tech-fault file through the three screens before drafting anything; if the component record, first cause, and airline log line up against the airline's label, the distance band above is the only remaining gate. That sequence is how you avoid building a file that dies at screen two.
Common Mistakes
The two common mistakes in a CJEU C-411/23 claim are both documentation errors, and both are avoidable. The first is accepting the airline's cause label as final. The second is building a proof package that stops at your own flight. Each one converts a recoverable claim into a forfeited one.
Pitfall 1: Treating "technical fault" as the end of the conversation. According to Irish Legal News, the CJEU held in Wallentin-Hermann (C-549/07) that technical defects caused by defective maintenance are not extraordinary circumstances and do not excuse compensation. Yet most passengers hear "technical fault" and assume the airline is off the hook. Consider a Norse Atlantic transatlantic departure: the carrier treats strikes as extraordinary circumstances, freeing it from paying compensation (Norse Atlantic Airways Delay and Cancellation Compensation). A traveler who hears the flight was delayed by a crew strike on the inbound rotation and does not file misses the legal question that matters — whether the strike actually caused the chain, or whether a maintenance defect was the root trigger. Wallentin-Hermann answers that question against the airline. The fix, per Mighty Travels, is to obtain written confirmation from the airline of the delay or cancellation — a letter, email, or printout from the airline's website — before leaving the airport, and to preserve the airline's stated cause verbatim. That written record is what lets you challenge the label later.
Pitfall 2: Documenting only your own flight, not the rotation. C-411/23 grew out of a clarification request asking whether an extraordinary circumstance can exempt an airline when it impacted the flight immediately preceding the disrupted flight. If your proof package starts and ends with your own flight's status, you cannot test that question. The logic extends to missed connections: a mechanical delay or cancellation that causes you to miss a connecting flight changes the compensation calculation, according to Angelina Travels, so the connection's boarding pass and rebooking record belong in your package. Article 5(3) of Regulation EC 261/2004 exempts a carrier only if the delay was caused by circumstances that could not have been avoided even if all reasonable measures had been taken (Irish Legal News). That reasonable-measures defense is testable only with the preceding flight's records: its written cause, its actual departure and arrival times, and the carrier's re-routing decisions. Without those, you are litigating with one hand tied.
The practical upshot: for a short-haul route under 1,500 km, the flat-rate compensation is 250 according to Mighty Travels — enough to justify thirty minutes of document collection. Submit the airline's written cause, the underlying technical records if a defect is suspected, and the preceding flight's status. That combination is what defeats the "extraordinary circumstances" defense and turns C-411/23 from abstract doctrine into a paid claim.
| Mistake | What the passenger does | What the proof package needs | Controlling authority |
|---|---|---|---|
| Trusting the airline's label | Reads "technical fault" and never submits a claim | Written confirmation of stated cause (letter, email, or website printout) per Mighty Travels | Wallentin-Hermann, C-549/07: defective maintenance is not extraordinary (Irish Legal News) |
| Stopping at your own flight | Collects only their own delay notice | Preceding flight's cause and status plus the carrier's reasonable-measures record | Article 5(3) reasonable-measures test; C-411/23 preceding-flight question |
Insider Tactics
The fastest path to a paid CJEU C-411/23 tech-fault claim is to stop litigating the abstract question of what "extraordinary" means and instead demand the airline's timestamped technical-log entry. A volcanic eruption is extraordinary, and a crew shortage is airline mismanagement (Myflyright); a technical fault sits between those poles, and the deciding document is often the maintenance entry the airline wrote before any passenger complained. This pivot costs nothing — you are not swapping a thorough case for a shortcut, but replacing guesswork with the one document the airline cannot contest.
The mechanism is simple enough to run from a phone. If the log identifies a component that had passed its scheduled service-life point, that is a maintenance-planning failure within the airline's control. If the log shows a sudden, unforeseeable failure, the airline still has to prove it could not have been detected — a much harder case when the entry was created contemporaneously, and a much easier one when the airline's "diagnosis" appears only after you file. The request costs nothing; the document decides the claim.
The edge case that exposes the tactic's value is a weather-blended tech fault. EL AL generally does not compensate delays caused by severe weather or political instability (EL AL Airlines Flight Delay Compensation Policy). Suppose your EL AL flight suffers a tech fault during a storm: the airline will blur cause and effect. Check the timestamps — if the technical log recorded the fault before the weather front reached the airport, the weather did not cause the delay; the tech fault did, and the extraordinary-circumstances defense collapses. Because the facts and circumstances of the specific flight determine claim eligibility (Bobby Storke), that timestamp sequence is the decisive fact.
Timing is the second lever, with two edges. First, file quickly — within days of landing, before the airline closes its internal irregular-operations classification — and request the technical log's creation date alongside the component's last scheduled replacement date. Second, read the response for what it does not say: a carrier with a genuine extraordinary circumstance documents it contemporaneously. A post-hoc write-up, or a refusal to produce the log, becomes evidence in your favor if you escalate to the national enforcement body.
One more layer: even when the extraordinary circumstance is valid — a hurricane, for instance — the airline still owes meals (Gatwick travel chaos guide). Submit meal receipts as a separate line item so the airline cannot package them into a single lowball settlement.
| Proof to demand | What it shows | Why it wins |
|---|---|---|
| Technical-log entry (timestamped) | Root cause and when the airline knew it | Contemporaneous entries defeat post-hoc extraordinary claims |
| Component service-life record | Scheduled replacement date vs. failure date | Past-due replacement reads as airline mismanagement, not extraordinary |
| Weather/NOTAM snapshot | Whether weather actually preceded the fault | A fault-before-weather order collapses the defense |
| Meal receipts | Out-of-pocket costs during the wait | Payable even when compensation is not, per the Gatwick rules |
Concrete next action: on arrival day, send the airline a short message requesting the technical log entry for the fault, its timestamp, and the component's last scheduled replacement date. If the entry predates the weather or shows a past-due service interval, you hold the proof that C-411/23 makes dispositive — and you get there without paying for anything except the flight you already lost.
Comparison
Put a C-411/23 tech-fault claim side by side with a passive filing, and the real spread is the difference between zero and 400. One documented denial put a £350 compensation claim to nothing: the airline invoked "extraordinary circumstances" from an earlier weather-delayed flight, even though the knock-on delay was not on the actual flight itself (Web search result: "Extraordinary circumstances" claimed for delay in earlier flight). A tech-fault claim meets the same label-shift, but the C-411/23 framework gives the passenger a documented rebuttal — and the rebuttal has a concrete euro value.
The side-by-side starts with the minimum Article 7 claim: airline, flight number, departure and arrival airports, and dates of travel (Mighty Travels). That conventional baseline is not a waste of money; it is the required foundation, and the money is lost only when the claim stops there. The proof-backed path adds the technical defect record. Payout is fixed by distance under Article 7 of the EU passenger-rights regulation (Irish Legal News): up to 1,500 km pays 250, and 1,500–3,500 km pays 400 (delayflight24). The long-haul tier is covered in Key Factors. The distance band is set by the original routing, so the airline's label changes neither the cap nor the calculation base — it only determines whether the passenger ever sees the money.
When each option wins: the passive filing wins in exactly one scenario — a short-haul claim where you submit the flight details first to test whether the airline concedes the operational character of the fault without further evidence. It stops winning the moment the airline answers with an "extraordinary circumstances" label. The proof-backed filing wins on every routing above 1,500 km, on every domino delay, and on any claim where the airline's response is a label unsupported by a technical record. It also forfeits nothing if the defense stands: refreshments and care obligations survive an extraordinary-circumstances ruling (Gatwick).
Missed connections are the sharpest edge case. The compensable delay is the difference between the originally scheduled arrival and the actual arrival of the final rebooked itinerary (Mighty Travels). Airlines frequently anchor the calculation to the first leg, which shortens the delay artificially. The documented £350 denial shows how a knock-on delay dies on an earlier flight's weather label; the proof-backed filing defeats that move by tying the technical defect to the aircraft that caused the missed connection.
| Claim scenario | Passive filing | Proof-backed filing | Winner |
|---|---|---|---|
| Tech fault, up to 1,500 km | €250 cap at risk if the airline labels the fault extraordinary (delayflight24) | €250 recovered with the defect documented (delayflight24) | Proof-backed — same payout, no reliance on concession |
| Tech fault, 1,500–3,500 km | €400 cap at risk on the same label (delayflight24) | €400 recovered with the defect documented (delayflight24) | Proof-backed — highest claim value |
| Missed-connection domino delay | £350 denied on an earlier flight's weather label (Web search result) | Delay from scheduled to actual arrival (Mighty Travels); payout per distance band | Proof-backed — defeats the first-leg anchor |
| Extraordinary circumstances upheld | €0 compensation; refreshments still owed (Gatwick) | €0 compensation; refreshments still owed (Gatwick) | Tie on compensation; proof-backed preserves the full record |
The comparison collapses to one question: does the airline's own record tie the delay to a technical defect? If yes, the proof-backed filing dominates every distance band — and the passive filing costs you exactly the compensation the record already justifies.
What to do next
| Step | Action | Why it matters |
|---|---|---|
| 1 | Request the component history log for the defective part from the airline's technical operations team, covering total service hours and normal service-life limits. | Proves the part was within its expected lifetime before departure, defeating a maintenance-neglect defence under CJEU C-411/23. |
| 2 | Get the pre-flight inspection reports and routine check sheets for the specific aircraft registration. | Shows checks followed manufacturer requirements, narrowing the airline's "hidden defect" argument. |
| 3 | Obtain the error codes and ACARS/ARINC fault messages logged for your flight from the airline's maintenance system. | Documents the exact technical breakdown and pins it to the flight that arrived more than 3 hours late. |
| 4 | Check the manufacturer's service bulletins (e.g., Airbus, Boeing, or engine OEM) for that part number for known defects issued before your departure date. | Demonstrates no prior known defect, shifting the burden to the airline to prove unforeseeability under the Van Der Lans v KLM framework. |
| 5 | File your EU 261 claim directly with the airline, then keep the denial letter. | The denial letter is the document that fixes the carrier to its "technical fault" defence, giving you leverage later. |
| 6 | If denied, submit the evidence package and demand the carrier's technical investigation report, citing CJEU C-411/23. | The airline — not you — bears the burden of proving the defect was a hidden manufacturing fault, not a maintenance failure. |
Frequently Asked Questions
For a Paris CDG to New York JFK flight that arrives 4 hours 20 minutes late because of a technical fault, what compensation amount applies?
The fixed compensation is 600 per passenger because the route exceeds 3,500 km and the delay surpasses the 3-hour threshold, and this is paid in addition to any retained ticket value.
What exact sentence should I add when filing a delay claim to force the airline to open its maintenance records?
Add this sentence: 'Please provide the maintenance log and technical records for the aircraft operating [flight number] on [date].'
If the airline's maintenance log for the affected aircraft shows a recurring issue with the failed component, what is the result?
The defense collapses because a maintenance record showing a known or recurring issue converts your claim from a dispute into a formality, and the airline remains liable.
What does a part that fails after its average lifetime indicate under the Van Der Lans framework?
A part that fails after its average lifetime points to a maintenance failure the airline controls, not an unexpected technical defect.
Can an airline refund my ticket and still owe me delay compensation?
Yes, a refund returns the ticket price while compensation is a separate indemnity up to 600, and an airline can refund and still owe compensation—they never offset.
My first leg left late, but I reached my final destination less than 3 hours after the scheduled arrival. Do I have a claim?
No, no claim exists if you reached your final destination less than 3 hours late, regardless of the first leg's departure delay, because eligibility is measured on arrival delay at the final destination.
Quick answers
| What must a carrier prove for a technical fault to qualify as an extraordinary circumstance under CJEU C-411/23? | The carrier must prove the defect was a hidden manufacturing fault, not a maintenance failure. |
| What records should passengers submit to support a delay claim after a technical fault? | Submit maintenance logs and component history, and records showing the defective part was within its normal service life and routine checks followed manufacturer requirements. |
| What happens if the airline's own upkeep caused the technical fault? | Defective maintenance defeats the airline's excuse; the extraordinary-circumstances exemption does not apply, and passengers delayed more than 3 hours should request the repair and inspection records. |
| What is the threshold that transforms a delayed flight into a compensable claim under EU law? | Three hours is the threshold that transforms a delayed flight into a compensable claim under EU law. |
| How does CJEU C-411/23 treat technical defects stemming from defective maintenance? | Technical defects stemming from defective maintenance do not qualify as extraordinary circumstances. |
Sources: Flyertalk, Flyertalk, Frequentmiler, Frequentmiler, Boardingarea
Also worth reading: How to get compensation for your delayed or cancelled flight: How to get compensation for · How to get paid for your delayed European flight under EC261 rules: How to get paid for · Delta Flight Delay Compensation What EU Regulation 261/2004 Means for Your Travel Rights: Delta Flight Delay Compensation What