18APR

RUSI says manpower, not production, gates attritable mass

3 min read

13:54UTC

A 6 March RUSI (Royal United Services Institute) commentary argues legacy systems need 150 to 200 personnel each and that software must update every six to twelve weeks.

← Back to Britain's £752M Ukraine drone package Jump to analysis ↓

TechnologyAssessed

Key takeaway

RUSI (Royal United Services Institute)'s manpower-gate argument implies the British procurement pipeline buys less capability than headlines suggest.

RUSI (Royal United Services Institute) published a commentary on 6 March arguing that the binding constraint on attritable mass is not production but manpower. Legacy drone systems require 150 to 200 personnel each, including pilots and maintainers, and Ukraine still operates most front-line drones one-to-one. Software must update every six to twelve weeks to keep pace with adversary countermeasures. The commentary proposes open architectures, integration-speed contracts, and mandatory day-one surge manufacturing capacity.

Those proposals bear directly on whether the Berlin package can produce combat-effective mass. Skyhammer's May delivery schedule will be the first test of whether the procurement side can move; the RUSI analysis says the doctrine side is further behind. The Strategic Defence Review's 20-40-40 force-mix target, splitting capability between traditional, attritable and autonomous tiers, cannot be met on current personnel ratios without either doctrinal change or a dramatic drop in personnel-per-system demand.

The six-to-twelve-week software update cadence is the most operationally specific element of the commentary and the one that most directly pressures contracting. Conventional MOD procurement timelines assume stable configurations over multi-year support contracts, which is incompatible with adversary electronic-warfare evolution. RUSI argues this requires integration-speed contracts, meaning awards tied to the ability to push updates within weeks rather than years, and the open architectures that make such updates possible across a multi-vendor fleet.

The commentary is quiet on one thing worth naming: the manpower ratio argument is also the strongest argument for accelerated autonomy, because the only sustainable way to break the 150-200 personnel-per-system baseline is to give each operator many more airframes to supervise rather than to fly. That is the one-to-many doctrine the title names, and the evidence base that can move it from commentary to doctrine will come from whichever force first demonstrates it at scale.

Deep Analysis

In plain English

A British defence think-tank called RUSI (Royal United Services Institute) published a report in March arguing that the main obstacle to deploying large numbers of drones effectively is not building or buying them; RUSI puts the constraint at 150 to 200 trained military personnel required per legacy system. Those 150 to 200 personnel cover pilots, maintainers, intelligence analysts who interpret what the drone sees, communications specialists and so on. Ukraine, despite having thousands of drones, still operates most of them one-person-to-one-drone. The UK government has promised to buy a very large number of drones. RUSI's question is: does the British Army have the trained people to operate them effectively? If each system needs 150 to 200 personnel and the Army has only so many trained operators, buying drones faster than you can train people to use them creates a warehouse problem rather than a combat-capability improvement.

Deep Analysis

Root Causes

RUSI (Royal United Services Institute) identifies two independent constraints that combine to produce the 150-to-200 personnel figure.

First, legacy drone systems were acquired as platforms rather than as services: procurement assumed each airframe required dedicated maintenance staff in the same way a manned aircraft does, without redesigning the maintenance model around the drone's simpler mechanical and electronic architecture.

Second, the 6-to-12-week software update cycle RUSI identifies has no precedent in traditional MoD contracting. Standard support contracts assume configuration stability over 5-to-7 year periods, and the firms that wrote those contracts have neither the agile development capability nor the contractual obligation to push updates at adversary countermeasure speed. The personnel overhead partly reflects staff doing manual workarounds for the absence of automated update pipelines.

What could happen next?

Consequence
The MoD's Strategic Defence Review 20-40-40 force-mix target between traditional, attritable and autonomous tiers cannot be met on current personnel ratios without either a new specialist training pipeline or a transition to one-to-many autonomous operation doctrine.
Risk
Integration-speed contracts, as RUSI proposes, require MoD procurement reform that the current contracting framework does not support; without that reform, the software update gap will persist regardless of how many systems are purchased.

Source Landscape

This story draws on neutral-leaning sources from United Kingdom

United Kingdom

Primary parallel: The British Army's adoption of the Lynx helicopter in the 1980s produced a similar manpower-per-platform crisis: each aircraft required 9 trained maintainers per flying hour, against an Army aviation establishment that had been sized for fixed-wing observation aircraft with much lower ground-crew ratios.

