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

Why this LHR–DUS page remains a legal reference

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.

A LHR–DUS case worksheet

• LHR departure: record the scheduled local time, terminal and check-in evidence at London Heathrow Airport.
• LHR operator: name the company that operated the disrupted sector leaving United Kingdom.
• LHR notice: preserve the first delay or cancellation message and its timestamp.
• LHR assistance: list meals, hotel, transport or rerouting requested before the journey continued.
• LHR–DUS booking: state whether the airport pair sat on one reservation or separate tickets.
• LHR–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 LHR–DUS worksheet gives the respondent a route-specific chronology and prevents generic assertions from replacing the booking, operator, timing and cause evidence.

From itinerary summary to airline response

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 DUS or the final destination.

Evidence pack for LHR to DUS

• Complete booking showing LHR 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

Add a one-line description to each attachment. The aim is a navigable evidence pack, not an unlabelled archive.

Reasonable measures on the LHR–DUS itinerary

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 LHR and DUS, because conditions at another airport or on an earlier aircraft rotation may also be cited.

Waiting, hotel and replacement travel

For a long wait after leaving or before leaving LHR, document what assistance was requested and provided. If an overnight stay or reasonable replacement became necessary, preserve the airline response and cost. A claim should list care expenses separately from the compensation request.

Scheduled versus actual final arrival

Create a time line with scheduled departure from LHR, disruption notice, replacement departure and actual final arrival. State whether the time comes from the airline, airport, boarding record or another source. Avoid rounding a threshold from memory.

One booking to DUS

Use the reservation reference to prove whether the journey from LHR to DUS 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.

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.

Route direction before airline nationality

The LHR 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.

Start with travel direction: LHR to DUS

Treat LHR–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.