The HOVER Act directs the Secretary of the Army to stand up an operational experimentation program to evaluate optionally piloted vehicle (OPV) rotary‑wing aircraft. The statute frames the effort as an operational testbed: assess OPV utility in contested environments, integration with crewed aircraft, maintenance and cost implications, and development of future tactics, techniques, and procedures for Army aviation.
For practitioners, the bill channels Army acquisition and aviation offices into a short, focused experimental cycle intended to feed near‑term modernization choices. The program’s outputs—conversion lessons, operational findings, and procurement recommendations—are meant to influence how the Army balances manned, optionally piloted, and unmanned rotary capabilities going forward, with downstream effects for manufacturers, sustainment planners, training commands, and joint interoperability efforts.
At a Glance
What It Does
The statute requires the Secretary of the Army to establish an operational experimentation program using OPV technology within 180 days of enactment, run that program for two years, and convert at least three existing Army rotary‑wing aircraft into optionally piloted platforms. Testing must occur in Department of Defense special use airspace, and the Assistant Secretary of the Army for Acquisition, Logistics, and Technology will run the effort in coordination with the Program Executive Office for Aviation. The Secretary must submit a report to congressional Armed Services committees with progress, initial findings, and procurement recommendations.
Who It Affects
Directly affects Army aviation units and their acquisition, PEO Aviation, ASA(ALT), maintenance depots, and training organizations. It also creates near‑term opportunities for defense primes, avionics and autonomy suppliers, universities and research labs, and DARPA collaborators tied to ACES, MAA, and the ALIAS workstream.
Why It Matters
This statutory experiment institutionalizes a rapid, operationally‑focused test of rotary‑wing autonomy rather than leaving trials solely to research programs, potentially accelerating procurement decisions and shaping the industrial base for rotorcraft autonomy. The results could change sustainment expectations, crew training, and how the joint force employs mixed crewed/optionally piloted formations.
More articles like this one.
A weekly email with all the latest developments on this topic.
What This Bill Actually Does
The bill creates an Army‑led, operationally oriented experiment to see whether retrofit OPV technology gives rotary‑wing aviation a workable blend of autonomy and crewed operation for real combat‑relevant missions. Instead of a laboratory prototype program, the statute pushes for conversion of service aircraft and testing in operationally realistic contexts so lessons are grounded in maintenance, logistics, and tactics tradeoffs that matter to commanders.
Operational execution sits inside the acquisition chain: the Assistant Secretary for Acquisition, Logistics, and Technology, working with PEO Aviation, is the delivery authority. That structure signals the experiment is intended to inform acquisition and sustainment choices, not merely produce scientific papers.
The law explicitly ties the experiment to ongoing autonomy efforts—ACES, MAA, and the ALIAS transition with DARPA—so results are intended to plug into existing S&T pipelines and reduce stove‑piping.Practically, converting crewed helicopters to optionally piloted vehicles requires hardware integration (sensors, flight controls, remote piloting links), software (autonomy stack, health monitoring), and human‑machine interface work that affects cockpit procedures and maintenance practices. Testing inside DoD special use airspace restricts public exposure and eases airspace integration, but it also constrains the operational scenarios that can be safely tried.
The required report to Congress is the program’s accountability mechanism: it must synthesize operational utility, cost and maintenance impacts, and give procurement recommendations that could change follow‑on buys or modifications to existing rotorcraft fleets.Finally, the statute preserves discretion: the Army can adjust platform selection, scope, and methods to stay aligned with service priorities. That flexibility is practical for a rapidly evolving tech area, but it also places weight on how the Army designs success metrics and documents lessons so Congress and industry can interpret the results consistently.
The Five Things You Need to Know
The Secretary of the Army must establish the OPV operational experimentation program within 180 days of enactment.
The program must convert at least three existing Army rotary‑wing aircraft into optionally piloted vehicles for testing.
All testing and evaluation under the program must occur within Department of Defense special use airspace.
The statute sets a two‑year period for carrying out the experimentation effort from the program’s commencement.
The Secretary must submit a report to the House and Senate Armed Services Committees within one year of enactment detailing conversion progress, initial findings on efficiency/costs, and procurement recommendations.
Section-by-Section Breakdown
Every bill we cover gets an analysis of its key sections.
Short title — HOVER Act of 2025
This is the naming clause; it establishes the bill’s citation as the Helicopter Operational Versatility and Enhanced Readiness Act of 2025 (HOVER Act). While ceremonial, the short title frames the statute’s focus on rotary‑wing versatility and readiness, signaling Congress’ intent that the effort be operationally relevant rather than purely experimental.
Establish operational experimentation program
This subsection directs the Secretary of the Army to create an experiment using OPV technology and lists five evaluation objectives: contested‑environment utility, integration with crewed aircraft in multi‑domain operations, cost and maintenance analysis, TTP development, and complementing existing autonomy R&D. The enumerated objectives make clear the program’s deliverables are operational insights and acquisition guidance, not basic research.
Program duration
The statute fixes the program’s active execution window at two years from commencement. That finite timeline forces prioritization of near‑term, actionable experiments and limits the program’s scope to what can reasonably be prototyped, flown, and analyzed within a short, focused campaign.
Conversion requirement
The law requires conversion of at least three existing Army rotary‑wing aircraft into optionally piloted configurations. By specifying retrofits rather than new builds, the provision pushes the Army to evaluate OPV technology on platforms already in the fleet, which produces realistic maintenance and integration data but constrains results to the characteristics of selected airframes.
Testing in DoD special use airspace
Mandating special use airspace confines trials to controlled military ranges, reducing civil airspace risk and easing classified or prototype testing. The tradeoff is that special use ranges may not fully replicate contested or distributed, austere environments—an important caveat when interpreting program outcomes.
Program management through ASA(ALT) and PEO Aviation
The statute requires execution through the Assistant Secretary of the Army for Acquisition, Logistics, and Technology in coordination with PEO Aviation. Placing program management inside acquisition leadership aligns experimental results with procurement pathways and sustainment authorities, increasing the chance findings translate into acquisition decisions.
Partnerships with industry, universities, and research institutions
The Secretary may collaborate with defense industry, universities, and research institutions to accelerate prototyping and ensure interoperability with Joint initiatives. This permissive language encourages public‑private partnerships but stops short of mandating specific contracting vehicles or intellectual property arrangements.
Reporting requirement and implementation flexibility
The Secretary must report to the Armed Services committees within one year on conversion progress, initial findings on efficiency and cost, and procurement recommendations. The bill also expressly preserves the Secretary’s ability to adjust scope, platform selection, and methodology to align with service priorities—granting practical flexibility but creating a need for transparent success metrics so Congress and stakeholders can interpret results.
This bill is one of many.
Codify tracks hundreds of bills on Defense across all five countries.
Explore Defense in Codify Search →Who Benefits and Who Bears the Cost
Every bill creates winners and losers. Here's who stands to gain and who bears the cost.
Who Benefits
- Army aviation leaders and doctrine developers — the program produces operationally relevant data and TTPs to inform how the service employs mixed crewed/optionally piloted formations.
- Defense primes and avionics suppliers — conversion work and prototyping create near‑term contracting and system‑integration opportunities for companies offering autonomy stacks, sensors, and retrofit kits.
- Research institutions and universities — the bill explicitly permits collaboration, providing research grants, flight test partnerships, and transition pathways for autonomy research.
- PEO Aviation and acquisition offices — getting empirical sustainment and cost data from fleet‑based conversions helps refine requirements for follow‑on procurements or upgrades.
- Pilots and maintainers — practical testing on existing airframes can yield concrete changes to training, human‑machine interfaces, and maintenance procedures that improve safety and efficiency.
Who Bears the Cost
- Army acquisition and sustainment accounts — converting aircraft, running tests, and analyzing results will draw from service budgets and could shift funding away from other modernization lines if not separately appropriated.
- Maintenance depots and logistic organizations — retrofits and new sustainment practices will impose labor, tooling, and parts demands during and after the experiment.
- Training commands and crews — integrating OPV modes requires development of new curricula, simulator upgrades, and potential retraining of pilots and RIOs (or analogous crew roles).
- Small defense contractors with narrow legacy products — the move toward integrated autonomy stacks favors system integrators and could squeeze vendors unable to meet interface/interoperability requirements.
- Congressional oversight workload — the required report and subsequent procurement decisions create additional oversight and appropriations questions that committees must address.
Key Issues
The Core Tension
The central dilemma is speed versus assurance: the bill pushes the Army to test and potentially accelerate adoption of OPV rotary‑wing capabilities to gain operational advantages, but doing so quickly risks locking in immature technologies, underestimating sustainment burdens, or producing trial results that don’t generalize to contested operations—so policymakers must balance rapid learning with rigorous metrics and cautious procurement decisions.
The bill is tightly scoped to operational experimentation, but several implementation questions could skew results. Testing only in DoD special use airspace eases safety and security concerns, yet that environment is not equivalent to a contested battlespace with degraded communications, electromagnetic attack, and dispersed basing.
Outcomes measured in controlled ranges may overstate OPV reliability under real‑world adversary pressure. Similarly, retrofitting existing airframes yields realistic sustainment data for those platforms but may not translate to newer designs optimized for autonomy.
Another area of tension is funding and metrics. The statute prescribes deadlines and reporting but does not appropriate funds or define objective success criteria—what constitutes sufficient 'military utility' or acceptable maintenance savings.
Without pre‑defined metrics, program managers could select scenarios and platforms that produce favorable outcomes or defer hard choices under the rubric of 'implementation flexibility.' Cybersecurity, command and control, and legal authorities for optionally piloted operations (e.g., delegated use of force, if applicable) also remain unresolved and will require separate policy and regulatory work to ensure fielded OPVs can operate safely and lawfully alongside crewed assets.
Try it yourself.
Ask a question in plain English, or pick a topic below. Results in seconds.