Congress Keeps Saying America Needs ‘Right to Repair.’ Then It Quietly Carved Out the One Place It Matters Most: the U.S. Military.
In public, lawmakers call military right to repair “common sense.” In NDAA conference rooms, the enforceable language keeps disappearing—right where readiness depends on it most: data, diagnostics, and permission to fix what the Pentagon already owns.
By TheMurrow Editorial
March 21, 2026
Key Points
- 1Track how NDAA “right to repair” language repeatedly appears, then vanishes in conference—where IP, pricing terms, and lobbying collide.
- 2Understand the real bottleneck: technical data rights, diagnostics, manuals, and software licenses—not whether maintainers can physically do repairs.
- 3Watch Section 828 (FY2025) and FY2026 §§836/863 as case studies in how sustainment profits shape readiness and contractor dependence.
The most expensive wrench in the Pentagon is the one it isn’t allowed to use.
For years, lawmakers have praised “right to repair” as common sense: if the U.S. buys equipment, the military should be able to fix it. Yet when the fight moved from speeches to statutory language—where contracts, intellectual property, and pricing collide—Congress repeatedly backed away. Not in a dramatic floor vote. In conference rooms, in edits that look like housekeeping, in provisions that appear and then vanish.
The story of military right to repair is not really about screwdrivers and spare parts. It’s about authority. Who gets to diagnose a failure, access the manuals, run the software, order the components, and do the work—uniformed maintainers and government depots, or the original manufacturer that built the system and wants to keep the sustainment business.
The consequence is felt far from Capitol Hill: when a vehicle, aircraft, or critical system sits deadlined because the unit can’t get the diagnostic tool, the technical manual, or the permission to proceed. That is what “right to repair” means in the defense world—and why it keeps getting quietly carved out where it matters most.
The fight isn’t over whether the military can hold a wrench. It’s over whether it can legally use the information that makes the wrench useful.
What “Right to Repair” Means for the Pentagon—And Why It’s Not Like Your Phone
In consumer technology, right to repair is often framed as freedom: the ability to fix your own device rather than being forced into a manufacturer’s service channel. In the military, the stakes are less personal and more structural. The central question is whether the Department of Defense has sustainment authority—the practical and legal ability to diagnose, maintain, and repair systems it already owns.
That authority is often limited by three obstacles that show up repeatedly in policy debates:
- Contract terms that require original equipment manufacturer (OEM) involvement for certain repairs
- Lack of technical data: manuals, schematics, test procedures, and diagnostic software
- Data rights and IP licensing constraints that determine what the government is allowed to do with contractor-developed information and software
The Government Accountability Office has framed the problem plainly: DoD needs intellectual property and data rights to maintain weapon systems, and weak planning or management around those rights can increase sustainment costs and extend repair timelines. GAO’s warning is not abstract; it’s a critique of how the government buys systems and then discovers—often too late—that it does not have what it needs to keep them running. (GAO, “DoD needs IP and data rights…; insufficient planning/management… can drive up sustainment costs and increase repair time.”)
Source: gao.gov/products/gao-25-107468
That authority is often limited by three obstacles that show up repeatedly in policy debates:
- Contract terms that require original equipment manufacturer (OEM) involvement for certain repairs
- Lack of technical data: manuals, schematics, test procedures, and diagnostic software
- Data rights and IP licensing constraints that determine what the government is allowed to do with contractor-developed information and software
The Government Accountability Office has framed the problem plainly: DoD needs intellectual property and data rights to maintain weapon systems, and weak planning or management around those rights can increase sustainment costs and extend repair timelines. GAO’s warning is not abstract; it’s a critique of how the government buys systems and then discovers—often too late—that it does not have what it needs to keep them running. (GAO, “DoD needs IP and data rights…; insufficient planning/management… can drive up sustainment costs and increase repair time.”)
Source: gao.gov/products/gao-25-107468
Three recurring obstacles to sustainment authority
- ✓Contract terms that require OEM involvement for certain repairs
- ✓Lack of technical data: manuals, schematics, test procedures, and diagnostic software
- ✓Data rights and IP licensing constraints that determine what the government may do with contractor-developed information and software
The practical effect: slower repairs, higher bills, weaker readiness
Policymakers and watchdogs describe a familiar chain reaction when repair authority is constrained. Units wait for OEM field service representatives. Components get shipped back rather than fixed locally. Sole-source arrangements turn routine sustainment into premium-priced service.
Those delays and markups are not mere annoyances. For the military, they translate into systems that remain “deadlined”—unavailable for operations—because the repair pathway runs through a contractor gatekeeper.
Those delays and markups are not mere annoyances. For the military, they translate into systems that remain “deadlined”—unavailable for operations—because the repair pathway runs through a contractor gatekeeper.
A deadlined system isn’t always broken beyond repair. Sometimes it’s broken beyond permission.
The Core Policy Clash: Readiness vs. Intellectual Property
Right to repair sounds simple until it collides with the modern defense economy, where sustainment can be as lucrative as production and where proprietary tools are treated as competitive advantage.
Reformers argue the government has accepted a bad bargain: it buys platforms without securing the data and rights needed to maintain them independently. Industry and OEMs counter that broad mandates risk forcing disclosure of trade secrets and could distort pricing and distribution models.
Both sides can point to real concerns; the conflict is over where the line belongs.
Reformers argue the government has accepted a bad bargain: it buys platforms without securing the data and rights needed to maintain them independently. Industry and OEMs counter that broad mandates risk forcing disclosure of trade secrets and could distort pricing and distribution models.
Both sides can point to real concerns; the conflict is over where the line belongs.
The reformers’ case: stop buying dependency
Repair advocates, some lawmakers, and watchdog groups argue DoD too often lacks the technical data rights required for:
- In-house repair by uniformed maintainers
- Sustainment at government depots
- Competitive contracting for maintenance rather than sole-source OEM service
They frame the issue as a triangle of priorities: readiness, affordability, and competition. The readiness claim is intuitive—field repair matters. The affordability claim often appears in political messaging as “billions” in potential savings, though the specific figures vary by system and are not settled by the research cited here. The competition claim is a structural warning: when only one entity has the data and tools, “competition” becomes rhetorical.
Sen. Elizabeth Warren’s office, for example, promoted right-to-repair language as a direct readiness measure and publicly described contractor opposition to it.
Source: warren.senate.gov/newsroom/press-releases/warren-leads-charge-to-protect-military-readiness-takes-on-defense-contractors-seeking-to-block-the-militarys-right-to-repair-its-weapons-and-equipment
- In-house repair by uniformed maintainers
- Sustainment at government depots
- Competitive contracting for maintenance rather than sole-source OEM service
They frame the issue as a triangle of priorities: readiness, affordability, and competition. The readiness claim is intuitive—field repair matters. The affordability claim often appears in political messaging as “billions” in potential savings, though the specific figures vary by system and are not settled by the research cited here. The competition claim is a structural warning: when only one entity has the data and tools, “competition” becomes rhetorical.
Sen. Elizabeth Warren’s office, for example, promoted right-to-repair language as a direct readiness measure and publicly described contractor opposition to it.
Source: warren.senate.gov/newsroom/press-releases/warren-leads-charge-to-protect-military-readiness-takes-on-defense-contractors-seeking-to-block-the-militarys-right-to-repair-its-weapons-and-equipment
The industry case: don’t mandate the surrender of trade secrets
Industry groups and OEM-aligned coalitions argue that some legislative proposals go too far—requiring access to “all repair materials and information” without sufficient carve-outs, and potentially imposing pricing controls that disrupt normal commercial channels. One coalition letter opposing a Senate provision argued it threatened proprietary information and included pricing requirements.
Sources: documents.nam.org/LLRP/Signed.FY25.NDAA.Section.828.Letter.pdf; irrigation.org (coalition letter)
The trade-secret concern matters because modern military equipment often depends on embedded software and proprietary diagnostics. A requirement drafted too broadly could, in industry’s view, function as compelled disclosure—especially if “repair” is defined expansively.
The pricing concern is also concrete. If Congress requires “most favorable” pricing terms, contractors fear it could ripple beyond defense contracts into wider dealer and distribution arrangements.
Sources: documents.nam.org/LLRP/Signed.FY25.NDAA.Section.828.Letter.pdf; irrigation.org (coalition letter)
The trade-secret concern matters because modern military equipment often depends on embedded software and proprietary diagnostics. A requirement drafted too broadly could, in industry’s view, function as compelled disclosure—especially if “repair” is defined expansively.
The pricing concern is also concrete. If Congress requires “most favorable” pricing terms, contractors fear it could ripple beyond defense contracts into wider dealer and distribution arrangements.
The Business Model Behind the Rhetoric: Sustainment Is Where the Money Lives
Defense procurement debates often sound ideological—government power versus private innovation—but the right-to-repair fight is also financial. OEMs don’t just sell equipment; they sell what comes after: sustainment, service, software updates, diagnostics, and parts supply.
That downstream revenue helps explain why right to repair draws intense lobbying. Reporting has highlighted how reform efforts threaten contractor sustainment income and how lobbying pressure shapes what survives the NDAA process.
Source: wired.com/story/the-military-almost-got-the-right-to-repair-lawmakers-just-took-it-away/
That downstream revenue helps explain why right to repair draws intense lobbying. Reporting has highlighted how reform efforts threaten contractor sustainment income and how lobbying pressure shapes what survives the NDAA process.
Source: wired.com/story/the-military-almost-got-the-right-to-repair-lawmakers-just-took-it-away/
A quieter form of lock-in: tools, software, and the keys to diagnosis
Vendor dependence does not always look like a monopoly contract. Sometimes it looks like a missing manual, a locked diagnostic port, or software the government can’t legally use without a license it didn’t negotiate.
GAO’s emphasis on planning and managing data rights underscores a critical point for readers: the government’s leverage is greatest before signing the contract. After a system is fielded, the military’s need for uptime becomes a bargaining disadvantage. The more urgent the readiness requirement, the more expensive sole-source service becomes.
GAO’s emphasis on planning and managing data rights underscores a critical point for readers: the government’s leverage is greatest before signing the contract. After a system is fielded, the military’s need for uptime becomes a bargaining disadvantage. The more urgent the readiness requirement, the more expensive sole-source service becomes.
Real-world implication: repair becomes permissioned
Even when maintainers are capable, capability does not equal authorization. If a contract requires OEM involvement, or if technical data is withheld, the repair pipeline becomes permissioned.
The result isn’t merely “inefficiency.” It is operational vulnerability: a system’s readiness depends not only on supply chains and maintenance skill, but on whether the government negotiated the rights to act.
The result isn’t merely “inefficiency.” It is operational vulnerability: a system’s readiness depends not only on supply chains and maintenance skill, but on whether the government negotiated the rights to act.
When sustainment is a profit center, dependence isn’t a bug—it’s a feature.
The FY2025 Senate Attempt: Section 828 and the “Fair and Reasonable Access” Standard
The most concrete recent attempt to legislate a defense right to repair arrived in the Senate version of the FY2025 National Defense Authorization Act (NDAA): Section 828 of S. 4638.
Section 828 proposed adding 10 U.S.C. § 4663, titled: “Requirement for contractors to provide reasonable access to repair materials.”
Source: nationalguard.mil/…/FY25%20NDAA%20Bill%20%28S4638%29.pdf
Section 828 proposed adding 10 U.S.C. § 4663, titled: “Requirement for contractors to provide reasonable access to repair materials.”
Source: nationalguard.mil/…/FY25%20NDAA%20Bill%20%28S4638%29.pdf
What Section 828 tried to do
The Senate language aimed to create a statutory expectation that contractors provide “fair and reasonable access” to repair materials—covering the practical items that make sustainment possible: parts, tools, and information. Crucially, it also included terms tied to “most favorable” pricing and conditions offered through the manufacturer or authorized channels, language that became a focal point for opponents.
Key statistic #1: The proposal would have written a new provision into federal law—10 U.S.C. § 4663—a rare elevation of sustainment access from policy preference to statutory requirement.
Source: S.4638 text hosted by nationalguard.mil
Key statistic #1: The proposal would have written a new provision into federal law—10 U.S.C. § 4663—a rare elevation of sustainment access from policy preference to statutory requirement.
Source: S.4638 text hosted by nationalguard.mil
10 U.S.C. § 4663
Section 828 would have created a new federal statute: “Requirement for contractors to provide reasonable access to repair materials.”
Why opposition was immediate
In July 2024, industry associations publicly opposed Section 828. A letter circulated by a broad coalition argued the provision was overbroad, threatened proprietary information, and imposed pricing constraints.
Source: documents.nam.org/LLRP/Signed.FY25.NDAA.Section.828.Letter.pdf
The critique was not purely theoretical. If “repair materials and information” is interpreted expansively, it could compel sharing proprietary diagnostics or software. If “most favorable” pricing becomes a statutory standard, contractors fear it could force defense-specific pricing rules into broader commercial arrangements.
Reformers saw the same language as the point: without enforceable access on reasonable terms, the government remains stuck paying what the only available seller demands.
Source: documents.nam.org/LLRP/Signed.FY25.NDAA.Section.828.Letter.pdf
The critique was not purely theoretical. If “repair materials and information” is interpreted expansively, it could compel sharing proprietary diagnostics or software. If “most favorable” pricing becomes a statutory standard, contractors fear it could force defense-specific pricing rules into broader commercial arrangements.
Reformers saw the same language as the point: without enforceable access on reasonable terms, the government remains stuck paying what the only available seller demands.
Key Insight
In this fight, the stakes aren’t “can someone repair it?” but “who controls the manuals, diagnostics, software licenses, and terms of access?”
The FY2026 Repeat—and the Conference Room Deletion
By late 2025, right-to-repair language resurfaced in both chambers’ FY2026 NDAA drafts. The Senate version included Section 836; the House version included Section 863. Both were widely described as “right to repair” provisions designed to require contractor access to repair materials—parts, tools, and information.
Source: wired.com/story/the-military-almost-got-the-right-to-repair-lawmakers-just-took-it-away/
Then, in the closed-door conference process—where House and Senate leaders reconcile their bills into a final NDAA—those sections were removed.
Key statistic #2: Right-to-repair language appeared in two separate NDAA drafts—Senate § 836 and House § 863—before being stripped from the final compromise.
Source: Wired reporting
Source: wired.com/story/the-military-almost-got-the-right-to-repair-lawmakers-just-took-it-away/
Then, in the closed-door conference process—where House and Senate leaders reconcile their bills into a final NDAA—those sections were removed.
Key statistic #2: Right-to-repair language appeared in two separate NDAA drafts—Senate § 836 and House § 863—before being stripped from the final compromise.
Source: Wired reporting
§ 836 + § 863
Right-to-repair provisions appeared in both Senate and House FY2026 NDAA drafts—then were removed in the final conference compromise.
“Quietly carved out” isn’t a metaphor—it’s a workflow
The phrase “quiet carve-out” captures how power works in Congress. A provision can have public momentum, bipartisan resonance, and clear messaging value—then disappear in conference when attention is lower and stakeholders are more concentrated.
Wired’s reporting emphasized lobbying pressure and conferee decision-making, including attention on Armed Services Committee leaders involved in the conference process.
Source: wired.com/story/the-military-almost-got-the-right-to-repair-lawmakers-just-took-it-away/
Key statistic #3: The removal became publicly clear when the final FY2026 NDAA text was released—reported in early December 2025 coverage.
Source: Wired reporting
For readers, the implication is straightforward: legislative intent means little without final text. The decisive fight often occurs after the headlines, in procedural terrain where industry has time, access, and strong incentives to prevail.
Wired’s reporting emphasized lobbying pressure and conferee decision-making, including attention on Armed Services Committee leaders involved in the conference process.
Source: wired.com/story/the-military-almost-got-the-right-to-repair-lawmakers-just-took-it-away/
Key statistic #3: The removal became publicly clear when the final FY2026 NDAA text was released—reported in early December 2025 coverage.
Source: Wired reporting
For readers, the implication is straightforward: legislative intent means little without final text. The decisive fight often occurs after the headlines, in procedural terrain where industry has time, access, and strong incentives to prevail.
Early Dec 2025
Reporting tied public confirmation of the deletion to release of the final FY2026 NDAA text in early December 2025 coverage.
What the Pentagon Actually Needs: Data Rights, Not Slogans
Public debate often treats right to repair as a moral claim—“if we bought it, we should own it.” Defense procurement doesn’t work that way. The government can buy a platform while licensing only narrow rights to the data and software required to maintain it.
GAO’s analysis points toward a more precise framing: DoD must better plan for and manage IP and technical data rights as part of acquisition, because failing to do so drives higher sustainment costs and longer repair timelines.
Source: gao.gov/products/gao-25-107468
GAO’s analysis points toward a more precise framing: DoD must better plan for and manage IP and technical data rights as part of acquisition, because failing to do so drives higher sustainment costs and longer repair timelines.
Source: gao.gov/products/gao-25-107468
What “technical data” really covers
In practice, “technical data” and related materials can include:
- Maintenance manuals and repair procedures
- Engineering drawings and specifications
- Diagnostic software and test tools
- Parts lists and interoperability information
Without clear rights, the government may be unable to share data with depots or third-party repair firms, even when doing so would improve readiness and reduce cost.
Key statistic #4: GAO explicitly links insufficient IP/data rights planning to increased sustainment costs and increased repair time—a two-part readiness penalty.
Source: GAO-25-107468
- Maintenance manuals and repair procedures
- Engineering drawings and specifications
- Diagnostic software and test tools
- Parts lists and interoperability information
Without clear rights, the government may be unable to share data with depots or third-party repair firms, even when doing so would improve readiness and reduce cost.
Key statistic #4: GAO explicitly links insufficient IP/data rights planning to increased sustainment costs and increased repair time—a two-part readiness penalty.
Source: GAO-25-107468
What “technical data” can include
- ✓Maintenance manuals and repair procedures
- ✓Engineering drawings and specifications
- ✓Diagnostic software and test tools
- ✓Parts lists and interoperability information
2-part penalty
GAO links weak IP/data-rights planning to both higher sustainment costs and longer repair time—directly affecting readiness.
The missing middle: protect trade secrets while enabling repair
The strongest policy solutions usually live in the middle: require access sufficient for repair and competition, while carving out genuine trade secrets unrelated to maintenance. The challenge is that “unrelated to maintenance” is contested when software diagnostics are the maintenance pathway.
Industry is right to fear compelled disclosure beyond legitimate sustainment needs. Reformers are right to insist that sustainment needs cannot be met with half-access and vague promises.
Industry is right to fear compelled disclosure beyond legitimate sustainment needs. Reformers are right to insist that sustainment needs cannot be met with half-access and vague promises.
Practical Takeaways: What Would Actually Change Readiness
Right to repair can sound like a culture-war slogan until you translate it into operational outcomes: shorter downtime, lower sustainment costs, and less contractor bottleneck. Even without a passed NDAA provision, the debate clarifies what readers should watch for in future acquisition fights.
For Congress: legislate precisely, not broadly
A workable statute would define:
- What counts as repair materials (parts, tools, manuals, diagnostic software)
- What constitutes reasonable access and on what timeline
- What IP remains protected as trade secrets
- How pricing standards apply, if at all, without unintended commercial spillover
Broad language invites broad opposition. Narrow language risks being toothless. The drafting is the policy.
- What counts as repair materials (parts, tools, manuals, diagnostic software)
- What constitutes reasonable access and on what timeline
- What IP remains protected as trade secrets
- How pricing standards apply, if at all, without unintended commercial spillover
Broad language invites broad opposition. Narrow language risks being toothless. The drafting is the policy.
For DoD: negotiate data rights before the platform is fielded
GAO’s emphasis on planning is a warning label. DoD’s leverage is highest during acquisition. If maintainers and depots will be expected to support a system for decades, then technical data rights should be treated as mission-critical requirements, not optional add-ons.
For taxpayers and service members: the hidden cost is dependency
Taxpayers fund both procurement and sustainment. When the government lacks the rights to repair competitively, costs rise and readiness suffers. Service members live with the outcome when a system can’t be restored quickly in the field, or when depot-level repair turns into a contractor scheduling exercise.
The most telling detail in the recent NDAA fights is not that right-to-repair provisions were proposed. It’s that they were removed—after being drafted in both chambers—once they threatened to alter the balance of power between the government customer and the contractor who controls the data.
The most telling detail in the recent NDAA fights is not that right-to-repair provisions were proposed. It’s that they were removed—after being drafted in both chambers—once they threatened to alter the balance of power between the government customer and the contractor who controls the data.
What to watch next
Whether future NDAA language defines repair materials precisely (including diagnostics/software), protects genuine trade secrets, and avoids pricing terms that trigger broad industry blowback.
Conclusion: The Real Test Is Whether Congress Will Protect Repair Rights Where Lobbying Is Strongest
Congress has learned how to praise military right to repair. The harder lesson is how to pass it.
The recent NDAA history shows the pattern: proposals emerge with strong messaging value, gather support, and then collide with the realities of IP, pricing, and the defense sustainment business model. In FY2025, Senate language (Section 828 of S.4638) attempted to set a statutory standard for “fair and reasonable access” and triggered organized industry opposition. In FY2026, similar language appeared in both House and Senate drafts—then vanished in conference.
The next right-to-repair push will succeed only if it answers two questions in text, not talking points. First: what data and tools must the government have to keep its systems ready? Second: what protections does industry legitimately need to safeguard trade secrets without converting sustainment into permanent dependence?
A military that can’t repair what it owns is not merely overpaying. It is accepting a narrower kind of sovereignty—one where readiness depends on a contractor’s calendar, contract language, and willingness to share the keys.
The recent NDAA history shows the pattern: proposals emerge with strong messaging value, gather support, and then collide with the realities of IP, pricing, and the defense sustainment business model. In FY2025, Senate language (Section 828 of S.4638) attempted to set a statutory standard for “fair and reasonable access” and triggered organized industry opposition. In FY2026, similar language appeared in both House and Senate drafts—then vanished in conference.
The next right-to-repair push will succeed only if it answers two questions in text, not talking points. First: what data and tools must the government have to keep its systems ready? Second: what protections does industry legitimately need to safeguard trade secrets without converting sustainment into permanent dependence?
A military that can’t repair what it owns is not merely overpaying. It is accepting a narrower kind of sovereignty—one where readiness depends on a contractor’s calendar, contract language, and willingness to share the keys.
T
About the Author
TheMurrow Editorial is a writer for TheMurrow covering explainers.
Frequently Asked Questions
What does “right to repair” mean for the U.S. military?
In defense policy, right to repair is about sustainment authority—whether military maintainers and government depots can diagnose and fix equipment without being blocked by contract terms, missing technical data, or restrictive IP licenses. It is less about consumer-style choice and more about readiness: the ability to return systems to service quickly and affordably.
Why can’t the Pentagon just repair equipment it already bought?
Owning the hardware doesn’t automatically include rights to the technical data and software needed to maintain it. Contracts can limit what the government can do, especially when proprietary diagnostics or manuals are required. GAO has warned that insufficient planning and management of these rights can increase sustainment costs and extend repair times.
What was Section 828 in the FY2025 NDAA debate?
Section 828 in the Senate’s FY2025 NDAA bill (S.4638) proposed adding 10 U.S.C. § 4663, requiring contractors to provide “reasonable access to repair materials.” The language also included pricing/terms tied to the “most favorable” offerings through the manufacturer or authorized channels—one reason it drew strong industry opposition.
Why did industry groups oppose the Senate right-to-repair language?
Industry coalitions argued provisions like Section 828 were too broad and could force disclosure of proprietary information or trade secrets beyond what’s necessary for repair. Opponents also objected to pricing requirements, saying “most favorable” pricing terms could function as price controls and disrupt commercial dealer and distribution models.
What happened to right-to-repair provisions in the FY2026 NDAA?
Reporting indicated right-to-repair language appeared in both chambers’ drafts—Section 836 (Senate) and Section 863 (House)—but was removed during the closed-door conference process that produced the final bill. The deletion became public when final language was released, with reporting in early December 2025 highlighting lobbying pressure.
What would a balanced right-to-repair policy look like?
A balanced approach would guarantee access to the parts, tools, manuals, and diagnostics needed for repair while protecting genuine trade secrets not required for sustainment. The key is precision: clearly define “repair materials,” set reasonable access terms, and align acquisition planning with long-term sustainment needs—so the military doesn’t discover after fielding that it lacks the rights to maintain what it operates.
