Logistics Is the Capital Question: Simon Sparkes and the Hybrid Navy’s Hidden Constraint

Simon Sparkes has put his finger on the constraint most hybrid fleet concepts quietly assume away: an uncrewed navy still has to be fueled, armed, repaired and commanded at distance. My forthcoming 2027 book argues that this is not a support problem sitting beside the capital ship question. It is the capital ship question.

What Sparkes Is Telling Us

On November 1, Simon Sparkes, a test pilot at the Norwegian Defence Materiel Agency, published “The Hybrid Navy’s Hidden Constraint: Logistics.” His starting point is the attraction of uncrewed vessels: no crew to feed or accommodate, smaller hulls, lower cost, fewer people for the same combat output. Those ideas have sound baselines, he writes, but a fleet of USVs will still need “fuel, spares, software updates, payload swaps, maintenance windows, recovery assets, data management, secure communications support and forward basing.” Many of those still need people to deliver them, and they need a new logistics concept built on programmed periods of activity rather than the reactive style of crewed operations.

He then works through five constraints:

1. No crew does not mean no support construct. Fuel, lubrication, failures from wear or enemy action, payload interfaces, hull deterioration, batteries, and launch and recovery systems all remain. The support tail may be smaller in some areas and larger in others.
2. Forward basing becomes critical. Each navy must decide where USVs are launched, recovered, refueled, repaired, rearmed, reconfigured, stored and secured. A regular return to the UK may have little operational utility.
3. Re-arming is not a minor detail. Where are weapons loaded, who certifies the vessel afterward, how are weapons secured, and who makes a damaged but still armed vessel safe? He calls this “safety, security and escalation management.”
4. Payload swapping requires infrastructure. Containers need craneage, trained personnel, mobile test equipment and software validation, especially for weapons employment and veto. “The container may present a flexibility in the delivery of a particular task, but it is not the whole capability. The support to that containerised ecosystem is.”
5. The Hybrid Navy may need a new class of support ship. The Royal Navy’s Common Combat Vessel must do more than control USVs. It must recover, refuel, reload, repair, host remote operators, manage data and relay communications.

His takeaway is the one I want to carry forward: the decisive question is whether navies can “support, arm, repair and command” uncrewed vessels at realistic operational distances over normal deployment periods, not only whether they can buy them quickly.

Why This Is a Capital Question

My book, Re-Imagining Capital Ships in the Autonomous Era: An Early Agenda of Questions for Naval Power, does not argue for a fleet. It argues for an order of questions, and it insists that the questions with budget lines attached (how many hulls, what tonnage, what unit cost) come after the conceptual ones. Sparkes’s article is, in effect, a field report on what happens when that order is reversed.

Question Six in the book asks where logistics sits in a re-imagined capital ship. Doctrine has always treated oilers and ammunition ships as necessary but never “capital.” The fleet was organized around combatants and logistics followed. If combat power is distributed across a mesh of manned and unmanned nodes, I argued, the ability to keep that mesh fueled, armed and repaired becomes the new center of gravity. The aggregate sustainment burden “does not shrink just because it has been distributed across smaller platforms, it simply changes shape and moves earlier in the planning process.”

That is Sparkes’s “smaller in some areas but larger in others” in different words. He supplies the engineering detail. The book supplies the reason it matters strategically: an adversary who understands intelligent mass will not sink the nodes one at a time. It will look for the sustainment chokepoints that keep the mesh fueled and rearmed, on the theory that starving the mesh is more efficient than attriting it.

Question Nine adds the arithmetic. A fleet availability rate of seventy percent sounds respectable until you recognize that roughly a third of your intelligent mass is not there on any given day. Exquisite platforms were few enough to track by name. A mesh of hundreds of low-cost nodes, each individually less monitored, is a much harder data and logistics problem. Chapter Fourteen makes the manpower point Sparkes implies: uncrewed vessels may reduce exposure on forward platforms without reducing the demand for mariners at all, shifting it toward remote operators, payload managers, and recovery and repair teams. The honest test of success is not a smaller crew roster. It is more operational presence per unit of scarce human effort.

