Key Points
- The Federal Aviation Administration ordered a nationwide ground stop on November 13, 2026, after communications problems affected air-route traffic-control centres.
- Minneapolis-St Paul International Airport and airports across the Midwest were affected.
- The ground stop lasted about four hours and was lifted at roughly 7:15–7:30 p.m.
- Flight disruptions at Minneapolis-St Paul International Airport included hundreds of delays and cancellations.
- Federal officials later attributed the outage to overloaded network equipment and instability linked to a communications-system update.
Minneapolis (Midwest News) November 13, 2026 – Flights were grounded across the Midwest after the Federal Aviation Administration halted departures nationwide because a temporary communications outage disrupted air-traffic-control operations. The order affected Minneapolis-St Paul International Airport and other major airports, while officials said the measure was taken for safety and that aircraft already in the air remained accounted for.
- Key Points
- Why were flights grounded across the Midwest?
- How long did the Federal Aviation Administration ground stop last?
- What caused the air-traffic-control communications outage?
- What happened after flights resumed?
- What is the background to the Minnesota air-traffic-control outage?
- How could the outage affect flights grounded throughout the Midwest?
Why were flights grounded across the Midwest?
As reported by Bring Me The News, the Federal Aviation Administration imposed the ground stop at about 3 p.m., citing “extraordinary circumstances and for reasons of safety”. Transportation Secretary Sean Duffy said a communications issue affected air-route traffic-control centres, while Federal Aviation Administration technicians investigated the fault.
Patch reported that the Federal Aviation Administration’s advisory was issued at 2:54 p.m. and applied to departing flights nationwide. The Minneapolis Air Route Traffic Control Center in Farmington, Minnesota, which manages en-route traffic over Minnesota and much of the Upper Midwest, was among the facilities affected. International flights travelling to the United States were handled case by case.
How long did the Federal Aviation Administration ground stop last?
The Federal Aviation Administration lifted the nationwide ground stop at approximately 7:15–7:30 p.m., according to reports from Bring Me The News, CBS News Minnesota and the Associated Press. Departures were then allowed to resume, although airlines faced continuing disruption as aircraft, crews and passengers were repositioned.
Minnesota Public Radio News reported that about 170 scheduled departures at Minneapolis-St Paul International Airport were affected. Flight-tracking data cited by several outlets showed hundreds of delays and cancellations at the airport, while disruptions across the country reached thousands of flights.
What caused the air-traffic-control communications outage?
CBS News Minnesota reported that an update to the private communications network linking the United States air-traffic-control system caused a reboot, followed by a communications outage. The Star Tribune later reported that a surge of data, including about 1,000 connection attempts every four to five seconds, overloaded switches and routers and disrupted aircraft communications and radar feeds.
The Star Tribune reported that L3Harris blocked two locations, after which the network stabilised and flights began resuming. Officials described the action as precautionary and did not report a loss of accountability for aircraft in flight.
What happened after flights resumed?
Minneapolis-St Paul International Airport advised passengers to contact their airlines and check the latest flight information. The Associated Press reported that hundreds of flights were diverted during the stoppage, while CBS News Minnesota said the Federal Aviation Administration planned to move as many flights as possible later that evening subject to crew availability.
What is the background to the Minnesota air-traffic-control outage?
The Minneapolis Air Route Traffic Control Center in Farmington directs aircraft travelling over Minnesota and much of the Upper Midwest. The incident affected more than the local facility because the communications problem extended across the national network of regional air-route traffic-control centres. The Federal Aviation Administration used a nationwide ground stop rather than permitting normal departures while communications and radar links were unstable. Flights at Minneapolis-St Paul International Airport were largely operating on time by the following Monday, although the disruption caused a weekend backlog.
How could the outage affect flights grounded throughout the Midwest?
Passengers travelling through Midwest hubs could face delayed departures, missed connections, aircraft substitutions and cancelled services even after the ground stop was lifted. Airports such as Minneapolis-St Paul International, Chicago O’Hare and Chicago Midway were particularly relevant to regional travellers because they connect local flights with national and international routes. Airlines’ ability to restore schedules depended on available aircraft and crews, meaning some effects could continue beyond the technical repair. Travellers were advised to verify flight status directly with their airline before going to the airport.
