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.