Flight disruptions at San Francisco International Airport on June 8 are rippling across the global network, with aviation tracking data showing 307 delayed departures and arrivals and two cancellations affecting United, JetBlue, SkyWest, Alaska and other carriers that link the Bay Area to destinations across the United States, Canada, Mexico, Europe and Asia.

Get the latest news straight to your inbox!

SFO Flight Delays Ripple Across Global Routes

Ground Delays Slow Departures At Key West Coast Hub

San Francisco International Airport operated under a formal ground delay program on June 8, with the Federal Aviation Administration’s national airspace status page listing SFO as subject to arrival management controls. That designation typically reflects capacity constraints in the tower or approach control and leads to longer-than-normal taxi and hold times for flights headed into the Bay Area hub.

Publicly available airport data and flight-tracking dashboards indicate that by mid-afternoon, 307 flights into and out of SFO had been delayed and at least two had been cancelled. While the majority of services continued to operate, the cumulative effect was longer travel days, tighter connections and significant schedule compression during peak banks of flights.

Weather, runway use and air traffic staffing have all contributed to periodic constraints at SFO in recent months, according to published coverage and historical airport performance reports. When arrival rates are reduced, the system-wide impact tends to be magnified because San Francisco functions as both a transcontinental gateway and a major transfer point for long-haul international services.

The FAA’s traffic management tools attempt to meter arrivals into the airport to keep operations safe and predictable, but that process often results in departure holds at origin airports around the United States and beyond. Passengers may see their flight listed as “on time” at the gate while facing an air traffic control hold that pushes actual wheels-up time significantly later.

United, JetBlue, SkyWest And Alaska Bear The Brunt

Schedule data filed with regulators show that United Airlines is SFO’s largest tenant by a wide margin, with regional affiliates such as SkyWest operating many of its United Express-branded routes. Alaska Airlines, JetBlue and several other domestic and international carriers also maintain sizable operations at the airport, positioning SFO as one of the West Coast’s busiest connecting hubs.

On June 8, that concentration meant United and its partners absorbed a significant share of the 307 reported delays. Regional jets operated by SkyWest on behalf of major brands saw knock-on effects as delays on early flights cascaded into afternoon rotations, particularly on short-haul routes up and down the West Coast and into the Mountain West.

Alaska and JetBlue, which both use San Francisco as part of their broader transcontinental and West Coast networks, also experienced schedule pressure. Even modest initial holds of 30 to 45 minutes can create crewing and aircraft-positioning challenges later in the day, compounding the disruption for passengers booked on onward connections.

Airline operational plans, investor filings and public performance rankings have long highlighted how a constraint at a single major hub can quickly translate into misconnects and forced rebookings across a carrier’s entire network. The June 8 pattern at SFO follows that familiar dynamic, as aircraft and crews arrived late, shortening turnaround times and putting subsequent departures behind schedule.

San Francisco’s role as an international gateway meant that June 8 delays were not confined to short domestic hops. Flight-tracking services showed schedule disruptions on services connecting the Bay Area with cities in Canada and Mexico, as well as long-haul routes to Europe and Asia that feed corporate, technology and tourism traffic.

Among the affected markets were transatlantic links to Italy and Spain, where evening departures from SFO feed overnight arrivals into major European hubs. Delays on those departures can push arrival times into mid-morning, tightening already short connection windows for onward flights across the continent and requiring some travelers to be rebooked.

In the Pacific, flights touching China, Japan, South Korea and Singapore were also exposed to the knock-on effects of the ground delay program. Because these sectors often exceed 10 hours in duration and operate within constrained slot regimes at their destination airports, even slight delays in leaving San Francisco can trigger a chain of schedule adjustments on both sides of the ocean.

Carriers typically prioritize operating these long-haul services rather than cancelling them, given their high revenue contribution and the difficulty of reaccommodating passengers. As a result, airlines may hold flights to wait for connecting customers from delayed feeders, further shifting departure times and driving late-night arrivals back into SFO.

Travelers Face Missed Connections And Longer Journeys

For travelers, the operational nuances behind an FAA ground delay program translate into practical headaches. Publicly available consumer forums and social media posts in recent days have described missed connections, overnight diversions and extended tarmac waits tied to air traffic constraints in the Bay Area.

Passengers booked on multi-leg itineraries through San Francisco on June 8 were particularly at risk when their inbound flights arrived late, leaving fewer options to connect onward the same day. This was especially pronounced on routes involving smaller Canadian and Mexican cities, as well as secondary markets in Europe and Asia that may only see a single daily frequency.

Some travelers reported being automatically rebooked by airline mobile apps onto later services or alternate routings through other hubs such as Los Angeles, Denver or Seattle. Others faced longer lines at customer service desks as they sought hotel vouchers, meal credits or revised itineraries, depending on each carrier’s policies and the cause of delay attributed in their reservation records.

Data published by aviation regulators show that on-time performance can vary widely by carrier and route, but large, complex hubs like San Francisco tend to experience higher variability when weather or air traffic constraints reduce capacity. June 8 offered another example of how those fluctuations can ripple through the experience of passengers far beyond the Bay Area.

What Passengers Can Do On High-Disruption Days

While the June 8 disruptions at SFO were driven in part by factors outside airline and passenger control, travel experts and consumer advocates frequently recommend a few strategies to reduce the impact of similar events. Monitoring flight status across multiple platforms, including airline apps and independent trackers, can provide early warning of holds or reroutes.

Booking earlier flights in the day, when possible, can also create more buffer for rebooking if something goes wrong. Historical performance data often show that delays accumulate as the day progresses, particularly at weather- and traffic-sensitive airports like San Francisco.

Travelers making critical connections to long-haul services to Europe or Asia may choose longer layovers than minimum connection times suggest, trading some time in the terminal for a greater margin of safety. In the event of widespread disruption, having airline customer service phone numbers, app messaging and airport agents all as options can speed the process of securing an alternate itinerary.

As summer travel ramps up across the Northern Hemisphere, industry performance metrics and recent patterns at SFO suggest that passengers connecting through major hubs may continue to face elevated disruption risk on peak days. The June 8 episode underscores how quickly conditions at a single airport can cascade into a global web of delayed arrivals and departures.