On the whole, I normally do not get much in the way of opportunity to scribble about the operational aspects of flying (and aviation in general) here in Croatia. Most of the time our pedestrian aviation scene simply doesn’t produce any material worth writing home about, while the country’s mostly pleasant terrain and climate – despite my regular rantings 😀 – also leave little in the way of excitement 🙂 .
On 30 July however, my hand was suddenly forced into action by the arrival of cyclone Melisa, another in an increasingly unusual string of low pressure systems to hit the region of late. Having made landfall on a broad front between the Adriatic towns of Pula and Zadar, Melisa had initially seemed to be a strong – but otherwise generally harmless – rainstorm, which would leave behind the occasional flooded street, but little else. However, news reports from Zadar had quickly revealed that this was no usual event, with the nearby island of Silba receiving 218 liters of rain per square meter in just 24 hours – an amount it normally gets in three months!
The red flags here in Zagreb were already beginning to come up by the time the cyclone had crossed the Velebit mountain range, having been replenished along the slopes by a strong, moist southern wind. Increasing in strength, the core of the storm had started turning slowly towards the city, prompting the Zagreb Airport (ZAG/LDZA) met office to issue a series of increasingly pessimistic TAFs – culminating in the dreaded +TSGR, thunderstorms with heavy hail…
Though the hail had failed to materialize (at the airport at least), the torrential downpour that followed was about to launch ZAG into a world of issues. One of the day’s METAR reports perhaps best illustrates just what was going on out there:
LDZA 301300Z 22038G48KT 0400 R05/0400VP2000N R23/0050VP2000N +TSRA FEW013 BKN030CB 17/16 Q1006 BECMG 05010KT 9999 NSW FEW015 SCT030
In normal-person speak, this reads out to:
- measurement taken at Zagreb Airport on the 30th of the month at 13:00 UTC (15:00 local)
- wind from 220 degrees, speed 38 knots (70 km/h), gusting to 48 knots (89 km/h)
- meteorological visibility 400 meters
- Runway Visual Range (RVR) down RWY 05 varying between 400 and more than 2000 meters, no significant change
- RVR down RWY 23 varying between 50 and more than 2000 meters, no significant change
- thunderstorm with heavy rain
- few clouds at 1300 ft above ground, CBs covering 6/8 to 7/8 of the sky at 3000 ft above the ground
- temperature 17 Centigrade, dew point 16 Centigrade
- QNH 1006 hPa
- weather imminently turning into a wind from 050 degrees, speed 10 knots (18 km/h), visibility greater than 10 km, few clouds at 1500 ft above ground, scattered clouds at 3000 ft above ground (they’d missed badly with this one!)
The first thing to go wrong was the runway midpoint transmissometer (one of three such units that measure RVR). This was not all that unexpected to be honest, since they also have a tendency to fail during heavy snows (and are an endless source of amusement during the winter 😀 ). Pretty soon however, the downpour became so severe that all operations were stopped dead in their tracks, eventually leading to the full closure of the airport (on top of the fact that even before the storm hit, flights were being delayed by 30 minutes due to anti-hale rocket activity in the area).
However, the worst was yet to come. Several minutes later, I was informed by a colleague – who’d been listening in on the tower and ops frequencies – that ZAG had suffered a “complete technical failure”. Tuning to the tower myself, I was to discover that pretty much the entire airspace surveillance system was down; Approach Control, Area Control, the works. Effectively, the whole of the Croatian ATC – with the exception of the individual Towers – had suddenly gone completely blind.
The issue that had caused the problem was later reported to be a leak in the Area Control Center main building, which had allowed rainwater to make it down into the surveillance system’s power supply, shorting it out instantly and plunging the ACC into darkness. While still unconfirmed officially, this had already sparked some local controversy, especially given that the building was purpose-built (at great cost) and commissioned only nine years ago…
EDIT: the cause was later revealed to not be just a mere leak, but a torrent of water that had suddenly flooded the master electronics room (located under the main ACC building). Subsequent reports had put the depth of the water there at between 1 and 1.5 meters…
A far more immediate problem though was the effect this failure was having on the flow of traffic through the country. Unlike its larger neighbors, Croatia has only one FIR – Flight Information Region, the area in which ATC provides its services – which covers its entire territory, and which is further subdivided into six “sectors” for easier management. However, all of these sectors are controlled and managed centrally from the same location, the ACC building at ZAG. With it out of the picture, there was no means to provide any form of control within the country’s airspace, leading Eurocontrol to impose the so called “zero flow rate” *.
* a common misconception is that a zero flow rate is equal to airspace closure. This is not so. When the airspace is closed outright, no flight is allowed to operate in it, be it an airliner, bizjet, private, IFR, VFR, training or any combination thereof. With a zero flow rate on the other hand, Eurocontrol’s Central Flow Management Unit (CFMU) simply does not approve any IFR flight plans that cross the target airspace. So, while the big birds were not allowed in, I could have taken my Skyhawk and gone flying without problems (apart from the rain obviously 🙂 ).
Activated at 13:40 UTC (15:40 local), the restriction was initially specified to last until 15:40 UTC, but was in the event extended to 16:40 and then finally 17:00. With the ACC restored to a minimal operational status, the restriction was lifted at 17:03, allowing traffic to resume using Croatian airspace. However, with the impetus being the get up and running as quickly as possible, the ACC had resumed operations with just three of its six sectors operational, each running at just 25% capacity – with expected effects on delay times…
Within the hour, all six sectors would be up and running, though still at just 25% of their nominal capacity. However, as the technicians worked their spanners off in the ACC, delays had started steadily dropping up until 21:00 UTC (23:00 local) when they dropped below the 15 minute mark and Croatia became grey again 😀 .
Other effects and consequences:
Unsurprisingly, Hungary had borne the brunt of the traffic diverted around Croatia. The high volume of aircraft suddenly crowing their airways – combined with the cyclone’s continued northward path – would cause a cascade effect, causing delays on par with those experienced in Croatia at the start of the storm (glowing bright red on the Network Situation snapshot). However, with only the west of the country affected, things had soon stabilized and delays dropped back to more manageable levels 🙂 .
Back at ZAG, other buildings had also suffered during the downpour. Drainage canals swamped by the sheer volume of water were responsible for the partial flooding of TWY F, ZAG’s only parallel taxiway and the only way to get to the RWY 23 without backtracking along the runway. The passenger terminal had suffered the same fate, though I’m told the flooding was on a very small scale and quickly taken care of…