Compensation is calculated on your final arrival delay — not your first flight's delay. That distinction alone can turn a "no claim" situation into full compensation.
The Myth
"If my first flight is delayed by only 20 minutes, causing me to miss my connection and land 6 hours late at my final destination, I'm only entitled to compensation based on the 20-minute first leg."
For which airline is actually liable when your itinerary involves a codeshare — the marketing carrier vs. the operating carrier — see our dedicated codeshare liability guide. This article focuses specifically on how the delay itself is calculated across a connection, and the technical evidence you need to prove it.
The Reality
Compensation for a missed connection is calculated based on the total accumulated delay at your final destination — not the delay on whichever individual leg actually caused the problem — provided the entire itinerary was booked under a single contract of carriage (a "through-ticket"). Proving this, however, requires capturing verifiable aviation data rather than relying on the airline's own account of what happened.
Through-Tickets vs. Self-Connecting: Why Booking Structure Matters
Through-Ticket (Single PNR / Contract)
The carrier is fully liable for rebooking, care, and delay compensation based on your final destination's arrival time — covered under EC261/UK261 and the Montreal Convention, treating the whole itinerary as one journey regardless of how many legs or connections it involves.
Self-Connecting (Separate PNRs / Tickets)
If you book two entirely separate tickets yourself to save money, the second airline generally treats you as a simple no-show if your first flight is delayed — there's no statutory compensation for a missed connection from either airline in this structure, and you absorb all rebooking and hotel costs yourself. This is one of the real trade-offs of self-connecting itineraries that budget travelers should weigh against the savings.
Landmark Case: Folkerts v. Air France (C-11/11)
The scenario: A passenger books a through-ticket from Bremen to Luanda via Paris. The first flight from Bremen is delayed by only 2 minutes — genuinely negligible — but the passenger misses the connecting flight in Paris and arrives in Luanda 11 hours late.
The CJEU ruling: Compensation depends on the delay experienced at the final destination, not the length of the delay on whichever leg actually triggered it. Because the passenger arrived more than 3 hours late in Luanda, full EC261 compensation was awarded — despite the initial delay being just 2 minutes. This is the ruling that makes the "my first flight was barely late" defense irrelevant on a through-ticket itinerary.
Essential Technical Evidence for Delay Disputes
To overcome an airline's rejection, you generally need independent, legally recognized data points rather than just your own account of events:
- In-Block Time (actual arrival): under CJEU case law, arrival time is legally defined as the moment at least one aircraft door opens — not when the wheels touch the runway. This distinction can matter by several minutes on a borderline claim.
- FlightAware / Flightradar24 logs: independent digital flight-tracking records capturing gate departure and gate arrival times, separate from the airline's own reporting.
- METAR reports: official meteorological records proving the actual weather conditions at the time of operation, useful if the airline cites weather as the cause.
The Protocol: Building an Unassailable Delay Evidence File
- Photograph the aircraft door opening upon arrival, with a timestamp, to establish the legal "in-block" time for your final destination.
- Download independent flight logs from FlightAware or a similar tracking service, showing scheduled vs. actual block times for every leg.
- Preserve all boarding passes for every segment of the journey, including connecting legs, not just the final one.
- Obtain a written connection failure notice from the transfer desk, showing your rebooked flight assignment and new arrival time.
Our Flight Status & Evidence Tools directory links directly to FlightAware, Flightradar24, and METAR lookup resources for exactly this purpose. Once your evidence file is complete, generate a formal compensation letter citing your final destination's arrival delay.
Related Kibbo Tools
- Flight Status & Evidence Tools (Directory) →
- Read: Codeshare Liability Guide →
- Generate a Flight Disruption Compensation Letter →
Sources
- Court of Justice of the European Union — Folkerts v. Air France, C-11/11. curia.europa.eu
- FlightAware — independent flight tracking and aviation data platform. flightaware.com