London City Airport to Gothenburg Landvetter Airport Flight Rights

Measure arrival for the LCY–GOT case

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.

Care and travel choices on the LCY–GOT journey

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

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.

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

Arrange the file in journey order so a reviewer can follow the route without guessing which document belongs to which sector.

Present the LCY–GOT case

State the immediate problem first: care, replacement travel, refund or information. Use the LCY–GOT chronology to show what the passenger needs and preserve the compensation question for the later coverage-and-cause screen.

Complete the London City Airport to Gothenburg Landvetter Airport route record

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

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

Do not assume an airport pair is a verified nonstop service

This record covers the legal and evidence questions for travel from London City Airport, United Kingdom, to Gothenburg Landvetter Airport, Sweden. It does not assert that a direct flight operates on the chosen date. Confirm the actual sectors, operating carrier and booking structure. A connecting itinerary can still use this airport-pair guide, but the claim must describe every sector and the final booked destination.

Coverage screen for LCY to GOT

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.

Carrier evidence for a direct or connecting itinerary

Record the operating carrier for each sector. A booking platform may show one brand while another airline operates the aircraft. On a connecting LCY–GOT journey, the disrupted sector and the carrier status can affect coverage. Keep flight numbers, boarding passes, code-share wording and every replacement itinerary.

Follow the protected itinerary to the final destination

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.