Uncrewed Systems — UAS, UUV, UGV.

Uncrewed is a procurement decision before it is a technology decision.

The question is almost never whether an uncrewed system can do the task. It is whether the customer can field one: whether spectrum can be allocated, whether national airspace rules permit it, whether there are enough trained operators to hold a shift pattern, and whether the attrition of small systems has been budgeted honestly.

We lead with those questions because they are what decides whether the program works, and because they are the questions that tend to go unasked until after a contract is signed.

The four ways to take it

As a service. We hold the systems, the operators and the maintenance, and you buy hours on task. Fastest to field, no capital, and — as with any service arrangement — it leaves nothing behind unless transfer is written in from the start.

Sold outright. You own the systems. We deliver, integrate, train your operators and maintainers, and sustain them under a defined support arrangement while your own organization matures.

Leased. Between the two, and useful where funding is annual rather than capital, or where a capability is needed for a defined operation rather than permanently.

Taught. Where the equipment is already bought — which happens more often than suppliers admit — and what is missing is a pipeline that produces qualified operators and maintainers year after year. We will train on systems we did not sell.

Where uncrewed wins

Long and dull. A tactical system holding a single orbit over a fixed point for eight hours is doing work that costs materially less than a crewed aircraft doing the same thing, and it does not fatigue.

Hazardous. Airspace where a crewed loss would be politically unacceptable, an underwater route survey, an approach to a suspected device on a road. The correct argument for uncrewed here is not cost, it is that nobody is on board.

Tempo your crew ratio cannot sustain. A small unit that needs its own eyes overhead several times a day is not going to get a crewed aircraft each time. A hand-launched system at platoon level solves a different problem from the one the air wing solves.

Where it does not

Wide-area search still favors a crewed aircraft in most partner-nation programs. The operator is in the environment, the payload is larger, the airspace access is simpler, and the aircraft does not stop working when a link is jammed.

The honest framing is that uncrewed systems are a layer alongside crewed aviation, not a replacement for it. In a layered border architecture they sit between the unattended ground sensors and the crewed ISR aircraft, and each covers what the others cannot.

Uncrewed does not mean unstaffed

This is the most consistently underestimated part of an uncrewed program.

A system on task continuously needs an operator, a relief, a supervisor and analysts to work the product — the same exploitation arithmetic that applies to any sensor. For a persistent tasking the total headcount is often higher than the crewed equivalent, because the aircraft can stay up longer than any one shift can.

Budgeting an uncrewed program as a hardware purchase is the single most reliable way to end up with systems in a container and nobody qualified to fly them.

Attrition is a line item

Small systems are lost. To weather, to link failure, to landing damage, to the ordinary accidents of operating from unprepared ground. A program that bought exactly the number of airframes it intends to have flying in year three has not bought enough.

We price an attrition allowance into every small-system proposal and say so explicitly, because the alternative is a customer watching a capability shrink and assuming they were sold poor equipment.

Counter-UAS is a different problem

Fielding uncrewed systems and defending against them are distinct disciplines with different sensors, different authorities and different operators. We do both, and we keep them separate on purpose — see counter-UAS.