“The Burden of Explanation”


*

Beyond Reproach
Ricardo F. Morín. Digital illustration, 2026.

*

Ricardo F. Morín

November 17, 2026

Oakland Park, Florida

*

On November 13, 2026, the Federal Aviation Administration ordered a nationwide ground stop after an interruption of the telecommunications network serving air traffic control facilities.  While aircraft departures were restricted across the country, SpaceX launched Starship Flight 15 from South Texas.  Before the disruption had been fully explained, Transportation Secretary Sean Duffy called upon Congress to provide $50 billion for aviation modernization, enlarging a request formalized in a letter dated November 12 and publicly reported on November 13.  The demand had an earlier history, and it was subsequently specified as a $50.1 billion proposal.  These events belong to different institutional processes.  Their occurrence within the same period nevertheless exposes a common difficulty:  the public has been told what the authorities did, but has not yet been given a sufficiently complete account of how those authorities distinguished among the causes of the emergency, the operations permitted to continue, and the expenditures subsequently demanded.1

The coincidence of events is not proof of a concealed arrangement.  A network failure is not evidence that someone intended to benefit a launch operator, and the continuation of an already planned launch is not evidence that its regulator granted an exception.  But there is a difference between the evidence needed to accuse an official and the evidence the public may require before judging an official decision.  The former must affirmatively connect conduct to an alleged violation.  The latter must disclose the circumstances, criteria, and records by which an exercise of public authority can be examined.  An inquiry that respects the first requirement need not abandon the second.  Its purpose is to prevent uncertainty from serving either as proof of wrongdoing or as an exemption from accountability.

The chronology fixes what can be said about the launch.  SpaceX’s mission had been scheduled before Friday’s disturbance, and the FAA had established a Starship-specific airspace routing constraint early that morning.  The FAA dates the onset of the telecommunications problem to approximately 3:30 p.m.  Eastern; Secretary Duffy described instability apparent at approximately 3:36 p.m.  At 3:54 p.m., FAA Advisory 111 imposed the national ground stop.  At 5:46 p.m., Advisory 119 listed that ground stop and the Starship restriction as concurrently active.  Flight 15 lifted off at approximately 5:47 p.m.  Advisory 121 subsequently canceled the Starship constraint at 6:05 p.m.; normal departures were authorized to resume at approximately 8:15 p.m.  The interval between discovery and the ground-stop order matters because the public inquiry must reconstruct what officials knew, and when, before asking how the launch was evaluated.  The advisories establish the overlap of operations, not the content of the final launch decision.2

A license issued for a commercial-space mission and a judgment about the use of airspace during that mission are related but distinct authorizations.  The former allows an operator to conduct designated activities under prescribed conditions.  The latter requires the responsible aviation authorities to manage hazards and aircraft movements as circumstances develop.  The FAA’s published procedures contemplate advance coordination, designated hazard areas, communications with air traffic facilities, and contingency measures during launch and reentry.  An authorization issued before an emergency does not answer whether all the operational conditions remained satisfied once that emergency began.  The fact that a planned airspace constraint remained active cannot serve as a substitute for a record of the final safety judgment.  3

The FAA’s preliminary technical account gives the national interruption a more definite outline.  According to the agency, the FAA Telecommunications Infrastructure network became unstable when legacy equipment received approximately 1,000 connection attempts every four to five seconds.  Excessive traffic was associated with a communications facility in El Dorado, Arkansas, where contractor L3Harris was replacing equipment, and with a radar site in Amarillo, Texas, where equipment had been replaced approximately three weeks earlier.  Isolating the affected locations stabilized the system, and the FAA disabled broadcasting functionality on roughly 60 comparable routers as a precaution.  The precise initiating fault, including the possibility of installation, configuration, equipment, or interacting-system errors, remained under investigation.  4

The presence of two recently serviced facilities changes the diagnosis.  The failure is not adequately described as the inexplicable breakdown of an old router.  It raises questions about how new or replacement components were introduced into an aging network, what validation preceded their activation, whether an interaction between the two sites was foreseeable, and why abnormal traffic was able to propagate so extensively.  Amarillo’s location in the Texas Panhandle supplies no geographical link to SpaceX’s launch site.  The documented relationship between Amarillo and El Dorado lies in the network and the maintenance history.  A causal connection to Starship would require evidence of an actual shared technical dependency or an operational instruction, neither of which follows from the state’s name.

The interruption reached 17 of the FAA’s 22 en route air traffic control centers and disrupted some radar and communications services, although the entire system did not go dark.  Aircraft already airborne were managed through surviving or alternate capabilities, and officials ordered departures held because the extent and progression of the malfunction were not yet known.  The ground stop was therefore a precaution taken in the face of uncertain system reliability.  Its necessity as an immediate safety measure does not settle the separate question of why a network designed with redundancy could suffer such a broad disturbance from equipment work at remote facilities.  5

