0006 - Demo Script: Military — Range Management — Fort Campbell

Opening screen

The Live Map is already on screen when the audience arrives. Fort Campbell range boundary visible as a dashed white perimeter. Dark map. A single red dot moves slowly across the range. No legend, no panels, no labels.

The presenter stands in front of the screen and does not reference the UI yet.

Talk track:

“Fort Campbell runs the largest Army UAS training program in the country. On any given training day, you have Groups 1 through 3 UAS at low altitude, rotary wing up high, and occasionally loitering munitions exercises that have historically required shutting the entire range down.”

“Managing all of that today means a lot of coordination overhead — flight schedules, radio calls, manual deconfliction. Your range control officers are good at it. But every one of those coordination touchpoints is a place where things can go sideways, and when they do, your response is only as fast as your slowest radio call.”

“What we’re going to show you today is what it looks like when that coordination overhead drops to near zero. But to get there, we need to talk about trust.”

Click the red dot. Detail panel opens — all fields unknown.

“This is your starting point. Let’s build the picture.”

Layer 1 — Unidentified (red)

The red dot is already running on the map.

Talk track: “This is your starting point. A counter-UAS sensor detected something. No identity. No intent. No authorization. Just a signal.”

Click the red dot. Show detail panel — all fields unknown.

Talk track: “In range management terms, this is a full stop. You don’t know if this is one of yours that lost its data link, a negligent operator who wandered in, or something worse. Until you know, you can’t safely run anything else in that airspace. One unidentified aircraft and your entire range tempo grinds to a halt. That’s the most expensive dot on this map.”

Layer 2 — Declared (orange)

Press Fly Declared. Dot transitions red → orange.

Talk track: “Now we have a Remote ID signal. The aircraft is broadcasting an identity and a pilot name.”

Click the orange dot.

Talk track: “Self-reported. No one checked. This is the digital equivalent of someone calling range control and saying ’that’s my drone.’ You have a name, but you have no way to confirm it’s real, no flight plan on record, and no authority has approved this operation.”*

“This is actually where most range operations live today. Your flight schedules, your radio check-ins — those are declared systems. Someone told you they’d be there, and you took them at their word. That works until it doesn’t.”

“Still a significant disruption if you encounter this unexpectedly. You’re making phone calls, pulling your range control officer off other tasks, slowing everything down.”

Layer 3 — Correlated (yellow)

Press Insert Flight Intent. Yellow polygon appears. Dot transitions orange → yellow.

Talk track: “Now we have a flight plan. Filed through RFMSS or a flight planning service — ATOMx matched it to this telemetry signal automatically.”

Click the yellow dot.

Talk track: “Better. You have context. But filing a plan doesn’t make you trusted — it makes you expected. Nobody has verified who this pilot is, nobody has confirmed the aircraft is what it says it is, and no authority has formally approved this operation. If something goes wrong here, you’re still chasing it down manually.”*

Layer 4 — Authorized (blue)

Press Fly Software-Verified Sim. Blue dot appears.

Talk track: “This flight came through the ATOMx authorization system. The pilot’s identity has been verified through a trusted identity provider. The aircraft has a software credential — validated automatically. And every authority whose airspace this flight touches has reviewed and approved it.”

Click the blue dot.

Talk track: “Verified pilot. Credentialed aircraft. Formally authorized. Every piece of that is machine-verifiable — same inputs, same answer, every time, in milliseconds.”*

“This is the threshold that matters for range management. An authorized flight gets its corridor and stays in it. Your range tempo starts to recover here.”

Layer 5 — Verified (green)

Press Fly TPM Sim. Green dot appears.

Talk track: “This aircraft has a hardware-backed identity — a trusted platform module physically bound to the airframe. You can’t spoof it. You can’t clone it. The signal you’re seeing and the aircraft that was authorized are provably the same thing.”

Click the green dot.

Talk track: “This is non-repudiation. Not ‘we think this is the right aircraft.’ We know.”*

