Claim assessment record
- Entity
- EDI to VNO journey rights
- From
- EDI
- To
- VNO
- Catalogued
- 2026-07-19
This guide builds a route-led claim assessment for Edinburgh Airport (EDI) to Vilnius Airport (VNO) without inventing live service data. A complete claim separates route coverage, notice, cause, expenses and fixed compensation instead of presenting one unexplained demand.
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 VNO sector operated.
Keep immediate remedies separate from fixed compensation
The passenger's first problem may be reaching VNO, 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–VNO itinerary
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 VNO 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
Keep original records and submit copies through the verified channel. Mark any item that comes from a third-party source.
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.
A EDI–VNO case worksheet
- 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–VNO booking: state whether the airport pair sat on one reservation or separate tickets.
- EDI–VNO disruption: identify the affected sector, stated cause and replacement path.
- VNO destination: record whether Vilnius Airport was the final booked destination or an intermediate point.
- VNO arrival: preserve the scheduled and actual arrival times and the source used for each.
- VNO expenses: connect each receipt to the wait, overnight stay, ground transfer or substitute journey.
- United Kingdom to Lithuania review: verify the applicable regime and procedural deadline before escalation.
A completed EDI–VNO 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.
Do not assume an airport pair is a verified nonstop service
This record covers the legal and evidence questions for travel from Edinburgh Airport, United Kingdom, to Vilnius Airport, Lithuania. It does not assert that a direct flight operates on the chosen date. Confirm the actual sectors, operating carrier and booking structure. A connecting itinerary can still use this airport-pair guide, but the claim must describe every sector and the final booked destination.
Route direction before airline nationality
The EDI departure is catalogued in the UK framework, so UK261 is the primary route screen. The VNO 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.
Carrier evidence for a direct or connecting itinerary
A route page cannot decide the airline question without the ticket. For EDI to VNO, list each sector in order, then write the operator beside it. This prevents a claim from being sent to a marketing carrier that did not operate the affected flight.
One booking to VNO
The booking structure determines which final arrival matters. If VNO 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.
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 VNO 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.