London Stansted Airport to Bucharest Henri Coandă Airport Flight Rights

Measure arrival for the STN–OTP case

Preserve the scheduled arrival at OTP, the actual arrival after the disruption and the source of that time. If the itinerary continued beyond OTP on one booking, measure the final booked destination instead. Departure delay is useful context but may not be the decisive compensation figure.

Care and travel choices on the STN–OTP journey

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

A route-based claim is easier to review when the cause is placed on the timeline. State when it arose, which operator reported it and which part of the STN–OTP itinerary it affected. Preserve later explanations if the initial message changes.

Evidence pack for STN to OTP

• Complete booking showing STN as departure and OTP 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.

A route-led request without unsupported assumptions

State the immediate problem first: care, replacement travel, refund or information. Use the STN–OTP chronology to show what the passenger needs and preserve the compensation question for the later coverage-and-cause screen.

A STN–OTP case worksheet

• 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–OTP booking: state whether the airport pair sat on one reservation or separate tickets.
• STN–OTP disruption: identify the affected sector, stated cause and replacement path.
• OTP destination: record whether Bucharest Henri Coandă Airport was the final booked destination or an intermediate point.
• OTP arrival: preserve the scheduled and actual arrival times and the source used for each.
• OTP expenses: connect each receipt to the wait, overnight stay, ground transfer or substitute journey.
• United Kingdom to Romania review: verify the applicable regime and procedural deadline before escalation.

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

Service verification and index status

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 London Stansted Airport, United Kingdom, to Bucharest Henri Coandă Airport, Romania. 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.

Coverage screen for STN to OTP

The STN departure is catalogued in the UK framework, so UK261 is the primary route screen. The OTP 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.

Identify every operating carrier on the STN–OTP journey

A route page cannot decide the airline question without the ticket. For STN to OTP, 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.

Separate tickets change the STN connection risk

Use the reservation reference to prove whether the journey from STN to OTP was protected as one itinerary. Keep rebooking documents and any ground transfer inserted after disruption. Do not combine independent tickets into one legal journey merely because they were purchased for the same trip.