Claim assessment record
- Entity
- STN to LYS journey rights
- From
- STN
- To
- LYS
- Catalogued
- 2026-07-19
This guide builds a route-led claim assessment for London Stansted Airport (STN) to Lyon Saint-Exupéry Airport (LYS) without inventing live service data. Use the sections as a case file: identify the operator, prove the route and timing, document the cause and request a reasoned decision.
Carrier evidence for a direct or connecting itinerary
Do not choose the respondent solely from the logo on the confirmation. Match the flight designator and operating-carrier line for the sector that failed. If rerouting introduced a different airline, preserve both the original and replacement operators so the chronology remains clear.
Follow the protected itinerary to the final destination
Where all sectors were issued on one booking, record the arrival at LYS 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.
Scheduled versus actual final arrival
Create a time line with scheduled departure from STN, 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.
Keep immediate remedies separate from fixed compensation
For a long wait after leaving or before leaving STN, 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.
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 STN and LYS, because conditions at another airport or on an earlier aircraft rotation may also be cited.
Route documents in travel order
- Complete booking showing STN as departure and LYS 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.
Present the STN–LYS case
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 LYS or the final destination.
Route-specific fields before submission
- STN departure: record the scheduled local time, terminal and check-in evidence at London Stansted Airport.
- STN operator: name the company that operated the disrupted sector leaving United Kingdom.
- STN notice: preserve the first delay or cancellation message and its timestamp.
- STN assistance: list meals, hotel, transport or rerouting requested before the journey continued.
- STN–LYS booking: state whether the airport pair sat on one reservation or separate tickets.
- STN–LYS disruption: identify the affected sector, stated cause and replacement path.
- LYS destination: record whether Lyon Saint-Exupéry Airport was the final booked destination or an intermediate point.
- LYS arrival: preserve the scheduled and actual arrival times and the source used for each.
- LYS 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 STN–LYS worksheet gives the respondent a route-specific chronology and prevents generic assertions from replacing the booking, operator, timing and cause evidence.
Why this STN–LYS 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.
Do not assume an airport pair is a verified nonstop service
The useful route fact is direction: departure at STN and booked destination LYS. 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 STN departure is catalogued in the UK framework, so UK261 is the primary route screen. The LYS 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 STN to LYS 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.