The Smart Marty Sky Dispatch

Worldwide AviationSmartMarty.ca
Breaking

Duffy and Bedford did not impose FAA ground stop. Here's who did

It was not Transportation Secretary Sean Duffy or FAA Administrator Bryan Bedford who made the decision to halt all departures on Friday, Nov. 13.

Duffy and Bedford did not impose FAA ground stop. Here's who did
Featured aviation image for this report.

A nationwide FAA ground stop occurred on a Friday afternoon as part of a broader review of air-traffic-control communications and modernization efforts, with outbound departures halted across the United States while aircraft already in flight could continue to their destinations under the last issued clearances. Several outlets describe the action as an extraordinary safety precaution tied to ongoing modernization work, rather than a conventional failure event, and note that international arrivals were to be handled on a case-by-case basis.

San Francisco International Airport was highlighted as one of the most visibly affected hubs, grounding more than 30 outbound flights as part of the nationwide measure. Other major gateways, such as Newark Liberty International, were reported as showing a mixed picture where some flights continued while others faced delays or cancellations, reflecting a patchwork of activity across airports during the stoppage. The scope of disruption extended to regional facilities as well, with Chicago’s O’Hare International Airport holding departures in a window around 1:00 p.m. to 2:15 p.m. local time due to thunderstorms in the area, and weather described as mostly cloudy with rain and gusty storms nearby in northwest Indiana.

The root cause of the outage was described by several outlets as tied to a modernization push intended to upgrade copper wiring to fiber for air-traffic-control infrastructure and related communications and surveillance improvements. Investigations and official statements repeatedly framed the incident as a safety review rather than a standard operational fault, with authorities seeking to determine whether the upgrade process, router installations, or weather conditions contributed to the disruption. Initial advisories indicated the pause could extend if conditions or the ongoing investigation warranted it, and there was no publicly announced end time in the earliest reports.

Reporting from NJ.com and corroborating outlets tied the outage to data traffic surges from routers involved in the fiber-upgrade program, including a Juniper device installed at an FAA facility in El Dorado, Arkansas, and additional activity at sites in Amarillo and Abilene, Texas. The intervention halted new outbound departures nationwide while allowing in-flight aircraft to continue under the last clearances, with international arrivals managed on a case-by-case basis as conditions evolved. Investigators described efforts as part of a broader safety and resilience review of the air-traffic-control modernization effort.

Across multiple outlets, observers and authorities cited a telecommunications upgrade, copper-to-fiber modernization, and router deployments—specifically noting an Arkansas router addition as a trigger noted by Fox Business reporting—to explain how a flood of connection signals could disrupt radar feeds and pilot-to-controller communications. The investigation was described as ongoing, with officials aiming to identify root causes and determine whether faulty equipment or installation steps played a role, while confirming the outage affected communications across several facilities.

Transportation Secretary Sean Duffy and FAA representatives characterized the situation as connected to ongoing modernization work and emphasized that L3Harris, the contractor involved in updating routing hardware, was central to the ongoing questions about responsibility. The coverage notes that Duffy criticized the contractor while acknowledging that investigators had not yet determined the exact root cause, and that technicians paused new router installations and disabled a function linked to the outage as part of the ongoing investigation.

In the immediate aftermath, dispatchers and airline operations faced a complex resumption phase, with outbound departures paused nationwide and travelers encountering a challenging rebooking landscape as carriers and passengers adapted to an ATC Zero-style environment. Reports describe tens of thousands of delays and cancellations over the weekend as the industry worked to restore normal operations and reposition aircraft, while officials warned that the pause could be extended if conditions or the investigation warranted it.

CNS Maryland, CP24, KJZZ, and other outlets note that the stoppage persisted for several hours, with lift of the ground stop occurring later in the evening, around 8:15 p.m. Eastern Time, and that international arrivals were being handled on a case-by-case basis during the disruption. The reports also indicate that the grounding affected a broad mix of airports—from major hubs to regional facilities—illustrating the nationwide reach and the complexity of resuming normal air traffic control operations after the pause.

Journals and outlets from The New York Times and The Washington Examiner summarize the broader narrative: no explicit count of injuries or fatalities is provided in the available material, and the primary anchor for timing and context is the fatal plane crash in the Hudson Valley town of Claverack, as reported by the NYT, with the identification of the deceased withheld pending family notification. The NYT description positions that event as a central reference point for the timing of the ground stop, while the Washington Examiner emphasizes who implemented the action rather than who rejected it and notes the lack of further detail about responsibility or scope.

Read the original source

Share this aviation story

Back to aviation news