Prime Rogue Media seal
Prime Rogue Media · Analysis

The stop began before the order

FAA records show Chicago communications trouble 44 minutes before the nationwide ground stop; our flight count and Ottawa's operations centre both put the halt before the written order

By , Prime Rogue Media · Published
← Back to live coverage: US ground stop, what it means for Canada

The official account of Friday's US aviation shutdown has a tidy shape: instability began at 3:36 p.m. Eastern, the FAA ordered every US airport to stop departures at 3:54 p.m., and the order was lifted at 8:19 p.m.

The FAA's own advisory record, and two records from the Canadian side, our own flight count and Ottawa's operations log, show the shutdown began earlier and in a messier way.

The Command Center's public advisory log shows a ground stop at Chicago O'Hare dated from 3:10 p.m. ET, for an "EQUIPMENT / OUTAGE" with the comment "COMMS ISSUES." That is 26 minutes before the time Transportation Secretary Sean Duffy gave for the start of the problem, and 44 minutes before the nationwide order. The O'Hare stop covered flights departing from Canadian airports, including Toronto, Montréal, Ottawa and Halifax.

Our count of flight-tracking data shows departures across the United States collapsing at 3:38 p.m., 16 minutes before the written nationwide order. And Canada's federal Government Operations Centre told us it was aware of the "US nationwide ground stop" at 3:45 p.m., nine minutes before the FAA issued it.

None of this shows anyone concealed anything. When an air traffic control centre loses communications, controllers stop releasing aircraft at once and put the paperwork in afterwards. What it does show is that the 3:54 p.m. time in most accounts dates the paperwork, not the stop.

What the FAA's record shows

The FAA's Air Traffic Control System Command Center publishes every advisory it issues on fly.faa.gov. On November 13 it issued 123. We read the ones issued between 3 and 6 p.m. ET.

Two things stand out. First, the stated reason for the national stop sharpened over two hours: from "extraordinary circumstances" and safety, to equipment outages, to communications failure. Second, the first equipment-related stops in the record are in Chicago, and they begin before 3:36 p.m.

The record does not say whether the Chicago trouble was the first stage of the national failure or a separate local fault that happened to come first. A ground stop's start time can also be entered after the fact. Advisory 107 was signed 18 minutes after the start time it gives. We have asked the FAA both questions.

Update, Nov. 16, 1:40 a.m. ET: the FAA's questions-and-answers page, dated Nov. 15, says the problem began at "approximately 3:30 p.m. ET" and points to a radar site in Amarillo, Texas, and a radio communications site in El Dorado, Arkansas. It does not mention Chicago. See the live update.

Line chart of US departures per minute from 3 to 4:30 p.m. ET on November 13, 2026, against a typical day. Departures track the typical day, about 30 a minute, until 3:37 p.m., then fall to 13 at 3:38 and near zero after. A shaded band marks 3:38 to 3:54 p.m., the 16 minutes before the FAA's written nationwide order. Numbered markers: 1, 3:10, O'Hare ground stop for 'COMMS ISSUES'; 2, 3:17, Midway ground stop; 3, 3:36, start of instability per Secretary Duffy; 4, 3:38, departures collapse; 5, 3:45, Canada's Government Operations Centre aware of the ground stop; 6, 3:54, FAA's written nationwide ground stop; 7, 4:20, nationwide airborne holding for equipment outages.
US departures fell from about 30 a minute to 5 at 3:38 p.m. ET, 16 minutes before the FAA's written nationwide order. The FAA's own advisories show Chicago ground stops for “COMMS ISSUES” from 3:10 p.m. Graphic: Prime Rogue Media. Flight data: adsb.lol, made available under the Open Database License (ODbL) 1.0; counted by Roger Wilco Imagery, part of Prime Rogue Inc.

What Canada's records show

Canada was a bystander to Friday's failure. But Canadian records turn out to be useful witnesses to it.

