Claim assessment record
- Entity
- EDI to VIE journey rights
- From
- EDI
- To
- VIE
- Catalogued
- 2026-07-19
This guide builds a route-led claim assessment for Edinburgh Airport (EDI) to Vienna International Airport (VIE) without inventing live service data. The page begins with eligibility facts and chronology, then builds the evidence, remedy and response-review stages.
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–VIE journey, the disrupted sector and the carrier status can affect coverage. Keep flight numbers, boarding passes, code-share wording and every replacement itinerary.
Follow the protected itinerary to the final destination
The booking structure determines which final arrival matters. If VIE 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.
Scheduled versus actual final arrival
Preserve the scheduled arrival at VIE, the actual arrival after the disruption and the source of that time. If the itinerary continued beyond VIE on one booking, measure the final booked destination instead. Departure delay is useful context but may not be the decisive compensation figure.
Keep immediate remedies separate from fixed compensation
The passenger's first problem may be reaching VIE, 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.
Reasonable measures on the EDI–VIE 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 VIE, because conditions at another airport or on an earlier aircraft rotation may also be cited.
Route documents in travel order
- Complete booking showing EDI as departure and VIE 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
Open with the booked route, operating carrier, disruption and actual final arrival. Then list notice timing, cause, care expenses and requested remedies. Ask for a reasoned response tied to those facts rather than a generic decision. Keep the acknowledgement before selecting a complaint or escalation route.
Complete the Edinburgh Airport to Vienna International 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–VIE booking: state whether the airport pair sat on one reservation or separate tickets.
- EDI–VIE disruption: identify the affected sector, stated cause and replacement path.
- VIE destination: record whether Vienna International Airport was the final booked destination or an intermediate point.
- VIE arrival: preserve the scheduled and actual arrival times and the source used for each.
- VIE expenses: connect each receipt to the wait, overnight stay, ground transfer or substitute journey.
- United Kingdom to Austria review: verify the applicable regime and procedural deadline before escalation.
A completed EDI–VIE worksheet gives the respondent a route-specific chronology and prevents generic assertions from replacing the booking, operator, timing and cause evidence.
Why this EDI–VIE 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 VIE
The useful route fact is direction: departure at EDI and booked destination VIE. 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 VIE 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 VIE 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.