I Tracked Every Official Statement on the FAA Ground Stop (Full Breakdown)

One router grounded America. A router upgrade in Arkansas flooded the FAA’s network, 12,462 flights were canceled, and every claim below is labeled confirmed, reported, or alleged.

Friday the 13th. At 3:54 PM Eastern, the FAA stopped every departure in the United States. It was the longest nationwide ground stop since 9/11. The January 2023 one lasted about 90 minutes. About two and a half hours earlier, a tanker on the Mississippi lost its steering and capsized a riverboat carrying 190 people. The day before, Outlook and Teams went dark around the world.

Officials say there is no evidence of a cyberattack. I believe that’s what the evidence shows so far. I also teach science, and I spent my Army career as a medic, so I know the difference between “we haven’t found it” and “it isn’t there.”

So here is the record, and here is what is only reported or alleged. I’ll label which is which.

CONFIRMED means an official source, a transcript, or a government filing. REPORTED means a news outlet said it, often from unnamed sources, and nobody official has confirmed it. ALLEGED means widely believed, never officially admitted.

Grab a coffee. This one is long on purpose. Save it.

Part One: The Timeline

  • Thursday, Nov 12 into Saturday, Nov 14 (CONFIRMED): Microsoft 365 went down for roughly a day or more across 70-plus countries. Outlook, Exchange, Teams, Copilot. Microsoft says it was “a technical issue not related to cyber or AI / agents,” and its preliminary report blames a latent software defect introduced in a July update, combined with two other factors. DHS Secretary Markwayne Mullin said Friday there is “no connection between this and Microsoft.”
  • Friday, 12:26 PM Central, New Orleans (CONFIRMED, NTSB): The tanker Atlantic Asphalt had what the NTSB calls a “steering casualty.” The rudder stayed hard to starboard. At 12:28 it hit the docked riverboat American Heritage. The riverboat capsized in about 22 minutes. 190 people aboard, 140 passengers and 50 crew. 32 taken to the hospital. Everyone accounted for. Nobody died.
  • Friday, about 3:30 to 3:36 PM Eastern (CONFIRMED): Radar and radio started going unstable. Pilots and controllers reported static and transmission problems around Chicago, Indianapolis, and elsewhere. Secretary Sean Duffy, at the White House that night: “At 3:36 p.m., we experienced instability for our radar and our communications and our centers and our TRACONs across the country.”
  • 3:54 PM Eastern (CONFIRMED): Nationwide ground stop. Instability hit 17 of the 22 air route traffic control centers and spread to several TRACONs. More than 3,500 airplanes already in the air were landed safely.
  • About 8:15 PM Eastern (CONFIRMED, FAA): Airspace reopened. Some news timelines put it at 8:19. Either way, call it four and a half hours.
  • The damage (CONFIRMED, FAA): 12,462 flights canceled on Friday. 9,082 of them by the major airlines. Less than two weeks before Thanksgiving.

Side note for my Ohio people: Cleveland Center, the en route center that runs a huge chunk of the sky over the Great Lakes, sits in Oberlin, about half an hour from my house. I have not seen a list of which 17 centers went unstable, so I’m not going to claim Cleveland was one of them. Show me the list and it goes in.

Part Two: What Actually Broke

Here’s the official story, in order, with the receipts.

  • The FAA’s cause (CONFIRMED, FAA Q&A): legacy equipment went unstable when data flooded the FAA’s telecom network, called FTI, “at a rate of 1,000 connection attempts every 4 to 5 seconds.” Two places: a radar site in Amarillo, Texas, and a radio site in El Dorado, Arkansas. The contractor, L3Harris, was installing a new router at El Dorado.
  • Why they were touching it (CONFIRMED, Duffy on ABC’s This Week, Nov 15): El Dorado was mid-cutover from old copper to fiber. The phone company was discontinuing the copper line. Duffy on CBS the same day: “We were forced by the telecom provider to actually update that copper to fiber.”
  • The second site (CONFIRMED, Duffy on ABC): Amarillo had the same kind of upgrade about three weeks earlier. When the new El Dorado router was switched on, the Amarillo system started flooding too.
  • The flood (CONFIRMED, Duffy at the Saturday DOT news conference): “That router that was being replaced as we switched from copper to fiber, it started flooding other routers in our air traffic control system. So, specifically, we had over 1,000 connection attempts every four to five seconds.”
  • How old the routers that choked were (CONFIRMED, Duffy on ABC’s This Week, Nov 15): “those routers were purchased in 2001. They were obsolete in 2006 and we still use them in 2026, just to underscore how old the network is. And the mission we have is to fix it.”

