Drone programs that support utility infrastructure inspection operate in a different documentation context than general commercial UAS work. A survey operator flying photogrammetry over a construction site needs a clean flight record and pilot log. A utility inspection program flying transmission corridors, substation perimeters, or distribution pole lines needs all of that plus documentation that connects each flight to a specific asset, supports the utility's own inspection recordkeeping, and can survive review by either an FAA auditor or the utility's internal compliance team.
This post covers how that documentation structure typically works and where the common gaps appear. The regulatory floor is Part 107, but the operational requirements imposed by utility clients often exceed that floor in specific ways that operators need to anticipate when setting up their record-keeping.
The Two-Track Documentation Requirement
Utility inspection operators work with two distinct documentation audiences simultaneously. The first is FAA compliance: Part 107 flight records, Remote ID documentation, airspace authorization records (LAANC for controlled airspace corridors, COA or waiver documentation for specific operating conditions), and equipment registration. These records exist to satisfy regulatory requirements for the UAS operation itself.
The second track is asset documentation: evidence that a specific structure was inspected on a specific date, with data sufficient for the utility to assess condition and plan maintenance. This is not an aviation record. It is an infrastructure management record. A utility line inspector who receives a drone inspection package wants to know which tower was flown, at what distance and angle, what imagery was captured, and what anomalies were flagged. The FAA record does not answer those questions.
The gap between these two tracks is where documentation programs tend to break down. Operators who focus on aviation recordkeeping sometimes produce flight records with no asset linkage. Operators who focus on the inspection deliverable sometimes produce thorough inspection reports with incomplete flight documentation. Both approaches create problems: the first fails when the utility asks for asset-specific records, the second fails during an FAA audit.
Flight Record Requirements for Part 107 Utility Work
The regulatory baseline for a Part 107 utility inspection flight is the same as any other commercial UAS operation. The flight record must be retrievable and must contain: the date, time, and location of the operation; the aircraft used (identified by FAA registration number); the remote pilot in command and their certificate number; and any waivers or authorizations that applied to the operation. There is no specific regulatory requirement to retain flight logs in machine-readable form, but the practical standard for an audit is that you can produce a record showing where the aircraft was and who flew it.
Utility corridors frequently cross controlled airspace, particularly transmission lines near airports. Every corridor segment flown under LAANC authorization needs a record that the authorization was obtained before the flight, including the authorization number, the ceiling granted, and the time window. A corridor segment flown under a Section 44807 exemption (for aircraft above Part 107 weight limits) requires the exemption documentation to be readily accessible. These are records that exist alongside the flight log, not within it, and they need to be associated with the correct flights in whatever system the operator uses for record-keeping.
Asset Linkage: What the Inspection Client Needs
The utility client documentation requirement typically involves connecting each flight segment to the specific structures it covered. A transmission line inspection program might number tower structures sequentially along a corridor. The inspection record for a given campaign needs to show which towers were included in each flight, confirmed by the GPS track. This means the GPS track from the flight needs to be reviewed against the asset register, and the connection between flight records and structure IDs needs to be explicit in the inspection package.
For substation inspections, the asset linkage is more granular. A substation inspection package typically documents each major piece of equipment, and the inspection record needs to identify which equipment was covered in which flight pass. The GPS track alone does not provide this, because a drone circling a transformer bay covers multiple equipment items in a single pass. The linkage between flight passes and equipment coverage usually requires a mission planning record that maps planned waypoints or coverage zones to the asset register, combined with a confirmation that the actual GPS track matched the plan within an acceptable tolerance.
Operators who build this linkage systematically at the flight planning stage have a much easier time producing the inspection package. Operators who try to reconstruct it after the fact from GPS tracks and rough notes typically spend hours on documentation that should have taken minutes.
Pilot Records and Certification Documentation
Utility inspection programs typically involve multiple pilots, often with different qualifications for different operational scenarios. The program-level documentation needs to maintain current records of each pilot's Part 107 remote pilot certificate, any additional training or qualification records the utility requires, and current medical status if the utility has added that requirement to their service agreement.
Each flight record needs to identify the specific pilot who served as remote pilot in command. This is both a regulatory requirement and an operational one: if an incident occurs, the investigation requires knowing who was flying. In programs with multiple pilots operating concurrently from a base camp during a long corridor campaign, the pilot-per-flight assignment is easy to lose unless it is recorded consistently at the start of each flight.
Certificate currency is an area where programs frequently have gaps. Part 107 requires recurrent knowledge testing every 24 calendar months. A utility program running for three years will have pilots whose certificates lapse and are renewed at different points. The program documentation needs to reflect current certificate status for every active pilot, and the responsible party needs to flag upcoming lapses before they occur rather than discovering them when a pilot's certificate shows as expired on the day of an operation.
Equipment Records in Utility Programs
Utility inspection programs often use the same aircraft repeatedly across a multi-year contract. Equipment records for these programs need to track not just current registration and insurance, but maintenance history, component replacements, and firmware updates at the airframe level. A utility client auditing the program two years into a contract may ask for the maintenance history of the aircraft used on a specific inspection campaign. If maintenance records are not organized at the airframe level with dates and cumulative hours, that question is difficult to answer.
Firmware updates on commercial DJI aircraft can affect flight behavior and compliance characteristics. The Remote ID broadcast behavior of a Matrice 300 RTK changed across firmware versions, and the specific version running at the time of a flight may be relevant to a Remote ID compliance question. Recording the firmware version as part of the aircraft configuration log at the start of a campaign, or at each update event, is a small step that closes a gap that would otherwise require reconstruction from DJI FlightHub records after the fact.
Building a Documentation Structure That Scales
The documentation requirements for a utility inspection program are more complex than for a single-operator survey business, but they are not inherently difficult to satisfy if the structure is set up correctly before operations begin. The common failure is starting with a documentation approach designed for simple Part 107 compliance and trying to add asset linkage and utility client requirements on top of it as the program grows. The two documentation tracks need to be designed together, because the flight record and the inspection record share core data points (date, location, aircraft, pilot) that should only be entered once.
We are not suggesting that every utility inspection operator needs a custom database. The goal is a consistent structure where each flight record automatically carries the fields needed for both the aviation compliance side and the utility client deliverable side. When that structure exists, producing an audit package or an inspection package becomes a reporting step rather than a reconstruction exercise.
The programs that have this working well tend to share one characteristic: they made the documentation structure explicit before the first flight of a new contract, including getting confirmation from the utility client on what format and fields they actually want for the inspection deliverable. Many documentation headaches in this sector trace back to an assumption about what the client needs that turns out to be wrong once the first package is delivered.