FAA names no cause for its nationwide ground stop, and Hacker News weighs the theories

The FAA ordered every departing flight at US airports held on the ground at 3:54pm ET on Friday 13 November (9:54am NZDT on Saturday 14 November), and hadn’t named a cause by about 4:30pm ET. Its command centre advisory cites “extraordinary circumstances and for reasons of safety”. Transportation Secretary Sean Duffy said on X the stop followed “a communication issue impacting all Air Route Traffic Control Centers”, the facilities that guide planes at cruising height.

The Hacker News thread on the order had 337 points and 114 comments when this was written. Commenters offered a failed telecom link, a radar data fault, the FAA’s new AI tool, a cyberattack and a date bug. Each theory is set out below with what the sources say about it, kept apart from what the FAA and Duffy have confirmed.

What the FAA and Duffy have confirmed

The advisory reads: “ATTENTION ALL AIRCRAFT OPERATORS, BY ORDER OF THE FEDERAL AVIATION COMMAND CENTER ALL AIRPORTS ARE GROUND STOPPED.” Inbound international flights “WILL BE MANAGED ON A CASE BY CASE BASIS”. The event window runs from 2053 UTC on 13 November to 0400 UTC on 14 November (5pm NZDT), but departures stay stopped “UNTIL FURTHER NOTICE”. Planes already in the air were allowed to continue, The Contrail reports.

Before the national order, the FAA’s status feed listed ground stops at O’Hare and Midway for “equipment outage”. CBS Chicago says the command centre’s alert on those stops mentions “comms issues”. Duffy added that “FAA technicians are investigating the issue.” Neither he nor the FAA has given a cause or an end time. SecurityWeek says federal officials haven’t identified what triggered the problem.

Where the theories stand

Theory	Who says it	What the sources show
Communication issue at all route centres	Duffy	Stated by Duffy on X.
Frequency outages at several centres	Washington Examiner, The Air Current	Reported by those outlets. The FAA hasn’t confirmed it.
A failed telecom link to the radio sites	inamberclad, spaceywilly, pests	Commenters’ claim. It matches how the AP described September’s outage. No source ties it to today.
A radar data pipeline fault	toomuchtodo	Commenter’s claim. The linked Sunhillo paper is a March 2025 vendor document and doesn’t mention today.
The FAA’s SMART AI tool	joshbuddy, jbredeche, jumploops	Commenters’ claim. The FAA says SMART only recommends. No source ties it to the outage.
A cyberattack	deadbabe	Commenter’s claim. The FAA hasn’t said whether it suspects one.
A date bug	gordonfish	Commenter’s claim, challenged in the thread.

What outlets report about frequencies

Washington Examiner reporter Anna Giaritelli posted notices describing a nationwide stop “due to widespread frequency outages”. MLQ.ai says the Examiner, citing two FAA employees, reported a “rolling frequency outage” at facilities that track aircraft in flight. Commenter mmooss shared the same notices, which they described as “a claimed photo of FAA documents”. Bloomberg, quoted by colechristensen, relayed The Air Current’s report that the stop came “due to several impacts to ATC Frequencies and/or Radar capabilities”, and that the command centre had no further information on the “timing or cause of this outage”. The FAA hasn’t confirmed any of this.

Animats pasted what they said was a later advisory: “DCC HAS IMPLEMENTED EXTENDED FLIGHT PLAN DROP TIMES TO 240 MINUTES FOR ALL ENROUTE CENTERS DUE TO NATIONWIDE COMMS FAILURE.” That is Animats’ transcription, and none of the news outlets quoted here repeats it.

Can radio fail nationwide?

PLenz opened the thread’s main argument at 21:19 UTC: “It seems the ATC radio system went down across the country.” anamexis objected: “ATC just uses basic AM radio for radio comms.” lxgr’s reply was that the radios “are no longer connected to the controller’s microphone via a long cord anymore”. spaceywilly went further: “They use third party telecom providers to relay communications between ATC ‘centers’ and remote radio transmitters. It is not purely AM radio and outages have occurred in the past, most recently in September.” pests said “the control rooms are separate from the actual antennas / areas being served”, and inamberclad wrote: “Probably a telecom issue. Most radio transmitters are operated over phone or Internet from a remote station.”

