MSP logs 100+ delays after East Coast air traffic control outage

Minneapolis-St. Paul International Airport (MSP) saw more than 100 flight delays ripple into Minnesota after an East Coast air traffic control outage disrupted operations at major Northeast hubs on Monday, Sept. 21, 2026, snarling schedules well beyond the region where the technical failure occurred.

What happened on the East Coast and why it affected MSP

Published coverage describes a communications breakdown linked to the Philadelphia-area air traffic control system that prompted the Federal Aviation Administration to impose ground stops and delays at multiple airports serving the New York and Philadelphia corridors. Those restrictions slowed departures headed west and interrupted inbound aircraft rotations that normally feed schedules at airports across the country, including MSP.

The disruption was tied to damaged fiber lines supporting air traffic communications and radar operations in the region. Reports indicate the primary communications line failed, and a backup fiber optic line was also compromised, creating a prolonged interruption that forced controllers to operate with reduced capability until repairs were completed.

Because MSP has heavy daily connectivity to the New York and Philadelphia markets, even short ground stops on the East Coast can cascade into later flights in Minneapolis and St. Paul. When aircraft and crews are held in place or arrive late from the Northeast, the next legs on their schedules frequently depart behind plan or face cancellations when legal crew duty limits are reached.

MSP delay count and what travelers saw Monday

By midafternoon Monday, published coverage tracking MSP operations showed more than 130 delayed arrivals and departures and several cancellations, a snapshot that can shift throughout the day as airlines swap aircraft and re-time departures to rebuild their networks. The delays reflected both direct impacts on flights to the Northeast and indirect disruptions from aircraft and crews arriving late from other cities.

MSP’s public flight boards showed a mix of on-time and delayed departures Monday evening and into early Tuesday, illustrating how a national disruption can affect individual routes differently depending on when a plane was scheduled to arrive, where it came from, and whether it could be substituted with another aircraft.

The FAA’s airport-status information for MSP later in the day indicated relatively modest general delays at the field itself, suggesting the primary driver of passenger disruption was the network effect from elsewhere rather than a major operational constraint inside the Twin Cities airspace.

Northeast ground stops: Newark, Philadelphia, and New York-area hubs

The outage’s epicenter was the Northeast, where ground stops and ground delays were issued at airports including Newark Liberty International, Philadelphia International, and New York-area airports such as JFK and LaGuardia. Published accounts described long holds and extensive flight backlogs as the region worked to resume normal traffic flows.

One widely cited data point from flight tracking coverage was the length of time Newark saw severely constrained arrivals, reflecting how a single major hub’s disruption can overwhelm reroute options and quickly spread delays to other airports that depend on the same aircraft rotations.

Reports also noted that the timing coincided with heightened travel demand into New York City for the United Nations General Assembly, increasing pressure on an already congested airspace system and making recovery more complex once operations began resuming.

What to do if you’re flying through MSP after a network disruption

For travelers departing MSP during a disruption rooted elsewhere, the most important step is to verify the status of the specific flight number with the operating airline before leaving for the airport. Even when the local airport is moving normally, a flight can still be delayed if its inbound aircraft is late, its crew is out of position, or the destination airport is still under traffic-management restrictions.

Rebooking decisions often depend on whether the trip involves a tight connection through an East Coast hub. If an itinerary includes a connection at a constrained airport, a later nonstop from MSP to the final destination, or a reroute through a different connecting city, can sometimes reduce risk, though availability may be limited while airlines work through backlogs.

Airlines commonly publish temporary travel waivers during major air traffic control events, allowing date changes or alternate routings without a change fee for eligible tickets. Travelers typically need to act within the waiver’s stated date window and may still pay any fare difference, so checking the airline’s waiver terms for MSP routes to the Northeast can be useful before changing plans.