The Architecture of
Critical Infrastructure
The FAA modernization crisis, contractor boundaries, and the difference between restoring service and repairing a system.
The FAA contained the immediate safety risk of a nationwide ground stop. The public record has not established that the architecture which allowed the disruption to propagate has been repaired.
The November 13 disruption exposed the dependency between national air traffic operations and telecommunications equipment being replaced during an accelerated modernization program. Pilots and controllers managed the immediate emergency, while the underlying governance questions crossed multiple contractors, budget accounts, and institutional responsibilities.
GAO had already identified the absence of a comprehensive lifecycle cost estimate and an integrated master schedule. The incident now raises a more specific question: who was responsible for understanding how a localized network change could affect the wider system before that change went live?
How did a local equipment change become a national disruption?
Accounts of the incident described repeated connection attempts associated with router changes on the FAA Telecommunications Infrastructure network. Those changes reportedly produced effects far beyond the installation sites, with instability reaching 17 of the FAA’s 22 en route centers. The complete technical causal chain has not been independently published.
The FAA’s response isolated the implicated sites and disabled broadcasting on other routers. Those actions appear to have stabilized operations. They do not, by themselves, establish whether a routing, segmentation, configuration, or approval defect has been permanently corrected.
Who was responsible for governing the whole dependency?
A contractor can meet its local obligations while the system remains vulnerable at the interfaces between contracts.
The relevant distinction is between operating a legacy telecommunications service, integrating a modernization portfolio, and deploying a separate AI-supported traffic-management platform. Each relationship has its own scope, deliverables, and approval chain.
The decisive documentary question is whether the router replacement appeared in the integrated modernization dependency network, remained within legacy network maintenance, or crossed both streams without an assigned system-level owner.
Three contractors, three different obligations
L3Harris
Operates the legacy FAA Telecommunications Infrastructure environment associated with the router replacement work. The installation requirements, change-control obligations, and FAA acceptance records are necessary to identify responsibility for the specific equipment substitution.
Peraton
Serves as the modernization systems integrator. GAO documented an incomplete integrated master schedule; the contract ceiling was reportedly reduced from $1.5 billion to an initial negotiated value near $876 million. The exact boundary of its interface-management duties requires the contract and statements of work.
Air Space Intelligence
Holds a separate contract of up to approximately $875 million for Flow Management Data and Services and SMART. Its November rollout is a legitimate testing and governance subject, but the public record does not establish that SMART caused the router disruption.
The most consequential unresolved boundary is the relationship between L3Harris’s legacy network changes and Peraton’s integration obligations. A master schedule that does not capture a critical dependency cannot help decision-makers anticipate its effects. Yet the record does not currently establish whether these specific installations were required to appear in Peraton’s schedule.
Responsibility also rests with FAA officials who approved the work, set acceptance criteria, authorized operational change windows, and decided what evidence was sufficient before deployment. Contractor separation does not remove the agency’s system-level obligations.
How did the request grow while planning controls remained incomplete?
Initial modernization appropriation
Congress provided approximately $12.5 billion for the broader initiative, with roughly $9 billion identified for first-phase systems modernization.
GAO warns of planning deficiencies
GAO reported that the accelerated program lacked a comprehensive lifecycle cost estimate and integrated master schedule despite thousands of individual project schedules.
Written $30.1 billion request
DOT and OMB requested $10.1 billion for ATC modernization, $10 billion for towers and airport infrastructure, and $10 billion for a terminal pilot program.
Ground stop and $50 billion public demand
Following the outage, Secretary Duffy publicly called for $50 billion. The additional $19.9 billion above the written request was not itemized in that request.
Congressional spending allegations
House Appropriations Democrats asserted that only $5 billion of $14.4 billion available had been spent and that $5 billion was being withheld. The underlying budget execution records are needed to distinguish appropriations, obligations, outlays, and apportionment.
The written request identifies $2 billion within its ATC modernization allocation for telecommunications and cloud infrastructure. The later public figure is a different kind of statement: a demand without an equivalent project-level justification in the documents reviewed.
The funding question is not whether aging systems need investment. It is whether Congress can trace proposed dollars to deliverables, system dependencies, testing obligations, and verifiable reductions in operational risk.
What shape does the modernization architecture create?
The Answerability Index locates eight functions from dominion logic at the center to relational logic at the rim. These provisional values assess the institutional structure visible in the current record. They are interpretive judgments, not a safety certification, a final finding of fault, or an overall grade.
Eight functions
Select a function to see the structural rationale behind its provisional value.
Where does the architecture fail to turn knowledge into control?
The system could detect and contain a disruption faster than it could demonstrate that the conditions allowing its propagation had been corrected.
Feedback exceeds Accountability
Feedback is 6.0; Accountability is 3.5. Operational telemetry, GAO audits, and congressional inquiries generated warnings and investigative channels. The record still lacks a complete, public assignment of responsibility across installation, integration, FAA approval, and independent validation.
The gap matters because observing risk does not guarantee that anyone has the authority, duty, or incentive to stop it before deployment.
Restoration does not establish Repair
Repair is 3.0. Isolating routers and lifting the ground stop restored service. Permanent architectural repair would require a tested explanation of fault propagation, corrected controls, and independent confirmation that similar changes cannot reproduce the failure.
Travelers, workers, and operators also absorbed costs beyond the immediate technical restoration. Those downstream consequences are not automatically repaired when the network returns.
Warnings did not become Adaptation
Adaptation is 4.0. GAO’s missing master schedule and cost-estimate findings predated the outage. October congressional questions about SMART testing predated it as well. Those warnings concern different aspects of modernization and cannot be assumed to have predicted this router incident. They nevertheless expose the program’s difficulty coordinating risk across its moving parts.
Frontline agency is uneven
Controllers and pilots exercised substantial operational judgment during the emergency. Their ability to manage aircraft safely does not mean they controlled the upstream procurement, testing, or deployment decisions that created the conditions they had to manage.
The scoring boundary
The values describe the current documentary record. Technical root-cause findings, contract provisions, change approvals, test records, and budget execution documents could materially change the assessment.
Where can compliant processes still leave systemic harm intact?
The Taxonomy of Structural Harm identifies mechanisms that may persist even when individual actors follow local procedures. The categories below are applied to documented governance weaknesses and unresolved interface questions, with uncertainty kept visible.
Dependencies that never reach a common record
What work or relationship sustains the system without appearing in its accounting?
Thousands of schedules without a completed integrated master schedule can conceal cross-project dependencies. The question is whether the affected router changes were included, excluded, or left outside the integration boundary.
A project can look complete while systemic risk remains
What does the chosen unit of measurement fail to see?
Local installation acceptance, milestones, and budget execution can all be reported while the capacity of a change to propagate across the national network remains insufficiently tested.
Technical knowledge is unevenly distributed
Who can obtain the information needed to challenge a decision?
Contractors and agency officials may possess configuration records and test evidence that congressional investigators, frontline workers, and the public cannot readily examine.
Costs fall differently on different actors
Do identical disruptions carry unequal consequences?
A ground stop is a network event for the FAA but can mean lost wages, missed care, travel expense, and cascading operational costs for people with very different resources to absorb them.
Emergency stabilization can become a substitute for redesign
Does an immediate solution reproduce the underlying vulnerability?
If the router workaround is accepted as closure without testing the broader architecture, the program may continue deploying changes into the same unresolved dependency structure.
A threshold-based penalty is not demonstrated
Where does improvement itself trigger a disproportionate loss?
The present evidence does not establish a distinct Cliff mechanism in this incident. The taxonomy should not be forced to classify every possible harm.
Each contract may be legible on its own while the dependency between them remains obscure.
That is the structural risk the incident brings into focus. Responsibility can be distributed across organizations without being reliably integrated at the point where a local technical change becomes a system-wide consequence.
What would verified repair actually require?
Emergency containment ↔ immediate safety
Controllers, pilots, and the FAA’s emergency procedures helped manage the operational consequences and restore service. That capacity deserves recognition as a real part of system resilience.
System governance ↔ durable prevention
The record does not yet show a completed independent root-cause analysis, an assigned cross-contract control owner, validated architectural corrections, or an integrated schedule that captures all relevant dependencies.
The necessary evidence is specific: installation requirements and acceptance criteria, router configuration and change logs, network dependency maps, escalation records, steering-committee decisions, contractor interface provisions, and independent regression testing.
A credible repair process would state which failure mechanism was found, who owned the defective control, what was changed, how the correction was tested, and which independent body accepted the result.
What the public record cannot yet establish?
Exact fault mechanism
The complete network path from the installation sites to the affected en route centers, including segmentation behavior and the source of repeated connection attempts, remains unresolved publicly.
Contractual boundary
The public record does not establish whether the router work was inside Peraton’s integration schedule, exclusively within L3Harris’s legacy maintenance scope, or subject to a separate FAA approval process.
Independent closure
Operational stabilization has been reported, but a published independent verification of permanent architectural repair has not been identified in the material used for this analysis.
The timing of SMART’s nationwide rollout is relevant to oversight of testing and deployment, but temporal proximity does not demonstrate that SMART caused the outage. Likewise, procurement relationships or political contributions are not evidence of corrupt award decisions without records establishing improper influence.
What must Congress and independent auditors establish?
Which exact routing, broadcasting, segmentation, or configuration condition allowed a change at a limited number of sites to affect 17 en route centers?
Who authorized the installations, what test and rollback procedures applied, and were they followed?
Did Peraton’s integration duties cover these router changes, or were they governed solely through L3Harris and FAA legacy-network procedures?
When will all relevant modernization dependencies be represented in a complete, controlled integrated master schedule?
Which projects and risk reductions justify the additional $19.9 billion implied by the public $50 billion demand?
What congressional controls would constrain the requested authority to move funds across accounts?
What independent safety validation and frontline-operator consultation preceded the nationwide SMART rollout?
Who will independently certify that the propagation vulnerability is corrected, and what evidence will that certification require?
The unanswered question is who governed the whole
The November 13 ground stop illustrates a familiar danger in critical infrastructure: operational systems can remain dependent on relationships that procurement and oversight records describe only in fragments. Localized change, vendor-specific responsibility, agency approval, and national consequences belong to one architecture, whether or not the contracts recognize them as such.
The emergency response protected people in the immediate crisis. The next obligation is to demonstrate that the institution can govern the dependencies that made the crisis possible. A completed root-cause investigation, explicit cross-contract authority, integrated planning, and independent verification of repair would make that obligation testable.
Congress can fund modernization without treating urgency as permission to bypass the controls modernization itself requires. The question for the next appropriation is what additional resources will make safer, more accountable, and independently verifiable.
Download
The approved designed PDF accompanies this Applied Research analysis.
PDF download link will appear here once the approved report is uploaded.
How to cite
Methodology
This investigation applies the Answerability Index and Taxonomy of Structural Harm to the technical, institutional, contractual, and budgetary relationships involved in the FAA modernization program.
Provisional Index values: Power 4.0, Access 3.5, Feedback 6.0, Accountability 3.5, Agency 4.5, Care 5.0, Repair 3.0, Adaptation 4.0. These are structural assessments, not an overall safety grade.
The root cause, scope of contractual duties, and permanent repair remain open pending additional records.
Analysis by Melissa Cosgrove for Toward Reconstitution. The Answerability Index™ and Dynamic Fractal Theorem of Relation © 2026 Melissa Cosgrove. Findings distinguish published records, preliminary accounts, and unresolved investigative questions.