Claim assessment record
- Entity
- EDI to OSL journey rights
- From
- EDI
- To
- OSL
- Catalogued
- 2026-07-19
This guide builds a route-led claim assessment for Edinburgh Airport (EDI) to Oslo Airport (OSL) without inventing live service data. The page begins with eligibility facts and chronology, then builds the evidence, remedy and response-review stages.
Why this EDI–OSL 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.
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–OSL booking: state whether the airport pair sat on one reservation or separate tickets.
- EDI–OSL disruption: identify the affected sector, stated cause and replacement path.
- OSL destination: record whether Oslo Airport was the final booked destination or an intermediate point.
- OSL arrival: preserve the scheduled and actual arrival times and the source used for each.
- OSL expenses: connect each receipt to the wait, overnight stay, ground transfer or substitute journey.
- United Kingdom to Norway review: verify the applicable regime and procedural deadline before escalation.
A completed EDI–OSL worksheet gives the respondent a route-specific chronology and prevents generic assertions from replacing the booking, operator, timing and cause evidence.
From itinerary summary to airline response
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.
Evidence pack for EDI to OSL
- Complete booking showing EDI as departure and OSL 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.
Link the disruption event to the affected sector
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 OSL, because conditions at another airport or on an earlier aircraft rotation may also be cited.
Keep immediate remedies separate from fixed compensation
Ask the operating airline for meals, accommodation and transport when the relevant waiting conditions arise. Decide separately whether to continue to OSL 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.
Scheduled versus actual final arrival
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 OSL sector operated.
One booking to OSL
Where all sectors were issued on one booking, record the arrival at OSL or at the final destination shown on that booking. A missed intermediate connection may be part of one disruption. Separate tickets can leave the passenger with different obligations and practical risks, even when the flights were planned as a connection.
Identify every operating carrier on the EDI–OSL journey
A route page cannot decide the airline question without the ticket. For EDI to OSL, 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.
How the uk departure and eea arrival interact
The EDI departure is catalogued in the UK framework, so UK261 is the primary route screen. The OSL arrival marker is eea. 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.
Do not assume an airport pair is a verified nonstop service
Treat EDI–OSL 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.
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 OSL 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.