Widespread operational upheaval unfolded across U.S. commercial airports last Friday, when the U.S. Federal Aviation Administration (FAA) implemented an immediate nationwide ground stop for all departing domestic flights, triggered by cascading instabilities in core national radar and air traffic communications infrastructure. The sudden order left tens of thousands of passengers stranded in airport terminals, as hundreds of scheduled flights were rerouted to alternate landing sites and more than 3,500 total services were fully cancelled within hours of the disruption.
Transportation Secretary Sean Duffy confirmed during a White House press briefing that the system failures first emerged at 3:36 p.m. EST (8:36 p.m. GMT), when data feeds from geographically dispersed radar facilities began returning inconsistent, untrustworthy readings, and two-way communication channels between air traffic control centers and airborne pilots started experiencing intermittent drops. At the moment the ground stop was enacted, over 3,500 commercial aircraft were already in U.S. airspace; all were granted clearance to proceed directly to their pre-planned destinations and land without incident to avoid additional safety risks.
The FAA formally lifted the blanket departure restriction at 8:15 p.m. the same day, but Duffy cautioned that full restoration of regular flight schedules would be a gradual, multi-hour process, as airlines worked to reposition misplaced aircraft, reassign displaced flight crews, and clear the massive backlog of delayed departures. Administration officials strongly advised all booked travelers to verify their flight status directly with their carriers before heading to airports for the following 48 hours.
Remarkably, the U.S. air travel disruption occurred barely 24 hours after a far-reaching global technical outage originating from Microsoft’s cloud infrastructure crippled access to a suite of the company’s flagship productivity tools, including Outlook, Teams, and Copilot, for millions of users across 150+ countries. The Microsoft outage, which kicked off Thursday morning and persisted through the end of the day, generated nearly 130,000 user-submitted problem reports for Outlook alone on outage-tracking platform Downdetector by 1 p.m. local time that day.
The ripple effects of the Microsoft service failure stretched across critical public and private sectors worldwide: in the United Kingdom, a Manchester judge was forced to adjourn an ongoing criminal trial and dismiss jurors entirely after court digital systems went offline; local law enforcement agencies across the country suspended online crime reporting portals and urged members of the public to call in all urgent emergency requests directly; and the UK National Pharmacy Association warned patients to expect significant prescription delays, as NHS system outages prevented general practitioners from sending digital prescription files to local pharmacies. In the U.S., Colorado’s Arapahoe County Sheriff’s Office reported that its online bond payment platform was fully non-functional for several hours during the outage.
Microsoft issued a public apology on official social media channels, noting that its internal investigation traced the root cause to an unforeseen technical flaw in internal infrastructure configuration, and explicitly confirmed there was no evidence of malicious hacking, ransomware, or coordinated cyberattack activity linked to the global service failure. Both U.S. Department of Transportation officials and Microsoft’s public affairs team separately confirmed that there was no established connection between the earlier global Microsoft outage and the subsequent FAA air traffic control system disruption, dispelling widespread unsubstantiated social media speculation that the two incidents were linked.