The U.S. Navy is exploring contractor-operated drone services for intelligence, surveillance, and reconnaissance missions under a contractor-owned, contractor-operated (COCO) model, according to a Request for Information (RFI) posted on SAM.gov. The initiative, managed through the Navy’s Program Manager, Air (PMA-263), seeks industry input on providing UAS ISR “as a service,” rather than the Navy purchasing and operating the systems itself. For the fleet and for defense contractors alike, the stakes are significant: how the Navy structures any follow-on drone service contract could influence the economics and operational tempo of maritime surveillance in the years ahead.
Navy Seeks Contractor-Owned Drone ISR Services
PMA-263, the Navy office responsible for unmanned aircraft procurement and sustainment, issued a formal Request for Information (RFI) seeking industry input on Unmanned Aircraft System (UAS) Contractor Owned Contractor Operated (COCO) ISR services. The solicitation, cataloged under SAM.gov, signals that the Navy wants private companies to supply, operate, and maintain drone platforms on behalf of the service branch, rather than purchasing the systems outright and staffing them with uniformed personnel.
The COCO model is not new to the U.S. military, but its application to naval ISR drone operations represents a deliberate expansion of outsourced capability. Under this approach, the contractor retains ownership of the aircraft and ground control equipment while providing trained operators, maintenance crews, and mission planning support. The Navy, in turn, receives ISR data and mission products without bearing the full lifecycle cost of fleet ownership. This arrangement can cut procurement timelines and shift financial risk from the government to the vendor, though it also raises questions about long-term dependency on private operators for sensitive intelligence collection.
In practical terms, the Navy is asking industry to demonstrate that it can deliver reliable, deployable ISR coverage at sea and from shore facilities with minimal ramp-up time. The RFI invites companies to describe not only their airframes and sensors, but also how they would handle logistics, training, cybersecurity, and integration with existing Navy command-and-control networks. Those responses will help PMA-263 determine whether to pursue a single-award contract, a multiple-award framework, or a more flexible arrangement that can scale as operational demands evolve.
Why the JUMP 20-X Fits the Navy’s Requirements
AeroVironment’s JUMP 20-X is a Group 3 unmanned aircraft system designed for vertical takeoff and landing (VTOL), which allows it to operate from confined spaces aboard ships or from austere forward positions ashore. Unlike traditional fixed-wing drones that need a runway or launch rail, the JUMP 20-X lifts off vertically, transitions to wing-borne flight for endurance, and returns to a vertical landing at mission’s end. This hybrid capability makes it well suited for naval operations where deck space is limited and traditional launch-and-recovery infrastructure may not be available.
The platform is built around persistent ISR, carrying electro-optical and infrared sensor payloads that can loiter over an area for extended periods. For Navy task forces operating in littoral zones or contested waters, a drone that can launch quickly, fly for hours, and land without a runway offers a tactical advantage over larger, more logistically demanding systems. The JUMP 20-X’s size also means it can be transported and deployed by a small team, reducing the footprint required aboard a vessel or at a forward operating base.
AeroVironment has marketed the JUMP 20 family as a solution for expeditionary forces that need organic ISR without the overhead of a full drone squadron. The “X” variant represents an upgraded configuration, though detailed public specifications on range, endurance, and payload capacity beyond what AeroVironment has released in marketing materials remain limited. Readers and analysts should note that the RFI stage does not guarantee a contract award to any particular vendor; it is a market research step where the Navy gathers information before deciding how to structure a formal solicitation.
Even so, the characteristics AeroVironment markets for the JUMP 20-X line up with the types of capabilities described in the RFI. A Group 3 VTOL platform can operate below the regulatory and logistical thresholds that govern larger Group 4 and 5 systems, while still offering meaningful endurance and payload capacity. That combination is attractive for distributed maritime operations, where smaller surface combatants and support ships may need their own ISR coverage without relying on larger, theater-level drones controlled from distant bases.
What COCO Means for Naval Operations
The contractor-owned, contractor-operated model carries real consequences for how the Navy conducts surveillance at sea. When the service buys a drone outright, it assumes responsibility for training operators, stocking spare parts, scheduling depot maintenance, and managing software upgrades across the fleet. Under COCO, those burdens shift to the contractor, who delivers ISR as a service rather than as a piece of hardware. The Navy pays for mission hours and data products, not for airframes sitting in hangars.
This approach can accelerate fielding. Instead of waiting years for a traditional acquisition program to move through milestones, the Navy can contract for ISR services from vendors who already have operational platforms. The tradeoff is control. When a contractor owns and operates the system, the Navy depends on that company’s workforce availability, supply chain health, and willingness to deploy to high-risk environments. In a conflict scenario, questions about contractor personnel operating in or near combat zones become urgent and legally complex.
There is also a strategic tension between cost efficiency and capability development. COCO arrangements may save money in the near term, but they can also slow the Navy’s own institutional learning about drone operations. If uniformed sailors never fly or maintain these systems, the service risks losing organic expertise that could prove essential when contractor support is unavailable. The balance between outsourced efficiency and retained military capability is a recurring debate in defense procurement, and this ISR services initiative sits squarely within it.
Operationally, COCO ISR could change how commanders think about surveillance tasking. Instead of competing for scarce hours on a small number of government-owned drones, fleet commanders might be able to purchase additional coverage from contracted providers as budgets allow. That flexibility could prove valuable in crisis response or surge operations, but it will depend on how contracts are structured, how quickly vendors can mobilize, and how seamlessly their systems can plug into Navy communications and data-processing architectures.
PMA-263’s Role in Shaping the Drone Fleet
PMA-263 manages several unmanned aircraft programs for the Navy and Marine Corps, making it the natural office to lead this market research effort. The office’s decision to issue an RFI rather than jump directly to a request for proposals suggests the Navy is still evaluating what industry can offer before committing to contract terms. RFIs typically ask vendors to describe their capabilities, pricing models, and operational experience so the government can write a more informed solicitation later.
The reference designation PMA-263 UAS ISR Services, tied to the SAM.gov listing, indicates this is a distinct initiative from the Navy’s other drone programs, such as the MQ-25 Stingray tanker drone or the MQ-8 Fire Scout. While those programs involve government-owned aircraft flown by military crews, the COCO ISR effort represents a parallel track where the Navy buys surveillance as a service. If the RFI leads to a formal contract, it could establish a template for how the Navy procures drone ISR across multiple theaters and mission sets.
For AeroVironment, a company that has built its defense business largely on small and medium UAS platforms like the Switchblade loitering munition and the Puma surveillance drone, the JUMP 20-X represents a step into a higher-end service market. Winning a Navy COCO ISR contract would validate the platform as a maritime-capable solution and could open doors to similar arrangements with other U.S. services and allied navies. For the Navy, selecting a mature, fielded system like the JUMP 20-X would allow it to test-drive the COCO model with relatively low technical risk.
Ultimately, the outcome of the PMA-263 effort will signal how far the Navy is willing to go in relying on private industry for core ISR functions. If the service embraces COCO at scale, contractors could become a permanent fixture in day-to-day maritime surveillance, operating alongside government-owned drones and manned aircraft. If the Navy instead opts for a limited pilot program, it may treat COCO as a stopgap while it builds up its own unmanned aviation workforce and platforms. Either way, the JUMP 20-X and its competitors are poised to shape the next phase of naval drone operations, where flexibility, endurance, and contractual agility matter as much as airspeed and altitude.
More from Morning Overview
*This article was researched with the help of AI, with human editors creating the final content.