Where the Book Meets Each Constraint

Each of Sparkes’s five constraints lands on ground the book already covers, from a different direction.

Sparkes’s constraint	Where the book meets it	What the book adds
No crew, still a support construct	Chapters 9, 13, 14	The “drydock problem” and robotic hull inspection; predictive maintenance that turns unplanned downtime into scheduled downtime; operators who must be fluent in both a hardware domain and a software domain
Forward basing	Chapters 3, 6, 14	The SOUTHCOM Special Mission Vessel as a converted commercial hull serving as a forward operating base; using existing ships as motherships to build doctrine during a hull gap; the Military Sealift Command and Marine Corps layered distribution models
Re-arming	Chapters 4, 14 and Question Seven	Carrying modules from a commercial offshore vessel to a warship at sea; moving selected munitions by low-profile connectors; accountability when a system has been handed off several times
Payload swapping	Chapters 4, 9	Why the Littoral Combat Ship’s modules failed while Denmark’s STANFLEX and the Cube system worked: where in the design process modularity is decided
A new class of support ship	Chapters 6, 13, 14	The Common Combat Vessel as “central brain”; the missing middle tier between a manned hub and a tactical connector; the warning that a mothership metaphor can work against a mesh

Three convergences deserve more than a table row.

Payload swapping is a design decision, not a container. Sparkes says the support to the containerized ecosystem is the capability. Chapter Nine reaches the same verdict through the Littoral Combat Ship. The Navy sold a hull that could swap mission modules in port, but the swapping infrastructure, trained crews and logistics tail were never fully funded, and by 2016 it abandoned the concept. The lesson is not that modularity fails. Denmark has run it since the 1980s because it decided modularity before the keel was laid, in standardized interfaces, frames and handling systems. In Chapter Four, SH Defence’s Peter Liisberg made the point that a mission bay full of unmanned systems is merely storage unless the ship can also launch and recover them. Modularity without that infrastructure is inventory, not capability. The Cube system moves containerized payloads through the ship on tracks in roughly ten minutes, up to Sea State 5. That is a direct answer to Sparkes’s craneage problem, and the Navy’s Special Mission Vessel requirement, with its non-crane-based launch and recovery system, points the same way.

Integration is harder than operation. Sparkes lists batteries, interfaces and rearming among the things that need people and procedures. Chapter Fourteen shows the same pattern in the Marine Corps’ 2026 shipboard testing of the TRV-150C cargo drone aboard a San Antonio-class ship. Integrating a system onto a ship is usually harder than flying it. Deck procedures, battery certification, hazardous-material rules and airspace coordination determine whether a capability becomes routine or stays a demonstration.

The support ship and the “central brain” are different jobs. Chapter Six argued that the Defence Investment Plan describes the Common Combat Vessel as the central brain that will “connect and control the uncrewed elements,” without saying whether it is a capital asset in the old sense or a node. Sparkes adds what that description leaves out: the ship must also support the vessels it controls. Chapter Fourteen identifies the same gap from the American side. Military Sealift Command has crewed oilers at one end and small receivers like the Seahawk at the other, the Marine Corps has amphibious ships and cargo drones, and neither has fielded the hull in between. MARTAC’s 82-foot T-82 Leviathan is a candidate, but its figures are trade-show figures and prototype trials are not expected before winter or spring of 2027. The hull matters less than whether the services can fold it into the sustainment architecture they are already building. Chapter Thirteen adds a caution. If the support ship becomes a mothership that tightly controls its boats, it recreates a disaggregated fleet with a larger flagship at the center. Control and support should be designed as separate functions.

Where Sparkes Pushes Further Than the Book

The book is an early agenda of questions, and Sparkes answers or sharpens three of them.

