Passenger-rights record
- Entity
- EDI to AGP journey rights
- From
- EDI
- To
- AGP
- Catalogued
- 2026-07-19
This guide separates the travel remedies and evidence questions for Edinburgh Airport (EDI) to Málaga Airport (AGP). Use the sections as a decision path: identify the operator, protect the journey, record assistance and only then assess the compensation question.
Scheduled versus actual final arrival
Preserve the scheduled arrival at AGP, the actual arrival after the disruption and the source of that time. If the itinerary continued beyond AGP on one booking, measure the final booked destination instead. Departure delay is useful context but may not be the decisive compensation figure.
Care and travel choices on the EDI–AGP journey
For a long wait after leaving or before leaving EDI, 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.
Cause evidence for this direction of travel
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.
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.
Route-specific fields before submission
- 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.
Using the airport codes on every line keeps the EDI–AGP chronology tied to the passenger's actual journey and separates immediate travel remedies from the later compensation analysis.
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.
Start with travel direction: EDI to AGP
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.
Identify every operating carrier on the EDI–AGP journey
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.
Follow the protected itinerary to the final destination
Where all sectors were issued on one booking, record the arrival at AGP 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 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.