America’s most elite military units buy drones with taxpayer money, train their operators, and deploy them into combat zones. But when those operators need to swap a sensor, update flight software, or reconfigure a payload for a specific mission, they often cannot touch the aircraft. The manufacturer says no.
That was the core complaint from senior U.S. special operations commanders who testified before the Senate Armed Services Committee’s Subcommittee on Emerging Threats and Capabilities in spring 2026. Leaders from all four special operations service components told lawmakers that contractor-imposed restrictions on unmanned systems are degrading readiness at a moment when adversaries can modify their own drones overnight.
What the commanders told Congress
The hearing brought together four witnesses: Lieutenant General Lawrence G. Ferguson, commanding general of the U.S. Army Special Operations Command; Lieutenant General Michael E. Conley, commander of Air Force Special Operations Command; Major General Peter D. Huntley, commander of Marine Forces Special Operations Command; and Rear Admiral Walter H. Allman III, commander of Naval Special Warfare Command.
Ferguson’s written testimony described a force that is leaning hard into small unmanned platforms for reconnaissance, targeting, and logistics but running into walls when it tries to adapt those platforms quickly. His statement addressed robotics integration and the need for equipment and training processes that can keep pace with threats that evolve faster than traditional acquisition timelines allow.
Conley’s posture statement struck a similar note, calling for modular, rapidly upgradable systems that operators can reconfigure for different missions without restarting the full certification and contracting cycle. Taken together, the written statements from all four commanders paint a consistent picture: special operations forces want drones that are open, modular, and field-adaptable, and they are not getting them.
General Bryan P. Fenton, the overall commander of U.S. Special Operations Command, reinforced the point in separate congressional testimony. In remarks summarized by the Department of Defense, Fenton said innovation cycles now move in days and weeks while the Pentagon’s acquisition system lags far behind. He argued that the mismatch demands fundamental changes to how SOCOM buys and fields technology, framing the drone modification dispute as a symptom of a deeper structural problem rather than an isolated contracting headache.
The right-to-repair parallel
The commanders’ frustration echoes a debate that has played out for years in the civilian world. Farmers have fought John Deere for the right to fix their own tractors. Hospitals have pushed back against medical device manufacturers that lock down diagnostic software. The Federal Trade Commission has taken enforcement actions against companies that use proprietary restrictions to block independent repair.
In the military context, the stakes are sharper. When a special operations team in a forward operating area needs a drone reconfigured for a new threat, a weeks-long wait for the manufacturer to authorize or perform the change is not just inconvenient. It can mean the difference between actionable intelligence and a missed target.
Senator Elizabeth Warren’s office seized on that connection after the hearing, releasing a statement noting that top military leaders from every branch committed to sharing more information about how contractor-imposed limits hurt readiness. The press release cited findings from the Government Accountability Office to counter industry arguments that proprietary protections are necessary and that government-led alternatives are impractical.
The GAO report in question, GAO-19-586, documented how the Defense Logistics Agency conducted reverse engineering of spare parts from fiscal years 2015 through 2018 while still protecting proprietary information. That finding directly challenges the claim that intellectual property barriers make independent maintenance impossible, though the data predates the current generation of military drones and the rapid expansion of the commercial drone market that followed.
The Ukraine factor
The urgency behind the commanders’ testimony is impossible to separate from what the world has watched in Ukraine. Ukrainian forces have built a drone adaptation ecosystem that operates on a cycle of days: identifying a battlefield need, modifying a commercial quadcopter or fixed-wing platform, testing it, and fielding it. Small workshops near the front lines swap payloads, rewrite firmware, and fabricate new components with 3D printers.
That model has become a case study at U.S. military war colleges and inside SOCOM itself. The contrast is stark. While Ukrainian operators iterate in garages, American special operators describe a system where the manufacturer’s permission is required before they can change a line of code on a drone they already own.
Fenton’s testimony acknowledged this gap without naming Ukraine directly, but his language about adversaries who innovate in “days and weeks” left little ambiguity about the comparison he was drawing.
What is still unclear
Several important details remain unresolved. Full oral transcripts from the hearing have not been published, so the specific remarks attributed to commanders in press coverage, including reported comments about the inability to “tinker” with purchased systems, cannot be confirmed through the prepared written statements alone. Oral testimony often diverges from filed statements, and without a verbatim record, the exact phrasing is sourced only through secondary summaries.
No primary evidence identifies which drone models or manufacturers are at the center of the dispute. The prepared statements address modernization and acquisition reform in general terms but do not name specific vendors or platforms. That gap matters. If the restrictions apply mainly to a handful of classified, niche systems, the fix may be as simple as renegotiating a few contracts. If they extend to widely used commercial off-the-shelf drones adapted for military use, the problem becomes a much larger challenge to the Pentagon’s relationship with the commercial technology sector.
Industry responses are also absent from the public record. Defense contractors have historically argued that proprietary controls protect trade secrets, ensure safety, and preserve warranty obligations. But no manufacturer testimony or formal rebuttal from a trade association appears in the hearing materials. Without that side of the story, the public picture is incomplete.
Quantitative data on the cost of the problem is missing as well. None of the filed testimonies attach dollar figures, mission delays, or specific operational failures to proprietary restrictions. Fenton described the speed mismatch in qualitative terms. The component commanders wrote about modernization shortfalls and the need for agility but stopped short of listing canceled missions or lost targets.
Where the policy fight goes next
The reform proposals now circulating in Congress and inside SOCOM converge on a few ideas: expanding the government’s rights to technical data in drone contracts, requiring open architectures that allow third-party or in-house modifications, and funding organic modification capabilities within special operations units themselves.
The GAO’s earlier findings on reverse engineering suggest that, at least for some categories of equipment, the Pentagon can develop alternative sources of parts and upgrades without violating legitimate intellectual property protections. Translating that precedent to drones, however, will require more transparency about which systems are affected, how contracts are structured, and what risks commanders are willing to accept when operators modify software and hardware outside the original manufacturer’s control.
The political alignment is notable. Lawmakers from both parties have signaled interest in defense right-to-repair principles, and the commanders’ testimony gives that push institutional credibility that a think-tank white paper or advocacy campaign cannot match. Four generals and admirals, each responsible for fielding drone capabilities to operators in the field, told Congress under oath that the current system is not working.
Whether that shared concern translates into concrete changes in acquisition law and contracting practice before the next generation of unmanned systems gets locked into the same constraints is the question that will define whether this hearing was a turning point or just another warning that went unheeded.
More from Morning Overview
*This article was researched with the help of AI, with human editors creating the final content.
