Claim assessment record
- Entity
- EDI to FRA journey rights
- From
- EDI
- To
- FRA
- Catalogued
- 2026-07-19
This guide builds a route-led claim assessment for Edinburgh Airport (EDI) to Frankfurt Airport (FRA) without inventing live service data. The page begins with eligibility facts and chronology, then builds the evidence, remedy and response-review stages.
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 FRA sector operated.
Waiting, hotel and replacement travel
The passenger's first problem may be reaching FRA, not proving compensation. Record the rerouting options, any hotel or transport offered and the choice made. Later, use the same chronology for the legal screen without treating all remedies as one payment category.
Link the disruption event to the affected sector
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 EDI and FRA, because conditions at another airport or on an earlier aircraft rotation may also be cited.
Evidence pack for EDI to FRA
- Complete booking showing EDI as departure and FRA 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.
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.
A EDI–FRA case worksheet
- EDI departure: record the scheduled local time, terminal and check-in evidence at Edinburgh Airport.
- EDI operator: name the company that operated the disrupted sector leaving United Kingdom.
- EDI notice: preserve the first delay or cancellation message and its timestamp.
- EDI assistance: list meals, hotel, transport or rerouting requested before the journey continued.
- EDI–FRA booking: state whether the airport pair sat on one reservation or separate tickets.
- EDI–FRA disruption: identify the affected sector, stated cause and replacement path.
- FRA destination: record whether Frankfurt Airport was the final booked destination or an intermediate point.
- FRA arrival: preserve the scheduled and actual arrival times and the source used for each.
- FRA 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 EDI–FRA 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.
Define the EDI–FRA itinerary
The useful route fact is direction: departure at EDI and booked destination FRA. Verify whether those points belong to one protected booking, whether another airport was used after rerouting and which carrier operated the disrupted sector. The catalogue deliberately avoids claiming current service frequency.
How the uk departure and eu arrival interact
The EDI departure is catalogued in the UK framework, so UK261 is the primary route screen. The FRA 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.
One booking to FRA
Where all sectors were issued on one booking, record the arrival at FRA 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 EDI to FRA 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.