Did new AI software cause the ground stop?

On Friday, November 13, the FAA halted every departure in the United States after a communications failure hit the centers that handle cross-country flights. Within an hour, speculation on cable news and social media pointed at SMART, an AI planning tool the FAA had expanded to all 22 of those centers three days earlier. This page tracks what officials have confirmed about the cause, and what would show whether SMART played any part.
This tracker closed on November 14, 2026. The ground stop was lifted at about 8:15 p.m. ET on Nov. 13. On Nov. 14 Transportation Secretary Sean Duffy said the failure began during contractor work at a remote facility and that the fault was not yet determined. No official has linked SMART to the outage; Duffy says it was not connected.
What the evidence shows
What would reopen it
Closed trackers reflect our provisional conclusion. We may reopen this one at any time if our editors see that new information has become available. The page and its sources stay online as a record.
On Nov. 14 Transportation Secretary Sean Duffy said the ground stop began when contractor L3Harris was upgrading copper wire to fiber optic cable at a remote facility, and that officials are working out whether a faulty router or an installation error was to blame. On Nov. 13 he said SMART “isn’t plugged in” and could not have played a role; its developer, Air Space Intelligence, says the same. SMART went to all 22 centers on Nov. 10, and no document has been published showing how it connects to center systems. The FAA has not yet said what the fault was.
What would change this rating ↓
groundstop.america2.newsAnalysis of Russian influence, information warfare and the networks behind them. Free; unsubscribe anytime.
New reporting from major outlets and official sources, listed as it appears. Our monitoring adds headlines from major outlets automatically. "Checked" means our software fetched the full report and confirmed it supports its headline. "Reviewed" means an editor checked it against its source. "Auto" items have not been checked yet. Tap a label for our note. None of this is an endorsement. Our assessment is the rating above.
The cause will be settled by the FAA, DOT, the NTSB or the DOT Inspector General, or by tier-one reporting that names documents or on-record officials. A timing coincidence does not count as evidence.
What we could not check: whether SMART shares any network path, vendor or data feed with the center communications systems that failed. The FAA's public material doesn't say.
The most-shared claims about the cause, and what public sources can confirm. Tap a row for the record; the link icon copies a direct link.
This is the FAA's own explanation, and DHS Secretary Mullin repeated it. Neither has said what failed, or why it affected every center at once (CNN).
Where it came from: FAA statement, Nov. 13.
FEC filings show that Air Space Intelligence’s corporate PAC gave $2,500 to Alfonso for Congress on March 30, 2026 (FEC). The campaign is that of Rep.-elect Michael Alfonso (R-Wis.), Duffy’s son-in-law. It was one of 19 contributions the PAC made from February to July, totaling $50,000, most of them to House and Senate appropriators. In June DOT announced that it had awarded ASI the contract for SMART, worth up to $875.9 million. The Bulwark first reported the donation in September, in a story on transportation-industry donors to Alfonso (The New Republic). ASI is not Alfonso’s company, and no record shows a $3 million donation. Officials trace the outage to an L3Harris network upgrade, not to SMART.
Where it came from: a Raw Story report on Nov. 13 that first gave the figure as $12,500 and then corrected it to $2,500. Posts and forum comments inflated it to “$3 million” and called ASI his company.
Officials trace the outage to a router during an L3Harris fiber upgrade at a remote facility, and on Nov. 13 Duffy said SMART “isn’t plugged in” (The Hill). SMART went nationwide on Nov. 10; no document shows how it connects to center systems. No official finding links SMART to the failure, and neither report below names it. But the case no longer rests on timing alone. Multiple sources told CBS News that an update to the private communications network connecting air traffic control caused a reboot and crash. A person familiar with the matter told Bloomberg the FBI is examining whether a software update caused the outage. SMART went nationwide on Nov. 10 and, per the FAA, runs alongside existing center systems. Whether the update touched SMART or its network link is not public. After flights resumed, Homeland Security Secretary Markwayne Mullin said new equipment and technology the FAA was adding “was overwhelming the older system,” without naming it (video). Air Space Intelligence, SMART's developer, says its product played no role. Secretary Mullin said he saw no evidence of a link but did not rule one out.
Where it came from: on-air speculation Friday afternoon, including by aviation lawyer and former DOT Inspector General Mary Schiavo, who said, “I don't know if they're linked,” in a clip viewed about 590,000 times by evening.
Two law enforcement officials told CNN that preliminary reports indicate it was not. Mullin said there was no indication of an attack but would not rule anything out (CNN). On Nov. 14 Duffy said, “we don’t believe this was cyber at all” (Al Jazeera).
Where it came from: social-media speculation during the stop.
The Heritage Foundation’s Mandate for Leadership (2023) argues on p. 632 that the FAA’s air traffic service and its safety regulator “ought to run separately.” It recommends separating the Air Traffic Organization from the FAA (p. 633), moving it out of Washington, paying for it with user fees and letting it issue bonds (p. 634). All of these changes “require legislation.” Page 633 does not mention privatizing a communications system. It discusses remote towers, text messaging between controllers and pilots, and consolidating centers. No law separating the Air Traffic Organization has passed, and no official account connects the Nov. 13 outage to the plan.
Where it came from: a verified X account’s post (about 23,000 likes and 426,000 views by Nov. 14) quoting both pages as if from the document. Copies of the post present the ground stop as the plan’s first step.
Mullin: “I don't see any reason to connect those two at all … Those are separate issues” (CNN).
Where it came from: reporters' questions at the White House.
Friday's stop is only the third nationwide ground stop in decades (New York Times).
| Date | What happened | How long |
|---|---|---|
| Sept. 11, 2001 | After the terrorist attacks, the FAA closed U.S. airspace and ordered planes in the air to land. It was the first unplanned closure of U.S. airspace; only military, police and medical flights flew (background). | Commercial flights resumed Sept. 13, about two days later. |
| Jan. 11, 2023 | The NOTAM system, which sends pilots safety notices, failed after a contractor unintentionally deleted files. Airborne flights continued to their destinations; thousands of flights were canceled or delayed (CNN). The FAA found no evidence of a cyberattack. | About 90 minutes (NYT). |
| Nov. 13, 2026 | A communications failure at the Air Route Traffic Control Centers. The FAA calls it a “temporary telecommunications outage.” | About four and a quarter hours (airspace reopened 8:15 p.m. ET, per Duffy; AP reported departures resuming about 8:30). |
A regional precedent: on the day SMART debuted for the Washington, D.C. airports in September, a circuit failure in air traffic communications delayed or canceled about 7,000 flights in the Northeast, per FlightAware (Reuters). Contractors had accidentally cut the fiber line meant to back it up (New York Times).
Times are Eastern.