The Federal Aviation Administration has cut the number of flights that can land at San Francisco International Airport each hour from 54 to 36, a one-third reduction that will stretch wait times for travelers passing through one of the West Coast’s busiest hubs. The change results from two overlapping factors: a runway closure for construction and a separate FAA rule revision governing how planes approach closely spaced parallel runways. For passengers, the math is simple: fewer landing slots per hour means more time circling in holding patterns or sitting on tarmacs at origin airports waiting for clearance.
Why SFO Lost a Third of Its Arrival Slots
The capacity drop did not come from a single cause. Part of the reduction is tied to the closure of SFO’s north-south runway, which is undergoing repairs that take it out of service for an extended period. With that runway offline, the airport cannot distribute incoming traffic across as many strips of pavement, and controllers must funnel all arrivals onto the remaining east-west parallel runways.
But the runway project alone does not account for the full 18-flight-per-hour gap. The FAA has also revised its rules for parallel runway operations, tightening the procedures that govern how two streams of arriving aircraft can land side by side when runways sit close together. That rule change applies even after the north-south runway reopens, meaning some portion of the capacity squeeze could persist beyond the construction timeline.
How Parallel Runway Rules Shape Arrival Limits
SFO’s layout presents a challenge that few American airports share to the same degree. Its two primary parallel runways are separated by less distance than the standard threshold the FAA uses to allow fully independent simultaneous approaches. When runways are that close, controllers rely on specialized procedures to keep planes safely apart while still landing two at a time.
The FAA’s Aeronautical Information Publication describes two key techniques for these situations. Precision Runway Monitor approaches, known as PRM, use high-update-rate radar so controllers can watch each aircraft’s lateral position in near real time. Simultaneous Offset Instrument Approaches, or SOIA, stagger one plane’s flight path at an angle so it does not converge with the adjacent stream until both are close enough to the ground for pilots to see each other visually. Both methods include what the FAA calls controller breakout logic, a protocol that forces an immediate turn-away if any aircraft drifts toward the no-transgression zone between the two approach corridors.
These procedures work, but they impose hard limits on throughput. Every breakout maneuver creates a gap in the landing sequence. Every offset approach requires extra spacing to allow the angled aircraft to realign before touchdown. The FAA’s rule revision appears to have widened some of those safety margins, which directly reduces the number of planes that can touch down in any given 60-minute window.
What the Capacity Profile Tells Us
The FAA maintains official capacity profiles for major U.S. airports, and the agency’s Airport Capacity Profiles program publishes detailed assessments of how many operations each facility can handle under various runway configurations and weather conditions. SFO’s profile has long reflected the constraints of its closely spaced runways, and the airport’s throughput has historically been more weather-sensitive than that of hubs with wider runway spacing, like Dallas-Fort Worth or Denver.
The new 36-arrivals-per-hour figure represents a configuration that strips away the optimistic assumptions built into the old 54-per-hour rate. That prior number assumed all runways available, favorable visibility, and full use of PRM and SOIA procedures. Remove one runway and tighten the rules on the remaining two, and the theoretical maximum drops sharply. The gap between 54 and 36 is not a bureaucratic abstraction. It translates directly into longer ground delay programs, more holding patterns over the Pacific, and cascading schedule disruptions at connecting airports.
Ripple Effects Across Northern California Airspace
Most coverage of the SFO reduction has focused on passenger inconvenience at the airport itself, but the downstream effects on the broader air traffic system deserve attention. When SFO’s arrival rate drops, the FAA’s traffic management system pushes delays backward to origin airports through a mechanism called a Ground Delay Program. Flights bound for SFO from cities like Los Angeles, Seattle, or Phoenix are held at their departure gates or taxiways, sometimes for hours, so they arrive in a sequence that matches SFO’s reduced acceptance rate.
That redistribution of delay does not stay neatly contained. Aircraft stuck on the ground at LAX waiting for an SFO slot occupy gates and taxiway space that other flights need. Crews hit duty-time limits. Passengers miss connections. The effect is a slow-motion traffic jam that radiates outward from a single bottleneck. For airlines operating hub-and-spoke networks through SFO, particularly United Airlines, the arithmetic is punishing: fewer inbound flights per hour means fewer banks of connections, which means either longer layovers or fewer itineraries offered to passengers.
Regional carriers that feed SFO from smaller Northern California and Pacific Northwest cities face their own squeeze. With a lower cap on arrivals, mainline flights from large markets tend to win priority in schedule planning. That can translate into trimmed frequencies or off-peak departure times for smaller communities, subtly reshaping how and when those regions connect to the national network.
A Challenge That Outlasts the Construction
Runway repairs are temporary, but the FAA’s revised parallel approach rules are not. Once the north-south runway returns to service, SFO will regain some capacity, but the tighter separation standards for its closely spaced parallels will remain in effect. That means the airport’s peak arrival rate after construction may settle somewhere between the old 54 and the current 36, rather than snapping back to the pre-construction ceiling.
This distinction matters because it reframes the story from a short-term construction headache into a longer structural constraint on Bay Area air travel. Airlines, airport planners, and regional transportation agencies will need to account for a permanently lower throughput baseline when projecting future schedules and infrastructure investments. SFO has long been one of the most delay-prone major airports in the country, largely because of its runway geometry and frequent fog. Stricter approach rules add another layer of restriction on top of conditions that were already tight.
In practice, that could influence everything from how aggressively airlines bank arrivals and departures to how much slack they build into connection times. It may also sharpen debates over whether more traffic should be shifted to Oakland and San Jose, or whether demand management tools like congestion pricing for peak-hour slots should be on the table.
Safety, Capacity, and the Politics of Delay
Underlying the technical details is a familiar trade-off between safety margins and operational efficiency. The FAA’s decision to tighten procedures for closely spaced parallel runways reflects a conservative approach to risk in complex, high-density airspace. While passengers may experience the result as longer waits and missed connections, regulators are responding to scenarios in which a single blunder on approach could have catastrophic consequences.
For local officials and business leaders, though, the new arrival cap raises uncomfortable questions. The Bay Area economy depends heavily on reliable air links, not just for tourism but for high-value business travel and cargo. A structurally lower ceiling on SFO’s arrival rate could, over time, erode some of the airport’s competitive position relative to other West Coast gateways that do not face the same runway geometry constraints.
Any push to claw back capacity will have to grapple with the technical realities laid out in the FAA’s own guidance. As long as SFO’s runways remain as closely spaced as they are today, and as long as regulators insist on generous buffers around the no-transgression zone between approach paths, there is limited room to restore the old 54-arrivals-per-hour pace without compromising the safety standards that prompted the changes in the first place.
For travelers, the implications are straightforward even if the aeronautical engineering is not. Flying through SFO is likely to involve more schedule padding, more susceptibility to ripple-effect delays, and a greater premium on early-morning or late-evening departures that avoid the most constrained peak hours. The airport will remain a vital hub for the region, but the era of squeezing every last landing into the timetable appears to be closing, replaced by a more cautious, less forgiving operating environment that prioritizes separation over speed.
More from Morning Overview
*This article was researched with the help of AI, with human editors creating the final content.
