Flight delays8 min readUpdated: May 11, 2026

Codeshare flight delay: when the operating carrier is responsible

On a codeshare flight, the name on the ticket is not always enough. Compensation usually turns on who actually operated the flight and how the delay affected final arrival.

Main guide for this topic: Flight delay compensation

When this scenario should be checked

For codeshare flights where the ticket and aircraft show different airlines, the first check is not departure delay alone, but the consequence for the whole journey. If you arrived at the final destination three hours or more late, compare the case with flight delay compensation. The same flight can have a different outcome if the passenger arrived late under one booking, bought an unrelated onward leg or received reasonable rerouting quickly.

It is important to separate three questions: whether fixed compensation may apply, whether care was owed during the wait and whether extra costs should be reimbursed. Let Kasni therefore treats this kind of case as a file with route, times, reason and evidence, not as one short complaint.

  • Final arrival is measured, not only late departure.
  • Coverage depends on route, operating carrier and booking.
  • The delay reason must be concrete, not only a broad message.

Next step

Find out if you are owed up to EUR 600 in compensation.

The quick check combines flight details, route distance and basic evidence to assess your right.

Route and rule coverage

For codeshare journeys, separate the marketing airline from the operating carrier first. The claim is usually directed at the airline that actually operated the flight because it controls the crew, aircraft and operation.

This is common on routes through European hubs, where the ticket is sold by one airline but a partner or regional carrier operates one segment. For every such situation, record the departure airport, arrival airport, operating carrier and whether all segments were bought together. Those four facts often decide whether the case is only a travel disruption or a compensation claim.

Passenger nationality is usually not the central fact. What matters more is whether the airport and carrier are covered and whether arrival at the last destination was late enough. That is why a claim should not be sent before the route is written down clearly and without assumptions.

Table for amount and arrival review

The simplest review is a small table with these columns: flight number, route, carrier, scheduled arrival, actual arrival, route distance, stated reason and assistance offered. This prevents confusion between departure, landing and aircraft-door opening, which is common during long waits.

For shorter routes, the amount may be 250 euros. For medium European routes, 400 euros is often checked, while longer routes may raise the 600-euro level, with special rules when the delay is between three and four hours. The amount depends on distance and eligibility, not ticket price.

If the airline cites bad weather, a slot, runway closure or security, that is not automatically the end. Check where the issue happened, how long it lasted and whether it directly explains your late arrival. For technical faults, crew issues or late aircraft rotation, a more precise explanation is usually needed.

Case file

What Let Kasni organizes first

  • exact flight, date, route and booking reference
  • scheduled and actual arrival time
  • airline's stated reason and the evidence behind it
  • receipts for meals, hotel, transfer or a new ticket

Care, costs and rerouting

Care rights are separate from fixed compensation. During a longer wait, ask for meals, refreshments, communication and, if departure moves to the next day, hotel accommodation with transfer. If assistance is not provided, costs should be reasonable and connected to the wait.

For rerouting, what was offered and when matters. If the alternative arrives much later, if you miss an onward leg or if you have to accept another arrival airport, include that in the timeline. Otherwise the airline may answer only about the first segment, even though the real consequence happened at the end of the journey.

Checklist for the evidence file

For a codeshare case, keep the ticket with both flight codes, boarding pass, operating-carrier name, messages from each airline involved and proof of arrival at the final destination.

The best case file has a short sequence of events: when you learned about the delay, what reason was given, what was offered, when you actually departed and when you arrived. If the reason changed across the app, email and verbal announcements, keep every version.

Professional claim handling helps because it relies on checkable facts instead of passenger impressions. A clean file shortens communication with the airline, reduces the risk of a generic rejection and makes the next step easier if the reply does not address all facts.

  • Boarding pass and booking confirmation for every segment.
  • Airline messages, status screenshots and a departures-board photo.
  • Receipts for food, hotel, transfer or a new ticket if costs arose.
  • Clear proof of actual arrival at the final destination.

Route, timing and airline responsibility

For codeshare flight delay: when the operating carrier is responsible, first check whether the route is protected, then what actually happened, and only then which claim makes sense. Use Flight delay compensation for the baseline rule and amounts, while this page checks the concrete scenario and the evidence that changes it.

The best approach is to build a short timeline. Write down the scheduled time, actual time, where you were when the problem happened, what the airline offered, what you accepted and what you paid yourself. That timeline later decides whether the case is about fixed compensation, ticket refund, expense reimbursement or only care rights.

If the case involves arrival delay, a missed connection, rerouting or an overnight wait, also check flight delay compensation. Most practical passenger questions eventually depend on how late the whole journey ended and whether the reason was within the airline's control.

Professional review

Why we do not stop at a generic rejection

Airlines often expect individual passengers to give up after the first short answer. A structured file, knowledge of the rules and procedural pressure change the speed and quality of the response.

Documents to save for review

The strongest evidence is evidence from the same day: boarding pass, booking confirmation, airline messages, app screenshot, departures-board photo, receipts for food, hotel or transfer and any written information received at the airport.

If the reason was explained verbally, write down the exact wording, time and place. If the reason changed, keep every version. The difference between a technical fault, air traffic control, bad weather, strike and crew shortage is not a formality; it is often the line between a strong and weak claim.

In the claim, do not only say that you want compensation. Include flight number, date, route, booking reference, scheduled and actual arrival time, a short timeline and a clear separation between fixed compensation and expenses you want reimbursed.

What if the airline rejects the claim

The airline's first reply is often not a full assessment. It may contain broad wording, an automatically selected category or an answer that covers only one part of the claim. Read it carefully: does it address the exact flight, date, final destination and concrete reason that caused the disruption?

If the answer does not mention evidence, timeline or the measures the airline took, send a short follow-up. You do not need to repeat the whole story. Ask for a precise explanation and attach the most important proof again. That follow-up often separates genuinely weak cases from cases that were only rejected superficially.

Aircraft parked at a gate before a codeshare flight