Flight Delay and Cancellation Rights in Bulgaria

Immediate duties in a Bulgaria-connected disruption

Write each unresolved item on a separate line: assistance, unused travel, replacement travel, extra expense and compensation assessment. This lets the airline answer precisely and shows which issue may require a national complaint or court route.

Evidence for a Bulgaria-connected case

• Complete booking with origin, destination and connection structure
• Operating carrier and flight number for every affected sector
• Scheduled and actual final-arrival times
• Cancellation or delay notice and reason given
• Replacement itinerary, refund record and care receipts
• Submission acknowledgement and airline response

The catalogue currently links Bulgaria with 2 airline or airport entities. Those relations aid navigation but do not prove that a particular carrier or route operated on the travel date.

Verify the deadline that applies in Bulgaria

Time limits and procedural routes can differ by jurisdiction and type of action. Do not assume that a deadline quoted for another country applies in Bulgaria. Preserve the travel date and submission history, then verify the current official rule before relying on ADR, a regulator complaint or court proceedings.

Choose a proportionate next step

Ask for a written decision that addresses the route, carrier and remedy requested. If the response is incomplete, identify the unanswered point before escalating. The appropriate national body may offer information or complaint handling, but its competence and binding power should be verified.

Questions unique to a Bulgaria-connected itinerary

A clean Bulgaria assessment uses a short jurisdiction table: travel direction, operating carrier, applicable passenger-rights regime, airline claim channel, possible national forum and verified deadline. Fill only the rows supported by evidence. The catalogue links 2 entities to BG, but current routes and carrier procedures still require independent confirmation.

Check official rules before filing

This catalogue record uses country code BG, regime marker eu and verification date 2026-07-19. It does not replace current official legislation, court interpretation or national procedure. Confirm the rule and deadline before filing. Eligibility and payment are never guaranteed.

Country context is not the same as automatic coverage

Bulgaria is catalogued in the EU passenger-rights framework. Departures from the country are normally screened under EU261 regardless of carrier nationality, while inbound journeys may depend on the operating carrier unless already covered from departure. National procedure can still affect complaint routes and deadlines.

Flights departing from Bulgaria

Use the first airport on the protected ticket, not the passenger's residence or the place where the booking was purchased. For a departure in Bulgaria, preserve each sector and carrier. A connecting itinerary should be assessed as booked rather than reduced to the country name alone.

Inbound coverage can depend on carrier status

Do not assume that every flight landing in Bulgaria is covered by the same rule. The operator's status and the journey's departure point can matter. Preserve code-share information and the full ticket so the inbound route can be assessed correctly.

Airline nationality versus route direction

Use carrier nationality as one factor in a structured screen: departure location, arrival location, operator and one-booking connections. This avoids treating every disruption connected with Bulgaria as governed by identical rules.