SAS missed connection at Copenhagen Airport
If an inbound SAS delay causes a missed connection at Copenhagen Airport on one protected ticket, SAS should normally reroute the passenger to the final destination, provide care during the wait and assess EC261 compensation from lateness at that final destination. Two independently bought tickets usually do not receive the same through-journey protection. Preserve the original PNR, operated-by details and replacement arrival time before the app changes the booking.
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:
Copenhagen Airport uses the code CPH. Follow its live transfer signs and SAS instructions because gates, security routing and document checks vary with the arriving and departing countries.
One booking or self-transfer?
| Booking feature | Through-ticket indication | Separate-ticket indication |
|---|---|---|
| Reservation record | One airline PNR covering every sector | Different PNRs and confirmations |
| Ticket receipt | One e-ticket itinerary to the last destination | Distinct contracts and ticket numbers |
| Baggage | Checked through where the route permits | Collection and new bag drop required |
| Missed-flight handling | SAS automatically protects or rebooks the connection | Later airline may treat the passenger as a no-show |
| EC261 final destination | Usually the last affected point on the ticket | Often ends at CPH for the first contract |
No single row is conclusive, but the transport contract is decisive. A travel website displaying both flights on one screen does not create through protection if it issued independent tickets.
Final arrival controls compensation
Imagine a single booking from Birmingham through Copenhagen to Helsinki. The first SAS service is 80 minutes late, the protected connection is missed and the replacement reaches Helsinki four hours after the original schedule. The relevant EC261 delay can be four hours at Helsinki, not 80 minutes at CPH.
Measure actual arrival when a door opens and passengers can leave at the final destination. Use the original schedule as the baseline. The distance band ordinarily uses the first origin and protected endpoint rather than adding each sector.
Crossing three hours does not guarantee payment. EC261 coverage, the operating carrier and the cause still matter. The SAS three-hour guide provides the full arrival and evidence test.
Minimum connection time and passenger conduct
When SAS sells a connection on one ticket, it has accepted the scheduled transfer under the itinerary's rules. The passenger should nevertheless proceed directly, monitor gate changes and complete required passport, security or document checks. A short connection accepted by the carrier is different from a missed flight caused by shopping, an expired document or ignoring instructions.
Save arrival and gate notifications if SAS alleges late presentation. Note when the incoming door opened, when the onward gate closed and any queue or transfer restriction. Copenhagen Airport's official transfer page should be used on the day of travel because the route through the airport can change.
Passengers moving between Schengen and non-Schengen journeys can face passport control. Some transfers require security screening. Do not promise a universal airside path based on a previous trip.
What SAS should offer
For a protected missed connection, rerouting should reach the booked final destination at the earliest reasonable opportunity under comparable transport conditions. SAS may use its own flight, a partner service or another workable route. Keep every offer, including its departure, arrival, airport and operator.
A passenger does not have to accept reimbursement if the objective remains to travel. Conversely, if a delay reaches five hours at departure and the trip has lost its purpose, the Article 8 reimbursement and return option may become relevant. Record the choice so the ticket is not refunded while the traveller still expects carriage.
If SAS offers only a route much later while realistic earlier seats exist, ask it to consider them and save contemporaneous availability. Buying a replacement independently can be recoverable in some circumstances but requires proof that SAS failed to reroute adequately and that the cost was proportionate.
Care at Copenhagen
Reasonable meals and refreshments are tied to waiting time. When the new itinerary requires an overnight stay, SAS may need to arrange hotel accommodation and transport between CPH and the lodging. These duties can survive an extraordinary-circumstances defence to fixed compensation.
Use SAS vouchers or arrangements when suitable. If none are provided, buy necessary, moderate options and retain itemised receipts. Record the passenger count and waiting period. A card transaction alone does not show whether a purchase was a meal, hotel or unrelated item.
Keep care expenses separate from EUR 250-600 compensation. The SAS care-cost guide explains documentation and proportionality.
Baggage after a missed connection
Ask SAS whether checked baggage was transferred, held at CPH or sent on a later flight. Preserve baggage tags and create a Property Irregularity Report at the final airport if the bag does not arrive. Do not leave with only an oral assurance.
Baggage delay follows Montreal rules, including a written claim within 21 days after delivery and proof of necessary purchases. It is not added to the EC261 distance payment. If the journey ends at CPH because the passenger abandons travel, obtain written instructions for collecting or forwarding the bag.
When another airline operated a sector
An SK code can be attached to a partner-operated flight. Fixed compensation normally follows the operating carrier of the flight linked to the disruption. On a one-ticket connection, identify every operator and explain which event caused the final delay.
SAS joining SkyTeam does not make the alliance responsible. The SAS codeshare guide shows how a partner-operated inbound or onward sector changes the addressee and sometimes territorial coverage.
Claim checklist
Retain the full e-ticket, one PNR, original and replacement boarding passes, baggage tags, app notifications and receipts. Record the incoming door-opening time, onward gate status and final arrival. State whether SAS rebooked automatically and which alternative was accepted.
In the request, list each passenger, complete route, operator per sector, final delay, distance amount and cause supplied. Itemise care separately. Keep the submission confirmation and case reference.
This CPH guide was reviewed on 26 August 2026. The EU reform adopted in July 2026 is not yet applicable, so its future filing timetable does not replace present rules.
FAQ
Does an 80-minute inbound delay qualify after a missed connection?
It can when one protected ticket is involved and the passenger reaches the final destination at least three hours late.
Must SAS rebook a separately ticketed onward flight?
Usually not under the same through-journey duty. Review the second ticket's terms, insurance and any voluntary assistance offered.
Can I request a hotel at CPH after an overnight rebooking?
Yes, reasonable accommodation and airport-hotel transport can be due during a covered wait when SAS does not provide another suitable arrangement.
Is baggage always transferred automatically at Copenhagen?
No. It depends on the ticket, route and customs or security requirements. Confirm the bag status with SAS and retain the tag.
Does a codeshare connection go into one claim to SAS?
Not automatically. Identify the operator responsible for the disrupted flight while using the complete one-ticket itinerary to explain final arrival.