Claim assessment record
- Entity
- GLA to KEF journey rights
- From
- GLA
- To
- KEF
- Catalogued
- 2026-07-19
This guide builds a route-led claim assessment for Glasgow Airport (GLA) to Keflavik International Airport (KEF) without inventing live service data. A complete claim separates route coverage, notice, cause, expenses and fixed compensation instead of presenting one unexplained demand.
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 KEF sector operated.
Care and travel choices on the GLA–KEF journey
Ask the operating airline for meals, accommodation and transport when the relevant waiting conditions arise. Decide separately whether to continue to KEF 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.
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 GLA–KEF itinerary it affected. Preserve later explanations if the initial message changes.
Evidence pack for GLA to KEF
- Complete booking showing GLA as departure and KEF 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–KEF 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.
A GLA–KEF case worksheet
- 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–KEF booking: state whether the airport pair sat on one reservation or separate tickets.
- GLA–KEF disruption: identify the affected sector, stated cause and replacement path.
- KEF destination: record whether Keflavik International Airport was the final booked destination or an intermediate point.
- KEF arrival: preserve the scheduled and actual arrival times and the source used for each.
- KEF expenses: connect each receipt to the wait, overnight stay, ground transfer or substitute journey.
- United Kingdom to Iceland review: verify the applicable regime and procedural deadline before escalation.
A completed GLA–KEF worksheet gives the respondent a route-specific chronology and prevents generic assertions from replacing the booking, operator, timing and cause evidence.
Confirm current operations before using route-specific facts
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.
Start with travel direction: GLA to KEF
This record covers the legal and evidence questions for travel from Glasgow Airport, United Kingdom, to Keflavik International Airport, Iceland. 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.
Route direction before airline nationality
The GLA departure is catalogued in the UK framework, so UK261 is the primary route screen. The KEF arrival marker is eea. 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–KEF journey
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.
One booking to KEF
Use the reservation reference to prove whether the journey from GLA to KEF 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.
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 KEF 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.
