The Documentation Hostage

 

Why Prime Contractors Withhold Technical Data

What Fifty Years of Failed Reform Tell Us About the Lunar Base

AEROSPACE & DEFENSE INDUSTRY ANALYSIS / PROCUREMENT POLICY

By Pseudo Publius   |   Aerospace & Defense Procurement Analysis   |   25 April 2026

Companion piece to “The Apollo Knowledge Trap” (Pseudo Publius, 25 April 2026)

 BLUF — BOTTOM LINE UP FRONT

The institutional knowledge problem documented in the companion piece is not solely a function of retired craftsmen and lost notebooks. It is structurally aggravated by a procurement dynamic that has persisted across five decades: prime contractors deliver technical data packages that meet the letter of contract requirements while withholding the manufacturing and process knowledge that would permit second-source production or organic government repair. The Government Accountability Office documented this pattern again in September 2025 across the F-35, F/A-18, Littoral Combat Ship, Stryker, and Virginia-class Submarine programs, finding that all five face vendor lock and that DoD lacks the policy framework to plan adequately for sustainment data rights. The Federal Trade Commission's January 2025 antitrust suit against John Deere — joined by five state attorneys general and now followed by a $99 million class-action settlement in April 2026 — demonstrates that the same business model operates in commercial agriculture, consumer electronics, and medical equipment. The FY 2026 National Defense Authorization Act, signed December 2025, dropped the right-to-repair provisions both chambers had initially passed and substituted a data-rights inventory requirement. For a sustained lunar architecture being built right now under the same procurement dynamics, the implications are unambiguous: without structural reform of how the government acquires manufacturing-process data, the next generation of programs will repeat the F-1 and Avcoat capability losses with industrial efficiency.

The Univac Pattern, Documented

In the 1970s and 1980s, NAVSEA technical representatives watched Univac — later Sperry, then Unisys — defend its monopoly on the Navy's standard tactical computer line through a combination of contract compliance and documentation insufficiency. The AN/UYK-7 and successor AN/UYK-43, which formed the computational backbone of the Naval Tactical Data System and early Aegis configurations, were produced under contracts that required technical data deliverables. The data was delivered. The data was insufficient for second-source manufacturing. Critical timing diagrams were omitted. Test procedures referenced proprietary test equipment. Component selection rationales went undocumented. The Navy's repeated attempts to develop the AN/UYK-44 as a competitive alternative, and the eventual transition to commercial off-the-shelf computing in the 1990s, both encountered systematic contractor resistance that took the form of compliance with the letter while withholding the spirit of the data rights clauses.

This pattern was not unique to Univac and was not a Cold War aberration. It was — and remains — the dominant business model among major defense prime contractors. The economic logic is unchanged across five decades: prime contractors bid hardware development at thin margins or losses to win the program, then capture the actual profit through sustainment over the operational life of the system. For a Navy ship class with a 40-year service life, sustainment revenue typically exceeds initial procurement revenue by a factor of three to five. Maintaining that sustainment monopoly requires controlling the technical data, and the marginal cost of obfuscating documentation is trivial relative to the revenue that obfuscation preserves.

GAO-25-107468: Five Programs, One Pattern

The Government Accountability Office's September 2025 report on weapon system sustainment, GAO-25-107468, examined five major programs in detail: the F-35 Joint Strike Fighter, the F/A-18 Super Hornet, the Littoral Combat Ship, the Stryker Combat Vehicle, and the Virginia-class submarine. The findings constitute the most comprehensive contemporary documentation of the pattern your generation of NAVSEA representatives identified in the 1970s, and they are damning.

All five selected programs experienced what GAO terms "vendor lock" — reliance on a single supplier driven by data-rights shortfalls. According to officials interviewed, this approach drives up costs and lengthens repair timeframes. Once a program enters sustainment without adequate data rights, the options to address vendor lock are extremely limited. The structural mistake is made early in the acquisition cycle and compounds across the operational life.

The F-35 case is particularly instructive. GAO had reported in 2014 that the F-35 program lacked an intellectual property strategy. The program did not release its IP strategy until July 2025 — eleven years later. By that point, the program had accumulated a sustainment cost trajectory that GAO has separately characterized as requiring billions in cuts to achieve affordability. The relationship between data-rights inadequacy and sustainment cost is direct: when the government cannot compete sustainment work, the prime sets the price.

The Littoral Combat Ship case illustrates the operational consequence in stark terms. GAO documented an instance in which Navy maintainers attempted to leverage a Master Ship Repair Agreement contractor — a private firm with general ship-repair expertise — to replace a broken hydraulic motor in a crane on an LCS. The MSRA contractor would not complete the repair without the Original Equipment Manufacturer present. The maintainers waited two and a half weeks for the OEM to be available, which shipyard officials characterized as a fast turnaround. When repairs are sequenced through the OEM, ships compete on a first-come-first-served basis with no ability to redirect contract work based on operational priority. The LCS absorbed the delay because the data rights structure left the Navy no alternative.

The Stryker case is the most candid admission in the report. According to program officials, the Army has tried unsuccessfully over time to acquire unlimited data rights for the base vehicle. As a result, in 2024, the Army established a technical support contract with the prime contractor — institutionalizing the contractor lock-in rather than overcoming it. After more than two decades of fielding and multiple reform attempts, the Army gave up trying to break the data-rights monopoly and contracted around it instead.

"All five selected programs experienced vendor lock — reliance on a single supplier — due to data rights shortfalls."

The Statutory Loophole

GAO identifies a specific statutory gap that Congress could close but has not. Federal statute affords DoD unlimited rights in operation, maintenance, installation, and training (OMIT) data. However, the same statute excludes detailed manufacturing or process data from the OMIT category. This is the loophole through which sustainment monopolies persist.

In practical terms: the Navy is entitled to the technical data needed to operate, maintain, install, and train on Aegis. The Navy is not entitled, by statute, to the detailed manufacturing data needed to actually fabricate Aegis components or to compete production with a second source. The contractor delivers the OMIT data and withholds the manufacturing process data, and the contractor is fully within statutory and contractual rights. The result is exactly the institutional outcome the companion piece documented at NASA: the artifacts can be operated and maintained at the surface level, but the underlying manufacturing capability remains the contractor's proprietary asset.

GAO's recommendation in the September 2025 report is that Congress clarify the treatment of detailed manufacturing or process data needed for OMIT — broadening the government's statutory entitlement so that personnel can make repairs themselves or compete maintenance work to different vendors. The recommendation has been on the table, in various forms, for decades. It has not been adopted because the contractor lobbying against it is sustained and well-organized, and the political constituency for reform is diffuse.

The Aegis Case in the Contract Record

The Aegis Combat System provides the contemporary worked example of how this pattern operates in practice on the most important surface combatant capability in the U.S. Navy. The contract record itself articulates the lock-in in formal procurement language.

In January 2026, Lockheed Martin secured a five-year, $99.9 million Aegis Weapon System core sustainment support contract from Naval Sea Systems Command, covering engineering, logistics, and technical support for all in-service or post-production Aegis platforms — Arleigh Burke-class destroyers, Constellation-class frigates, Coast Guard cutters, the Aegis Training and Readiness Center, the Integrated Warfare Systems Laboratory, and the Surface Combat Systems Center. The award is one in a continuing series stretching back decades. A 2023 contract action was characterized as a $853 million seven-year fielding-and-sustainment award; a 2024 modification added $141.5 million; a 2025 modification added $92.2 million; subsequent modifications in mid- and late-2025 added further hundreds of millions. The pattern is continuous: NAVSEA awards Lockheed Martin Rotary and Mission Systems modification after modification, sole-source, for the system Lockheed Martin built and continues to control.

The formal procurement justification on a $140 million Aegis fielding and sustainment award stated the structural reality directly:

“LM RMS is the only responsible source, and no other supplies or services could fulfill the AEGIS F&S requirements without causing unacceptable schedule delays and substantial duplication of costs that is not expected to be recovered through competition.”

— Naval Sea Systems Command, sole-source justification, AEGIS F&S contract

This is the operational consequence of the Univac pattern your peers watched in the 1970s, expressed in the procurement record of 2024. The Navy cannot compete the work because the data rights, the proprietary software environment, the configuration management infrastructure, and the human expertise are all controlled by a single contractor. "Substantial duplication of costs that is not expected to be recovered through competition" is the contracting officer's polite formulation for: we are locked in, the contractor knows we are locked in, and the price reflects that.

The Aegis Ballistic Missile Defense system — Lockheed's Combat Systems Engineering Agent role — is supported through a sole-source indefinite-delivery contract worth up to $2.97 billion over ten years, awarded by the Missile Defense Agency. The same structural logic operates: no alternative source exists because the data rights and the operational expertise are concentrated in a single industrial location in Moorestown, New Jersey, where roughly 96 percent of contract work is performed. If that location, that workforce, or that corporate organization were disrupted by labor action, financial difficulty, or kinetic attack, the Navy's entire surface combatant air-defense capability would be operationally degraded with no organic backup.

The Right-to-Repair Parallel

The connection between defense TDP resistance and commercial right-to-repair resistance is structural, not analogical. The same business model operates in both domains, modified by the regulatory environment in which it functions. The Federal Trade Commission's January 2025 antitrust suit against John Deere makes the parallel explicit and actionable.

The FTC, joined by the attorneys general of Illinois, Minnesota, Michigan, Wisconsin, and Arizona, alleged that Deere created and maintained a repair services monopoly through control of its Service ADVISOR diagnostic and calibration tool, available in fully functional form only to Deere-authorized dealers. A nominally consumer-facing version called Customer Service ADVISOR exists, but the FTC complaint alleges it cannot diagnose, test, or calibrate "restricted" repairs — the category that requires access to the underlying software and coding. The complaint cites internal Deere documentation indicating the practices were intentional and strategic, approved by company executives, designed to steer service and parts revenue to Deere's authorized dealer network.

In April 2026, Deere agreed to a $99 million class-action settlement filed in the U.S. District Court for the Northern District of Illinois. Under the settlement, Deere will reimburse class plaintiffs for repairs made by authorized dealers since January 2018, and will make available for ten years the digital tools required for maintenance, diagnosis, and repair of large agricultural equipment, including reprogramming and diagnostic functions through John Deere Operations Center PRO Service in offline mode. The FTC's separate antitrust case continues. In June 2025, the federal court denied Deere's motion to dismiss, finding the FTC's claims legally sufficient to proceed.

The pattern Deere represents is not isolated. As of January 1, 2026, enacted right-to-repair laws in California, Colorado, Minnesota, New York, Oregon, and Washington require manufacturers of consumer electronics and other covered products to make parts, tools, documentation, and diagnostic software available to independent repair providers and product owners on fair and reasonable terms. Connecticut and Texas laws are scheduled to take effect later in 2026. More than 33 right-to-repair bills were introduced in the first weeks of January 2026 alone. H.R. 5857, the FARM ACT, was introduced in October 2025 to extend right-to-repair principles specifically to farm equipment.

The legislative and litigation momentum reflects what the courts and state attorneys general are increasingly willing to articulate: the business model of controlling sustainment through documentation restriction is anticompetitive, and antitrust law provides actionable remedy when manufacturers exploit aftermarket monopoly positions. Apple, John Deere, and the major medical equipment manufacturers have all been forced to make partial accommodations under regulatory pressure. The accommodations remain partial. The underlying business model has not been abandoned voluntarily.

The FY 2026 NDAA: Reform Deferred Again

The Fiscal Year 2026 National Defense Authorization Act, signed into law December 18, 2025 (Public Law 119-60), illustrates how defense reform on this question proceeds. Both the House and Senate versions of the FY 2026 NDAA initially included significant right-to-repair provisions that would have extended commercial right-to-repair principles to DoD weapon systems. The final compromise legislation dropped these provisions.