At the November 14 briefing, Duffy himself characterized the work at El Dorado as routine maintenance, describing the transfer of communications lines from aging copper to fiber.  FAA Administrator Bryan Bedford separately distinguished sustaining the existing L3Harris-operated network from the Peraton-led effort to construct a broader new air traffic control system.  These descriptions need not conflict.  Replacing copper with fiber is a technological upgrade even when carried out under a legacy-network contract or characterized administratively as sustainment.  The administration reported that more than 68 percent of the copper-to-fiber conversion had been completed by mid-October.  Whether the particular replacement implicated in the outage was financed from sustainment obligations, the 2025 telecommunications-modernization appropriation, or overlapping arrangements requires the contracts, invoices, and agency accounting records.  The administrative label cannot decide the technical cause or the proper funding classification.6, 7

The necessary distinction is therefore among the physical work undertaken, the network architecture within which it occurred, and the appropriations or contracts under which it was paid for.  If the immediate defect arose in installation or configuration, the agency must examine contractor performance, testing, and supervision.  If a local malfunction exposed an inability to contain abnormal traffic across the national network, the inquiry must also examine resilience and system design.  Both conditions may coexist.  Duffy’s case for constructing a new architecture may be technically defensible, but it does not settle whether adequate safeguards should have prevented this particular failure or which funded work was responsible for them.  That determination is necessary before the incident can be assigned to an existing contractual failure, a broader design deficiency, or both.

The question of testing has now become the subject of a documented challenge from Democratic members of the Senate Commerce Committee.  In a letter dated November 16 and published November 17, those senators reported information supplied to them by L3Harris that the copper-to-fiber conversion contemplated 3,648 Juniper routers, of which approximately 400 had been installed and 69 were operational.  They acknowledged that a sample passed FAA predeployment testing, but questioned whether those tests represented actual operating conditions and requested independent validation of failover, rollback, and recovery procedures before further deployment.  The FAA separately confirmed that it had paused new Juniper installations and disabled a function of existing units while investigators examined the failure, temporarily relying on older equipment.  Hewlett Packard Enterprise, Juniper’s parent company, maintained that the router operated as configured by the installer and did not itself fail.  That is the manufacturer’s account, not an established determination of root cause.  It places the approved configuration, installation, testing, and interaction with the existing network among the necessary subjects of inquiry without demonstrating that the installer made an error.  The senators’ letter is a formal request for answers by committee minority members, not an investigation authorized by the committee as a whole.8, 9

The distinction is equally necessary when considering the Starship launch.  The national order did not mean that every aviation function was unavailable.  But an operational exception cannot be inferred merely from that fact.  Which communications circuits and air traffic facilities were used to protect aircraft from the Starship flight corridor?  Were any of them affected by the FAA Telecommunications Infrastructure instability?  Did the agency’s Space Data Integrator, launch telemetry, notification arrangements, and contingency communications remain serviceable?  Who confirmed their readiness after the ground stop began, and did officials consider postponement?  These questions can be answered only through mission-specific coordination records and contemporaneous decisions.  10

The existence of a backup launch opportunity the following day makes postponement an identifiable alternative rather than an imaginary one.  A delay would have had possible consequences for SpaceX’s preparations, personnel, weather, and the availability of restricted airspace.  Proceeding also had consequences for aviation already recovering from a national interruption.  Neither consideration determines the correct decision by itself.  The issue is whether the responsible officials assessed the alternatives under the safety rules applicable to the mission, and whether those rules adequately addressed an emergency affecting much of the aviation system.

A documented consequence of the launch gives this inquiry greater specificity.  The Hawaiʻi Department of Transportation reported at 1:55 p.m.  local time, or 6:55 p.m.  Eastern, that flights between Hawaiʻi and the West Coast had again been halted because of debris associated with the SpaceX launch.  The announcement followed an earlier partial resumption of those flights.  The restriction was subsequent to liftoff and separate in its stated cause from the telecommunications malfunction.  It nevertheless imposed another aviation constraint during the recovery from that malfunction.  An FAA environmental decision of August 31 had already addressed expanded Pacific landing and contingency areas for Starship, but the public materials examined do not establish whether the November 13 restriction was a planned contingency, a precaution, or a response to an unexpected condition.  11

That record creates a question about the decision not to postpone.  A later launch might have required a similar Pacific restriction, so postponement cannot simply be presented as a way of avoiding the hazard altogether.  But delaying Flight 15 would have avoided imposing this particular restriction at that particular moment upon a system already under exceptional pressure.  Did the decision-makers consider that cumulative effect?  Were Pacific facilities or their communications affected by the earlier outage?  What information about possible debris or reentry contingencies reached the authorities who directed the subsequent halt?  The matters are operationally connected through the consequences of proceeding, even though the two interruptions need not have shared a technical cause.

