Bucharest Henri Coandă Airport Compensation Claim
Delayed, cancelled, denied boarding or rerouted at Bucharest Henri Coandă Airport? Keep the booking, operating carrier, airline notices, replacement itinerary and actual arrival at the ticketed final destination.
OTP is Romania’s principal international airport and an EU departure point. Direct European flights, domestic links and journeys connecting through larger hubs create different evidence patterns after disruption.
When can a Bucharest Airport compensation claim arise?
For departures from OTP, EU261 territorial scope is generally clear because the journey starts in Romania, an EU Member State. Compensation is not automatic: final-destination delay, cancellation notice timing, denied-boarding circumstances and the disruption cause still need assessment.
For arrivals from outside the EU, preserve the origin, operating carrier and complete itinerary because these can affect territorial scope.
Direction, carrier and final destination matter
Departing OTP
A Bucharest departure starts at an EU airport, subject to EU261’s other requirements and exceptions.
Arriving OTP
For a non-EU origin, identify the operating carrier and complete route before deciding the EU261 position.
Final arrival
For a protected connection, preserve actual arrival at the ticketed final destination rather than only the OTP sector.
OTP disruption files can involve different network patterns
Bucharest combines international flying with domestic Romanian links and connections through other European airports. That means the same cancellation can create a simple direct-flight file for one passenger and a missed-connection file for another.
Direct Europe
Keep scheduled and actual arrival plus every delay, cancellation or replacement-flight notice.
Domestic connection
If a Romanian domestic sector forms part of one booking, preserve it with the international sectors and final arrival.
Hub itinerary
For a protected connection through another European hub, keep every sector and replacement offered.
A missed OTP connection needs the complete booking
If the affected flight formed part of one protected itinerary, keep all sectors, scheduled connection times and replacement flights. Actual arrival at the ticketed final destination can be more important than the delay on the first disrupted sector.
Connection evidence
- Complete booking and ticket numbers
- Domestic and international sectors
- Scheduled connection time
- Missed and replacement flights
- Actual final-destination arrival
Record the rerouting actually offered
A Bucharest disruption can produce a later direct service, a connection through another European airport, or a materially different replacement journey. Keep each option the airline actually offered, replacement operating carriers, ground transport where relevant and final arrival.
Evidence for a strong OTP file
Journey evidence
- Booking confirmation and ticket
- Boarding passes and check-in proof
- Original and replacement itinerary
- Operating carrier for affected sectors
- Actual final arrival
Disruption evidence
- Delay or cancellation notices
- Airline’s stated disruption reason
- Rerouting, refund and care offers
- Reasonable itemised expense receipts
- Messages and relevant screenshots
Related compensation guides
Bucharest Airport compensation FAQ
Are flights departing Bucharest covered by EU261?
Does Bucharest Airport itself pay flight compensation?
What if an OTP disruption makes me miss a domestic connection?
What if the airline changes my route?
Check your Bucharest disruption
Keep the booking, operating carrier, airline notices, replacement journey, disruption reason and final-arrival evidence together.
