
One misbehaving router at a remote site helped freeze America’s skies within minutes.
Story Snapshot
- Transportation Secretary Sean Duffy tied the outage to L3Harris copper-to-fiber work and a rogue router.
- More than 1,000 connection attempts hit every four to five seconds during the event, officials said.
- The Federal Aviation Administration issued a nationwide ground stop around 3:36 p.m. Eastern.
- Seventeen of twenty-two en-route centers felt effects as communications and radar feeds stumbled.
What Triggered The Ground Stop
Transportation Secretary Sean Duffy said a contractor, L3Harris, was switching lines from copper to fiber when a router began to flood other routers. That flood disrupted air traffic control communications with aircraft and interfered with radar feeds. The Federal Aviation Administration imposed a nationwide ground stop as a safety step after the system became unstable. Duffy said investigators still needed to determine whether the issue was an install error or bad hardware.
Duffy gave a striking data point on the abnormal traffic. He said the system saw more than 1,000 connection attempts every four to five seconds. That pattern is consistent with a device caught in a loop or misconfigured to retry at a rapid pace. The behavior would strain control-plane resources and can cascade across connected nodes. The pressure on voice links and radar feeds made controllers lose trust in the data, which forced the pause.
How A Local Change Spilled Nationwide
Officials said the Federal Aviation Administration ordered the stop at about 3:36 p.m. Eastern on November 13, 2026. Reports cited disruption across 17 of the 22 en-route centers that manage high-altitude flights between airports. That reach shows how backbone links connect facilities and share routing paths. If a core device sprays connection requests or malformed sessions, upstream routers can choke, timers can expire, and failovers can flap, turning a local problem into a national one.
Major outlets echoed the core account. Coverage described the copper-to-fiber work, named L3Harris, and focused on the router flood that hit communications and radar feeds. Reports noted that officials did not yet say whether the cause was installer error or a defective device. That split matters for accountability, but in both cases the mechanism is the same: an equipment event created a flood, which stressed the network and forced a safety halt.
Why Safety Demanded A Hard Stop
Controllers need steady communications with pilots and clean radar tracks to separate aircraft. When those tools wobble, risk rises fast. The ground stop buys time to stabilize links, confirm data integrity, and avoid bad clearances. Duffy framed the stop as a precaution in line with standard practice when systems degrade. That choice reflects a simple rule in aviation: when in doubt, slow down and verify. The inconvenience hurts, but the alternative can kill.
Large flight counts made the ripple effects severe. Airlines need aircraft, crews, gates, and maintenance to line up like gears. A nation-scale pause knocks those gears out of sync. Recovery takes days as crews time out and planes miss rotations. The numbers climbed into the thousands of delays and cancellations, which is exactly what you expect when en-route centers stumble together for hours.
What This Reveals About The System
The event fits a pattern that watchdogs have flagged for years: one technical fault exposes deeper fragility. The Government Accountability Office found that over three quarters of the Federal Aviation Administration’s 138 air traffic control systems were unsustainable or potentially unsustainable after the 2023 shutdown review. That backlog means upgrades happen on live, old systems, where change control and redundancy must be airtight to avoid nationwide pain.
Common-sense priorities line up here. First, lock change control. No live swap should push unstable traffic into the backbone without a clean rollback path and staged isolation. Second, harden the core. Critical routers need strict rate limits, peer filters, and lab-tested configs before any field cutover. Third, prove resilience. Drill failovers and publish timelines so the public sees that safety, not spin, drives each call. The facts so far point to that path, and the system should follow it.
Sources:
npr.org, transportation.gov, abc7.com, bbc.bm, thenewstribune.com, ca.news.yahoo.com














