US Flight Delays: Low Clouds Snarl Hubs as DOT Refund Rules Hold

A week of gray skies, not storms

In the last week of October 2026, the biggest problem for US air travel was low cloud cover, not hurricanes or blizzards. The FAA flagged low ceilings at one group of major airports after another. Day after day, the national count of delayed flights ran into the hundreds by morning and kept climbing into the evening.

The pattern was easy to see in the FAA's daily outlooks. For Thursday, October 29, the agency said low clouds could slow traffic in Austin, San Antonio, Seattle and all three Washington, D.C.-area airports: BWI, DCA and IAD.11 By 10:06 a.m. Eastern that morning, FlightAware had counted 580 delays and 53 cancellations on flights touching the United States, and 8,604 delays worldwide.14 Morning snapshots showed holds of 15 minutes or less at Austin and Seattle, which looks modest. The effect was cumulative, though, because aircraft that fall behind early carry that lateness into every later leg of the day.14

Two days earlier, the pressure was in the West. The FAA's operations plan for Tuesday, October 27 listed low ceilings and reduced visibility at Denver and low ceilings at Seattle-Tacoma. It also listed a possible ground stop or delay program at San Diego.13 By 11 a.m. Eastern, FlightAware showed 784 US-related delays and 32 cancellations.18 By 6:45 p.m. those numbers had grown to 1,886 delays and 52 cancellations, with more than 12,000 delays worldwide.19 Nearly 800 delays by midday turning into nearly 1,900 by evening shows how much worse a manageable morning can get as the hours pass.

On Monday, October 26, the FAA's list was broader. It flagged low clouds at Chicago O'Hare, Midway, Denver, Detroit, San Francisco and Seattle, plus gusty winds at Fort Lauderdale, Orlando, Miami and Tampa.12 San Francisco was already running a weather ground delay program, with arriving flights held an average of about 58 minutes.1215

Why low clouds matter so much

Low cloud does not sound dramatic, but it directly reduces how many flights an airport can handle. The National Weather Service says instrument flight rules apply when the cloud ceiling is below 1,000 feet or visibility is under three miles. Under those rules, controllers have to space arriving aircraft farther apart, so fewer planes can land each hour.13 When a hub loses some of its arrival slots during a busy period, the delays spread to every airport that feeds it.

This week, construction made the weather worse. Denver had Runway 16R/34L closed until November 5, and Seattle had Runway 16C/34C closed until November 15.1215 Taking a runway away at an airport already slowed by low ceilings leaves controllers with very little room. That probably helps explain why Denver and Seattle kept appearing on FAA watch lists all week.1213

This was not a one-off. On October 23, a mix of low ceilings in the Pacific region and heavy traffic elsewhere produced 3,287 US delays and 121 cancellations by mid-afternoon. Austin was under a ground delay advisory averaging 75 minutes, and San Francisco's averaged 57 minutes.20 Southwest alone had 877 of those delays, roughly a quarter of the national total.20 My reading: with schedules this full, the system has very little slack, so even routine autumn weather can cause large disruptions.

Where the coverage agrees, and where it overreaches

The more careful reports were clear that an FAA advisory is a forecast of possible restrictions, not proof that they happened. They noted that some listed contingencies, such as the San Diego delay program, were never directly tied to low clouds.13 Local TV coverage of the October 27 disruptions also noted that the FAA did not blame weather for every delay FlightAware recorded.19 Readers should treat the national totals as a picture of the whole system, not as a count of weather victims. Some stories blurred that line by describing the full tally as delays caused by cloud cover.1417

That difference matters, because what passengers are owed depends on why a flight was delayed.

What passengers are actually owed

The Department of Transportation's refund rules still apply. If an airline cancels a flight, for any reason, and the passenger chooses not to travel, the passenger is owed a refund. That includes passengers who turn down a rebooking.22 Weather does not remove this right. The refund rules cover weather cancellations and delays too.24 A "significant change" also triggers a refund if you decline to travel. That includes an arrival three or more hours late on a domestic trip, or six or more hours late on an international one.2529 Refunds must be automatic, go back to the original form of payment, and arrive within seven business days for credit card purchases or 20 calendar days for other payment methods.2425

