Technical fault flight compensation: check the fault, not just the label.
An aircraft technical problem does not automatically let the airline refuse compensation. Under EU261, the nature and origin of the problem matter; ask the airline to explain the event it relies on.
Last reviewed: 2026-10-11
Check my flightOrdinary operating problems can still support a claim
In C-549/07 Wallentin-Hermann, the Court explained that technical problems encountered in normal aircraft operations are not automatically extraordinary. Problems found during maintenance, or resulting from a failure to maintain the aircraft, do not establish the exception by themselves. Meeting minimum maintenance requirements does not, by itself, establish that all reasonable measures were taken either.
The practical question is what caused the fault and whether it belongs to normal operating activity. A response that only says technical issue or flight safety does not answer that question. Ask the airline to identify the problem and explain why it falls outside its normal activity and actual control.
Unexpected does not automatically mean extraordinary
In C-257/14 van der Lans, the Court considered a technical problem that arose unexpectedly, was not attributable to poor maintenance and was not detected during routine checks. Those features did not make that problem extraordinary. If the airline relies only on the fault being unforeseen, ask it to explain what distinguishes your case from an ordinary component failure. This does not mean every unexpected event has the same outcome.
Some events can fall outside normal operations
Wallentin-Hermann discusses examples such as a hidden manufacturing defect affecting flight safety, or damage from sabotage or terrorism. The airline still needs to establish the facts relevant to Article 5(3). Do not treat a routine failed part as a hidden manufacturing defect without evidence. Ask whether a manufacturer or authority identified a wider defect and how that event affected your flight.
UK technical-fault claims: Huzar v Jet2
In Jet2.com Ltd v Huzar, [2014] EWCA Civ 791, the England and Wales Court of Appeal rejected the extraordinary-circumstances defence for an unforeseen wiring defect. Proper inspection and maintenance could not have predicted that fault. Its unforeseeability did not make this ordinary operating problem extraordinary. The nature and origin of the problem mattered, rather than whether the airline was at fault for missing it.
Huzar is a domestic Court of Appeal judgment, rather than a CJEU ruling. The CAA’s current technical-fault guidance discusses it alongside the exceptions for hidden manufacturing defects, sabotage and terrorism. It does not establish that every technical event qualifies for compensation. Ask for the actual cause and evidence, and check the remaining claim conditions.
For UK261, use the applicable UK regulation and complaint route. The UK261 guide explains coverage and how UK courts treat EU judgments. A later EU ruling does not automatically change UK law.
Free technical-fault reply paragraph
Use this only for an EU261 claim where the airline refused because of a technical problem. Keep your case reference and replace the brackets. This paragraph asks for evidence; it does not state that your case must succeed.
Re: [case reference], flight [flight number] on [date] Your response refers to [the airline's description of the technical problem]. Please identify the nature and origin of the fault and explain why you consider it extraordinary under Article 5(3) of Regulation (EC) No 261/2004. Please explain how the circumstances differ from ordinary technical problems considered in C-549/07 Wallentin-Hermann and C-257/14 van der Lans, and provide supporting evidence of the event and measures taken.
The rest of your flight facts still matter
An ordinary fault does not establish every condition for compensation. Check route coverage, the operating airline, your disruption and the relevant timings. For a cancellation, keep the notice and replacement offers. For a delay, distinguish a landing report from doors-open arrival. The coverage guide explains the scope of the check.
Preserve the airline's original reason, including any later changes. A technical-fault message followed by a weather explanation gives you a question to ask; it is not conclusive proof that the later answer is false. Keep records rather than relying on a remembered phone conversation.
Choose the next step after the airline replies
Find the official claim entry before supplying booking details. Send your follow-up through the airline's official claim channel and keep its confirmation. The airline guides help you find that entry. If the airline maintains its refusal, use the rejected-claim guide to check the complaint route. You do not need to buy a pack to use this paragraph.
For a UK261 flight, check the UK judgment and guidance above and your complaint route before sending a legal argument. The UK261 guide explains the starting point. Keep any claim for expenses separate from fixed compensation and retain your receipts.
Check your flight
Free, no account. The result is an estimate: the airline decides whether to pay.
Sources
- Regulation (EC) No 261/2004 on EUR-Lex
- Regulation (EC) No 261/2004 as it applies in the UK, on legislation.gov.uk
- Court of Justice, C-549/07 Wallentin-Hermann (2008)
- Court of Justice, C-257/14 van der Lans v KLM (2015)
- England and Wales Court of Appeal: Jet2.com Ltd v Huzar, [2014] EWCA Civ 791
- UK Civil Aviation Authority: compensation and extraordinary circumstances
This page is general information, not legal advice. Owed is self-service software and not a law firm.
Questions about technical-fault refusals
Is every technical fault eligible for compensation?
No. Ordinary faults do not automatically excuse an airline, but exceptional events and the other conditions of your claim still need to be assessed.
Does an unforeseen fault count as extraordinary?
Not automatically. In C-257/14 van der Lans, the unexpected technical problem considered by the Court did not qualify simply because routine checks had not detected it.
What evidence should I ask for?
Ask for the nature and origin of the fault, its connection to your flight, supporting evidence for the claimed exception, and the measures taken.
What if the airline refuses again?
Keep the correspondence and check the relevant complaint or dispute-resolution route. Use the rejected-claim guide to organise your next step. Rejected-claim guide