🔔 Subscribe to ShipUniverse Weekly →
Why Seahawk May Be the First Real Step Toward a Hybrid U.S. Fleet
USS Theodore Roosevelt has crossed a line the Navy has spent more than a decade approaching. Carrier Strike Group 9 is now operationally deployed with Seahawk, a 135-foot autonomous surface vessel with nobody aboard. It is not yet a robotic destroyer and there is no public evidence that Seahawk is carrying missiles. The milestone is more fundamental: an uncrewed ocean-going ship has entered the communications, logistics and command structure of a deployed carrier strike group. Nine days after the carrier sailed, the Navy also committed to buy 30 production MUSVs. The prototype era is beginning to collide with fleet operations.
This is a deployment, not another harbor demonstration
Carrier Strike Group 9 left San Diego in late September. Public Navy tracking subsequently listed Seahawk with the deployed group, and Acting Secretary of the Navy Hung Cao described the deployment as the first time a carrier strike group had deployed with a large-sized unmanned surface vessel.
The distinction matters because the Navy has operated large unmanned vessels with fleet ships before. It has crossed oceans with them, taken them to major exercises and fired a Standard Missile from a related prototype. What it had not publicly done was place one inside a carrier strike group's real deployment cycle.
The threshold is organizational
The important change is not that Seahawk can steer itself. That has been demonstrated for years.
The new test is whether a carrier strike group can plan around an uncrewed ship, communicate with it, refuel it, assign missions, troubleshoot failures and keep it useful thousands of miles from the technicians and infrastructure that normally support experimental systems.
A 142-ton sensor ship with nobody aboard
| Attribute | Public information | Operational implication |
|---|---|---|
| Length | Approximately 41 meters / 135 feet | Large enough for ocean operations but far smaller than a destroyer. |
| Displacement | 142.3 metric tons full load in Navy fact file | Closer to a large patrol craft in physical scale than a conventional warship. |
| Crew | None permanently aboard | Removes sailors from the platform but does not eliminate shore operators or maintainers. |
| Fuel | Leidos disclosed approximately 14,000 gallons | Designed for long-duration ocean operations rather than short harbor sorties. |
| Hull | Composite trimaran | Long-range, stable unmanned platform with reduced corrosion burden. |
| Navigation | Autonomous navigation and perception | Routine maneuvering does not require a helmsman continuously steering remotely. |
| Collision avoidance | Designed to comply with COLREGS | Critical for operating in ordinary commercial sea traffic. |
| Communications | Failover paths plus remote-control capability | The vessel can switch communications paths rather than depending on one link. |
| GPS loss | Demonstrated waypoint navigation without GPS | Reduces dependence on uninterrupted satellite navigation. |
| Current public role | Distributed sensing, maritime-domain awareness and ASW support | It should not yet be counted as another missile shooter. |
Seahawk is not publicly an armed robotic destroyer
The phrase “uncrewed warship” can create the wrong picture. The Navy still describes Sea Hunter and Seahawk as prototype MUSVs used for experimentation and fleet integration. Their published operational role centers on distributed sensing, maritime-domain awareness and anti-submarine warfare.
There is no public confirmation that Seahawk deployed with VLS cells, anti-ship missiles or another offensive weapon.
The Navy has already demonstrated the technical path toward an armed unmanned surface vessel. In 2021, the related unmanned vessel Ranger fired an SM-6 from a containerized modular launcher.
The September 2026 MUSV production announcement goes further by explicitly identifying sensors, weapons and other mission payloads as future containerized capabilities.
Ten years of experiments led to this cruise
Refueling matters more than autonomy demonstrations
An autonomous ship that has to return to San Diego every time it needs fuel cannot function as a permanent carrier escort.
That is why the September 11 fueling evolution with USS Chafee is easy to underestimate. It tests whether a USV can plug into the same basic sustainment network that keeps destroyers and cruisers operating forward.
The core engineering trade is simple. Removing the crew removes berthing, food, habitability and personnel risk. It also removes the people who normally isolate leaks, reset breakers, replace pumps and improvise repairs at sea.
Hybrid fleet economics only work if autonomous ships remain reliable enough that the Navy does not need to surround every robot with technicians and support vessels.
The first value is more likely to be sensing than missiles
One Seahawk is a prototype. Eight would alter the geometry
Robotic sensors
USVs can operate farther from the carrier than a commander may want to position a billion-dollar crewed combatant simply to maintain persistent surveillance.
Persistent submarine search
Multiple unmanned platforms can create distributed sonar coverage while MH-60Rs, P-8As, SSNs and destroyers concentrate on prosecution.
More targets to solve
Low-cost unmanned emitters could complicate an adversary's attempt to determine which contact is the carrier, an escort, a decoy or a remote sensor.
Future distributed weapons
Armed MUSVs could eventually carry missiles that are launched under human authorization from elsewhere in the force.
Carrier + destroyers
High-end warships retain SPY radar, Aegis, aviation, command facilities, damage control and the human judgment required for complex combat.
The Navy has already ordered the next 30
The first production MUSVs are scheduled for delivery before the end of FY2027.
That timing changes how the Roosevelt deployment should be read. If Seahawk were the only vessel involved, this could still be treated primarily as an extended prototype experiment. It is instead deploying just as the Navy begins buying the first sizeable production batch.
30 MUSVs cost less than one Flight III destroyer pair
A Flight III Arleigh Burke has recently been estimated at roughly $2.5 billion to $2.7 billion per ship. Thirty MUSVs at the Navy's stated average procurement price equal roughly $1.2 billion.
That comparison is not an argument that 30 MUSVs equal half a destroyer. They do not carry a destroyer's radar, 96-cell VLS magazine, helicopters, command staff, damage-control organization or multirole combat system.
The comparison explains the attraction: autonomous platforms allow the Navy to purchase additional distributed hulls without paying destroyer prices for every sensor or payload it wants at sea.
Zero sailors aboard does not mean zero sailors
| Platform | People physically aboard | People still required elsewhere | What automation removes |
|---|---|---|---|
| Flight III Arleigh Burke | 359 Navy-listed crew | Shore maintenance, training and logistics organizations | Limited relative to MUSV |
| Seahawk | 0 | Remote command, mission planning, software, maintenance, payload and logistics personnel | Watchstanders, cooks, berthing, habitability and onboard routine personnel workload |
| Future MUSV squadron | 0 aboard each autonomous vessel | Centralized operator and maintenance teams can potentially support multiple hulls | Potentially breaks the one-ship/one-full-crew relationship |
The real manpower test will be the support ratio.
If every autonomous ship needs a large dedicated control team and frequent maintenance intervention, much of the personnel advantage disappears. If one operator team can supervise several reliable vessels, the Navy can increase the number of deployed hulls without increasing sailors at the same rate.
The hard problems begin after autonomous navigation
Machinery casualties
A destroyer has an engineering department onboard. An unmanned vessel needs machinery reliable enough to survive failures without immediate human intervention.
Electronic warfare
Communications failover and GPS-denied navigation have been demonstrated. Sustaining useful combat operations under deliberate jamming and cyber attack is a higher bar.
Data overload
Adding sensors has limited value if the strike group cannot automatically classify, prioritize and distribute their information without overwhelming watch teams.
Weapons authorization
An armed MUSV requires clear human control over target identification, engagement authorization and behavior when communications are interrupted.
Battle damage
An inexpensive robotic vessel can be more expendable than a destroyer, but a platform that fails after minor damage may also have poor wartime persistence.
Fleet logistics
A strike group with eight or twelve USVs creates new requirements for fuel, spare parts, payload swaps, towing, software support and recovery.
Five things have to happen after Seahawk
| Test | What success looks like | Current public status |
|---|---|---|
| Deploy | USV completes normal long-range carrier deployment cycles | Now underway |
| Sustain | Fueling and maintenance occur without constant return to a dedicated test facility | Fueling demonstrated; full deployment maintenance remains the test |
| Network | USV sensor information enters the strike group's normal tactical picture | Integrated into CSG communications and C2 framework |
| Scale | Multiple autonomous vessels operate concurrently under manageable operator workload | 30 production MUSVs now ordered |
| Fight | Future platforms carry useful combat payloads under robust command and control | Weapons demonstrated on related prototype; Seahawk not publicly armed |
The unmanned surface ship is only half the transition
In April 2026 the first operational Navy MQ-25A Stingray completed its first flight. In May the program received approval for low-rate initial production, and Boeing received a three-aircraft production award in September.
The Navy's FY2026 planning called for an initial MQ-25 carrier deployment beginning in FY2027.
The future carrier group may contain more machines than ships
The carrier and its destroyers remain the high-end combat core. Around them, autonomous aircraft can refuel fighters, surface vessels can extend sensor and weapon geometry, underwater vehicles can search beneath the formation and small expendable systems can perform reconnaissance, deception or one-way missions.
That is a different fleet architecture from simply adding another destroyer to the screen.
Seahawk's failures may be more informative than its successes
How long it stays with the force
A complete deployment would mean far more than a few weeks of integration near established support infrastructure.
How often humans board it
Frequent technician visits would expose a maintenance burden hidden by the phrase “uncrewed.”
Whether it joins Keen Sword operations
Integration into a large allied exercise would show whether the command architecture works outside purely U.S. formations.
Whether it moves into higher-threat waters
The operational significance rises sharply if the vessel moves from transit and exercises into an environment with electronic warfare, submarine and missile threats.
What payload it actually carries
The Navy has disclosed the platform's autonomy far more clearly than its current mission payload.
Hybrid Carrier Screen Builder
This model does not treat a USV as equivalent to a destroyer. It tests how quickly an unmanned layer can increase distributed mission nodes around a carrier while showing the cost, availability and control burden.
Is this the beginning of the hybrid fleet?
Yes in one narrow but important sense: an autonomous ocean-going ship is now being treated as part of a deployed carrier formation rather than as an exercise participant that returns to the test organization afterward.
No in another sense: one unarmed prototype does not yet create a hybrid combat screen. The transformation begins when several unmanned vessels can remain forward for an entire deployment, share data automatically with the strike group, operate through communications disruption and carry useful mission payloads without creating an unsustainable maintenance or operator burden.
The 30-MUSV production order makes that test imminent. If those vessels begin appearing beside carriers, amphibious groups and independent surface action groups in FY2027 and beyond, the traditional carrier strike group stops being a formation made only of crewed ships and aircraft.
Research base
We welcome your feedback, suggestions, corrections, and ideas for enhancements.
Please click here to get in touch