Aviation & public systems Research brief 001
The documented ground stop, officials’ explanations, and a separate review of modernization delivery—with source links and questions for public leaders.
Downloadable Edition 2 reviewed through: 14 November 2026, 6:15 a.m. EST / 12:15 p.m. CET. This is a dated research snapshot. Editorial revision: 14 November 2026.
Developing record · 14 November 2026
The public explanation became more specific. The exact fault is still being investigated. Read the earlier account and the later statements together.
13 November · Official account
DOT’s published briefing highlights record Duffy attributing communications and radar instability to overloaded older routers. He also said newly installed IP switches had not failed. Source: DOT →
14 November · Reported briefing
According to ABC News, Duffy described copper-to-fiber maintenance, a router generating excessive connection attempts, and restoration after the work was isolated. He identified contractor error or faulty equipment as possibilities. Source: ABC News →
What officials have not yet resolved: ABC reports that Bedford said investigators had found no evidence of malicious or AI-related activity and would share the root-cause analysis once complete. That statement is not a published technical finding. Source: ABC News →
Recovery outlook: AP reports Bedford expected schedules to recover by the end of Sunday, November 15. That is a forecast; disruption continued on Saturday. Source: AP via CityNews →
Our analysis · Question for officials
Which component failed, which change triggered it, and how did the failure spread beyond the remote site? Request the change log, approval and test records, isolation timeline, and final root-cause analysis. The age of equipment and the timing of maintenance, by themselves, do not resolve responsibility.
This update uses reporting of Saturday’s briefing; we have not independently reviewed its full recording or the underlying engineering records. Read the L3Harris history and separate Microsoft evidence track →
Edition note: The downloadable PDF, Word brief and connections explorer remain Edition 2, reviewed through 6:15 a.m. EST / 12:15 p.m. CET. This later web update is not yet incorporated into those materials.
Read before downloading
What this brief establishes, what remains open, and how to use it.
On November 13, 2026, the FAA ordered departures stopped nationwide and later cancelled the restriction. The operational notices establish those actions and their recorded times. [16] [17]
Secretary Sean Duffy attributed the disruption to overloaded legacy equipment, said new IP equipment was unaffected and excluded SMART. He also said radar and communications were not completely lost and existing procedures enabled safe landings. These remain attributed explanations and accounts of the response. [18]
GAO documented aging-system risks in 2024, before the May 2025 modernization plan. Its 2026 review acknowledged initial progress while identifying cost and schedule gaps; DOT disputed aspects of that assessment. This history informs modernization oversight without establishing what caused the November 13 incident. [28] [2] [6]
No final FAA technical root-cause report was located in the official releases reviewed by the stated cutoff. The brief therefore makes no finding about cause, fault or misconduct. Announcement timing and missing public documents do not establish a causal link or prove that safeguards were absent.
Eleven recommended questions identify who can answer, why the question matters and which records could resolve it. Incident causation, modernization readiness and local impacts are treated as distinct oversight tasks. The goal is a documented explanation that can be checked and updated.
Edition 2 · 28 source references · 11 recommended questions
New: November 14 briefing and contractor-history supplement. Read the update, Microsoft statements and contracting timeline → The downloadable Edition 2 brief retains its earlier cutoff.
Scope & evidence
Purpose and scope: this brief separates two oversight tasks: establishing what caused the November 13 disruption, and assessing modernization delivery and safeguards. The chronology does not presume a connection between SMART and the incident. It recommends questions for documented answers and makes no finding about cause, fault or misconduct.
Evidence rule: an announcement establishes what was publicly stated. Deployment counts, technical explanations and projected benefits remain attributed to their source. An oversight request establishes that questions were asked, not that an allegation was proved. Each numbered citation links directly to a source.
01 / The modernization record
Federal Aviation Administration (FAA) presentation: reported a March 27 FENS telecommunications contract award to Verizon and an initial testing and transition phase. This establishes a modernization predecessor, not completion. [1]
GAO reported that FAA’s 2023 assessment classified 51 of 138 air traffic control systems as unsustainable and 54 as potentially unsustainable. GAO found slow modernization of critical systems. These historical findings establish earlier risks, not the cause of the 2026 incident. [28]
Secretary Sean Duffy and the Department of Transportation (DOT): announced a broad air traffic control replacement plan and projected greater safety, fewer outages and fewer delays. [2]
Duffy and FAA Administrator Bryan Bedford: selected Peraton as prime integrator, announced an end-2028 objective and described $12.5 billion as a down payment requiring additional funding. [3]
DOT: launched the Modern Skies website, with a commitment to monthly progress updates and local information on completed and upcoming projects. [4]
FAA: announced Air Space Intelligence (ASI) work on Flow Management Data and Services (FMDS) and Strategic Management of Airspace, Routes, and Trajectories (SMART). Initial software operations were planned for fall; reduced congestion and workload were projected. [5]
GAO acknowledged initial modernization progress and the urgency of replacing aging systems, while finding incomplete lifecycle cost estimates and no integrated Phase 1 schedule. DOT partially concurred, stating that program cost estimates and schedules existed. GAO maintained its recommendations because the materials omitted costs and did not integrate project dependencies. Phase 1 targeted December 2028; Phase 2 had no estimated start or completion. [6]
DOT’s response said teams had developed and continued updating Phase 1 lifecycle cost estimates and that program schedules existed. GAO found that the supplied estimates omitted government costs, much of later operations and maintenance, and Phase 2; it also found that separate project schedules did not incorporate their interdependencies. GAO retained both recommendations. This disagreement concerns the completeness and integration of planning, not whether any planning existed. [6]
Dates above are public release or presentation dates. Most sources supply no verified publication clock. The contract date within the first row is explicitly retrospective.
02 / Launch, scrutiny & expansion
Bedford testimony: described intended links among connectivity, data, planning and future automation upgrades. These were architectural objectives, not a verified inventory of live production connections. [7]
FAA launch release: announced limited SMART use around Washington, D.C.; projected fewer delays, lower fares and reduced controller stress. It said staff review recommendations and local leaders may accept or reject them. [8]
DOT fact sheet: described a slow, staged rollout with continuing testing, training and assessment as additional functions were introduced. No separate publication day was verified. [9]
Duffy, Bedford and Senator Eric Schmitt: supported proposed additional modernization funding. DOT linked future completion to reduced disruption. The announcement was a funding appeal, not certification of a completed system. [10]
Senator Chris Van Hollen, Representative April McClain Delaney and fellow Democratic signatories: requested a pause and answers about approvals, testing, training and oversight. Their letter described a 90-day evaluation before broader deployment and requested answers by October 19. This was the signatories’ request, not a finding or action by Congress as a whole. [11]
House Transportation and Infrastructure Democrats: requested a GAO audit of SMART/FMDS safety analysis, testing, performance measures and deployment strategy. This was a request, not an audit finding. [12]
DOT: announced E-IDS information displays at five initial facilities, with 435 sites targeted by end-2028. It separately reported 69% copper replacement and 226 IP voice switches. These are agency-reported component measures. [13]
FAA: announced SMART expansion to the airspace of all 22 centers after describing the regional rollout as successful. It reported 180 rerouted flights and average time and fuel savings. Exact activation times were not supplied. [14]
Analysis
Analysis: September 21 to November 10 is 50 elapsed days. The source for a 90-day evaluation is the October 9 letter from Democratic lawmakers. These records alone do not establish an FAA deadline, a violated requirement or the release of every SMART capability. Question 4 requests the approved plan, any revisions and the expansion decision. [8] [11] [14]
The November 10 announcement preceded the November 13 incident by three calendar days. That sequence does not establish a causal relationship. Modernization oversight remains a separate line of inquiry unless incident evidence establishes a connection.
03 / The incident record
All times below are EST, UTC minus 5 hours. Event time, notice issue time and the time a statement was made are kept separate. Briefing clock estimates use its observed 8:31 p.m. start; transcript offsets identify the relevant passage. [21]
FAA Advisory 107: O'Hare ground-stop period cites equipment outage and communications issues. Whether it shared the national incident's cause is not established here. [15]
FAA Advisory 111: orders departures stopped until further notice; inbound international flights handled individually. [16]
Duffy: retrospectively placed broader radar and communications instability at 3:36 p.m. He said communications and radar were not completely lost and existing procedures enabled aircraft to land safely. These are attributed statements about the response, not an independent safety finding. [18] [19]
Other dated records: the FAA’s November 13 newsroom statement labels its information preliminary. House committee Chair Sam Graves, a Republican, and Ranking Member Rick Larsen, a Democrat, jointly thanked FAA personnel and controllers for swift safety action and committed to reviewing the incident. The statement’s exact publication clock is unavailable. [14] [22]
As of the review cutoff: no final FAA technical root-cause report was located in the official releases reviewed. Missing public records are not treated as proof that testing, approvals or agency replies did not exist. Service restoration does not itself establish the cause.
04 / Questions for decision-makers
Eleven questions, each paired with its basis, an appropriate respondent, and the records that could provide clarity. These are recommended oversight questions.
State and county offices can request FAA briefings and work with their congressional delegation on federal oversight. Federal airspace management belongs to the FAA; local offices should not assume authority to direct federal air traffic operations. FAA Regional Administrators coordinate with state and local governments. [23] [24]
Showing all 11 questions.
What is the earliest verified fault, which facilities and functions were affected, and what evidence identifies the initiating event? How do the Chicago notice and the later 3:36 p.m. account relate, if at all?
Why this question mattersThe Chicago notice records a local restriction, while Duffy described broader instability at 3:36 p.m. Their relationship is unestablished; different event scopes and time fields should not be treated as a contradiction. [15] [18] A common timeline should distinguish detection, degradation and decisions to stop departures.
Who can answerFAA incident lead.
Records to requestTimestamped incident log, affected-facility list and causal report with unresolved hypotheses.
Which software, configuration or network changes, if any, were made to affected systems before the first fault? What did Secretary Mullin mean by patches and new technology, and has that account been confirmed, revised or rejected?
Why this question mattersMullin offered a tentative transition explanation (transcript offset 14:19-14:49). [19] Age and overload do not identify what initiated the failure.
Who can answerFAA technical lead and responsible providers through FAA.
Records to requestChange register, approval records, versions, rollback actions and supporting telemetry.
Which systems contributed to the incident, which were ruled out, and what evidence supports those conclusions? What evidence supports the stated exclusion of SMART, including any relevant interfaces or shared infrastructure?
Why this question mattersDuffy excluded SMART, citing separation and human review. [18] [19] The same evidentiary standard should support both causal findings and exclusions. This question seeks the technical record; it does not imply SMART contributed.
Who can answerFAA architecture and incident leads.
Records to requestPublic architecture summary and interface inventory; supporting logs through appropriate oversight channels.
What evaluation period and success criteria did FAA approve? How does the 90-day period described in the congressional letter relate to the November 10 expansion? Identify the approving official and any revised scope, schedule or authorization.
Why this question mattersThe limited launch and expansion announcements were 50 days apart. [8] [11] [14] This establishes which decision was made and whether it met the applicable criteria, without presuming a breach.
Who can answerFAA official responsible for operational acceptance.
Records to requestApproved plan, evaluation results, decision memorandum and revision history.
Which compatibility, load, backup and rollback tests, if any, evaluated the mix of old and new components? What passed, what limitations remained, and who accepted them? Separately, what tests supported lifting the ground stop?
Why this question mattersDOT described staged rollout; the briefing distinguished old and new equipment. [9] [18] Deployment acceptance and recovery acceptance answer different readiness questions.
Who can answerFAA safety and operational acceptance officials.
Records to requestTest plans, pass criteria, results, risk acceptances and signed release decisions.
Which staff were trained before each rollout stage? How were recommendations and any rejections, overrides or inaccuracies recorded? What evidence assesses workload, decision quality and safety alongside delay or fuel benefits?
Why this question mattersFAA said staff review SMART recommendations; the October 9 signatories requested training and evaluation details. [8] [11] Operational records can show how that human role works in practice.
Who can answerFAA operational lead, with controller and workforce input.
Records to requestTraining completion data, procedures, aggregate recommendation logs and evaluation measures.
Which capabilities, sites and dependencies are included in each funded phase and deadline? What remains unfunded? What has changed in the integrated schedule and lifecycle cost estimate since GAO's review?
Why this question mattersGAO identified cost coverage and schedule integration gaps; DOT said program estimates and schedules existed. [6] The later funding request raises a separate question about funded deliverables and dependencies. [10] Neither establishes the outage’s cause.
Who can answerFAA program and financial leads; DOT.
Records to requestCurrent baseline, cost assumptions, dependencies, change history and response to GAO recommendations.
What responses were provided to the October requests, on what dates, and which can be released? Who owns the incident review, when will findings be issued, and how will provisional statements be corrected if evidence changes?
Why this question mattersThe lawmakers who signed the October letters requested records and review. [11] [12] Graves and Larsen later committed to reviewing the incident. [22] These requests do not establish that agency replies were absent or that a failure occurred.
Who can answerFAA/DOT legislative affairs and the identified review lead.
Records to requestResponse correspondence, review scope, publication milestones and corrective-action register.
How many local flights, passengers and essential movements were affected, over what period? What public costs or service interruptions can be documented, and what remains estimated?
Why this question mattersThe federal departure restriction was national. [16] National disruption figures do not establish the effects or costs in a particular county.
Who can answerAirport operator, airlines and relevant local agencies.
Records to requestTime-bounded counts, definitions, service logs and itemized public costs, with duplicates removed.
Who coordinated airport, airline, emergency-management and ground-transport responses? What arrangements covered accessible communications, mobility assistance, medication needs and overnight accommodation, and what gaps, if any, were recorded?
Why this question mattersFAA's overnight plan kept coordination lines open and noted separate airline-requested stops. [27] Canceling the national order does not establish that local services or passenger needs had returned to normal.
Who can answerAirport operator, emergency management, airlines and transport providers.
Records to requestActivation timeline, assistance logs, after-action findings and assigned improvements.
Which upgrades serving our airports are planned, installed, tested and accepted for operational use? Which dependencies sit outside the county, and how are local officials notified of outages and scheduled changes?
Why this question mattersDOT committed to providing local project reporting and published national component counts. [4] [13] A national percentage cannot establish the readiness or resilience of a particular airport.
Who can answerFAA regional/program officials and airport operator.
Records to requestSite-level status, acceptance dates, external dependencies, planned outages and contact procedures.
Confirm each airport's owner/operator and the office's actual oversight role. Airport-owner obligations vary; the local questions above are recommended requests, not claims of universal county authority. Coordinate federal technical questions through the FAA Regional Administrator and congressional delegation. [24] [25]
Request the finding, supporting record and date; the responsible official; remaining uncertainty; and the next verification step. If evidence cannot be released publicly, request a public summary and a route for authorized oversight review. A project count, funding total or general safety assurance does not answer a question about a particular approval or technical cause.
05 / Using the brief
Request one coordinated briefing with named technical and operational respondents. Send the numbered questions in advance and request a record-based written response. Ask the congressional delegation to coordinate existing committee, GAO and DOT Inspector General work; the Inspector General accepts congressional audit requests. [26]
Set an explicit response date agreed with the recipients, identify an office contact and maintain a public tracker of requests, answers and outstanding records. Preserve local incident records and copies of source statements. Publish corrections with dates and source links. These are recommended practices, not asserted statutory deadlines.
Download the revised oversight brief, including its executive summary, chronology, questions, and numbered source register.
06 / Follow the evidence
28 references supporting this edition. Source dates and notes distinguish announcements, operational notices, oversight requests, and transcripts. The Factbase transcript is a secondary reference; source 20 links to the original recording.
Showing 28 of 28 sources
9 Nov 2023 workshop, slide 69; reports the 27 Mar 2023 Verizon award and planned testing.
8 May 2025; proposed program scope and public benefits.
4 Dec 2025; end-2028 objective, existing funding and additional funding request.
22 May 2026; monthly reporting and local project information commitment.
22 Jun 2026; planned capabilities and initial fall operations.
GAO-26-107992, released 14 Sep 2026. Planning findings and agency response: printed pages 23–29; DOT response dated 12 Aug 2026 in Appendix III.
15 Sep 2026; intended relationship among connectivity, data, planning and automation upgrades.
21 Sep 2026; Washington-region launch, projected benefits and human review.
September launch materials; staged rollout, continuing testing and training. Separate issue day unverified.
28 Sep 2026; funding proposal and projected benefits conditional on future completion.
9 Oct 2026; Democratic signatories describe a 90-day evaluation and request answers by 19 Oct. This is not a finding by Congress as a whole.
13 Oct 2026, dated in committee release index; request concerns SMART and FMDS.
5 Nov 2026; first five facilities, 435-site target and agency-reported replacement figures.
10 Nov expansion entry and 13 Nov preliminary outage entry. Rolling page; use the individual entry dates.
13 Nov: ground-stop period begins 20:10Z; signed 20:28Z. These are different time fields.
13 Nov: event 20:53Z; issue/effective time 20:54Z. Departures stopped until further notice.
14 Nov UTC: event 01:16Z; signed/effective 01:19Z. Both fall on 13 Nov in EST.
13 Nov; Duffy’s account of the response, legacy overload, new equipment, reopening and SMART. Includes recording link.
13 Nov. Secondary transcript; elapsed offsets cited in chronology. Original White House recording: source 20.
13 Nov; linked by DOT. Player has lead-in, so transcript offsets are not player timestamps.
Reporter Naomi Lim: briefing ran 8:31-9:04 p.m. EST; note sent 9:06 p.m. Independent archive.
13 Nov; bipartisan committee leaders thank FAA and controllers for the safety response and commit to review. Publication clock unavailable.
49 U.S.C. 40103(a)-(b); federal airspace sovereignty and FAA airspace responsibilities.
See Regional Administrators and Ombudsman: coordination with federal, state and local governments.
Airport Compliance Program overview; obligations vary by agreements and conveyance documents.
Explains audit initiation, including congressional requests, evidence review and agency responses.
14 Nov UTC; describes overnight coordination and separate airline-requested ground stops.
GAO-24-107001, published 23 Sep 2024; historical findings based on FAA’s 2023 sustainability assessment. Current recommendation statuses on the web page may change.
No sources match your search. Try an agency name, such as FAA or GAO.
Follow the source record
A curated news feed on the nationwide ground stop. Summaries are ours; linked articles belong to their publishers. Source type identifies who is speaking, not whether every claim is established.
Last reviewed: . Manually reviewed; not an automatic or real-time feed. Newer publication dates appear first; same-day items are not ordered by exact time.
Showing 5 sources
Coverage of Duffy’s account of the router disruption and Bedford’s commitment to publish the root-cause analysis. These are attributed statements while the investigation continues.
Live page: entries and headlines may change.
Read source at ABC News (opens in a new tab)↗AP reports Bedford’s expectation that schedules would recover by the end of Sunday, alongside continuing cancellations. It notes that investigators were considering a faulty router, correcting an earlier reference to wire.
Recovery timing is an official forecast, not a confirmed outcome.
Read source at Associated Press · via CityNews (opens in a new tab)↗Reuters covers continuing cancellations, officials’ recovery expectations and the investigation into work by L3Harris. Flight totals are time-specific and may change.
News reporting; not a final engineering finding.
Read source at Reuters (opens in a new tab)↗The department’s briefing highlights record Duffy’s explanation involving overloaded older routers and instability in communications and radar. This preserves the official account given on Friday.
Primary source for what officials said; not independent verification of cause.
Read source at U.S. Department of Transportation (opens in a new tab)↗The FAA announced communication issues affecting multiple Air Route Traffic Control Centers and said technicians were investigating. The statement explicitly identifies the information as preliminary.
Initial statement retained for chronology; not a current flight-status service.
Read source at Federal Aviation Administration (opens in a new tab)↗Dated web supplement · 14 November 2026
Executive update: Reporting on the November 14 briefing identifies L3Harris maintenance as the work officials are examining. The exact fault remains unresolved. Separately, primary records establish that Harris won the legacy network contract in 2002, the L3Harris merger closed in 2019, and Verizon received the successor network award in 2023. A newer corporate name does not mean a new aviation contractor.
Version note: This supplement postdates Edition 2’s 12:15 p.m. CET review cutoff. The PDF, Word brief and connections explorer retain that earlier scope. Supplement sources are labelled U1–U8 below; original citation numbers are unchanged.
Reuters reports that Duffy identified L3Harris work converting a remote location from copper to fiber, with installation error or faulty equipment still under investigation. This is an attributed briefing account, not a published final technical finding. Reuters reported no response from L3Harris to its request for comment; that is not a refusal to respond to this publication. [U1]
We have not independently reviewed the full November 14 briefing recording or the underlying change tickets, logs and engineering findings for this supplement. The earlier equipment-overload explanation should therefore remain in the chronology alongside the later, more specific account, rather than be silently replaced.
In the November 13 briefing transcript, Mullin said he saw no reason to connect the Microsoft outage with the FAA disruption (02:13–02:19). [U2] Anadolu separately reported Microsoft’s statement that it had no indication the ground stop related to its services. We have not independently retrieved the original company post for this supplement. [U3]
Evidence limit: These are attributed statements about the absence of an identified connection. Neither overlapping timing nor similar language about upgrades establishes a common cause. A comparison should use each incident’s own service scope, change record, failure timeline and post-incident findings.
The reviewed records establish competitive selection, corporate continuity and the successor award. They do not supply the complete source-selection evaluation, every extension after the original 2017 term, the current division of responsibility, or the work order for the affected site. Those gaps prevent a complete explanation of why Harris won, how the legacy arrangement continued, and who controlled the specific change.
The reporting record
Method: selected substantive public records from the modernization and incident timelines, with duplicate releases consolidated. The same evidentiary standard applies to every administration, official and party. Relevant agency responses, historical context and contrary evidence are included; attributed statements, analysis and recommendations are distinguished from findings. No anonymous-source causal account is presented as established. This dated snapshot is not a forensic investigation or an exhaustive catalogue of public statements.