Protecting Innovation While Enabling Readiness
The debate over right to repair in the defense sector has intensified as Congress considers sweeping changes to data access and repair rights. Efforts to improve system readiness and reduce sustainment costs are clearly essential, but emerging legislative proposals risk unintended consequences for national defense. This article outlines the core engineering, acquisition, and industrial implications of proposed mandates while highlighting opportunities to preserve innovation, security, and warfighter readiness through carefully scoped data-access policies. As the world’s largest aerospace technical society, the American Institute of Aeronautics and Astronautics (AIAA) presents this perspective to ensure the ongoing modernization of the U.S. defense capabilities is grounded in technical rigor and operation urgency.
The Issue: Readiness vs. Rights
As the United States seeks to rapidly modernize and scale its military capabilities, issues of system readiness and lifecycle sustainment have gained increasing importance. Congress is rightly focused on ensuring field-level maintainers, whether uniformed, contracted, or civilian, can service the complex systems required for modern warfighting. However, legislative proposals inspired by the consumer right-to-repair movement may unintentionally disrupt the aerospace and defense innovation base.
Recent legislation have proposed sweeping mandates to force original equipment manufacturers (OEMs) to share data that includes detailed repair manuals, technical drawings, and even source code, commonly considered as proprietary information, with third parties not involved in the original system design. While this may echo consumer-facing debates over smartphones or tractors, it could create a risk in a military context where readiness, system integrity, and national security are directly impacted.
Proponents of right to repair argue that unnecessary repair bottlenecks can degrade readiness, drive up costs, and limit operational flexibility. They cite examples in consumer electronics, farm equipment, and medical supplies. However, defense systems are not consumer products. They are often software intensive, targets for cyber-attacks, and safety critical platforms developed through tightly integrated design, test, and qualification processes. In this context, poorly scoped mandates requiring the disclosure of proprietary information could compromise system performance and integrity, fracture accountability, and disincentivize innovation.
The Stakes for Defense Innovation
The U.S. defense ecosystem relies on a balance between public acquisition authority and private sector innovation. Many systems are developed through cost sharing, where companies invest significant private capital into early design, modeling, and testing long before a formal contract is awarded. As a result, intellectual property (IP) protections, especially around technical data, design drawings, and digital twins, play a vital role in incentivizing this upfront investment.
Under current law (10 U.S.C. § 3771–3773), the Pentagon receives unlimited rights to any deliverable technical data developed entirely with government funding. For privately funded data, the government typically retains limited rights, which permit internal use but may restrict third-party access or depot-level repair activities. While this framework preserves critical IP protections, it can also create barriers to timely maintenance if key technical data falls under limited rights and is not otherwise accessible. While not a perfect framework, this carefully constructed legal balance preserves operational readiness and protects innovation incentives. That said, targeted updates grounded in technical rigor may be warranted to expand government access while maintaining the U.S. innovation edge.
Emerging legislative proposals risk upsetting this balance. Mandating third-party disclosure of proprietary information, even for systems developed without government funds could undermine innovation incentives established through longstanding public and private intellectual property. Therefore, defense primes, mid-tier suppliers, and non-traditional entrants may become reluctant to offer their best or most advanced technologies upfront, particularity if they believe that doing so will expose proprietary information to third parties or create long-term disadvantages.
This could quickly erode the very goals that right-to-repair advocates seek to advance. Instead of accelerating repair timelines or lowering costs, such provisions could easily reduce market competition, limit innovation, and fragment accountability. In high consequence environments such as aerospace and defense, design and repair authority cannot be fully decoupled without risking cascading performance issues.
Additionally, some suppliers warn that mandates to share data with unauthorized repair vendors could jeopardize product warranties, interfere with safety critical certifications, or introduce cyber vulnerabilities. These are not speculative concerns; they have already been raised by defense contractors and have affected product offering and support.
Finding the Balance: A Path Forward
Policymakers must thread a difficult, but essential needle to ensure warfighting readiness without compromising national security, supply chain integrity, or innovation incentives. To that end, the most productive path forward is not to oppose right to repair outright, but rather distinguish who gets access to what data, and under what conditions. Not all repair scenarios or data types are equal in this space.
Instead of mandating broad third-party access to design data, a more durable approach could involve the following:
- Under current statute, the government retains certain rights for technical data funded entirely through public dollars. However, critics have noted that these protections can still allow cost inefficiencies or delays, especially when IP restrictions limit third-party repair or depot-level solutions. Thoughtful reform should address these operational pain points while preserving incentives for cutting-edge R&D.
- Expanding secure, OEM-backed data-as-a-services (DaaS) models would allow military repair personnel to 3D print or source parts under time-sensitive conditions, while maintaining design traceability, cyber integrity, and performance accountability.
- Funding the Pentagon Sustainment Enterprise to invest in digital sustainment tools, model-based systems engineering (MBSE), and smart diagnostics infrastructure will reduce dependency on outside vendors over time.
- Encouraging modular open systems architecture approaches (MOSA) will ensure long-term upgradeability without compromising baseline system integrity.
These reforms would empower field maintainers, improve logistics timelines, and reinforce repair agility without requiring indiscriminate disclosure of trade secrets or proprietary manufacturing techniques. The goal is not to deny the right to repair but to enhance the current public and private framework by ensuring government access to essential data, reducing sustainment costs, and improving readiness without undermining the innovation ecosystem that enables national security superiority.
Considerations for Policymakers
AIAA recommends Congress consider the following principles when evaluating future proposals:
- Try not to conflate commercial and military domains: consumer right-to-repair paradigms cannot be cut and pasted into national defense contexts without serious risk. National security systems, given their complexity and mission critical nature, inherently require different standards and levels of data access than consumer goods. Applying consumer repair frameworks to defense acquisition may conflate fundamentally different risk, safety, and strategic considerations.
- Exercise discretion when directing IP or repair access requirements, recognizing the diverse technical and contractual realities across defense platforms. Assertions of improved access or cost savings must be carefully evaluated and validated to ensure they do not introduce unintended vulnerabilities or trade-offs in mission assurance or supply chain resilience.
- Invest in digital sustainment and field-level innovation: Congress can accelerate readiness gains by funding OEM-certified tools, DaaS models, and trusted government sustainment facilities or depots with appropriate clearances and infrastructure to manage sensitive components.
- Preserve incentives for innovation: IP protections aren’t a loophole, rather they’re a cornerstone of defense innovation. Undermining these protections may hinder the Pentagon’s ability to access cutting-edge capabilities on acceptable timelines.
- Convene neutral technical experts: Congress should consult with independent engineering societies, systems integrators, and acquisition professionals to fully understand the readiness, cybersecurity, and performance trade-offs involved in any proposal.
Conclusion
The goals of right-to-repair advocates and the defense acquisition community are not mutually exclusive. Both seek a stronger, more responsive sustainment enterprise. In the national security arena, however, how those goals are achieved matters.
Done well, Congress can enhance system readiness without undermining innovation or exposing vulnerabilities. If done poorly, it risks incentivizing system fragmentation, vendor attrition, and unintended supply chain fragility.
AIAA stands ready to assist Congress, the Pentagon, and industry as a neutral, technically credible partner, committed to ensuring smart sustainment reforms enhance and not erode U.S. warfighting readiness.
