Claim assessment record
- Entity
- EDI to AGP journey rights
- From
- EDI
- To
- AGP
- Catalogued
- 2026-07-19
This guide builds a route-led claim assessment for Edinburgh Airport (EDI) to Málaga Airport (AGP) without inventing live service data. The page begins with eligibility facts and chronology, then builds the evidence, remedy and response-review stages.
Identify every operating carrier on the EDI–AGP journey
A route page cannot decide the airline question without the ticket. For EDI to AGP, list each sector in order, then write the operator beside it. This prevents a claim from being sent to a marketing carrier that did not operate the affected flight.
Follow the protected itinerary to the final destination
The booking structure determines which final arrival matters. If AGP 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.
Do not use departure delay as the only time figure
Create a time line with scheduled departure from EDI, 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 EDI–AGP journey
The passenger's first problem may be reaching AGP, 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
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 EDI–AGP itinerary it affected. Preserve later explanations if the initial message changes.
What proves this airport-pair case
- Complete booking showing EDI as departure and AGP 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.
Present the EDI–AGP case
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.
Complete the Edinburgh Airport to Málaga Airport route record
- 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–AGP booking: state whether the airport pair sat on one reservation or separate tickets.
- EDI–AGP disruption: identify the affected sector, stated cause and replacement path.
- AGP destination: record whether Málaga Airport was the final booked destination or an intermediate point.
- AGP arrival: preserve the scheduled and actual arrival times and the source used for each.
- AGP expenses: connect each receipt to the wait, overnight stay, ground transfer or substitute journey.
- United Kingdom to Spain review: verify the applicable regime and procedural deadline before escalation.
A completed EDI–AGP worksheet gives the respondent a route-specific chronology and prevents generic assertions from replacing the booking, operator, timing and cause evidence.
Why this EDI–AGP page remains a legal reference
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–AGP itinerary
The useful route fact is direction: departure at EDI and booked destination AGP. 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 AGP 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.
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 AGP 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.