Ground stop at MSP after air traffic control outage

Flights into and out of Minneapolis–St. Paul International Airport were halted for several hours on Thursday after a major radar and communications outage at the regional air traffic control center triggered a ground stop across a wide swath of the Upper Midwest.

Outage at Minneapolis air traffic control center triggers halt

Publicly available aviation data and passenger accounts indicate that operations at Minneapolis–St. Paul International Airport (MSP) slowed to a near standstill on Thursday afternoon as air traffic controllers lost access to key radar and communication systems. The disruption affected the Minneapolis Air Route Traffic Control Center, commonly referred to by its identifier ZMP, which manages high-altitude traffic over large portions of Minnesota, the Dakotas, Iowa, Wisconsin and neighboring states.

Reports from flight-tracking platforms showed a sudden clearing of traffic over Minnesota and adjacent airspace during the outage period, with very few commercial aircraft visible at cruising altitudes normally dominated by transcontinental routes. Airline passengers posting on social platforms described boarding aircraft only to be held at the gate, or in some cases diverted midflight, after the ground stop took effect.

Information shared from the Federal Aviation Administration’s traffic management system indicated that an equipment problem at the center prompted strict flow controls and ground stops for flights entering the affected airspace. Aviation-focused discussion forums citing those FAA notices described the facility as operating in an “ATC zero” state for a time, meaning controllers were unable to safely manage instrument flight traffic through their sector.

Although some limited local operations continued, the combination of halted departures, suspended overflights and diversions produced a noticeable gap in regional flight activity that stretched beyond the immediate Minneapolis area. Observers compared real-time radar images before and during the disruption to illustrate the extent of the traffic void.

Telecommunications issues and wider internet outage cited

According to regional news coverage and aviation community summaries, the outage at the Minneapolis air traffic control center was linked to a broader telecommunications failure affecting parts of the Twin Cities on Thursday afternoon. Residents and businesses in the Minneapolis–St. Paul area reported losing internet connectivity around the same time that controllers reported radar and communication problems.

Descriptions compiled from FAA status messages and local reporting pointed to “equipment” and “telecommunication” issues as the underlying cause of the control center’s difficulties. While detailed technical explanations had not been publicly released by late Thursday, accounts from aviation personnel suggested that redundant systems were initially impaired, forcing controllers to curtail operations until stable communications and surveillance could be restored.

Commentary from pilots and dispatchers emphasized that modern en route centers rely heavily on robust data and voice networks to coordinate with aircraft and neighboring facilities. When those networks become unreliable, traffic managers typically respond by limiting or stopping departures bound for the affected airspace in order to avoid airborne holding patterns and potential safety concerns.

The reported connection between the control center outage and a larger regional connectivity problem underscored the dependence of air traffic infrastructure on external telecommunications providers. Some industry observers noted that the simultaneous impact on early voting systems, consumer broadband and aviation services illustrated how a single point of failure can ripple across multiple critical sectors.

Ground stop lifted but delays ripple through evening

FAA planning messages summarized in aviation forums indicate that the initial traffic management restrictions were imposed in the early afternoon, with the most severe measures in effect for roughly two hours. By mid to late afternoon, publicly accessible tracking data showed flights gradually climbing back into high-altitude airspace over Minnesota as portions of the system returned to service.

Updates circulating among passengers and airline employees suggested that the formal ground stop for many routes into MSP was lifted by around 4 p.m. local time, once controllers had regained sufficient capability to safely handle additional arrivals and overflights. Even after that point, however, travelers continued to experience significant knock-on delays as airlines worked through a backlog of disrupted flights.

Departure boards at MSP and at connecting airports across the Midwest reflected extended waits and re-timed flights for much of the evening. Some aircraft that had been held at outstations eventually departed with hours-long delays, while others returned to gates for refueling or crew changes after prolonged holds.

Travelers transiting the hub reported missed connections and rebookings, particularly for late-afternoon and evening departures that rely on feed from earlier waves of inbound flights. Airline operations teams faced the added challenge of repositioning aircraft and crews that had been diverted around the affected airspace during the outage.

Impact extends beyond Minneapolis hub

Because the Minneapolis Air Route Traffic Control Center oversees a broad region, the outage affected flights that never intended to land at MSP. Published airspace maps show that the center controls approximately 330,000 square miles of airspace stretching across portions of multiple Midwestern and Great Plains states, serving as a key corridor for both domestic and transborder routes.

During the disruption, some flights crossing the Upper Midwest were rerouted around the affected sectors, lengthening travel times and adding to congestion in neighboring centers. Others were delayed at their departure points far from Minnesota as traffic managers worked to prevent excessive demand from building up at the edge of the constrained airspace.

Passengers on certain long-haul and transcontinental flights described unscheduled holding patterns or diversions as crews waited for clearance to enter the Minneapolis-controlled region. Airlines with major connecting operations at MSP, particularly those using the airport as a primary hub, appeared to be among the most heavily affected, but smaller carriers and regional routes also reported schedule disruptions.

Smaller airports within the Minneapolis center’s jurisdiction, including regional facilities in surrounding states, experienced their own slowdowns as flights destined for MSP or passing through the area were paused. For some communities with limited daily service, a single delayed or canceled flight represented a substantial share of available capacity.

Questions over resilience and future safeguards

The outage and resulting ground stop quickly prompted discussion among aviation observers about the resilience of critical air traffic infrastructure. Commentators pointed out that while weather-related ground stops are relatively common, large-scale interruptions tied to equipment or telecommunications issues raise different concerns about redundancy and contingency planning.

Industry analysts noted that the National Airspace System incorporates multiple layers of backup procedures intended to keep aircraft safe when individual systems fail. Thursday’s events highlighted how those safeguards can still require drastic reductions in capacity when a key facility such as an en route center temporarily loses core capabilities.

Some discussions in professional aviation circles suggested that the episode may prompt renewed scrutiny of how air traffic control networks are interconnected with commercial telecommunications providers and large data centers. Observers argued that understanding any shared points of vulnerability will be important for limiting the impact of future outages.

For travelers, the incident served as a reminder that even on clear-weather days, disruptions unrelated to storms can abruptly alter flight plans across a wide region. As of late Thursday, publicly available information indicated that operations at MSP and in the surrounding airspace had largely normalized, but residual delays and repositioning flights were expected to continue into the night as airlines worked to restore regular schedules.