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

A completed LCY–GOT 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

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

What proves this airport-pair case

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

Cause evidence for this direction of travel

A route-based claim is easier to review when the cause is placed on the timeline. State when it arose, which operator reported it and which part of the LCY–GOT itinerary it affected. Preserve later explanations if the initial message changes.

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

Scheduled versus actual final arrival

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

One booking to GOT

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

Carrier evidence for a direct or connecting itinerary

A route page cannot decide the airline question without the ticket. For LCY to GOT, 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.

Route direction before airline nationality

The LCY departure is catalogued in the UK framework, so UK261 is the primary route screen. The GOT 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–GOT itinerary

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