Read that again. Purchased in 2001. Obsolete in 2006. Still holding up the national airspace in 2026.

  • What did NOT break (CONFIRMED, Duffy at the White House, Nov 13): “And our new IP switches did not go down; it’s the old hardware that went down.” The FAA Q&A says the same thing: none of the upgraded towers that got equipment from the modernization money went down.
  • The fix so far (CONFIRMED, Duffy on ABC): the broadcast function has been turned off on 69 routers across the network as a precaution. The FAA’s written Q&A says “approximately 60.” Same move, slightly different count. I’ll use Duffy’s 69 because it’s the newer number, and I’ll fix it if the FAA’s final report says otherwise.
  • Where the evidence is now (CONFIRMED, Duffy on Fox News Sunday): L3Harris has both routers, the Texas one and the Arkansas one, at its lab in Florida for “deep diagnostics testing,” with FAA, Juniper, and Cisco engineers in the room. The FBI and other law enforcement are still involved.
  • Is this the $12.5 billion modernization project? (CONFIRMED, FAA Administrator Bryan Bedford, Nov 14, as quoted by CNBC): “We are constantly replacing 2,000 … Cisco 600 routers with Juniper routers … This is ordinary course of business stuff. This is not part of the … FAA $12.5 billion modernization efforts. So let’s not conflate those two things.”

Now the parts that are only REPORTED. Treat these as leads, not findings.

  • REPORTED (CBS News, anonymous sources): the trouble was limited to Cisco 600-series routers made between 2001 and 2006. CBS also reported “conflicting information,” including that an update to the L3Harris network caused a reboot and then a crash.
  • REPORTED (Bloomberg): the FBI sees no sign of a cyberattack or a crime and is looking at whether a software update caused the outage.
  • What Duffy said about blame (CONFIRMED, Saturday): “So what we’re working to determine was whether we had incompetence, meaning was it user error or install error from L3Harris or did they install a faulty router? We haven’t determined what the fault was.” And: “Our contractor didn’t meet the moment. Or the equipment didn’t meet the moment.”

So: a router flood, at a copper-to-fiber cutover, into hardware that was obsolete when George W. Bush was president. A “software update” might be in the mix. Root cause is not final.

Part Three: How Old Copper Works (A Science Teacher Explains TDM)

On Friday night Duffy said a sentence most people skipped right past: “We have TDM telecom, so this is analog telecom.”

TDM stands for time-division multiplexing. It’s how the phone company squeezed lots of conversations onto one copper line back before the internet ate the world. Here’s how I’d teach it to my students.

Imagine my classroom has one microphone and thirty kids. Instead of passing it around whenever somebody wants it, I put a metronome on my desk. Every tick, the next kid in the seating chart gets exactly one syllable. Tick, kid 1. Tick, kid 2. Tick, kid 3. Around and around, thousands of times a second. Nobody waits long, and everybody gets a turn.

That’s TDM. One line, chopped into fixed time slots that take turns. Every site on the line has to keep the same clock. That’s why the old network is so rigid. The slots are reserved whether anybody is talking or not.

Now here’s the catch. Knock that clock off by a hair, or flood the line with traffic it was never built to handle, and data starts landing in the wrong slots or not landing at all. The radar picture stutters. The radio goes to static. And because a lot of sites share the same switching gear, one problem does not stay one problem.

Engineers call that a common-mode failure. You think you have two independent backups, but they both run through the same box. When the box goes, they both go. Duffy said it himself back on Sept 28, 2026: “We have redundant lines that go through a single point of failure.” In the medic world we’d call that putting the primary and the backup airway in the same bag and then dropping the bag.

The modern stuff works differently. IP networks, the kind your phone and your house use, chop data into packets with addresses on them, and the packets find their own way around a problem. That’s why Duffy’s “new IP switches did not go down” line matters. The weak spot isn’t the new gear or the old gear by itself. It’s the seam where they meet. New fiber and new routers on one side. 25-year-old routers and a 1980s architecture on the other. A gateway in the middle translating between them.

