FlightAware counted 15,897 cancellations of flights within, into or out of the United States on Friday 13 and Saturday 14 November, by our arithmetic from its daily totals: 9,201 on Friday, the day of the FAA’s nationwide ground stop, and 6,696 on Saturday. Thursday’s count was 1,026, so Friday ran about 9 times the day before, by our arithmetic.
The stop lasted 4 hours 14 minutes, or 254 minutes, by our arithmetic. Over Friday and Saturday that is about 63 US cancellations for each minute of the stop, by our arithmetic. FlightAware counts cancellations from every cause, so not every one traces back to the ground stop.
Business Pill · Embedded Dependency
A short explainer on embedded dependency: what sits inside the systems you buy. It teaches the general idea only and does not discuss the FAA or the ground stop.
The key insight: As we read it, the number that matters is the ratio of stop to toll: by our arithmetic, 254 minutes of ground stop sat alongside 15,897 US cancellations over two days, about 63 for each minute, though FlightAware counts every cause.
Update, 15 November 2026, 17:30 UTC: DHS says the outages are not connected. Homeland Security Secretary Mullin told Fox News that the FAA failure and the Microsoft outage were unrelated: “They are not connected whatsoever.” On Microsoft, Mullin said: “The Microsoft, we knew that almost immediately”. On the aviation fault: “You have a 50-year-old system that just failed”, and “It’s just the first time it’s failed nationwide”.
Mullin said “we need the money from Congress” and that the aim is “to build a full, brand-new system on top of the old system and then be able to take the old system totally offline”. Fox summarised that Mullin says DHS has found no connection between the two incidents and that the government needs to stop funding piecemeal fixes. The quotes are our transcription of the 2-minute clip Fox posted at 16:44 UTC.
As we read it, Mullin’s case for a full replacement sits beside Administrator Bedford’s statement, quoted below, that the FAA spends a billion dollars a year maintaining and sustaining the existing network. Mullin did not name a cause for Friday’s fault beyond the system’s age, so the Department’s account that the fault is not determined stands. The three-outage timeline is in our 46-hour piece.
What it shows: the Fox News clip (posted 16:44 UTC, 15 November, about 2 minutes) in which the DHS Secretary answers a Fox correspondent’s question on whether the FAA failure and the Microsoft outage could be connected. It is the primary for the quotes in the box above.
The Count, Day by Day
FlightAware’s cancellation statistics pages, read at 16:24 UTC on Sunday, list “Total cancellations within, into, or out of the United States” of 1,026 for Thursday, 9,201 for Friday and 6,696 for Saturday. Sunday’s partial count stood at 1,622, which takes the three days to 17,519, by our arithmetic.
Above Thursday’s level, Friday and Saturday carried 13,845 extra US cancellations between them, by our arithmetic, using Thursday as a rough baseline. Saturday ran about 6.5 times Thursday. On Friday, US flights made up about 93% of the 9,938 cancellations FlightAware counted worldwide, by our arithmetic. Delays within, into or out of the US were 7,468 on Friday and 9,132 on Saturday, per FlightAware.
Reuters put the wider toll at a shutdown “that has disrupted more than 20,000 flights since Friday”, in its report on Saturday.

