Feeder → Lisbon
Record the scheduled and actual arrival of the first flight plus the connection originally available in Lisbon.
A TAP Air Portugal disruption can become a connection claim when Lisbon sits between a European feeder and a longer onward flight. Preserve the full ticket: a modest delay into Lisbon can matter very differently if it causes a protected onward sector to be missed.
TAP is an EU carrier, so EU261 can be relevant on qualifying EU departures and qualifying TAP-operated flights arriving in the EU from outside it. On long itineraries, the route, actual operating carrier and final arrival after rerouting should be assessed together.
A qualifying long arrival delay, cancellation or involuntary denied boarding can support compensation. If a TAP feeder and onward flight were sold together as one protected journey, keep the original final destination and every segment in the booking.
If you assembled the onward travel using a separate ticket, preserve both reservations but show the boundary clearly. A self-built connection should not automatically be assessed as though TAP sold one through itinerary.
Record the scheduled and actual arrival of the first flight plus the connection originally available in Lisbon.
Keep the sector you could no longer board and every replacement flight TAP arranged after the disruption.
On a protected itinerary, document when you actually reached the endpoint on the original ticket, not merely when you arrived in Lisbon.
Qualifying TAP journeys departing from an EU airport can fall within EU261 when the other conditions are met.
A qualifying flight into the EU can also be relevant when TAP actually operates it, because TAP is an EU carrier.
Where a qualifying disrupted sector affects a protected connection, preserve the whole booking and actual final arrival for review.
Long itineraries may include partner or codeshare flights. A TAP flight number on the booking does not by itself establish that TAP operated every sector.
Keep the “operated by” information for the flight that was delayed or cancelled. The actual operator, route and booking structure should be reviewed together before responsibility is assigned.
Save the initial booking showing the planned connection and original endpoint.
Record each new flight, carrier and connection point, including rerouting that bypasses Lisbon.
Document when the replacement journey reached the original final destination so the overall delay can be reconstructed.
We identify the disrupted sector, Lisbon connection and whether the onward flight belonged to the same protected itinerary.
We verify the actual operating carrier and the passenger-rights framework relevant to the route.
For a protected connection, we organize missed flights, rerouting and arrival at the original final destination.
Send the complete itinerary, especially any Lisbon connection, together with the operating carrier, disruption messages, replacement travel and actual arrival at the original final destination.