San Francisco delays strand 293 flights
- On May 10, SFO was hit by a broad delay wave as low ceilings and FAA traffic controls slowed arrivals, stranding travelers across domestic and international routes. - FAA status showed an SFO ground delay program with average arrival delays around 42 to 59 minutes, while flight trackers counted roughly 293 delays and 14 cancellations. - The bigger issue is structural: SFO is heading into summer with weather sensitivity, packed schedules, and a national air-traffic system still short on slack.
Airports break in boring ways. Not usually with one dramatic shutdown, but with a slow pileup — weather trims capacity, the FAA meters flights, crews and planes fall out of position, and suddenly a normal travel day turns into a mess. That’s basically what happened at San Francisco International on Saturday, May 10. By the end of the disruption, flight trackers were showing roughly 293 delayed flights and 14 cancellations, while FAA advisories showed active delay programs at SFO tied to low ceilings and broader traffic-management controls. ### What actually tripped SFO up? The immediate trigger was weather — specifically low ceilings. At SFO, that matters more than people realize because the airport’s layout and marine weather can quickly reduce the rate at which planes can land. The FAA’s live airport-status page showed a traffic management program in effect for arrivals into San Francisco because of weather, with average arrival delays around 42 minutes, and the broader FAA NAS status page showed a ground delay program at SFO on May 10 with average delays pushing close to an hour later in the day. (fly.faa.gov) ### Why do low clouds cause such a big mess? Because this is a capacity problem, not just a visibility problem. When conditions deteriorate, the FAA spaces aircraft farther apart and reduces arrival flow. That means planes don’t just wait in the air — many get held at their origin airports under a ground delay program. One local report on the May 8 version of the same problem said the FAA had capped SFO arrivals at roughly 36 flights per hour during low-cloud conditions. That gives you the shape of the issue: once arrival slots shrink, the whole network backs up. (fly.faa.gov) ### Were these just a few bad flights? No — this was airport-wide enough to hit the major carriers people most associate with SFO. United is the big one because SFO is one of its main hubs, but the disruption also spilled across other domestic and international operators using the field. SFO’s own flight-information pages were directing passengers to live status tools and airline-specific updates, which is usually what airports do when the problem is broad and constantly changing rather than tied to one broken aircraft or one route. (hoodline.com) ### Why does one airport snarl so many routes? Because SFO is a network airport. A late inbound jet from Chicago can delay an outbound to Los Angeles. A transpacific arrival that misses its slot can scramble gates and crews. And once aircraft start arriving late, the next several flights that same plane was supposed to operate can slide too. That’s why a delay board can balloon from “annoying” to “whole day gone” without a single headline-grabbing closure. The catch is that recovery usually takes longer than the weather event itself. (fly.sfo.gov) ### Is this just an SFO thing? Not really. SFO is unusually sensitive to marine weather, but the broader U.S. system is still fragile. FAA traffic-management initiatives are now common tools for preventing worse congestion, and they work by slowing flights early instead of letting the airport gridlock later. That helps safety and flow, but for travelers it still feels like the same outcome — long waits, missed connections, and aircraft out of place for the next bank of departures. (flysfo.com) ### What should travelers take from this? The lesson isn’t that SFO had a freak collapse. It’s that routine weather can still knock a major airport off rhythm fast, especially on a busy weekend. If you’re flying through San Francisco, the practical move is to watch the FAA and airline status pages early, not just your boarding time. When low ceilings show up at SFO, the disruption often starts upstream — before your aircraft even leaves the previous city. (nasstatus.faa.gov) ### Bottom line This was a classic modern air-travel failure — not one catastrophe, but a thin-margin system running out of room. Low clouds started it. FAA flow controls spread it. And by the time passengers saw the board, the damage was already baked in. (nasstatus.faa.gov) (flysfo.com)