Let me be honest about one thing, because I’d rather fix it myself than have somebody fix it for me. The FAA’s official description so far is a FLOOD of connection attempts and a broadcast function, not a clock failure. TDM timing is how this kind of network is fragile, and it’s why the seam between old and new is where you’d look first. It is my explanation, not an official finding. If the root-cause report says it was something else, I’ll say so.

And this wasn’t a surprise. CBS reported (REPORTED, describing the document) that an FAA-commissioned safety review back in November 2023 called FTI “obsolete,” said it depended on TDM, and warned that an unexpected failure could disconnect facilities “or even an entire regional air traffic control center.” Then the GAO, in September 2024 (CONFIRMED, GAO-24-107001), found the FAA rated 51 of its 138 air traffic control systems “unsustainable” and 54 more “potentially unsustainable.”

Now connect that to Stuxnet, carefully. Stuxnet never touched a telecom network. It went after the motors spinning Iran’s uranium centrifuges, changing their speed while the control screens showed operators normal readings. Different target. Same lesson: the most dangerous failure is the one where the machine tells you everything’s fine.

Part Four: Why I’m Even Asking the Cyber Question

I want to be really clear here, because the Community Notes folks are going to read this slowly, and they should.

I’m not saying this was a virus. I’m saying it’s a possibility, because we have allegedly done something like it ourselves, to Iran.

Here’s the history, labeled.

  • ALLEGED: Stuxnet, discovered in 2010. Malware made Iran’s Natanz centrifuges tear themselves apart while operators saw normal readings. David Sanger of the New York Times reported on June 1, 2012 that it was a joint US-Israeli operation, code-named Olympic Games. Neither government has ever officially admitted it.
  • CONFIRMED: Ukraine, Dec 23, 2015. Hackers cut power to about 225,000 customers. CISA documented it. Ukraine got hit again in December 2016.
  • CONFIRMED: Colonial Pipeline, May 2021. Ransomware. The company shut down the East Coast’s biggest fuel pipeline for days.
  • CONFIRMED: Volt Typhoon. On Feb 7, 2024, CISA, the NSA, and the FBI warned that Chinese state hackers were pre-positioning inside US critical infrastructure, transportation included. Their word: pre-positioning. That means getting in early and sitting quietly until you need it.
  • CONFIRMED, but not connected to this: a worm-like campaign abusing ConnectWise ScreenConnect. Huntress documented it in early September 2026, and CISA added the related vulnerability (CVE-2026-84869) to its Known Exploited Vulnerabilities catalog on Sept 11. Nobody has tied it to the FAA, the tanker, or Microsoft’s outage. I’m not tying it either. I’m listing it because remote-access tools being abused in 2026 is part of the background.

So “it broke on its own” and “someone made it look broken” both have a track record. And if the reporting on Stuxnet is right, we wrote the playbook for the second one.

That’s the whole thesis. Not “it was a hack.” Just: rule it out in writing, with a name on it, and I’ll share the report myself.

Part Five: What the Officials Said (On Tape)

Every time I raise the cyber question, I’m going to put this right next to it. That’s the deal.

  • Duffy, Friday night, White House (CONFIRMED, transcript): “I don’t want to rule out that we didn’t have nefarious activity here, that’s Markwayne and the cybersecurity team that works with us.”
  • Mullin, Friday night (CONFIRMED, transcript): “NSA is working with us; there is nothing that indicates it yet.” And: “There’s no chatter. We haven’t seen any footprints … It appears that this was mechanically driven; however, we’re still looking, so we’re not going to rule that out.” And: “We’ve seen zero evidence that this was … a cyberattack.” Asked about Iran: “we’re not seeing that at all.”
  • Duffy, Saturday (CONFIRMED): “A lot of questions came in yesterday was, was this a cyber attack? Did some foreign nation attack this network? And the answer to that is we don’t believe so. Once we’re able to isolate the work that was being done at this remote location, all of our systems came back online. So we don’t believe this was cyber at all.”
  • Duffy, Sunday on Fox (CONFIRMED): “We think it was the installation or the router that was the bad actor. But we’re open, if we see something else, we’re gonna continue to investigate with our federal partners and law enforcement.” And: “President Trump actually had the whole of government on the phone on Friday. Was anyone seeing footprints? Was anyone hearing chatter? … We have no indication that that was at play here.”
  • The FAA, in writing (CONFIRMED): “Based on all available evidence, we have no indication that this was a cyberattack or an outside nefarious actor.”
  • Duffy, Sunday on ABC (CONFIRMED): “I don’t want to give information before we’re certain.”

