Claim assessment record
- Entity
- GLA to EDI journey rights
- From
- GLA
- To
- EDI
- Catalogued
- 2026-07-19
This guide builds a route-led claim assessment for Glasgow Airport (GLA) to Edinburgh Airport (EDI) without inventing live service data. The page begins with eligibility facts and chronology, then builds the evidence, remedy and response-review stages.
Do not use departure delay as the only time figure
Create a time line with scheduled departure from GLA, disruption notice, replacement departure and actual final arrival. State whether the time comes from the airline, airport, boarding record or another source. Avoid rounding a threshold from memory.
Keep immediate remedies separate from fixed compensation
For a long wait after leaving or before leaving GLA, document what assistance was requested and provided. If an overnight stay or reasonable replacement became necessary, preserve the airline response and cost. A claim should list care expenses separately from the compensation request.
Reasonable measures on the GLA–EDI 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.
What proves this airport-pair case
- Complete booking showing GLA as departure and EDI 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.
Present the GLA–EDI case
Open with the booked route, operating carrier, disruption and actual final arrival. Then list notice timing, cause, care expenses and requested remedies. Ask for a reasoned response tied to those facts rather than a generic decision. Keep the acknowledgement before selecting a complaint or escalation route.
A GLA–EDI 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–EDI booking: state whether the airport pair sat on one reservation or separate tickets.
- GLA–EDI disruption: identify the affected sector, stated cause and replacement path.
- EDI destination: record whether Edinburgh Airport was the final booked destination or an intermediate point.
- EDI arrival: preserve the scheduled and actual arrival times and the source used for each.
- EDI expenses: connect each receipt to the wait, overnight stay, ground transfer or substitute journey.
- United Kingdom to United Kingdom review: verify the applicable regime and procedural deadline before escalation.
A completed GLA–EDI 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
Treat GLA–EDI 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.
Route direction before airline nationality
The GLA departure is catalogued in the UK framework, so UK261 is the primary route screen. The EDI arrival marker is uk. 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–EDI 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–EDI journey, the disrupted sector and the carrier status can affect coverage. Keep flight numbers, boarding passes, code-share wording and every replacement itinerary.
One booking to EDI
Where all sectors were issued on one booking, record the arrival at EDI 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 EDI 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.