The September outage is documented. The AP reported that on 21 September the Philadelphia facility lost both its primary and backup data lines at once, leaving controllers without radar or communications for hours. That supports the general point that radio sites depend on leased lines. It doesn’t show that lines failed today. toomuchtodo took a narrower guess, “Radar multiplexer pipeline, or some component of it, is likely down”, and linked a Sunhillo paper on moving FAA radar data from leased T1 lines to internet links. The paper is dated March 2025 and says nothing about this outage.

The AI tool theory

joshbuddy linked Gizmodo’s report on the FAA’s $875 million SMART tool (Strategic Management of Airspace, Routes and Trajectories) and wrote “I’m sure this isn’t related.” bbor replied that “If true and this ends up lasting an hour or more, that’s going to be undeniably, objectively hilarious”, then added that the outage “could just be the first issue that’s arisen” because the FAA announced the nationwide rollout on Tuesday. jbredeche and jumploops raised the same link.

The pushback came with specifics. sigmarule noted the FAA began testing SMART in Washington in September and announced the national rollout three days ago, and that the FAA says a team of specialists in Washington validates its output before it reaches facilities. They added a doubt of their own: the FAA could be “overstating the level of human oversight/HIL”. dysoco wrote: “I really doubt something announced yesterday went into effect today.” ceejayoz quoted Gizmodo’s line that the FAA has reassured the public SMART “only suggests routes and doesn’t affect air safety”, and answered: “Seems unlikely.”

The record backs the commenters’ timeline. The FAA’s 10 November statement, as Ars Technica reports it, says the FAA “will now use SMART in the airspace of all 22 centers across the country”. The AP reports limited operations began in Washington on 21 September. The National Air Traffic Controllers Association told Flying Magazine it wasn’t involved in SMART’s design, testing or implementation, per Gizmodo. The FAA hasn’t said whether SMART is live at any centre that lost frequencies, and no source connects it to the outage.

Cyberattacks, a date bug and the base rate

deadbabe declared “This is it, massive cyberattack on the USA.” soundworlds answered: “I’ve worked in IT long enough to know it is 99/100 times an internal glitch or misconfiguration, not hackers.” underseacables took the opposite view: “First Microsoft, then anthropic, now ATC radio. Something big is going on.” temp0826 replied with “Hanlon’s razor”. The Microsoft 365 outage is real; it’s covered in an earlier post, and no source reviewed links it to the FAA.

Two commenters framed it as politics. testtestmetest predicted “an AI cyber attack on critical infra to hammer the point that government needs complete control over AI”, and etaioinshrdlu wrote: “Can’t help but suspect that ‘AI’ is to blame and the response is to sort of ban open source AI”. gdulli rejected both: “when Netflix goes down it’s not a false flag due to their fear of people running their own Plex servers.” No source in the thread or in the coverage reviewed here supports an attack, and the FAA hasn’t said whether it suspects one.

gordonfish floated “another case of delayed Y2K”, where the system thinks the century is 19 for the two-digit year 26. Jtsummers asked: “Based on what? Just wild speculation or something you’ve actually seen about the systems involved?” kunai added that “ATC radio is unencrypted analog for safety and communicability reasons, this shouldn’t matter.” No source supports a date bug.

The base-rate answer has history behind it. hasteg recalled that in 2023 “a contractor deleted some file and caused NOTAM to go down”. The FAA’s own statement says contract personnel unintentionally deleted files and that it found no evidence of a cyber attack. September’s Northeast outage came from a cut fibre line: Duffy blamed an Amtrak construction crew and Amtrak pointed to a New Jersey Transit crew, per the AP.

What pilots and passengers say they were told

jbredeche, on a plane about to take off, wrote that “The captain is very confused and says he doesn’t know what this means.” kevvok, at San Jose, reported: “The captain basically said, ‘IDK what to do, so I’m just going to read the bulletin Alaska sent out’.” These are first-hand accounts from commenters and haven’t been verified.

sparkling asked what backs up air-to-ground radio. tjohns, who described the system in detail, answered: “There isn’t really one.” They added that pilots fall back on lost-communications rules, so “all the aircraft would fly their last assigned clearance, and attempt to deconflict manually with other aircraft over air-to-air radio”. That is tjohns’ account of procedure. cogogo raised a gap that got no reply in the thread: the FAA says international arrivals “will be managed on a case by case basis”, yet flights into Boston were landing in a mix of foreign and domestic carriers.

The FAA hasn’t published a cause, a restart time or a count of affected flights. The advisory’s event window closes at 0400 UTC on 14 November, 5pm NZDT, and the FAA’s status page lists a planning webinar for 2215 UTC, 11:15am NZDT.