Claim Compensation for a Glasgow Airport to Geneva Airport Flight

Define the GLA–GVA itinerary

Treat GLA–GVA 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.

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 GLA–GVA journey, the disrupted sector and the carrier status can affect coverage. Keep flight numbers, boarding passes, code-share wording and every replacement itinerary.

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.

Reasonable measures on the GLA–GVA itinerary

Ask which sector was affected, what event occurred and how it prevented the planned journey. A broad label such as weather or operational reasons does not by itself show the causal link. Keep notices for both GLA and GVA, because conditions at another airport or on an earlier aircraft rotation may also be cited.

From itinerary summary to airline response

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.

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

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

A completed GLA–GVA worksheet gives the respondent a route-specific chronology and prevents generic assertions from replacing the booking, operator, timing and cause evidence.

What proves this airport-pair case

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

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

Follow the protected itinerary to the final destination

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

Coverage screen for GLA to GVA

The GLA departure is catalogued in the UK framework, so UK261 is the primary route screen. The GVA arrival marker is other-europe. 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.