SpaceX’s commercial interest in the launch is clear without embellishment.  Flight 15 deployed 26 Starlink V3 satellites and demonstrated the successful recovery of Starship’s upper stage at Starbase on November 14.  The Super Heavy booster did not complete its intended tower catch; it was redirected toward the Gulf of Mexico and exploded shortly before reaching the water.  These achievements belonged to a mission planned before the ground stop.  Whether the interruption conferred a distinct advantage requires a different comparison:  did reduced aircraft traffic change a clearance, shorten a delay, relax a requirement, or otherwise alter the conditions under which Flight 15 proceeded?  That comparison depends on the contemporaneous aviation and launch-coordination records, not on the fact of the mission’s success.12

SpaceX had, however, another documented relationship with the FAA beyond its status as a regulated launch operator.  In February 2025, Duffy announced that SpaceX engineers would visit FAA facilities to examine the existing air traffic control system and possible improvements.  In March, the FAA acknowledged trials of Starlink terminals at non-safety-critical sites in Alaska and tests involving Starlink and other communications technologies at facilities in Oklahoma City and Atlantic City.  The FAA said the tests were conducted through its Telecommunications Infrastructure program, administered under the L3Harris contract.  SpaceX publicly confirmed that it was working with L3Harris and the FAA to identify circumstances in which Starlink could serve as a long-term infrastructure upgrade for aviation safety.  A possible future commercial role was therefore stated by the company itself, rather than merely inferred from the trials.13

The overlapping relationships had already prompted congressional scrutiny.  Senator Edward Markey questioned the procurement process, the possible involvement of SpaceX personnel, and protections against conflicts of interest.  In July 2025, Bedford told lawmakers that the FAA was not contemplating replacing its L3Harris or Verizon telecommunications contracts with SpaceX and would not rely on Starlink alone for safety-critical air traffic services.  Those assurances concerned the agency’s position at that time, while the technology evaluation and SpaceX’s expressed interest concerned possible future uses.  The inquiry should therefore identify any later trial agreement, procurement evaluation, technical access, or award, and determine which safeguards governed decisions involving a company that was also subject to the FAA’s launch regulation.14

The demand for additional funding did not begin on November 13.  On September 21, a failure of a primary communications circuit affecting Northeastern air traffic coincided with damage to a backup fiber line, disrupting flights through several major airports.  The following day Duffy announced that he would seek approximately $30 billion for aviation infrastructure and air traffic control improvements.  On September 28 he publicly supported the proposed Modern Skies Act, which combined new spending with authority to move money among specified purposes.  The September event and the November ground stop had different known technical circumstances.  What links them in the public record is the administration’s recurring argument for replacing the telecommunications architecture, and the resulting need to distinguish a funded repair program from additional reconstruction.15

The public financial consequences of the November failure developed quickly.  Duffy and White House budget director Russ Vought signed a formal request for $30.1 billion on November 12, reported publicly on November 13.  It proposed $10.1 billion for air traffic control digital modernization, $2 billion for FAA-owned control towers, and $18 billion for airport and terminal programs.  By Friday evening, following the ground stop, Duffy advocated $50 billion.  On November 17, the Department of Transportation published a $50.1 billion proposal allocating $10.1 billion to digital architecture and $10 billion each to airport infrastructure, terminals, consolidated en route control centers, and control towers.  At the level of the published categories, the digital-architecture amount remained $10.1 billion; the $20 billion increase consisted of $8 billion more for towers, $10 billion for five consolidated en route centers, and a net $2 billion more for airport and terminal purposes.  The added amount was not assigned to the digital-architecture line most directly associated with the failed telecommunications network.  Yet the network instability reached 17 of 22 en route control centers, and the Republican-led Senate Commerce Committee argued that their modernization should take priority over other projects.  The committee did not specify whether control towers, which also perform essential aviation safety functions, fell within that comparison.  The administration must therefore explain how it determined the order of priority among the proposed expenditures in light of the vulnerabilities revealed by the emergency.  The spending request thus invokes two different relationships to the failure:  a technical cause within telecommunications infrastructure and the widespread consequences for the centers that depend on it.  The justification for new facilities must show how the proposed construction would address the second problem and how it relates to correcting the first.16, 17

The administration’s financial account invites confusion because several kinds of money and several kinds of work are repeatedly treated as though they formed one undifferentiated total.  In May 2025, Duffy had already announced a modernization plan calling for six new air traffic control centers.  Congress provided $12.5 billion for air traffic control improvements in July 2025, including $4.75 billion for telecommunications modernization and systems upgrades and, separately within that same $12.5 billion, $1.9 billion for construction of one new en route air traffic control center.  The November 17 proposal seeks $10 billion for five consolidated centers.  One center previously funded and five newly proposed correspond numerically to the earlier six-center objective, suggesting continuity in a program conceived before the November emergency.  The published summaries do not yet establish that the later five are precisely the remaining projects originally contemplated, with identical sites, technical scopes, or purposes.  A different $1.9 billion was provided through the February 2026 transportation appropriations law, bringing the recent combined funding described by congressional appropriators to approximately $14.4 billion; that additional appropriation must not be mistaken for the center allocation within the July 2025 package.  The existing copper-to-fiber work has meanwhile been described as sustainment of the legacy network even as its physical purpose involves installing newer technology.  These overlapping descriptions make a precise reconciliation of the preexisting plan, contractual scope, earmarks, obligations, available balances, and proposed construction essential.18

