FAA's nationwide ground stop exposes ageing aviation infrastructure, contractor accountability gaps and a $50 billion overhaul funding dispute
Officials have traced the November 13 nationwide ground stop to a surge of data traffic originating from two routers connected to the Federal Aviation Administration's contractor-operated telecommunications network, but investigators have yet to establish what caused the equipment to generate the traffic. The administration is using the outage to argue for a full rebuild, while Democrats who take control of Congress in January want an accounting of the money already approved.
The Federal Aviation Administration (FAA) halted departures at every U.S. airport for more than four hours on Friday, November 13, after a flood of data on its telecommunications network destabilized radio links and radar feeds at 17 of its 22 en route air traffic control centers, as described in the agency's question-and-answer account. The FAA's command center issued the order at 3:54 p.m. EST (UTC-05). Traffic resumed at 8:15 p.m. EST, the agency reports, and all of the roughly 3,500 aircraft already airborne when departures stopped landed safely.
Three days later, officials can say where the trouble started but not why. Transportation Secretary Sean Duffy has traced the data flood to router work by contractor L3Harris Technologies at a remote radio site in El Dorado, Arkansas, and he has cited the outage in pressing Congress for $50 billion to replace the network outright. That request runs into Democrats who contend that most of the $12.5 billion Congress approved in 2025 has not yet been spent. The ground stop has become an early test of whether a Democratic-controlled Congress will pay for a full rebuild before it gets answers on the failure and on the money it has already provided.
The biggest gap in that account is the root cause. On November 14, Duffy told reporters that investigators were still weighing installer error against a faulty router, adding, "We haven't determined what the fault was." Investigators are also examining why a second router, at an FAA radar site in Amarillo, Texas, that had been replaced about three weeks earlier, began flooding the network too, Duffy told an interviewer on November 15. On the night of the ground stop, he acknowledged that no economic analysis of the disruption had yet been done.
What officials have established is the sequence of the failure, and it shows how quickly a local fault spread. Duffy put the start of the instability in radar and communications at 3:36 p.m. EST, at centers and terminal radar approach control facilities across the country. For about 45 minutes, officials were unsure what was causing it, by the account of FAA Administrator Bryan Bedford. The advisory that followed told operators that all departing traffic should remain grounded "until further notice" and that inbound international flights would be handled case by case.
Behind that timeline was a specific technical failure. The FAA traces the instability to legacy equipment that faltered when data began flooding the network at a rate of 1,000 connection attempts every 4 to 5 seconds. The excess traffic came from the Amarillo radar site and the El Dorado radio site, and the network stabilized after L3Harris blocked both locations, in the agency's telling. "No facilities went dark. Nothing was fully lost," Bedford said on November 14. As a precaution, the FAA disabled the same function on about 60 similar routers.
The El Dorado work places the contractor at the center of the investigation. In a November 15 interview, Duffy described the old copper line at the site as unusable and the switch to fiber as one the telecom provider forced on the FAA, adding, "And that's when we saw the flooding of the network." Asked separately that day whether the FAA would cut ties with L3Harris, he replied that it could not, because the company owns the network the agency operates on. "So I want to get away from L3Harris and get to a new one. But they own the network," he told the interviewer.
The contractor's reply to those remarks has been brief. L3Harris's short November 14 statement described the company as supporting the FAA's investigation and reported that more than 70% of the planned conversion of airspace communications from copper wires to fiber optics was complete, without addressing Duffy's remarks about possible installer error. Two people familiar with the investigation described the installation itself as smooth. In their accounts, an agency employee oversaw the work, and the problems began shortly after service at the facility was handed back to the FAA, which had signed off on it. The Professional Aviation Safety Specialists (PASS), a union representing FAA safety employees, said its technicians were not involved in the upgrades.
Beyond who did the work, its timing has drawn scrutiny. The FAA's answers acknowledge that maintenance at major air traffic control facilities is usually done at night, and the agency has committed to reevaluating when such work is scheduled after the daytime replacement at El Dorado. Duffy defended daytime work at remote sites on the grounds that "the risk, historically, has been very low."
Those few hours on Friday afternoon produced disruption that lasted through the weekend. Airlines canceled about 9,200 U.S. flights on Friday and delayed about 7,500, according to FlightAware data cited on November 14. Of about 20,000 flights still to complete their journeys when the order was issued, 12,000 "were unable to recover," Bedford told reporters the next day. On Saturday, airlines canceled nearly 6,700 flights and delayed more than 9,100, FlightAware reported. Sunday brought some 2,100 cancellations and 9,400 delays in the same data.
After three days of cancellations, the recovery reached most passengers on Monday. By 7 a.m. EST (UTC-05) on November 16, FlightAware counted 533 cancellations nationwide, as air travel largely returned to normal. Bedford had predicted on November 14 that travel would be back to normal by the end of Sunday, declaring that "the worst is behind us." He also apologized for the disruption.
Bedford's apology contrasted with Duffy's stance on responsibility. Asked in a Sunday television interview whether he owed the public an apology, Duffy conceded "it happened on my watch," then added, "But I can't apologize for what was passed off to us." He blamed "20, 25, 30 years of a lack of investment" under both parties. "I don't apologize for shutting down the air space and keeping people safe," he said.
That argument about inherited neglect is the basis of the administration's funding request. On November 12, a day before the outage, Duffy and Office of Management and Budget (OMB) Director Russ Vought asked appropriators for $30.1 billion. Duffy raised that figure at the White House briefing the next night, telling reporters, "I want $50 billion." Homeland Security Secretary Markwayne Mullin described the new figure as an estimate for a "complete overhaul of the system." President Donald Trump joined in on November 15, posting, "Congress must approve."
Part of that pitch rests on the claim that money already provided cannot cover the telecom network. Duffy argued on November 15 that the $12.5 billion in the 2025 law was set aside for radar, radios and new facilities but not for telecom or new software. He named AT&T, Verizon and Lumen Technologies as ready to build a new network that could be finished "by the end of 2028 or possibly the first quarter of 2029." None of the towers upgraded with the earlier money went down, the FAA reports.
Democrats who will soon run the committees handling the request dispute that case. Representatives Rick Larsen of Washington and André Carson of Indiana are the top Democrats on the House Transportation and Infrastructure Committee and its aviation subcommittee. Their November 14 statement counted $4.3 billion obligated and only $1 billion spent in the 15 months since Congress approved the money. "Explain to Congress, again, why they need more money?" they asked. Both are slated to chair those panels next year, when Democrats take control of Congress after their gains in the November 3 midterm elections, according to a November 14 report.
Alongside the dispute over spending, the oversight schedule is already taking shape. FAA and Transportation Department staff are due to brief committee staff on Monday, November 16, on the $30 billion request, and Larsen and Carson expect answers from Bedford at a hearing in early December. Senator Maria Cantwell of Washington, the Democrat poised to chair the Senate Commerce Committee in January, announced that the panel would review how planes communicate through primary and backup frequencies. Representative Jim Himes, a Connecticut Democrat, said, "This is not a Congress money problem," calling it instead "a prioritization problem."
While lawmakers weigh the money, officials have ruled out the newest piece of FAA technology, which drew early suspicion. The agency had announced on November 10 that it was expanding SMART, an artificial intelligence (AI) traffic-planning tool built under an $875 million contract with Air Space Intelligence, to all 22 en route centers. Mullin initially declined to rule out a link. The FAA's answers now describe the two systems as unrelated and report no indication of a cyberattack. Bedford cited "zero evidence of anything AI-related."
With a cyberattack and the AI tool set aside, the outage resembles earlier FAA failures linked to contract work or telecom links. It was only the second nationwide ground stop since the September 11, 2001, attacks, two people at the FAA confirmed. The previous one, on January 11, 2023, followed an outage of the Notice to Air Missions system, and a preliminary FAA review found that contract personnel had unintentionally deleted files. Guy Gratton, an associate professor of aviation at Cranfield University, said that halt lasted 1 hour and 52 minutes. In April 2025, an outage the FAA attributed to telecommunications and equipment issues left screens dark for roughly 60 to 90 seconds at the facility guiding aircraft in and out of Newark Liberty International Airport, according to people with knowledge of the incident.
Unlike those episodes, Friday's failure struck in the middle of a network conversion that is still under way. More than 3,500 of the 5,170 communication lines the FAA plans to convert by 2028 have been replaced, according to FAA data cited on November 16. Duffy dated the flooded routers to a 2001 purchase and called them obsolete by 2006. "But let's not kid ourselves; it will continue to break until we replace it," Bedford warned reporters on November 14.
The statements and flight data released since Friday show where the failure began and how far it spread. They do not show whether a faulty router or a flawed installation caused it, or why a router replaced weeks earlier joined in. L3Harris is running diagnostics on both routers at its headquarters in Florida, with engineers from the FAA and the equipment makers Juniper Networks (now HPE) and Cisco assisting, Duffy posted on X. Those results could help clarify responsibility, and Bedford's expected appearance at the December hearing could show how much of the earlier funding has reached the network. The open question is whether the remaining copper-to-fiber conversions on L3Harris's network can continue without another flood while Congress decides whether to pay for its replacement.
Apple News, Google News, Feedly, Flipboard, and WhatsApp Channel