Notice the arc. Friday: not ruling it out. Saturday: we don’t believe so. Sunday: no indication, but we’re open. That’s a normal investigation getting more confident as the evidence comes in. It is not a cover-up. It is also not a final report.

The two routers are in a lab in Florida right now with the FBI involved. That’s exactly where they should be. All I’m asking is that when the lab is done, somebody tells us, in writing, whether anybody checked the firmware for tampering and not just for defects.

Part Six: The Riverboat (An Open Question, Nothing More)

I’m putting this in its own section so nobody can say I smuggled it into the FAA story.

  • CONFIRMED (NTSB): the voyage data recorder shows a “steering casualty” at about 12:26 PM Central, with the rudder “remaining to starboard.” The crew sounded the whistle, radioed warnings, and ordered the anchors. It still hit.
  • CONFIRMED: NTSB investigator Bart Barnum, asked what caused it: “It could be many different things. That is something that we are investigating very closely.” Preliminary report expected in about 30 days.
  • CONFIRMED (city of New Orleans, via CNN): As of Monday morning, 4 people were still hospitalized, 1 in serious condition.
  • What NOBODY has said: No official has raised cyber in connection with the tanker. Not the NTSB. Not the Coast Guard. Not DHS. I haven’t found a single one.

So I’m not raising it either, not as a claim. It’s one question for the NTSB: was the rudder failure mechanical, hydraulic, or electronic, and if any part of that steering system is computer-controlled, will the report say whether it was checked?

That’s it. If the answer is “a hydraulic line failed,” I’ll post it and move on. Ships have been losing rudders since before electricity.

Part Seven: To Be Fair

This part isn’t for show. These are the strongest reasons to think I’m overthinking it, and you should weigh them as heavily as everything above.

  • No agency has found evidence of an attack. Not the FAA, DHS, NSA, or FBI. Zero footprints, zero chatter, by their account.
  • The systems came back the moment they isolated the El Dorado work. That’s what you’d expect from a bad install or a bad box. A smart attacker usually doesn’t leave a “pull this plug and it stops” switch.
  • Duffy says this exact kind of work has “been done thousands of times by L3Harris in our network” without this happening. That cuts both ways. It’s why they have to find out what was different here. It’s also why a one-time install mistake is very plausible.
  • Most of these failures really are just mechanical or human. Jan 11, 2023: the last nationwide ground stop came from a contractor who deleted files by accident. March 2024: the Key Bridge in Baltimore went down because the Dali lost power. Sept 19, 2025: Dallas lost its telecom for hours, and the FAA blamed failed redundancies on L3Harris’s watch. Sept 21, 2026: the Philadelphia TRACON lost its primary circuit, and the backup fiber had been cut by a construction crew. No hackers in any of those.
  • Different systems, different owners, different causes so far. Microsoft’s problem was a months-old bug in its own cloud. The tanker was on a river. The FAA’s network belongs to L3Harris. Three bad things on one day is a coincidence until somebody shows it isn’t.
  • Friday the 13th isn’t evidence of anything. I know. I’m a science teacher. Correlation is not causation, and a spooky date is not a mechanism.
  • The FAA’s equipment is old enough to fail on its own. When your routers were obsolete in 2006, you don’t need a foreign intelligence service to explain a bad day. Occam’s razor says start with the 25-year-old hardware.

If the lab report says “bad router” or “install error,” I’ll post that myself, out loud, with the same energy as this article. Pass the crow, I’ll take mine with hot sauce.

Part Eight: The Ask

I’m not saying it was a virus. I’m saying “preliminary” is not “final,” and “no indication” is not “ruled out.” Those are different results, and I grade the difference for a living.

