Arrival into Warsaw
Record the scheduled and actual arrival of the feeder flight plus the connection time in the original itinerary.
A LOT disruption can become a connection claim when Warsaw is the transfer point between a regional European flight and an onward journey on the same protected booking. In that situation, the useful claim record follows the whole itinerary: the late feeder, the missed onward sector, the replacement route and the time you reached the original final destination.
LOT is an EU carrier. EU261 can therefore be relevant on qualifying EU departures and qualifying LOT-operated flights into the EU from outside it. Partner-operated sectors and separately purchased onward tickets should be identified before responsibility or final-destination delay is assessed.
A qualifying long arrival delay, cancellation or involuntary denied boarding can support compensation. If the disrupted LOT sector and onward flight were sold as one protected itinerary, keep every segment and the final destination shown on the original ticket.
If the onward journey was independently purchased, preserve it as separate evidence. Do not automatically treat a self-built connection as though LOT sold the flights together under one protected booking.
Record the scheduled and actual arrival of the feeder flight plus the connection time in the original itinerary.
Keep the sector you could no longer take and every replacement flight offered after the disruption.
On one protected booking, document when the replacement journey ultimately reached the endpoint shown on the original ticket.
A qualifying LOT flight departing an EU airport can fall within EU261 when the regulation's other requirements are met.
A qualifying inbound flight can also be relevant when LOT actually operates it, because LOT is an EU carrier.
If the disruption affects a protected connection, keep the complete booking so the final-destination impact can be reviewed.
Partner and codeshare flights can appear within a LOT booking. A LOT marketing flight number is useful evidence, but it does not by itself prove that LOT operated the affected aircraft.
Keep the “operated by” line from the itinerary or boarding pass. The actual operator, route and booking structure should be considered together before responsibility is assigned.
Save the booking showing the planned Warsaw transfer and original final destination.
Record every new flight, operating airline and connection point, including a reroute that no longer uses Warsaw.
For a protected itinerary, document when the replacement travel reached the original final destination.
We identify the disrupted sector, Warsaw 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 the missed flight, replacement journey and arrival at the original endpoint.
Send the complete itinerary, especially any Warsaw connection, together with the operating carrier, disruption messages, replacement travel and actual arrival at the original final destination.