Thirty minutes outside Atlanta, the pilot got on the intercom to announce that something was wrong.
A communications issue with the Federal Aviation Administration was cascading across the country. The pilot didn’t offer much detail except to say that the issue might affect gate access and connecting flights.
For Amanda Khera, the timing couldn’t be worse. Her family vacation to a small island off the coast of Belize had already turned into a medical scare when her 22-month-old son Rio developed a high fever and had to be rushed to a local clinic. Exhausted, they were trying to get home to Virginia Beach, Virginia, to see his pediatrician and rest in their own bed. First, they had to connect through Atlanta.
“It was honestly pretty scary,” Khera said. “We didn’t know if the pilot was flying blind without any access to the control towers, or if planes would run into each other.”
“We didn’t know if the pilot was flying blind without any access to the control towers, or if planes would run into each other.”
— Amanda Khera
She had every right to be scared. She didn’t know what was going on in the cockpit or on the ground. She had no idea that pilots are trained to follow strict procedures that minimize safety risks during major air traffic control outages. All she knew was that several recent incidents, including a midair collision over Reagan National Airport in 2025 that killed 67 people, have called into question the safety of America’s skies. So she spent the rest of the descent looking out the window for nearby aircraft.
Her flight landed safely. But she deplaned into a terminal frozen in place. More than 600 flights out of Atlanta, including their connection to Norfolk, had been canceled. And no one knew when they would be able to take off because every flight across the United States had been grounded.
On Friday, November 13, the nation’s air traffic control system began to fail. Around 3:15PM ET, pilots and air traffic controllers in the Midwest started reporting difficulty communicating with each other over the radio.
“We’re 11,000 [feet] over Grand Rapids airport, about nine miles to the west,” said the pilot of Allegiant Flight 547, his transmission already becoming garbled. “Unable to get… contact… approach on any [frequency].”
Four minutes later, controllers at Quad Cities Airport in Moline, Illinois, reported similar issues across the region.
“We’re dealing with some communication issues on a larger scale than we initially anticipated,” said one. “It sounds like Chicago Approach is going ATC zero, so it might be worse than we initially thought. We thought it was just here.”
With communication outages spreading around the country, the FAA issued a nationwide ground stop at 3:54PM ET “due to extraordinary circumstances and for reasons of safety.” From that moment on, no airplanes were allowed to take off in US airspace.
The sudden halt surprised both pilots and controllers.
“Just a heads up, we went in a national ground stop,” said a controller in Seattle.
“Are you saying national as in Reagan National,” asked one United pilot, “or national in the whole country?”
“Across all en route facilities, they’re having communication issues.”
Like so many of the safety incidents that have plagued the air traffic control system over the last few years, this latest failure began with a fragile and outdated piece of FAA infrastructure. In this case, according to the agency, the faulty system was the FAA Telecommunications Infrastructure, or FTI.
Built by defense giant L3Harris in the early 2000s, FTI is the data backbone of the entire air traffic control system. It links more than 4,400 aviation facilities and carries the voice and radar data controllers rely on to keep planes separated, bridging the gap between the FAA’s legacy phone-based transmission systems and modern,Internet Protocol-based ones.
FTI is scheduled to be replaced in 2028. Until then, L3Harris must make incremental upgrades to keep FTI operational.
“We’re dealing with some communication issues on a larger scale than we initially anticipated.”
— Air traffic controller
One of these upgrades accidentally brought down the entire system, according to The Wall Street Journal. Early in the day, L3Harris contractors replaced an old wired telephone switch with a new wireless data router at the FAA radio facility in El Dorado, Arkansas. Once activated, however, the router began to flood the network with hundreds of connection attempts every second.
This may have added enough extra load to the system to degrade the whole network’s performance, according to I-Hong Hou, professor of electrical and computer engineering at Texas A&M University.
Hou explained that telecom networks break pieces of information — radio transmissions or radar coordinates, for example — into data packets small enough to be transmitted over the network and reassembled at the other end.
“When the network is degraded, it may start to lose a small portion of packets,” Hou said. “Since you need all packets to reassemble the data feed, just dropping one out of 10 packets may cause your feed to completely stop.”
Most modern communications apps are built to compensate for packet loss. FaceTime, for example, will blur the video or switch to audio-only to preserve the connection.
Air traffic control doesn’t have that luxury.
“Many NAS [National Air Space] applications … require a highly reliable synchronization source with exceptional stability,” according to FAA technical documentation, which warns that instability may cause widespread failure of critical systems.
FAA technicians believe the El Dorado router’s repeated connection attempts created enough instability within the FTI to cut off radio and radar feeds to 17 of the FAA’s 22 Air Route Traffic Control Centers and several Terminal Radar Approach Controls.
“We sometimes call this a cascading failure, meaning that one failed device can cause nearby devices to fail, and so on,” explained Hou.
“We sometimes call this a cascading failure, meaning that one failed device can cause nearby devices to fail, and so on.”
— I-Hong Hou, professor of electrical and computer engineering at Texas A&M University
L3Harris’s contractors isolated the malfunctioning router and another one at a nearby radar facility in Amarillo, Texas. Once those two routers were taken offline, the network began to stabilize once again.
Four and a half hours later, at 8:15PM ET, the FAA lifted the ground stop. It was the nation’s longest since 9/11, spurring airlines to cancel more than 13,000 flights and delay more than 25,000 more through the weekend, according to FlightAware. And more than 1.5 million passengers were stranded.
Faulty technology created the crisis. The FAA’s hamfisted attempts to reassure the public that everything was okay made the situation worse.
For six hours after the ground stop began, the FAA did not provide any public updates except for a terse, 31-word press release and a single X post. Finally, at 11:30PM ET, US Transportation Secretary Sean Duffy and Homeland Security Secretary Markwayne Mullin held a press conference to explain the day’s events.
Instead of providing clarity, however, they issued confusing and sometimes even contradictory statements. Mullin opened the conference with a joke (“Welcome to Friday the 13th, right?”) before confidently declaring that “there is no cyberattack.” Instead, he appeared to blame the outage on the FAA’s modernization project.
“As Secretary Duffy and FAA was going in and putting patches into the system, they were putting new equipment and new technology, and that new equipment and technology was just overwhelming the older system,” said Mullin.
Mullin’s remark appeared to surprise Duffy, who looked at the ground and shook his head. Mullin later walked the statement back after a reporter’s follow-up question, admitting that “there’s nothing completely certain right now.”
Duffy offered more details but did not exactly give a straight answer. “Our switches and routers actually got overloaded with data, and they went down,” he said. “I shouldn’t say they went down. They started to give us inconsistency in the data from those routers.”
“I don’t want to rule out nefarious activity,” he later added.
“This is what the leadership of President Trump looks like,” Mullin concluded. “We are built to handle crisis like this.”
A follow-up press conference on Saturday afternoon was equally bizarre. It started with piercing audio feedback produced by a faulty microphone, which interrupted Duffy right after he introduced Rebecca Guy, the FAA’s acting chief technology officer.
After a four-minute delay, Duffy continued with the briefing. He floated the potential that contractor “incompetence” had caused the outage. And he demanded that Congress allocate billions more dollars to the FAA so it could complete its modernization efforts — calling its existing $12.5 billion modernization budget a “partial payment.”
The conferences only flamed online rumors that the outage was caused by a cyberattack or a rogue AI tied to the September rollout of the FAA’s new SMART system. (So far, no evidence has emerged for either.)
The problem was compounded by an administration already struggling to command public trust. When cabinet officials offered shifting, improvised explanations from the podium, millions of anxious travelers — and even prominent allies — simply refused to take the government at its word.
“Until proven otherwise, not some presser by our government, I firmly believe this was a DDOS attack,” former National Security Adviser Mike Flynn wrote on X. “This is what was being described by two smart cabinet officials who clearly did not understand the technical nature of what happened.”
Khera and her family didn’t know about the political gamesmanship behind the outage — and frankly, they didn’t care. She just wanted to get out of Atlanta on something other than an airplane.
After a night in one of the last available hotel rooms in Atlanta, she and her family rented a car and drove the nine hours back to Virginia Beach. They made it home late Saturday night.
Because of the FAA’s mishaps, they don’t plan to fly again anytime soon.
“We’ve had enough of planes,” she said. “It will take a couple months and more explanations from the FAA to make sure something like this or worse doesn’t happen again.”
Follow topics and authors from this story to see more like this in your personalized homepage feed and to receive email updates.
- Darryl Campbell
Source: The Verge · Darryl Campbell
At a glance
- Topic
- Technology
- Country
- 🇺🇸 US
- Publisher language
- EN
- Added to Allnira