Feeder sector
Keep the scheduled and actual arrival of the first SAS or partner-operated flight and the connection originally available.
SAS Compensation Claim
A SAS disruption can become a network-connection claim when a Scandinavian feeder is tied to an onward sector on the same protected booking. The important record is not only the first late flight, but the connection that failed and the time you ultimately reached the original final destination.
For a SAS claim, preserve the exact route, booking structure and operating carrier. European passenger-rights rules can be relevant on qualifying journeys, while partner-operated sectors and separately purchased onward tickets need to be distinguished before responsibility and final-destination delay are assessed.
Scandinavian connectionsProtected itinerariesOperating carrierFinal arrival
Build a SAS claim around the affected itinerary, not the airline name alone
A qualifying long arrival delay, cancellation or involuntary denied boarding can support compensation. On a SAS itinerary with connecting sectors, keep the complete booking and establish whether the disrupted flight and onward journey formed one protected itinerary.
If the onward flight was purchased independently, preserve that reservation but keep the booking boundary visible. A self-built connection should not automatically be treated as a through journey sold under one SAS booking.
When a SAS feeder causes a protected connection to fail
Missed onward sector
Preserve the flight you could no longer take and any replacement itinerary issued after the disruption.
Original endpoint
For one protected booking, record when you finally reached the destination shown at the end of the original itinerary.
The booking structure changes what a missed SAS connection means
One protected booking
Keep every sector together, including the original onward flight and final destination.
Separate onward ticket
Document the later booking and resulting consequences separately rather than assuming it forms one protected SAS journey.
Multi-airline itinerary
Where another carrier appears on the booking, identify which airline actually operated the flight that was delayed or cancelled.
On a SAS-branded itinerary, identify the operator of the disrupted flight
Connecting journeys can contain partner or codeshare sectors. The marketing flight number is useful evidence, but it does not by itself establish who physically operated the affected flight.
Keep the “operated by” line from the itinerary or boarding pass. Responsibility should be assessed using the actual operator, route and protected-booking structure together.
After a SAS reroute, preserve the entire replacement path
Original connection
Save the initial itinerary showing the planned transfer and final destination.
Replacement sectors
Record every new flight, operating airline and connection point after the disruption.
Actual final arrival
For a protected journey, document when the replacement itinerary reached the original final destination.
Evidence for a SAS compensation claim
Journey record
- Full booking confirmation
- All SAS and partner flight numbers
- Connection points and original final destination
- Operating carrier of the disrupted sector
- Original boarding passes where available
Disruption record
- Delay or cancellation messages
- Reason communicated by the airline
- Missed onward sector
- Replacement itinerary and boarding passes
- Actual final arrival and relevant expense receipts
How Airdelay reviews a SAS case
01 — Map the itinerary
We establish the disrupted sector, connection and whether the onward journey belonged to the same protected booking.
02 — Verify the operator
We identify the airline that actually operated the affected flight and review the route under the relevant passenger-rights framework.
03 — Reconstruct the outcome
For a protected connection, we organize the missed sector, replacement travel and actual arrival at the original endpoint.
SAS compensation claim FAQ
What should I keep if a SAS delay made me miss a connecting flight?
If the flights were on one protected booking, keep the full itinerary, missed onward flight, replacement travel and actual arrival at the original final destination.
What if my onward flight was bought separately?
Keep both reservations, but distinguish the independently purchased flight from a protected connection sold as one itinerary.
What if another airline operated the SAS-coded flight?
Record the actual operating carrier shown on the itinerary or boarding pass. The SAS marketing code alone may not identify the operator of the disrupted sector.
What if I was rerouted through a different Scandinavian or European airport?
Preserve the original itinerary and every replacement sector, then record when you reached the originally booked final destination.
Should I keep receipts after a long SAS disruption?
Keep relevant reasonable expense receipts together with airline messages and the replacement itinerary.
Check your SAS compensation claim
Send the complete itinerary, especially any protected connection, together with the operating carrier, disruption messages, replacement travel and actual arrival at the original final destination.
