More news on this day
U.S. air travelers faced a rough Thursday as flight delays climbed past 7,000 amid a mix of thunderstorms, runway construction, and Federal Aviation Administration traffic-management programs that squeezed capacity at several major hubs.
Get the latest news straight to your inbox!

Where delays were concentrated on Thursday
Publicly available flight-tracking tallies showed systemwide disruption building through the day on Thursday, September 17, 2026, as constraints at a handful of high-volume airports spread across airline networks. When hubs slow down, aircraft and crews arrive late to their next assignments, which can cascade into missed connections and rolling delays into the evening banks.
FAA air-traffic planning guidance for Thursday flagged thunderstorms as a potential driver of slowdowns in Chicago (O’Hare and Midway), South Florida (Fort Lauderdale and Miami), and Houston (Hobby and Intercontinental). The same FAA report also highlighted gusty wind as a possible factor in Denver and Philadelphia, and low clouds as a concern in San Francisco.
By late Thursday into early Friday UTC updates, the FAA’s National Airspace System status pages showed multiple programs affecting key airports, underscoring how the day’s disruption was not tied to a single cause or region. For travelers, that matters because mitigation strategies differ: weather-related issues may ease quickly, while construction or staffing constraints can persist over long windows.
Boston Logan: runway construction and long arrival delays
Boston Logan International Airport was among the most constrained major airports on Thursday, with FAA traffic-management information showing construction-related limits on arriving traffic. The FAA indicated that flights headed to Boston were experiencing destination-specific delays averaging 2 hours and 16 minutes under the program.
That kind of destination-driven delay can catch travelers off guard because flights may appear “on time” at the origin early in the day, then absorb holding time later through gate holds, taxi delays, or metered departure slots designed to manage Boston’s arrival rate. Travelers connecting through Boston can see knock-on effects if inbound aircraft arrive late and turn times compress.
Boston’s issues also illustrate how a localized capacity reduction can weigh on the Northeast corridor, where airports sit close together and share congested airspace. Even travelers not flying to Boston may experience indirect effects when aircraft and crews are displaced from their scheduled rotations.
Chicago O’Hare: storms and operational constraints ripple nationwide
Chicago O’Hare International Airport, one of the nation’s busiest connecting hubs, was a focal point for Thursday’s delays as storms moved through the region. Published coverage described FAA ground stops early in the morning at both O’Hare and Midway, with the ground stop for O’Hare ending around 7:15 a.m. local time and average delays near two hours expected to linger during the day.
FAA system status information also showed an overnight program affecting O’Hare tied to staffing, with average delays listed at more than two hours at times. In practice, Chicago’s mix of weather and capacity limits can be especially disruptive because so many itineraries rely on tight connections across multiple airlines.
As delays stack up in Chicago, travelers may see fewer same-day rebooking options than expected. Even if seats are available, late-arriving aircraft can mean fewer planes physically positioned to operate the recovery schedule, and crews may run into duty-time limits that force additional substitutions or cancellations.
Other airports under FAA programs: Washington, San Francisco, San Diego, Seattle
Beyond Boston and Chicago, FAA National Airspace System status pages showed multiple airports operating under traffic-management programs during the Thursday-to-Friday update window. Those included Ronald Reagan Washington National, Las Vegas, San Diego, Seattle, San Francisco, and others, with listed causes spanning thunderstorms, wind, volume constraints, construction, and low ceilings.
For travelers, these programs matter because they are not airline-specific. A flight can be delayed even if the aircraft is ready and the weather at the departure airport looks fine, simply because the destination airport is metering arrivals or limiting acceptance rates.
San Francisco’s low ceilings, for example, can reduce arrival rates and create airborne and ground delays during certain weather patterns, while volume-related programs at airports like San Diego can slow flow when demand peaks. In the Pacific Northwest, construction-related constraints can similarly compress capacity, adding friction during busy arrival banks.
What travelers can do right now to manage disruption risk
On heavy-delay days, the most useful first step is to separate a single-flight status update from broader airport conditions. Checking FAA airport status and delay programs alongside an airline’s app can help travelers understand whether a delay is likely to worsen or whether recovery is possible once a weather cell passes or a traffic-management window ends.
When major hubs are constrained, travelers with connections can reduce risk by evaluating same-day reroutes that avoid the most affected airports, even if the alternate itinerary is less direct. Rebooking earlier departures can also help because delays tend to compound later in the day as aircraft and crews fall behind schedule.
For passengers already at the airport, keeping an eye on the operational picture can guide practical decisions such as staying airside to preserve rebooking flexibility, confirming bag status if a connection is missed, and checking whether the destination airport is under a metering program that could hold departures at the gate. The key is acting early, before irregular operations reduce the pool of available seats on later flights.