On November 16, PBS NewsHour reported an additional complication:  congressional records showed that the White House Office of Management and Budget had held more than $5 billion of previously appropriated modernization funding for availability in a later fiscal period, beginning October 1, 2027.  Congressional Democrats pointed to approximately $9 billion that remained unspent.  These descriptions are not identical.  Appropriated money may be legally unavailable for immediate obligation, obligated but not yet disbursed, assigned to future procurements, or legally restricted to a specified purpose.  A meaningful accounting must state which condition applies to each amount.  Without such reconciliation, the contrast between money supposedly withheld by Congress and money already provided but not yet used becomes a political argument rather than a financial explanation.  19

Duffy maintains that existing appropriations are committed to equipment and projects such as radars, radios, and other components, leaving insufficient authority or funding for a new telecommunications architecture and software for managing aircraft.  Existing restrictions may indeed prevent a transfer between appropriations categories without legislative authorization.  Yet the Modern Skies Act, introduced on September 28 as S.  5572, directly addresses that question.  Section 4 would allow transfers among categories of its proposed new air traffic control funding and require quarterly spending reports; Section 5 would authorize transfers among categories in the 2025 modernization appropriation, with reporting.  Those powers had been proposed, not enacted.  Their existence nevertheless makes it necessary to compare three distinct remedies:  obtaining new appropriations, changing the permissible uses of existing funds, and correcting the management or sequencing of projects already funded.  None can be judged by the headline size of the request alone.20, 21

The administration’s public account was organized around inherited deficiencies and a promise of decisive reconstruction before the technical investigation was complete.  On November 13, the White House presented the emergency as evidence that President Trump had begun to rebuild an antiquated system but required Congress to provide the remaining funds.  22  Two days later, Duffy acknowledged that the interruption had occurred on his watch while emphasizing the failures of previous administrations and the pace of his own modernization effort.  Trump separately blamed the Biden administration for worsening the inherited system.  23 These statements establish how credit and responsibility were publicly assigned.  They do not establish an intention to evade accountability, nor do they resolve whether the government’s present decisions about engineering, funding, and personnel were adequately justified.

The most serious evidence of deficient coordination predates the emergency.  In September, the Government Accountability Office reported that the FAA’s accelerated modernization effort lacked a comprehensive, well-supported lifecycle cost estimate.  It also lacked an integrated master schedule:  11,389 individual projects were proceeding without the coordination needed to manage dependencies and installations at common sites.  Some projects could return repeatedly to the same facilities without optimizing the sequence of work or minimizing disruptions to controllers.  The GAO did not contend that modernization was unnecessary.  It warned that the drive for speed, without adequate cost and schedule discipline, could increase the risks of delays, overruns, and operational disturbance.  24

The GAO’s findings do not establish that the November 13 event arose from one of the projects reviewed in the accelerated reconstruction program.  The agency classified the failed work as part of the continuing legacy-network transition, although that transition also involves new technology and modernization expenditures.  The subsequent request by Democratic members of the Senate Commerce Committee for independent testing, verified failover, and rollback procedures adds a different form of scrutiny:  whether the ongoing network conversion was protected against operational failure while new components were introduced.  The GAO establishes a separate institutional condition, that an ambitious reconstruction was proceeding without an integrated project schedule or a reliable estimate of total lifecycle costs.  Together, these inquiries require the administration to explain how it will coordinate installations, protect live aviation operations, supervise contractors, and account for money already authorized.  Larger sums and faster procurement do not themselves supply those controls.

The administration’s treatment of personnel introduces another contradiction into the diagnosis.  During the DOGE-driven reductions in February 2025, approximately 400 probationary FAA employees were dismissed.  The administration said controllers and critical safety positions were protected, but reporting identified technical and supporting functions among the affected jobs.  In congressional testimony that June, acting FAA Administrator Chris Rocheleau said approximately 360 of those employees had returned following litigation.  The initial dismissals, their reversal, and the uncertainty they introduced into technical staffing belong to the institutional history of the modernization effort, even though their relation to the November 2026 network failure has not been established.  25

