Sofia Airport (SOF) flight compensation: delays and cancellations
Short answer: Use the departure rule first at Sofia Airport: a journey starting at SOF is normally protected by the European framework whatever airline flies it. A third-country departure ending at SOF has a narrower rule, because the aircraft generally must be operated by an eligible European carrier. For travel through SOF, coverage is only the first gate: the passenger must still prove the final delay, cancellation notice or denied boarding and connect it to the flight actually operated.
Free eligibility check
Check your case in the form
Enter your route, date and type of disruption. We will check whether your case qualifies for a claim under EU 261/2004 or UK261.
What happened to your flight?
Claim up to €600 for a delayed or cancelled flight.
Choose the situation that applies to your flight:
Information about Sofia Airport was checked on 12 September 2026. Confirm the live itinerary because airlines and operating arrangements can change.
The local screening line should contain SOF, the aircraft operator and every ticketed endpoint. When recording the SOF event, names such as Bulgaria Air, Turkish Airlines, Europe and Bulgarian domestic routes illustrate the range of possible records at this airport, but only the passenger's own documents establish the relevant combination.
The passenger pattern behind Sofia Airport
Sofia Airport is Bulgaria's principal hub with network, low-cost and regional services. Applied to SOF, the operating mix includes Bulgaria Air, Wizz Air, Ryanair, Lufthansa Group carriers and Turkish Airlines, with journeys commonly linking Sofia to Europe, Türkiye, the Middle East and Bulgarian domestic routes.
For travel through SOF, Sofia has two terminals and airline changes can alter the check-in point; capture the replacement flight details rather than relying on the original booking screen.
Airlines can suspend or wet-lease a Sofia Airport route after publication. On the documented SOF facts, the passenger should therefore anchor the claim in contemporaneous ticket and gate records.
The local coordinates of a SOF claim
Operator checking at SOF should be literal: compare the seller, marketing carrier and the company flying the aircraft. For travel through SOF, the range from Bulgaria Air to Turkish Airlines shows why those roles cannot safely be assumed to coincide.
In the SOF record, likewise, a journey toward Europe is not interchangeable with travel involving Bulgarian domestic routes. Applied to SOF, direction can change territorial scope, route length can change the compensation band, and a common reservation can move the relevant arrival beyond the first hub.
The airport field in a demand should read Sofia Airport (SOF), not a broad regional label. When recording the SOF event, add Bulgaria and the scheduled date so the airline can retrieve the exact operational record.
Keep the result as a one-line header above the evidence schedule. The airline should be able to identify the SOF operation before reading the legal argument or the amount requested.
For this airport, the working record links SOF, Bulgaria Air, Turkish Airlines, Europe and Bulgarian domestic routes only where the passenger's own ticket and day-of-travel documents support that connection.
Direction, operator and the SOF legal map
| Route through SOF | Who actually flies? | Framework to examine |
|---|---|---|
| Aircraft leaves SOF | Operator of any nationality | European territorial scope normally applies |
| Overseas flight into SOF | Carrier qualifying under the inbound rule | The non-European origin can still qualify |
| Arrival from outside the area at SOF | Third-country performing airline | Landing at SOF alone does not create EU261 coverage |
| Multiple sectors sold as one journey through SOF | Name the airline responsible for the connection failure | Through-ticket delay requires both arrival and operator analysis |
Read a SOF itinerary from sector to sector. When recording the SOF event, the company named after 'operated by' is more important to statutory liability than the agency, alliance or loyalty brand used to sell it.
Once Sofia Airport falls within the relevant regime, keep the legal remedies separate: a fixed sum, rerouting or refund, care expenses and baggage damage answer different questions.
One ticket or self-transfer through SOF
On the documented SOF facts, a one-ticket connection through Frankfurt, Munich, Vienna, Warsaw or Istanbul must be separated from a self-transfer before losses are allocated. Ticket number sequence, PNR and baggage destination help separate a protected transfer at SOF from a passenger-created self-connection.
For a protected SOF itinerary, compare scheduled arrival with the time a door opened at the final destination. For the journey involving SOF, runway touchdown, a gate announcement or the departure delay alone can produce the wrong result.
Build a verifiable SOF timeline
A later claim should reconstruct the SOF event minute by minute. Applied to SOF, download the ticket before it changes and preserve contemporary airport and airline updates.
- On the documented SOF facts, planned and actual times for each sector, with runway touchdown kept distinct from door opening at the final airport;
- the first operational explanation, later updates and visible SOF status board before those records disappear;
- dated invoices that identify each meal, hotel night or ground transfer purchased because of the SOF wait;
- In this SOF claim, the written cancellation, denied-boarding or rerouting choice, plus proof of when it was communicated;
- the original reservation for Sofia Airport, with the PNR and 'operated by' wording visible before any rebooking overwrites it;
- digital or paper boarding records for each traveller and sector affected by the Sofia Airport disruption.
For SOF, keep care receipts separate from consequential losses such as prepaid hotels at the destination. The legal basis and evidence burden are not the same.
Do not merge compensation with SOF expenses
The highest fixed amount is not automatic on every long SOF route. For SOF, apply the EUR 250/400/600 distance structure, then account for defined halving rules and any extraordinary circumstances established by the airline.
A cancellation at Sofia Airport requires an informed transport choice before any voucher is accepted. When recording the SOF event, record whether the airline offered cash, the earliest replacement and later travel on the passenger's chosen date.
If the SOF carrier supplies no workable care, buy only what is necessary and proportionate, keep itemised receipts and explain why waiting for the airline was no longer reasonable.
Worked outcome for a journey touching SOF
Suppose a non-EU airline operates a flight out of SOF and delivers the passenger four hours late after an internal scheduling failure. Applied to SOF, the covered European departure supports the territorial test even though the carrier is foreign.
The point of the SOF comparison is not to guarantee recovery. For the journey involving SOF, it shows why route direction, operator and final arrival must be fixed before a monetary demand is calculated.
Name the respondent before filing from SOF
For SOF, begin with a traceable written airline submission. Applied to SOF, keep the confirmation number, the exact attachments and a copy of the form text because portals can later hide what was sent.
Escalation from SOF should match the applicable law and airline participation. For the journey involving SOF, bulgarian Civil Aviation Administration provides the official jurisdictional reference, but national limitation periods and court competence still need separate checking.
A SOF assessment can be cross-checked against the airport hub; use the separate pages for delayed arrival, cancelled travel and amount calculation.
Current rules, not future rules, for SOF
This SOF analysis uses the law in force on 12 September 2026. Although the EU adopted amendments in July 2026, the Council describes a later application point after publication plus 12 months and 20 days; those future procedures are not applied to today's Sofia Airport file.
For the SOF traveller, the conservative course is immediate record preservation followed by a traceable claim under today's framework, with any civil time limit checked separately.
FAQ
Does EU261 cover every flight departing from SOF?
Airline nationality normally does not remove a SOF departure from EU261. In this SOF claim, a claimant nevertheless needs the ticket, travel presentation and facts supporting the requested remedy.
Who is responsible for a codeshare disruption at SOF?
A codeshare does not transfer liability to the most familiar brand. In the SOF record, send the passenger-rights demand to the actual operator and the booking-service issue to the relevant seller.
Which arrival time counts after a connection through SOF?
The final ticketed airport may supply the relevant delay on one reservation. Do not assume that flights displayed together by a search engine are contractually linked.
Can the airline reject everything by citing weather at SOF?
Extraordinary conditions may remove the distance-based payment without erasing every duty. The airline should still explain the causal chain and its response.
Which documents strengthen a SOF claim?
Retain the complete e-ticket, operating-carrier entry, original and replacement boarding passes, airline notices, SOF display photographs, final-arrival time and itemised receipts.