SAS three-hour delay: calculate arrival at the final destination
The three-hour threshold for SAS compensation is normally tested at the final destination on one protected booking, using the moment at least one aircraft door opens and passengers may disembark. Touchdown, departure delay and arrival at an intermediate airport are not substitutes for that calculation. A missed connection can therefore create a qualifying claim even when the first SAS sector was less than three hours late.
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:
Three hours is only one condition. The journey must also fall within EC261, the correct operating carrier must be identified, and SAS can avoid the fixed payment if it proves extraordinary circumstances plus reasonable measures.
Which time belongs in the calculation?
| Event | Does it normally establish legal arrival? |
|---|---|
| Aircraft touches the runway | No |
| Aircraft reaches a parking position | Not by itself |
| First door opens and passengers can leave | Yes, this is the usual EC261 measure |
| Passenger collects checked baggage | No, although the timestamp can support evidence |
| Passenger reaches the city centre | No |
Compare the scheduled arrival in the original ticket with the actual door-opening time. Do not use a revised schedule issued after disruption as the baseline. If the case is close to 180 minutes, write down the time immediately and retain several independent records.
Useful proof includes a timestamped message from the aircraft, a photograph after the door opens, airport movement data, the first usable mobile connection, a baggage receipt and reliable tracking history. None is automatically decisive alone. Ask SAS for the operational door-opening record when its calculation differs.
Final destination means the ticketed endpoint
On a single reservation, the final destination is ordinarily the last airport named in the transport contract, or a later connecting destination affected by the disruption. Imagine Dublin-Copenhagen-Gothenburg on one ticket. The first flight reaches Copenhagen 95 minutes late, the connection is lost, and the substitute service reaches Gothenburg four hours late. The four-hour result at Gothenburg is the relevant delay.
This approach protects the purpose of connecting travel. It also means distance is generally measured between the first departure point and the protected final destination rather than by adding the lengths of each sector. The SAS amount guide explains the resulting payment bands.
A stopover chosen as a genuine destination can divide the journey. So can a later flight purchased under an independent contract. Read the ticket rather than assuming every itinerary with two flight numbers is one journey.
Separate tickets change the risk
Two bookings purchased in the same browser session are not necessarily protected together. If the passenger holds Dublin-Copenhagen on one ticket and Copenhagen-Gothenburg on another, the first carrier's contractual destination can be Copenhagen. Missing the second departure does not automatically turn Gothenburg into the endpoint of the first EC261 claim.
Look for one PNR, a unified e-ticket receipt, through baggage and a carrier-issued connection. These facts support integration but should be assessed together. A self-transfer warning, two payment confirmations or a requirement to collect baggage and check in again points the other way.
When tickets are separate, calculate each disrupted flight independently and investigate contractual or insurance remedies for the lost onward booking. Do not overstate the final destination in the SAS form; an inaccurate route can weaken an otherwise valid delay claim.
Missed connections and passenger conduct
SAS cannot normally rely on a short connection that it accepted as part of one ticket merely because the transfer later became difficult. Minimum connecting times are part of the carrier's scheduling decision. At Copenhagen, Stockholm and Oslo, however, the passenger should follow transfer signs, passport and security instructions, and any rebooking directions without avoidable delay.
If the incoming aircraft arrives in time but the traveller stops for shopping, ignores a gate change or lacks required documents, the resulting missed connection may not be caused by the flight disruption. Preserve app notices and gate records when SAS alleges that the passenger was late.
The Copenhagen missed-connection guide addresses through tickets, baggage and rerouting at CPH.
Rerouting does not reset the clock
Measure arrival against the original itinerary even when SAS places the passenger on another flight or carrier. A new boarding pass does not create a new scheduled benchmark. Record every replacement because the route can also affect care, transfer duties and a possible long-haul reduction.
If the substitute flight lands at a different airport, legal arrival may involve the time needed to reach the original airport or another nearby destination agreed with the passenger. A bus arranged by SAS is part of the chronology. A passenger who independently travels elsewhere should document the reason and proportionate route.
Cause and reasonable measures remain essential
Crossing 180 minutes does not make payment automatic. SAS may establish that the delay followed an air traffic restriction, dangerous weather, airport closure, security event or another circumstance outside normal operations. It must show how the event affected this flight and what reasonable alternatives were considered.
Routine faults, late crew positioning and ordinary rotation problems generally remain within the carrier's sphere. When SAS cites an earlier extraordinary event, ask for the chain of sectors, recovery time and causal link. The existence of snow somewhere in Scandinavia is not enough to explain every later flight.
Care operates on a different track. Meals, refreshments, overnight accommodation and airport-hotel transport can remain due during a covered wait even if the fixed amount is refused for a proven external cause.
Present a precise claim
State the entire one-ticket itinerary, each operating carrier, original scheduled arrival, actual door-opening time and total minutes late. Explain any missed connection and identify the replacement sectors. Attach the original ticket before and after rebooking, boarding documents and timing evidence.
Claim the correct amount per passenger and place expenses in a separate schedule. If SAS gives a different arrival time, ask which operational timestamp it used. Keep the submission confirmation and case reference.
This analysis was reviewed on 26 August 2026. The future EU reform adopted in July 2026 is not yet applicable, so its filing procedure does not alter today's three-hour test.
FAQ
Does a 179-minute SAS arrival qualify?
Normally no for fixed delay compensation, because the threshold is at least three hours. Other rights such as care can arise earlier.
Is arrival measured when the wheels touch down?
No. The usual legal point is when one door opens and passengers are permitted to leave the aircraft.
Can a 90-minute first-flight delay produce compensation?
Yes, when it causes a missed connection on one protected booking and arrival at the final destination is at least three hours late.
Does a separate onward ticket count in the final delay?
Usually not automatically. Each independent transport contract must be assessed on its own route and destination.
What if SAS disputes the door-opening time?
Provide contemporaneous records, request the airline's operational timestamp and explain how each item supports the stated arrival.