ALL SYSTEMS NOMINAL ·
Field Operations · Controlled Procedure

VC-SOP-0131 — Pollinator Drone Swarm Tasking & Deconfliction

The controlled procedure for assigning sorties to the Pollinator Drone Swarm and deconflicting shared airspace — allocating airspace blocks, enforcing separation minima, and resolving conflicts between concurrent swarm operations.

SOP ID: VC-SOP-0131 Rev: D Effective: 2090-05-22 Next Review: 2092-05-22 Owner: Swarm Marshal Approver: Dr. P. L. Isley, CBO Class: Field Operations
One airspace block, one tasked sortie. No two swarm operations may hold the same airspace block in the same time-block without an approved separation plan meeting the minima in Section 6. This SOP governs tasking and deconfliction only — charging, flight discipline, and maintenance are governed separately by VC-SOP-0313 and are not duplicated here.

1. Purpose

To define the controlled procedure for tasking the Pollinator Drone Swarm and deconflicting its operations — assigning sorties to objectives, allocating airspace blocks and time-blocks, applying separation minima, and resolving conflicts when concurrent operations contend for the same volume.

2. Scope

Applies to all mission tasking and airspace deconfliction for the Pollinator Drone Swarm across the canopy operating area under the Spectral Canopy Array. Covers sortie assignment, airspace-block allocation, separation rules, and conflict resolution between concurrent swarm operations. Flight operations — charging, launch/recovery, flight discipline, and maintenance — are governed by VC-SOP-0313 and are explicitly out of scope here. Cultivation tasks the swarm supports are scheduled under VC-SOP-0101.

3. Definitions

TermDefinition
SortieA single tasked swarm objective with a defined drone count, airspace block, time-block, and priority.
Airspace BlockA bounded operating volume (zone × altitude band) allocated to at most one sortie per time-block.
Time-BlockA scheduled window (default 30 min) during which an airspace block is reserved to a sortie.
Separation MinimaThe minimum lateral and vertical spacing required between concurrent swarm operations.
DeconflictionThe Swarm Marshal's resolution of contention for the same airspace block or violation of separation minima.

4. Responsibilities

RoleResponsibility
Swarm Marshal (Owner)Approves the tasking plan; allocates airspace blocks; adjudicates conflicts; owns this SOP.
Tasking PlannerBuilds the sortie schedule from objective requests; assigns drone counts and priorities.
Airspace CoordinatorMaintains the airspace-block map; verifies separation minima before activation.
Flight Operations LeadReceives approved tasking and executes flight per VC-SOP-0313; reports availability.
CHLORAHolds the live airspace-block ledger, detects separation violations, and issues automatic stand-downs on conflict.

5. Equipment & Pre-Checks

6. Airspace-Block & Deconfliction Matrix

Zone (Airspace Block)Default Time-BlockPriority TierSeparation Minima (lateral / vertical)
Z-N Canopy North · Band A (0–8 m)06:00–18:00 · 30-min slotsRoutine pollination15 m / 3 m
Z-S Canopy South · Band A (0–8 m)06:00–18:00 · 30-min slotsRoutine pollination15 m / 3 m
Z-C Central Bay · Band B (8–16 m)06:30–17:30 · 20-min slotsSurvey / metrics20 m / 4 m
Z-Q Quarantine Overflight · Band C (16–24 m)By window onlyRestricted30 m / 6 m · single sortie
Z-E Emergency Corridor · all bandsOn demand · preempts allPriority overrideClear-the-volume; all other sorties stand down

7. Procedure

7.1 Objective Intake & Sortie Build

  1. Tasking Planner pulls the objective request queue and assigns each a priority tier per Section 6.
  2. Build sorties: for each objective set the drone count, target airspace block, and time-block.
  3. Confirm requested drones are flight-ready per VC-SOP-0313; under-resourced sorties are re-scoped or deferred.

7.2 Airspace-Block Allocation

  1. Airspace Coordinator reserves one airspace block per sortie per time-block against the CHLORA ledger.
  2. Verify no overlapping reservation exists; restricted Z-Q overflights are single-sortie and require an approved window.
  3. Hold the Z-E emergency corridor clear at all times; it preempts all routine sorties.

7.3 Separation & Activation

  1. Confirm planned tracks meet the lateral/vertical separation minima for the block (Section 6) against any adjacent concurrent sortie.
  2. Swarm Marshal approves the tasking plan; CHLORA activates the reservations and begins live separation monitoring.
  3. Flight Operations Lead executes the sortie under VC-SOP-0313; tasking does not relax any flight rule.

7.4 Conflict Resolution

  1. On a detected separation violation or double-booked block, CHLORA issues an automatic stand-down to the lower-priority sortie.
  2. The Swarm Marshal adjudicates: re-slot the time-block, re-assign an alternate airspace block, or reduce drone count to restore separation.
  3. An emergency-corridor (Z-E) activation immediately clears the volume; all conflicting sorties stand down and re-task after the corridor closes.

7.5 Quality Checkpoints

8. Records

9. References

10. Revision History

RevDateAuthorSummary
A2086-08-12Swarm MarshalInitial issue; sortie tasking and airspace-block concept established.
B2088-04-25Swarm MarshalSeparation minima table and time-block reservations added.
C2089-09-30Swarm MarshalZ-E emergency corridor preemption and Z-Q restricted overflight rules added.
D2090-05-22Swarm MarshalScope split clarified vs. VC-SOP-0313; automatic CHLORA stand-down on conflict. CBO approval.