“And here’s what that certainty buys you operationally: this aircraft earns the tightest operating envelope on your range. The 2,000-foot horizontal bubble the FAA requires around an unidentified UAS exists because nobody knows what it’s going to do next. An L5 aircraft — verified identity, authorized flight plan, hardware-attested telemetry — has earned a much smaller footprint.”

Show density comparison diagram.

“The difference between a range running primarily red and orange dots and one running primarily green is not just a safety story. It’s a sortie capacity story. It’s how many pilots you can train in a day.”

“That’s the range we’re building toward.”

The authorization panel

Switch to the range authority browser. Open Flight Review.

Talk track: “Everything we just saw on the map — the blue dot, the green dot — those came from somewhere. This is where the range authority works.”

Show the pending requests queue.

Talk track: “Every UAS operation on this range starts here. A pilot submits a request — the aircraft, the area, the time window, the altitude. The authority reviews it against everything else scheduled on the range. If it fits, they approve it.”*

Approve a flight. Pilot notification appears.

“The pilot is notified immediately. The system records the authorization with a unique ID. From this point forward, that aircraft is blue on the map.”

Point to pilot certificate validation.

Talk track: “The authority can see the pilot’s credentials directly in the review panel. Validated certificates show here. If it’s pending, the authority knows before they approve.”*

“And if a flight plan touches airspace managed by more than one authority — a UAS route that crosses from the primary training area into the helicopter operations corridor — each responsible authority approves their segment independently. No phone calls between them. The system routes the request and collects the approvals.”

A known aircraft goes off-script

Switch back to live COP. Zones visible as overlays. Blue and green dots moving in the UAS training zone.

Talk track: “The range is running. Authorized flights in the UAS training zone, rotary wing corridor active above 500 feet, loitering munitions window coming up at 1400.”

“Watch this aircraft.”

Trigger non-conformance. Green dot drifts. Non-conformant indicator appears.

“This aircraft just left its authorized area. ATOMx caught it the moment conformance broke.”

Click the non-conformant dot. Show the detail panel.

Talk track: “Everything we know about this aircraft is still right here. Hardware-verified identity. Authorized flight. Verified pilot. None of that changed. What changed is that it’s no longer where it said it would be.”*

“This isn’t an unknown intruder. This is a known aircraft behaving unexpectedly. Those are two completely different situations — and ATOMx tells you which one you’re dealing with, instantly.”

Pause.

“Why did it drift? We don’t know yet. Could be pilot error. Could be a technical fault.”

“What we do know: it’s moving toward the loitering munitions corridor. And that window opens in under two minutes.”

“Let’s talk about what happens next.”

Full picture

Switch back to observer view. Zoom out to show full Fort Campbell range. All three zones visible. Mix of blue and green dots in UAS training zone.

Talk track: “This is what we’re delivering.”*

Pause. Let the map speak.

Talk track: “One screen. Every aircraft in your range, classified in real time. Every zone, every authority, every scheduled event — visible, enforced, and actionable.”*

Walk the legend:

“Red — unknown. Full stop until you know what it is.” “Orange — declared. Someone said who they are. You have no reason to believe them yet.” “Yellow — correlated. A plan was filed and matched. Context without authorization.” “Blue — authorized. Verified pilot, credentialed aircraft, every authority approved it.” “Green — verified. Hardware-bound identity. The gold standard. The aircraft that earns the smallest footprint and the most airspace.”

Pause.

“The difference between a range running mostly red and orange dots and one running mostly green isn’t just a safety story. It’s a throughput story. It’s how many units you can train simultaneously. It’s whether a GPS glitch grounds your whole operation or gets resolved in 30 seconds while everything else keeps moving. It’s whether you can run a loitering munitions exercise and a swarm operation on the same range on the same afternoon.”

“Today, that’s not possible. Not because the Army doesn’t have the aircraft. Because the infrastructure to manage that level of complexity doesn’t exist yet.”

Pause.

“This is that infrastructure.”