The main catch is that once you accept a rebooked flight, or take the delayed flight, you lose the refund.2230 The US system also does not pay cash compensation for delays in the way the EU's Regulation 261 does. The DOT rule gives you your money back. It does not pay extra for the inconvenience.2526

Care during a delay, such as meals and hotels, is a separate matter, and this is where weather counts against passengers. Most large US airlines have committed to covering meals and hotels when a disruption is within their control.22 Weather-related FAA flow restrictions are treated as outside airline control, so those commitments generally do not apply. Problems like IT outages or staffing shortfalls do trigger them.17 On a low-cloud day, a stranded traveler can usually get a refund but probably not a hotel voucher.

There is also a regulatory change in progress. In December 2025, the DOT paused enforcement of one narrow part of the refund rule. The paused provision treated a renumbered flight as a cancellation, even when the passenger was rebooked under the new number and nothing about the trip significantly changed. The pause ran until June 30, 2026.21 The department also started a new rulemaking, called "Refund III," to redefine what counts as a cancelled flight. It had earlier targeted February 2026 for a proposal.21 Explainers broadly agree the exception is narrow. Actual cancellations, significant-change refunds and baggage-fee refunds all remained enforceable.27 Still, airlines will be pushing to define "cancellation" more narrowly, and travelers should watch how Refund III turns out.

An earlier DOT proposal went much further. It asked for comment on requiring cash compensation, free rebooking, meals and lodging when a disruption is the airline's fault.23 Nothing in this week's coverage suggests it has become a binding rule. This week's travelers had refunds and voluntary airline commitments, nothing more.

Strikes: mostly a European story this month

For travelers worried about strikes, the US picture was fairly calm. Horizon Air flight attendants, who work for an Alaska Air Group subsidiary, held a system-wide day of action on October 14 to push for a new contract. The airline said bargaining with a mediator had produced tentative agreements on 12 contract articles.37 That was a protest, not a walkout that grounded flights.

The bigger risks were elsewhere. Five French crew unions called a five-day strike of pilots and cabin crew for October 17–21 over a pension rule, timed for the start of France's autumn school holidays.33 The unions suspended the notice on October 9 while they wait for a government decree. Coverage described this as a pause, not a settlement.3138 In Mexico, Aeromexico's pilots rejected the airline's latest offer but extended talks by up to 45 days. That pushes any strike to around mid-November, and the airline says flights are operating normally.34 easyJet crew in Italy planned a 24-hour strike on October 16.39 Americans with connections through Paris or Mexico City should keep watching, because both disputes remain unresolved.

Security lines: conflicting numbers

Reports on airport security wait times did not agree. One travel site described a nationwide checkpoint crisis in mid-October. It reported PreCheck waits of 95 minutes in Atlanta and 85 minutes at O'Hare, which it blamed on a backlog and a surge in REAL ID enrollment.2 Other data pointed the other way. A 2026 analysis of the 50 busiest US airports found an average wait of 9.9 minutes. O'Hare had the second-longest average at 20.2 minutes, and San Antonio was fastest at 3.7 minutes.74 Live readings late in the month showed SFO at single-digit waits and LaGuardia's checkpoints at a few minutes.35 Atlanta's own checkpoint board showed waits between 4 and 20 minutes in one reading.1

The crisis account is the outlier, and the large-sample and live data deserve more weight. Peak-hour spikes are real, though. Raleigh-Durham's standard lanes, for example, can reach 35–50 minutes during the morning rush.10 Checking the airport's live checkpoint data before leaving home is more useful than any national average.

The takeaway

This week's disruptions were caused by the system's own limits, not by one dramatic event. Low ceilings at hubs that were already short a runway, on schedules with little spare capacity, were enough to produce delay counts in the thousands. For passengers, the advice is the same as before. You have a firm right to a refund if you decline to fly, and you lose it if you accept a rebooking or voucher. Meals and hotels depend on whether the airline caused the problem. On a low-cloud day, that usually means passengers absorb the inconvenience themselves.