Flight Delays Top 5,000 Thursday: U.S. Hubs Facing the Biggest Slowdowns

U.S. flight delays climbed past the 5,000 mark on Thursday, September 17, 2026, as weather, construction, and traffic-management programs squeezed arrival capacity at several major hubs, pushing connection-heavy itineraries into longer waits.

FAA programs target five major airports as delays mount

Publicly available FAA system summaries on Thursday showed multiple Ground Delay Programs in effect at Boston Logan (BOS), Ronald Reagan Washington National (DCA), Chicago O’Hare (ORD), San Diego (SAN), and San Francisco International (SFO). These initiatives are designed to meter arrivals when runway capacity or airspace flow cannot match scheduled demand, limiting how many flights can be released toward a constrained destination at any given time.

As of the FAA’s published summary update Thursday evening, the listed average delays varied widely by airport and cause: BOS was posted with an average delay of 136 minutes tied to runway and taxiway construction; ORD with 104 minutes tied to weather and wind; SFO with 77 minutes tied to low ceilings; SAN with 40 minutes tied to volume; and DCA with 30 minutes tied to thunderstorms.

Separately, large-scale tracking totals from FlightAware showed thousands of delays across the U.S. system during the day, underscoring how quickly constraints at a handful of hubs can ripple outward as aircraft and crews arrive late and subsequent flights depart behind schedule.

Boston Logan stands out for the longest posted average delays

Among the FAA’s major delay programs on Thursday, Boston Logan was one of the most heavily constrained by the numbers, with the FAA’s BOS status page indicating arriving flights delayed on average by roughly an hour or more during the afternoon update window. The publicly posted reason in system summaries pointed to runway and taxiway construction, which can lower the number of safe arrivals per hour even in otherwise workable weather.

For travelers, construction-driven constraints can be especially disruptive because they tend to follow set work windows rather than dissipating quickly like a passing storm. That can make it harder for schedules to “snap back” later in the day, especially when aircraft rotations depend on a tight series of turns.

The practical takeaway for passengers connecting through Boston on Thursday was that inbound arrival metering could translate into late gates and compressed connection times, even if a departure airport outside New England appeared clear.

Chicago O’Hare delays can cascade nationwide

Chicago O’Hare, one of the country’s highest-volume connection hubs, was posted under a Ground Delay Program with an average delay of 104 minutes, with the reason described in FAA summaries as weather and wind. When arrival rates are reduced at a hub of that scale, the impact often extends far beyond local weather because late inbound aircraft can trigger late outbound departures across multiple time zones.

O’Hare’s role as a network connector means even passengers who never set foot in Chicago can feel the effects if their aircraft, crew, or inbound leg originates there. Once rotations slip, airlines may need to swap aircraft or adjust connections, and later flights can become vulnerable to rolling delays and, in some cases, cancellations if a schedule cannot be recovered by evening.

Earlier this year, the FAA highlighted Chicago O’Hare as a location where sustained congestion and operational strain can force broader traffic-management interventions, a reminder that day-to-day delay programs are often part of a larger effort to keep the national system from gridlocking.

San Francisco delays persist amid low ceilings and runway constraints

On the West Coast, the FAA’s Thursday summary showed SFO under a Ground Delay Program with an average delay of 77 minutes, attributed to low ceilings. Low clouds and reduced visibility can cut arrival throughput because aircraft spacing requirements increase under instrument conditions, limiting the number of landings per hour.

San Francisco’s delay picture in recent weeks has also been shaped by runway-related constraints. Published coverage has pointed to a major runway repaving project that has reduced flexibility in runway use, complicating recovery when weather conditions deteriorate and pushing more flights into longer holding patterns on the ground or delayed release times from their departure airports.

For travelers, that combination matters: when weather restrictions and infrastructure constraints overlap, the recovery timeline often depends not only on improving skies but also on how quickly the airport can rebuild arrival and departure banks without clogging taxiways and gates.

Washington-area thunderstorms expand the disruption footprint

In the Mid-Atlantic, the FAA’s program summary listed DCA with an average delay of 30 minutes tied to thunderstorms. But FAA restriction postings also showed a broader regional traffic-management action affecting routes into the Washington area, including DCA, Baltimore-Washington International (BWI), and Washington Dulles (IAD), reflecting how convective weather can influence multiple airports that share the same airspace and arrival corridors.

This is one of the most common ways travelers experience “surprise” delays: a flight can be held on the ground at a departure airport far from the storm because the destination airport’s arrival capacity is temporarily reduced. When that happens, airlines may keep passengers at the gate longer, sometimes delaying boarding, to avoid long taxi waits and missed arrival slots.

For passengers traveling Thursday, the most reliable way to gauge risk was to check airport-wide delay programs in addition to a single flight’s status. A flight marked “on time” earlier in the day can still pick up a significant delay if a Ground Delay Program is extended or expanded as storms redevelop.