SFO Sees Spike in Cancellations as FAA Outage Snarls East Coast Flights

San Francisco International Airport (SFO) logged an unusually heavy day of cancellations and widespread delays as a Federal Aviation Administration (FAA) communications outage in the Northeast disrupted key hubs and forced carriers to reshuffle aircraft and crews across the country.

East Coast air-traffic disruption ripples to the Bay Area

Published coverage indicates the outage centered on FAA systems supporting the Philadelphia Terminal Radar Approach Control (TRACON), which sequences traffic for major airports including Newark Liberty (EWR), Philadelphia International (PHL), and Teterboro (TEB). Ground stops and long delays in that corridor quickly spilled into the national network because aircraft scheduled to fly transcontinental routes to and from California were delayed, diverted, or unable to depart.

Reports described a failure of a primary communications circuit, followed by additional trouble when controllers attempted to switch to backup connectivity. The interruption temporarily reduced the flow of arrivals into multiple Northeast airports and triggered cascading schedule changes, including aircraft swaps and crew legality issues that can take a full day or longer to untangle.

While SFO sits far from the affected airspace, the airport is tightly connected to the New York and New Jersey market via frequent service by multiple airlines. When departures out of the Northeast stall, the resulting shortage of inbound aircraft can lead to cancellations in San Francisco even if local flying conditions remain workable.

What made SFO’s disruption feel worse than a typical bad day

In the same time window as the East Coast outage, FAA status pages showed SFO operating under a traffic management program due to weather conditions, with low ceilings contributing to arrival delays. That local constraint meant SFO had less slack to absorb late-arriving aircraft and re-timed schedules.

Published coverage also noted SFO has been operating with reduced capacity tied to airfield work and FAA procedural limits, which can lower the number of aircraft the airport can handle during certain conditions. When national disruptions collide with local arrival-rate limits, even a moderate schedule shock can produce outsized delays at gates and more cancellations than travelers expect.

Flight-tracking summaries and local coverage pointed to hundreds of delays at SFO during the peak of the Northeast disruption, alongside a notable count of cancellations. For passengers, the on-the-ground experience often reads as “SFO chaos,” even though the root cause may be split between local weather constraints and an air-traffic bottleneck thousands of miles away.

Where the cancellations hit hardest: New York and New Jersey connections

The Northeast outage had a concentrated impact on the New York City area’s airport system, with widespread cancellations reported at Newark and significant interruptions across other metro-area airports. Because many SFO travelers rely on those hubs for onward connections, a cancellation on one leg can wipe out an entire itinerary, including international departures later in the day.

Routes linking SFO with Newark, New York-area airports, Philadelphia, and Washington-area airports are especially sensitive to air-traffic constraints because they operate on tight turn times and often use the same aircraft rotations for multiple legs. If a morning arrival into the Northeast is delayed for hours, the return flight to California may cancel rather than operate deep into the night, particularly if the crew would time out.

For Bay Area travelers heading to the East Coast for meetings, events, or onward connections, the risk is not only the initial cancellation, but also limited rebooking inventory. When a major hub spends hours under restrictions, replacement seats fill quickly across all carriers, and the remaining options may require reroutes through Chicago, Dallas, Denver, or Atlanta, adding time and complexity.

What travelers at SFO can do right now

For trips scheduled within 24 to 48 hours of a major air-traffic disruption, travelers benefit from checking both their airline’s app and the FAA’s airport status updates before leaving for the airport, since official airport-wide programs can change rapidly. A departure that looks fine the night before can shift into a long delay if the inbound aircraft is held on the other side of the country.

Travelers connecting through the New York and New Jersey area can also reduce risk by confirming whether their itinerary depends on a single hub. When seats are available, moving to a nonstop itinerary or switching connections to a different region can help avoid chokepoints during recovery operations.

For those already at SFO, the most practical steps are operational: keep carry-ons packed for a long wait, confirm whether your flight is waiting on an inbound aircraft, and watch for same-day rebooking opportunities as carriers rebuild schedules. In many disruptions, the earliest rebooked departure is not always the best choice if it depends on an aircraft still stuck in the impacted corridor.

As of Tuesday, September 22, FAA daily planning guidance continued to flag weather factors that can slow traffic in both New York and San Francisco, suggesting that recovery could remain uneven even after the immediate outage is repaired. For travelers, that means extra time buffers and flexible plans remain valuable until airline networks fully stabilize.