An engineering program cannot be evaluated solely by its procurement budget.  It also depends on people capable of defining system requirements, testing interactions, supervising installations, preserving technical knowledge, and determining when a new component may safely be introduced into service.  How did the workforce reductions affect those capabilities?  Which technical vacancies, if any, remained, and which departures followed the dismissals or deferred-resignation initiatives?  Was the agency’s own engineering capacity sufficient to challenge contractor assumptions and evaluate the 11,389 projects identified by the GAO?  PBS aviation correspondent Miles O’Brien specifically raised the degradation of institutional systems-engineering expertise alongside the DOGE cuts.  His assessment requires examination of staffing and project records; the reported cuts themselves do not establish that they caused the router malfunction.  26

The tension between this public explanation and the administration’s decisions is institutional rather than merely rhetorical.  The explanation emphasizes an inherited network and insufficient funding, while the administration has accelerated modernization without the integrated planning identified as necessary by the GAO, reduced portions of its technical workforce before partially restoring them, and issued successive funding demands whose differing budget categories have not been reconciled.  The vulnerabilities of the inherited network are genuine, and each policy decision may have its own justification.  The public account, however, allocates responsibility among predecessors, Congress, and the present administration before providing a complete administrative account of what was done under present authority.  The question is not what officials privately intended by that presentation, but whether the decisions together formed a strategy attentive to their cumulative consequences.

The separation of the participating companies is essential to the inquiry.  L3Harris operates the legacy telecommunications network implicated in the outage; Peraton is prime systems integrator for the newer modernization initiative.  SpaceX participated in engineering discussions and technology trials, including Starlink tests conducted within the L3Harris-managed program, and publicly identified potential long-term uses for its technology.  The November 17 digital-architecture proposal names no eventual suppliers.  The testing relationship therefore establishes neither an award under that proposal nor the exclusion of SpaceX from a possible future commercial benefit.  The relevant records concern contracts, trial agreements, technical access, procurement safeguards, testing obligations, and any resulting awards.  Responsibility for an installation failure by one contractor must be examined on its own terms, while any decision to purchase, reject, or continue testing another supplier’s technology must be assessed on its documented grounds.27

These matters may yield different findings rather than one account encompassing every event.  The network malfunction may have originated in equipment configuration, contractor maintenance, or weaknesses in the inherited architecture.  The modernization effort may have suffered from inadequate planning and financial control.  The nationwide ground stop may have been justified while questions remain about the launch’s contemporaneous airspace coordination.  Yet separating these questions does not mean that the institutions responsible for them were independent.  The FAA regulated SpaceX’s launch and also evaluated communications technologies supplied by the company; the FAA’s technical staff worked within contractual systems operated by L3Harris while the department pursued a Peraton-led reconstruction; Congress and the Office of Management and Budget affected the funding available to each effort.  Their responsibilities differ, but their decisions may interact.  The inquiry concerns where those interactions were documented, anticipated, and governed, rather than whether their concurrence proves a single concealed design.

A distinction within the executive branch makes the problem more visible.  On November 16, President Trump told reporters that he took no responsibility for the nationwide ground stop, praised Secretary Duffy’s response, and attributed responsibility to decades of neglected infrastructure.  He also suggested that the emergency might help secure the requested congressional funding.  His statements establish a public allocation of responsibility; they do not establish why the network failed or what individual officials privately intended.  The president is not the air traffic controller who ordered a ground stop, the engineer who certified a router, or the regulator who assessed a space launch.  But the administration’s policies on funding, staffing, procurement, and modernization are not external to the operation of the departments that carry them out.  The distinction between political authority and individual operational responsibility cannot be used either to assign the president a technical decision he did not make or to exempt executive policy from examination when its consequences become apparent.  28

The funding dispute demonstrates why an account confined to the responsibility of one office would be incomplete.  Congress appropriates money and may restrict its use.  The Office of Management and Budget affects when appropriated funds become available.  The Department of Transportation proposes additional expenditures and supervises the FAA, while the FAA defines technical requirements and oversees contractors.  The September Modern Skies Act also placed before Congress a means of changing some restrictions on the movement of funds.  An agency may need resources for one new project while having money obligated to another; a contractor may fail in installation even when the relevant account is adequately funded.  Each proposition may be true.  The administration must nevertheless reconcile available balances, legal restrictions, proposed transfer authority, projects and their dependencies, and the reasons for seeking still larger sums.  A total budget figure cannot answer which decisions were available and why those decisions were made.

The same demand for an account across institutional boundaries applies to November 13 itself.  A technical investigation should identify the initiating failure mechanism and the safeguards expected to contain it; the Senate Commerce Democrats’ November 16 letter and the FAA’s reported pause in router installations provide concrete tests of whether initial validation, redundancy, and recovery procedures were sufficient.  An operational investigation should reconstruct the interval between the first observed instability and the ground-stop order, who assessed the capabilities required for Flight 15, which communications remained available, and how the later Hawaiʻi restrictions were evaluated amid the recovery of ordinary aviation.  A financial inquiry should distinguish sustaining the older network, replacing components within it, and constructing a new architecture, while following the appropriations and contracts that may fund overlapping physical work.  The inquiry must also identify what SpaceX’s separate technology-testing relationship did and did not involve.  Only then can findings about engineering supervision, procurement, executive funding policy, and overlapping aviation operations be compared under the responsibilities of the institutions that governed them.

