How EU261 Applies to Code-Share Flights on Budget Carriers

The rule in one sentence: EU261 liability always falls on the operating carrier (the airline that physically flew the plane), not the marketing carrier that sold you the ticket. If Ryanair operated your flight but you booked through a travel agency selling it under a different code, Ryanair owes the compensation.

Code-sharing is an arrangement where one airline (the marketing carrier) sells seats on a flight operated by another airline (the operating carrier) under its own flight number. When your flight is delayed or cancelled, knowing which carrier actually flew the aircraft determines which airline you claim from under EU261.

Budget carriers such as Ryanair, easyJet, Wizz Air, Vueling, and Transavia sometimes enter code-share or interline arrangements with legacy carriers. Understanding the EU261 rules for these arrangements is essential to claiming correctly.

EU261 Article 2(b) defines the 'operating air carrier' as the airline that performs or intends to perform the flight. Compensation claims run against this carrier, not the one whose name appears most prominently on your booking.

• ›

  Operating carrier (liable for EU261): The airline whose aircraft and crew physically operated the flight. Their IATA designator and flight number appear on the aircraft's tail and on actual operational systems.

• ›

  Marketing carrier (not liable for EU261 compensation): The airline that sold the ticket or placed its flight code on the itinerary. Your e-ticket may show a Lufthansa flight number, but if the plane was operated by Eurowings, Eurowings is the liable party.

• ›

  Duty of care (Article 9): Duty of care (meals, hotel, transport) is owed by the operating carrier at the airport, even if you booked through the marketing carrier.

• ›

  Refunds under Article 8: Refund rights under EU261 can be claimed from the marketing carrier if that carrier sold you the ticket, since the commercial contract is with them. Compensation is always from the operating carrier.

The European Court of Justice confirmed in case C-532/17 (Wegener v Ryanair) that the operating carrier is the entity responsible for paying EU261 compensation. Booking through an OTA, travel agency, or partner airline does not shift that liability.

The most common code-share scenarios involving budget carriers and EU261 are:

• ›

  Vueling operated by Iberia code: Vueling (VY) and Iberia (IB) are both part of IAG. Flights may appear with an IB code but be operated by Vueling. If the Vueling aircraft was delayed, Vueling is liable under EU261.

• ›

  Eurowings / Lufthansa arrangements: Some routes marketed by Lufthansa with an LH code are operated by Eurowings (EW). The operating carrier (Eurowings) owes EU261 compensation.

• ›

  Transavia and KLM: Transavia (HV) is a subsidiary of KLM's parent Air France-KLM. Some itineraries show KLM codes but are operated by Transavia Netherlands. Transavia is the liable EU261 carrier.

• ›

  Ryanair and airline partnerships: Ryanair has limited interline arrangements. Where Ryanair (FR) operates the aircraft, they carry full EU261 liability regardless of how the ticket was distributed.

• ›

  Wizz Air and third-party distribution: Wizz Air (W6) tickets sold through OTAs remain subject to EU261. Wizz Air as the operating carrier holds full liability.

Always check your boarding pass or the aircraft's tail livery to confirm which airline actually operated your flight. The IATA two-letter code before the flight number (e.g., VY, EW, HV, FR, W6) identifies the operating carrier.

EU261 applies when either the departure airport is within the EU, or the operating carrier holds an EU operating license and the flight arrives in the EU from outside. The airport test is applied to the operating carrier's actual flight, not the marketing carrier's itinerary.

• ›

  Departure from EU airport, non-EU operating carrier: EU261 applies. For example, an American Airlines-operated flight code-shared with British Airways departing from London is covered by UK261 for that segment.

• ›

  Departure from non-EU airport, EU operating carrier: EU261 applies because the operating carrier holds an EU license. A Vueling flight from Buenos Aires to Barcelona is covered even though the departure is outside the EU.

• ›

  Departure from non-EU airport, non-EU operating carrier: EU261 does not apply. If United Airlines operates the flight from Chicago to Frankfurt, EU261 coverage depends on the Frankfurt-departing return leg, not the outbound.

• ›

  Layover at EU airport: If your itinerary includes a connection at an EU airport and the EU-departing leg is delayed, EU261 applies to that connecting segment based on its operating carrier.

Before filing an EU261 claim, confirm who operated your flight. The wrong carrier will simply redirect you, costing weeks of delay.

1. 1

   Check your boarding pass. The flight number printed on your boarding pass is usually the operating carrier's code and flight number.

2. 2

   Look at the aircraft livery in any photos you took at the gate or during boarding.

3. 3

   Search your flight number on FlightAware. FlightAware shows which airline's aircraft operated the flight and the actual tail registration.

4. 4

   Check your e-ticket or booking confirmation for a note such as 'operated by [Carrier Name].' This is a legal disclosure required when marketing and operating carriers differ.

5. 5

   If your itinerary shows an LH, IB, or KL code but the plane had Eurowings, Vueling, or Transavia livery, the latter is your operating carrier for EU261 purposes.

Common mistake: Filing the EU261 claim with the booking airline rather than the operating carrier. The booking airline will often reject the claim correctly, but this wastes time. Always go directly to the operating carrier.

Once you have confirmed the operating carrier, the claim process is the same as for any EU261 flight. Use the operating carrier's EU261 claim form, not the marketing carrier's general complaint process.

• ›

  Address your claim letter or online form to the operating carrier, not the one whose name is on your credit card charge.

• ›

  Reference your booking confirmation that shows 'operated by [Carrier]' and your boarding pass, which should show the operating carrier's code.

• ›

  Cite EU Regulation 261/2004 by name, specify the disruption (delay over 3 hours at final destination, cancellation, or denied boarding), and state the exact compensation amount you are entitled to based on the flight distance.

• ›

  Attach FlightAware data showing the actual arrival time if a delay is disputed.

If you need help identifying the right carrier and filing the claim correctly, TravelStacks handles EU261 claims across all EU carriers on a no-win no-fee basis. For the complete EU261 framework, see the EU261 rights guide.

A common problem on code-share itineraries is that the operating carrier claims you must contact the marketing carrier, and the marketing carrier claims it was not responsible for the disruption. This is not a legally valid defence for either party.

• ›

  EU261 liability rests with the operating carrier for compensation. This is settled law under Article 2(b) of EU Regulation 261/2004. Document any correspondence where the operating carrier denies responsibility.

• ›

  If the operating carrier refuses to pay while claiming the marketing carrier is liable, file a complaint with the national enforcement body (NEB) for the country of your departure airport. Include the operating carrier's denial letter as evidence.

• ›

  For refund claims under Article 8, you may also have a valid claim against the marketing carrier as the ticketing agent. Pursue both if the operating carrier refuses.

• ›

  Credit card chargebacks can be initiated against the card charge (usually the marketing carrier) citing failure to provide the contracted service. This is independent of your EU261 claim against the operating carrier.

Find your national enforcement body through the European Commission's NEB directory. Filing an NEB complaint is free and typically prompts carriers to resolve disputes that have stalled in customer service queues.