British Airways technical fault and IT outage: when compensation is due
Reviewed on 10 August 2026. A routine British Airways aircraft defect, maintenance problem or airline-controlled IT failure is not automatically an extraordinary circumstance. If it causes a covered arrival delay of at least three hours or a short-notice cancellation, fixed UK261 or EC261 compensation can be due. BA must prove any genuinely external exception and its reasonable response.
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 words "technical issue" identify a subject, not a legal defence. Ask what failed, who controlled it, when it affected the flight and what recovery action was available.
Classify the technical event
| Event | Starting analysis |
|---|---|
| Component failure found during normal operation | Usually inherent in airline activity |
| Maintenance delay or unavailable spare | Ordinarily operational |
| Manufacturer reveals a hidden fleet-wide safety defect | Can be extraordinary |
| Sabotage or terrorism damages aircraft | Can be extraordinary |
| BA booking, check-in or crew system fails | Examine airline control and resilience |
| Airport-wide infrastructure outage | External origin may qualify, subject to mitigation |
| Third-party supplier failure | Supplier status alone does not settle inherency or control |
Do not assume that unexpected equals external. Aircraft systems and operational software sometimes fail; managing ordinary failure is part of running an airline.
Routine aircraft faults
The Court of Justice held in Wallentin-Hermann that technical problems revealed during maintenance, or caused by failure to maintain, do not in themselves amount to extraordinary circumstances. A carrier may show an exception where a manufacturer or authority reveals a hidden defect affecting aircraft already in service, or where sabotage or terrorism causes damage.
Ask BA for the defect category, discovery time, maintenance action and release time. A general statement that safety required cancellation does not answer whether the underlying problem was routine. Safety always comes first, but lawful cancellation for safety and entitlement to compensation can coexist.
Spare aircraft availability is part of reasonable measures, not an automatic requirement to keep an aircraft at every station. BA should nevertheless explain its network options, especially at a principal operating airport, and why rerouting or an aircraft swap was not feasible.
Airline IT failures
An IT incident can affect check-in, flight planning, crew allocation, baggage, boarding or customer communication. The legal result depends on system ownership, origin and safeguards. BA should say whether the failure sat within its infrastructure, an airport common-use platform, telecommunications provider or a malicious external attack.
Ordinary software defects, capacity failure, maintenance errors and inadequate redundancy are closely connected to airline operations. Outsourcing a platform does not necessarily make failure extraordinary; the supplier may perform functions integral to BA's service.
A sophisticated external cyberattack or nationwide infrastructure event can lead to a different conclusion. Even then, BA must show the causal path to the particular flight and reasonable contingency measures. Restoration time, manual processing, passenger prioritisation and rerouting are relevant.
Historic BA outages do not prove the cause of a current disruption. Use the present incident record rather than arguing from press reports about another year.
Knock-on technical delay
The aircraft may arrive late from an earlier sector because engineers addressed a defect elsewhere. Request the tail rotation, defect timing and delay carried into the disputed service. If BA fixed the issue but then added hours through crew timeout or aircraft allocation, those later causes require separate treatment.
Suppose a routine hydraulic indication delays an inbound flight by two hours. After arrival, BA has no replacement crew and the next departure reaches its destination five hours late. The claim should analyse both engineering and crew-planning periods, not accept one technical label for the whole result.
An earlier extraordinary hidden defect can propagate, but reasonable measures become more important as time and distance from the original event increase.
Coverage and amount
UK departures normally use UK261. BA-operated arrivals into the UK, and BA-operated arrivals into the EU, can also fall under UK rules. EU departures use EC261. A BA code on a partner-operated flight requires the partner's facts and nationality.
The normal bands are GBP 220/350/520 or EUR 250/400/600. Long UK261 journeys arriving between three and four hours late ordinarily use GBP 260. Measure final door opening on a through booking and calculate distance by the direct first-to-final route.
The BA delayed-flight guide covers timing, while the BA amount guide explains long-distance reductions.
Rights during repairs or system recovery
Care is due at the applicable waiting threshold even before BA determines compensation. Ask for food, drink, communications, hotel accommodation if necessary and transport to the hotel. If the airline cannot arrange them, retain itemised receipts for reasonable alternatives.
After cancellation, choose refund, earliest rerouting or later travel. A passenger does not need to wait for the original aircraft to be repaired when lawful earliest rerouting on another reasonable service is available. Document requests for partner or competitor flights.
At a five-hour delay, abandoning the journey for a refund is a separate decision. Choosing repayment ends transport, but a fixed claim can still exist if the technical cause and threshold qualify.
Evidence and challenge wording
Save BA messages, the engineering explanation given at the gate, screenshots of system errors and records of other offered flights. Note whether check-in failed for all airlines or only BA. Keep the original itinerary and final arrival time.
In a claim, avoid demanding proprietary maintenance documents without focus. Ask for the defect class, whether a manufacturer or authority issued a safety notice, the event timeline and mitigation. For IT, request system owner, failure source and contingency action.
If BA rejects with "unexpected technical fault", respond that unexpectedness alone does not establish extraordinary circumstances under the established test. Ask it to address inherency, control and reasonable measures. The BA rejected-claim page provides an escalation structure.
FAQ
Is every unexpected BA aircraft fault compensable?
Not automatically, but routine technical problems are generally inherent and do not by themselves establish the extraordinary-circumstances defence.
Can a hidden manufacturing defect excuse BA?
It can where a manufacturer or competent authority reveals a defect affecting aircraft already in service. BA still needs to prove causation and mitigation.
Does an outsourced IT supplier make the outage external?
Not necessarily. If the service is integral to airline operations, outsourcing alone does not settle inherency or actual control.
Can I obtain meals while engineers repair the aircraft?
Yes when the relevant care threshold is met. Assistance is independent of the eventual decision on fixed compensation.
What evidence matters for an IT disruption?
Save error screens, BA notices, airport information, check-in attempts, alternative offers and the final arrival record. Ask BA to identify the failed system.