In their place, the FY 2026 NDAA requires DoD to inventory its existing data rights and data rights contractual requirements, including requirements that DoD may not always invoke. The provision is useful — knowing what data rights the government has, contractually, is a prerequisite to exercising those rights — but it is a substantial retreat from the operational reform the original legislation contemplated. The pattern is familiar: bold reform language is introduced, contractor lobbying mobilizes, the conference committee negotiates the substance away, and the enacted statute requires reporting and inventory in lieu of structural change.

The same FY 2026 NDAA expanded the Expedited Acceptance and Qualification process under Section 832 to allow accelerated approval of secondary sources for critical readiness items, and required Expedited Qualification Panels in each military department. These are useful incremental reforms. They do not address the underlying problem, which is that primes deliver insufficient data and the government accepts the deliverable because contracting officers lack the technical expertise and institutional authority to verify that the delivered TDP would actually support second-source manufacturing.

DoD's Intellectual Property Cadre, established under Section 838 of the FY 2020 NDAA, was supposed to address the expertise gap. GAO has reported that the Cadre operates as an advisory function rather than a verification function, and that none of the five programs examined in GAO-25-107468 included all required elements in their IP strategies. The institutional reform was made; the institutional behavior was not changed. This is the iron pattern of defense acquisition reform across five decades: regulatory frameworks improve incrementally, contractor compliance becomes more sophisticated, and the underlying lock-in persists.

The Operational Vulnerability

Concern about Navy operational availability under contractor lock-in is now documented in GAO findings, congressional testimony, and the procurement record itself. The strategic implications extend beyond cost.

A Navy combat system that cannot be repaired by Navy sailors at sea, whose depot-level maintenance requires contractor field service representatives flown from CONUS to forward-deployed locations, is a system whose operational availability depends on commercial logistics chains that may not survive contested wartime conditions. The Pacific scenario that defense planners now openly discuss makes this a strategic vulnerability of the first order. If the supply lines from CONUS to forward-deployed naval forces are interrupted in a Taiwan contingency, contractor field service cannot reach the ships. Combat systems that fail in operational use cannot be restored to service through organic Navy capability. The fleet degrades.

Chinese strategic planners understand this. Open-source PLA writing on the U.S. military's contractor dependence has been consistent for at least a decade in identifying it as a critical vulnerability of American power projection. The PLA does not need to defeat the U.S. Navy in fleet engagement. It needs to interdict the maintenance pipeline that keeps the U.S. Navy operating. A six-month interruption of the Aegis sustainment pipeline would degrade U.S. surface combatant capability faster than combat attrition. The contractor lock-in pattern that began as a 1970s procurement convenience has become, in the 2020s, a wartime vulnerability.

Naval Reactors stands as the institutional counterexample. Admiral Rickover's organization preserved organic Navy capability for nuclear propulsion across 70 years specifically because Rickover refused to accept the contractor-lock-in business model. Naval Reactors maintains its own technical authority, its own training pipeline, its own engineering standards, and substantial organic capability for components and sustainment that other Navy programs outsource entirely to primes. The result is a fleet of nuclear-powered submarines and carriers whose operational availability does not depend on contractor goodwill or commercial logistics under contested conditions. The model is institutionally expensive. It works. The Navy has chosen, repeatedly, not to apply the model to combat systems.

"The contractor lock-in pattern that began as a 1970s procurement convenience has become, in the 2020s, a wartime vulnerability."

What Real Reform Would Require

The reforms that would actually break the documentation-hostage pattern are known. They have been recommended in GAO reports across decades. They have not been implemented because the political coalition required to overcome contractor lobbying has not coalesced. Listed in approximate order of difficulty:

Closing the OMIT loophole. Congress could amend the relevant statute to extend government unlimited rights to detailed manufacturing or process data needed to repair, maintain, or competitively procure systems acquired with substantial government funding. GAO has effectively recommended this in the September 2025 report. The contractor lobbying against it would be intense, but the legal framework is straightforward.

Mandatory escrow with independent verification. TDP deliverables should be escrowed with an independent third party empowered to verify, through actual second-source manufacturing trials, that the delivered data is sufficient. Primes would have to deliver actually-sufficient data because verification testing would expose inadequacy before contract closeout. The model exists in some classified weapons programs and could be extended.

Organic capability funding for critical systems. The Naval Reactors model applied to surface combat systems would require sustained congressional investment in organic Navy expertise for Aegis, SPY-6, CEC, and other critical capabilities. The political resistance from contractor districts would be severe but not insurmountable, particularly under sustained external pressure.

Right-to-repair extension to defense procurement. The legal framework being developed in commercial right-to-repair litigation translates directly to defense contexts. Antitrust principles applicable to John Deere are equally applicable to Lockheed Martin and Raytheon when those companies use data-rights restriction to capture sustainment monopolies on government-funded systems.

False Claims Act enforcement on TDP inadequacy. Existing legal authority permits treating verifiably insufficient TDP delivery as fraud rather than as routine contract dispute. The institutional willingness to use this authority has been minimal. A few high-profile cases would change contractor behavior across the industry.

Multi-source procurement architecture from program inception. New programs should be structured with multiple competing primes from initial development, each required to deliver complete TDP, with the government as the integrator. The model has been used successfully on some engine and missile programs. It costs more initially and produces vastly lower lifecycle cost through preserved competition.

The Lunar Base Implication

The companion piece to this article identified the lunar base as a forcing function for institutional knowledge preservation. The same institutional analysis applies, with greater urgency, to procurement reform. The lunar base will not be built by NASA or the DoD directly. It will be built by prime contractors operating under exactly the procurement dynamics documented above.

SpaceX, Blue Origin, Lockheed Martin, Boeing, Northrop Grumman, and the second-tier primes that will build lunar transport, surface infrastructure, ISRU systems, habitat modules, and surface mobility have every commercial incentive to control sustainment through documentation restriction. The lunar economy that NASA and DoD planners describe — sustained presence, regular logistics, eventual commercial expansion — will be operationally captive to whichever primes establish lock-in early. The Avcoat case documented in the companion piece is a preview: Lockheed Martin holds the manufacturing process knowledge for the heat shield, and NASA flies what Lockheed delivers. Multiply that across every critical lunar-system component and the resulting architecture is a sustained American lunar presence whose operational availability is contractor-dependent in exactly the same way Navy surface combatants are now contractor-dependent.

If the Pacific deterrent depends on Aegis, and Aegis sustainment depends on a single contractor, the contractor's organizational health and commercial decisions become matters of national security. If lunar logistics depend on a single transport provider, and lunar surface operations depend on a single habitat provider, and lunar communications depend on a single sensor and relay provider, then the lunar architecture is operationally captured before it is built. The fact that the primes building the lunar architecture are commercially dynamic and currently performing well does not change the structural vulnerability. Organizations change. Leadership changes. Strategic priorities change. The institutional structure that locks the government into single-source dependence persists across those changes, with effects measured in decades.

The reform window, as the companion piece argued, is the present moment when the commitments are being made and the contracts are being structured. Once the lunar architecture is locked into prime-controlled sustainment with inadequate government data rights, the lunar base will exhibit the same operational and cost pathologies that GAO has documented in F-35, F/A-18, LCS, Stryker, and Virginia-class. The pathologies are not failures of execution. They are predictable consequences of a procurement structure that allows primes to capture sustainment through documentation control. The Univac pattern your generation watched at NAVSEA in the 1970s will be the lunar pattern of the 2030s and 2040s, unless the structural reforms outlined above are implemented during the architecture-definition phase.

Apollo lost the manufacturing knowledge through institutional decay and contractor reorganization. Artemis is losing it through the same mechanisms, in real time. A lunar base built under current procurement structures will not lose it — it will simply never have it, because the primes will retain it as a proprietary commercial asset and the government will not require otherwise. The fifty-year pattern of failed reform is not a reason for fatalism. It is a description of what happens when external pressure for reform is insufficient. The China factor, the Pacific deterrent vulnerability, and the lunar-base architecture decision are all converging into the same forcing function. Whether the resulting reform is real or another round of inventory requirements and Cadre advisories is the open question for the next two years of defense and space policy.

"The Univac pattern your generation watched at NAVSEA in the 1970s will be the lunar pattern of the 2030s and 2040s, unless the structural reforms are implemented during the architecture-definition phase."

Sources

All sources accessed 25 April 2026. URLs verified at time of publication. Sources are organized by category. Citation numbering continues independently from the companion piece.

Government Accountability Office Reports

[1]  U.S. Government Accountability Office. "Weapon System Sustainment: DOD Can Improve Planning and Management of Data Rights." GAO-25-107468, reissued with revisions 29 September 2025. Examines F-35, F/A-18, LCS, Stryker, and Virginia-class submarine programs.  https://www.gao.gov/products/gao-25-107468

[2]  GAO-25-107468 full report (Highlights and full text).  https://files.gao.gov/reports/GAO-25-107468/index.html

[3]  U.S. Government Accountability Office. "Defense Acquisitions: DOD Should Take Additional Actions to Improve How It Approaches Intellectual Property." GAO-22-104752, November 2021.  https://www.gao.gov/assets/gao-22-104752.pdf

[4]  U.S. Government Accountability Office. "Weapon System Sustainment: DOD Needs to Better Capture and Report Software Sustainment Costs." GAO-19-173, February 2019.  https://www.gao.gov/assets/gao-19-173.pdf

[5]  U.S. Government Accountability Office. "Defense Acquisition: DOD Should Clarify Requirements for Assessing and Documenting Technical-Data Needs." GAO-11-469, May 2011.  https://www.gao.gov/assets/a318192.html

Federal Acquisition Regulation & Statute

[6]  DFARS 252.227-7013, Rights in Technical Data — Other Than Commercial Products and Commercial Services; DFARS 252.227-7014, Rights in Noncommercial Computer Software; DFARS subparts 227.71 and 227.72.  https://www.acquisition.gov/dfars/252.204-7012-safeguarding-covered-defense-information-and-cyber-incident-reporting.

[7]  Defense Pricing and Contracting. "Open DFARS Cases as of 4/10/2026." Tracking document for pending DFARS rulemaking, including section 804 (NDAA FY 2012) on technical data rights for modular system interfaces and section 809 on items developed at private expense.  https://www.acq.osd.mil/dpap/dars/opencases/dfarscasenum/dfars.pdf

FY 2026 National Defense Authorization Act Analysis

[8]  Crowell & Moring LLP. "The FY 2026 National Defense Authorization Act." Client alert, 23 December 2025. Notes that final compromise NDAA dropped right-to-repair provisions both chambers had initially passed; substituted data-rights inventory requirement.  https://www.crowell.com/en/insights/client-alerts/the-fy-2026-national-defense-authorization-act

[9]  Crowell & Moring / Government Contracts Legal Forum. "The FY 2026 National Defense Authorization Act." Government Contracts Legal Forum analysis, 29 December 2025.  https://www.governmentcontractslegalforum.com/2025/12/articles/dod/the-fy-2026-national-defense-authorization-act/

[10]  Public Law 119-60, Fiscal Year 2026 National Defense Authorization Act, signed 18 December 2025. Sections 832 (Expedited Acceptance and Qualification), 875 (DFARS contract-stay procedures), 1846 (advanced manufacturing process approval).

DoD Small Business Innovation Research / Technical Data Rights Rulemaking

