Claim assessment record
- Entity
- LCY to WAW journey rights
- From
- LCY
- To
- WAW
- Catalogued
- 2026-07-19
This guide builds a route-led claim assessment for London City Airport (LCY) to Warsaw Chopin Airport (WAW) without inventing live service data. Use the sections as a case file: identify the operator, prove the route and timing, document the cause and request a reasoned decision.
Identify every operating carrier on the LCY–WAW journey
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
The booking structure determines which final arrival matters. If WAW is only an intermediate point on one reservation, use the actual final booked destination. If the passenger held separate tickets, explain that fact and assess each contract rather than assuming through-journey protection.
Do not use departure delay as the only time figure
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.
Care and travel choices on the LCY–WAW journey
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
Ask which sector was affected, what event occurred and how it prevented the planned journey. A broad label such as weather or operational reasons does not by itself show the causal link. Keep notices for both LCY and WAW, because conditions at another airport or on an earlier aircraft rotation may also be cited.
Evidence pack for LCY to WAW
- 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.
Present the LCY–WAW case
A strong route submission does not claim that a direct service always operates. It describes the actual ticket. State every sector, identify where the disruption occurred and explain how the passenger ultimately reached WAW or the final destination.
A LCY–WAW case worksheet
- 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.
A completed LCY–WAW worksheet gives the respondent a route-specific chronology and prevents generic assertions from replacing the booking, operator, timing and cause evidence.
Confirm current operations before using route-specific facts
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.
Do not assume an airport pair is a verified nonstop service
Treat LCY–WAW as a journey frame rather than a live schedule. The passenger may have flown directly, connected elsewhere or held separate tickets. Preserve the ticket and identify the operator of each sector before applying route coverage or measuring the final-arrival impact.
How the uk departure and eu arrival interact
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.