MSP Hit With 100+ Delays After East Coast Air Traffic Control Outage

Minneapolis-St. Paul International Airport (MSP) logged more than 100 delayed flights after a major air traffic control communications failure along the East Coast disrupted Northeast hubs on Monday, Sept. 21, 2026, and rippled through flight schedules nationwide.

What happened on the East Coast and why it mattered to MSP

Published coverage described the disruption as a communications breakdown linked to the Federal Aviation Administration’s Philadelphia-area air traffic control facility that handles a heavy volume of Northeast traffic, including flows into the New York metro airspace. The outage triggered ground stops and restrictions that slowed departures and arrivals at some of the busiest airports in the country, especially those connected to Newark, Philadelphia, and New York City-area operations.

Reports described a failure of the primary communications line and a separate problem affecting a backup fiber route, tied to construction activity near a rail corridor in New Jersey. With traffic management programs in place to keep aircraft separated and safely sequenced, carriers across the U.S. began holding aircraft at origin airports rather than sending flights into congested airspace.

Even though MSP sits far from the Northeast corridor, it depends on tightly timed aircraft rotations and connecting itineraries to and from East Coast hubs. When aircraft and crews are delayed or out of position in New York, New Jersey, and Pennsylvania, downstream routes to the Upper Midwest can be delayed for hours, especially late-day flights when recovery options narrow.

How the disruption showed up at Minneapolis-St. Paul International Airport

At MSP, the effect was visible as delayed departures, delayed arrivals, and missed connections accumulating through the afternoon and evening, according to regional reporting and airline status pages. Travelers scheduled on flights bound for East Coast destinations or connecting through those airports were among the most likely to see gate holds, late inbound aircraft, and schedule changes.

The FAA’s airport status information for MSP did not consistently list a single, airport-wide delay program tied to local conditions, highlighting that the problems were largely network-driven rather than caused by weather or a local equipment issue in Minnesota. That pattern is typical when disruptions originate at major hubs: the airport itself can appear operational while individual flights run late due to aircraft, crew, or airspace constraints elsewhere.

MSP is also a major connecting point, so delays can snowball in both directions. A late inbound from the East Coast can delay an onward flight to the West, while a late inbound from the West can miss its scheduled turn back to an East Coast hub, compounding disruptions for passengers who never set foot in the Northeast.

Airline waivers and what passengers can do right now

Airlines issued travel advisories and change-fee waivers tied to the Northeast air traffic control equipment outage, including policies covering travel on Sept. 21 and Sept. 22, 2026. These waivers typically allow eligible travelers to rebook without a change fee within a defined window, although fare differences may still apply depending on the replacement itinerary and cabin.

For passengers departing MSP, the most useful immediate step is to verify whether a delay is tied to an inbound aircraft or an airspace program affecting the destination airport. That distinction matters because an inbound-aircraft delay may worsen if the arriving flight is also held elsewhere, while a destination airspace restriction can sometimes ease quickly once capacity returns.

Travelers who no longer need to travel on the original day should compare rebooking options against the airline’s waiver terms, especially for itineraries involving connections through New York City-area airports, Philadelphia, or Newark. Checking the flight’s current aircraft assignment and earlier routing can also provide clues about whether a later departure is realistic or likely to slip further.

Passengers already at MSP are often better served by watching for rolling gate and departure-time updates rather than relying on the first posted delay. During system-wide disruptions, departure times can move repeatedly as airlines juggle crews, gate availability, and arrival slots into constrained airspace.

What to watch next as airlines try to recover schedules

Published coverage indicated repairs were completed and airport operations in the Northeast began resuming, but widespread disruptions often persist into the following day. Aircraft and crews can end up scattered across the system, and airlines may need to cancel select flights to reset rotations, even after the original technical issue is resolved.

MSP travelers should expect the highest risk of knock-on delays on routes that depend heavily on Northeast connectivity: late-night departures, early-morning flights that rely on late inbound aircraft, and itineraries that include tight connections through congested hubs. Recovery can be uneven, with some flights operating close to schedule while others run hours late due to missing aircraft or crew legal-time limits.

For those traveling Tuesday, Sept. 22, real-time flight status and rebooking tools remain essential, since the network can take a full operating day to stabilize. Travelers with flexible plans may find better reliability by shifting to midday departures when aircraft positioning has had more time to normalize and replacement crews are more available.