[11]  Crowell & Moring. "Final DoD Rule Codifies 20-Year SBIR Data Protection Period and Other SBIR Program Protections." Government Contracts Legal Forum, 28 January 2025. DFARS amendment finalized 17 December 2024, effective 17 January 2025.  https://www.governmentcontractslegalforum.com/2025/01/articles/cybersecurity/final-dod-rule-codifies-20-year-sbir-data-protection-period-and-other-sbir-program-protections-while-punting-potential-changes-to-marking-requirements/

Aegis Combat System Sustainment Contracts

[12]  ExecutiveBiz. "Lockheed RMS Wins Navy Aegis Logistics Support Contract." 22 January 2026. Five-year, $99.9 million Aegis Weapon System core sustainment support contract from NAVSEA.  https://www.executivebiz.com/articles/lockheed-rms-navy-aegis-logistics-support-contract

[13]  GovCon Wire. "Lockheed Secures $853M Navy Contract to Support Aegis Combat System Fielding, Sustainment." 6 January 2023. Sole-source seven-year fielding-and-sustainment award.  https://www.govconwire.com/articles/lockheed-secures-853m-navy-aegis-fielding-and-sustainment-support-contract

[14]  Executive Gov. "Lockheed Secures $142M Navy Contract Modification for AEGIS Combat System Services." December 2023.  https://executivegov.com/2023/12/lockheed-secures-142m-navy-contract-modification-for-aegis-combat-system-services/

[15]  OrangeSlices AI. "Contract Award: $140M Navy AEGIS Fielding & Sustainment." Documents NAVSEA sole-source justification: "LM RMS is the only responsible source."  https://orangeslices.ai/contract-award-140m-navy-aegis-fielding-sustainment/

[16]  GovCon Wire. "Lockheed Books Navy, MDA Contracts for Aegis BMD Support." Includes ten-year, $2.97 billion Combat Systems Engineering Agent indefinite-delivery contract.  https://www.govconwire.com/articles/lockheed-aegis-ballistic-missile-defense-system-csea-contract-award

[17]  ExecutiveBiz. "Lockheed Secures Navy Contract Modification for Aegis System Fielding, Sustainment Support." 14 March 2023.  https://www.executivebiz.com/articles/lockheed-secures-navy-contract-modification-for-aegis-sustainment-support

[18]  Investing.com. "Lockheed Martin Secures $81 Million in Defense Contracts for Aegis Systems." 24 September 2025.  https://www.investing.com/news/stock-market-news/lockheed-martin-secures-81-million-in-defense-contracts-for-aegis-systems-93CH-4254410

Right-to-Repair: FTC v. Deere & Company

[19]  Federal Trade Commission. "FTC, States Sue Deere & Company to Protect Farmers from Unfair Corporate Tactics, High Repair Costs." Press release, 15 January 2025.  https://www.ftc.gov/news-events/news/press-releases/2025/01/ftc-states-sue-deere-company-protect-farmers-unfair-corporate-tactics-high-repair-costs

[20]  Troutman Pepper Locke. "FTC, States Sue John Deere in Right to Repair Lawsuit." Regulatory Oversight blog, 10 March 2025. Notes 3-2 FTC vote along party lines, joining of Michigan, Wisconsin, and Arizona AGs.  https://www.regulatoryoversight.com/2025/03/ftc-states-sue-john-deere-in-right-to-repair-lawsuit/

[21]  National Agricultural Law Center. "FTC Files Suit Against John Deere." Legal analysis covering Sherman Act § 2, FTC Act § 5(a), and state antitrust claims.  https://nationalaglawcenter.org/ftc-files-suit-against-john-deere/

Right-to-Repair: Class Action Settlement & State Laws

[22]  The Register. "John Deere Agrees $99m Right-to-Repair Settlement." 9 April 2026. Settlement filed in U.S. District Court Northern District of Illinois.  https://www.theregister.com/2026/04/09/john_deere_repair_settlement/

[23]  Farm Policy News (University of Illinois). "Deere Settles Class Action Right-to-Repair Lawsuit." April 2026. Reports settlement requires ten years of digital tool availability.  https://farmpolicynews.illinois.edu/2026/04/deere-settles-class-action-right-to-repair-lawsuit/

[24]  University of Arkansas Division of Agriculture. "Deere Settles Right-to-Repair Suit, but Federal Trade Commission Case Still Looms." 15 April 2026.  https://uaex.uada.edu/media-resources/news/2026/april/04-15-2026-ark-nalc-right-to-repair.aspx

[25]  Arnold & Porter Kaye Scholer LLP. "John Deere's $99 Million Settlement and the Accelerating State Right-to-Repair Landscape." April 2026. Documents enacted state laws in California, Colorado, Minnesota, New York, Oregon, and Washington effective 1 January 2026; Connecticut and Texas pending; H.R. 5857 (FARM ACT) introduced October 2025.  https://www.arnoldporter.com/en/perspectives/blogs/consumer-products-and-retail-navigator/2026/04/john-deeres-99-million-settlement-and-the-right-to-repair-landscape

[26]  AgTech Navigator. "John Deere to Pay $99m in Right-to-Repair Settlement, Amid Ongoing FTC Litigation." April 2026.  https://www.agtechnavigator.com/Article/2026/04/07/john-deere-settles-right-to-repair-case-with-99m-faces-other-lawsuit/

[27]  SlashGear. "John Deere Lawsuit Ends in $99M Payout for Farmers." April 2026. Cites Reuters and AP News reporting on settlement terms.  https://www.slashgear.com/2153345/john-deere-right-to-repair-lawsuit-settlement/

Companion Piece

[28]  Pseudo Publius. "The Apollo Knowledge Trap: Why America Keeps Forgetting How to Build Its Greatest Machines — And Why Video May Be the Cure." 25 April 2026. Companion piece on institutional knowledge loss, Avcoat reformulation, F-1 reconstruction, and video documentation as preservation standard.

 

 

ABOUT THE BYLINE  Pseudo Publius is the byline used for civic and industrial-policy analysis directed at general aerospace and defense readership. The byline preserves the nonpartisan posture of affiliated nonprofit publications. This piece is the second of a two-part series on institutional capability preservation in U.S. aerospace and defense.

Why America Keeps Forgetting How to Build Its Greatest Machines —

 

The Apollo Knowledge Trap

AEROSPACE INDUSTRY ANALYSIS / KNOWLEDGE PRESERVATION

Why Video May Be the Cure

By Pseudo Publius   |   Aerospace Industry Analysis   |   25 April 2026

  BLUF — BOTTOM LINE UP FRONT

The most expensive lesson of the Apollo program was not technical but institutional: the United States lost the ability to build the F-1 engine within a generation of its retirement, and the same pattern is now visible in the Avcoat heat shield reformulation that drove the Artemis I char-loss anomaly. NASA's own knowledge-management apparatus — the Lessons Learned Information System and APPEL Knowledge Services — captures decisions and outcomes in text, but not the embodied manufacturing skill that determines whether complex hardware actually works. Meanwhile, the U.S. Army, Air Force, and commercial aerospace primes are quietly converting to augmented-reality and video-based work instruction, with measured error reductions of 36 to 100 percent in maintenance tasks. As DoD and NASA prepare for sustained lunar operations and a workforce transition in which 25 percent of aerospace employees are at or beyond retirement eligibility, the question is no longer whether video and AR-based capture should supplement engineering drawings and text procedures, but whether the institutions can adopt them fast enough to preserve the manufacturing capability the next generation of programs will require.

The Engine We Cannot Rebuild

In January 2013, a small team of NASA engineers at Marshall Space Flight Center wheeled a 50-year-old artifact onto Test Stand 116 in the East Test Area and lit it. The artifact was the gas generator from F-1 serial number F-6049 — an engine originally manifested for Apollo 11, pulled before flight due to a glitch, and stored at the Smithsonian for four decades. For roughly twenty seconds it produced about 31,000 pounds of force, the small piece of the larger 1.5-million-pound-thrust machine that once powered the Saturn V first stage.

The hot fire was not a celebration. It was an audit. NASA was evaluating Pratt & Whitney Rocketdyne and Dynetics' proposed F-1B booster for the Space Launch System, and the engineers needed to understand what they actually had. Marshall propulsion engineer Nick Case told Aviation Week's contemporaries at the time that his team had "pulled F-1 engine drawings and data packages and studied an F-1 engine that we had on hand at Marshall." The team used structured-light 3-D scanning to produce CAD models of the gas generator and selective laser melting to fabricate test parts. The original drawings, in other words, were not sufficient to build the part. The component had to be reverse-engineered from a museum piece.

This is the central, embarrassing fact of post-Apollo American aerospace: the F-1 cannot be built today, even though the blueprints survive. Industry observers and NASA engineers attribute this to a combination of retired and deceased craftsmen who held the manufacturing know-how, hand-fabrication techniques no longer in routine practice, materials such as the original Inconel X-750 forging stock that are no longer produced in identical specification, and design notes that were kept on scraps of paper or in the heads of engineers under deadline pressure during the 1960s. The F-1B that ultimately competed for the SLS Advanced Booster contract in 2015 was — in the candid assessment of engineers involved — less a rebuilt F-1 than a new engine inspired by it, using modern manufacturing techniques because the originals could not be replicated. The F-1B lost the competition to a five-segment derivative of the Shuttle Solid Rocket Booster, and the question became academic. The capability remained lost.

"The original drawings were not sufficient to build the part. The component had to be reverse-engineered from a museum piece."

The Avcoat Sequel

If the F-1 case were unique, it might be dismissed as a Cold War curiosity. It is not unique. The Artemis I heat-shield investigation, formally closed by NASA in December 2024, makes the institutional pattern unmistakable.

Avcoat 5026-39 is the ablative material developed by Avco Corporation for the Apollo Command Module heat shield. Composed of silica fibers in an epoxy-novolac resin, it performed flawlessly across Apollo's lunar-return reentries. When NASA selected Avcoat for Orion, the formulation had to be modified to comply with environmental legislation enacted after Apollo, and the manufacturing approach was redesigned: instead of hand-filling more than 300,000 honeycomb cells as Apollo had done, Lockheed Martin's process at Michoud Assembly Facility produced fewer than 200 pre-machined Avcoat blocks bonded to a titanium-and-composite substrate.

On 11 December 2022, Orion returned from its uncrewed lunar flyby and made the fastest, hottest reentry of any human-rated capsule. Internal temperatures remained safe; the vehicle splashed down on schedule. But post-flight inspection revealed something engineers had not predicted. More than 100 locations on the heat shield had shed charred material in chunks rather than ablating uniformly. The trail of debris was visible in entry imagery.

Two years of investigation, more than 100 arc-jet tests at NASA Ames, and detailed sampling of approximately 200 Avcoat specimens at Marshall produced a specific technical answer. During Artemis I's skip-entry profile, Orion dipped into the upper atmosphere, climbed back out, and reentered. Between dips, the outer surface cooled but the underlying material was still hot, undergoing pyrolysis and producing gas. The reformulated Avcoat lacked sufficient permeability for the gas to escape through the char layer, so internal pressure built up and blew chunks of material away — a phenomenon engineers call spallation.

The most striking sentence in the public record is the one engineers familiar with the investigation have made repeatedly: Apollo engineers were aware of the permeability issue and designed around it. Apollo capsules used skip-reentry profiles without trouble. The Artemis Avcoat reformulation, undertaken decades later for legitimate environmental-compliance reasons, altered permeability in ways the ground-test program — which used heating rates higher than Orion actually experienced — failed to surface. NASA elected to fly Artemis II with the already-installed heat shield using a modified, steeper, lofted reentry trajectory; former NASA astronaut and heat-shield specialist Charles Camarda publicly disputed that decision, arguing in The New York Times that engineers do not fully understand the root cause. Artemis II returned successfully in April 2026, but the dispute illustrates the deeper problem: a working capability had been silently degraded across a generational handoff, and nobody knew until the artifact was used in flight.

