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.
A position needs twenty kilograms of stores. The ground route is watched, the flying route crosses a ridge at 3,000 m, and the load is split across items that do not all need to arrive at the same time or by the same means.
Mixed air and ground delivery under one plan
The requesting position states what it needs and by when. Items carry priority, not just mass.
The load is split across available assets by urgency, route risk and remaining capacity.
The allocation and its routes are shown as one plan for approval, not as separate tasks.
Time-critical items go by air over the ridge, direct to the position.
Bulk and non-urgent stores go by ground on a route chosen for cover rather than speed.
If a route closes mid-delivery, the remaining load is reallocated against the same priorities.
5 assets, one operator
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.
Above 3,000 m, payload capacity falls and the mass the plan assumed is no longer liftable.
Capacity is computed against the actual route altitude before allocation, so the plan is built on what the aircraft can carry that day.
Wind and visibility close the air leg with little warning.
Ground legs are planned as a fallback for time-critical items, not only for bulk, and the operator sees which items lose their delivery window first.
A released load in wind lands wide, and a wide landing in contested ground is a lost load.
Release is computed from measured wind at altitude, and where accuracy cannot be assured the system recommends a landing delivery instead.
Every delivery is one-way unless the asset returns, and return legs cost endurance nothing else can use.
Return legs are part of the allocation from the start rather than an afterthought, and are shown in the plan.
Take this mix into the fleet builder
Bring a mission, not a shortlist
We will walk the concept of operations against your requirement and say plainly where it does not fit.