On the afternoon of Friday, November 13, 2026, the Federal Aviation Administration issued a nationwide ground stop, citing "extraordinary circumstances and for reasons of safety." Departing flights were held at airports across the country; Chicago was affected first, with Minneapolis-St. Paul also confirmed affected; international flights were handled case by case. The underlying issue, per reporting at the time, involved communications problems affecting multiple Air Route Traffic Control Centers. Transportation Secretary Sean Duffy confirmed that FAA technicians were investigating. As of this writing, it has not been established whether the cause was an internal technical failure or something external — and we are not asserting either.
What is established is the rarity of the event itself. A full nationwide ground stop has happened only twice in recent memory before Friday: in January 2023, after a failure in the system that distributes safety notices to pilots, and before that, only in the hours after the September 11 attacks. Whatever caused Friday's stoppage, the FAA judged it serious enough to halt departures everywhere in the country at once — a decision that is not made lightly and is not made often.
That same week, a separate and unrelated event — the Microsoft 365 outage that began Wednesday — disrupted email, Teams and related services nationwide for more than a day. We've written about what that means for digital continuity in a companion piece. We have seen nothing connecting the two events, and we are not suggesting a link. They are two serious, independent disruptions in the same week — each one worth taking seriously on its own terms, and each one a live test of a contingency plan most people have never actually run.
Why a ground stop is a different problem than a delay
Executives and traveling families deal with flight delays constantly, and most programs already have a standard response: hold, rebook, adjust ground transportation at the other end. A nationwide ground stop is a different category of event. It is not one flight or one airport — it is every departing flight in the country, at once, for an unknown duration, for a reason that is not yet public. The practical effects compound quickly:
- Every traveler in the system is affected simultaneously, which means rebooking options that would normally absorb a delay — an alternate flight, a different airport, a different carrier — are themselves overwhelmed.
- Ground transportation plans built around a specific arrival window stop working. A security driver staged for a 6:00 PM pickup has no way to know whether the actual arrival is three hours late or the next morning.
- International connections are handled case by case, which means a principal mid-itinerary on a multi-leg trip may be stranded at a connection point with no clear guidance on when movement resumes.
- Private aviation is not automatically exempt. FBOs and private terminals operate within the same national airspace system; a ground stop of this kind affects scheduling and slot availability even for travelers who are not flying commercial.
What a sound travel contingency plan covers
None of this is new in principle — it is the same logic that governs any protective travel plan, applied to a scenario most people assume won't happen to them.
A real alternate, not a theoretical one. "We'll rebook if something happens" is not a plan unless someone has actually identified what the alternate routing, alternate airport or ground-transport option would be before the day it's needed.
A ground-transportation plan that isn't tied to a single arrival time. The driver, the detail lead and the principal's office should have a standing protocol for what happens when an arrival window becomes unknown — including who is actively tracking flight status and who makes the call to stand down or extend coverage.
Direct lines that don't depend on airline apps or hold lines. During a disruption of this scale, airline call centers and apps are the least reliable source of real-time information. A protective program should have its own channel for tracking a principal's status — the detail lead confirming directly with the principal or gate staff, not waiting on hold.
A plan for the stranded leg, not just the missed one. If a principal is mid-itinerary when a disruption hits, the plan needs to cover where they wait, how they're kept secure and informed at an unfamiliar airport or FBO, and how the next leg gets re-planned once service resumes.
Decision authority, decided in advance. Someone needs to be pre-authorized to make real-time calls — extend a driver's wait, book a hotel near the airport, adjust the next day's schedule — without waiting for a round of approvals that can't happen quickly enough during an active disruption.
What we are telling our own clients this week
Regardless of what the FAA's investigation ultimately finds, Friday's ground stop is a useful, low-cost prompt to pressure-test travel contingency plans before the next disruption, rather than during one. We are recommending three steps:
- Confirm who is tracking flight status in real time for any principal traveling this week, and that it is not left to the traveler's own phone and patience.
- Walk through the ground-transportation plan for an unknown arrival time, not just a delayed one.
- Identify, in writing, who is authorized to make contingency decisions — lodging, rebooking, extended coverage — without waiting for sign-off that can't arrive fast enough.
A nationwide ground stop is rare. That is exactly why most programs have never been tested against one — and exactly why this week is worth using to find the gaps before travel resumes as normal.
Frequently Asked Questions
Was the FAA ground stop caused by a cyberattack?
That has not been confirmed. Reporting at the time pointed to communications issues affecting multiple air traffic control centers, and officials said the cause was under investigation. We are not asserting a cyberattack occurred, and we are not ruling one out — the honest answer, as of this writing, is that it is not yet known.
How often does a nationwide ground stop happen?
Rarely. Friday's stoppage was only the second full nationwide ground stop since the September 11 attacks, with the only other one occurring in January 2023 after a system failure affecting pilot safety notices.
Is this connected to the Microsoft 365 outage earlier the same week?
We have seen no source connecting the two events. Treat them as separate disruptions that happened to occur in the same week.
Does a ground stop affect private aviation the same way it affects commercial flights?
Private aircraft operate within the same national airspace system, so scheduling and slot availability can still be affected even when private travel is not the direct focus of a ground stop. Confirming status directly with the FBO, rather than assuming private travel is exempt, is the safer approach.
Request a Private Consultation
If this week's ground stop exposed a gap in how your travel plan handles an unknown-duration disruption, that is worth addressing before your next trip rather than during it.
Request a Private Consultation · (281) 799-1877 · scott@amerineexecutivelogistics.com
Related Reading
AMERINE Executive Logistics is licensed by the Texas Department of Public Safety, License No. C31012001. This article reflects publicly reported information available as of November 14, 2026, and will be updated if investigators publish further findings.
