SAS rejected your compensation claim: how to challenge it
A rejection from SAS is not conclusive when it relies on a vague phrase, the wrong operator, an incorrect final-arrival calculation or an unsupported extraordinary-circumstances defence. Match the refusal to the ticket and chronology, ask for flight-specific facts, and reply to the existing case with the missing evidence. Keep fixed compensation separate from refund, rerouting and care because a valid defence to one remedy does not remove all the others.
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:
Read the decision line by line before sending a generic objection. A focused reply is more useful than opening duplicate cases or demanding internal safety documents that are unnecessary to decide the legal test.
Diagnose the refusal
| SAS reason | What to verify | Productive response |
|---|---|---|
| Flight outside EC261 | Departure, destination and actual operator | Provide the complete route and operated-by evidence |
| Arrival under three hours | Original final destination and door-opening time | Submit the one-ticket itinerary and contemporaneous timestamps |
| Notice given early enough | Date the cancellation reached the passenger | Preserve the first message and replacement timetable |
| Extraordinary circumstances | Event, causal link and reasonable measures | Request a flight-specific chronology and available alternatives |
| Passenger did not present on time | Check-in, gate and document records | Provide boarding pass, app events and witness or airport evidence |
| Claim already paid or settled | Passenger count, amount and scope | Compare the transfer or voucher with each requested remedy |
Do not answer every possible argument. Identify the factual or legal premise SAS used and correct that premise with the strongest records.
Check the operating carrier first
An SK number can appear on a flight operated by a partner. If the rejection says SAS was not the operating carrier, inspect the original e-ticket, boarding pass and airport record. The conclusion may be correct even when SAS sold the ticket. Direct fixed compensation to the airline that performed or intended to perform the affected sector.
The reverse also occurs: a partner sold the itinerary, but SAS actually operated the disrupted flight. In that case, attach the operated-by wording and explain why marketing or ticketing identity does not transfer operational liability.
SAS Connect, SAS Link and wet-lease arrangements deserve exact entity records. The SAS operating-carrier guide provides a document-based method for choosing the respondent.
Recalculate the protected delay
SAS may refer to touchdown or arrival at an intermediate airport when the passenger relies on a later final destination. For a single protected booking, compare the original arrival at the last affected destination with the time passengers could leave the replacement aircraft there.
Show one PNR, one ticket and the missed-connection sequence. State each scheduled and actual time. If the bookings were separate, do not combine them merely because the routes fit together. Correcting an overstated itinerary can preserve a valid claim on the first flight even when the onward loss belongs elsewhere.
For a threshold dispute, offer more than one contemporaneous source and ask which SAS operational timestamp was used. The three-hour SAS analysis explains door opening and connecting journeys.
Test an extraordinary-circumstances defence
SAS must establish both an extraordinary event and that the qualifying disruption could not have been avoided through reasonable measures. A label such as weather, air traffic control, security or airport restrictions identifies a category, not the complete proof.
Ask where and when the event occurred, how it affected this aircraft, whether the restriction applied at the relevant time, and what rerouting or recovery options were considered. A prior rotation event needs a direct causal chain and evidence that SAS could not reasonably absorb or mitigate the knock-on effect.
Routine defects encountered in airline operation generally are not extraordinary. A newly revealed manufacturing issue affecting a fleet, external collision or sabotage can be different. Internal labour disputes also require care: the Court of Justice ruled in Airhelp v SAS that a lawful strike by the carrier's own staff over employment demands was not outside normal airline activity merely because collective action was involved.
Reasonable measures are a second requirement
Even when the trigger was external, SAS should explain why reasonable steps could not avoid the final delay. Alternatives can include timely rerouting on its own services or another carrier, deploying realistically available resources, or reorganising the rotation. The regulation does not require an intolerable sacrifice, but a bare assertion that no action was possible is incomplete.
Use contemporaneous availability rather than today's search results. Screenshots of seats, trains or partner services at the time can support a challenge. Explain why the route was comparable and achievable, accounting for airport transfer, documents and connection time.
Preserve remedies that survive the refusal
A successful extraordinary-circumstances defence normally concerns the fixed EUR 250-600 payment. It does not automatically extinguish reimbursement after cancellation, the five-hour delay choice, earliest rerouting or reasonable care while waiting.
If SAS rejected an entire submission with one paragraph, restate each head of claim. Attach itemised meal, hotel or transfer receipts and identify the period of required care. Ask for the ticket repayment calculation separately. Baggage claims follow Montreal rules and should not be decided as EC261 compensation.
Write the response
Quote the case reference and the precise reason under challenge. Give a short chronology, then attach the evidence that changes the conclusion. Request a reasoned reconsideration and specify the amount or remedy sought for each passenger.
Avoid unsupported allegations and mass-produced legal quotations. A reply that names the route, operator, arrival time, event and missing reasonable-measures analysis is easier to decide. Set a sensible response date while protecting any external limitation period.
If the refusal remains, choose the ADR, enforcement or court path connected to the operating carrier and journey. The SAS escalation guide distinguishes those functions and national routes.
The assessment on this page is current to 26 August 2026. The EU's adopted future nine-month filing and 30-day reply provisions are not yet applicable and should not be cited as present procedural defaults.
FAQ
Is "operational reasons" enough to reject compensation?
No. It does not identify an extraordinary event, connect it to the flight or explain the reasonable measures taken.
Must SAS disclose confidential technical records?
Not necessarily. Ask for sufficient flight-specific evidence and chronology to test the defence without demanding irrelevant safety-sensitive material.
Can an earlier weather event excuse a later rotation?
Only if SAS proves the causal link and shows that reasonable recovery steps could not prevent the qualifying final delay.
Should I open a new claim after rejection?
Usually reply under the existing case reference so the evidence and chronology remain together, unless SAS directs a different formal appeal route.
Can I still seek hotel costs if compensation is refused?
Yes. Reasonable care expenses can remain payable even when extraordinary circumstances defeat the fixed-compensation element.