The nationwide FAA ground stop is no longer a mystery order with no explanation attached.

Officials now say a telecommunications outage disrupted the 22 regional air traffic control centers that manage aircraft between airports across the United States.

That is the critical update to our earlier report, which covered the Federal Aviation Administration’s extraordinary nationwide safety order as the first details were breaking.

Transportation Secretary Sean Duffy first confirmed that the disruption reached every Air Route Traffic Control Center and said FAA technicians were investigating.

The Associated Press later reported that the problem was a telecommunications outage affecting all 22 centers. Those facilities direct aircraft through enormous blocks of en route airspace after departure and before the final approach to an airport.

ADVERTISEMENT

Homeland Security Secretary Markwayne Mullin said officials had found no indication that the outage was a malicious attack. He also said every aircraft already in the air was accounted for and that travelers did not need to fear for loved ones who were flying.

That reassurance matters. The ground stop was a preventive safety action: it kept new departures on the ground while controllers and technicians worked through a communications failure.

It was not an order for thousands of aircraft already airborne to make emergency landings.

The scale was still extraordinary. Flightradar24 counted roughly 3,100 aircraft already flying toward U.S. airports shortly after the stop began.

The FAA’s order allowed inbound international flights to be managed case by case. That gave controllers room to handle aircraft already approaching the country without adding another nationwide wave of departures to a strained system.

Trending Politics showed how the problem widened before the national order. Equipment outages first forced ground stops at Chicago O’Hare and Midway, while Newark, Las Vegas, Phoenix, Teterboro, Houston and Orlando also reported equipment-related delays.

The Chicago restrictions were initially expected to remain in place until 4:30 p.m. Eastern. Shortly after 4 p.m., O’Hare was reporting departure delays averaging 45 minutes and rising.

Teterboro’s average departure delay had reached an hour and was also increasing. Those separate warnings showed an equipment problem spreading across widely separated facilities before the Command Center stopped departures nationwide.

The national advisory did not give airlines a firm resumption time. It told departing aircraft to remain on the ground until further notice while international arrivals were handled individually.

ADVERTISEMENT

That progression helps explain why the FAA used such blunt language. A disruption that appears local can become a national safety problem when communications between multiple control centers are affected at the same time.

There is another question investigators cannot ignore.

Only days before the outage, the FAA announced that it was expanding its new Strategic Management of Airspace, Routes and Trajectories system, known as SMART, to the airspace managed by all 22 centers.

The FAA describes SMART as a planning tool that brings together roughly 200 data streams, including weather, flight paths, traffic flow and controller staffing. It is designed to identify congestion and recommend better routes before aircraft depart.

The timing does not prove that SMART caused Friday’s outage. No official has established that connection, and the system is a traffic-planning layer rather than a replacement for the voice communications controllers use with pilots.

But the Associated Press reports that investigators will examine whether there is any relationship between the new nationwide rollout and the communications failure. That is a reasonable question, not a conclusion.

The distinction is important. Officials have identified what failed at the operational level — telecommunications across the regional control-center network — but they have not yet disclosed the underlying technical event that made those communications fail.

A damaged line, a failed network component, a configuration error, a software interaction and a deliberate attack would all require different responses. The current evidence rules out none of those technical possibilities except that officials say they have no present indication of a malicious attack.

Friday’s event is the first nationwide ground stop since January 2023, when the FAA’s Notice to Air Missions system failed. That earlier outage was ultimately traced to damaged database files and an accidental deletion during maintenance, not a cyberattack.

ADVERTISEMENT

The current failure is different. It involved communications across the centers that coordinate en route traffic, not the NOTAM safety-information system involved in 2023.

Even after the nationwide order is lifted, the consequences will not disappear immediately. Aircraft, flight crews, gates and connecting passengers will be out of position, creating delays and cancellations that can continue long after the original systems problem is stabilized.

DFW Airport urged passengers to check directly with their airlines for current flight information.

For travelers, the practical advice remains simple: use the airline’s app or direct alert system before heading to the airport, and expect schedules to keep changing as the national network recovers.

The immediate safety picture is reassuring. Every airborne flight is accounted for, officials say there is no current sign of a hostile attack, and the FAA stopped new departures rather than gambling with degraded communications.

Now the public needs the complete technical answer: what failed, why it spread across all 22 centers, whether the SMART rollout played any role, and what must change before the same failure can happen again.

This is a Guest Post from our friends over at WLTReport. View the original article here.

 

Join The Conversation. Leave a Comment.