Claim assessment record
- Entity
- LHR to BRU journey rights
- From
- LHR
- To
- BRU
- Catalogued
- 2026-07-19
This guide builds a route-led claim assessment for London Heathrow Airport (LHR) to Brussels Airport (BRU) 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.
Define the LHR–BRU itinerary
Treat LHR–BRU 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 LHR departure is catalogued in the UK framework, so UK261 is the primary route screen. The BRU 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.
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.
Follow the protected itinerary to the final destination
Use the reservation reference to prove whether the journey from LHR to BRU 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.
Measure arrival for the LHR–BRU case
Preserve the scheduled arrival at BRU, the actual arrival after the disruption and the source of that time. If the itinerary continued beyond BRU on one booking, measure the final booked destination instead. Departure delay is useful context but may not be the decisive compensation figure.
Waiting, hotel and replacement travel
Ask the operating airline for meals, accommodation and transport when the relevant waiting conditions arise. Decide separately whether to continue to BRU 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.
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.
What proves this airport-pair case
- Complete booking showing LHR as departure and BRU 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.
Present the LHR–BRU case
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.
Route-specific fields before submission
- 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–BRU booking: state whether the airport pair sat on one reservation or separate tickets.
- LHR–BRU disruption: identify the affected sector, stated cause and replacement path.
- BRU destination: record whether Brussels Airport was the final booked destination or an intermediate point.
- BRU arrival: preserve the scheduled and actual arrival times and the source used for each.
- BRU expenses: connect each receipt to the wait, overnight stay, ground transfer or substitute journey.
- United Kingdom to Belgium review: verify the applicable regime and procedural deadline before escalation.
A completed LHR–BRU worksheet gives the respondent a route-specific chronology and prevents generic assertions from replacing the booking, operator, timing and cause evidence.
Why this LHR–BRU 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.
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 LHR to BRU 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.
