What Is a Protected Connection?

What is a protected connection?

A protected connection is a change of planes sold on one ticket so that if a delay or cancellation makes you miss the next flight, the ticketing airline must rebook you onward — you are not treated as a no-show on a separate fare.

Protection is a property of the ticket, not of the airport clock. Two flights with a comfortable two-hour gap can still be unprotected if you bought them as separate tickets. Conversely, a tight but legal same-ticket link that meets minimum connection time usually carries rebooking duty when the airline caused the miss.

Codeshares and alliances can appear on one ticket and still be protected; the operating carrier may re-accommodate on partner metal. Self-transfers marketed by OTAs as “hacker fares” are typically unprotected even when the app shows a single trip view — read whether one ticket number covers every segment.

When protection fails in practice (no seats, long overnight), care and compensation rules may still apply on qualifying routes — see flight delay compensation rights and EU261 complete rules. contract of carriage for virtual interlining brands.

How do you tell if a connection is protected before you buy?

Check that every flight shares one booking reference / e-ticket stock and was sold as a single itinerary — not two order numbers stitched in a shopping cart.

Example: Airline.com sells London → Frankfurt → Singapore on one PNR. Your first leg is late; you miss Frankfurt → Singapore. The airline must rebook you on a later flight, subject to its rules and passenger-rights care duties. Contrast: you buy EasyJet into Frankfurt and a separate Singapore Airlines ticket onward — that is a self-transfer; Singapore Airlines can treat you as absent if you never check in.

Document timelines if you claim later via how to claim flight compensation DIY or AirHelp. Layover comfort still matters: airport layover survival.

Which terms sit next to protected connections?

Protected connection is the opposite of self-transfer; MCT sets the legal floor; codeshares explain who operates each leg.

See self-transfer, minimum connection time and codeshare.

• Self-transfer — unprotected separate tickets
• Overbooking — protection does not remove bump risk
• EU261 — care and cash on qualifying misses

What should you do the moment a protected connection breaks?

Get rebooked before leaving the airport: join the airline desk queue and the phone or app queue simultaneously, ask for the next available flight on any partner, and request meal or hotel vouchers if the wait runs long — all owed on a single protected ticket.

A protected connection means every segment sits on one ticket, so the airline owns the problem when a delay cascades. Your leverage is strongest immediately: rebooking inventory evaporates as a planeload of misconnected passengers competes for the same seats. Open the airline app while taxiing in, rebook yourself if the tool offers it, and treat the airport desk as backup rather than first resort.

Know what you can ask for. On a protected ticket the carrier must get you to the final destination, and most will rebook onto partner or even rival airlines if their own seats are gone — agents rarely volunteer this, so ask explicitly. Long involuntary waits usually trigger meal vouchers, and overnight misconnects caused by the airline typically include a hotel; weather events shrink the duty of care, but the rebooking obligation remains.

Document everything as it happens: boarding passes, delay announcements, and receipts for anything you buy. Those records power later compensation claims under regimes like EU261 or UK261, where arrival delays over three hours can be worth EUR 250–600 depending on distance. Our flight delay compensation rights guide walks the full claim sequence.