Skip to content
← Back to feed
Ben Ray Lujan (D-NM)
Ben Ray Lujan
Democrat·New Mexico

Luján, Commerce Committee Democrats Demand Clear & Fact-Based Answers From DOT, FAA on Root Cause of Nov. 13th Nationwide Ground Stop

“Modernization cannot come at the expense of operational safety.” Washington, D.C. – U.S. Senator Ben Ray Luján (D-N.M.), a member of the Senate Commerce, Science, and Transportation Committee,joined Ranking Member Maria Cantwell (D-Wash.), and all Democratic Committee members in a letter to Department of Transportation (DOT) Secretary Sean Duffy and Federal Aviation Administration (FAA) Administrator Brian Bedford demanding clear, fact-based answers about the root cause of last Friday’s nationwide ground stop. The DOT and FAA leaders have blamed a router malfunction in Arkansas and FAA contractor L3 Harris’ work converting the FAA’s communications network from copper to fiber for the disruption. “The Department of Transportation (DOT) and FAA must explain how this failure occurred and identify the corrective actions and oversight needed to prevent a recurrence,” the Senators wrote. “Identifying the device that failed does not establish why it failed. FAA must investigate further to determine the root cause and report to Congress on how it intends to prevent future issues.” According to information provided by L3 Harris, the Senators learned that the copper-to-fiber transition involves converting more than 3,600 routers to Juniper devices. To date, according to the contractor, 400 devices have been installed and 69 are operational.  While a small sample of the Juniper routers were tested before installation, the Senators expressed concerns about continued deployment of the new routers until the root cause of the failure has been identified. “We request an immediate pause on the deployment of additional Juniper devices,” the Senators continued . “Deployment should resume after the FAA demonstrates the devices’ readiness for safe deployment through improved operational testing, independent validation, verified failover capability, and rollback procedures. Congress expects a briefing on these improvements before the FAA resumes deployment of the routers.” The letter comes as Duffy and Beford are demanding $50 billion in funding for air traffic control modernization, up from a request for $30 billion just last week and after prior outages earlier this year in Philadelphia Terminal Radar Approach Control and Minneapolis Air Route Traffic Control Center. “DOT, FAA and OMB must provide Congress with a complete account of what happened and how additional funding would address the vulnerabilities presented on November 13,” the Senators wrote. “Congress deserves clear answers on how the FAA is ensuring the safety of the aviation system for the traveling public while these new systems are being deployed.” “Modernization cannot come at the expense of operational safety,” they concluded. Along with Luján and Cantwell, the letter was signed by U.S. Senators Tammy Duckworth (D-Ill.), Amy Klobuchar (D-Minn.), Brian Schatz (D-Hawai’i), Ed Markey (D-Mass.), Gary Peters (D-Mich.), Tammy Baldwin (D-Wisc.), Jacky Rosen (D-Nev.), John Hickenlooper (D-Colo.), John Fetterman (D-Pa.), Andy Kim (D-N.J.) and Lisa Blunt Rochester (D-Del.). The text of the letter can be found below and HERE . November 16, 2026 Dear Secretary Duffy and Administrator Bedford, The November 13 nationwide ground stop disrupted air travel across the country, eroded public trust in our aviation system, and raised serious questions about the Federal Aviation Administration’s (FAA) ability to ensure reliable and resilient operations. Congress expects clear, fact-based answers about the root cause of this disruption and why existing safeguards failed to prevent it. The Department of Transportation (DOT) and FAA must explain how this failure occurred and identify the corrective actions and oversight needed to prevent a recurrence. Based on information provided to our offices from L3 Harris, the copper-to-fiber transition involves converting 3,648 routers to Juniper devices. To date, it is our understanding that 400 devices have been installed, and 69 are operational. With thousands of conversions remaining, FAA must address outstanding safety and reliability concerns before expanding installation. Identifying the device that failed does not establish why it failed. FAA must investigate further to determine the root cause and report to Congress on how it intends to prevent future issues. We understand the FAA Technical Center tested a sample of Juniper devices before installation. The devices passed pre-deployment testing. The November 13 failure raises serious questions about whether that testing adequately reflected operating conditions or evaluated all potential failure modes or outcomes. We request an immediate pause on the deployment of additional Juniper devices. Deployment should resume after the FAA demonstrates the devices’ readiness for safe deployment through improved operational testing, independent validation, verified failover capability, and rollback procedures. Congress expects a briefing on these improvements before the FAA resumes deployment of the routers. The ground stop demonstrated a breakdown in a system Americans rely on, and Congress was left to piece together critical facts. We expect accurate information as soon as it is available. Concerningly, the DOT attributed the November 13 network disruption to “old switches [and] old routers,” when in fact the deployment of the new Juniper routers seem to be the problem. This discrepancy between the FAA’s contractor and the DOT further fuels our concern that the root cause of the disruption has not yet been identified, leaving the potential for another failure. The DOT and FAA have assigned blame to L3 Harris and used this moment to call for $50 billion in funding for Brand New Air Traffic Control System (BNATCS). This is notably $20 billion more than the request from DOT and the Office of Management and Budget (OMB) that was sent on Thursday, November 12. DOT, FAA and OMB must provide Congress with a complete account of what happened and how additional funding would address the vulnerabilities presented on November 13. DOT and FAA must also take full responsibility for managing contractors working to modernize the NAS. Congress deserves clear answers on how the FAA is ensuring the safety of the aviation system for the traveling public while these new systems are being deployed. Further, we request a joint technical briefing with FAA, L3Harris, and Juniper, and the following information no later than November 23, 2026: An initial safety assessment of operational Juniper devices in the NAS, identifying shared infrastructure dependencies and common points of failures, vulnerabilities in primary and backup telecommunications paths, and the adequacy of failover, rollback, and recovery procedures. An explanation of why the FAA’s operational systems lacked sufficient redundancy to recover immediately from the November 13 outage An explanation of how a cut fiber-optic line or other localized telecommunications failure could result in widespread operational disruption, including actions taken to reinforce network redundancy following the Philadelphia Terminal Radar Approach Control and Minneapolis Air Route Traffic Control Center outages. Given recent events, Congress is concerned about the FAA’s oversight of the BNATCS program. Modernization cannot come at the expense of operational safety. We expect a prompt response and look forward to working with the FAA to ensure the safety, reliability, and resilience of the NAS. We are grateful for the air traffic controllers, pilots, flight attendants, and all aviation workers who continue to be impacted by Friday’s events. Sincerely, ###

Source: https://www.lujan.senate.gov/newsroom/press-releases/lujan-commerce-committee-democrats-demand-clear-fact-based-answers-from-dot-faa-on-root-cause-of-nov-13th-nationwide-ground-stop
Captured:
Last seen live:
Record ID: 6ce3eb39-b665-49dd-81fb-859bfd512362

Issued within 24 hours

Other senators' releases published in the day before or after this one.