Case study · 02

UAS Sensor Emplacement

Turn a short drone flight into persistent ground sensing.

Product Discovery & Concept Development · Independent · Ongoing

Context

The Problem

Small military units face a brutal tradeoff: situational awareness costs exposure. Sending a patrol to monitor a route or chokepoint risks lives. Keeping a drone overhead burns battery, creates an RF signature, and can't scale across multiple points of interest simultaneously.

Traditional unattended ground sensors solve the persistence problem — but they're expensive, require manual emplacement, and take operators into the exact terrain they're trying to avoid.

The design question

How might small units create persistent awareness of key terrain using existing drone platforms and low‑cost sensing — without adding personnel risk?

Discovery

The Pivot That Mattered

Early concepts focused on perimeter security — using drone‑deployed sensors to establish a protective ring around a fixed position. After structured conversations with Marine infantry and special operations personnel, the use case shifted fundamentally:

Original concept

Perimeter protection — monitoring the boundary around a fixed position.

Refined concept

Intelligence collection — temporary monitoring of roads, trails, chokepoints, and named areas of interest.

The distinction matters operationally. Persistent ISR at specific terrain features creates actionable intelligence for movement planning. Operator feedback — not technical feasibility — drove the right problem framing.

Approach

Key Decisions

Minimize RF signature

Operators flagged detectability as the primary concern — not power consumption, not cost. This drove exploration of lower‑signature communication approaches and store‑and‑forward architectures designed to minimize emissions until deliberate data retrieval. The threat environment defines the comms architecture.

Platform independence over deep integration

Rather than designing around a specific drone platform, the concept evolved toward a modular payload approach deployable across a wide range of existing systems. Units shouldn't need a new drone program to adopt a new sensing capability.

Design the full operational workflow, not just the hardware

The technical concept only becomes tactically useful if the deployment, collection, and retrieval workflows are operationally sound. I developed end‑to‑end workflow concepts and pressure‑tested them with operators.

Primary technical risk — Communications architecture. Balancing data fidelity, RF signature, and operational simplicity under contested spectrum conditions is the hardest unsolved problem in the concept.

Results

Outcomes

Multiple sensing architectures developed and evaluated across power, fidelity, and RF tradeoffs.
Use cases refined from operator interviews with Marine infantry and SOF personnel.
End‑to‑end operational workflows produced for deployment, collection, and retrieval.
Communications identified as primary risk area; store‑and‑forward architecture prioritized.

Reflection

What I Learned

The most important insights came from user discovery, not technology research. The largest improvements emerged from understanding how operators actually collect information, where persistence creates real value, and what risks they're willing to accept in the field. A technically elegant solution to the wrong problem is worthless downrange.

Back to home Talk about this work →