Etihad Airways technical fault: is compensation still owed?
Airlines cite a technical fault more often than any other excuse for a delay or cancellation, and it is also the excuse most frequently overturned once properly challenged. Courts across Europe have consistently held that a technical fault, however inconvenient or unexpected it felt to the passengers affected, usually does not excuse an airline from paying fixed compensation.
Free eligibility check
Check your case in the form
Enter your route, date and type of disruption. We will check whether your case qualifies for a claim under EU 261/2004 or UK261.
What happened to your flight?
Claim up to €600 for a delayed or cancelled flight.
Choose the situation that applies to your flight:
The starting position: technical problems are normal business risk
Modern aircraft are made of thousands of components that require ongoing maintenance and occasionally fail without warning. Precisely because this is an inherent, foreseeable part of running an airline, the prevailing legal position is that a technical fault is not, by itself, an extraordinary circumstance. Etihad, like any carrier, generally remains liable for fixed compensation when a technical fault causes a qualifying delay or cancellation.
The narrow exception: a genuinely hidden defect
An exception exists for faults traced to a hidden manufacturing or design defect that the manufacturer, and reasonably diligent maintenance, could not have discovered beforehand. This is a demanding, narrow standard, requiring specific evidence about the nature of the defect and why it was genuinely undiscoverable in advance — a general statement that a part "unexpectedly failed" does not meet it.
What a vague rejection looks like, and why it fails
A rejection stating only that your flight was delayed "due to a technical issue" or "for engineering reasons," without identifying the specific fault, does not meet the evidentiary standard Etihad needs to clear. Push back and ask for the precise nature of the fault, when it was discovered, and why it could not have been anticipated through normal maintenance — a response that cannot answer these questions in detail is a sign the technical-fault defence does not actually hold up.
Sabotage and third-party interference
A different, similarly narrow exception can apply where damage results from sabotage or a similarly unforeseeable act by someone outside the airline's control, rather than an internal maintenance issue. Like the hidden-defect exception, this requires specific evidence rather than a general assertion, and remains uncommon in practice.
What happens if the fault occurred on an earlier flight that day?
A technical fault discovered on an earlier rotation of the same aircraft, causing knock-on delays to your later flight, is analysed the same way as if it had occurred on your own flight directly — the underlying classification does not change simply because the fault surfaced earlier in the day on a different sector.
Practical assistance continues regardless of the outcome
Whether or not a technical fault ultimately qualifies as an extraordinary circumstance, the right to meals, refreshments and, where an overnight stay becomes necessary, hotel accommodation continues throughout the disruption. This entitlement is entirely separate from the fixed compensation question.
A worked example
Etihad cancels a flight from Milan, citing a technical fault discovered during pre-flight checks. Under the prevailing legal standard, a routine technical fault of this kind is treated as ordinary business risk rather than an extraordinary circumstance, so fixed compensation remains owed, provided the notice given fell short of the fourteen-day threshold that would otherwise remove it. Had Etihad instead demonstrated the fault traced to a specific, previously undiscoverable manufacturing defect confirmed by the aircraft manufacturer, the outcome could genuinely differ.
Why airlines still cite technical faults so often
Given how frequently the technical-fault defence is ultimately unsuccessful once challenged, it might seem surprising airlines continue to cite it as often as they do. In practice, some passengers simply accept the first explanation given without pushing back, which means a defence with a fairly low success rate in a properly contested case still gets used routinely as the default first response to a claim.
What documentation might Etihad rely on to support this defence?
A genuine hidden-defect defence would typically need to reference specific manufacturer communications, an airworthiness directive, or a formal engineering finding identifying the fault as previously undiscoverable. A rejection that cannot point to anything beyond an internal, unverifiable assertion is considerably weaker than one backed by this kind of specific, checkable documentation.
FAQ
Does a technical fault usually excuse Etihad from paying compensation?
No. The prevailing legal position treats routine technical faults as normal business risk, not an extraordinary circumstance.
When can a technical fault actually excuse compensation?
Only in narrow cases involving a genuinely hidden manufacturing or design defect, or sabotage, supported by specific evidence.
What should I do if Etihad's rejection just says "technical issue"?
Ask for the specific nature of the fault, when it was found, and why it could not have been anticipated through normal maintenance.
Does it matter if the fault happened on an earlier flight that day?
No. The same classification standard applies regardless of which specific flight in a chain of rotations the fault first appeared on.
Am I still owed meals or a hotel if the technical fault is accepted as extraordinary?
Yes. Practical assistance during the disruption is unaffected by how the fixed compensation question is ultimately resolved.
Does the age of the aircraft matter?
Not directly. Both a newer and an older aircraft can experience a technical fault that falls under the normal-business-risk standard, and neither the presence nor the absence of a specific aircraft's age is, by itself, decisive either way. What matters is the specific, documented nature of the fault itself, not general assumptions about how reliable a particular aircraft type or age tends to be.
What if a technical fault leads to a diversion rather than a delay?
The same underlying classification standard applies whether the technical fault causes a delay, a cancellation, or an unplanned diversion to a different airport. The type of disruption that results does not change whether the fault itself qualifies as ordinary business risk or a genuine, narrow exception.
Keeping your own notes on what you were told
Write down, as close to the moment as possible, exactly what any airline staff told you about the cause of the delay, including any specific detail they mentioned about the fault. This kind of contemporaneous note can be useful later if Etihad's eventual written response offers a different or vaguer explanation than what was said at the gate.
A final practical tip
Photograph any visible information boards or gate announcements referencing the cause, alongside your written notes, for a more complete record.