Flight delayed by an IT failure or cyberattack: can you claim?
An IT outage does not decide compensation by itself. Identify the failed system, the cause and the airline’s response. A cyberattack or third-party failure can raise an extraordinary-circumstances defence, but that defence needs flight-specific proof.
Last reviewed: 2026-10-11
Check my flightApply the legal test before accepting a system-failure label
Article 5(3) requires proof that an extraordinary circumstance caused the disruption and that it could not have been avoided even with all reasonable measures. It is an exception to fixed compensation, not an exemption from every passenger-rights duty.
The Court’s test in C-549/07 Wallentin-Hermann requires two cumulative conditions: the event is not inherent in the airline’s normal activity, and it is beyond its actual control. Being unexpected, expensive or difficult to fix does not alone establish both conditions.
The Commission’s 2024 guidelines, section 5 distinguish that classification from the additional proof of causation and reasonable measures. Keep these questions separate when reading a refusal. The exception checklist explains the wider assessment.
Identify the airline’s own IT and any external service
Ask whether the problem concerned the airline’s reservation or check-in system, a shared airport platform, a communications service or an air traffic control system. Record who operated it and what the airline says failed. “IT problem” does not identify the event’s nature or origin.
For an ordinary failure within airline operations, examine how it relates to the airline’s normal activity and actual control. For a supplier or airport failure, examine those same conditions. The supplier’s name or separate ownership is not a substitute for that assessment. Ask which dependency stopped this flight and what alternatives were available.
The CAA’s 2021 ADR issues list includes both airline and airport system failures. It expressly includes extraordinary and non-extraordinary issues. That list concerns the normal dispute-assessment process; it does not classify every listed outage as compensable or exempt.
A cyberattack needs evidence of the event and its effect
The CAA’s compensation guidance identifies security risks, sabotage and terrorism among possible extraordinary circumstances. That does not turn every software error into a security incident or every claimed cyberattack into an automatic refusal.
Ask the airline to explain the actual incident, why it was outside its normal activity and control, and how it caused your delay or cancellation. An official incident notice can help establish that an event occurred. It may still say nothing about your particular aircraft, passenger booking or recovery decisions.
Do not infer a different cause without evidence. Preserve the airline’s wording and distinguish a confirmed external attack from an unexplained outage. A headline describing disruption across an airport network is not a judgment about each passenger’s entitlement.
September 2025 Collins Aerospace: what the official statement confirms
On 20 September 2025, the UK National Cyber Security Centre published a statement about the incident affecting Collins Aerospace. It said it was working with Collins Aerospace, affected UK airports, the Department for Transport and law-enforcement colleagues to understand the impact.
That statement confirms the reported incident and official response. It does not decide EU261 or UK261 compensation, list your flight as affected, or establish your arrival delay. Keep a separate record of what your operating airline told you and when.
If your claim concerns that event, explain the connection between the affected service and your flight. Keep any airport notice, airline message and alternative offer. A later unrelated delay should not be attributed to the incident solely because it occurred during the same period.
Ask what the airline did to avoid or reduce the disruption
The CAA’s current industry guidance calls for a case-specific assessment of the cause and airline response. The Commission’s guidelines discuss measures appropriate to the situation and available resources, without requiring intolerable sacrifices.
Ask for the timeline of restrictions, restoration and recovery. Relevant questions can concern available manual processing, alternative arrangements or rerouting. These are evidence questions, not a claim that every airline must use an unsafe workaround or the same backup in every case.
If an earlier affected flight is blamed, ask how that disruption reached your own journey. The knock-on delay guide addresses the causal link and later decisions. System restoration and your eventual arrival are different points in the timeline.
Keep care, refund and rerouting requests separate
In C-12/11 McDonagh, extraordinary circumstances did not release the airline from its applicable care duties. An IT incident that defeats fixed compensation therefore does not automatically remove meals, necessary accommodation or other assistance due under the relevant conditions.
For a covered cancellation, the Regulation’s Article 8 provides the refund and rerouting choices. For a delay, the refund route has its own conditions; the current EU261 waiting threshold is 5 hours if you choose not to travel. A ticket refund and fixed compensation answer different questions.
Ask for assistance before arranging it yourself where possible. Keep contact attempts, offers and itemised receipts for necessary costs. Use the hotel, meal and expense guide. Choosing a refund or later travel can affect ongoing care, so retain the choice you made.
Record your own disruption, not just the incident date
- Keep the booking, flight date, route and operating airline.
- Save the planned arrival and relevant actual-arrival evidence.
- Keep any cancellation notice and offered replacement timings.
- Retain the airline’s cause explanation and incident references.
- Record assistance, alternative offers, expenses and payments already received.
For a covered delay claim, the current EU261 threshold is 3 hours at final arrival, subject to the remaining conditions. The arrival-delay guide explains why landing time and doors-open arrival are different. A collected airport report does not prove the outage cause.
Owed’s check estimates eligibility from the supplied facts. It does not investigate a cyberattack or decide who controlled the failed system. Do not describe an uncertain security incident as a confirmed ordinary technical fault merely to obtain a favourable estimate.
Submit a focused request and choose the appropriate dispute route
Use the official airline claim directory. State the disrupted flight and remedy, attach relevant evidence and request the missing explanation. Keep the submission confirmation and complete response. A generic outage label is the point to clarify, rather than a reason to invent a different cause.
If unresolved, consult the refusal guide and the applicable EU or UK complaint procedure. UK industry guidance is not a court judgment, and post-2020 EU judgments are not automatically binding on UK courts. The UK ADR guide distinguishes the available routes. Owed does not submit or argue the claim for you.
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)
- European Commission: 2024 guidelines, section 5 on extraordinary circumstances
- Court of Justice, C-12/11 McDonagh v Ryanair (2013)
- UK Civil Aviation Authority: compensation and extraordinary circumstances
- CAA: consumer-law guidance, extraordinary circumstances and the airline’s response
- CAA CAP1324A, February–March 2021: issues assessed through the normal ADR process
- NCSC statement, 20 September 2025: incident affecting Collins Aerospace
- European Union (Withdrawal) Act 2018, section 6: CJEU decisions in UK courts
This page is general information, not legal advice. Owed is self-service software and not a law firm.
IT outage compensation questions
Does an airline’s own IT outage always lead to compensation?
Do not decide from the label alone. Assess the event’s nature, normal airline activity, actual control, flight-specific cause and reasonable measures.
Does a cyberattack automatically remove every passenger right?
No. Fixed compensation and applicable care, refund or rerouting duties need separate assessments.
Does using a third-party system automatically make the failure extraordinary?
No. Supplier ownership alone does not replace the legal tests or evidence of what happened to the specific flight.
Does the NCSC Collins statement prove my flight qualifies or is exempt?
No. It confirms the incident and official response, not the outcome of an individual compensation claim.