What Deconfliction Actually Means at the Fleet Level
Airspace deconfliction is one of those terms that gets used loosely enough in UAS sales pitches that it starts to lose meaning. At its core, deconfliction is the process of ensuring that multiple aircraft operating in shared airspace maintain adequate separation — vertically, horizontally, and temporally — to eliminate collision risk and maintain coherent mission execution. For a single-aircraft operator, deconfliction is largely a regulatory exercise: check for NOTAMs, verify LAANC authorization status, stay out of restricted areas. For a fleet operator running 20+ aircraft from multiple crews across a shared operational corridor, deconfliction becomes an active operational problem that requires systems, not just checklists.
This article is written for program managers and chief RPICs who are past the single-aircraft stage and dealing with the practical coordination challenges of multi-aircraft fleet operations. If you're running five or fewer aircraft in non-overlapping areas with clear crew assignments, most of this will feel like overkill. If you're coordinating across sections of a utility corridor with mixed platform types, or planning multi-drone grid surveys at a mining site with overlapping flight paths, read on.
The Regulatory Foundation: What 14 CFR Part 107 Actually Requires
Let's start with what the regulations do and don't say, because there's significant misunderstanding in industry conversations about deconfliction obligations.
Under 14 CFR Part 107, each remote pilot in command (RPIC) is individually responsible for the safe operation of their aircraft. Section 107.31 establishes the visual line of sight (VLOS) requirement — the RPIC must be able to see the aircraft unaided at all times (except under waiver). Section 107.37 prohibits operations that create a hazard to other aircraft. There is no specific regulation that defines a required separation standard between two UAS operating in proximity under Part 107, the way manned aviation has defined vertical and horizontal separation minima in IFR operations.
What this means in practice: when two Part 107 aircraft are flying in the same general area, the obligation falls on each RPIC to maintain awareness of the other and avoid conflict — but the mechanism for doing so is left to the operators. For small programs where every RPIC knows every other aircraft's position by line of sight and radio communication, that's workable. For enterprise programs where aircraft may be out of visual range of each other and RPICs are too far apart for radio clarity, it isn't.
BVLOS (Beyond Visual Line of Sight) operations under Part 107.200 waiver or COA introduce more structure: the FAA typically requires a ConOps that specifies separation standards, detect-and-avoid (DAA) provisions, and airspace coordination procedures. But most enterprise inspection programs operating at scale are still primarily VLOS, with BVLOS waivers for specific corridor segments. For the VLOS majority, deconfliction discipline is self-imposed — which makes program-level standards essential.
Vertical and Horizontal Separation: Working Definitions
Enterprise programs that have thought carefully about internal deconfliction standards typically work with three separation concepts:
Altitude Band Separation
The most common approach for programs with multiple simultaneous flights in the same geographic zone is altitude band assignment: each mission profile is pre-assigned to operate within a specific altitude band (e.g., 100–200 ft AGL for close-up tower inspection, 300–400 ft AGL for wide-corridor photogrammetry passes). Aircraft in different altitude bands don't enter each other's band without a formal mission pause and handoff. This is clean in theory and works well when mission profiles are stable. It breaks down when a specific inspection task requires a platform to leave its assigned band — for example, a multirotor needing to close on a transmission tower top that puts it in the same band as a fixed-wing survey aircraft.
Temporal Separation
For operations where two missions must occupy the same altitude band, time sequencing is the standard alternative: mission A completes its pass and lands (or exits the area) before mission B begins. This is conservative and reliable but has obvious throughput implications. In a program trying to maximize daily flight hours, serial sequencing of overlapping missions can eliminate 25–40% of potential operational capacity depending on mission density.
Geographic Zoning
Hard geographic boundaries — defined as geofenced operational cells or explicitly briefed exclusion areas — are the most operationally durable approach for programs with regular repeating missions. Each crew owns a cell; aircraft don't cross cell boundaries without explicit authorization from the mission supervisor. The weakness here is flexibility: cell boundaries that work for standard operations may not accommodate rerouting around a weather event or an unexpected access restriction mid-mission.
LAANC in the Enterprise Context
The Low Altitude Authorization and Notification Capability (LAANC) system, administered by the FAA and operated through approved UAS Service Suppliers (USS), provides near-real-time authorization for operations in Class B, C, D, and surface Class E airspace. For enterprise operators, LAANC is frequently a daily operational requirement rather than an exception — utility transmission lines, pipeline rights-of-way, and industrial facilities often fall within controlled airspace designations, particularly near regional airports.
A few LAANC mechanics that matter for fleet operations: LAANC authorizations are issued to individual pilots, not to programs or fleets. Each RPIC needs their own authorization for their specific planned operation. If your program has 8 RPICs operating in controlled airspace on the same day, you need 8 separate LAANC authorizations, each reflecting the specific altitude and geographic extent of that pilot's planned flights. Running eight authorizations through an approved USS (most programs use one of the major USS providers integrated into their GCS) is manageable but requires coordination: authorization requests submitted without knowledge of each other can create conflicts when reviewed against available airspace grid cells.
LAANC grid cell altitude limits also create mission planning constraints that aren't always obvious until you're filing the authorization. A grid cell might have a 200 ft AGL authorization ceiling while your photogrammetry mission requires 350 ft for adequate GSD. That requires either a mission redesign (fly lower, accept lower image resolution) or a standard Part 107 waiver process — which is not a same-day solution. Programs operating in complex airspace regularly encounter this ceiling mismatch and need to build LAANC pre-check into mission planning, not flight-day logistics.
UTM and the Direction the Industry Is Moving
The FAA's UAS Traffic Management (UTM) framework, developed in collaboration with NASA and industry stakeholders, represents the long-term infrastructure for managing high-density UAS operations at scale. UTM is fundamentally a network of USS (UAS Service Suppliers) sharing flight intent data — not a single centralized air traffic control system, but a federated information-sharing architecture where operators publish their flight plans and the USS ecosystem flags potential conflicts before they happen.
ASTM F3411 (Standard Specification for Remote ID and Tracking of Unmanned Aircraft Systems) is the standards foundation underlying Remote ID — the broadcast mechanism that allows aircraft to be identified in real time by authorized parties. As of September 2023, Remote ID compliance became mandatory for most UAS operating in the US national airspace. For enterprise fleet operators, Remote ID means every aircraft in your fleet is broadcasting its position, altitude, and identity continuously during flight. This is primarily a compliance requirement, but it also creates a technical substrate for the kind of real-time position sharing that genuine deconfliction requires.
The direction of travel is clear: UTM-integrated operations, with flight intent pre-shared and conflicts flagged through USS services, will be the operational norm for enterprise UAS programs within the next several years. Programs that build their internal coordination workflows around LAANC authorization and Remote ID compliance today are building toward that infrastructure rather than against it.
Practical Deconfliction for the Program Manager Today
Given the regulatory landscape and the limitations of current tooling, here's what actually works for enterprise programs operating at fleet scale before full UTM integration is available:
- Pre-mission altitude band assignment in the mission brief: Every mission gets an assigned altitude band before crews leave the office. Band assignments are part of the official mission brief document, not verbal instructions at the flight line.
- Shared position visibility during operations: A common telemetry aggregation layer — whether that's a shared GCS instance, a purpose-built fleet monitoring dashboard, or a dedicated situational awareness tool — that gives the mission supervisor real-time position of every active aircraft. This doesn't replace RPIC responsibility; it creates a supervisor-level check that can catch developing conflicts before they become close calls.
- Defined conflict resolution protocol: A written procedure for what happens when two aircraft are converging on the same airspace, including who has authority to order a mission abort, what the abort procedure is for each platform type, and how the mission supervisor communicates conflict alerts to RPICs in the field. Radio clarity and a clear chain of command matter more than the specific protocol details.
- LAANC pre-check as a planning step, not a day-of step: Airspace analysis including LAANC grid cell ceiling review should happen during mission planning, ideally 48–72 hours before flight, so that authorization conflicts surface when there's time to address them.
- Incident reporting for all conflict events above a defined proximity threshold: Not just actual near-misses, but any event where two aircraft closed to within a program-defined separation threshold (many programs use 500 ft horizontal or 50 ft vertical as trigger thresholds). Incident data is the input to protocol improvement over time.
Where Deconfliction Breaks Down Even With Good Process
We're not saying that process discipline solves the deconfliction problem completely — it doesn't. There are failure modes that persist even in well-run programs:
Dynamic airspace events — a TFR issued mid-flight, a manned aircraft entering the operational area at low altitude, a helicopter approaching a transmission tower for emergency access — require real-time response that no pre-mission planning can fully anticipate. The contingency procedures (mission abort, return-to-launch, crew alert) need to be practiced and fast. Under real-world pressure, a crew that hasn't drilled the abort sequence makes slower decisions.
Communication failures in remote or RF-saturated environments are more common than programs expect. When an RPIC loses radio contact with the mission supervisor and is simultaneously managing a near-VLOS platform at maximum range, the informal deconfliction system that relies on radio coordination fails immediately. Programs that depend entirely on voice coordination for deconfliction have a single point of failure that operates in exactly the environments where things are most likely to go wrong.
Platform diversity creates deconfliction asymmetries: a fixed-wing cruising at 45 knots and a multirotor hovering for close inspection have very different energy states, turning radii, and abort capabilities. Procedures designed around multirotor performance assumptions may be inadequate when applied to fixed-wing platforms in the same operational area. Platform-specific deconfliction parameters — minimum horizontal separation distances that account for wing loading, minimum abort decision altitudes that account for glide performance — belong in the mission brief, not just in the RPIC's head.
The enterprise programs getting this right are the ones treating deconfliction as a system design problem — defining procedures, building in technical visibility layers, drilling exception scenarios, and reviewing incident data regularly. It's not glamorous operational work, but it's what allows a 30-aircraft program to run day after day without the kind of airspace event that stops operations and surfaces in a safety report.
