[ APPLICATIONS ]

Six missions that need more than one machine

Each is set out as a concept of operations — the problem, the sequence, the force mix, and what degrades it. No case studies, because we have not earned any yet.

Every mission below runs on the same five-step spine.
01
Detection
02
Human in the loop
03
Assignment
04
Coordinated action
05
Scale
[ Mission 01 · AIR ]
Terrain the mission is flown over
Block 01 — the problem

A target of interest moves 40 km across broken terrain over nine hours. A single aircraft loses it at the edge of its endurance, at the edge of its sensor cone, or the moment it turns to refuel. The operator gets a track, then a gap, then a new track he cannot prove is the same object.

↓ Concept of operations
Block 02 — concept of operations

Continuous custody across four airframes

AIRBORNE ASSETGROUND NODETARGET / CONTACTTASKINGSENSOR
AIR LAYERTARGETGROUNDA-012 KG EO/IRA-022 KG EO/IRA-042 KG EO/IRA-0320 KG RELAYTARGETTARGETT+9 HRGROUND STATIONONE OPERATOR010203040506CUSTODY TRANSFER
01DETECTION
Initial detection
A-01 · 2 kg EO/IR

Onboard detection classifies a moving vehicle and opens a track file with a unique identity.

02HUMAN IN THE LOOP
Operator confirms interest
GROUND STATION

The operator marks the track as a target of interest. Nothing downstream requires further input.

03ASSIGNMENT
Relief aircraft tasked
A-02 · 2 kg EO/IR

The system computes A-01's remaining endurance and launches A-02 to arrive before bingo, not after.

04COORDINATED ACTION
Custody transfer
A-01 → A-02

Track state, identity and sensor lock pass between aircraft while both hold the target in view.

05COORDINATED ACTION
Relay holds the link
A-03 · 20 kg relay

A relay orbits high so the mesh reaches past the ridgeline as the target moves out of direct sight.

06SCALE
Cycle repeats
A-04 · 2 kg EO/IR

The same transfer runs at each endurance boundary. Operator workload does not grow with duration.

Block 03 — why this needs multiple agents
Mission 01

Continuity of track is not an endurance problem, it is a coordination problem. Asset B receives the target state from Asset A before A reaches bingo, so the track identity survives the handoff. No single airframe, at any endurance, produces this.

The rest of this page is the working detail behind that claim — the sequence, the assets, and the conditions under which it fails.↓ Force mix
Block 04 — force mix

6 assets, one operator

Each row opens the configurator preloaded with that configuration. The fleet builder template renders the same objects.
Block 05 — constraints and mitigations

What degrades this, and what the system does about it

Stated plainly because an evaluator will find these anyway. Mitigations are design decisions, not guarantees.

01
GNSS jamming

Position solutions degrade or drop, and a target's geolocation becomes unreliable at the moment it matters most.

Every tracking aircraft in this mix carries GNSS-denied navigation as standard. Track geometry is held by visual-inertial odometry and terrain matching, and absolute coordinates carry a stated confidence rather than being silently wrong.

02
Thermal contrast collapse

Around dawn and dusk, ground and vehicle temperatures converge and EO/IR detection rates fall sharply.

The system flags the crossover window rather than reporting a clean track. Where a Tier 4 night-capable aircraft is in the mix, custody is preferentially handed to it through the window.

03
Mesh range in broken terrain

Ridgelines cut line of sight between aircraft, and a transfer attempted during an outage loses track identity.

The relay is positioned from terrain rather than a fixed pattern, and transfers are scheduled only while both aircraft hold a link. A transfer is deferred rather than attempted blind.

04
Endurance loss with altitude

Above roughly 12,000 ft, thinner air costs hover efficiency and the endurance the handoff schedule assumes no longer holds.

Endurance is computed against density altitude, not sea level. The relief aircraft launches earlier as altitude rises, so the overlap window is preserved.

05
Target behaviour

A target that stops under cover, or splits into two vehicles, breaks the single-track assumption entirely.

The track file forks and the operator is asked which identity to hold. This is a deliberate human decision point, not an automated guess.

Block 06 — next

Take this mix into the fleet builder

Configure this force mix

Bring a mission, not a shortlist

We will walk the concept of operations against your requirement and say plainly where it does not fit.