Passenger-rights record
- Entity
- LCY to WAW journey rights
- From
- LCY
- To
- WAW
- Catalogued
- 2026-07-19
This guide separates the travel remedies and evidence questions for London City Airport (LCY) to Warsaw Chopin Airport (WAW). Immediate care and travel choices remain separate from a later fixed-compensation decision.
Carrier evidence for a direct or connecting itinerary
Do not choose the respondent solely from the logo on the confirmation. Match the flight designator and operating-carrier line for the sector that failed. If rerouting introduced a different airline, preserve both the original and replacement operators so the chronology remains clear.
Follow the protected itinerary to the final destination
Use the reservation reference to prove whether the journey from LCY to WAW was protected as one itinerary. Keep rebooking documents and any ground transfer inserted after disruption. Do not combine independent tickets into one legal journey merely because they were purchased for the same trip.
Scheduled versus actual final arrival
Preserve the scheduled arrival at WAW, the actual arrival after the disruption and the source of that time. If the itinerary continued beyond WAW on one booking, measure the final booked destination instead. Departure delay is useful context but may not be the decisive compensation figure.
Keep immediate remedies separate from fixed compensation
The passenger's first problem may be reaching WAW, not proving compensation. Record the rerouting options, any hotel or transport offered and the choice made. Later, use the same chronology for the legal screen without treating all remedies as one payment category.
Cause evidence for this direction of travel
Separate the event from the airline's legal conclusion. Record the exact explanation, timing and sector, then ask what measures were taken to reduce the delay or provide replacement travel. The passenger should not invent operational facts, but can request enough detail for a reasoned decision.
Route documents in travel order
- Complete booking showing LCY as departure and WAW or the final booked destination
- Operating carrier and flight number for every sector
- Boarding passes, check-in proof and replacement itinerary
- Scheduled and actual final-arrival times with sources
- Cancellation or delay notices and the reason given
- Care, hotel, transport and substitute-travel receipts
Arrange the file in journey order so a reviewer can follow the route without guessing which document belongs to which sector.
From itinerary summary to airline response
A route guide should help the passenger preserve choices, not encourage an automatic compensation demand. Document the alternative offered to WAW, the waiting conditions and any unused travel before deciding which remedy to request.
Route-specific fields before submission
- LCY departure: record the scheduled local time, terminal and check-in evidence at London City Airport.
- LCY operator: name the company that operated the disrupted sector leaving United Kingdom.
- LCY notice: preserve the first delay or cancellation message and its timestamp.
- LCY assistance: list meals, hotel, transport or rerouting requested before the journey continued.
- LCY–WAW booking: state whether the airport pair sat on one reservation or separate tickets.
- LCY–WAW disruption: identify the affected sector, stated cause and replacement path.
- WAW destination: record whether Warsaw Chopin Airport was the final booked destination or an intermediate point.
- WAW arrival: preserve the scheduled and actual arrival times and the source used for each.
- WAW expenses: connect each receipt to the wait, overnight stay, ground transfer or substitute journey.
- United Kingdom to Poland review: verify the applicable regime and procedural deadline before escalation.
Using the airport codes on every line keeps the LCY–WAW chronology tied to the passenger's actual journey and separates immediate travel remedies from the later compensation analysis.
Service verification and index status
The catalogue stores this as an airport-pair legal reference and marks current service as unverified. It does not confirm a direct flight, distance band or operating airline. The page therefore remains protected from indexing until current service, distance and carriers are verified. The passenger should use the actual booking, not this route record, as evidence of travel.
Define the LCY–WAW itinerary
The useful route fact is direction: departure at LCY and booked destination WAW. Verify whether those points belong to one protected booking, whether another airport was used after rerouting and which carrier operated the disrupted sector. The catalogue deliberately avoids claiming current service frequency.
Coverage screen for LCY to WAW
The LCY departure is catalogued in the UK framework, so UK261 is the primary route screen. The WAW arrival marker is eu. If the journey reaches the EU/EEA, EU coverage should be considered from the real route and operating carrier, not assumed merely because the destination is European.
Verification and legal limitation
This page is general passenger-rights information, not legal advice, live flight data or a promise of payment. The structured record for LCY to WAW journey rights was last catalogued on 2026-07-19. Verify the current itinerary, operating carrier, official channel, law and procedural deadline before acting.
Care, reimbursement, rerouting, expenses and fixed compensation are separate questions. Eligibility and outcome depend on the complete facts and are not guaranteed.