How Utilities Run Multi-Site Drone Inspection Programs

A decade ago, the question utilities asked themselves about drones was whether to use them at all. Five years ago, the question was how to start a program. Today, the question is how to run an established program well across a service territory that may span tens of thousands of square miles, with multiple operating models, multiple stakeholder groups, and inspection demands that never quite catch up to the asset base.

This article is for the program lead, T&D engineering manager, or asset management director responsible for the operational discipline of an active utility drone program. It covers what actually works at scale: program structure, the in-house and contractor mix, multi-site coordination, recordkeeping discipline, and the metrics that matter.

Where the Program Sits in the Organization

Drone programs at utilities started in different places depending on which group sponsored the first deployment. Some grew out of T&D engineering. Some grew out of vegetation management. Some grew out of customer operations or storm response. Where the program lives inside the organization shapes the priorities it serves and the operational disciplines it develops.

The pattern that has converged at most large utilities over the last few years places the drone program under a director-level role inside transmission and distribution, with reporting relationships into engineering, operations, and asset management. The program lead is typically a UAS program manager or chief pilot reporting into a director, with budget authority over equipment, pilots, training, and software.

Underneath the program lead, the operational structure usually includes a small set of in-house pilots who run the core operations, a project management layer that coordinates work across the service territory, and relationships with contracted services firms that handle specialized work and capacity expansion. The exact headcount varies with the size of the utility, but the role structure is broadly similar.

What works less well is when the program is owned by a smaller group within the utility, like a single team within asset management, and has to negotiate access to other teams' assets for inspection work. Programs without clear cross-organizational authority struggle to maintain consistent inspection cadence and consistent recordkeeping discipline.

The In-House and Contractor Mix

Almost every large utility drone program runs a mix of in-house pilots and contracted services. The split varies, but the underlying logic is consistent.

In-house pilots typically handle the recurring work: patrol inspections of transmission and distribution circuits on scheduled cycles, substation inspections, vegetation management surveys, and the day-to-day inspection backlog. The in-house team understands the utility's specific procedures, has the security clearance for restricted facilities, and operates under the utility's safety management system.

Contracted services typically handle three categories of work:

Specialized inspections. LiDAR mapping, complex BVLOS operations, helicopter-mounted drone deployments, or other inspection types where the equipment and expertise sit with specialist firms rather than with the utility.

Capacity expansion. During peak demand periods (post-storm assessment, year-end inspection push, regulatory deadline-driven work), contracted services scale capacity beyond what the in-house team can handle alone.

Geographic coverage. Service territories that span hundreds of miles often include remote areas where in-house deployment is impractical. Contracted services with regional teams handle the geographic edge of the service territory more efficiently than centralized in-house deployment.

The software question that comes out of this mix is whether contractors are operating inside the utility's drone platform or maintaining their own records that get shared with the utility on completion. Programs that have moved contracted services into the utility's own platform have generally found that the operational record is more consistent and the audit trail is more complete than when contractors maintained separate records. The trade-off is that contractor access has to be managed carefully, with project-scoped permissions that prevent contractors from seeing data outside their specific engagement.

Multi-Site Coordination Across Service Territory

A service territory of any meaningful size creates coordination problems that smaller drone operations do not face.

The same fleet, the same pilots, and the same equipment are not at the same place. Aircraft are distributed across district offices or regional bases. Pilots are deployed to specific territories. Equipment moves with the work. Coordinating this without losing track of what is where is a non-trivial operational discipline.

The patterns that work at scale:

Decentralized deployment with centralized record. Aircraft and pilots are deployed to district offices, but the operational record lives in a single central platform. The district team logs flights, files reports, and accesses local equipment, but the records are consolidated centrally for visibility, recordkeeping, and audit. This pattern requires a platform that supports both local access for the field team and central visibility for program management.

Asset-based work assignment. Inspection work is organized around the specific assets being inspected (this transmission line, this substation, this vegetation segment), not around the people doing the work. This makes it easier to track inspection completion against the asset base and to identify gaps where the inspection cycle has fallen behind.

Inspection cycle tracking. The platform should track when each asset was last inspected and when it is next due. This is the foundation of inspection backlog management, which is one of the metrics regulators and internal asset management teams care about most.

Cross-territory currency tracking. A pilot certified to work on transmission may not be cleared to work on distribution. A pilot cleared for substation work may not be cleared for energized work. The platform should track these currencies and prevent assignments that put pilots into work they are not cleared for.

Recordkeeping for the Three Audiences

Utility drone programs maintain records for three audiences, and the records have to satisfy all of them with the same source of truth.

The FAA. Standard commercial drone compliance, including pilot certification and currency, aircraft registration, Remote ID compliance, airspace authorization where required, and incident reporting for events meeting reporting thresholds.

Internal compliance. Inspection completion rates against the annual plan, defect identification and follow-up tracking, pilot training and currency records, equipment maintenance posture, incident response procedures and outcomes, and the program's overall operational discipline. Internal compliance audiences usually include the utility's safety, reliability, and asset management functions.

