Persistence is a systems problem.

It is tempting to treat persistence as a single number — hours of flight time — and optimise for it in isolation. In practice, an airframe that can stay airborne for ten hours is only as persistent as the weakest link around it: the data link that drops at range, the ground crew rotation, the handoff between operators mid-mission.

Designing for persistence means designing the whole loop, not just the platform. That includes how sensor data is triaged, how a second crew picks up a mission without losing context, and how the system degrades gracefully when one link in the chain is under stress.

The hardest part of a long-endurance mission is rarely the flight itself — it is the transition points. A shift change, a weather diversion, a re-tasking mid-mission. Each of these is a place where situational awareness can be lost if the system was not built to preserve it.

That is why our approach to ISR platforms treats the ground segment, the comms architecture and the airframe as one connected design problem from the outset, rather than integrating them after the fact.