[ AIRSPACE DOCTRINE ]

We ground ourselves so air attack never has to.

Every fire aviator knows the rule, and every drone company should say it out loud: if you fly, we can't. An unknown drone over an incident grounds the tankers and the helicopters, and a grounded air program costs more than any drone can deliver.

So we built the system backwards from that rule. The fleet's first obligation isn't to fight fire. It's to never be the reason crewed aviation can't.

How the system yields

Listen, always

Every operation runs with continuous ADS-B monitoring. Crewed aircraft in the operating area appear in AD.OS as first-class tracks, not an afterthought.

Compute the approach

The system computes closest point of approach for every crewed track, continuously. Proximity isn't noticed; it's calculated, with margins.

Yield by procedure

Air attack inbound means the operator is alerted and the fleet yields: altitude, standoff, or full ground-and-hold. Deconfliction is architecture, not etiquette.

Standing commitments

TFR compliance

Temporary flight restrictions are hard boundaries in the system: geofenced, not advisory.

Coordination first

Operating procedures are developed with the agency and its air program before wheels leave the ground, never assumed.

Visibility to command

Every aircraft position publishes to the common operating picture and to TAK. Incident command always knows where the fleet is.

No exceptions culture

There is no mission profile in which the fleet contests airspace with crewed fire aviation. None.

ADS-B MONITORING & CPA ALERTING: IMPLEMENTED IN AD.OS · OPERATING PROCEDURES: COMMITMENT, DEVELOPED WITH EACH AGENCY BEFORE OPERATIONS

Ask us the hard questions.

If you run an air program, we want your scrutiny. It makes the doctrine better. Bring your worst-case scenario.

Talk to us