Ground stop at MSP after air traffic control outage

A ground stop affecting flights at Minneapolis–St. Paul International Airport on Thursday afternoon followed an apparent outage at the Minneapolis Air Route Traffic Control Center, briefly halting large portions of commercial traffic across the Upper Midwest and forcing diversions, delays, and cancellations throughout the region.

Outage at Minneapolis Center Triggers Sudden Ground Stop

Publicly available flight-tracking data and aviation community reports indicate that the disruption began early Thursday afternoon, August 6, when Minneapolis Center, the Federal Aviation Administration facility responsible for high-altitude traffic over a broad swath of the Upper Midwest, experienced a loss of radar and communications services. The facility, known by its identifier ZMP, manages traffic across roughly 330,000 square miles, including Minnesota, the Dakotas, Iowa, Wisconsin and parts of several neighboring states.

Within minutes of the outage, the National Airspace System showed a pronounced gap in high-altitude traffic over Minnesota and surrounding states, with commercial jets diverted around the affected region or held on the ground at departure airports. Aviation enthusiasts monitoring radar feeds shared images of the “void” in traffic, noting that it was unusual for such a busy corridor to appear effectively empty of scheduled airline flights.

Reports from passengers and airline staff describe aircraft already en route being placed into holding patterns or diverted, while departures bound for Minneapolis–St. Paul International Airport were instructed to remain at their origin until further notice. Online discussions referencing FAA traffic management notices pointed to a formal ground stop, a procedure in which specific categories of flights are required to stay on the ground until airspace capacity can safely be restored.

The ground stop at Minneapolis–St. Paul primarily affected flights arriving into or departing from the airport, but its impact extended well beyond the Twin Cities. Because Minneapolis Center oversees much of the en route traffic over the northern Plains and Upper Midwest, the outage disrupted long-haul connections, regional services, and flight routings that pass through the region even if they do not land at MSP.

Passengers Face Delays, Diversions and Extended Gate Holds

Accounts shared publicly by travelers suggest that the outage caught many flights in mid-operation. Some passengers reported boarding aircraft at airports across the country, only to receive delay notifications after being seated. In several cases, travelers described pilots relaying information about a sudden loss of radar capability in the Minneapolis-controlled airspace and the resulting instruction not to depart toward the region.

Other passengers reported flights that had already departed turning back to their origin or diverting to alternate airports to await further guidance. Flight-tracking services showed a number of aircraft holding at intermediate locations, including airports in the central United States, as crews and operations centers checked updated routing information and fuel requirements while the status of the Minneapolis airspace evolved.

At Minneapolis–St. Paul International itself, travelers described a period with few or no visible takeoffs and landings, followed by a gradual resumption of activity as services were restored. Some social media posts referenced aircraft that had pushed back from gates before being instructed to hold on taxiways, while others detailed returns to the gate to await revised departure times.

Airlines operating through MSP, including major hub carriers and regional affiliates, appeared to implement rolling delays as the ground stop and subsequent flow restrictions took effect. Some travelers reported misconnecting from international and cross-country flights as arrival banks were shifted and evening departure waves compressed into a smaller operating window once the airspace reopened.

What a Ground Stop Means for the National Airspace System

Ground stops are among the most visible tools used in the U.S. air traffic management system during significant operational disruptions. According to public FAA documentation, a ground stop is instituted when conditions such as severe weather, runway closures or equipment outages reduce an airport’s or airspace sector’s capacity to a level that cannot safely accommodate normal traffic flows. When in effect, qualifying flights are instructed to remain at their departure points rather than depart into constrained or uncontrolled airspace.

In the Minneapolis case, the issue appeared centered on communications and radar capabilities at the air route traffic control facility, a type of center responsible for sequencing and separating aircraft across wide regions between terminal areas. Observers within the aviation community noted that Minneapolis Center effectively reached what is described in industry terminology as “ATC Zero,” a status in which a facility is unable to provide its standard level of service and traffic must be rerouted or held out of the affected area.

When such an event occurs, neighboring control centers and local terminal facilities typically coordinate closely using national traffic management programs. These can include ground stops, ground delay programs and reroute advisories designed to meter flows into constrained airspace. Publicly available FAA guidance indicates that these programs are adjusted dynamically as capacity is restored, with rates increased gradually to avoid overwhelming controllers or creating new bottlenecks as operations ramp back up.

The Minneapolis outage also underscores how interdependent the National Airspace System has become. Even an event lasting a couple of hours at a single facility can cause a cascade of delays as aircraft, flight crews and airport resources fall out of their planned positions, an effect that can extend well into the evening as airlines work through backlogs of delayed departures and misaligned connections.

Regional Internet Problems and Data Center Issues Cited in Early Reports

While a detailed technical explanation had not been publicly released as of Friday, early accounts circulating among local technology and aviation observers linked the air traffic disruption to a broader regional network problem. Residents in the Twin Cities area reported widespread internet outages around the same time as the Minneapolis Center issue, and discussions referencing local infrastructure pointed to an incident affecting a large data facility serving multiple customers, including government operations.

Commentary from individuals familiar with local networking and infrastructure suggested that a power or connectivity loss at that site may have interrupted critical communications pathways used by the air traffic control system. Those accounts described a roughly one to two hour period of degraded or unavailable service, generally aligning with the window in which the ground stop and associated traffic management measures were in effect.

In the absence of a detailed post-incident report, it remains unclear exactly which systems failed and how redundancies performed during the outage. However, the sequence of connectivity problems, air traffic disruptions and subsequent restoration of both internet service and flight operations has fueled questions among travelers and aviation watchers about the resilience of critical infrastructure and the safeguards in place to isolate air traffic systems from commercial network failures.

Publicly available information from longstanding FAA materials indicates that U.S. air traffic facilities are designed with multiple layers of redundancy, including backup communications paths and procedures to maintain safety in the event of system failures. The Minneapolis episode is likely to draw attention to how those redundancies are implemented in practice and whether additional protections are needed as reliance on digital networks continues to grow.

Operational Recovery and Ongoing Impact on Travelers

By Thursday evening, aviation hobbyists monitoring Minneapolis-area radio frequencies reported that traffic routes into and out of the region were gradually reopening, with controllers resuming normal sector operations and aircraft flows increasing toward typical levels. Passenger accounts from Minneapolis–St. Paul International described a noticeable uptick in departures from both terminals as delayed flights were cleared to leave and inbound traffic resumed more standard arrival patterns.

Despite the relatively short duration of the underlying outage, the operational recovery extended well beyond the initial incident window. Airlines faced the challenge of repositioning aircraft and crew that had been held, diverted or delayed, while also managing duty-time limits for pilots and flight attendants affected by extended ground holds. In some cases, evening and late-night services were canceled outright when pairings could no longer be completed legally within crew scheduling constraints.

For travelers, the ripple effects included missed connections, unplanned overnight stays and rebookings onto later flights through Minneapolis or alternative hubs. Some passengers reported being offered hotel and meal assistance, while others navigated self-service rebooking tools or contacted customer service channels to rearrange itineraries. The incident arrived during the busy summer travel period, magnifying its effects on vacationers and business travelers alike.

Industry analysts watching the event noted that although the Minneapolis disruption was localized in time and geography compared with previous nationwide technology incidents, it demonstrated how dependent modern air travel is on continuous, high-reliability data and communications systems. The ground stop at MSP served as a reminder that even short-lived outages at key facilities can quickly reshape travel plans far beyond the immediate area, reinforcing the importance of robust contingency planning for airports, airlines and passengers across the network.