A Pattern, Not an Accident

The literature on tribal-knowledge loss in U.S. aerospace and defense manufacturing is now extensive, and the pattern is consistent. Per Aspera, an industrial-policy organization that has documented several cases, cites the Fogbank example: in the early 2000s, the United States found it could not reproduce a classified interstage material used in nuclear warheads, because veteran staff had retired without recording the manufacturing process. Re-learning the lost knowledge cost roughly 5 years and $69 million, and delayed a warhead refurbishment program. The plutonium-pit case is similar: large-scale production halted in 1989, and the United States has struggled for more than three decades to restart the manufacturing line.

The aerospace workforce numbers underscore the urgency. PwC's analysis of Aerospace Industries Association data finds that 25 percent of A&D workers are aged 56 or older. Deloitte's 2025 industry outlook reports that 25 percent of the workforce has more than 20 years of experience and is at or beyond retirement eligibility. The Manufacturing Institute projects 2.1 to 4 million unfilled manufacturing positions by 2030. An IEEE GlobalSpec survey found that more than 60 percent of engineers view loss of tribal knowledge as extremely or very important — the fourth-ranked concern in the profession.

Apple CEO Tim Cook captured the macro picture in a widely reported 2024 remark: in the United States, a meeting of tooling engineers might not fill a room; in China, multiple football fields. The observation is anecdotal, but the structural data align. America has lost more than four million manufacturing jobs since 2000. Roughly a quarter of U.S. machinists and tool-and-die makers are over 55. The institutional muscle memory required to build complex, low-volume, high-precision hardware is atrophying at the same time the country is contemplating a sustained lunar presence and a contested Pacific.

What NASA's Knowledge System Actually Captures

NASA is not unaware of the problem. NASA Procedural Directive 7120.6A, revalidated with Change 1 in July 2024, establishes the agency's Lessons Learned Process, and the Office of the Chief Knowledge Officer operates a federated system that includes the Lessons Learned Information System (LLIS), the NASA Engineering Network, the APPEL Academy of Program/Project & Engineering Leadership, and ASK Magazine. The 2012 NASA Office of Inspector General audit (IG-12-012) found that the agency was spending roughly $750,000 annually on LLIS alone, and that JPL was the only NASA Center consistently contributing.

The deeper finding from both the OIG audit and the earlier 2002 GAO report (GAO-02-195) is that NASA's lessons-learned culture captures decisions and outcomes — what was done, what went wrong, what was concluded — but is poorly structured to capture process knowledge. The GAO noted "cultural barriers to the sharing of lessons learned, such as the lack of time to capture or submit lessons and a perception of intolerance for mistakes." The OIG noted that 6 of 10 NASA Centers did not cross-reference lessons to their engineering standards. The system records that the F-1 used a particular injector pattern; it does not record the welder's hand motion, the visual cue that distinguishes a sound braze from a marginal one, the cure-rate variability that depends on humidity and ambient temperature, or the dozens of small craft decisions that determine whether the artifact actually works.

This is the gap your retired senior engineer corps is pointing at, and it is the gap that text-based documentation systems — however well-administered — cannot fill on their own.

The YouTube Generation

Outside formal aerospace, an entirely different documentation regime has emerged in the past fifteen years, built almost without aerospace's participation. iFixit's photographic and video disassembly guides for thousands of consumer products have become the de facto repair documentation for most devices made in the past decade. YouTube has displaced manufacturer manuals as the primary technical reference for everything from automotive repair to surgical technique. Modern surgical training has institutionalized recorded procedures with expert commentary as a primary teaching modality, on the explicit recognition that surgical skill cannot be transmitted through text alone.

The reason is straightforward. Spatial relationships, hand motions, sequence dependencies, and the visual cues that distinguish correct work from incorrect work are tacit knowledge categories that text struggles with. A photograph captures static geometry; video captures motion, timing, and the auditory and visual feedback signals that experienced craftsmen use to know when something is right. The consumer-electronics workforce that grew up with these documentation forms now expects them as the default. The aerospace workforce that came up through engineering drawings and text procedures is retiring.

The Military Has Started to Move

The most aggressive institutional adopters of video and augmented-reality work instruction are not the prime contractors but the U.S. military services and the commercial firms that train them. The pattern is now well-documented and is accelerating.

On 14 April 2026 — eleven days before this report — the U.S. Army staged a public demonstration at the 4th Battalion, 27th Field Artillery Regiment motor pool at Fort Bliss, Texas, in which Bradley Fighting Vehicle maintainers and self-propelled artillery mechanics tested AR headsets that overlay maintenance procedures on the actual vehicle. The Army Combat Capabilities Development Command Armaments Center deployed the systems with tablets linked to the headsets. The DVIDS imagery release described the program in operational rather than experimental terms: "Innovation in maintenance means giving Soldiers the right information at the right time to keep systems operational and units mission capable."

The U.S. Air Force has taken the same direction further. The Air Force Institute of Technology conducted a structured study of the Manifest AR platform from Taqtile, used to train jet-engine mechanics. The published results found that technicians using traditional paper Technical Orders installed parts incorrectly 57 percent more often than technicians using the AR-based work instruction. Other military studies of AR maintenance documentation have reported error reductions in the range of 36 to 100 percent across various tasks. Booz Allen Hamilton, working with the Army, deployed a 5G-networked wireless XR training system at Fort Cavazos that allows subject-matter experts in remote locations to observe and coach trainees through AR headsets in real time — a capability the firm describes as a U.S. military first.

Microsoft's Integrated Visual Augmentation System (IVAS), built on a ruggedized HoloLens 2 derivative under a 10-year Army contract, has had a troubled development history but has shifted toward maintenance and training applications where its capabilities are better matched to the use case. Commercial defense training firms — DiSTI's VE Studio, Manifest, and others — now serve as primary contractors or major subcontractors on essentially every U.S. service maintenance-trainer program. The technical maturity is no longer in dispute. The institutional question is integration.

"Technicians using traditional methods installed parts incorrectly 57 percent more times than technicians using AR-based work instruction."

The Commercial Aerospace Lag

On the commercial-aerospace side, video-and-AR adoption is more uneven. Boeing has used video work instruction for major-assembly procedures since the 787 program, partly because distributed manufacturing across multiple countries and language groups required visual references that transcended text. Airbus pursues similar practices. Hexagon's Manufacturing Intelligence business has deployed laser-guided inspection systems for aircraft assembly that automate quality verification in ways that paper-based first-article inspection cannot match. AkzoNobel Aerospace Coatings announced drone-enabled inspection capabilities for fleet-wide coating maintenance at MRO Americas earlier this month.

