The Federal Aviation Administration expanded its SMART air traffic management tool nationwide on November 10, 2026. Three days later, a communications failure triggered a nationwide ground stop. The timing put the new AI-supported system under scrutiny, but the FAA and SMART developer ASI told The Associated Press that the events were unrelated.
The FAA’s explanation draws a specific technical distinction: SMART aggregates data and supports routing recommendations, while the disruption involved the telecommunications network carrying aircraft communications and radar feeds. Human traffic managers retain authority over routing decisions.
That distinction leaves a separate set of questions intact. Lawmakers had requested an audit in October, before the nationwide expansion, covering workforce input, training, reliability and hallucination risks. The strongest case for examining SMART is its growing influence over airspace management, not an unsupported connection to the ground stop.
The Timeline: A Nationwide Expansion, Then a Separate Failure
SMART stands for Strategic Management of Airspace Routing Trajectories. According to POLITICO Pro’s November 10 report, the tool initially launched in September for flights at three Washington-area airports, under what was intended to be a 90-day trial.
The FAA then announced nationwide use on November 10. The expansion covered the airspace of all 22 U.S. Air Route Traffic Control Centers, which manage aircraft traveling between airports. Nationwide coverage means a flight could be subject to the tool’s recommendations depending on its route, traffic and weather conditions. It does not mean SMART makes a decision about every flight.
The documented sequence is:
- September: SMART began its Washington-area trial.
- October: Lawmakers requested a Government Accountability Office audit, according to AP.
- November 10: The FAA announced nationwide use across the airspace of all 22 centers.
- November 13, approximately 3:30 p.m. ET: A technical problem prompted a nationwide ground stop.
- November 13, 8:15 p.m. ET: The network was stable and air traffic resumed, according to the FAA.
- November 15: The FAA published a detailed explanation denying a SMART connection.
The ground-stop times come from the agency’s official questions-and-answers document. The rollout reporting supplies a date, but no exact activation time.
A September start followed by a November 10 expansion places nationwide deployment inside the originally described 90-day trial window. That is a useful oversight question: what evidence justified broadening use at that point? The chronology alone cannot tell us whether the trial continued alongside the expansion or what internal approval criteria the FAA applied.
What SMART Actually Does
SMART is a decision-support tool for managing airspace routing. It brings information together and produces visualizations and recommendations that human specialists can use when deciding how to move traffic through the national airspace.
AP reports that human traffic managers retain final routing authority. POLITICO Pro places the tool’s operation at Transportation Department headquarters in Washington. Those details describe a centrally operated recommendation system, not AI autonomously controlling aircraft.
The FAA’s ground-stop explanation states:
“SMART is a data aggregator, and it does not feed information into the air traffic control system.”
That sentence, from the FAA’s November 15 Q&A, identifies an important system boundary. SMART’s recommendations can influence human choices without directly supplying data to the underlying air traffic control system.
The two roles should not be conflated:
| Function | SMART | Network involved in the ground stop |
|---|---|---|
| Main purpose | Aggregate information and support routing recommendations | Carry communications and radar information |
| Human role | Traffic managers decide whether to act on recommendations | Controllers use available communications and radar feeds to manage aircraft |
| Reported problem | No causal role in the ground stop, according to FAA and ASI | Instability associated with excessive connection attempts |
| Relevant oversight issue | Recommendation quality, training and human decision-making | Network reliability, maintenance and root-cause investigation |
This boundary is the most consequential detail in the published explanation. A recommendation tool and a communications network can both be important to aviation while failing in very different ways.
My view is that retaining human authority is a meaningful safeguard, but it is only one part of the evaluation. A specialist still needs enough information to judge a recommendation, recognize a questionable result and reject it when necessary. The quality of that process depends on training and presentation as well as the recommendation itself.
What the FAA Says Caused the Ground Stop
The FAA attributes the November 13 disruption to instability in its legacy telecommunications infrastructure. Its initial account says data flooded the FAA FTI network at a rate of approximately 1,000 connection attempts every four to five seconds, disrupting aircraft communications and radar feeds.
That figure describes repeated connection attempts, not a measured volume of data in bytes. It illustrates the pattern the agency observed without, by itself, identifying the ultimate cause.
The FAA’s preliminary explanation identifies two possible source locations:
- Amarillo, Texas: A radar site under investigation for excessive data entering the network.
- El Dorado, Arkansas: A radio communications site where network provider L3Harris had been performing work, including deploying a new router.
The FAA said L3Harris blocked the two locations, after which the network stabilized. Broadcasting functions were also disabled on all the new routers as a precaution.
The agency reported instability at 17 of its 22 Air Route Traffic Control Centers, with effects spreading into several Terminal Radar Approach Control facilities. It described a partial communications disruption: some radio frequencies and radar feeds remained available, allowing controllers to communicate with and track aircraft.
Approximately 3,500 aircraft were airborne when the ground stop began. The FAA said they landed safely and that critical life-saving, law enforcement and military flights continued.
The root-cause investigation was still underway when the Q&A was published. The defensible account is therefore that the FAA identified network flooding, isolated two potential source sites and restored stability. Treating either site, or the router installation alone, as a conclusively established root cause would go beyond that document.
FAA and ASI’s denial of a SMART connection is consistent with the functional separation the agency describes. The published evidence supports examining the telecommunications failure on its own terms; it provides no basis for assigning that failure to the routing tool.
Early Efficiency Claims Have a Narrow Scope
The FAA has offered encouraging figures from SMART’s Washington-area testing. AP reported the agency’s results as follows:
| Reported measure | FAA-reported result |
|---|---|
| Flights rerouted | 180 |
| Average time saved per flight | 10 minutes |
| Average fuel saved per flight | 80 gallons |
These are agency-reported results, not an independent evaluation. They describe a particular test and should not be read as an expected saving for every flight nationwide.
Frequently Asked Questions
4 questions
1Did SMART Cause the Nationwide Ground Stop?
The FAA and developer ASI say no. The FAA attributes the disruption to instability in its telecommunications network and says SMART does not feed information into the air traffic control system. The network root-cause investigation was ongoing when its explanation was published.