London City Airport to Düsseldorf Airport Flight Rights

Do not assume an airport pair is a verified nonstop service

Treat LCY–DUS 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.

Route direction before airline nationality

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.

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.

Separate tickets change the LCY connection risk

Where all sectors were issued on one booking, record the arrival at DUS or at the final destination shown on that booking. A missed intermediate connection may be part of one disruption. Separate tickets can leave the passenger with different obligations and practical risks, even when the flights were planned as a connection.

Do not use departure delay as the only time figure

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.

Care and travel choices on the LCY–DUS journey

The passenger's first problem may be reaching DUS, 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.

Link the disruption event to the affected sector

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.

Evidence pack for LCY to DUS

• 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

Keep original records and submit copies through the verified channel. Mark any item that comes from a third-party source.

Present the LCY–DUS case

A route guide should help the passenger preserve choices, not encourage an automatic compensation demand. Document the alternative offered to DUS, the waiting conditions and any unused travel before deciding which remedy to request.

A LCY–DUS 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–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.

Using the airport codes on every line keeps the LCY–DUS 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.