But the documentation standards that govern aerospace certification — FAA, DoD, AS9100 — remain text-and-drawing-centered. Industry analyses of U.S. aerospace operational excellence in 2026 (TeepTrak's published OEE benchmarking) note that aerospace suppliers typically operate at 50 to 65 percent OEE, against 70 to 80 percent in automotive, with the structural drag attributed in significant part to documentation overhead: paper-based SPC, manual quality transcription, and certification-driven stoppages. The same analysis identifies real-time digital SPC and tablet-based digital work instruction as the practical path to capturing more of the improvable operational loss without compromising traceability.

Configuration management for video documentation remains an unsolved aerospace problem at scale. When a design changes, text and drawings update through formal change control. Video updates require re-shooting on a manufacturing floor that may no longer be configured for the original task, with workers who may no longer be qualified to perform it. Stale video showing superseded procedures could be more dangerous than no video at all. The aerospace primes have not yet collectively committed to solving these problems, and the certification authorities have not yet collectively required them to.

What a New Standard Would Look Like

A multi-modal documentation standard adequate to preserve manufacturing capability across generations would combine three representations:

CAD and engineering drawings as the geometric ground truth — what the artifact is supposed to be, with full dimensional and tolerance specification.

Text documentation for procedural logic, design rationale, requirements traceability, and the analytical reasoning that explains why the design is as it is.

Video documentation for the embodied skill — what proper manufacturing technique looks like, what failure modes look like, how skilled inspectors recognize problems before instruments confirm them, and the auditory and visual feedback signals that experienced craftsmen rely on.

Each form captures information the others cannot. CAD without text is geometry without rationale; text without CAD is interpretation without ground truth; both without video lose the embodied knowledge that distinguishes a working artifact from a nominally compliant one. The Department of Energy's Stockpile Stewardship Program — funded at roughly $15 billion annually — has been pursuing a version of this standard for nuclear-weapons manufacturing capability since the 1992 testing moratorium, including aggressive video documentation of retiring technicians explaining their craft. The Naval Reactors program, which has preserved deep technical capability across 70 years of the Navy's nuclear-propulsion fleet, achieves a similar result through extreme standardization, formal apprenticeship, and an explicit person-to-person knowledge-transfer pipeline. Both models are institutionally expensive. Both demonstrate that the problem is solvable when an organization treats long-term capability preservation as a first-class budget line.

A more bounded near-term proposal — and the one most likely to achieve traction in the current NASA and DoD acquisition environment — is preservation video. When a major manufacturing line is set up, dedicate explicit resources to systematic video capture of the actual processes, the inspection criteria, the failure modes, and the tribal-knowledge commentary that workers express when explaining their craft. Index this material against the formal documentation. Store it in long-term archives at appropriate classification levels. Make it available to future programs that may need to reconstitute the capability. The cost is modest relative to program development cost. The value is preserved against precisely the institutional decay patterns that destroyed Apollo's manufacturing base.

The Lunar Base Forcing Function

None of this is academic. The Artemis program is in the middle of a reformulated Avcoat campaign for Artemis III and beyond. The U.S. Army is fielding AR maintenance systems at Fort Bliss this month. China's lunar-program timeline — crewed landing by 2030, International Lunar Research Station partnership growing — is pacing competitive pressure on a U.S. infrastructure that has already demonstrated, twice, that it cannot reliably reconstitute capability across a generational gap.

A sustained lunar presence cannot be built on the documentation standards that built Apollo. The math of expendable architecture does not close at base scale, and the institutional knowledge required to support reusable cislunar transport, in-situ resource utilization, and surface infrastructure cannot be allowed to dissipate between programs the way F-1 and Avcoat capability dissipated. The aerospace-and-defense workforce that will operate that base in 2040 is the workforce that grew up watching YouTube tutorials. The documentation standard they need is the one this generation is now building, in fragments, across the U.S. Army motor pools, the Air Force jet-engine training schoolhouses, and the commercial aerospace shop floors that have already begun the transition.

The most important industrial lesson of Apollo was not how to build a Saturn V. It was that we did not know how to keep knowing. The technology to fix that problem now exists. The institutional commitment is the variable.

"The most important industrial lesson of Apollo was not how to build a Saturn V. It was that we did not know how to keep knowing."

Sources

All sources accessed 25 April 2026. URLs verified at time of publication.

NASA Official Releases & Documentation

[1]  NASA. "NASA Identifies Cause of Artemis I Orion Heat Shield Char Loss." Press release, 5 December 2024.  https://www.nasa.gov/missions/artemis/nasa-identifies-cause-of-artemis-i-orion-heat-shield-char-loss/

[2]  NASA. "NASA Shares Orion Heat Shield Findings, Updates Artemis Moon Missions." Press release, 5 December 2024.  https://www.nasa.gov/news-release/nasa-shares-orion-heat-shield-findings-updates-artemis-moon-missions/

[3]  NASA. "F-1 Engine Gas Generator Test at Marshall." Marshall Space Flight Center, 24 January 2013.  https://www.nasa.gov/exploration/systems/sls/multimedia/gallery/f1test_1.html

[4]  NASA. "F-1 Gas Generator at Marshall's Test Stand 116." Marshall Space Flight Center image release.  https://www.nasa.gov/image-article/f-1-gas-generator-marshalls-test-stand-116/

[5]  NASA. NPD 7120.6A, "Knowledge Policy on Programs and Projects." Revalidated with Change 1, 10 July 2024.  https://nodis3.gsfc.nasa.gov/displayDir.cfm?t=NPD&c=7120&s=6

[6]  NASA. NPR 7120.6, "NASA Lessons Learned Process," Chapter 1.  https://nodis3.gsfc.nasa.gov/displayCA.cfm?Internal_ID=N_PR_7120_0006_&page_name=Chapter1

[7]  NASA APPEL Knowledge Services. "Lessons Learned Lifecycle and Highlights."  https://appel.nasa.gov/lessons-learned/lessons-learned-lifecycle-and-highlights/

[8]  NASA. "Knowledge Management (KM) Resources." NASA HQ Library bibliography.  https://www.nasa.gov/general/knowledge-management-km-resources/

Government Audits & Investigations

[9]  NASA Office of Inspector General. "NASA's Process for Acquiring Information Technology Security Assessment and Monitoring Tools." Report IG-12-012, 6 March 2012 (lessons-learned audit findings).  https://oig.nasa.gov/wp-content/uploads/2024/02/IG-12-012.pdf

[10]  U.S. Government Accountability Office. "NASA: Better Mechanisms Needed for Sharing Lessons Learned." GAO-02-195, January 2002.  https://www.gao.gov/products/gao-02-195

Defense & Military AR/Maintenance Documentation

[11]  U.S. Army / DVIDS. "Augmented Reality Transforms Army Maintenance and Training." Image series from Fort Bliss, Texas, 14 April 2026 (4th Battalion, 27th Field Artillery Regiment).  https://www.dvidshub.net/image/9634766/augmented-reality-transforms-army-maintenance-and-training

[12]  U.S. Army. "Improving Warfighter Readiness Using Augmented Reality." Army.mil article, 25 March 2025.  https://www.army.mil/article/283803/improving_warfighter_readiness_using_augmented_reality

[13]  Booz Allen Hamilton. "Developing a Military First for AR and VR Training." Case study, 17 July 2025 (Fort Cavazos 5G XR system).  https://www.boozallen.com/insights/defense/developing-a-military-first-for-ar-and-vr-training.html

[14]  Taqtile. "Military Aircraft Maintenance Training with Augmented Reality." Manifest AR platform case study referencing AFIT study of jet-engine mechanic training.  https://taqtile.com/case-studies/jet-engine-maintenance/

[15]  U.S. Army SBIR/STTR Program. "Augmented Reality/Virtual Reality (AR/VR) for Railroad Inspection and Maintenance." Topic announcement.  https://armysbir.army.mil/topics/augmented-reality-virtual-reality-ar-vr-for-railroad-inspection-and-maintenance/

[16]  DiSTI Corporation. "VR Military Training & Simulation Solutions." Defense industry portfolio.  https://www.disti.com/marketing-solutions/defense

Aerospace Workforce & Knowledge-Transfer Analyses

[17]  Society of Manufacturing Engineers / advancedmanufacturing.org. "The $10M Knowledge Gap: When Your Experienced Supervisors Can't Transfer What They Know." 3 March 2026.  https://www.advancedmanufacturing.org/industries/aerospace-defense/the-10m-knowledge-gap-when-your-experienced-supervisors-can-t-transfer-what-they-know/article_9bce7393-744e-4c7c-b4a8-0050909329cd.html

[18]  Per Aspera. "Tribal Knowledge's Comeback." Industrial-policy analysis, June 2025 (Fogbank, plutonium-pit, F-1 cases).  https://www.peraspera.us/tribal-knowledges-comeback/

[19]  Siemens Digital Industries Software. "Workers Are Departing and It's Rattling the Aerospace Industry." 10 April 2020 (citing IEEE GlobalSpec 2019 Pulse of Engineering survey on tribal-knowledge concerns).  https://blogs.sw.siemens.com/ee-systems/2020/04/10/workers-are-departing-and-its-rattling-the-aerospace-industry/

Artemis I/II Heat-Shield Coverage

[20]  Space.com. "The Artemis 1 Moon Mission Had a Heat Shield Issue. Here's Why NASA Doesn't Think It Will Happen Again on Artemis 2." February 2026.  https://www.space.com/space-exploration/artemis/the-artemis-1-moon-mission-had-a-heat-shield-issue-heres-why-nasa-doesnt-think-it-will-happen-again-on-artemis-2

[21]  CBS News. "As Artemis II Heads Back to Earth, Crew Stakes Their Lives on the Heat Shield." April 2026.  https://www.cbsnews.com/news/artemis-ii-return-earth-heat-shield-reentry/

[22]  Spaceflight Now. "NASA Confident Artemis 2 Heat Shield Will Protect Crew During Re-entry." 10 April 2026.  https://spaceflightnow.com/2026/04/10/nasa-confident-artemis-ii-heat-shield-will-protect-crew-during-re-entry/

[23]  R&D World. "How NASA Engineered Around an Avcoat Failure for Artemis II." April 2026.  https://www.rdworldonline.com/how-nasa-engineered-around-a-known-avcoat-failure-mode-to-fly-artemis-iis-crew-safely-home/

[24]  New Space Economy. "The Orion Heat Shield: Description, Problems, Current Status, and What It Means for Artemis II." 3 April 2026 (citing NASA OIG January 2026 report).  https://newspaceeconomy.ca/2026/04/03/the-orion-heat-shield-description-problems-current-status-and-what-it-means-for-artemis-ii/

[25]  Live Science. "There's an Issue with the Artemis II Heat Shield, but NASA Isn't Worried. Here's Why." April 2026.  https://www.livescience.com/space/space-exploration/theres-an-issue-with-the-artemis-ii-heat-shield-but-nasa-isnt-worried-heres-why

F-1 Engine Reconstruction

[26]  SpaceRef. "NASA Engineers Resurrect and Test Mighty F-1 Engine Gas Generator." 24 May 2013 (interviews with Marshall propulsion engineers Nick Case, Kate Estes, Ryan Wall).  https://spaceref.com/science-and-exploration/nasa-engineers-resurrect-and-test-mighty-f-1-engine-gas-generator-3/

[27]  Space.com. "Blast from the Past: NASA Fires Historic Engine Parts for New Rocket." 22 January 2013.  https://www.space.com/19379-saturn-5-f1-engines-test-firing.html

[28]  The Space Review. "A Mighty Thunderous Silence: The Saturn F-1 Engine after Apollo." 3 June 2019 (history of F-1 Production Knowledge Retention program).  https://www.thespacereview.com/article/3724/1

[29]  Heroic Relics. "F-1 Rocket Engine Gas Generator." Reference compendium with 1961 Rocketdyne design documentation.  http://heroicrelics.org/info/f-1/f-1-gas-generator.html

[30]  Apollo11Space. "Why Can't We Remake the Rocketdyne F1 Engine?" 15 November 2024.  https://apollo11space.com/why-cant-we-remake-the-rocketdyne-f1-engine/

Industry & Manufacturing Context

[31]  Aerospace Manufacturing magazine. Latest industry news, April 2026 (B-21 Raider flight test, NASA X-59 progress, Hexagon laser-guided inspection systems).  https://www.aero-mag.com/

[32]  Orcalean. "Aerospace Manufacturing Strategies: How to Improve Performance in 2025 and 2026." 29 May 2025.  https://www.orcalean.com/article/aerospace-manufacturing-strategies:-how-to-improve-performance-in-2025-and-2026

[33]  TeepTrak. "US Aerospace Manufacturing OEE 2026 Guide." April 2026 (aerospace OEE benchmarks, documentation-burden analysis).  https://teeptrak.com/en/us-aerospace-manufacturing-oee-2026-guide/

Reference

[34]  Wikipedia. "AVCOAT." Composition history and Apollo-to-Orion reformulation.  https://en.wikipedia.org/wiki/AVCOAT

[35]  Wikipedia. "Rocketdyne F-1." Engine history including F-6049 serial-number reference and 2013 Marshall test campaign.  https://en.wikipedia.org/wiki/Rocketdyne_F-1

ABOUT THE BYLINE  Pseudo Publius is the byline used for civic and industrial-policy analysis directed at general aerospace and defense readership. The byline preserves the nonpartisan posture of affiliated nonprofit publications.

Two Centuries Under the Lens:

The Greenbelt Corridor From Bladensburg to Roman

A 19-square-mile patch of suburban Maryland captured by an astronaut from the International Space Station holds the densest concentration of U.S. military, aerospace, and civil-science heritage anywhere outside the National Mall — and is now the locus of three simultaneous federal disputes that will shape the next decade of civil space science.

 

By Pseudo Publius — Special to Aviation Week — April 24, 2026

BLUF — 

A NASA Earth Observatory Image of the Day released April 22, 2026, showing the I-495 corridor through Greenbelt, Maryland, captures one of the most institutionally dense rectangles in the United States. Within and immediately adjacent to the frame lie the August 24, 1814 battlefield at Bladensburg — the  ground over which a foreign army has fought and marched on the U.S. capital; College Park Airport, the world’s oldest continuously operating airport, established by the U.S. Army Signal Corps for the Wright Brothers in 1909; the 1798–1812 Rossborough Inn, predating the University of Maryland itself and used as a Confederate cavalry headquarters in 1864; the former Naval Ordnance Laboratory at White Oak, where Nitinol, Bismanol, the Polaris fuze, and Space Shuttle hypersonic models were developed and which now houses FDA headquarters; the Henry A. Wallace Beltsville Agricultural Research Center; the New Deal-era Old Greenbelt National Historic Landmark; and NASA’s Goddard Space Flight Center, the agency’s first space-flight complex, where the $4.3-billion Nancy Grace Roman Space Telescope completed final performance testing on April 21, 2026, ahead of a September 2026 Falcon Heavy launch. Three federal disputes are active in the same geography: a 25% Goddard footprint reduction under contested FY2026 budget authority; a federal lawsuit by Maryland and Prince George’s County over the diverted FBI headquarters site at Greenbelt Metro; and ongoing congressional review of preemptive science-mission terminations. Every layer in the photograph — from War of 1812 powder smoke to the dark-energy-survey telescope shipping to Cape Canaveral in June — is alive in some form on the public record this week.

The Frame From Orbit

Astronaut photograph ISS069-E-39302 was acquired with a Nikon D5 at 1,150 mm focal length on July 30, 2023, by a member of the Expedition 69 crew. The ISS Crew Earth Observations Facility and the Earth Science and Remote Sensing Unit at Johnson Space Center released the processed image on April 22, 2026, with annotations identifying Greenbelt Park, the Old Greenbelt historic district, the I-495 Capital Beltway, the University of Maryland in College Park, and Goddard Space Flight Center. The photograph — a near-vertical view from low Earth orbit at roughly 408 km altitude — resolves individual cul-de-sacs, the Beltsville Agricultural Research Center fields, and the parking lots of NASA’s east campus.

What the released frame does not annotate is two centuries of accumulated military, aviation, and scientific heritage running through the same ground — the historical layers that explain why so many federal institutions are clustered here, and why the contemporary disputes over their futures are politically combustible.

A 212-year corridor at a glance ·  

• 1798–1812 Rossborough Inn built on the Baltimore–Washington Turnpike (now U.S. Route 1) ·  
• Aug. 24, 1814 Battle of Bladensburg; British march on Washington · 
• 1856 Maryland Agricultural College chartered (today’s University of Maryland) ·  
• 1864 Confederate cavalry under Bradley T. Johnson occupies UMD campus ·  
• 1909 College Park Airport established for Wright Brothers Army training · 
• 1910 USDA acquires Walnut Grange plantation — nucleus of BARC ·  
• 1924 UMD opens dairy showroom on Route 1 (Turner Hall) ·  
• 1937 Old Greenbelt opens; first New Deal greenbelt town · 
• 1944–45 Naval Ordnance Laboratory built at White Oak ·  
• 1958 McKeldin Library opens at the head of McKeldin Mall ·  
• May 1, 1959 Beltsville Space Center renamed Goddard Space Flight Center · 
• Jan. 29–31, 1966 Blizzard of 1966 buries DC–Baltimore corridor · 
• Late 1960s UMD dairy herd put out to pasture · 
• 1997 NOL closed under BRAC; site to GSA ·  
• Sep. 24, 2001 F3 tornado tracks across UMD campus, killing two students ·  
• Aug. 23, 2011 5.8-magnitude Mineral, Va. earthquake; 13,500–27,000 books off McKeldin shelves 
• Nov. 2023 GSA selects Greenbelt for new FBI headquarters ·  
• Jul. 2025 Trump administration redirects FBI HQ to Reagan Building ·  
• Sep.–Nov. 2025 Goddard begins consolidation; library closed Jan. 3, 2026 ·  
• Nov. 6, 2025 Maryland sues over FBI HQ diversion ·  
• Apr. 21, 2026 Roman Space Telescope completes final testing

1814: The British March Through

The Anacostia River drainage that defines the southern edge of the orbital frame is the same ground over which Major General Robert Ross’s 4,500-man British expeditionary force advanced on August 24, 1814. Landed at Benedict, Maryland on August 19 and marched fifty miles overland from the Patuxent, Ross’s force — veterans of the Napoleonic Wars, freed for North American service after Napoleon’s April 1814 abdication — arrived at Bladensburg, four miles south of present-day College Park, around midday.

The American defense was a hastily assembled mix of approximately 6,500 regulars, militia, and a 400-sailor naval contingent under Commodore Joshua Barney, deployed under Brigadier General William H. Winder, a political appointee who had been captured the previous year at Stoney Creek. Most of the militia broke within the first hour. Barney’s sailors and Marines, manning naval guns at the third American line, fought to the point of being surrounded; Barney was wounded and captured. The rout — mocked in contemporary accounts as the “Bladensburg Races” and described by later historians as “the greatest disgrace ever dealt to American arms” — opened the road to Washington. Ross’s troops entered the capital that evening and burned the Presidential Mansion, the Capitol, the Treasury, the War Office, and the Navy Yard. It remains the only successful capture of the U.S. capital by a foreign power.

The lineages of two American units that fought at Bladensburg — the 5th Maryland Regiment and the Columbian Division — are perpetuated today by the 175th Infantry (Maryland Army National Guard) and the HHD/372nd Military Police Battalion (D.C. Army National Guard). The British battle honor “Bladensburg” was awarded to the 4th, 21st, 44th, and 85th Regiments of Foot. National Park Service interpretive infrastructure at Bladensburg Waterfront Park is being expanded under an American Battlefield Protection Program grant administered through the Anacostia Trails Heritage Area.

The Rossborough Inn: A Pre-Federal Survivor on Route 1

One mile east of the Bladensburg battlefield, on the same Baltimore–Washington Turnpike that became Route 1, the tavern-keeper John Ross began construction of a brick stagecoach inn in 1798; the building was complete and operating by 1803–04, with later finishing work documented through 1812. Ross had previously operated the Indian Queen Tavern in Bladensburg before purchasing roughly 200 acres in what is now College Park and naming the property “Ross Borough.”

By 1858, the property had passed to Charles Benedict Calvert, who incorporated the inn and 420 acres of his Riversdale plantation into the founding endowment of the Maryland Agricultural College. The Rossborough Inn is, accordingly, older than the institution that absorbed it. In July 1864, during Jubal Early’s raid on Washington, Confederate cavalry under Brigadier General Bradley Tyler Johnson briefly occupied the campus and used the building as headquarters. The Inn later housed the federally chartered Maryland Agricultural Experiment Station beginning in 1888, and was extensively renovated by the Works Progress Administration in 1937–38 at a cost of approximately $30,000 ($19,042 of which was the original WPA grant). Today the structure houses the University of Maryland’s Office of Undergraduate Admissions and remains the oldest building on campus and in College Park, fronting U.S. 1 a few hundred feet from the building — Turner Hall — that was the original 1924 home of the campus dairy.

McKeldin Library and the Campus’s Natural-Hazard Record

At the western anchor of McKeldin Mall — the largest academic mall in the United States — stands the Theodore R. McKeldin Library, opened in 1958 and named for the former Maryland governor. The eight-floor structure houses the university’s general collection, the East Asia Collection, and the regional Federal Depository Library serving Maryland, Delaware, and the District of Columbia (a status the UMD library system has held since 1925; the regional designation was awarded in 1965). The library predates the construction of the Capital Beltway and the establishment of Goddard Space Flight Center. Outside its main entrance — since 1965, when it was relocated there from Maryland Stadium and filled with approximately 700 pounds of cement and steel rods to discourage further theft — sits the original 1933 bronze Testudo statue by Aristide Cianfarani, the Class of 1933’s gift to the university. Generations of students have rubbed Testudo’s nose for luck on entering the library; the bronze on the snout is visibly polished as a result.

For the aerospace and defense reader, McKeldin is a less obvious data point than NASA Goddard or NOL White Oak, but its building has accumulated a quietly remarkable record of natural-hazard exposure that bears on infrastructure-resilience analysis for the broader corridor.

The Blizzard of 1966. The North American Blizzard of 1966 is the corridor’s benchmark winter event of the past sixty years. The nor’easter, which struck January 29–31, 1966 (with antecedent storms beginning January 22–23), produced 13.8 inches at Washington National Airport and 12.1 inches at Baltimore. Federal employees in Washington were excused from work on Monday, January 31; international airports closed from Boston to Washington; an estimated 201 deaths were attributed to the storm complex across the affected region from Tennessee to Maine. For UMD students of the 1965–66 academic year, the blizzard was the most significant disruption of the era, but it caused no structural impact on the campus.

The September 24, 2001 F3 tornado. A long-track multivortex F3 tornado — one of two spawned that afternoon by a supercell complex moving northeast under 45–55-knot wind shear — touched down in Crystal City, Virginia at 5:03 PM EDT and reached the College Park campus at approximately 5:24 PM. With peak winds estimated at over 200 mph — high enough that the storm would be classified EF5 under the post-2007 Enhanced Fujita scale — it produced an approximately 30 km damage track from west of the campus to Laurel and into Howard County, where it dissipated near Snowden River Parkway. On-campus damage included roof and window damage to Denton and Easton Halls, the destruction of the ten triple-wide and portable trailers then housing the Maryland Fire and Rescue Institute (MFRI) immediately north of the President’s Mansion, the displacement of 200–300 vehicles in Parking Lot 2, and roof damage to the newly opened Clarice Smith Performing Arts Center. Two University of Maryland undergraduates — sisters Colleen and Erin Marlatt, daughters of an MFRI staff member — were killed when their vehicle was lifted from a roadway and thrown approximately 300 yards into a wooded area; a third tornado-related death occurred elsewhere in the storm path. On-campus damage was estimated at $15 million, statewide damage at approximately $73 million, and damage across the entire path at over $100 million. Debris from the MFRI trailers was recovered up to 60 miles away in northern Harford County, Maryland and southern York County, Pennsylvania. McKeldin Library, then twelve hundred feet east of the tornado’s closest approach, sustained no significant damage.

The Mineral, Virginia earthquake of August 23, 2011. The library was less fortunate when, at 1:51 PM EDT on August 23, 2011, a magnitude 5.8 earthquake struck with epicenter near Mineral, Louisa County, Virginia — the strongest seismic event in the Eastern Seismic Zone since 1944, and the most widely felt earthquake in U.S. history by population. At McKeldin, contemporaneous staff estimates put the number of books shaken from shelves between 13,500 (UMD Libraries internal count) and approximately 27,000 (figure later cited by American Libraries Magazine and based on full clean-up tallies). Compact shelving on three floors was compromised; one unit tilted off its track. A free-standing bookshelf on the fourth floor collapsed. Surface cracks appeared in two stairwells and at the tops of pillars on the first floor. Library staff loaded the displaced volumes onto approximately 150 book carts within twenty-four hours; only about 700 items required preservation treatment. Materials also fell from shelves at Hornbake, Art, Architecture, and Engineering and Physical Sciences libraries. McKeldin Library was closed pending structural engineering review.

The same earthquake caused the closure of the Washington Monument until 2014 for repairs to its pyramidion, cracked the central tower of the National Cathedral, and delayed the dedication of the Martin Luther King Jr. Memorial. For the corridor under examination here, it is a useful reminder that even systems engineered for civilian use in the East — where seismic codes are less stringent than on the West Coast — are not immune to the kind of structural disruption that, in a different building, could have been catastrophic for irreplaceable holdings. The library’s 4-million-volume collection emerged with a documented loss of fewer than a thousand volumes requiring treatment.

1909: The Wright Brothers and the World’s Oldest Airport

Three miles north of the Rossborough Inn, on a 160-acre tract leased on August 25, 1909 by the U.S. Army Signal Corps and selected by Lieutenant Frank Lahm from a balloon ascent, College Park Airport (FAA LID: CGS) opened operations that fall when a Wright Type A biplane, uncrated October 7, was assembled and flown by Wilbur Wright. Wright’s assignment was to train the first two military pilots in the United States — Lieutenants Frederic Humphreys and Frank Lahm. The Army had moved its flight-training operation to College Park because Fort Myer’s parade ground, where Orville Wright had crashed in September 1908 (killing Lieutenant Thomas Selfridge, the first powered-flight fatality), was inadequate for sustained operations.

Civilian flight operations began at College Park in December 1911, establishing what the Federal Aviation Administration, Maryland Department of Transportation, and National Park Service all recognize as the world’s oldest continuously operating airport. Subsequent “firsts” at the field constitute a partial syllabus of early American aviation:

• 1909: Mrs. Ralph H. Van Deman, first woman in America to fly as an airplane passenger; Lt. George C. Sweet, USN, first naval officer to fly
• 1911: First U.S. Army flying school; instructors included future Army Air Forces commander then-Lt. Henry H. “Hap” Arnold and Lt. Thomas DeWitt Milling
• 1912: First testing of an aerial bomb sight and an aerial machine gun; Bernetta Adams Miller, first woman to demonstrate flight in a military aircraft (October 7)
• 1918: Inauguration of U.S. Post Office airmail service to Philadelphia and New York (Belmont Park) on August 12, with War Department trial flights beginning May 15
• 1920–24: Emile and Henry Berliner test the first helicopter with practical maneuvering capability
• Pre-WWII: First U.S. radio navigational aids for all-weather flight, and the first reported nighttime landing using acetylene ground lamps

The airport was placed on the National Register of Historic Places in 1977. The Maryland-National Capital Park and Planning Commission acquired the field in 1973 and operates it today; the adjacent 27,000-square-foot College Park Aviation Museum, opened September 12, 1998, holds Berliner Helicopter No. 5, a Wright Model B reproduction, and an original Curtiss-built Postal mail plane. Since 9/11, operations have been governed by Special Flight Rules Area restrictions imposed by TSA, FAA, and the Secret Service; pilots clear a one-time background check before being authorized to operate from the field.

1944–1997: Naval Ordnance Laboratory at White Oak

Twelve miles northwest of College Park, just across the Montgomery County line, the U.S. Navy began acquiring a 712-acre wooded site at 10903 New Hampshire Avenue in 1944 for the Naval Ordnance Laboratory. The lab was the lineal descendant of the Navy Mine Unit established at the Washington Navy Yard in 1918, which was merged with the Indian Head Experimental Ammunition Station in 1929 to form NOL. The Navy Yard had been overwhelmed by the magnitude of work required after the German aircraft-laid magnetic mine emerged as a strategic threat in early World War II.

NOL White Oak grew to over 300 buildings on a campus deliberately sited — in what was then farmland — well outside Washington under the wartime federal policy of dispersing mission-critical research from concentrated targets. (One Navy official, asked in 1945 whether the war would end before the laboratory was finished, replied: “That laboratory is not being built for this war.”) Functional groups were segregated by hazard category: administration and laboratories near the New Hampshire Avenue entrance, magnetics testing in the wooded 200 area, explosives storage and small-scale explosives testing, ballistics, and a hypersonic wind tunnel complex. The Phoenix/Casino building in the 100 area was used for nuclear-weapons radiation simulation of components and systems.

The technical output is hard to summarize briefly, but a partial list conveys the scope:

• Bismanol — an iron-manganese-bismuth permanent-magnet alloy (the “-nol” suffix is from NOL)
• Nitinol — nickel-titanium shape-memory alloy, named for nickel + titanium + NOL; now ubiquitous in medical stents, aerospace actuators, and seismic damping
• Polaris missile fuze work — carried out by Lee Reed and others, building on World War II proximity-fuze research
• Hypervelocity wind tunnel testing of Space Shuttle models for NASA
• Large Scale Gap Test (LSGT) — standard methodology for assessing shock sensitivity of solid rocket propellants
• Acoustics Division headed by John Vincent Atanasoff, inventor of the first electronic digital computer
• Laboratory work associated with two-time Nobel Prize physicist John Bardeen
• Cofounder of Teledyne, Inc., Henry Earl Singleton, was an NOL alumnus

Under BRAC 1991 the staff was reduced to 650; BRAC 1993 disestablished the laboratory entirely. Weapons-systems research transferred to NSWC Dahlgren, explosives research to NSWC Indian Head, and basic research to NSWC Carderock (the former David Taylor Model Basin). The site closed in 1997 and approximately 600 acres were conveyed to the General Services Administration as the Federal Research Center at White Oak; 137 acres had been transferred to the Army in 1969 for the Harry Diamond Laboratories (now the U.S. Army Research Laboratory’s Adelphi facility). Under the FDA Revitalization Act of 1990, with construction funding approved in 1999 and groundbreaking in 2000, 130 acres became the consolidated U.S. Food and Drug Administration headquarters. The former NOL Administration Building — with the words “Naval Ordnance Laboratory” still carved in stone above the main entrance — was renovated to LEED-NC 2.0 Gold standard in 2008 and now anchors the FDA campus, which the 2018 GSA master plan envisions accommodating up to 18,000 employees in approximately one million square feet of additional space. Trichloroethylene contamination from former NOL operations remains under active CERCLA management; an air-stripping unit treats groundwater migrating onto the adjacent Army property.

The Federal Cluster Visible in the Frame

The Beltsville Agricultural Research Center

The large green area in the upper portion of the orbital photograph — a mix of forested land and agricultural fields — is the Henry A. Wallace Beltsville Agricultural Research Center, established in 1910 when the Department of Agriculture purchased the 475-acre Walnut Grange plantation. The Wallace name was added in June 2000. BARC today operates more than 7,000 acres and houses the USDA Agricultural Research Service’s Animal Genomics and Improvement Laboratory; the laboratory’s long-running joint program with Israel’s Agricultural Research Organization on dairy-cattle genetic-evaluation methodology was recognized in September 2020 by the U.S.–Israel Binational Agricultural Research and Development (BARD) Fund as one of the top three most economically impactful projects in BARD’s 40-year history.

NASA’s Goddard Space Flight Center

NASA’s Goddard Space Flight Center, established as the agency’s first space-flight complex on May 1, 1959, occupies 1,270 acres immediately east of the Beltway. The land was carved directly from BARC; until May 1959, the facility was known officially as the Beltsville Space Center, and was renamed for rocketry pioneer Robert H. Goddard at the recommendation of NASA Administrator T. Keith Glennan. Goddard’s first 157 employees transferred from the Naval Research Laboratory’s Project Vanguard.

Goddard has been the integration and operations home of TIROS-1, the Cosmic Background Explorer, the Hubble Space Telescope, the Tracking and Data Relay Satellite System, the Lunar Reconnaissance Orbiter, the Solar Dynamics Observatory, the James Webb Space Telescope, and the upcoming Nancy Grace Roman Space Telescope. The center has held more than 800 patents, sent more than 300 satellites to orbit, and contributed to a Nobel Prize in physics. As recently as 2019, the workforce stood at approximately 13,000 civil servants and contractors. That figure now stands at approximately 6,600 — a one-third reduction in a single year — through buyouts, the federal Deferred Resignation Program, and early retirements.

The contraction follows the White House’s fiscal-year 2026 budget request, transmitted in May 2025, proposing an overall NASA top-line of approximately $18.8 billion (a 24% cut from FY2025) with science programs cut by roughly 47%. Under the proposal, Goddard would lose more than 42% of its remaining staff. Congress has not enacted the request: the House would hold NASA flat, and the Senate has proposed $24.4 billion. NASA continues to operate under continuing resolutions.

Despite the absence of an enacted budget, Goddard leadership began implementing a facilities consolidation plan in September 2025, with building closures continuing through the 43-day federal government shutdown that ended November 12, 2025. The International Federation of Professional and Technical Engineers, parent of the Goddard Engineers, Scientists and Technicians Association, reported in a November member brief that 13 buildings on the west side of the campus were marked for closure by March 2026, with nearly 100 laboratories to be emptied or displaced. The largest research library in NASA, holding more than 100,000 volumes including pre-digital mission documentation, was closed January 3, 2026. On October 30, 2025, the Senate Committee on Commerce, Science, and Transportation, under ranking member Maria Cantwell (D-Wash.), released findings concluding that NASA leadership had been prematurely implementing the FY2026 request before congressional enactment — a posture that, if sustained, raises Impoundment Control Act questions. NASA officials disputed the characterization. A 2025 executive order reclassified portions of NASA as covered by national-security exemptions, suspending collective-bargaining negotiations.

The Roman Counter-Narrative

Against this backdrop, Goddard delivered, on April 21, 2026, the most important programmatic milestone in U.S. astrophysics this decade: completion of comprehensive performance testing of the Nancy Grace Roman Space Telescope. Roman, a 2.4-m wide-field infrared observatory derived from a National Reconnaissance Office heritage primary mirror, will fly to Sun–Earth L2 aboard a SpaceX Falcon Heavy. NASA Administrator Jared Isaacman, announcing the milestone at Goddard, confirmed an early-September 2026 target launch — eight months ahead of the formal May 2027 commitment date — with the spacecraft to ship to Kennedy Space Center in mid-June. The mission has held to its $4.3 billion lifecycle cost. Roman’s 288-megapixel Wide Field Instrument will image fields roughly 200 times larger than Hubble’s WFC3, supporting three high-priority surveys (High-Latitude Wide-Area, High-Latitude Time-Domain, and Galactic Bulge Time-Domain) and demonstrating a Jet Propulsion Laboratory coronagraph instrument that is a critical pathfinder for the proposed Habitable Worlds Observatory. The FY2027 budget proposal, which Isaacman began defending before the House Science Committee on April 22, 2026, again seeks a 47% cut to NASA science and the cancellation of more than 50 missions including the Chandra X-ray Observatory.

Old Greenbelt: A New Deal Artifact Still in Use

The crescent-shaped historic district visible north of Greenbelt Park is the federally planned community of Old Greenbelt, one of three “greenbelt towns” built by the Resettlement Administration under economist Rexford G. Tugwell between 1935 and 1938. (The other two are Greenhills, Ohio, and Greendale, Wisconsin; a fourth, planned for New Jersey, was not built.) Construction was performed largely by Works Progress Administration labor; the Farm Security Administration added approximately 1,000 defense-housing units in 1941–42. The complete Greenbelt plans were reviewed at the White House by President and Mrs. Roosevelt on April 30, 1936; the first tenants moved in on September 30, 1937. The 756.8-acre district was placed on the National Register of Historic Places on November 25, 1980, and elevated to National Historic Landmark status on February 18, 1997. The federal government sold the housing stock to a veterans’ cooperative in December 1952; today, Greenbelt Homes, Inc., holds title to roughly 1,600 units, and the central Roosevelt Center grocery and the local newspaper (originally The Greenbelt Cooperator) remain cooperatively operated.

The FBI Headquarters Litigation

The Greenbelt Metro station, just north of the orbital frame, is the contested locus of the most consequential federal real-estate dispute in the corridor. After a 15-year process, GSA Administrator Robin Carnahan announced in November 2023 that Greenbelt had been selected from three congressionally designated sites — Greenbelt and Landover in Maryland and Springfield in Virginia — for the new FBI headquarters, citing taxpayer cost, transit access, and project-delivery certainty. Then-FBI Director Christopher Wray publicly disputed the process; the GSA Inspector General opened a probe; GSA legal counsel found Wray’s concerns to be without merit. Congress had appropriated more than $1.1 billion across multiple statutes between 2016 and 2024; Maryland and Prince George’s County had committed an additional $300 million in transportation and parking infrastructure based on the federal selection.

In July 2025, the FBI and GSA jointly announced that the bureau would instead occupy the Ronald Reagan Building and International Trade Center on Pennsylvania Avenue — a site not among the three Congress had designated. FBI Director Kash Patel cited cost-effectiveness; GSA documents indicated $1.4 billion in renovation costs at the Reagan Building, including $95 million in fire-protection upgrades and $38 million in structural repairs.

On November 6, 2025, Maryland Attorney General Anthony Brown and Prince George’s County filed suit in U.S. District Court against the Trump administration, seeking to block the Reagan Building selection and prevent diversion of approximately $555 million in already-appropriated funds. The complaint alleges that the executive branch ignored an explicit congressional directive limiting selection to the three pre-designated sites and that redirection of the funds requires affirmative action by the House Transportation and Infrastructure Committee and the appropriations panels — action that has not occurred. The state estimates the Greenbelt project would, if restored, produce 7,500 jobs and roughly $4 billion in regional economic activity. Governor Wes Moore, Senators Chris Van Hollen and Angela Alsobrooks, and Representative Glenn Ivey have publicly endorsed the litigation. The Department of Justice declined to comment on pending litigation; the General Services Administration, which under prior leadership had defended the Greenbelt selection, also declined to comment.

Why This Corridor Matters to the Aerospace Reader

The Greenbelt corridor has no production lines, no tier-one assembly facilities, no flight-test infrastructure of contemporary military significance. Its strategic value is institutional and historical: a 19-square-mile rectangle that has, in turn, hosted the only successful invasion of the U.S. capital, the world’s first military aviation training, the laboratory where Nitinol and the Polaris fuze were developed, the nation’s first land-grant agricultural research enterprise, the largest U.S. agricultural-research campus, NASA’s civil-science integration capability for Earth-observing, heliophysics, and astrophysics flagship missions, the principal land-grant university partner for that capability, and the federal law-enforcement real-estate dispute with the largest current dollar value.

The astronaut photograph released April 22, 2026, was almost certainly intended as a routine Earth Observatory feature on the New Deal-era greenbelt-town concept and the persistence of urban tree canopy. Its timing places it on the public record at a moment when much of the institutional infrastructure visible — and audible, in adjacent White Oak — is being restructured at a pace and under legal conditions that the affected agencies, unions, lawmakers, and Article III courts dispute.

For an aerospace audience, the relevant data point is straightforward. The Roman Space Telescope is on track to launch from Cape Canaveral in September 2026 on a Falcon Heavy — a mission planned, designed, and integrated in a campus where, six months earlier, employees were moving equipment out of laboratories during a federal government shutdown, on land originally carved from a USDA agricultural research station, three miles from where the Wright Brothers trained the first Army pilots, four miles from where the British army marched on Washington, and fifteen miles from where the Polaris missile fuze was perfected. Both kinds of facts are true at the same time. Both will continue to be true at least through the FY2027 budget cycle.

Author’s note: The author is a 1960s-era University of Maryland alumnus who shelved books part-time at the McKeldin Library and remembers the Blizzard of 1966 as the most significant natural-hazard event of his undergraduate years. The byline “Pseudo Publius” is used to preserve the nonpartisan character of the author’s patient-advocacy and civic-journalism affiliations.

Verified Sources

1. Hansen, K. “Belts of Green in the Washington Suburbs.” NASA Earth Observatory / NASA Science, April 22, 2026 (source of astronaut photograph ISS069-E-39302). https://science.nasa.gov/earth/earth-atmosphere/belts-of-green-in-the-washington-suburbs/
2. American Battlefield Trust. “Battle of Bladensburg.” https://www.battlefields.org/learn/war-1812/battles/bladensburg
3. U.S. National Park Service. “Summer 1814: American troops flee in humiliation, leaving Washington exposed.” https://www.nps.gov/articles/bladensburg-races.htm
4. U.S. National Park Service. “Never the Same River Twice: Interpreting the War of 1812’s Battle of Bladensburg.” https://www.nps.gov/articles/000/never-the-same-river-twice-interpreting-the-war-of-1812-s-battle-of-bladensburg.htm
5. Town of Bladensburg, Maryland. “Battle of Bladensburg.” https://www.bladensburgmd.gov/community/about_us/history/battle_of_bladensburg.php
6. Battle of Bladensburg Visitor Center. “History.” https://www.battleofbladensburg.org/history
7. Rickard, J. “Battle of Bladensburg, 24 August 1814.” HistoryOfWar.org, December 11, 2007. https://www.historyofwar.org/articles/battles_bladensburg.html
8. U.S. National Park Service. “College Park Airport.” https://www.nps.gov/articles/college-park-airport.htm
9. College Park Airport (KCGS) official site. https://collegeparkairport.aero/
10. College Park Aviation Museum / Field of Firsts. https://www.fieldoffirsts.com/about-the-museum
11. Maryland-National Capital Park and Planning Commission. “College Park Airport.” https://www.pgparks.com/facilities/college-park-airport
12. Living New Deal. “Rossborough Inn Improvements, University of Maryland.” https://livingnewdeal.org/sites/rossborough-inn-improvements-university-of-maryland-college-park-md/
13. Historical Marker Database. “The Rossborough Inn.” https://www.hmdb.org/m.asp?m=66433
14. University of Maryland Libraries. “The Rossborough Inn on the University of Maryland Campus: Two Centuries of Change.” https://drum.lib.umd.edu/items/48828c4a-c961-4fe6-9a71-a77eb17fcde7
15. Naval Ordnance Laboratory entry, Wikipedia (verified against Montgomery County Planning historical-preservation testimony cited below). https://en.wikipedia.org/wiki/Naval_Ordnance_Laboratory
16. Montgomery County Planning Department / Historic Preservation Commission. “Historic Background for the Naval Ordnance Laboratory Administration Building.” June 27, 2013 staff memorandum to the Planning Board. http://www.montgomeryplanning.org/community/wosg/documents/AppendixFHistoricBackgroundfortheNavalOrdnanceLaboratoryAdministrationBuilding.pdf
17. National Capital Planning Commission. “FDA White Oak Final Master Plan / Memorandum of Agreement.” https://www.ncpc.gov/files/projects/2018/MP201_..._White_Oak_..._MOA_Dec2018.pdf
18. Maryland Department of the Environment. “Naval Surface Warfare Center White Oak Detachment.” (Brownfield site documentation.) https://mde.maryland.gov/programs/Land/MarylandBrownfieldVCP/Documents/.../nswcwhiteoak_mc_pg.pdf
19. NASA. “Goddard Space Flight Center History.” https://www.nasa.gov/goddard/history/
20. NASA. “NASA’s Goddard Space Flight Center Celebrates 60 Years.” (Archival release.) https://www.nasa.gov/news-release/nasas-goddard-space-flight-center-celebrates-60-years/
21. NASA. “NASA Targets Early September for Roman Space Telescope Launch.” April 22, 2026. https://www.nasa.gov/image-article/nasa-targets-early-september-for-roman-space-telescope-launch/
22. Foust, J. “NASA sets early September launch date for Roman Space Telescope.” SpaceNews, April 22, 2026. https://spacenews.com/nasa-sets-early-september-launch-date-for-roman-space-telescope/
23. NASA. “NASA Completes Nancy Grace Roman Space Telescope Construction.” November 25, 2025. https://www.nasa.gov/missions/roman-space-telescope/nasa-completes-nancy-grace-roman-space-telescope-construction/
24. Dinner, J. “NASA is sinking its flagship science center during the government shutdown.” Space.com, October 31, 2025. https://www.space.com/space-exploration/nasa-is-sinking-its-flagship-science-center-during-the-government-shutdown-and-may-be-breaking-the-law-in-the-process
25. Brown, D. J. “NASA moves quickly on plan to shrink Goddard campus by 25%.” Maryland Matters, November 23, 2025. https://marylandmatters.org/2025/11/23/nasa-moves-quickly-on-plan-to-shrink-goddard-campus-by-25/
26. World Socialist Web Site. “NASA closes Goddard Space Flight Center library as it dismantles astronomy infrastructure.” January 20, 2026. https://www.wsws.org/en/articles/2026/01/20/evzh-j20.html
27. Gibney, M. “NASA’s Goddard Space Flight Center hit by significant downsizing.” Physics World, November 13, 2025. https://physicsworld.com/a/nasas-goddard-space-flight-center-hit-by-significant-downsizing/
28. Obis, A. “NASA workers, supporters protest deep funding, staffing cuts.” Federal News Network, September 18, 2025. https://federalnewsnetwork.com/workforce/2025/09/nasa-workers-supporters-protest-deep-funding-staffing-cuts/
29. Maryland Office of the Attorney General. “Attorney General Brown and Prince George’s County Sue Trump Administration to Stop Unlawful Diversion of FBI Headquarters Project from Maryland.” Press release, November 6, 2025. https://oag.maryland.gov/News/Pages/Attorney-General-Brown-and-Prince-George%E2%80%99s-County-Sue-Trump-Administration...
30. CBS Baltimore (WJZ). “Maryland sues Trump administration for blocking FBI headquarters move to Prince George’s County.” November 6, 2025. https://www.cbsnews.com/baltimore/news/maryland-lawsuit-trump-administration-fbi-headquarters-greenbelt/
31. U.S. National Park Service. “Greenbelt Historic District.” https://www.nps.gov/places/greenbelt-historic-district.htm
32. National Historic Landmark nomination, Greenbelt Historic District. NPS NRHP/NHL records. https://npgallery.nps.gov/NRHP/GetAsset/NHLS/80004331_text
33. Greenbelt Museum. “Greenbelt History.” https://www.greenbeltmuseum.org/greenbelt-history
34. Living New Deal. “Old Greenbelt Planned Community.” https://livingnewdeal.org/sites/old-greenbelt-planned-community-greenbelt-md/
35. USDA Agricultural Research Service. “Beltsville Agricultural Research Center.” https://www.ars.usda.gov/northeast-area/beltsville-md-barc/beltsville-agricultural-research-center/
36. Maryland Department of Commerce. “BARC — Henry A. Wallace Beltsville Agricultural Research Center.” https://commerce.maryland.gov/Documents/BusinessResource/BARC-Henry-A-Wallace-Beltsville-Agricultural-Resource-Center.pdf
37. Maryland State Archives. “University of Maryland, College Park — Historical Evolution.” https://msa.maryland.gov/msa/mdmanual/25univ/umcp/html/umcph.html
38. Maryland Today. “What It Takes: The Campus Farm.” September 2025. https://today.umd.edu/what-it-takes-the-campus-farm
39. Terp Magazine (UMD Alumni Association). “Still Cool, 100 Years Later.” November 2025. https://terp.umd.edu/still-cool-100-years-later
40. Baltimore Sun. “College dairy bar sticks to tradition.” November 15, 1995 (archival). https://www.baltimoresun.com/news/bs-xpm-1995-11-15-1995319105-story.html
41. University of Maryland Libraries entry, Wikipedia (verified against UMD Libraries primary site). https://en.wikipedia.org/wiki/University_of_Maryland_Libraries
42. UMD Libraries. “McKeldin Library.” https://www.lib.umd.edu/visit/libraries/mckeldin
43. Maryland Today. “Standing the Testudo of Time.” September 2025. https://today.umd.edu/standing-the-testudo-of-time
44. UMD Libraries Exhibitions. “Testudo” (MAC to Millennium). https://exhibitions.lib.umd.edu/macmil/testudo
45. Charleston Hub. “Earthquake Update: University of Maryland.” August 26, 2011 (UMD Libraries press communication). https://www.charleston-hub.com/2011/08/earthquake-update-university-of-maryland/
46. The Diamondback (UMD student newspaper). “Earthquake rocks campus; no damages or injuries reported.” August 23, 2011. https://dbknews.com/0999/12/31/arc-evlvf3dssjewvijlnnpaic4pgm/
47. American Library Association. “East Coast Libraries Endure Hurricane Irene.” American Libraries Magazine, August 31, 2011 (citing approximately 27,000 books displaced from McKeldin shelves). https://americanlibrariesmagazine.org/2011/08/31/east-coast-libraries-endure-hurricane-irene/
48. Tornado Talk. “College Park, MD F3 Tornado — September 24, 2001.” (Detailed damage survey with NWS Sterling and University of Maryland Archives photo support.) https://www.tornadotalk.com/college-park-md-f3-tornado-september-24-2001/
49. National Weather Service Baltimore/Washington Forecast Office. “September 2001 Storm Data.” https://www.weather.gov/media/lwx/stormdata/2001/storm0901.pdf
50. Zhang, D.-L., et al. “The College Park, Maryland, Tornado of 24 September 2001.” Geosciences 9(10):452 (2019). MDPI. https://www.mdpi.com/2076-3263/9/10/452
51. UMD Department of Atmospheric and Oceanic Science. “Tornado Hit College Park on 24 September 2001.” (Photographic record by Dr. Ming-Ying Wei.) https://www2.atmos.umd.edu/~dalin/tornado9-24.html
52. Capital News Service Maryland. “10 Years Later: Remembering the College Park Tornado.” October 5, 2011. https://cnsmaryland.org/2011/10/05/10-years-later-remembering-the-college-park-tornado/
53. North American blizzard of 1966 entry, Wikipedia (verified against AccuWeather and Washington Post retrospectives below). https://en.wikipedia.org/wiki/North_American_blizzard_of_1966
54. AccuWeather. “60 years ago, a record blizzard killed 200 people in the Northeast.” January 30, 2026. https://www.accuweather.com/en/winter-weather/60-years-ago-a-record-blizzard-killed-200-people-in-the-northeast/1858079
55. WUSA9. “DC’s 15 worst winter storms of all time.” (Tabular reference for 1966 totals at Washington National and Baltimore.) https://www.wusa9.com/article/weather/weather-blog/65-598322161