London Stansted Airport to Lyon Saint-Exupéry Airport Flight Rights

Measure arrival for the STN–LYS case

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.

Care and travel choices on the STN–LYS journey

The passenger's first problem may be reaching LYS, 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.

Cause evidence for this direction of travel

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.

What proves this airport-pair case

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

A route-led request without unsupported assumptions

A route guide should help the passenger preserve choices, not encourage an automatic compensation demand. Document the alternative offered to LYS, the waiting conditions and any unused travel before deciding which remedy to request.

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.

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

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.

Define the STN–LYS itinerary

This record covers the legal and evidence questions for travel from London Stansted Airport, United Kingdom, to Lyon Saint-Exupéry Airport, France. 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 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.

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