Claim assessment record
- Entity
- EDI to AYT journey rights
- From
- EDI
- To
- AYT
- Catalogued
- 2026-07-19
This guide builds a route-led claim assessment for Edinburgh Airport (EDI) to Antalya Airport (AYT) without inventing live service data. The page begins with eligibility facts and chronology, then builds the evidence, remedy and response-review stages.
Do not assume an airport pair is a verified nonstop service
Treat EDI–AYT 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 other arrival interact
The EDI departure is catalogued in the UK framework, so UK261 is the primary route screen. The AYT arrival marker is other. 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
Record the operating carrier for each sector. A booking platform may show one brand while another airline operates the aircraft. On a connecting EDI–AYT 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 AYT
The booking structure determines which final arrival matters. If AYT 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
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 AYT sector operated.
Care and travel choices on the EDI–AYT 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.
Link the disruption event to the affected sector
Separate the event from the airline's legal conclusion. Record the exact explanation, timing and sector, then ask what measures were taken to reduce the delay or provide replacement travel. The passenger should not invent operational facts, but can request enough detail for a reasoned decision.
What proves this airport-pair case
- Complete booking showing EDI as departure and AYT 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
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 Antalya 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–AYT booking: state whether the airport pair sat on one reservation or separate tickets.
- EDI–AYT disruption: identify the affected sector, stated cause and replacement path.
- AYT destination: record whether Antalya Airport was the final booked destination or an intermediate point.
- AYT arrival: preserve the scheduled and actual arrival times and the source used for each.
- AYT expenses: connect each receipt to the wait, overnight stay, ground transfer or substitute journey.
- United Kingdom to Turkey review: verify the applicable regime and procedural deadline before escalation.
A completed EDI–AYT 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.
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 AYT 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.