Presented at Commercial UAV Expo 2026 in Las Vegas as part of the session “Before You Scale: The Operational, Technical, and Strategic Realities of Building a Drone Program.”
There’s a familiar pattern in utility drone-in-a-box programs. The dock goes in, and then the problems show up: an RF dead zone no one saw on the coverage map, an access road that floods, an emergency response time that doesn’t hold up.
Why now
Utilities are moving from pilot docks to permanent infrastructure — multi-site rollouts, dock-hopping fleets, and long-term contracts. In a pilot program, a bad site is a lesson. In a permanent installation, it’s a stalled program.
Apply the systems lens
Site selection is not a real estate decision. It’s a systems engineering problem — specifically, a system-of-systems problem. You’re not just siting a dock; you’re siting the intersection of flight operations, communications infrastructure, logistics and power, and a regulatory envelope that has to scale.
Treat it like any other system-of-systems design: define the interfaces, understand the failure modes, and validate before you commit — not after.
Four domains, evaluated as interfaces
Each domain should clear validation on its own, but they have to be evaluated as interfaces in one system rather than as independent problems.
- Flight operations and airspace. What gets missed: approach and departure paths in off-nominal weather, and real emergency landing options. What you see later: the only viable landing zone sits inside an energized substation fence line.
- Communications. What gets missed: RF propagation near substation equipment — interference that never shows up on a coverage map. What you see later: if satellite is the only backhaul, it’s now a single point of failure for command and control.
- Power and logistics. What gets missed: power requirements aren’t finalized before the pad is poured, and maintenance access is restricted. What you see later: inconsistent backup power becomes a safety risk, and truly remote sites change the risk math.
- Regulatory scalability. What gets missed: a site sized for a single-dock §44807 exemption with no path to broader BVLOS authority. What you see later: sensor coverage and detect-and-avoid infrastructure the site can’t support — and you may need to re-site entirely.
Your regulatory posture is the sum of your airspace, comms, and logistics decisions.
A four-phase decision framework
- Desktop screening — does this site survive elimination?
- Onsite validation — does the site hold up to what you assumed on paper?
- Cross-domain review — does every domain sign off independently?
- Commit.
The site disqualifier checklist
- No verified line-of-sight RF path under realistic conditions
- Emergency landing options inside energized or restricted areas
- Power infrastructure that requires an unbudgeted upgrade
- Site access that fails in bad weather
- No defined path to future regulatory scaling
- No documented decision record
- For remote sites: no power margin sized for self-sufficiency
- For remote sites: no predictive-maintenance signal between visits
Any one of these might be manageable. Two or more together, and it’s not a site risk — it’s a system risk.
Communicate in the business’s language
Translate site risk into the terms the business already tracks: cost, schedule, and the safety case. Systems thinking isn’t just how you evaluate sites — it’s how you get people to trust the evaluation.
The site is the system
The drone-in-a-box programs that scale well aren’t the ones with the best aircraft. They’re the ones that treated site selection like an engineering decision from day one.
Planning a dock rollout? Talk with us about drone program strategy.