SAS technical fault compensation
A routine technical fault discovered during normal SAS operation or maintenance is generally not an extraordinary circumstance, so a covered three-hour arrival delay or qualifying cancellation can still produce EUR 250, EUR 400 or EUR 600. SAS may have a defence for a truly external or exceptional event, such as a hidden fleet-wide manufacturing defect newly disclosed by the maker, sabotage or certain outside impacts. The airline must prove the actual cause and reasonable measures, not merely write "technical reasons."
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:
Passenger safety always comes first. The legal question is not whether SAS should have flown an unsafe aircraft, but who bears the financial consequence of the resulting disruption.
Technical-cause table
| Stated cause | Ordinary EC261 direction | Evidence needed |
|---|---|---|
| Component failure arising in normal service | Usually within airline activity | Defect timing, repair and effect on the flight |
| Fault found during scheduled maintenance | Usually within airline responsibility | Maintenance chronology and reasonable recovery steps |
| Unexpected defect despite proper maintenance | Still not extraordinary merely because it was unforeseen | Nature and origin of the defect |
| Manufacturer reveals a hidden fleet defect | Can be extraordinary | Manufacturer notice and affected aircraft link |
| Sabotage or deliberate external interference | Can be extraordinary | Flight-specific external event evidence |
| Bird strike or airport equipment impact | Requires separate case-law analysis | Exact impact, resulting checks and avoidable delay |
Do not diagnose the aircraft from a gate announcement. Ask for a sufficiently specific explanation without demanding confidential engineering records.
Wallentin-Hermann remains the starting point
In Wallentin-Hermann, the Court of Justice explained that technical problems revealed during maintenance or caused by failure to carry out maintenance are not extraordinary as a general rule. An event must not be inherent in normal carrier activity and must be beyond the carrier's actual control to satisfy the exception.
The fact that SAS complied with maintenance rules is relevant to reasonable conduct but does not automatically convert an operational defect into an extraordinary event. Nor does rarity or unpredictability alone settle the legal test.
A hidden manufacturing defect affecting the fleet, sabotage or terrorism can stand differently because its origin is external to ordinary airline operation. The SAS rejected-claim guide shows how to ask for the event and causal evidence.
Repairs and reasonable measures
Even if the initiating event is extraordinary, SAS must demonstrate that reasonable measures could not avoid the qualifying arrival delay or cancellation. Relevant facts include when the defect became known, whether another aircraft or rerouting was realistically available, how quickly qualified maintenance could act and whether the problem continued after repair.
The regulation does not require SAS to keep an unlimited spare fleet or incur intolerable sacrifice. It does require a concrete account. A statement that "safety comes first" explains why the aircraft did not depart but not why no reasonable alternative could limit the passenger impact.
If a replacement aircraft was available but arrived much later because of ordinary rotation choices, separate the original technical event from subsequent operational delay.
Knock-on technical disruption
SAS may say that the aircraft suffered a fault on an earlier flight and reached the passenger's airport late. Ask for the rotation, fault location, repair completion, scheduled recovery time and alternatives. An earlier event can remain causally relevant, but it does not excuse every later sector indefinitely.
The more time and operational opportunities existed between the first event and the claimed flight, the more important the reasonable-measures evidence becomes. Conversely, an immediate next sector using the same aircraft may have a clearer causal link.
Do not confuse a previous partner-operated flight with an SAS rotation. Identify who controlled the aircraft and which legal operator cancelled the passenger's service.
Compensation calculation
For delay, measure arrival at the protected final destination when a door opens. One-ticket connections are assessed to their last affected endpoint. The standard distance bands are EUR 250, EUR 400 and EUR 600 per eligible passenger.
Cancellation also depends on notice and replacement timing. A technical cause within SAS's activity does not remove the passenger's refund or rerouting choice. Involuntary denied boarding due to an aircraft substitution can require analysis of whether the passenger was refused for commercial capacity reasons or a justified safety ground.
The SAS compensation overview links event type, distance and remedy.
Aircraft change and cabin consequences
A substitute aircraft can solve the delay while creating a lower cabin, missing paid seat or reduced service. These are separate claims. A true downgrade to a lower travel cabin can trigger reimbursement of 30, 50 or 75 percent for the affected segment. Losing a preferred seat while remaining in the same cabin normally calls for the seat fee, not a statutory downgrade percentage.
Keep the original and replacement cabin, booking class and seat receipt. The technical reason for the substitution does not automatically remove the price-based remedy.
Care remains separate
During a covered wait, SAS should provide reasonable meals and refreshments. An overnight delay can require hotel accommodation and airport-hotel transport. If assistance is absent, use proportionate options and retain itemised receipts.
Care does not depend on proving SAS negligence and can survive an extraordinary-circumstances defence. Likewise, a five-hour departure delay can allow the passenger to abandon a pointless journey and seek reimbursement.
Evidence and claim wording
Preserve the original itinerary, operated-by statement, all notices, aircraft-change information, replacement flights and final arrival. In the claim, quote SAS's exact technical wording. Ask for the defect category, when it was identified, its connection to the aircraft and the reasonable measures taken.
Avoid alleging poor maintenance without evidence. State instead that an ordinary technical defect is normally inherent in airline activity and request a reasoned application of the extraordinary-circumstances test. List each passenger and keep expenses separate.
The legal analysis was reviewed on 26 August 2026. It applies current EC261 case law; the adopted future EU reform is not yet operative.
FAQ
Is an unexpected SAS fault automatically extraordinary?
No. Unforeseen technical problems arising during normal operation generally remain within airline activity unless their origin is genuinely exceptional and external.
Does proper maintenance remove compensation?
Not by itself. Compliance can support SAS's conduct, but the cause must still satisfy the extraordinary-circumstances test.
Can a hidden manufacturer defect be extraordinary?
Yes, when SAS proves a newly disclosed defect affecting the relevant fleet or aircraft and shows reasonable measures could not avoid the disruption.
Is a replacement aircraft proof that no compensation is due?
No. It is one mitigation step; final arrival, cancellation timing, cause and any cabin loss still require assessment.
Can I claim meals during a technical delay?
Reasonable care can be due during the wait independently of the final decision on EUR 250-600.