Human-Machine Teaming: Autonomy Across Air, Land and Sea

One command node, many effectors

In the concept diagram, a crewed H-60-class aircraft carries the team command node. Its crew manages tasking, arbitrates sensor conflicts and holds engagement authority; the quadrotor, the ground vehicle and the rescue boat contribute sensing and reach. No unmanned node needs a full picture, it needs its slice, plus enough autonomy to keep working when the link degrades.

That division is deliberate. Judgment concentrates where humans are; endurance, exposure and repetition go to machines.

The kill chain and the rescue chain are the same chain

Detect, identify, decide, act, assess. A counter-UAS engagement and a maritime rescue run the identical loop with different terminal effects, one ends in a defeat mechanism, the other in a recovery. Systems built for one transfer cleanly to the other, which is why counter-UAS radar, ISR drones and SAR aircraft increasingly share sensor and datalink lineage.

Shortening that loop is the actual technology race. Sensor fusion and onboard autonomy compress detect-to-decide; the human stays in the decide step where accountability lives.

Degrade gracefully or don't field it

Contested environments mean jammed GNSS, intermittent SATCOM and spoofed returns. A teaming architecture is only credible if every node has a defined behavior when it goes dark: return to a rally point, continue the last tasked pattern, or hold and beacon. Those behaviors belong in the requirements document, not in a demonstration script.

What we are building toward

Across our aviation, robotics, counter-UAS and search-and-rescue lines, the common thread is open interfaces at the sensor, datalink and autonomy boundaries, so a customer can add a node without re-procuring the system. That is the practical shape of how technology is reshaping warfare: fewer monolithic platforms, more composable teams.