What the Department Says Happened
The Department of Transportation’s release of 14 November says “Telecommunications issues that impacted the stability of communications and radar systems utilized by Air Traffic Control led the FAA to issue a nationwide ground stop out of an abundance of caution”. It says controllers and pilots were responsible for “grounding over 3,500 flights swiftly”, and that “over 8,000 flight operations resumed last night alone” once the stop lifted.
Transportation Secretary Sean Duffy said at the briefing: “In at least one of our remote FAA locations, a contractor was doing routine maintenance to switch telecommunication lines from old copper wire and they were bringing it over to fiber”. Duffy named the contractor as L3Harris and said “the network that we use at the FAA to control the airspace, L3Harris actually owns that network”.
On the mechanism, Duffy said the router “started flooding other routers in our air traffic control system” and that “we had over 1,000 connection attempts every four to five seconds”. Reuters reported that the issue “began overloading communications at 17 of the FAA’s 22 en route centers across the country”. Asked about a cyber attack, Duffy said: “We don’t believe so”.
The Network Underneath
FAA Administrator Bryan Bedford separated the fault from the modernization programme: “We spend a billion dollars a year maintaining and sustaining the existing 1980’s TDMI telco network”, and “we are constantly replacing 2,000 Cisco 600 routers with Juniper routers”. Bedford said this work “is not part of the Peraton-FAA $12.5 billion modernization effort”.
Duffy listed progress on that programme, including “we have replaced 69% of the copper communications”. On timing, Duffy said work at remote sites is done during the day and that “there’ll be a reevaluation of when we do this work”.
The Structural Read
As we read the Department’s account, the stop began in the network layer rather than in the aircraft or the controllers: a router swap at one remote site flooded other routers, and Reuters reported 17 of 22 en route centers were affected.
As we read the counts, Saturday’s 6,696 cancellations, about 6.5 times Thursday by our arithmetic, came after the airspace had reopened, so most of the second day’s toll is recovery rather than the stop itself.
Transportation Secretary Sean Duffy, DOT release, 14 November 2026
“the network that we use at the FAA to control the airspace, L3Harris actually owns that network”
Three Implications
FOR TRAVELLERS AND AIRLINES FlightAware still listed 1,622 US cancellations for Sunday at 16:24 UTC, a partial-day count.
FOR CONTRACT OWNERS Duffy named L3Harris as the contractor that owns the network; the fault is not determined, and L3Harris said it is supporting the FAA investigation, Reuters reported.
FOR OPERATIONS TEAMS Duffy said there will be a reevaluation of when such switchover work is done; Bedford said the FAA spends a billion dollars a year sustaining the existing network.
The Business Engineer Lens
This story maps onto the Business Engineer framework Enterprise AI: From Software to Substrate.
The framework says: “The value proposition shifts from features to integration depth.”
As we read it, the ground stop showed that depth from the other side: air traffic in the whole country stopped when one router in a contractor-owned network failed, per the Department’s account. The framework predates the stop and does not discuss it.
What Is Not Established
The fault itself is not determined. Duffy said: “We haven’t determined what the fault was”, and framed the open question as “contractor error or a faulty piece of equipment”. L3Harris said it was “supporting the FAA in its investigation to understand the conditions that led to the Nov. 13 ground stop of our nation’s air travel”, Reuters reported. FlightAware’s totals cover all causes, including weather and the usual daily cancellations, and its day boundaries are its own. We did not contact the FAA, L3Harris or FlightAware for this piece.
The Bottom Line
FlightAware’s daily totals show 15,897 US flight cancellations across Friday and Saturday, about 9 times Thursday’s count on Friday alone, by our arithmetic. The Department of Transportation ties the ground stop to a router swap during copper-to-fiber work at one remote site; the fault is not yet determined. The stop was one of three outages we counted in 3 Outages, 46 Hours in Two Days, alongside Microsoft 365 and Workday. We first covered the stop in FAA Ground Stop: Officials to Check Link to $875M AI Tool.
95,000+ executives read Business Engineer for the AI strategy frameworks cited by ChatGPT, Claude, and Perplexity.
A note on sourcing. Cancellation and delay counts are FlightAware’s daily totals for flights within, into or out of the United States, read at 16:24 UTC on 15 November; they count all causes. The cause, scope and network figures come from the US Department of Transportation’s release of 14 November quoting Secretary Duffy and Administrator Bedford; the en route centre count, the 20,000-flight figure and L3Harris’s statement are as reported by Reuters.
The stop’s 254 minutes run from the first reports at 21:01 UTC to Duffy’s 8:15 p.m. EST reopening. Totals, multiples and rates are our arithmetic. We did not contact the FAA, L3Harris or FlightAware.
Sources: US Department of Transportation release, 14 Nov 2026 · FlightAware cancellation statistics, read 15 Nov 2026 16:24 UTC · FAA statement, 13 Nov 2026 · NBC News live blog, 13 Nov 2026









