Claim Compensation for a London City Airport to Düsseldorf Airport Flight

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.

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–DUS booking: state whether the airport pair sat on one reservation or separate tickets.
• LCY–DUS disruption: identify the affected sector, stated cause and replacement path.
• DUS destination: record whether Düsseldorf Airport was the final booked destination or an intermediate point.
• DUS arrival: preserve the scheduled and actual arrival times and the source used for each.
• DUS expenses: connect each receipt to the wait, overnight stay, ground transfer or substitute journey.
• United Kingdom to Germany review: verify the applicable regime and procedural deadline before escalation.

A completed LCY–DUS worksheet gives the respondent a route-specific chronology and prevents generic assertions from replacing the booking, operator, timing and cause evidence.

A route-led request without unsupported assumptions

Use one paragraph for eligibility facts and a separate table for money requested. This prevents reimbursement, care expenses and fixed compensation from being combined into an unexplained total. Verify the relevant deadline and escalation forum for the jurisdiction before proceeding.

What proves this airport-pair case

• Complete booking showing LCY as departure and DUS 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.

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.

Care and travel choices on the LCY–DUS journey

Ask the operating airline for meals, accommodation and transport when the relevant waiting conditions arise. Decide separately whether to continue to DUS by rerouting or abandon unused travel for reimbursement. Keep itemised receipts and the alternatives offered; the cause of disruption does not automatically eliminate every care duty.

Measure arrival for the LCY–DUS case

The route file should explain where and when the passenger finally arrived. A cancellation followed by rerouting may use another airport or ground transport. Preserve that alternative path so the reviewer can calculate the impact without assuming the original DUS sector operated.

Separate tickets change the LCY connection risk

The booking structure determines which final arrival matters. If DUS 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.

Marketing airline versus operator on this airport pair

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.

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 DUS 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.

Define the LCY–DUS itinerary

The useful route fact is direction: departure at LCY and booked destination DUS. 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.