WASHINGTON — The aircraft carrier Theodore Roosevelt is gearing up for a deployment with a Seahawk medium unmanned surface vessel (MUSV) as part of its strike group for the first time — a key milestone signifying the transition of the unmanned system from an experimental to operational part of the fleet.
In fact, multiple experts told Breaking Defense that this deployment could lay the foundation for how the Navy develops its concept of operations (CONOPS) for integrating unmanned into the rest of the fleet, at a time when the Navy is still struggling to articulate how and when it will make autonomous vessels a core part of its arsenal.
“It is certainly a significant development,” said Bradley Martin, a retired Navy captain who is now a senior policy researcher at RAND. “Up to now, it’s all been a matter of testing, and the actual use in operational deployment is a major step. I think that what will happen as a result of this is, we won’t necessarily see immediately some big change in the way the fleet operates, but it will tell the fleet a lot about how to use this type of capability.”
The Seahawk vessel is one of Leidos’ unmanned vessels. An upgraded design of the firm’s Sea Hunter autonomous vessel, the Seahawk supports anti-submarine warfare and maritime domain awareness, and stems from a Defense Advanced Research Projects Agency initiative.
The Navy ly deployed four unmanned ships — including a Seahawk and a Sea Hunter — to the Western Pacific in 2023. But the announced upcoming deployment with the Theodore Roosevelt shows the Navy wants unmanned systems to supplement primary forces as the Navy develops new tailored force packages for specific mission sets and geographies, according to Bryan Clark, a retired submarine officer and a senior fellow at the Hudson Institute.
“This is a regularly scheduled deployment by a full carrier strike group that shows MUSVs have progressed from science project to become part of the operational fleet,” Clark said.
While the Navy officially announced the deployment with the MUSV at the Sea Air Space exposition in April, the service did not respond to questions from Breaking Defense about when exactly the carrier strike group will get underway, how the deployment would guide the development of unmanned CONOPS, when the Navy plans to release an unmanned strategy, and what specific things the Navy wants to test while at sea.
But the analysts largely agreed with a key point: Whatever is learned from this deployment will help the service set its approach to both the concept of operations (CONOPS) for unmanned vessels, and the acquisition strategy for procuring them.
“This is a really important, initial early step in terms of developing those CONOPS. The Navy isn’t waiting around to develop a bunch of prototypes and just sort of leave them stateside,” said Stacie Pettyjohn, a senior fellow at the Center for a New American Security. “They’re putting them out and integrating them with the crewed vessels immediately and allowing them to experiment and consider different ways of how they can work together.”
Developing CONOPS
In February, the Navy’s top officer, Chief of Naval Operations Adm. Daryl Caudle, unveiled his “Fighting Instructions” framework. There, he laid out plans to utilize a “hedge force strategy” that seeks to capitalize on unmanned systems and create a range of tailored options that fall outside the traditional carrier strike group model where an aircraft carrier, a destroyer, and several other assets go out to sea together.
This coincides with the rest of the fleet facing increased strain amid extended deployments like the aircraft carrier Gerald R Ford’s 326-day period at sea — where it was one of three carrier strike groups operating in the Middle East concurrently for the first time since 2003.
“One of the challenges that they’re trying to use the uncrewed systems for…is really to help with just sort of the shrinking force structure more broadly, and the fact that the fleet has been shrinking, continues to shrink, and can’t meet the current demand, and is being operated at such a high tempo that they’re going to face challenges meeting all of their requirements going forward,” Pettyjohn said.
Caudle’s “Fighting Instructions” issues some key tasks for the Navy to develop. Specifically, it orders the Navy to detail how fleet commanders and the joint force will integrate unmanned capabilities, known as robotic autonomous systems (RAS), into “service decisions like strategic laydown, dispersal, and global force management.” No model is in place yet for RAS capabilities, according to the guidance.
As a result, Caudle said in February he is facing an “unmanned dilemma” about how to organize RAS capabilities into the fleet. At the time, he said he was not ready to release an unmanned strategy as he and the rest of the Navy work together to figure out the command structure for employing unmanned systems fleetwide.
When asked about an unmanned strategy at the Sea Air Space Exposition in April, Caudle pointed to the Seahawk’s upcoming deployment with the Theodore Roosevelt. He also said the Navy is eying establishing a Warfighting Development Center (WDC) for RAS like the Navy already has for areas like aviation, and surface and mine warfighting.
“We need to move these capabilities from individual units into composite mission sets, including contested logistics,” Caudle told reporters in April. “Using USVs to move food and parts — replenishing underways without risking humans — is a major use case.”
Additionally, Caudle has ly floated setting up a RAS commander to oversee unmanned capabilities. Currently, RAS is now arranged by domain, like undersea, aviation and cyber, but a RAS commander could coordinate across the domains, according to Caudle.
While Martin, the senior policy researcher at RAND, said a RAS commander could serve as an advocate for these systems, the Navy must remain cautious that it doesn’t silo unmanned capabilities too much.
“It may be best to leave them with communities, so that all the communities have opportunity to work with these things and become familiar, as opposed to making yet another type commander where additional risk and additional coordination has to take place,” Martin said.
Meanwhile, Pettyjohn said that the Navy likely has already established some CONOPS for unmanned, and will develop more through this upcoming deployment — although whether those lessons learned are baked into official doctrine and dispersed throughout the fleet more broadly remains a question, considering there are so few prototypes currently in the fleet.
Regardless, Pettyjohn said the Navy is on the right track to develop the CONOPS and capabilities concurrently so that the service can identify different attributes that may be more or less important for future iterations.
“All of this should be sort of a living document that isn’t going to remain static, because they’ll develop some way of doing it, and it’ll work in one environment against one threat picture,” Pettyjohn said. “And then others will learn or you’ll face a more capable adversary, and it won’t work as well there. So as technology changes, as adversaries adapt, and as we move along, these should continually be being updated and revised.”
Meanwhile, lawmakers on the House Armed Services Committee want the Navy to verify to congressional defense committees that CONOPS for unmanned systems have already been developed ahead of accepting a USV, according to the chairman’s mark of the National Defense Authorization Act (NDAA) released in May.
Likewise, the draft legislation includes a section that would require the secretary of the Navy to craft and execute a strategy for USV integration into the fleet and joint maritime operations.
Acquisition Influence
The deployment could also factor into how the Navy chooses to move forward procuring new MUSVs, according to experts, as the service zeroes in on a new acquisition model