A cascade of telecom failures at a US Federal Aviation Administration centre on 21 September forced ground stops across the US Northeast and disrupted more than 7,000 flights. By early 22 September, Emirates flight EK203 and Etihad’s EY1 had departed Dubai and Abu Dhabi for New York, signalling that UAE–US trunk routes were largely restored. The glitch—triggered by a severed fibre-optic cable during construction—knocked out a primary and backup communications circuit, stranding aircraft at Newark, JFK, LaGuardia and Boston. UAE carriers weathered the storm thanks to generous schedule buffers on long-haul flights and the availability of spare A380 and B787 crews in Dubai and Abu Dhabi. Still, EK203 left 22 minutes late and ground-handlers warned of possible baggage misconnects for passengers traveling beyond JFK. Corporate travel managers should note that downstream delays often linger for 24-48 hours as crews reset duty limits and US airports clear aircraft positions. Travellers with same-day connections in the US are advised to monitor both operating carriers and airport social-media channels; travel insurers may treat consequential hotel costs as claimable due to a documented “air-traffic-control failure.” The episode also highlights resilience differences between global hubs: Dubai and Abu Dhabi’s ground-handling teams faced minimal knock-on disruption because their own ATC and telecom backbones remained unaffected, underpinning the UAE’s appeal as a transfer point even when origin or destination markets hiccup. For now, the guidance is simple—check your flight status, allow extra time for US immigration queues that could swell as backlogs clear, and keep receipts in case re routing or overnight stays become necessary.
Source: Travels Dubai
