America Cancels 4,000 More Flights. FAA Denies Impact of New AI System.
7 71UPDATE: FAA Administrator Bryan Bedford said Saturday that U,S. airlines will likely cancel 4,000 to 5,000 of the roughly 41,000 flights scheduled for Saturday, reports Yahoo News. And as to the cause of the incident...
[U.S. Transportation Secretary Sean] Duffy said a router involved in the switch from copper wire to fiber "started flooding other routers in our air traffic control system." The system saw "over 1,000 connection attempts every four to five seconds," he said. That disrupted communications with airplanes and radar.
America's nationwide grounding of flights on Friday happened "amid growing scrutiny... of a new AI-powered air traffic management system" deployed by America's Federal Aviation Administration, reports Texas news station KXAN.
Ironically, that system is called SMART — but the outage happened "following warnings" from members of the U.S. Congress about this new AI system's safety, reliability and oversight: In an Oct. 13 letter to the Government Accountability Office, more than 20 members of Congress requested an independent review of the FAA's development and implementation of its Strategic Management of Airspace, Routes and Trajectories system, known as SMART. The lawmakers questioned whether the technology was being deployed with adequate input from frontline air traffic controllers, sufficient training and appropriate safety evaluations... In their letter to the GAO, the lawmakers specifically questioned whether the FAA had adequately evaluated risks associated with SMART's artificial intelligence capabilities, including the potential for the technology to interfere with experienced controllers' decision-making or generate inaccurate safety-critical information. "The nation's frontline aviation safety workforce apparently had little to no input into SMART's development and have received limited training and information during the current deployment process," the lawmakers wrote. The letter also questioned the FAA's decision to initially pilot the technology in heavily congested airspace, including the National Capital Region.
"Our switches, our routers, actually got overloaded with data," U.S. Transportation Secretary Sean Duffy acknowledged Friday.
But FAA Administrator Bryan Bedford said Saturday that officials have found "zero evidence of anything AI related" in Friday's outage, according to Yahoo News.
An article from The Hill.com notes that Duffy also said the new AI tool had nothing to do with the ground stop, and that he said the system "isn't plugged in." "This is completely disconnected, and I love that some people have said this would be the root cause. By the way, if it was, I'll tell you that, but this is not even plugged in," he said. "So, there's no possible way SMART would have impacted."
Duffy also asked Congress for $50 billion to rebuild what he described as an "incredibly old" air traffic control system.
Duffy had posted the day before that the AI system had been at least partially rolled out and that it was already working (adding "Soon this technology is going NATIONWIDE")
And Friday CNN's aviation analyst said they believed that AI system could be connected to the nationwide outage, calling it "a tremendous amount of coincidence," according to a report from Mediaite: CNN Aviation Analyst: "Many times in the past, what we have seen, and this has gone back decades, is that because air traffic control is this piecemeal, mishmash of a whole bunch of different systems... some going back to radio, telephones and floppy disks... when they put in new computer systems, they often have difficulty talking with, communicating with, or working with the much older systems. And I have to say, it's a tremendous amount of coincidence... If they're putting in new software now, this new SMART system to start managing that, and now we have a communications outage, I'm — we've seen this so many times in the past. I don't know if they're linked, but it's just too much coincidence that they were trying to start that moving today, and now we have problems with the en route system.
So if I was to guess — and we haven't heard any, you know, it's not that it's threats or criminals or terrorists. We haven't heard anything like that. So I am guessing that once again we have a problem with new air traffic control computer systems, AI — you know, modern systems trying to communicate with old systems. And we have just seen this so many times in the past, and it's a big problem... Our whole national airspace system is you know, pieces and parts. It's kind of a Franken-system. And that would be my guess, that they are having computer issues by putting the new software in with the old, just because today they announced that that were going to do this new system.
KXAN describes some of the complexity of the newly-launched AI system: According to the FAA, the system consolidates approximately 200 data streams, including airline schedules, flight paths, weather patterns, airport capacity, airspace conditions and air traffic controller staffing metrics. The agency says SMART uses artificial intelligence to analyze that information, predict traffic flows, identify potential conflicts and recommend adjustments to flight routes and departure schedules before disruptions occur. The FAA describes the technology as a shift from a reactive approach to a predictive one, allowing aviation officials to identify congestion, weather-related restrictions and other operational problems hours, days or even weeks in advance...
The congressional letter raised questions about whether the FAA's implementation strategy was moving faster than its safety evaluations, workforce training and independent oversight could support.
Ironically, the article points out that the FAA promoted anticipated benefits from the technology including fewer delays and flight cancellations. (Other anticipated benefits included improved on-time performance and faster recovery from weather disruptions.) Although the FAA has realized one of the system's anticipated benefits: reduced fuel consumption.
7 comments
Re:Yes and no (Score: 5, Funny)
by 93 Escort Wagon ( 326346 ) on Saturday November 14, 2026 @04:41PM (#66424566)
These renaming things are so pointless/stupid.
It's not stupid to them. They know that, if they don't do it, they'll have to deal with the wrath of their Stable Genius boss - and they'd like to keep their jobs.
The claim is that it was a router problem (Score: 5, Informative)
by drinkypoo ( 153816 ) on <drink@hyperlogos.org> on Saturday November 14, 2026 @01:07PM (#66424285)
CBS reports [cbsnews.com] that:
The network DDoS'ed itself.
If the system is designed so that a couple of routers in one spot can make it necessary to ground everything, the design is bad. Saying they need $50B stat is wild when it clearly wasn't done right the first time with however much was spent so far.
Re:The claim is that it was a router problem (Score: 5, Interesting)
by Luckyo ( 1726890 ) on Saturday November 14, 2026 @01:33PM (#66424325)
The system is ancient and built for a time when floppy disks were common. Notably, they're still used to load weather data into the system.
Such systems do not expect modern volumes of data transport, nor are they built to handle it.
"But this fairly modern threat isn't handled well by this ancient system". Indeed. But updating such systems requires functioning bureaucracy, that isn't devoured by corruption on one side, and by ideology that views competence as the greatest evil that exists on the other.
It's in fact one of the greatest achievements of US that it can run with this level of dysfunction and remain clear #1 in the world in most productive aspects, including adoption of commercial aviation.
Re:The claim is that it was a router problem (Score: 5, Insightful)
by organgtool ( 966989 ) on Saturday November 14, 2026 @04:13PM (#66424532)
For me, the bigger question is who the fuck authorized replacement of network equipment in the middle of the day? When I worked on an FAA contract, we had to perform even basic software updates overnight.
Indeed. If this really was a network issue, there is already a contract well under way to replace FTI with FENS. But if the story about the L3Harris contractor is true, then the problem was human error. If Mr. Duffy wants us to believe it takes $50 billion to fix human error during maintenance that shouldn't have been approved to be done during the day in the first place, then maybe he needs to spend more time in the Real World.
L3Harris (Score: 5, Insightful)
by CommunityMember ( 6662188 ) on Saturday November 14, 2026 @01:11PM (#66424293)
L3Harris has a long history of various contracting and implementation anomalies. As a large government contractor, with lots of moving parts and lots of contracts, that is not, itself, too surprising. However Duffy seems to be throwing them under the bus before the full facts in this case are known. That always raises an eyebrow or two.
Just remember (Score: 5, Interesting)
by lennier1 ( 264730 ) on Saturday November 14, 2026 @01:25PM (#66424311)
Duffy's son-in-law's company got the contract for the FAA's AI tool after they'd made a 3 million donation, so of course Duffy has no reason to pull excuses out of his ass whatsoever...
Re:Right... (Score: 5, Interesting)
by Vlad_the_Inhaler ( 32958 ) on Saturday November 14, 2026 @03:37PM (#66424488)
I've actually been peripherally involved in something like this, I think it was September 2000, maybe a few months later.
An ATC system where they had two networks, the "office" network and the "core business of actually directing flights" network. The offices were around 10 miles away from the airport, which is where the ATC mainframe and - obviously- the ATC tower were. There was a bridge between the networks.
There were building works going on in the city, and they cut the cables while excavating. The agreement with the provider was that there would be two high speed lines and that they would not be in the same bundles of cables (or maybe glass fibre, if that was a "thing" back then). Unfortunately they had not insisted in the cables being in the separate ditches. The excavator cut both connections.
This should not have been a problem, two separate networks right? The critical one was at the airport and the whole point of that setup was so things would carry on if the offices were cut off. Most of the network group worked in the offices rather than at the airport. Some component was in the offices, the router at the airport was set up so that the control traffic to that component had the highest priority.
Bottom line, the core network was nominally unaffected, but a router there was trying to reach the office network and it was using all of its processor power for that. The core network pretty much came to a standstill. I can't remember how long that outage lasted but it was several hours.
Lessons were learned and all that.
The offices moved to a new location a year or so later, something which had been in preparation for a few years by then. New offices, new cables, whatever.
In 2003 (or maybe early 2004) something similar happened, an excavator chopped the connection. I was working on the mainframes at the airport from the offices so obviously I was affected, I just drove to the airport and carried on from there, everything worked exactly as it was supposed to - the offices could communicate with each other and the ATC Tower had full access to the ATC mainframes. It took a few hours before the two networks were linked to each other again but nobody outside noticed anything.