We covered the Balkan corridor in Issue 04 through the lens of the Ukraine-closure reroute. This issue is about a sharper, more specific risk: Belgrade. Serbian airspace is the natural funnel between Central Europe and Greece, Türkiye, Cyprus and the Middle East. A very large share of IST–Western/Central Europe traffic, and almost all of the Central-Europe-to-IST inbound stream, crosses the Belgrade FIR. That makes Serbia one of the highest-leverage points on the entire Turkish network map.

The problem is that Serbia combines high network leverage with weak strike protection. When Belgrade ACC went to minimum service in 2025, the carriers hit hardest were overflights — the flights that had no Serbian origin or destination and therefore no protection under Serbian law. Ryanair publicly tallied the first two strike days (20–21 August) as disrupting around 99 of its flights and 17,800 passengers, the overwhelming majority of them overflying rather than touching Serbia. (Ryanair)

This is the single most important planning fact in the issue: minimum-service protection is national, and Serbia’s does not extend to overflights. In Italy, Spain and Greece, guaranteed service bands and overflight protection mean a strike degrades but does not sever your transit. In Serbia, a strike can force the network to route around the Belgrade FIR entirely — and the detours (north via Hungary/Romania, or south via North Macedonia/Bulgaria and the Greek FIR) are longer, narrower, and fill up immediately.

For a Turkish operator, that means a Belgrade strike is not a “Serbia problem” to be ignored because you don’t fly there. It is a direct threat to your Western Europe block times and a compounding load on the very Greek and Bulgarian sectors that are already among the summer’s most constrained.

When Belgrade regulates or strikes, traffic redistributes onto two main alternatives. The northern detour routes via Hungarian and Romanian airspace; the southern detour pushes traffic through North Macedonia, Bulgaria and the Greek FIR. Both add track miles and both concentrate traffic into sectors with their own constraints — the southern option in particular dumps additional load onto Athens/Makedonia, which Issue 09 flagged as already carrying 21% of network delay. The Serbian problem and the Greek problem are linked: a Belgrade event makes the Greek picture worse.

Track SMATSA strike notices specifically, even though you may have no Serbian origin or destination — overflights are where the disruption actually lands.

Pre-plan both detour geometries (north via HU/RO, south via MK/BG/Greek FIR) before any confirmed event, and assume the southern option compounds Greek-sector delay.

Build the longer reroute track miles and fuel into the plan on a confirmed strike day rather than absorbing them tactically airborne.

Serbia is the cleanest illustration of a principle this newsletter keeps returning to: the delay that hurts you is often generated in airspace you have no intention of landing in. Belgrade is a small ACC, but it sits on the throat of the Turkish network’s western routes, and its strike law leaves overflights exposed in a way Italy’s and Greece’s do not. The operators who plan around the Belgrade calendar — and who understand that a Serbian strike is also a Greek problem — will protect their Western Europe schedule. The ones who file their normal route and hope will spend late August discovering the southern detour the hard way.

Clearance is published weekly through Summer 2026. Written by Cengehan Vefali, First Officer B737, Istanbul. Data sourced from Eurocontrol Network Manager, CODA delay statistics, and NOP rolling plan publications.

clearanceatfm.com · [email protected]