Passenger-rights record
- Entity
- GLA to BER journey rights
- From
- GLA
- To
- BER
- Catalogued
- 2026-07-19
This guide separates the travel remedies and evidence questions for Glasgow Airport (GLA) to Berlin Brandenburg Airport (BER). Use the sections as a decision path: identify the operator, protect the journey, record assistance and only then assess the compensation question.
Measure arrival for the GLA–BER case
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.
Care and travel choices on the GLA–BER journey
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.
Evidence pack for GLA to BER
- 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
Arrange the file in journey order so a reviewer can follow the route without guessing which document belongs to which sector.
A route-led request without unsupported assumptions
Ask the carrier to confirm the operating sector, route alternative and final-destination plan. If the journey no longer serves its purpose, document that before accepting reimbursement. Keep the response for the later claim assessment.
A GLA–BER 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–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.
Using the airport codes on every line keeps the GLA–BER chronology tied to the passenger's actual journey and separates immediate travel remedies from the later compensation analysis.
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
This record covers the legal and evidence questions for travel from Glasgow Airport, United Kingdom, to Berlin Brandenburg Airport, Germany. 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.
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.
Carrier evidence for a direct or connecting itinerary
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.
Separate tickets change the GLA connection risk
Where all sectors were issued on one booking, record the arrival at BER 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 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.