External compliance. State public service commissions, regional reliability organizations, federal regulators where applicable, and sometimes courts or arbitration panels in litigated matters. These audiences look at the drone program as evidence of the utility's broader asset management and operational discipline.

A program that handles the FAA layer but neglects the internal layer will struggle during internal audits even when the regulatory posture is clean. A program that handles internal and FAA layers but neglects external compliance will struggle when external scrutiny arrives. The discipline of running the program is largely the discipline of maintaining records that all three audiences will accept.

KPIs That Utilities Actually Track

Mature utility drone programs track a small number of operational metrics that signal program health.

Inspection completion against plan. The percentage of planned inspections completed within the planned window. A program that is consistently behind on completion is heading toward an asset management problem.

Defect identification rate. The number of defects found per inspection or per asset inspected. Tracking this over time reveals both the value the drone program is producing and any changes in the underlying asset condition.

Defect closure rate. The percentage of identified defects that have been remediated within their target window. This metric ties the inspection program to the maintenance workflow and is often where utilities discover that defects are being identified faster than they are being closed.

Pilot currency rate. The percentage of active pilots within the 24-month Part 107 recurrent window. A program with a falling currency rate is heading toward operational restrictions.

Equipment utilization. Flight hours per aircraft per month, used to size the fleet. Aircraft with very low utilization may be candidates for redeployment. Aircraft with very high utilization may need additional capacity behind them.

Incident rate per hundred flight hours. The base rate for the operation, against which trends can be evaluated. A rising incident rate signals an emerging operational issue before it becomes a major event.

Time-to-record-closeout. How long after a flight the operational record is finalized. Programs with long closeout times accumulate operational debt that surfaces during audits.

Programs that track these metrics consistently usually identify issues months earlier than programs that wait for issues to surface as audit findings or incidents.

Common Mistakes in Utility Drone Program Management

Several mistakes show up across utility drone programs.

Treating the program as a tool rather than a function. Drone work is a continuing operational function, not a one-time technology adoption. Programs that resource the function appropriately (named owner, defined budget, dedicated tools) outperform programs that treat drones as something pilots do in addition to their main job.

Underweighting recordkeeping discipline. The recordkeeping is what holds up under audit, but it is the part of the program that most often gets neglected during peak operational demand. Programs that maintain the discipline year-round perform better in audits than programs that catch up at year-end.

Skipping the contractor governance question. Contracted services are a normal part of the operating model, but contractor access to the operational record needs explicit governance. Programs that let contractors run on their own systems and share records on completion tend to have inconsistent operational records and weaker audit trails than programs that bring contractors into the same platform.

Not tracking the KPIs. Programs that do not track inspection completion, defect closure, pilot currency, equipment utilization, incident rates, and time-to-closeout are flying blind on program health. The KPIs are diagnostic, not just reporting metrics, and ignoring them tends to compound operational issues.

FAQ

How does a utility decide between expanding the in-house drone team and contracting more work?

The decision usually rests on three factors: the recurring volume of work that can be predicted and planned, the security or access requirements that favor in-house staffing, and the cost structure comparison between fully-loaded in-house pilots and contracted services. Most utilities settle into a mix rather than choosing one or the other, with the in-house team handling the predictable recurring work and contractors handling the variable demand.

What size service territory justifies a dedicated drone program manager?

There is no formal threshold, but the role becomes necessary when the drone program crosses a few markers: more than five to ten in-house pilots, more than one operating territory, more than one inspection type running concurrently, or contractual or regulatory obligations that require single-point accountability. Below those markers, the program can usually be run as a part-time responsibility of an engineering or operations manager.

How do utilities handle drone operations in wildfire-prone service territories?

Wildfire mitigation programs have driven significant investment in drone-based inspection and recordkeeping over the last several years. The programs typically include pre-fire-season inspection cycles, post-event assessment protocols, and recordkeeping that supports state-level wildfire mitigation plan reporting. The drone program in fire-prone territories tends to operate under more intensive recordkeeping discipline than programs in other regions, and the software supporting it has to handle the heightened audit expectations.

How do utility drone programs typically integrate with asset management systems?

The integration is usually one-directional: the drone program's operational data feeds into the asset management system to update inspection records, defect identification, and condition assessments. Maximo, SAP, and other enterprise asset management platforms are the common targets. The integration is typically built via API rather than file exchange at the utility scale, because the volume of records makes file-based integration impractical.

Closing Thought

Running a utility drone inspection program well is largely about operational discipline rather than technology choice. The programs that succeed have clear ownership, a sensible in-house and contractor mix, consistent multi-site coordination, recordkeeping that satisfies all three audit audiences, and KPIs that signal program health before it deteriorates. The software supports the discipline; it does not replace it.

For utility drone programs ready to bring the operational record together inside one platform that satisfies the three audit audiences with a single source of truth, FlybyOps was built for regulated enterprise drone operators with the project structure, role-based access, equipment registry, and audit-grade recordkeeping that utility-scale programs depend on.