Claim Compensation for a London Gatwick Airport to Rotterdam The Hague Airport Flight

Define the LGW–RTM itinerary

Treat LGW–RTM 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.

Marketing airline versus operator on this airport pair

A route page cannot decide the airline question without the ticket. For LGW to RTM, list each sector in order, then write the operator beside it. This prevents a claim from being sent to a marketing carrier that did not operate the affected flight.

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 RTM sector operated.

Reasonable measures on the LGW–RTM itinerary

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.

From itinerary summary to airline response

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.

Why this LGW–RTM 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 LGW–RTM case worksheet

• LGW departure: record the scheduled local time, terminal and check-in evidence at London Gatwick Airport.
• LGW operator: name the company that operated the disrupted sector leaving United Kingdom.
• LGW notice: preserve the first delay or cancellation message and its timestamp.
• LGW assistance: list meals, hotel, transport or rerouting requested before the journey continued.
• LGW–RTM booking: state whether the airport pair sat on one reservation or separate tickets.
• LGW–RTM disruption: identify the affected sector, stated cause and replacement path.
• RTM destination: record whether Rotterdam The Hague Airport was the final booked destination or an intermediate point.
• RTM arrival: preserve the scheduled and actual arrival times and the source used for each.
• RTM expenses: connect each receipt to the wait, overnight stay, ground transfer or substitute journey.
• United Kingdom to Netherlands review: verify the applicable regime and procedural deadline before escalation.

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

What proves this airport-pair case

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

Keep immediate remedies separate from fixed compensation

Ask the operating airline for meals, accommodation and transport when the relevant waiting conditions arise. Decide separately whether to continue to RTM 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.

Separate tickets change the LGW connection risk

Where all sectors were issued on one booking, record the arrival at RTM 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.

How the uk departure and eu arrival interact

The LGW departure is catalogued in the UK framework, so UK261 is the primary route screen. The RTM 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.