SAS missed connection at Stockholm or Oslo
A missed SAS connection at Stockholm Arlanda or Oslo Airport can be protected when all sectors form one ticket and an incoming disruption causes late arrival at the final destination. SAS should reroute that booking and provide proportionate care. Self-transfer tickets normally leave the passenger responsible for the onward flight, and airport procedures differ between ARN and OSL, especially where border, customs, security or domestic-transfer steps apply.
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:
Use live airport instructions on the travel date. Terminal transport and transfer flows can change, so an account from an earlier journey is not reliable evidence of today's required route.
First establish the transport contract
| Evidence | Why it matters |
|---|---|
| One PNR and e-ticket receipt | Supports one journey to the last destination |
| Operated-by line for each flight | Identifies the airline responsible for the disruption |
| Through baggage confirmation | Shows expected handling, subject to border rules |
| Self-transfer notice | Warns that the carrier may not protect the onward booking |
| Replacement itinerary | Establishes rerouting and actual final arrival |
One search result, one credit-card transaction or two flights sold by the same agency does not conclusively create a through ticket. Read the contractual documents.
Stockholm Arlanda connections
Arlanda uses airport code ARN. Its terminals and gates are connected through airport transport arrangements, but passengers should check the current route and operating times on Swedavia's official pages. A terminal change can add walking, waiting, security or document-control time.
Travelling between Schengen and non-Schengen sectors can require passport control. Security rescreening depends on origin and transfer path. Checked baggage may continue automatically on an eligible through ticket, while a self-transfer can require collection and new check-in.
If an inbound delay leaves little time, proceed directly and save live gate notices. Record when the aircraft door opened and when the onward gate closed. A terminal transfer imposed by the accepted one-ticket itinerary is not automatically passenger fault, but avoidable delay after arrival can affect causation.
Oslo Airport connections
Oslo Airport uses code OSL. Norway participates in European air-passenger protection through the EEA. An OSL departure can therefore receive EC261-style treatment even though Norway is outside the EU.
International-to-domestic transfers can involve route-specific baggage, customs and security procedures. Avinor publishes current transfer information and should be consulted for the actual itinerary. Do not assume a bag is through-checked merely because both flights carry SK numbers.
When entering Norway, passport and customs obligations can affect the path to a domestic connection. Keep evidence of unusually restricted transfer flows or airline instructions, but remember that missing required travel documents remains the passenger's responsibility.
Calculate final arrival, not airport waiting alone
Suppose one ticket covers Amsterdam-Stockholm-Luleå. A delayed incoming service causes the passenger to miss the protected domestic flight and the substitute reaches Luleå three hours and 40 minutes late. The legal delay can be measured at Luleå, using the original schedule and actual door opening.
For a separate ARN-Luleå ticket, the first contract may end in Stockholm. The cost of the missed domestic flight is then not automatically part of the EC261 claim against the inbound operator. Travel insurance, agent promises or the second ticket's conditions can still matter.
At OSL, apply the same contract test. The airport layout does not turn two reservations into one. The SAS delayed-flight guide explains coverage, distance and cause after the correct endpoint is known.
Rerouting duties
For a protected connection, SAS should offer transport to the final destination at the earliest reasonable opportunity under comparable conditions. A later SAS flight may be suitable; another carrier or reasonable ground transport can be relevant when it arrives materially sooner.
Keep screenshots of the offered and available routes. Ask SAS before purchasing an alternative, unless urgency makes contact impracticable, and choose a proportionate fare. Record transfer time between airports if an alternative uses a different location.
Reimbursement is a different choice. Selecting it normally ends carriage on the refunded ticket. If travel already started and the journey lost its purpose, a return to the first departure point may be required where Article 8 conditions are satisfied.
Meals, hotel and local transport
Care depends on the wait and can include refreshments, meals, overnight accommodation and transport between airport and lodging. Weather or air traffic restrictions may defeat fixed compensation but generally do not erase care on a covered disruption.
Use reasonable options. At ARN or OSL, a hotel far from the airport may create unnecessary taxi costs if appropriate nearby accommodation was available. Conversely, widespread disruption can make the nearest realistic room more expensive. Save availability evidence and itemised receipts.
The SAS care-expense guide shows how to connect each purchase to the delay.
Identify the cause and operator
Crossing three hours at the final destination is not the whole test. SAS can avoid fixed compensation by proving extraordinary circumstances and reasonable measures. Airport closure, air traffic restrictions and dangerous weather require a specific chronology; routine technical or internal resource problems normally remain within airline operations.
Check who operated the late inbound flight. A partner with an SK marketing code may be the proper respondent. If the onward SAS flight departed as scheduled, explain that the incoming operator's delay caused the missed protected connection.
Evidence for the claim
Preserve the original and replacement itineraries, all boarding passes, baggage tags, gate notices and receipts. Record door opening, passport or security routing, onward gate closure and final arrival. State whether the passenger followed transfer directions promptly.
List each traveller and remedy separately. Include the great-circle amount only after confirming one protected booking and the correct operator. Use the SAS claim form guide to organise submission.
Airport procedures and legal sources were checked on 26 August 2026. Always verify live ARN and OSL transfer instructions on the day of travel.
FAQ
Is a connection at ARN protected when both flights show SK?
Not merely because of the code. Confirm one ticket and the actual operator for each sector.
Does Norway apply European passenger rights?
Yes, Norway participates through the EEA, so qualifying OSL journeys can receive EC261-style protection.
Must I collect baggage when connecting at Oslo?
It depends on the route, ticket and current customs procedure. Check Avinor and SAS instructions for the specific itinerary.
Can a terminal transfer excuse a missed flight at Arlanda?
It can form part of the chronology on an accepted through ticket, but the passenger must still follow current signs and proceed without avoidable delay.
Who pays after a partner-operated inbound delay?
The compensation request normally follows the operator of the disrupted incoming flight, using final arrival on the protected booking.