This is the full research file behind the action guide. It is written for reporters, congressional staff and anyone who wants every finding, its limits and its source.
Case file 001 — The Nov 13, 2026 ground stop: fixing how the public gets told
Public edition · Nov 16, 2026 · Fix drafted (v0.1)
Starting point: CNN (Brian Stelter, Nov 14), “'No answer': Messaging failures worsened the air traffic freeze and sowed distrust in government”
Read this first. Everything here comes from public reporting, official releases and federal records gathered three days after the event. The root cause is still under investigation and details will move. Items resting on one person's account are marked.
Who wrote this. A private citizen, with research and drafting help from Claude, an AI assistant made by Anthropic. It is not connected to the FAA, any airline, any political party or any campaign. Every claim names its source so that it can be checked.
1. Why this problem and not the bigger one
Two things failed on Nov 13. The equipment failure, in a telecom network of 1980s design, is a multi-year job costing tens of billions, and it already has the attention of the White House and Congress. The communication failure is small, cheap and has no owner: officials had facts and no dependable way to get them to people in terminals and on aircraft.
By the Transportation Secretary's own estimate, a new network funded today would be ready in late 2028 or early 2029, and he has said to expect more outages until then. So the communication plan is the only piece that can be in place before the next one.
2. What happened
- 3:36 p.m. ET — radar and radio links at en route centers and approach facilities turn unstable (DOT).
- 3:54 p.m. — departures stopped at every U.S. airport (ABC timeline; the FAA administrator has also said 3:45). About 3,500 aircraft were airborne. All landed safely.
- 8:15 p.m. — stop lifted, 4 hours 21 minutes after it began.
- Seventeen of the FAA's 22 en route centers saw the instability (FAA Q&A).
- Official account so far (FAA Q&A, DOT, Newsweek): L3Harris, the contractor that owns and operates the FAA's telecom network, installed a new router at a radio site in El Dorado, Arkansas, during routine copper-to-fiber conversion. That router, and one installed about three weeks earlier at a radar site in Amarillo, Texas, flooded the older network with roughly 1,000 connection attempts every four to five seconds. Blocking both sites stabilized the network, and a broadcast function was then switched off on about 60 similar routers. Whether the fault was hardware, installation or a bad interaction with old equipment is not yet determined.
- Officials report no evidence of a cyberattack and no connection to the FAA's new SMART planning tool or to that week's Microsoft outage.
- Friday cancellations: about 12,500 by the FAA's count, which notes that not all were caused by the stop; 9,159 by FlightAware's count (CBS).
3. What the public was told, and when (Friday, Eastern time)
| Time | What reached the public | Source |
|---|---|---|
| 3:54 p.m. | The FAA's advisory to aircraft operators: all airports stopped “due to extraordinary circumstances and for reasons of safety.” No cause, no real end time (listed expiry: 11:30 p.m.). This wording became the headline. | ABC, USA Today |
| About 4:00 | Three sentences on faa.gov: communication problems at several en route centers, technicians investigating, and a promise: “We will provide updates.” | CNBC, archived FAA page |
| 4:16 | Transportation Secretary on X: a communication issue at all en route centers; immediate updates promised. | CBS, Newsday |
| About 5:00 | Homeland Security Secretary, to reporters at the White House: a telecom outage, no indication of an attack, nothing ruled out, a possible link to the new AI tool being looked at. FAA on X: a temporary telecom outage; every flight accounted for. | ABC, USA Today |
| About 5:00, Newark | Still no airport-wide announcement. One staff member heard about the stop from a passenger. | USA Today |
| 7:35, JFK | A traveler learns of the stop from Instagram while departure boards still list flights as on time. | Newsday |
| 7:45 → about 8:30 | The scheduled briefing starts more than 30 minutes late, after the stop has ended. Officials told CBS a fix was minutes away and they did not want to interrupt it. | CBS, ABC |
| 8:15 | Stop lifted. The FAA's operations site notes the cancellation around 8:30. | DOT, USA Today |
| Sat. 11:00 a.m. | First briefing that includes the FAA administrator; the router explanation is given. It starts late because of technical problems. | ABC, CNN |
| Sunday | The FAA publishes a question-and-answer page. | FAA |
4. Findings
1. The official record never moved. The FAA's statement page carried three sentences and a promise of updates. Archived copies from Friday 8:38 p.m., Friday 9:00 p.m. and Saturday 1:57 p.m. ET all show the same three sentences. As of Nov 16 the FAA's general-statements page still lists that Nov 13 entry and nothing later on the subject, and the original address now forwards to Sunday's Q&A.
Two comparisons from the FAA's own record:
- Its page for the January 2023 nationwide stop still shows statements stamped 7:15, 8:15 and 8:50 a.m. and 6:30 p.m. The first one gave an expected end time.
- On Feb 1, 2025, during a NOTAM-system outage, the FAA said it would send aviation stakeholders status notices every 30 minutes.
So a timestamped running log and a 30-minute cadence are both existing FAA practice. Neither was used for the public on Nov 13.
Fair caveats: the 2023 failure built slowly overnight and the stop was shorter; on Nov 13 controllers were landing 3,500 aircraft at once. The FAA did post on X around 5 p.m. and did note the cancellation on its operations site. This finding rests on three archived snapshots, not a continuous record.
2. No clock. Updates arrived at about 4:00, 4:16, 5:00 and 8:30. None named a time for the next one. Duration estimates depended on where you stood: the advisory listed 11:30 p.m.; an announcement at San Francisco reportedly said at least six hours (second-hand, Boston Globe).
3. Several voices, shifting answers. The FAA, DOT and DHS each spoke. On the two fears that mattered most to the public, an attack or the new AI tool, the answer moved from not-ruled-out at about 5 p.m. to no-evidence at 8:30.
4. No last mile. Logan announced the stop over its loudspeakers. Newark had not after about an hour. Travelers at JFK, Dallas-Fort Worth, Los Angeles, Miami and LaGuardia describe learning from phones, relatives or strangers while boards showed flights on time or merely delayed. LaGuardia later announced it was closing; the Port Authority then said not to take that literally. Each airport and airline improvised.
5. The public is not in the contingency plan. The FAA's 2024 order on operational readiness and contingency planning (JO 1900.47G) requires notices to industry, the military, other FAA facilities and airport authorities. A keyword search of its text found nothing addressed to passengers, the press or the public. A separate FAA communications procedure may exist; none turned up. (Keyword search of the order, not a full read.)
6. A thin rule on aircraft. Since a 2021 amendment, federal rules require a single status notice once a tarmac delay passes 30 minutes; anything further is the airline's choice (14 CFR 259.4(c)(6)). Before that, carriers owed passengers status and cause every 30 minutes. DOT's 2021 reasoning: repeated notices add little when nothing has changed, especially overnight. Most commenters agreed; the passenger group FlyersRights objected.
- Individual travelers told reporters of five to eight hours on aircraft on Nov 13 (AP, CNN). Single accounts, unverified.
- Airlines owe DOT a written report on each delay over three hours within 30 days.
- Scale: airlines reported 437 domestic tarmac delays of more than three hours in 2024, and 289 in 2023 (Bureau of Transportation Statistics, accessed Nov 16, 2026; figures may be revised).
7. Status and advocacy shared a podium. By ABC's account, most of the Transportation Secretary's time at the Friday briefing went to the funding appeal. No FAA official spoke there (NPR).
5. Both sides, fairly
The administration's account
- The safety procedures worked: every aircraft landed, and officials say no one was at risk.
- They moved quickly: the Homeland Security Secretary was on camera within about an hour to address terrorism fears; the cause was isolated and the stop lifted in a little over four hours; a public explanation with the FAA administrator came within a day, then a Q&A and five Sunday interviews. The DHS Secretary called the pace unprecedented.
- The Transportation Secretary says he does not want to release information before it is certain.
- They attribute the failure to decades of underinvestment by both parties, and say Congress restricted the $12.5 billion already appropriated so that none of it can build a new network.
The critics' account
- CNN analyst Juliette Kayyem: Friday lacked the basics of crisis communication, which are what is known, what is not, and what is being done about the gap.
- Rep. George Whitesides (D-Calif., former NASA chief of staff): updates were slow and explanations thin.
- Reps. Rick Larsen and André Carson (top Democrats on House Transportation and its aviation panel): the administration took hours to share answers, and has spent about $1 billion of the $12.5 billion.
- CNN's piece also argues that officials came into the day with a trust deficit of their own making. That is the article's analysis, not a settled fact.
A third position — Speaker Mike Johnson: committees will engage, but no investigation is needed to know more investment is needed.
The fair objection to any fix: officials were busy fixing the thing and reluctant to speak before they were sure. The standard below answers that by having them say what is unknown, on a clock, instead of waiting for certainty.
6. Proposed fix — a public-update standard for nationwide air traffic stops (draft v0.1)
Applies whenever the FAA stops departures at all U.S. airports, or several en route centers lose reliable service.
- First notice within 15 minutes, in plain words. Posted at one fixed public address and sent at the same moment to airlines, airports and TSA. It always answers five questions: what is happening; what kind of problem it is (equipment, weather, security, or not yet known); what is not yet known; what travelers should do; and the clock time of the next update.
- An update every 30 minutes until the stop ends, even when nothing has changed.
- One operational voice. The FAA owns status updates, delivered by a named senior official from the operation. Security agencies contribute one line: whether there is any evidence of an attack. Cabinet briefings add to the clock; they never replace or delay it.
- Status only. Updates carry no budget requests and no blame. Those wait for the after-action report.
- Last mile. Airports put each update on loudspeakers and screens within 15 minutes. Departure boards stop showing affected flights as on time. TSA tells people in line before they are screened. Airline crews get the same text to read to passengers.
- On aircraft. DOT restores a status update at least every 30 minutes during a tarmac delay, with the cause if known.
- A permanent record. Every update stays online with its timestamp. A full public timeline within 72 hours, a root-cause report within 30 days, and an independent review that covers the communication as well as the equipment.
- Practice. One exercise a year with airlines and airports.
Illustrative first notice (model text for this proposal, not an FAA statement; it uses only what officials were already saying by about 4 p.m.)
4:05 p.m. ET. The FAA has paused all departures from U.S. airports. Radio and radar links at several air traffic centers are unstable. Aircraft now in the air are being guided to land normally. This began in our own telecommunications equipment. We do not yet know the cause or how long this will last. Security agencies are checking for any sign of an attack and we will report what they find. If you have not left for the airport, wait. If you are at the airport, stay near your gate. Next update: 4:35 p.m. ET, at this address.
7. Who can adopt it
- The FAA administrator, by internal order: items 1–5, 7 and 8. No appropriation is needed. No new legal authority appears necessary, though that is a question for counsel.
- Congress, with one paragraph in whatever carries the FAA money. The administration-backed vehicle is the Modern Skies Act (S.5572, Sen. Eric Schmitt, R-Mo.; identical H.R.10683, Rep. Tracey Mann, R-Kan.): $30.1 billion, no cosponsors on either as of Nov 16, and no provision on public communication (Congress.gov, U.S. Library of Congress, accessed Nov 16, 2026). It already contains a quarterly-reporting clause (Sec. 4(c)), a natural place to add a 90-day deadline for a public-notification protocol. Stopgap government funding expires Dec 11, the likeliest moment for FAA money to move. Committee report language is the lighter alternative.
- DOT, by rulemaking, for item 6. Any person may petition (49 CFR Part 5).
- Airports and airlines, by agreement with the FAA, for item 5.
8. Routes open to a private citizen
This is not legal advice. The filings below are simple, but procedure should be confirmed before anything is signed.
- A. Hand it to the people scoping the reviews. The one-page standard plus sections 3–4 of this file, to staff on both sides of House Transportation & Infrastructure (Graves, Larsen, Carson) and Senate Commerce (Cruz, Cantwell, Duckworth), and to your own two senators and House member. Members who have already spoken about the communication specifically: Whitesides, Larsen and Carson, Blumenthal. Odds for any single letter are low. They improve when the ask is one paragraph, costs nothing, comes with a checkable finding, and arrives while the bill is being written.
- B. Give the checkable finding to people with platforms. The unchanged statement page versus the 2023 log can be verified in two minutes. Candidates: the CNN author, Kayyem, aviation reporters.
- C. Formal filings in your own name. (1) A petition asking DOT to restore periodic status updates during tarmac delays. (2) A FOIA request to the FAA for its public-notification procedures and the log of what it sent airlines, airports and TSA on Nov 13. Both are slow (months), but each creates a record and an obligation to answer.
- D. Allies with standing. FlyersRights (which objected in 2021), other passenger groups, the controllers' union, airport associations.
- E. An op-ed with a local angle. One example: Atlanta's Hartsfield-Jackson was among the hardest-hit airports in the recovery (NBC).
9. Calendar
| Date | Event |
|---|---|
| Mon Nov 16 | DOT's detailed funding request due on the Hill; FAA and DOT staff brief House Transportation; Homeland Security Council meets (CBS, AP) |
| Wed Nov 18, 10:00 a.m. ET | House Homeland Security hearing, “Worldwide Threats to the Homeland: 25 Years After 9/11,” Cannon 310. The DHS Secretary is the expected lead witness (Congress.gov, Newsday) |
| From about Nov 20 | Thanksgiving travel builds; Thanksgiving is Nov 26 |
| Fri Dec 11 | Stopgap funding expires |
| About Dec 13 | Airlines' tarmac-delay reports for Nov 13 due at DOT |
| Jan 3, 2027 | New Congress convenes |
10. Context from federal records
- Contractor dependence. USAspending shows about $3.99 billion in FAA contract transactions with Harris Corporation from October 2019 through September 2026, plus about $0.46 billion under L3Harris Technologies names (USAspending.gov, U.S. Department of the Treasury, accessed Nov 16, 2026). (Recipient rows are not merged by company; recent periods are provisional.) The Transportation Secretary says he cannot drop the contractor because it owns the network the FAA runs on.
- Oversight history. DOT's inspector general reported in February 2024 that the FAA extended IT and telecom contracts without competition; the FAA agreed to all seven recommendations, and the report page lists each as closed by September 2025. CBS reports the same audit counted ten improperly authorized extensions of the Harris telecom contract.
- A prior incident. In September 2025 the FAA's own statement on a Dallas approach-control outage said L3Harris's oversight had failed to ensure backups worked.
- GAO, September 2026. No reliable life-cycle cost estimate and no integrated master schedule for the modernization program; 11,389 separate project schedules. DOT partly concurred. The FAA says Friday's router swap was routine sustainment and not part of that program.
- The $12.5 billion. House Transportation Democrats say $4.3 billion is obligated and $1 billion spent. The Secretary says all of it is committed and will be deployed by the end of 2028.
- The $30.1 billion request, as written in the Modern Skies Act. $10.1 billion for air traffic control systems, of which $2.0 billion is for cloud computing and related telecommunications; $10 billion for terminals at up to three medium-hub airports; $10 billion for towers and airport grants (bill text, Congress.gov, U.S. Library of Congress, accessed Nov 16, 2026). The Secretary's $50 billion figure from Friday had not been itemized when this file was written.
11. Draft questions on the network failure
For network engineers and for the committees doing oversight. These are questions, not findings.
- Blast radius. How could a device at one remote radio site reach and destabilize equipment serving 17 of 22 centers? What segmentation, filtering or rate limiting sits between remote sites and the core, and why did it not contain this?
- Load. The reported flood works out to roughly 200–250 connection attempts a second. What made that enough to disturb radar and voice feeds? What is the measured capacity of the 2001-era routers, and was it documented?
- The disabled function. What is the broadcast function that was switched off on about 60 routers, why was it on in newly installed devices, and what does turning it off cost?
- Change control. What testing was done on this router model and configuration against the legacy equipment? Was there a staged rollout, a rollback plan and a monitored window? Who at the FAA approved a Friday mid-afternoon cutover?
- The second site. Amarillo's router had been in place about three weeks and began flooding only when El Dorado was switched on. What interaction explains that, and how many similar pairs exist?
- Detection. The FAA administrator said the source was unclear for about 45 minutes. What monitoring would locate a flooding device in minutes?
- Ownership. The contractor owns and operates the network. What visibility and control does the FAA itself have over configuration and telemetry, and what does the contract require?
- Remaining exposure. Roughly 30 percent of circuits are still to convert. What changes before the next cutover, and what is the plan for Thanksgiving week?
12. Open questions
- Does the FAA have any written procedure for informing the public during a system-wide event?
- Exactly what did the FAA send airlines, airports and TSA on Nov 13, and when?
- What did the FAA's public status site (nasstatus.faa.gov) show during the stop?
- How many aircraft exceeded the three-hour tarmac limit?
- Which committee holds the first hearing on the outage itself? House Transportation lists its Nov 10 modernization hearing as postponed. A former DOT inspector general said on NPR that a hearing was set for Tuesday Nov 17; none could be confirmed on Congress.gov.
- Is an inspector-general or GAO review under way? None found as of Nov 16. House Democrats asked GAO in October to audit the SMART tool.
13. How this was researched, and its limits
- About 30 news reports and nine official pages read; the CNN piece, the FAA Q&A, the DOT and DHS releases and the USA Today and Newsday live logs read in full.
- Partial reads: the FAA's general-statements page (newest entries plus keyword search); FAA Order JO 1900.47G (keyword search only); the 2021 Federal Register rule (the notification sections; the connector cut the page off at about 50,000 characters).
- Could not open: two Reuters reports, SFGATE and KGW.
- Congress.gov check of hearings covered the most recently updated meeting records in each chamber, not every scheduled meeting.
- Federal records were pulled through the USAFacts connector on Nov 16, 2026 (Congress.gov, USAspending, and .gov pages).
14. Sources
Official statements
- FAA: Nationwide Ground Stop — Questions and Answers (Nov 15)
- FAA statement page as archived Fri 8:38 p.m. ET · Fri 9:00 p.m. · Sat 1:57 p.m.
- FAA General Statements (Nov 13, 2026 entry; Feb 1, 2025 NOTAM entry; Sept 20, 2025 Dallas entry)
- FAA NOTAM Statement, January 2023
- FAA Order JO 1900.47G
- DOT release, Nov 13 · Nov 14 · Nov 15
- DHS release, Nov 13
- Larsen and Carson statement
Federal records via the USAFacts connector (all accessed 2026-11-16)
- S.5572, Modern Skies Act and H.R.10683 — Congress.gov, U.S. Library of Congress. Bill text
- House Homeland Security hearing notice, Nov 18 — Congress.gov, U.S. Library of Congress
- USAspending award search — USASpending.gov / U.S. Department of the Treasury (FAA as awarding sub-agency; recipients matching “L3Harris”; contracts; Oct 1, 2019 – Sep 30, 2026)
- Tarmac Delay Rule, 86 FR, May 3, 2021 — Federal Register
- Air Travel Consumer Report: full year 2024 — Bureau of Transportation Statistics
- DOT OIG, FAA IT and telecom contracting, Feb 26, 2024 — DOT Office of Inspector General
- USAFacts' notice for its government web search, which retrieved the last three items and the FAA statements page: “Web search is performed through the You.com Search API: the search query is sent to You.com, a third-party commercial search provider. Pages are fetched through the You.com Contents API: the page URL is sent to You.com, which retrieves the page. When You.com returns no page or an error page, USAFacts requests the page directly from its host.”
Other federal sources
- 14 CFR 259.4 · 49 CFR Part 5
- GAO-26-107992 (Sept 14, 2026)
- FEMA ICS reference guide and CDC crisis-communication principles, the existing federal doctrine the standard borrows from
News
- CNN: Messaging failures worsened the air traffic freeze
- ABC: main report · timeline
- CBS: administration timeline · what to know · years of warnings
- NPR: Nov 13 · Schiavo interview · Nov 15
- AP: Nov 13 · funding dispute · SMART questions
- USA Today: live log · oversight
- New York Times: Nov 13 log · Nov 14 log
- Newsday live log · Boston Globe · Los Angeles Times · WPLG Miami
- CNBC: Nov 13 · Nov 14
- Newsweek · Politico · The Hill · Roll Call · GeekWire · Florida Today