Belgrade Nikola Tesla Airport (BEG) flight compensation: delays and cancellations
Short answer: Do not treat every BEG departure as an EU261 journey: Belgrade Nikola Tesla Airport is outside the regulation's European departure territory. The same route can switch legal answers by direction, with a qualifying operator needed from BEG but not normally for the European-origin leg. On the documented BEG facts, the passenger may still have remedies under Serbia's law, but those remedies and amounts must be checked independently.
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:
The BEG network and legal references were reviewed on 12 September 2026. Current tickets, rather than historic flight numbers, control an individual case.
Before applying a compensation table, write one factual line for BEG: operating airline, origin, final destination and booking reference. For the journey involving BEG, the local examples Air Serbia, Middle Eastern partners, the Balkans and regional feeders help test the record, while the current ticket remains the controlling source.
How the BEG network shapes disruption
The local value of a BEG guide comes from its function as a Western Balkans hub with a large Air Serbia transfer network. Applied to BEG, the current operator mix includes Air Serbia, Wizz Air and European and Middle Eastern partners, across links such as the Balkans, Europe, North America, the Middle East and regional feeders.
On the documented BEG facts, Serbia is not an EU member, but its aviation legislation implements comparable passenger protections through the ECAA framework.
Airlines can suspend or wet-lease a Belgrade Nikola Tesla Airport route after publication. In this BEG claim, the passenger should therefore anchor the claim in contemporaneous ticket and gate records.
The local coordinates of a BEG claim
The presence of Air Serbia or Middle Eastern partners on a BEG confirmation does not settle operational control. On the documented BEG facts, preserve the line beneath the flight number, because codeshare, wet lease and a same-day substitution can place another airline on the aircraft.
The network examples, from the Balkans to regional feeders, create different legal paths through BEG. In this BEG claim, record origin, endpoint and every ticketed connection instead of reducing the case to the name of the city containing the airport.
A clear Belgrade Nikola Tesla Airport case begins with identifiers rather than adjectives: IATA code BEG, city Belgrade, country Serbia, operator and date. That format makes the factual request harder to misunderstand.
Keep the result as a one-line header above the evidence schedule. The airline should be able to identify the BEG operation before reading the legal argument or the amount requested.
For this airport, the working record links BEG, Air Serbia, Middle Eastern partners, the Balkans and regional feeders only where the passenger's own ticket and day-of-travel documents support that connection.
Which regime reaches Belgrade Nikola Tesla Airport?
| Travel pattern at BEG | Carrier in operational control | Working coverage answer |
|---|---|---|
| Journey from the EU/EEA/Switzerland into BEG | Whichever carrier operates | EU261 normally applies from the European departure |
| Flight from BEG to the EU/EEA/Switzerland | Qualifying European airline | EU261 can apply because of the operator |
| BEG to Europe | Local or other non-Operator established in the Union | Do not assume EU261; test the applicable local regime |
| Missed onward flight under one BEG booking | Identify the sector causing the loss | Contract, direction and operator must be read together |
Treat every sector touching BEG as a real flight rather than a city-pair label. For the journey involving BEG, outbound and return legs are separate, and a partner code cannot convert one operator into another.
Coverage only opens the door for a BEG claim. For BEG, arrival delay, cancellation notice, presentation for travel and the causal event remain independent parts of the analysis.
Protect the connection record at BEG
For an EU-origin itinerary connecting at BEG, retain the original reservation and final arrival because EU261 coverage can arise from the starting point and contract. Before combining delays across BEG, verify who sold through transport and whether the carrier rebooked the onward sector as part of the same journey.
If the contract ends at BEG, measure that arrival; if the same ticket continues, use the promised final airport. The reservation boundary must be fixed before counting three hours.
The documents that survive a BEG dispute
The strongest Belgrade Nikola Tesla Airport file connects documents to decisions. In the BEG record, record what the carrier communicated, what choice the passenger made and which expense followed from the disruption.
- airline emails, app messages and photographs of the BEG departure or transfer screens;
- receipts linking necessary food, lodging and airport transport directly to the disruption at Belgrade Nikola Tesla Airport;
- written evidence that the passenger asked for rerouting before purchasing a substitute journey from BEG;
- the original reservation for Belgrade Nikola Tesla Airport, with the PNR and 'operated by' wording visible before any rebooking overwrites it;
- the first boarding pass plus replacement coupons that show how the airline changed the route after BEG;
- For travel through BEG, a chronology tied to Belgrade: notification, airport presentation, replacement offer and access to the final terminal.
If the operator changes its explanation for BEG, preserve both versions and ask which event directly prevented the scheduled operation.
Refund, rerouting, care and the fixed sum at BEG
Coverage decides the currency path at BEG: European scope can unlock Regulation 261's fixed bands, while a non-qualifying departure remains governed by distinct rules in Serbia.
Do not present every BEG loss as one compensation figure. On the documented BEG facts, fixed payment, unused fare, substitute transport and necessary waiting costs have different legal tests.
Before purchasing a costly substitute from BEG, ask the airline for rerouting in writing and preserve its refusal or silence. That sequence makes a later reimbursement demand much stronger.
Apply the test to a realistic BEG journey
A European carrier operates the outbound sector from BEG, but its codeshare partner flies the return from the EU. When recording the BEG event, both may be covered for different territorial reasons, and each causative operator receives its own claim.
One altered fact can reverse the result at BEG; preserve source documents rather than relying on an itinerary summary created after the event.
Send and escalate the BEG claim correctly
Open the BEG claim with one sentence identifying the operating carrier, flight date, route and requested remedy. For the journey involving BEG, follow it with a chronology and numbered evidence rather than a general account of the trip.
Escalation from BEG should match the applicable law and airline participation. In this BEG claim, civil Aviation Directorate of the Republic of Serbia provides the official jurisdictional reference, but national limitation periods and court competence still need separate checking.
Keep the BEG page focused on location and operator. For the journey involving BEG, follow the airport index for another gateway, delayed flights for timing, cancelled flights for transport choices and the calculator for the final estimate.
Why this BEG guide uses the present law
Nothing in this Belgrade Nikola Tesla Airport guide treats the 2026 amendment as immediately operative. For the journey involving BEG, the assessment is fixed at 12 September 2026, before completion of the publication-based waiting period described by the Council.
When recording the BEG event, act on the existing entitlement rather than waiting for reform: retain the booking, timestamps and correspondence, then verify the limitation rule for the competent country.
FAQ
Is a departure from BEG automatically covered by EU261?
Direction and operator decide the answer. European-origin travel to BEG is treated differently from a BEG-origin flight operated by a local airline.
Which airline should receive my BEG compensation claim?
The usual respondent is the carrier in operational control of the affected aircraft. The airport itself answers only for matters within its own control.
Does a missed connection change the BEG delay calculation?
On the documented BEG facts, use the endpoint promised on one reservation and record when passengers could leave the aircraft there. A self-transfer at BEG may instead divide the journey into different contracts.
Does bad weather end every claim involving BEG?
Extraordinary conditions may remove the distance-based payment without erasing every duty. The airline should still explain the causal chain and its response.
What is the most useful evidence to save at Belgrade Nikola Tesla Airport?
A useful bundle shows what was promised and what occurred. On the documented BEG facts, include the complete ticket, operating airline, contemporaneous updates, arrival timestamp and expense receipts.