The U.S. Navy is racing to build a fleet of large unmanned surface vessels designed to carry missiles, sensors, and modular payloads without putting sailors at risk. But cheap, expendable drone boats already in use by Houthi forces in the Red Sea are exposing a painful gap between that ambition and the threat environment these vessels will actually face. The collision between the service’s high-tech procurement plans and the low-cost swarm tactics now common in contested waters raises hard questions about whether the Navy is building for the right fight.
The Navy’s Unmanned Vision Takes Shape
For years, the Navy has framed large unmanned surface vessels as force multipliers that could extend the fleet’s reach. These ships are meant to function as adjunct magazines and distributed sensors, spreading firepower across a wider area while keeping crewed warships out of harm’s way. The concept is straightforward: pack offensive and defensive systems onto relatively inexpensive, uncrewed hulls that can be risked in ways a destroyer or cruiser cannot. The Navy and Marine Corps formalized this thinking when they released their unmanned campaign blueprint, describing a future in which autonomous systems become “trusted” teammates, fully integrated into warfighting operations rather than treated as experimental add-ons.
That vision is now moving from PowerPoint slides to steel and software. DARPA’s No Manning Required Ship effort produced the demonstration vessel USX‑1 Defiant, which finished construction and entered testing as a purpose-built, crewless hull. Defiant’s design strips out traditional accommodations in favor of endurance, maintainability, and autonomy, signaling a real, funded bet on ships that can operate independently for long periods. In parallel, Naval Sea Systems Command opened a solicitation for the Modular Attack Surface Craft, or MASC, a program centered on containerized unmanned craft that can carry different payloads and act as adjunct magazines. Together, these efforts show a Navy intent on fielding operational unmanned platforms, not just prototypes, even as the threat environment evolves faster than its acquisition cycle.
Red Sea Drone Attacks Shatter Assumptions
While the Navy refines its unmanned fleet concepts, a very different kind of surface drone war is already underway. In the Red Sea, Houthi forces have used explosive-laden unmanned surface vessels alongside UAVs and missiles in a layered mix that has kept U.S. and allied ships under steady pressure. During an on-the-record briefing about Operation Prosperity Guardian, Vice Admiral Brad Cooper described a sustained pattern of attacks involving one-way drones, cruise missiles, and ballistic threats that can arrive nearly simultaneously. The result is a saturation problem: even highly capable destroyers can be overwhelmed if enough cheap weapons are launched at once from multiple domains.
Specific incidents underscore how low-cost platforms can generate high-end dilemmas. In one case, Houthi forces sent a sea drone toward commercial shipping in the wake of a U.S.-led warning, and the explosive craft managed to close within a couple of miles of its target area before detonating. These jury-rigged boats are crude by Navy standards, yet they are reliable enough to force warships to expend expensive interceptors and maintain constant defensive postures. Each improvised drone boat costs a fraction of the missiles and sensor time required to counter it, highlighting the asymmetry between the Navy’s capital-intensive platforms and the low-end tools that can still threaten sea lanes. That mismatch is precisely what the Navy’s unmanned surface vessels are supposed to address, but the Red Sea experience suggests the problem may be more about numbers and resilience than about exquisite technology.
Software and Command Gaps Threaten the Timeline
The challenge facing the Navy’s unmanned ambitions is not limited to shipyards and hardware. A Government Accountability Office review of the unmanned portfolio found that the service has repeatedly underestimated the cost and complexity of digital infrastructure, including command-and-control software, data systems, and sustainment. GAO analysts noted that programs often lacked clear criteria for moving from experimentation into full programs of record, leaving key decisions about autonomy, reliability, and lifecycle support unresolved. For systems that depend on secure networking and real-time data flows to function safely, these shortfalls translate directly into schedule slips and integration headaches.
This software and command layer is where the Navy’s unmanned concept is most vulnerable. The public conversation tends to focus on hull size, missile capacity, and range, but a large unmanned vessel is only as effective as the algorithms steering it and the communications architecture tying it back to human commanders. In congested waters, autonomy software must distinguish between benign traffic and threats while complying with navigation rules; in contested environments, it must keep operating even as adversaries jam or spoof signals. Without robust, tested solutions to those problems, an unmanned surface combatant risks becoming an expensive, slow-moving target. The GAO’s findings suggest the Navy still lacks a mature institutional framework for validating autonomy and C2 at the pace its procurement plans envision, raising the possibility that hardware will arrive before the fleet is ready to employ it safely and effectively.
MASC and the Pivot Toward Speed
The MASC program is emerging as the Navy’s most direct attempt to reconcile its long-term unmanned aspirations with the near-term realities revealed in the Red Sea. According to early descriptions, requirements emphasize payload flexibility, range, and endurance, with a strong focus on a containerized concept that would allow rapid reconfiguration of each craft’s mission set. Naval Sea Systems Command’s request for industry input on fast attack surface drones highlights the desire for platforms that can be produced and modified quickly, potentially in larger numbers than the Navy’s first generation of large unmanned vessels. By treating the hull as a truck for swappable payloads, the service is signaling that adaptability and speed to field may matter more than bespoke, highly specialized designs.
Yet MASC inherits the same vulnerabilities that GAO flagged across the broader unmanned portfolio. Containerized payloads are only as effective as the control systems and networks that integrate them with the rest of the fleet, and the program will still depend on reliable autonomy, resilient communications, and coherent doctrine for employment. If those elements lag behind the hardware, the Navy could end up with a flotilla of well-armed but operationally brittle craft that require close human babysitting, undermining the very cost and manpower advantages unmanned systems are meant to provide. The Red Sea’s cheap, one-way attack boats show that adversaries can iterate tactics and designs in months; MASC will only fulfill its promise if the Navy can match that tempo not just in shipbuilding, but in software updates, concept development, and training.
Building for the Fight Ahead, Not the Last War
The tension between the Navy’s high-end unmanned vision and the low-cost threat environment it faces today is not easily resolved. Large, missile-laden unmanned ships could help restore magazine depth and distribute risk across the fleet, but they will operate in waters where adversaries already use expendable drones, mines, and missiles in combination. The Red Sea experience suggests that future conflicts at sea may be defined less by individual platform sophistication and more by the ability to absorb losses, reconstitute quickly, and maintain decision advantage amid constant, low-cost harassment. In that context, the Navy’s investments in large unmanned vessels, MASC, and supporting digital infrastructure will need to prioritize resilience, redundancy, and rapid adaptation over sheer technical ambition.
That shift will demand more than new hulls and better software. It will require acquisition processes that can spiral upgrades into the fleet in months instead of years, operational concepts that treat unmanned craft as expendable scouts and decoys as much as as strike platforms, and training pipelines that accustom sailors to commanding mixed formations of crewed and uncrewed ships under fire. The Navy’s current programs show it understands the potential of unmanned systems, but the Red Sea’s drone boats are a reminder that adversaries get a vote, and they may choose to fight with tools that are far cheaper and cruder than the systems the United States is building. Bridging that gap will determine whether the Navy’s unmanned surface fleet becomes a decisive advantage or an elegant solution to the wrong problem.
More from Morning Overview
*This article was researched with the help of AI, with human editors creating the final content.
