Claim assessment record
- Entity
- EDI to TLS journey rights
- From
- EDI
- To
- TLS
- Catalogued
- 2026-07-19
This guide builds a route-led claim assessment for Edinburgh Airport (EDI) to Toulouse-Blagnac Airport (TLS) without inventing live service data. The page begins with eligibility facts and chronology, then builds the evidence, remedy and response-review stages.
Define the EDI–TLS itinerary
Treat EDI–TLS 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.
Marketing airline versus operator on this airport pair
Record the operating carrier for each sector. A booking platform may show one brand while another airline operates the aircraft. On a connecting EDI–TLS journey, the disrupted sector and the carrier status can affect coverage. Keep flight numbers, boarding passes, code-share wording and every replacement itinerary.
Scheduled versus actual final arrival
Preserve the scheduled arrival at TLS, the actual arrival after the disruption and the source of that time. If the itinerary continued beyond TLS on one booking, measure the final booked destination instead. Departure delay is useful context but may not be the decisive compensation figure.
Cause evidence for this direction of travel
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.
A route-led request without unsupported assumptions
A strong route submission does not claim that a direct service always operates. It describes the actual ticket. State every sector, identify where the disruption occurred and explain how the passenger ultimately reached TLS or the final destination.
Service verification and index status
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.
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–TLS booking: state whether the airport pair sat on one reservation or separate tickets.
- EDI–TLS disruption: identify the affected sector, stated cause and replacement path.
- TLS destination: record whether Toulouse-Blagnac Airport was the final booked destination or an intermediate point.
- TLS arrival: preserve the scheduled and actual arrival times and the source used for each.
- TLS expenses: connect each receipt to the wait, overnight stay, ground transfer or substitute journey.
- United Kingdom to France review: verify the applicable regime and procedural deadline before escalation.
A completed EDI–TLS worksheet gives the respondent a route-specific chronology and prevents generic assertions from replacing the booking, operator, timing and cause evidence.
Route documents in travel order
- Complete booking showing EDI as departure and TLS 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.
Care and travel choices on the EDI–TLS 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.
One booking to TLS
The booking structure determines which final arrival matters. If TLS 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.
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 TLS 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 TLS 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.