Claim assessment record
- Entity
- GLA to BER journey rights
- From
- GLA
- To
- BER
- Catalogued
- 2026-07-19
This guide builds a route-led claim assessment for Glasgow Airport (GLA) to Berlin Brandenburg Airport (BER) without inventing live service data. The page begins with eligibility facts and chronology, then builds the evidence, remedy and response-review stages.
Measure arrival for the GLA–BER case
Preserve the scheduled arrival at BER, the actual arrival after the disruption and the source of that time. If the itinerary continued beyond BER on one booking, measure the final booked destination instead. Departure delay is useful context but may not be the decisive compensation figure.
Waiting, hotel and replacement travel
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–BER itinerary
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–BER itinerary it affected. Preserve later explanations if the initial message changes.
Route documents in travel order
- Complete booking showing GLA as departure and BER 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.
A route-led request without unsupported assumptions
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–BER booking: state whether the airport pair sat on one reservation or separate tickets.
- GLA–BER disruption: identify the affected sector, stated cause and replacement path.
- BER destination: record whether Berlin Brandenburg Airport was the final booked destination or an intermediate point.
- BER arrival: preserve the scheduled and actual arrival times and the source used for each.
- BER expenses: connect each receipt to the wait, overnight stay, ground transfer or substitute journey.
- United Kingdom to Germany review: verify the applicable regime and procedural deadline before escalation.
A completed GLA–BER 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.
Do not assume an airport pair is a verified nonstop service
Treat GLA–BER 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.
How the uk departure and eu arrival interact
The GLA departure is catalogued in the UK framework, so UK261 is the primary route screen. The BER 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.
Marketing airline versus operator on this airport pair
Record the operating carrier for each sector. A booking platform may show one brand while another airline operates the aircraft. On a connecting GLA–BER 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 BER
The booking structure determines which final arrival matters. If BER is only an intermediate point on one reservation, use the actual final booked destination. If the passenger held separate tickets, explain that fact and assess each contract rather than assuming through-journey protection.
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 BER 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.
