All flights in and out of MSP Airport were halted Thursday afternoon after the Federal Aviation Administration issued a ground stop tied to apparent air traffic control system issues. The stop went into effect around 2 p.m. and was later extended to 4:15 p.m.
That is the kind of operational break that ripples through an airport fast. A ground stop means flights are held on the ground instead of being allowed to depart, and when it covers both directions at once, it freezes the schedule rather than slowing it.
The timing made the disruption especially sharp for anyone watching MSP Airport on Thursday. With the stop beginning around 2 p.m., the halt arrived in the middle of the afternoon and immediately put every flight in and out of Minneapolis-St. Paul International Airport on hold.
The FAA described the problem only as apparent air traffic control system issues, which leaves a gap between the language used and the scale of the disruption. “Apparent” suggests the agency had identified a problem affecting operations but had not spelled out the exact fault, even as the airport-wide stop showed the impact was already real.
The extension to 4:15 p.m. pointed to a disruption that was lasting longer than an initial pause. The source does not say what happened after that extension, but the key fact for travelers and airlines Thursday was that MSP Airport was not moving traffic normally while the stop was in place. For now, the unanswered question is the most practical one: what specific system issue forced the halt, and how long did the airport remain under it after 4:15 p.m.?