So, to the FAA, DOT, L3Harris, the FBI, and the NTSB:

  • Was the new El Dorado router’s firmware and configuration checked against a known-good image for tampering, not just for defects? Who checked, and will you say so in writing?
  • Was the “software update” Bloomberg reported real? If so, who wrote it, who signed off on it, and was it tested in a lab before it went live on the national airspace?
  • Why did a broadcast function that could flood the whole network stay switched on in 69 routers until after the country was grounded?
  • Why could one remote radio site in Arkansas destabilize 17 of 22 en route centers? Who designed a network where that was possible, and when was that risk first written down?
  • Will the final FAA report include a public cyber-forensics finding, yes or no, with the agency that did the work named?
  • For the NTSB: was the Atlantic Asphalt’s steering failure mechanical, hydraulic, or electronic?

None of that is a conspiracy theory. It’s a checklist. You do a secondary survey even after the obvious wound is packed.

Pop Quiz. No Notes.

  1. What time did the FAA declare the nationwide ground stop?
  2. How many connection attempts was the bad router throwing at the network, and how often?
  3. What does TDM stand for, and what’s it chopping up?
  4. What year were the routers that choked purchased, and what year did they go obsolete?
  5. What did Duffy say about the new IP switches?
  6. Has any official found evidence of a cyberattack?
  7. Stuxnet: confirmed, reported, or alleged?

Answers:

  1. 3:54 PM Eastern.
  2. More than 1,000 every four to five seconds.
  3. Time-division multiplexing. It chops one line into fixed time slots that take turns.
  4. Purchased in 2001. Obsolete in 2006. Still in use in 2026.
  5. “Our new IP switches did not go down; it’s the old hardware that went down.”
  6. Zero evidence so far, per DHS, NSA, FBI, the FAA, and DOT. They say they’re still looking.
  7. Reported by the NYT in 2012 as a US-Israeli operation. Never officially admitted.

If you got 7 out of 7, you know more about Friday than half the cable panels did.

What I’ll Update

The L3Harris lab results. The FAA’s root-cause report. The NTSB preliminary report on the tanker, due in about a month. If any of them changes a single line of this, I’ll change it here and tell you what changed.

Got something wrong? Show me and it goes in.

But what do I know, I’m only a science teacher who teaches that “no evidence yet” is not the same as “ruled out,” and a medically retired Army combat medic who learned never to trust a plan with one point of failure, and never to call a scene clear until somebody actually checked it.

Sources: FAA, “Nationwide Ground Stop Questions and Answers” (Nov 15). White House briefing transcript, Nov 13 (Roll Call

Factba.se

). DOT news conference and Sunday-show recaps, Nov 14-15 (

transportation.gov

). ABC This Week, Fox News Sunday, CBS Face the Nation, Nov 15. CNBC, Nov 14 (Bedford). CBS News and Bloomberg, Nov 13-14 (REPORTED, anonymous sources). NTSB briefing, Nov 15. GAO-24-107001. CISA IR-ALERT-H-16-056-01 and AA24-038A. NYT, June 1, 2012. Microsoft preliminary post-incident report, Nov 16. Huntress on rogue ScreenConnect clients, Sept 2026, and CISA KEV listing, Sept 11.

Mike Borowski is a medically retired Army combat medic with 23 years of service, including a combat deployment to Iraq, and a high school Anatomy and Physics teacher at a high-need Career Technical district in Northeast Ohio — where he also wrote and published the textbooks for both courses. He runs “Bski’s Classroom,” a platform dedicated to cutting through political noise with data, history, and the kind of blunt honesty that comes from someone who has seen both war and the American classroom up close.

—

X (Twitter): x.com/BskiMike22802
Substack: substack.com/@bskimike22802
YouTube: www.youtube.com/@BskiMike22802
AFNN: https://afnn.us/author/mikeborowski/

If you enjoyed this article, then please REPOST or SHARE with others; encourage them to follow AFNN. If you’d like to become a citizen contributor for AFNN, contact us at managingeditor@afnn.us Help keep us ad-free by donating here.

Substack: American Free News Network Substack
Truth Social: @AFNN_USA
Facebook: https://m.facebook.com/afnnusa
Telegram: https://t.me/joinchat/2_-GAzcXmIRjODNh
Twitter: https://twitter.com/AfnnUsa
GETTR: https://gettr.com/user/AFNN_USA
CloutHub: @AFNN_USA

Leave a Comment