On a Friday afternoon in mid-November, the nation's skies went quiet when the Federal Aviation Administration halted nearly every departing flight in the United States, citing a temporary telecommunications failure and what it called extraordinary circumstances. It is a rare thing for a system built on constant motion to simply stop, and the stillness exposed how much modern travel rests on old wires and older machinery. Officials insisted no cyberattack lay behind the halt and that no one aboard was ever in danger, while the coincidence of a separate Microsoft disruption drew attention that b
FAA Lifts Nationwide Ground Stop Blamed on Telecom Outage; Microsoft Denies Link to Its Service Disruption
Nearly every departing flight in the United States stopped
Why does this one stand out? Ground stops happen.
Not like this. Nearly all departures nationwide halted, and it's only the second nationwide stop since September 11, 2001.
What did officials say caused it?
A temporary telecommunications outage. Duffy described it as a communication issue affecting all Air Route Traffic Control Centers.
Worth noting that's a description of the symptom. Nobody has said what actually failed or why.
And Microsoft was having problems the same day?
Yes, a Microsoft 365 disruption. Microsoft says it has no indication of any link to the FAA stop.
Careful with that wording. It's "no indication," not a finding that they're unrelated. It's Microsoft's statement, not an investigation's result.
What about a cyberattack?
Mullin said officials haven't seen one, and that passengers were never in danger.
"So far" is doing real work in his sentence. That's an early assessment, not a closed case.
And Duffy's point about old systems?
He called the air traffic control system incredibly old and listed needs like new towers and communication networks.
That's his argument about the system generally. The reporting doesn't show the old equipment caused Friday's outage.
Le Pouls
- At shortly before 4 p.m. Eastern on November 13, the FAA abruptly froze nearly every departure across the country.
- Thousands of passengers sat stranded in terminals as the stoppage dragged on for hours with explanations arriving in fragments.
- Officials scrambled to name the cause, first pointing to a communication problem, then a temporary telecommunications outage.
- Microsoft's concurrent service degradation sparked suspicion, and both the company and officials rushed to deny any connection.
- The ground stop lifted Friday night, but Microsoft's health page still warned of connection failures for Microsoft 365 users.
- Transportation Secretary Sean Duffy is turning the crisis into a push for new towers and communication networks.
On a Friday afternoon in mid-November, the nation's skies went quiet when the Federal Aviation Administration halted nearly every departing flight in the United States, citing a temporary telecommunications failure and what it called extraordinary circumstances. It is a rare thing for a system built on constant motion to simply stop, and the stillness exposed how much modern travel rests on old wires and older machinery. Officials insisted no cyberattack lay behind the halt and that no one aboard was ever in danger, while the coincidence of a separate Microsoft disruption drew attention that both companies moved quickly to dismiss. What remains is a question about how the country keeps its aircraft safely apart, and whether the infrastructure beneath that work will be renewed before the next silence.
Shortly before 4 p.m. Eastern on Friday, November 13, the Federal Aviation Administration stopped nearly every departing flight in the United States. The agency's advisory cited "extraordinary circumstances and for reasons of safety," and thousands of passengers found themselves stranded as the halt stretched for hours.
The explanation came in pieces. Transportation Secretary Sean Duffy first described a communication problem affecting all Air Route Traffic Control Centers. The FAA then called it a temporary telecommunications outage, saying flights were stopped out of caution and that every aircraft had been accounted for.
The timing invited suspicion, since Microsoft was dealing with its own global disruption affecting Microsoft 365 users. The company said it had no indication its problems were related to the FAA stop, and its health page still showed degradation that evening.
The ground stop was lifted Friday night. Homeland Security Secretary Markwayne Mullin told reporters at the White House that passengers were never in danger and that there was no sign of a cyberattack. Duffy seized the moment to argue for investment, calling the air traffic control system "incredibly old" and pointing to the need for new towers and better communication networks.
The event is rare, the second nationwide ground stop since September 11, 2001. Coverage also noted that the FAA had recently launched a new AI air traffic tool, though officials did not cite it as a factor. What comes next is whether the agency explains exactly what failed, and whether Duffy's call for new infrastructure becomes a concrete funding effort.
Shortly before 4 p.m. Eastern on Friday, November 13, the Federal Aviation Administration stopped nearly every departing flight in the United States. An advisory from the agency's Air Traffic Control System Command Center, obtained by FlightRadar24, said the move came under "extraordinary circumstances and for reasons of safety." Thousands of passengers were left stranded as the stoppage ran for hours.
The explanation arrived in pieces. Transportation Secretary Sean Duffy pointed to "a communication issue impacting all Air Route Traffic Control Centers." The FAA then said there had been a temporary telecommunications outage, and that flights were halted out of an abundance of caution. The agency said every flight had been accounted for, and that international flights would be handled case by case.
The timing raised an obvious question. Microsoft was in the middle of its own global service disruption, one that was still affecting Microsoft 365 Business and Enterprise users. The company moved to separate the two events. In a post on X, it said it had no indication that the FAA's nationwide ground stop was related to any Microsoft services. A spokesperson gave a similar line in a statement to People magazine.
Microsoft's own problem had not been resolved. Its service health page, last refreshed at 10:00:36 PM UTC on Friday, still reported a degradation and warned that users might be unable to connect to multiple Microsoft 365 services.
The ground stop was lifted Friday night. Minutes afterward, Duffy and Homeland Security Secretary Markwayne Mullin spoke to reporters at the White House. Mullin said passengers were never in danger during the stoppage. He repeated that officials had seen no sign of a cyberattack, saying, "So far, what we've seen, there is actually no cyberattack." He also said the grounding was not linked to the Microsoft outage.
Duffy used the moment to make a case about infrastructure. As quoted by The New York Times, he blamed "an incredibly old air traffic control system." He described investments the system needs, including new air traffic control towers, wider infrastructure upgrades and better communication networks.
The event is rare. Friday's stop was the second nationwide ground stop since the September 11, 2001, terrorist attacks.
One other thread surfaced in coverage. The FAA had launched a new AI air traffic tool days before the grounding, which prompted questions about whether it played a role. The officials' stated cause, a temporary telecommunications outage, did not involve it, though the reporting here does not address the question directly.
What to watch next: whether the FAA explains what failed in its communications link, and whether Duffy's call for new towers and networks turns into a concrete funding push.
Citations marquantes
So far, what we've seen, there is actually no cyberattack.— Markwayne Mullin, Secretary of Homeland Security
We have no indication that the FAA's nationwide ground stop is related to any Microsoft services.— Microsoft, in a post on X