Edinburgh Airport to Toulouse-Blagnac Airport Flight Rights

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.

One booking to TLS

Use the reservation reference to prove whether the journey from EDI to TLS was protected as one itinerary. Keep rebooking documents and any ground transfer inserted after disruption. Do not combine independent tickets into one legal journey merely because they were purchased for the same trip.

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.

Waiting, hotel and replacement travel

Ask the operating airline for meals, accommodation and transport when the relevant waiting conditions arise. Decide separately whether to continue to TLS by rerouting or abandon unused travel for reimbursement. Keep itemised receipts and the alternatives offered; the cause of disruption does not automatically eliminate every care duty.

Reasonable measures on the EDI–TLS itinerary

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 TLS, because conditions at another airport or on an earlier aircraft rotation may also be cited.

Evidence pack for EDI to TLS

• 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.

Present the EDI–TLS case

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–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.

Using the airport codes on every line keeps the EDI–TLS chronology tied to the passenger's actual journey and separates immediate travel remedies from the later compensation analysis.

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.

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.

Coverage screen for EDI to TLS

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.