That comparison may produce findings of compliance and findings of deficiency at the same time.  The FAA could establish that Flight 15 satisfied every applicable launch requirement without resolving whether the ground stop incidentally reduced air traffic conflicts.  A technical investigation could identify the router or configuration failure while leaving open why the wider network permitted such extensive disruption.  Congress could determine that additional modernization funds are necessary while finding the administration’s proposed amount unsupported by an integrated cost estimate.  The fact that the presidential, departmental, regulatory, and contractual accounts do not converge on a single conclusion would not make them worthless.  It would make their differences important, since those differences could identify where responsibilities were fulfilled, where coordination failed, or where available records cannot settle the matter.

The limits of knowledge must also be assigned to their proper causes.  Some uncertainty is technical, arising because interacting failures cannot be reconstructed with complete precision.  Some is evidentiary, because the decisions made during the countdown or the emergency may not have been adequately recorded or disclosed.  Some is counterfactual:  no investigation can directly observe the aviation conditions that would have prevailed had the launch been postponed or the equipment replacement undertaken on another day.  A further uncertainty arises when officials offer separate, defensible explanations that do not address their common effects.  That last uncertainty cannot be resolved by demanding certainty about motives.  It requires examining whether the authority responsible for coordinating public policy has provided the means to reconcile the actions carried out under that authority.  An explanation of each event in isolation is not necessarily an explanation of the administration’s response to the events together.

The November 13 emergency may ultimately prove to have originated in an ordinary technical failure aggravated by an aging network.  Flight 15 may have proceeded in full compliance with every applicable safety requirement.  Additional federal investment may be justified even if the amount requested and the management of existing appropriations require correction.  Such findings would not invalidate the inquiry; they would show why a diagnosis must be able to distinguish among causes, decisions, and consequences.  A government cannot satisfy its obligation to explain by distributing each question to a different office while leaving their interdependence unexamined.  Nor does a failure to explain that interdependence prove an undisclosed bargain or corrupt intention.  The burden is to establish what each authority knew and decided, how the authorities’ responsibilities met, and what the surviving evidence allows the public to judge.  Where evidence permits a finding, the finding should be made.  Where a question cannot be answered, the precise reason for that limit should be stated.  And where the decisive records remain with those who exercised the authority, the burden of making those decisions intelligible remains with them.

Documentary endnotes

