Boston Logan Ranks Most Disrupted US Airport on Sept. 14 With 495 Events

Boston Logan International Airport (BOS) appeared to be the most disrupted major U.S. airport on Monday, September 14, after flight-tracking data tallied 495 total disruptions, a combined count of delays and cancellations that rippled across airline networks throughout the day.

What the 495 “disruptions” represent

The 495 figure is typically presented as the combined total of delayed and canceled flights attributed to a specific airport over a defined period, most often a single day. In publicly available flight-tracking summaries for September 14, the disruption total at Boston Logan was broken down as 412 delays and 83 cancellations.

Those numbers can shift during the day as schedules update, aircraft rotate in and out of position, and airlines make late cancellations. Separate dashboards that focus only on cancellations can also show different totals depending on the time of capture and filtering methods, underscoring why “disruptions” is often used as a broader real-time snapshot rather than a final audited total.

FAA operational status pages also reflected Logan’s constrained environment on September 14, showing the airport’s live status information and system updates posted that day. Independently, flight-tracking pages for BOS showed arrival delays and inbound delays at origin airports, indicating congestion effects extending beyond Boston itself.

FAA flow programs and regional knock-on delays

One reason disruptions can pile up quickly at a hub like Logan is the use of traffic management initiatives that meter arrivals when airspace or runway capacity tightens. Public FAA feeds and third-party trackers based on those feeds showed a ground delay program involving flights destined for Boston, with reported average and maximum delays posted as the program ran.

Notably, some of the listed impacted departure points were in eastern Canada, a sign that flow constraints were being managed well before aircraft reached New England airspace. When departure slots are held at origin airports, the effect shows up as “delayed at origin,” and that can cascade into later segments for the same aircraft and crew.

On the day of heavy disruption, flight-tracking airport status pages for BOS also displayed arrival delay metrics for airborne aircraft and inbound delays, reinforcing the picture of constrained throughput rather than a localized issue affecting only one terminal or one carrier.

Weather and operational constraints around Boston

September can bring fast-changing conditions in coastal New England, and aviation weather observations for Boston Logan on September 14 showed gusty winds around the time of reporting. Even when visibility remains acceptable, stronger gusts and shifting wind direction can tighten arrival rates, alter runway configurations, and raise spacing requirements between aircraft.

Broader delays also tend to increase when weather interacts with other constraints, including air traffic management initiatives and demand peaks. For travelers, that combination often translates into late gate departures, extended taxi times, missed connections, and aircraft arriving out of sequence for later turns.

Separately, recent publicly distributed Massport information has highlighted runway safety work at Logan continuing through September and October, with the agency noting that travelers may experience delays, particularly during periods of inclement weather, air traffic constraints, or other operational disruptions. While that does not by itself explain a single day’s totals, it adds context to why the system may have less slack during irregular operations.

Why Logan can top national disruption lists on a single day

On days when multiple large airports are dealing with storms or congestion, the “most disrupted” label can come down to where delays and cancellations are most concentrated. In the September 14 snapshot, published coverage tying together FlightAware-based data and nationwide delay totals placed Logan at the top of the disruption count, even as other airports also reported significant delays.

Logan’s role as a focus city for several carriers and a key transatlantic gateway means irregular operations can spread quickly into the national network. When inbound aircraft arrive late, the result is often a higher share of delayed departures, and cancellations may follow if crews time out or aircraft cannot be repositioned efficiently.

Public airport-traffic reporting also shows Logan handling substantial monthly flight activity, which can amplify the visible impact of even moderate capacity reductions. When arrival rates dip for a few hours, backlogs can take much of the day to unwind.

What travelers can do when disruptions spike

For passengers traveling through Boston during high-disruption periods, the most time-sensitive step is verifying the flight’s status using the airline’s app alongside FAA and independent flight-tracking airport status pages. Flight-tracking airport dashboards can show whether delays are primarily “inbound,” “at origin,” or “arrival delays for airborne aircraft,” which helps set expectations before heading to the terminal.

Rebooking options are often best early in the disruption cycle, before later flights fill up. If a flight is canceled, airlines frequently reroute travelers through alternate hubs, and Boston-area flyers sometimes look at nearby airports depending on destination and seat availability, though the feasibility depends on the airline’s policies and same-day inventory.

Travelers are also likely to see the biggest schedule swings in late afternoon and evening, when accumulated delays compress turnaround times. Even if the weather improves, aircraft and crews may be out of position, keeping departure boards uneven well after the initial cause has passed.