Claim assessment record
- Entity
- GLA to GOT journey rights
- From
- GLA
- To
- GOT
- Catalogued
- 2026-07-19
This guide builds a route-led claim assessment for Glasgow Airport (GLA) to Gothenburg Landvetter Airport (GOT) without inventing live service data. A complete claim separates route coverage, notice, cause, expenses and fixed compensation instead of presenting one unexplained demand.
Do not use departure delay as the only time figure
Preserve the scheduled arrival at GOT, the actual arrival after the disruption and the source of that time. If the itinerary continued beyond GOT on one booking, measure the final booked destination instead. Departure delay is useful context but may not be the decisive compensation figure.
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 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.
Link the disruption event to the affected sector
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 GLA–GOT itinerary it affected. Preserve later explanations if the initial message changes.
Route documents in travel order
- Complete booking showing GLA 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
Add a one-line description to each attachment. The aim is a navigable evidence pack, not an unlabelled archive.
Present the GLA–GOT 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
- GLA departure: record the scheduled local time, terminal and check-in evidence at Glasgow Airport.
- GLA operator: name the company that operated the disrupted sector leaving United Kingdom.
- GLA notice: preserve the first delay or cancellation message and its timestamp.
- GLA assistance: list meals, hotel, transport or rerouting requested before the journey continued.
- GLA–GOT booking: state whether the airport pair sat on one reservation or separate tickets.
- GLA–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 GLA–GOT worksheet gives the respondent a route-specific chronology and prevents generic assertions from replacing the booking, operator, timing and cause evidence.
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 Glasgow 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 GLA to GOT
The GLA 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.
Identify every operating carrier on the GLA–GOT journey
Record the operating carrier for each sector. A booking platform may show one brand while another airline operates the aircraft. On a connecting GLA–GOT journey, the disrupted sector and the carrier status can affect coverage. Keep flight numbers, boarding passes, code-share wording and every replacement itinerary.
Separate tickets change the GLA connection risk
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.
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 GLA to GOT 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.