Sea domain
Autonomous surface and undersea systems sharing the same Flowstate core — and the same payload modules — as our aircraft.
Land domain
Ground systems that inherit the air picture rather than rebuild it, and carry the aircraft forward instead of waiting on it.
Autonomy core
Perception, decision and control on board. No cloud, no dependency, no link required.
Flowstate
Works
Airframe to firmware, taken in-house from concept through CFD, qualification and flight test.
Capability
Type to filter · Enter to open · Esc to close
Land domain · Concept
Ground systems that inherit the air picture rather than rebuild it — and that carry the aircraft forward instead of waiting on it.
Concept · first systems 2028
The ground element is usually last to see and first to be surprised. It waits on air support it does not control, reading a picture assembled somewhere else and relayed by voice.
Both systems here change who holds the sensor. One carries an aircraft; the other is left behind and keeps watching. Neither has a separate console, because neither builds a separate picture.
Two concepts. One moves, one stays.
Land / 01 · Concept
Uncrewed ground vehicle
Small electric UGV that carries a HADI as a tethered mast, then releases it to fly free when the mission needs reach. Doubles as a forward launch, recovery and recharge point.
The ground element stops waiting for air support and starts carrying it.
Land / 02 · Concept
Unattended ground sensor
Hand-emplaced node running seismic, acoustic, magnetic and passive infrared. Sleeps at near-zero draw for months, wakes on a cue from an aircraft or a neighbour, and reports tracks rather than raw detections.
Unattended sensors normally come with their own network and their own console. Datum has neither.
Targets, not measurements. Nothing here has been built.
| Target | Talus | Datum |
|---|---|---|
| Class | Mobile | Static, emplaced |
| Emplacement | Driven | Hand, single person |
| Propulsion | Electric | None |
| Sensing | EO / IR · RF | Seismic · acoustic · magnetic · PIR |
| Standby | Days | Months |
| Carries aircraft | Yes — tethered or free | No |
| Reports | Tracks | Tracks |
| Autonomy | Flowstate, on board | Flowstate, on board |
Marked rows differ between systems. Everything else is common by design.
Four consequences of a ground system that shares the aircraft’s picture.
A tethered aircraft sits an order of magnitude above what a vehicle mast can reach, and comes down when the vehicle moves.
Launch, recovery and recharge happen at the ground element rather than at a rear airfield. The aircraft is where the requirement is.
Emplaced sensors report resolved tracks into the shared picture. Nobody watches a console waiting to interpret a seismic trip.
An aircraft passing overhead can wake a field of Datums. They sleep the rest of the time, which is why they last months.
Neither system is frozen. Operator input now is worth more than a requirement document later.
Register interest