Programmed rather than reactive logistics. Question Nine of the book notes that predictive maintenance, of the kind built into the CH-53K, matters because it converts unplanned downtime into scheduled downtime. Sparkes generalizes the point to the whole fleet. A hybrid navy cannot sustain itself reactively, because there is no crew aboard to improvise a repair. Support has to be planned into periods of activity. That is a different operating rhythm from a crewed navy, and I did not state it as plainly as he does.

Rearming and certification. The book raises accountability and rules of engagement for systems handed off across controllers, and it notes that the Corps’ low-profile connectors can carry selected munitions. It does not ask Sparkes’s more basic questions: where weapons are loaded, who certifies the vessel afterward, who makes a damaged but still armed vessel safe. He is right that this is safety, security and escalation management as much as supply. It belongs on the agenda, and I take it as an addition to Question Seven.

Persistent presence has limits. The book cites Bluebottle’s ability to stay on station for months on solar, wind and wave power as an example of reach no manned patrol fleet can match. Sparkes’s reminder that hulls deteriorate and nothing can stay perpetually on operations applies even there. Energy endurance is one limit among several: hull condition, payload interfaces and software all need recovery and attention on a schedule. Planning for that schedule is part of the availability question, not a footnote to it.

What a Navy Should Do With This

Sparkes ends with a question rather than a program, and so does the book. Combining the two, four practical steps follow.

1. Score the support concept before the hull count. The book’s seventh design imperative says to design for availability, not just capability, and recommends that milestone review boards score such criteria with real weight rather than treat them as narrative color. A hybrid fleet plan that cannot say where its USVs are launched, recovered, refueled, repaired and rearmed is not yet a fleet plan.
2. Use the hull gap to learn logistics. Chapter Six proposed that Britain use its existing Type 23s, Type 45s and River-class patrol vessels as today’s motherships for cheaper, available uncrewed systems, to build command doctrine and crewing models before the Type 91 to 94 family exists. Sparkes’s list shows what that bridging program must also test: refueling, recovery, payload handling and rearming at realistic distances.
3. Build handling, launch and recovery into the hull. The Navy’s Special Mission Vessel requirement, with fuel transfer, container sockets and a non-crane launch and recovery system, is a usable checklist for any support ship, whether converted or purpose-built.
4. Fix the standards while they are cheap. Chapter Six argued that the UK’s Lunna House partnership with Norway is the occasion to lock in shared data standards and control protocols for node hosting. Chapter Four recorded Rear Admiral Torben Mikkelsen’s argument that modules built to standard 20- and 40-foot dimensions could open a shared allied arsenal. Support interfaces, battery and fuel standards and weapon-handling procedures belong in that same coalition conversation. Sparkes writes from a Norwegian vantage point, and the case for a common logistics model among the northern navies is strong.

The Book Behind the Argument

Re-Imagining Capital Ships in the Autonomous Era: An Early Agenda of Questions for Naval Power is forthcoming from SLDinfo in 2027. It lays out eleven questions, ordered from the conceptual to the operational and industrial, and ends with questions about deterrence and an adversary’s perception that have no clean technical answer. The sixteen chapters between the opening questions and the conclusion test them against the Danish modular tradition, the mother ship and its two industrial paths, Australia’s, Britain’s and the Philippines’ hull gaps, the bifurcated shipbuilding base, ship availability, the payload-utility framework, the mesh fleet, maritime and expeditionary logistics, littoral operations and the undersea domain.

It is built on a simple claim that Sparkes’s article supports from the logistics side: concepts do not build ships, requirements documents do, and a navy that asks the acquisition questions before the capital question will buy the old fleet with a few drones bolted on. For readers working on the Hybrid Navy, Chapters Three, Six, Nine, Thirteen and Fourteen are the closest companions to what Sparkes has written.

Sources

• Simon Sparkes FRAeS, “The Hybrid Navy’s Hidden Constraint: Logistics,” LinkedIn, November 1, 2026.
• Robbin Laird, Re-Imagining Capital Ships in the Autonomous Era: An Early Agenda of Questions for Naval Power (SLDinfo, 2027), Introduction and Chapters 1, 3, 4, 6, 9, 13 and 14.