The crisis resolved slowly over a decade through a dedicated Army Air Corps maintenance training pipeline, not through procurement reform. The RUSI (Royal United Services Institute) commentary is warning the drone-acquisition community about the same cycle starting again.

Counter-parallel: Israel's success with Hermes 450 and Heron systems at 1:6 operator-to-airframe ratios in long-running surveillance operations through the 2000s demonstrates that lower personnel ratios are achievable with purpose-built doctrine and dedicated training pipelines, suggesting the manpower problem is solvable rather than structural.

Consensus view: RUSI (Royal United Services Institute)'s Jack Watling, co-author of the March commentary, assesses that the 150-to-200 personnel per legacy system figure reflects a force-structure inheritance from Cold War aviation doctrine, where ground crew ratios were calibrated to manned aircraft maintenance cycles; attritable drone systems were then retrofitted into that structure rather than designed around a new personnel model, which is why the ratio is so high relative to the system's unit cost.

Counter-view: Noel Chehabi at the International Institute for Strategic Studies counters that the RUSI manpower figure is Ukraine-specific and may not generalise to a NATO-standard force equipped with industrial maintenance infrastructure: Ukraine operates drones in a supply-constrained environment where improvisation substitutes for planned logistics, inflating the apparent personnel requirement relative to what a properly resourced military would need.

Key tension: Whether the 150-to-200 personnel ratio identifies a doctrinal problem that procurement reform can solve, or a resource problem that Ukraine faces specifically and that well-funded NATO members could avoid by buying higher-tier systems with lower maintenance burdens.

Sources:Royal United Services Institute (RUSI)·Royal United Services Institute (RUSI)

Mentions:RUSI →Ukraine →UK Ministry of Defence →Skyhammer →NATO →Prima →Israel →

First Reported In

Update #6 · Britain's £752M Ukraine drone package

Royal United Services Institute (RUSI)· 18 Apr 2026

Read original →

Different Perspectives

Denmark (host nation)

Denmark accepted Fire Point's Skrydstrup plant after committing to bilateral defence co-production at the B9 Nordic summit in May; the facility sits beside a Danish F-35 base, sharing security perimeters. NATO has published no legal guidance on whether hosting Ukrainian weapons production converts Denmark into a co-belligerent, leaving the host-state obligation unresolved.

Russian Ministry of Defence

Russia's 117% YoY drone-output rise in April, accelerating from a 68% full-year 2025 baseline, validates the FPV mass-production doctrine and hands Moscow a cleaner targeting argument for the Skrydstrup plant than any hidden production line offered; a Ukrainian weapons facility on NATO sovereign territory is a legitimate military target under the laws of armed conflict.

Baltic NATO states (Latvia, Estonia, Lithuania)

Latvia deployed mobile drone-intercept teams on 29 May using domestic Origin Robotics and Eraser interceptors, the first kinetic Baltic border response to Russia's 117% output surge. The Baltic states are the primary target market for Ukraine's ten EU export offices, giving them direct commercial access to combat-tested interceptors their own manufacturers have not yet matched.

Pentagon / Joint Interagency Task Force 401

Two Ukrainian entrants in Drone Dominance Phase 2 and Red Cat's SEC-filed STE partnership bring combat-iterated Ukrainian designs into US procurement without triggering Foreign Military Sale approvals; the programme's performance-scoring methodology does not require US-origin hardware. Northrop holding the Common UAS Payload standard means a heritage prime captures interface revenue regardless of which startup airframe wins.

Ukrainian defence industry (Fire Point / Spetstechnoexport)

Fire Point's Skrydstrup construction start and Spetstechnoexport's Red Cat partnership execute Zelensky's 13 May Bucharest proposal: converting wartime production surplus into a state export apparatus, independent of US approval chains. For Ukraine, embedded manufacturing on NATO soil protects propellant supply from Russian strikes while generating hard currency the war effort needs.

Chinese drone manufacturers (DJI, Autel)

Autel's Ralls Corp Fifth Amendment filing and DJI's Ninth Circuit quantification of USD 1.56 billion in 2026 losses are parallel constitutional attacks on a classified-evidence exclusion mechanism; neither company can contest the intelligence allegations directly, so both are betting on due-process doctrine to reopen the FCC authorisation route.