Claim assessment record
- Entity
- STN to OTP journey rights
- From
- STN
- To
- OTP
- Catalogued
- 2026-07-19
This guide builds a route-led claim assessment for London Stansted Airport (STN) to Bucharest Henri Coandă Airport (OTP) 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.
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 OTP sector operated.
Keep immediate remedies separate from fixed compensation
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.
Link the disruption event to the affected sector
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.
Route documents in travel order
- 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
Add a one-line description to each attachment. The aim is a navigable evidence pack, not an unlabelled archive.
From itinerary summary to airline response
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 OTP or the final destination.
Complete the London Stansted Airport to Bucharest Henri Coandă Airport route record
- 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.
A completed STN–OTP worksheet gives the respondent a route-specific chronology and prevents generic assertions from replacing the booking, operator, timing and cause evidence.
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
Treat STN–OTP 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.
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 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
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 OTP 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.
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 OTP 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.