Source titles below are direct, visible hyperlinks to the cited documents or reporting. Each numbered note corresponds to a reference in the essay.

  1. Sources: FAA — “Nationwide Ground Stop: Questions and Answers” (15 Nov. 2026); Roll Call — Aviation funding after the halt (13 Nov. 2026); DOT — Formal $50.1 billion proposal (17 Nov. 2026).The FAA documents the nationwide stop; Roll Call reports the enlarged funding demand; DOT sets out the later itemized proposal.Return to reference ↩
  2. Sources: FAA — ATCSCC Advisory 111 (13 Nov. 2026); FAA — ATCSCC Advisory 119 (13 Nov. 2026, 5:46 p.m. ET); FAA — ATCSCC Advisory 121 (13 Nov. 2026); FAA — Technical chronology (15 Nov. 2026); Spaceflight Now — Flight 15 launch chronology (13–14 Nov. 2026).Advisory 119 concurrently identifies the ground stop and FCA001:STARSHIP_WEST; the operational advisories do not disclose the final launch go/no-go deliberations.  The FAA places the first technical difficulties at about 3:30 p.m.  ET, while Duffy described instability at approximately 3:36 p.m.Return to reference ↩
  3. Sources: FAA — “Airspace Integration”; FAA — “Space Data Integrator” (4 Aug. 2025).These sources explain the general division of launch licensing, hazard-area coordination, communications, telemetry, and airspace management.  They do not document the specific Flight 15 decision during the outage.Return to reference ↩
  4. Sources: DOT — Secretary Duffy’s interviews and technical update (15 Nov. 2026); FAA — Preliminary technical Q&A (15 Nov. 2026); CBS News — Duffy interview transcript (15 Nov. 2026).These accounts identify recent equipment work in El Dorado and Amarillo and the resulting network instability.  The initiating fault remained under investigation as of the documentary cutoff.Return to reference ↩
  5. Sources: FAA — “Nationwide Ground Stop: Questions and Answers” (15 Nov. 2026).The agency reports instability at 17 of 22 en route centers, surviving communications capabilities, and the precautionary management of air traffic.Return to reference ↩
  6. Sources: DOT — Duffy and Bedford restoration briefing (14 Nov. 2026); ABC News — “This Week” interview transcript (15 Nov. 2026).Duffy described the copper-to-fiber conversion as routine maintenance; Bedford distinguished sustaining the existing L3Harris network from the Peraton-led reconstruction.  Neither explanation identifies the particular funding account used for the El Dorado installation.Return to reference ↩
  7. Sources: Roll Call — “Aviation funding becomes political football” (16 Nov. 2026); DOT — Duffy and Bedford briefing (14 Nov. 2026).Copper-to-fiber conversion was an upgrade performed within the legacy-network arrangement.  The administration reported that more than 68 percent of copper conversion was complete by mid-October; the cited public descriptions do not resolve the cost classification of the implicated work.Return to reference ↩
  8. Sources: Senate Commerce Committee Democrats — Press release and letter dated 16 Nov. (published 17 Nov. 2026).The minority members attribute the counts of planned, installed, and operating routers to L3Harris; they question whether predeployment tests reflected operating conditions and request independent validation, failover, and rollback procedures.  The letter is an official oversight challenge, not a completed technical finding or a committee-wide investigation.Return to reference ↩
  9. Sources: Associated Press — FAA pauses router installations (17 Nov. 2026); CNN — FAA pause and network safeguards (17 Nov. 2026); ABC News — HPE statement on router configuration (16–17 Nov. 2026).The FAA reported pausing installations and disabling a function on installed Juniper devices.  HPE said its device operated in accordance with the installer’s configuration.  That account does not determine who authorized the configuration or identify the network-wide initiating cause.Return to reference ↩
  10. Sources: FAA — “Airspace Integration”; FAA — ATCSCC Advisory 119 (13 Nov. 2026).These records establish general spaceflight coordination requirements and the contemporaneous airspace restriction, but not the specific operational readiness review for Flight 15.Return to reference ↩
  11. Sources: Hawaii News Now — Hawaiʻi DOT notice (13 Nov. 2026); FAA — Starship Pacific reentry contingency environmental decision (31 Aug. 2026).The state reported the later Hawaiʻi–West Coast restriction; FAA’s earlier decision supplies the Pacific contingency-planning context.  Neither document alone identifies whether the November 13 restriction was preplanned or newly triggered.Return to reference ↩
  12. Sources: SpaceX — Starship Flight 15 mission page; Spaceflight Now — Launch and upper-stage recovery (13–14 Nov. 2026); CBS News — Flight 15 booster account (13 Nov. 2026).Mission records and contemporary reporting cover the 26 Starlink satellites, the upper-stage tower catch, and the aborted booster recovery ending in an explosion over the Gulf of Mexico.  Mission outcome is not evidence of benefit from the national ground stop.Return to reference ↩
  13. Sources: FAA — Statement on Starlink trials (5 Mar. 2025); Reuters — SpaceX statement on existing FAA contracts (5 Mar. 2025); The Washington Post — Starlink and FAA telecommunications trials (6 Mar. 2025).The FAA described the trial sites and the L3Harris-managed FTI program.  SpaceX stated its interest in identifying longer-term Starlink infrastructure uses while denying plans to take over an existing contract.  Interest and testing are not procurement awards.Return to reference ↩
  14. Sources: Senator Edward Markey — Letter concerning Starlink and FAA safeguards (26 Feb. 2025); Reuters — Bedford’s response on L3Harris and Verizon contracts (16 July 2025).Markey requested procurement and ethics information.  Bedford said that the FAA was not considering substituting SpaceX for the identified contracts or depending on Starlink alone for safety-critical services.  These were the agency’s positions at the cited dates.Return to reference ↩
  15. Sources: ABC News — Northeastern communications disruption (21 Sept. 2026); Reuters — Duffy seeks another $30 billion (22 Sept. 2026); DOT — Modern Skies Act endorsement (28 Sept. 2026).The September episode involved a failed primary circuit and a damaged backup line.  Duffy’s renewed funding campaign preceded the November nationwide ground stop.Return to reference ↩
  16. Sources: Duffy and Vought — Budget request letter (12 Nov. 2026); Roll Call — Public report of the request (13 Nov. 2026).The letter requests $30.1 billion: $10.1 billion for air traffic control modernization, $2 billion for control towers, and $18 billion across airport and terminal programs.  The letter is dated November 12 and was reported November 13.Return to reference ↩
  17. Sources: DOT — Itemized $50.1 billion proposal (17 Nov. 2026); Duffy and Vought — Original $30.1 billion request (12 Nov. 2026); Reuters — Senate Commerce Republicans’ response (13–14 Nov. 2026).At the broad-category level, digital architecture remained $10.1 billion; towers increased from $2 billion to $10 billion, combined airports and terminals from $18 billion to $20 billion, and five consolidated en route centers received a proposed $10 billion category.  The Republican-led Senate Commerce Committee urged prioritizing en route centers over other projects but did not specify whether towers were included in that comparison.Return to reference ↩
  18. Sources: Public Law 119-21, §40003(a) (July 2025); Roll Call — Appropriations analysis (16 Nov. 2026); House Appropriations Democrats — Ground-stop funding timeline (Nov. 2026); DOT — Six-center modernization plan (8 May 2025).The July 2025 law includes $1.9 billion for one new en route center within its $12.5 billion package.  Congressional appropriators identify a separate $1.9 billion in the February 2026 spending law.  The earlier six-center goal, one funded center, and five newly proposed centers suggest continuity without proving identical sites or specifications.Return to reference ↩
  19. Sources: PBS NewsHour — Lisa Desjardins and Miles O’Brien on FAA funding (16 Nov. 2026); Roll Call — Peter Cohn, “Aviation funding becomes political football in lame-duck session” (16 Nov. 2026).PBS reported that the White House Office of Management and Budget had delayed access to approximately $5 billion in previously appropriated FAA modernization funding.  Roll Call, citing a fact sheet issued by Representatives Rosa DeLauro and James Clyburn, reported that an OMB apportionment held more than $5 billion of the July 2025 appropriation until October 1, 2027.  The underlying OMB apportionment was not independently examined for this essay.  “Unspent,” “unobligated,” and “deferred” refer to different financial conditions.Return to reference ↩
  20. Sources: DOT — Duffy’s November 15 statements on modernization funding; Modern Skies Act, S. 5572, §§4–5 (introduced 28 Sept. 2026).Duffy distinguished already designated equipment expenditure from proposed software and new architecture.  The introduced bill addresses additional appropriations and proposed transfer authority, rather than transfer authority already enacted.Return to reference ↩
  21. Sources: Modern Skies Act — Introduced legislative text, S. 5572, §§4–5; DOT — Description of proposed transfer authority (28 Sept. 2026).The bill proposes transfers among specified categories of new funding and prior modernization appropriations, with reporting requirements.  It does not itself confer enacted transfer authority.Return to reference ↩
  22. Sources: White House — “After Nationwide Ground Stop, Trump Administration Prioritizes Safety…” (13 Nov. 2026).The White House links the emergency to inherited equipment deficiencies and calls for rebuilding funding.  The statement is a political and administrative explanation, not a completed root-cause finding.Return to reference ↩
  23. Sources: Associated Press — Trump’s comments on responsibility (16 Nov. 2026); The Washington Post — Duffy’s public defense of the response (15 Nov. 2026); The Washington Post — Trump’s comments about inherited FAA problems (15 Nov. 2026).The reports document public explanations and allocations of responsibility.  They do not establish undisclosed personal motives or the technical cause of the outage.Return to reference ↩
  24. Sources: GAO — Air Traffic Control Modernization, GAO-26-107992 (14 Sept. 2026).GAO describes problems with the comprehensive lifecycle cost estimate and the lack of integration across 11,389 individual project schedules.  The report concerns modernization planning, not the subsequent November 13 incident investigation.Return to reference ↩
  25. Sources: Associated Press — FAA probationary employee dismissals (Feb. 2025); House Appropriations Subcommittee — FAA budget hearing, Rocheleau oral testimony and recording (4 June 2025; about 1:03:23).Associated Press reported probationary dismissals affecting FAA technical and supporting functions in February 2025.  During oral questioning before the House Appropriations Subcommittee on Transportation, Housing and Urban Development on June 4, 2025 (at approximately 1:03:23 in the recording), Acting FAA Administrator Chris Rocheleau stated that approximately 400 probationary employees had been terminated and that 360 had returned to the FAA following a court case.  Neither the dismissals nor the subsequent return of employees establishes a causal relationship to the November 2026 network failure.Return to reference ↩
  26. Sources: PBS NewsHour — Miles O’Brien and Lisa Desjardins (16 Nov. 2026).O’Brien’s assessment of systems-engineering capacity and DOGE-era personnel reductions is reported expert analysis, not a completed causal investigation of the router failure.Return to reference ↩
  27. Sources: DOT — Peraton prime systems integrator announcement (Dec. 2025); FAA — Statement on Starlink trials (5 Mar. 2025); DOT — November 17 digital-architecture funding category.The records describe separate roles for L3Harris, Peraton, and SpaceX.  The proposed $10.1 billion digital-architecture category does not identify eventual vendors or recipients.Return to reference ↩
  28. Sources: Associated Press — Trump’s November 16 statements; Public remarks transcript — November 16, 2026.The president publicly denied personal responsibility, praised Duffy’s response, and attributed infrastructure problems to earlier neglect.  These statements document public positions, not private motives or a technical finding.Return to reference ↩

Tags: , , , , , , , ,

PLease leave a Reply