SFO sees 400+ delays as East Coast ATC outage ripples nationwide

San Francisco International Airport logged more than 400 delayed flights on Monday, September 21, 2026, as a major air traffic control communications outage in the U.S. Northeast disrupted one of the country’s busiest air corridors and sent schedule problems cascading nationwide.

What triggered the outage and where it hit first

Published coverage described the disruption as a communications failure tied to a key air traffic control facility serving the Philadelphia and New York region, where damaged lines interrupted the flow of information needed to safely manage arrivals and departures. The incident led to ground stops and traffic management programs across multiple airports in the Northeast, including Newark, Philadelphia, and other New York area airports.

Reports indicated the technical problem was linked to a construction mishap in New Jersey that damaged fiber communications, leaving controllers with reduced capability until repairs were completed. Even after service was restored, airline schedules remained out of position, a common outcome when aircraft and crews are stranded away from their next planned flights.

The disruption was especially consequential because the Northeast corridor contains tightly packed airspace and heavily banked schedules. When departures pause and arrivals are throttled there, delays can spread quickly to flights that never go near the affected airspace, including long-haul trips heading west.

How an East Coast stoppage translated into SFO delays

Although the outage occurred far from California, SFO is deeply connected to Northeast hubs through nonstop routes and connecting banks. When departures from New York and New Jersey are held, aircraft scheduled to continue onward after landing in San Francisco often arrive late, compressing the rest of the day’s operation and pushing back later departures.

Flight-tracking data showed SFO’s delay totals spiking on Monday, with “delayed” designations climbing well past normal levels as inbound flights arrived late and gate plans were reshuffled. Travelers could see this in the form of late aircraft arrivals, extended boarding holds, and departure times moving in increments as airlines tried to rework rotations.

Even travelers not flying to the Northeast were affected because airlines frequently use the same aircraft for multiple legs across different regions. A delay chain that begins with a single held departure at Newark can later impact a transcontinental aircraft, which then affects an entirely different route once it reaches California.

Where delays and cancellations were concentrated

Early reporting pointed to Newark Liberty International Airport as one of the hardest-hit locations during the outage window, with long stretches of limited arrival flow and large numbers of delayed flights. Philadelphia also experienced significant disruption, adding strain to an already congested region during a high-volume travel day.

By Tuesday, September 22, operations in the New York area were resuming with ongoing but reduced disruption compared with Monday’s peak. However, the aftereffects were still visible as airlines worked through mispositioned aircraft and crews, a process that can take a full day or more depending on the size of the initial stoppage.

For West Coast airports like SFO, that recovery period matters: when the East Coast is “catching up,” it often means late-departing red-eyes, swapped aircraft types, and tighter turnaround times, all of which can raise the odds of additional delays later in the day.

What travelers should do at SFO if their flight is impacted

With schedules still recovering, travelers departing SFO on routes connected to the Northeast or feeding into New York area connections may want to monitor both their flight number and the inbound aircraft assignment, since delays often trace back to late-arriving equipment. Airline apps typically display the operating aircraft’s previous leg once the day’s plan is set.

Passengers facing a long delay should verify whether their ticket is eligible for a same-day change or rebooking option, which many airlines make available during major airspace disruptions. If rebooking is needed, earlier flights in the day can sometimes be easier to protect than later departures, when delay chains have had more time to compound.

For those already at the airport, keeping an eye on gate changes and boarding times is critical during irregular operations, since late aircraft arrivals can trigger last-minute moves. And because a regional disruption can produce congestion at airline counters, using app-based chat support or phone callbacks may be faster than waiting in line, depending on the carrier’s tools at the time.

Why the incident is fueling renewed attention on ATC infrastructure

The outage arrived amid ongoing national focus on the resilience of U.S. air traffic control systems and the vulnerability of communications links that support radar and radio operations. Recent years have brought multiple high-profile disruptions in U.S. aviation, and each one adds urgency to efforts aimed at modernizing technology and improving operational redundancy.

Published coverage of this week’s disruption emphasized how quickly a localized failure can ripple into a nationwide network problem, affecting airports thousands of miles away. For travelers, the takeaway is that “regional” air traffic disruptions can quickly become “national” schedule disruptions, particularly when they occur in the Northeast, where traffic density is high and recovery options are limited.