FAA ground stops today: Airports affected after Northeast outage

Flight disruptions that triggered ground stops across parts of the Northeast earlier this week were still rippling through airline schedules Tuesday, but FAA status information early Sept. 22, 2026 showed an active ground stop tied to weather at Dallas-Fort Worth, not an equipment outage.

What the FAA status page shows Tuesday, Sept. 22, 2026

The FAA’s National Airspace System status page is the quickest public snapshot of ground stops and large-scale traffic management programs, and it changes frequently as conditions evolve. As of the latest update shown early Tuesday (01:42 GMT on Sept. 22, which is late evening Monday in much of the U.S.), the page listed one active ground stop: Dallas-Fort Worth International Airport (DFW).

That DFW ground stop was labeled as weather-related, with thunderstorms cited as the reason. The same status snapshot also displayed delay information indicating average delays at DFW and smaller delays at Atlanta’s Hartsfield-Jackson, again tied to thunderstorms.

Separately, the FAA status page showed several overnight “national programs” affecting arrival flows at Boston Logan (BOS), Seattle-Tacoma (SEA), San Francisco (SFO), and San Diego (SAN). These programs were attributed to factors such as volume, construction, and low ceilings, rather than a communications outage.

Full list of airports tied to the Northeast equipment outage in published reports

The headline-grabbing ground stops that prompted widespread traveler concern were tied to a communications failure at an FAA facility in the Philadelphia area on Monday, Sept. 21, 2026. Published coverage described that outage as affecting the Philadelphia Terminal Radar Approach Control facility, commonly called the Philadelphia TRACON, which plays a key role in sequencing and separating aircraft in a dense corridor of Northeast airspace.

Coverage from multiple outlets described ground stops and delays at major airports that depend on that air traffic control infrastructure. The airports most consistently named in reports of ground stops were Newark Liberty International (EWR), Philadelphia International (PHL), Teterboro (TEB), John F. Kennedy International (JFK), and Westchester County (HPN).

LaGuardia (LGA) was widely described as operating under ground delays rather than a full ground stop. Boston Logan (BOS) was also noted in some reports as experiencing delays or intermittent restrictions as traffic management absorbed diversions and congestion, even if the primary disruption was centered farther south and west.

What caused the outage, and what that means for travelers

Reports indicate the disruption began when a primary communications circuit failed at the FAA’s Philadelphia-area air traffic facility. When systems attempted to shift to backup connectivity, the backup fiber path was found to be unavailable as well due to damage associated with construction activity along rail infrastructure in New Jersey.

For travelers, the practical takeaway is that a short period of reduced air traffic control capacity can produce a long tail of disrupted schedules. Even after ground stops lift, airlines must reposition aircraft and crews, rebook passengers, and untangle missed connections. That can keep cancellations and long delays elevated across a region well after the immediate technical problem is addressed.

It also explains why disruptions were not limited to one airport. In the New York and Philadelphia metro area, airports share congested airspace and depend on coordinated flow management. When arrival rates drop at one major hub, the effects can cascade to nearby airports as airlines reroute, hold aircraft at origin, or cancel rotations.

Why the “hacking warning” is part of the story, but not the cause of this outage

The equipment failure arrived alongside a new wave of cybersecurity scrutiny for aviation communications. A Government Accountability Office report published Sept. 21, 2026 highlighted vulnerabilities in text-based communication applications used across the aviation system, noting risks that can include interception and spoofing when authentication and encryption are limited or outdated.

That warning has fueled public speculation whenever a technical failure hits a critical aviation node. Still, the outage tied to the Northeast ground stops has been described in published coverage as a telecom and infrastructure problem, not a cyber incident. The difference matters for travelers: infrastructure failures often lead to localized but intense operational slowdowns, while a true cybersecurity event could trigger broader containment steps and longer diagnostic timelines.

Even without a cyber link, the juxtaposition underscores how heavily modern flight operations depend on resilient communications pathways. When primary and backup links share geography or are exposed to the same construction risks, even routine physical damage can look and feel like a systemwide emergency to passengers stuck in terminals.

How to check if your airport is under a ground stop right now

Because ground stops can be issued and lifted quickly, travelers should treat “today” lists circulating on social media as time-stamped rather than definitive. The FAA’s public National Airspace System status page and ATCSCC advisories are designed to reflect current operational programs, including ground stops, ground delay programs, and major reroutes.

If you’re flying today, the most useful routine is to check your flight’s status with the airline first, then cross-check whether the FAA is showing a ground stop for your destination airport at the time you plan to depart. A ground stop typically means departures bound for that airport may be held at origin, even if your departure airport weather looks fine.

For travelers connecting through the Northeast corridor, it can also help to monitor multiple airports in the same airspace cluster, since restrictions at one hub can create gate shortages and crew timing issues at another. And for Tuesday specifically, the FAA status snapshot early Sept. 22 showed the only listed ground stop as DFW, driven by thunderstorms, while the earlier Northeast outage was being handled through recovery operations rather than an ongoing ground stop on the status page.