LEVEL missed connection at Barcelona: your rights
Barcelona sits at both ends of a LEVEL itinerary that involves a connection — either a feeder flight arriving into Barcelona to catch a LEVEL long-haul departure, or a LEVEL long-haul flight landing in Barcelona to connect onward somewhere else. Because LEVEL itself flies point-to-point out of a single Spanish gateway, a missed connection on a LEVEL journey almost always means a different airline's flight was involved on one side of the itinerary — and whether that whole journey is protected under EU261 depends heavily on one detail: whether both flights were booked as a single reservation or as two separate tickets.
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:
Check the specific journey in the compensation calculator once the booking structure and actual delay are clear.
Single booking versus separate tickets
This is the single most important fact to establish before anything else. A single booking reference covering both the feeder or onward flight and the LEVEL sector is generally treated as one connecting itinerary for EU261 purposes, with the passenger's rights assessed against the delay at the true final destination of the whole journey, not just the individual sector that happened to run late. Two separately purchased tickets — even if timed to connect at Barcelona — are generally treated as two independent contracts, each assessed entirely on its own terms, with no obligation on either airline to protect the connection or compensate for a missed one caused by the other flight.
Feeder flight into Barcelona, then a LEVEL departure
If a delayed connecting flight into Barcelona causes a passenger to miss a LEVEL long-haul departure, and both flights were on one booking, the disruption is generally assessed against the final arrival delay at the LEVEL destination — Miami, Los Angeles, Buenos Aires, or wherever the itinerary was ultimately headed — even though the actual delay happened on the earlier, non-LEVEL sector. Rebooking onto a later LEVEL flight, or onto a different route entirely, does not by itself remove this entitlement if the overall itinerary was booked as one journey and the final arrival ends up sufficiently delayed.
A LEVEL arrival into Barcelona, then an onward flight
The reverse situation works the same way in principle: if a delayed LEVEL flight into Barcelona causes a passenger to miss a later connecting flight booked on the same reservation, the relevant delay for compensation purposes is measured against the passenger's true final destination, not against Barcelona as an intermediate stop. Because LEVEL's own network consists of long-haul sectors that can themselves run several hours behind schedule, this scenario is a genuine risk for any itinerary built around a tight connection window at Barcelona.
Who is responsible for the compensation
Under EU261, the specific operating carrier of the delayed sector is generally the one liable for compensation tied to that sector's own delay. Where the missed connection stems from LEVEL's own delayed arrival into Barcelona, LEVEL is the relevant carrier for that portion of the claim. Where the missed connection stems from a delayed feeder flight before the LEVEL sector, the feeder airline is typically the relevant carrier for its own delay, though the overall itinerary's EU261 eligibility can still depend on where the journey as a whole began. This can mean directing different parts of a single disrupted journey to different airlines, which is one of the reasons keeping the connecting flights on a single booking, and documenting which carrier operated which sector, matters so much in practice.
What to check before assuming coverage
- Was the itinerary booked as a single reservation covering both the connecting flight and the LEVEL sector, or as two separate tickets?
- What was the scheduled connection time at Barcelona, and was it a reasonable window given typical processing times?
- What was the actual delay on the sector that caused the missed connection?
- What was the final arrival time actually achieved, including any rebooking, compared with the original scheduled final arrival?
- Which airline operated each affected sector, according to the boarding passes and booking confirmation?
Evidence to gather for a connection claim
Keep the full original itinerary showing both flights under one booking reference, the boarding pass or confirmation for each sector, any rebooking or replacement flight confirmation, and the actual arrival time at the true final destination. A missed-connection claim depends more heavily on the paper trail linking the two flights together than most other LEVEL disruption claims, since the connecting-booking status is itself part of what needs to be established.
A worked example
A passenger books a single reservation covering a regional flight into Barcelona and an onward LEVEL flight to Buenos Aires, scheduled with a two-hour connection window. The regional flight is delayed by ninety minutes, leaving too little time to make the LEVEL departure; LEVEL rebooks the passenger onto the next available flight, which lands in Buenos Aires roughly five hours after the original scheduled arrival. Because both flights were on one booking, the passenger's compensation claim is assessed against that five-hour delay at the true final destination, Buenos Aires, even though the actual delay occurred entirely on the earlier, non-LEVEL sector.
Booking connections deliberately versus arriving separately
A meaningful distinction sometimes arises between a passenger who deliberately booked two flights to connect at Barcelona as part of a planned itinerary, and a passenger who happened to be in Barcelona already and separately purchased a LEVEL ticket for unrelated reasons. Only the first scenario, where the connection was part of the original booking intent and reflected in a single reservation, generally receives the connecting-itinerary protection described above. Two flights that merely happen to occur close together in time, without being part of the same booked journey, do not gain this protection regardless of how tight the actual gap between them turned out to be.
FAQ
Does it matter whether I booked both flights together or separately?
Yes, significantly. A single booking covering both the connecting flight and the LEVEL sector is generally assessed as one itinerary, with compensation tied to the delay at the true final destination. Two separate tickets are generally treated as entirely independent, with no protection for a missed connection between them.
If my feeder flight was delayed and I missed my LEVEL flight, who pays compensation?
It depends on which sector caused the relevant delay and how the itinerary was booked. The feeder airline is typically responsible for its own sector's delay; the overall itinerary's EU261 eligibility can still depend on where the journey as a whole began.
My LEVEL flight into Barcelona was late and I missed my onward flight — is that covered?
If both flights were on a single booking, yes, in principle, with the relevant delay measured against your true final destination rather than against Barcelona as an intermediate stop.
Does rebooking onto a later flight remove my right to compensation?
Not by itself. If the itinerary was a single booking and the final arrival ends up sufficiently delayed compared with the original schedule, the rebooking generally does not cancel the underlying compensation entitlement.
What if my connection time at Barcelona was very short to begin with?
A tight but properly ticketed connection is still generally protected under the same rules; the length of the original connection window does not itself remove the entitlement, though it may be relevant to the airline's own scheduling and rebooking obligations.