Skip to content
Training and test

Train it. Measure it.
Then make it harder.

An exercise is only worth the measurement that comes out of it.

Scenario authoring

If you can describe it,
you can fly it.

A scenario is a set of decisions, not a flight plan. These are the decisions.

01

Formation and geometry

Wedge, line, column, ring, stacked. Re-form mid-run.

02

Timing and waves

Arrivals to the second. Hold a wave back until the first is engaged.

03

Multiple axes

Several bearings at once, so no sector owns the problem.

04

Mixed profiles

High-value tracks, decoys and saturation in one picture.

05

Low and slow

Under the clutter threshold, at the speeds a small drone actually flies.

06

Terrain masking

Approaches shaped by your own ground. They appear late.

07

Behavior under engagement

Press on, disperse, or re-form and attack again.

08

Repeatability

The same scenario, re-flown identically, on demand.

Illustrative
Who trains with it

Crews, programs,
and the systems themselves.

One puts people under pressure. The other puts equipment under it. Both need the same threat, on demand.

Air defense and C-UAS crews

Repeated exposure to saturation and ambiguity, until prioritizing under pressure is trained rather than improvised.

Test and evaluation

A repeatable stimulus. The same scenario re-flown is what makes two systems comparable.

Force protection

Exercises built on the ground of your own installation, not a generic range.

Critical infrastructure and events

Airports, energy sites, ports. The rehearsal has to include everyone who responds.

C-UAS manufacturers

Find where detection, tracking and effector logic break down before a customer does.

Doctrine and tactics

Try a tactic, measure it, change one variable, measure again.

On the range

Several full repetitions
in one booking.

Range time is the scarce resource, not aircraft. The hardest run should be the last one, not the only one.

  1. 07:00

    Set up

    Kit unpacks, aircraft prepared. One team, no flight crew per aircraft.

  2. 08:30

    Author and brief

    The opening scenario is built, validated against the range, and briefed to both sides.

  3. 09:30

    First run

    The swarm executes. Everything either side does is recorded on one clock.

  4. 10:15

    Debrief

    Replay in 3D against the numbers. What leaked, and why.

  5. 11:00

    Escalate and re-fly

    Raise the variable that was too easy. Same booking, harder problem.

  6. 16:00

    Close out

    Export the day, and the baseline the next cycle is measured against.

Times are illustrative. A real day is shaped by your range and your approvals.

Next step

Build the first exercise
around your gap.

Tell us what your crews defend and what your range allows. A person replies by email.

Request a capability briefing defense@flightops.io