Our flight count. Roger Wilco Imagery, part of Prime Rogue Inc., counted departures from the 100 busiest US airports, minute by minute, in the adsb.lol flight-tracking archive. About 30 aircraft took off each minute until 3:37 p.m. ET. Then 13 took off at 3:38, five at 3:39, and between none and four a minute after that. On the comparison days, the same minutes averaged about 30. The near-total halt began 16 minutes before the written nationwide order. (The Chicago stops alone don't show up as a national drop: departures nationally carried on at near-normal rates until 3:37.)

Ottawa's operations log. Public Safety Canada told us its Government Operations Centre, which runs around the clock, "became aware of the US nationwide ground stop as of 15:45 EST." That is nine minutes before the FAA's nationwide advisory existed. Public Safety did not say how the centre found out. Either someone told federal partners about a national stop before the FAA put it in writing, or the centre logged the moment it first heard of the disruption under the name the event later got. Either would be worth knowing, and we have asked.

The centre kept its focus on the event until 8:35 p.m. Public Safety said "US partners have informed the federal government that the cause of the disruption was a technical failure." That is the US account as relayed to Ottawa, not a Canadian finding.

NAV CANADA's own ground stops. The FAA's advisory site also carries NAV CANADA's advisories. They show NAV CANADA holding flights bound for Toronto Pearson from 4:54 p.m. ET and for Montréal-Trudeau from 5:00 p.m. at their departure airports. These were ground stops on traffic into Canada's two busiest hubs. At first they covered departures from everywhere; revisions narrowed them to flights from the United States. NAV CANADA cancelled them at 6:03 p.m. (Montréal) and 6:05 p.m. (Pearson), so each lasted a little over an hour. The stated condition was "OTHER / OTHER," with no comment.

Earlier, at 4:21 p.m., NAV CANADA's National Operations Centre had called a special conference call with airspace users for 4:35 p.m. to discuss the FAA's operations and constraints.

That matters because of a disagreement over words. On Friday, Porter Airlines attributed its system-wide cancellations to "a U.S. FAA outage & NAV Canada ground stops." NAV CANADA told us its measures at major Canadian airports were "precautionary" traffic management measures and did not use the words "ground stop." On Saturday Porter told us: "NAV Canada issued a ground stop at select airports for a very short period." NAV CANADA's own advisories back Porter. A ground stop is one kind of traffic management measure, so NAV CANADA's description wasn't false. But it described the measures in the most general terms available. No Calgary or Vancouver ground stop appears in the advisory list, though NAV CANADA said it had measures at both. NAV CANADA's routine 3:06 p.m. outlook, issued before the first Chicago trouble in the FAA's record, had already planned reduced arrival rates at Vancouver from 4:45 p.m. and at Calgary from 6 p.m. We have asked whether those are the measures it meant.

NAV CANADA has not yet answered our question about this.

Update, Nov. 15, 6:55 a.m. ET: flight-by-flight data shows five flights from Ottawa and Toronto flew into US airspace during the stop and turned back, two of them dispatched after US departures had stopped. See Five flights from Canada turned back.

Timeline chart, 3 to 9 p.m. ET, November 13, 2026, with one bar per measure: US nationwide ground stop, 3:54 to 8:19 p.m.; O'Hare ground stop covering flights from Pearson, Montréal, Ottawa and Halifax, 3:10 to its scheduled end at 4:30 p.m.; Midway ground stop, 3:17 to 4:30 p.m.; Ottawa's Government Operations Centre focus, 3:45 to 8:35 p.m.; NAV CANADA ground stop on flights to Pearson, 4:54 to 6:05 p.m.; NAV CANADA ground stop on flights to Montréal, 5:00 to 6:03 p.m. A dotted line marks NAV CANADA's 4:35 p.m. conference call with airlines. A note says the time Canadian airports were told is unknown: Billy Bishop and Winnipeg say they heard 'through industry groups'.
What was stopped, and when, for flights touching Canada on Nov. 13. NAV CANADA held flights bound for Pearson from 4:54 to 6:05 p.m. and for Montréal from 5:00 to 6:03 p.m.; the FAA's Chicago stops held flights from four Canadian airports from 3:10 p.m. Graphic: Prime Rogue Media. Sources: FAA Command Center advisories; NAV CANADA advisories on fly.faa.gov; Public Safety Canada.

Who told Canadian airports?

This is the question we started with, and it is still open.

Billy Bishop Toronto City Airport and Winnipeg's airport both told us they were notified "through industry groups." The Canadian Airports Council said it and its US parent "sent an update to its members as events unfolded," and described airports' channels to NAV CANADA as "well-established and effective." It did not say when it sent the update.

Asked whether notifying airports is its job, Public Safety said: "No, this is not a responsibility of the GOC," and referred us to Transport Canada. Transport Canada had earlier referred us to NAV CANADA and to Public Safety. NAV CANADA referred questions about the ground stop to the FAA. So did NORAD and CISA.

There may be a simple explanation. The FAA and NAV CANADA formally notify aircraft operators, meaning airlines, because a ground stop applies to flights. Airports may sit outside the formal notice chain by design. But no Canadian agency has yet told us it notifies airports of a foreign ground stop. Meanwhile the FAA's records show flights from four Canadian airports being held for Chicago from 3:10 p.m.

What we've asked

We have put these questions, with a deadline of noon ET Monday, November 16:

We will update this story with their answers.

How we did this

Updates and corrections to this story will be noted here, with times.