San Francisco Ground Delay Program, Monday 16 November
On Monday morning, San Francisco International Airport faced a new disruption — and it was not the ground stop. Low cloud ceilings and rain forced the FAA to restrict arrivals, with an average departure delay of 2 hours 46 minutes. This page is about that weather disruption, which is a separate event from Friday's nationwide ground stop, and it says so at every step.
In short
DEVELOPING — checked about 06:25 ET on Monday 16 November 2026. San Francisco International Airport was under a Ground Delay Programme on Monday morning because of low cloud ceilings and rain — a weather disruption, separate from Friday's nationwide ground stop. The FAA advisory put the initial average departure delay at 2 hours 46 minutes (166 minutes) for flights heading to San Francisco, with a maximum assigned delay of 895 minutes and an arrival rate of 36 aircraft per hour. The morning programme was cancelled by the FAA at 07:32 UTC (02:32 ET). The FAA's later operations plan identified the possibility of a further ground stop or ground delay programme after 16:00 UTC (11:00 ET) if low ceilings and rain continue — that is developing and unconfirmed, and this page will be updated after 11:00 ET. Do not present the 166-minute figure as a live delay after the programme was cancelled.
What happened on Monday morning
Low cloud ceilings and rain over San Francisco Bay forced the FAA to restrict arrivals at San Francisco International Airport on Monday morning, 16 November 2026. The tool was a Ground Delay Programme — a GDP — which assigns each departing flight a later departure time so that arrivals at the destination are spaced at a rate the airport can handle. The initial programme covered arrivals from 05:00 to 07:59 UTC and included departures from across the contiguous United States as well as Edmonton, Vancouver and Calgary. The FAA advisory, reported by Travel and Tour World on 16 November, put the initial average departure delay at 2 hours 46 minutes — 166 minutes — for flights heading to San Francisco, with airborne delays of 15 minutes or less and a programme arrival rate of 36 aircraft per hour. The 166-minute figure relates to the earlier programme: the FAA cancelled the morning GDP at 07:32 UTC, which is 02:32 ET, so the figure should not be presented as a live delay after that time.
Why low clouds cut San Francisco's capacity by a fifth
San Francisco's capacity falls in low visibility because of its runways. The airport's closely spaced parallel runways sit about 750 feet apart, and in low cloud ceilings they cannot run simultaneous approaches — aircraft must arrive one at a time rather than in parallel pairs. The programme arrival rate of 36 aircraft per hour compares with about 45 per hour in good visibility, a cut of roughly a fifth. That is the mechanism behind the delays: the same number of aircraft trying to arrive at an airport that can accept a fifth fewer of them per hour, with each one assigned a later departure time to spread the arrivals out. It is a weather problem with an infrastructure cause, and it is the reason San Francisco is more vulnerable to low cloud than an airport with widely spaced runways. The ground stop, by contrast, was a communications failure — a different cause, a different mechanism, and a different remedy.
This is not the ground stop — and why the distinction matters
The Monday San Francisco disruption is a weather event. Friday's nationwide ground stop was a communications failure in the FAA network after router work at El Dorado, Arkansas, and Amarillo, Texas. The two share a symptom — delayed and cancelled flights — and nothing else. Conflating them would mislead readers in both directions: it would make Monday's weather look like a new failure of the air traffic control system, and it would make Friday's ground stop look like a weather event. The distinction also matters for passenger rights. A weather delay is treated the same way as a ground-stop delay for refunds — a significant change of 3 hours domestic or 6 hours international, and you choose not to fly, triggers the refund — but the cause is different, and the reporting should say so. This site's San Francisco airport page covers the ground-stop weekend at SFO; this page covers Monday's weather programme.
What may happen after 11:00 ET — developing
DEVELOPING. The FAA's later operations plan for Monday identified the possibility of a further San Francisco ground stop or ground delay programme after 16:00 UTC, which is 11:00 ET, if low ceilings and rain continue. That is a possibility in a planning document, not a confirmed restriction: whether a new programme is imposed after 11:00 ET was not known at the time this page was checked, about 06:25 ET on Monday 16 November. This page will be updated after 11:00 ET with the outcome. Until then, passengers flying to San Francisco should check the airline app and FlightAware before travelling, and should not assume that the cancellation of the morning programme means the day is clear. If a new programme is imposed, the delay figures for it will be reported with their own snapshot time, and the 166-minute figure from the morning programme will not be reused for it.
What to do if your San Francisco flight is delayed
Check the airline app for your flight status before leaving for the airport, and keep checking: a weather delay can lengthen, shorten, or turn into a cancellation as the cloud ceiling moves. Do not cancel your own ticket while the delay is still developing — the refund right is strongest when the airline cancels or makes a significant change. If the delay passes 3 hours on a domestic flight or 6 hours on an international flight, you can decline the flight and claim a full refund to your original payment method. If you are connecting through San Francisco, ask the airline whether the connection will still work: a two-hour delay on the first leg can mean a missed connection even if the first flight still operates. Keep receipts for anything you buy while waiting, and keep the airline's delay notice. For the current position at San Francisco, check FlightAware's SFO page or the United app — United operates the major hub there — before travelling.
Frequently asked questions
No confirmed ground stop as of about 06:25 ET. San Francisco was under a weather Ground Delay Programme on Monday morning, which the FAA cancelled at 07:32 UTC (02:32 ET). A further programme after 11:00 ET is possible and developing — not confirmed.
Low cloud ceilings and rain. The airport's closely spaced parallel runways, about 750 feet apart, cannot run simultaneous approaches in low visibility, so the arrival rate fell to 36 aircraft per hour against about 45 in good weather.
The initial average departure delay was 2 hours 46 minutes (166 minutes), with a maximum assigned delay of 895 minutes, under the morning programme. That figure relates to the programme before it was cancelled at 07:32 UTC — do not present it as a live delay after cancellation.
No. Monday's San Francisco disruption is weather. Friday's nationwide ground stop was a communications failure after router work. They share a symptom — delays — and nothing else.
A programme that assigns each departing flight a later departure time (EDCT) so arrivals are spaced at a rate the destination can handle. It meters traffic; a ground stop halts it.
Figures are given with their snapshot time and source. Developing items are marked as developing. Last checked Monday 16 November 2026, about 06:25 ET.