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
Unmanned aerial systems · Autonomous by default
Turbulent Industries designs, builds and flies autonomous unmanned aircraft — one autonomy core, one operator picture, across every domain.
HADI — flight tested
Capability that arrives in a decade deters nobody. We build aircraft that fly this year, on hardware and software we own end to end — airframe, avionics, autonomy.
One autonomy core runs across every platform we field. Add an aircraft to the mission and the picture gets richer, not harder to manage.
Designed, built and flight-tested in-house.
HADI reconfigures in the field between persistent ISR and precision strike — no retooling, no specialist support equipment.
Config / A
Persistent ISR
Config / B
Precision strike
Figures shown are the loitering-munition configuration. VTOL differs — see the full specification.
Software core
The autonomy stack that flies every Turbulent aircraft. Perception, decision and control run entirely on board — no cloud, no dependency, no link required.
Operators give intent. The aircraft resolve the rest.
Air first, because air proves the core. Sea and land inherit it rather than rebuild it.
A force that cannot share what it sees is three forces, not one.
2026
Air · HADI flight tested
2027
Sea · Eddy, Undertow
2028
Land · Talus, Datum
Most forces run a separate stack per domain. Each one builds its own picture, and the seams between them are filled by a person reading a grid reference down a radio. That person is the bottleneck, and the seam is where the target is lost.
We build the opposite way. One autonomy core, one perception model, one message bus — so a new domain is a new body on an existing nervous system, not a new nervous system.
A contact held by an aircraft is already held by the surface and ground pictures. No relay, no translation layer, no retyping. Systems task each other directly, and a person authorises the decisions that matter.
HADI flies on that core today. Eddy and Undertow take it to sea; Talus and Datum take it to ground. Each inherits the work rather than repeating it.
Airframe to firmware, taken in-house from concept through CFD, qualification and flight test.
Concept, aerodynamics and CFD run in-house. The people who size the wing are the people who fly it.
Composite layup and structural qualification on site. No waiting on a supplier to iterate a part.
Flight computer and firmware written against our own autonomy core, not integrated around someone else’s.
Our own test cadence. Prototypes fly in months, and what we learn goes straight back into the airframe.
We hire aerodynamicists, structures engineers, GNC and firmware people who would rather fly a prototype this year than brief one for five.
Programme, procurement and partnership enquiries are handled through official channels.
Contact