More news on this day
Flights have resumed at Minneapolis–St. Paul International Airport after a ground stop linked to an air traffic control radar and communications issue, but published tracking data shows many travelers are still facing extended delays and disrupted connections across the U.S. network.
Get the latest news straight to your inbox!

Ground Stop Lifted After Radar and Telecom Glitch
According to publicly available flight tracking records and local broadcast coverage, a ground stop affecting Minneapolis–St. Paul International Airport began on Thursday, August 6, after a failure at Minneapolis air route traffic control center disrupted radar and radio communications across portions of the upper Midwest airspace. The outage led to an immediate halt of most commercial traffic into and out of MSP, with some flights already en route forced to hold or divert.
Social media posts and traveler accounts compiled over the past two days describe aircraft returning to gates, departures pushed back in short increments, and long waits onboard and in terminals. One flight from Chicago reportedly turned back over Iowa, while some long-haul services bound for Minneapolis were held at origin airports to avoid adding to airborne congestion.
The ground stop was gradually relaxed later in the afternoon after air traffic controllers regained enough capability to handle limited flows. Local television reports indicated that the formal ground stop order was extended several times before being lifted around late afternoon, allowing airlines to begin rebuilding operations out of Delta’s key hub.
By the evening of August 6, traffic flows into MSP had largely resumed, but schedules remained heavily distorted as aircraft and crews were out of position. Industry analysts note that even a relatively short ground stop at a major hub can take many hours, and in some cases days, to work through the system.
Travelers Face Rolling Delays Across the Network
Even with the ground stop lifted, flight status boards showed persistent disruption on Friday, August 7, particularly on routes connecting through Minneapolis and other Midwest hubs. Passengers reported missed connections, last-minute cancellations and rebookings onto evening or next-day departures as airlines tried to reassemble aircraft rotations.
Some travelers connecting from coastal airports described knock-on delays when their inbound aircraft originated from or passed through the affected airspace. Posts referencing major East Coast airports such as New York’s JFK indicated that departures bound for the Midwest were held for extended periods, compounding schedule pressure at already busy facilities.
Publicly available data from tracking services suggested that average delays for some MSP flights stretched to well over an hour at the height of the disruption, with individual services waiting significantly longer for departure slots or diversion recovery. For travelers, the irregular operations added to an already challenging summer marked by strong demand, convective storms and tight airline staffing.
Air travel observers note that when a central node like Minneapolis experiences an abrupt capacity reduction, the ripple effects can extend far beyond the immediate region. Flights that never touch MSP may still be affected if they rely on shared aircraft or crews that were scheduled to pass through the hub earlier in the day.
Old Infrastructure and Complex Airspace Under Scrutiny
The incident has renewed attention on the resilience of critical air traffic control infrastructure. Local news segments in Minnesota referenced experts who described some equipment in regional facilities as aging and overdue for modernization, even as traffic levels continue to recover and in some cases exceed pre-pandemic volumes.
The Minneapolis center oversees a large expanse of high-altitude airspace across several states, handling both cross-country overflights and flows in and out of major hubs such as MSP. When a technical failure affects such a facility, capacity can drop sharply, prompting ground stops, rerouting and distance-increasing detours for flights that would normally traverse the region at cruise altitude.
Recent federal planning documents have highlighted ongoing construction and procedural updates in and around Minneapolis–St. Paul International, including runway and taxiway work that can at times constrain available configurations. While these long-term projects are designed to enhance safety and efficiency, they also leave less margin when unexpected events such as a radar or telecommunications outage occur.
Aviation analysts point out that investment in digital backup systems, redundant communication links and modern surveillance technology is intended to reduce the likelihood and duration of such outages. However, implementing upgrades across a vast and complex national airspace system remains a long-running challenge that can take years to complete.
What Passengers Can Expect in the Coming Days
With the ground stop at MSP now over, airlines are focusing on clearing backlogs and repositioning aircraft and crews. Operations over the weekend of August 8 and 9 are expected to improve compared with Thursday’s disruption, but schedule data suggests that some scattered delays and equipment swaps will likely persist as carriers work to normalize rotations.
Travel experts recommend that passengers with upcoming connections through Minneapolis monitor their flight status frequently, as same-day changes remain more common in the immediate aftermath of a significant interruption. Longer minimum connection times may be advisable, especially for those linking from regional flights to long-haul or last departures of the day.
For travelers whose flights were canceled or heavily delayed, airlines are applying standard irregular-operations policies, which can include rebooking at no additional fare, limited hotel assistance where required, or credits for future travel in some cases. Consumer advocates emphasize the importance of reviewing each carrier’s contract of carriage and keeping documentation of disruption-related expenses.
While Thursday’s outage appears to have been localized and relatively short-lived compared with nationwide events triggered by weather or systemwide technical failures, it has added another layer of strain to an already busy peak travel season. Those planning to fly through Minneapolis in the near term are being urged, through publicly available advisories and travel alerts, to build in extra time and stay flexible as airlines continue to stabilize their schedules.
Broader Questions About Summer Reliability
The MSP episode comes amid a series of weather and infrastructure-related interruptions affecting U.S. aviation this summer, raising broader questions about network resilience under high demand. Thunderstorms around major coastal hubs, construction-related capacity limits and staffing constraints in some air traffic control facilities have all contributed to elevated delay statistics.
Industry data reviewed by transportation researchers shows that delays can propagate quickly when one major hub experiences a capacity shock, as aircraft and crews cascade through interconnected route structures. A single afternoon of restricted operations at a large airport can generate missed connections and out-of-position aircraft that linger in the system for several days.
For Minneapolis–St. Paul, the latest ground stop underscores its importance within that network. As a key connecting point for domestic and international traffic, any significant constraint on MSP’s throughput can be felt by travelers far beyond the Twin Cities. Observers expect that the incident will feature in ongoing discussions about funding priorities for air traffic technology upgrades and operational contingencies at major hubs.
For now, with flights once again arriving and departing, attention is focused on restoring confidence among passengers who experienced the disruption firsthand. As schedules gradually recover, the episode is likely to fuel calls for continued investment in the systems that keep high-volume airports like MSP moving, even when unexpected technical problems arise.