Drone program policy for local agencies: flight logs and imagery

Reference article · 7 min read

Small unmanned aircraft have become ordinary equipment in local government. Police use them for searches, pursuit alternatives, and scene documentation. Fire departments use them for size-up and thermal imaging. Public works inspects bridges, roofs, culverts, and storm damage. Assessors, planners, and parks departments capture aerial imagery of parcels, construction progress, and drainage. The aircraft are cheap enough that a single division can buy one from a discretionary line, which is how programs end up flying for a year or more with no written policy, no retention schedule, and no ready answer when the first records request or council question arrives.

A defensible program is mostly paperwork, not hardware. The policy should be adopted at a level that survives staff turnover, ideally by the governing body or the chief executive rather than by one unit, and it should hold up whether the reader is a pilot, a records clerk, a requester, or opposing counsel. The structure below is what tends to survive scrutiny.

Name the authorized missions, and the prohibited ones

A policy that says drones may be used "for official purposes" tells no one anything. List mission types explicitly and require that every flight be recorded against one of them.

Enumerate approved missions. Search and rescue, crash and crime scene mapping, fire attack support, hazmat standoff, disaster damage assessment, infrastructure inspection, construction and property documentation, event overwatch. Say which require supervisory approval in advance.
State the prohibitions plainly. No flights based solely on protected activity such as assembly or worship, no flights based on race, ethnicity, or other protected characteristics, no weaponization, no personal use, no use of facial recognition on drone imagery unless separately authorized.
Address first amendment activity directly. If drones may be used over a demonstration for crowd safety or traffic management, say so, say who approves it, and say what happens to the imagery afterward.
Set a rule for incidental capture. Pilots will see things that were not the mission. Define whether incidental imagery may be retained, referred, or must be deleted.

Pilots, FAA duties, and program authority

Most local agencies operate under FAA Part 107 with certificated remote pilots. Public agencies also have the option of operating as public aircraft operations under a Certificate of Waiver or Authorization, which carries different responsibilities. Federal rules on remote identification, airspace authorization, night operations, flight over people, and beyond visual line of sight change over time, so treat any summary, including this one, as a starting point and confirm current requirements with the FAA and your counsel.

Local policy should add what the FAA does not supply: minimum flight hours before solo operation, recurrent training intervals, a documented proficiency check, fitness for duty and fatigue rules, a visual observer requirement for specified missions, and a named program manager accountable for certificates, registrations, maintenance logs, and battery condition.

Treat flight logs as records from the first flight

The flight log is the spine of the whole program. Capture it at the time of flight rather than reconstructing it later, and capture enough that an auditor can tell why each flight happened.

Date, start and end times, pilot and any visual observer
Aircraft identifier and registration
Mission type from the approved list, plus the incident, case, work order, or parcel number that authorized it
General location and airspace authorization used
Whether imagery was captured, whether it was retained, and where it was stored
Anomalies, incidents, and any deviation from policy

Flight logs are government records. They fall under your state's retention schedule and are generally subject to disclosure, sometimes with narrow exemptions for active investigations or security details. Design the log assuming it will be released. An annual summary drawn from the log, showing flight counts by mission type, is also the simplest way to satisfy public reporting expectations.

Retention and handling of imagery

Imagery deserves a separate policy section because the right answer differs by purpose.

Classify by category. Non-evidentiary operational imagery, evidentiary imagery tied to a case, and asset or inspection data such as orthomosaics and inspection photos each have different useful lives.
Set a short default for non-evidentiary imagery and make deletion automatic. Retention that depends on someone remembering to delete does not happen.
Let evidentiary imagery follow case rules, not drone rules, and route it into the evidence system with normal chain of custody.
Plan for redaction. Faces, plates, windows, and private yards drive the cost of every future records request. Know which tool your staff will use before the first request.
Log access. Who viewed, exported, or shared imagery should be auditable, and sharing outside the agency should require documented approval.
Remember derived products. Photogrammetry outputs and GIS layers inherit the sensitivity of their source imagery and need their own retention entry.

Surveillance technology ordinances, notice, and procurement limits

Where a jurisdiction has adopted a surveillance technology ordinance, drones are usually covered, because coverage typically turns on whether the equipment can collect identifiable information about people, not on whether the agency intends to. A roof inspection camera can still record a neighbor's yard. The practical approach is to assume coverage: draft a use policy, take it to the governing body before acquisition, and commit to the periodic report the ordinance requires. Even without an ordinance, publishing the policy and an annual flight summary costs little and forestalls a great deal.

Several states have enacted their own limits, including warrant requirements for certain law enforcement uses and restrictions on purchasing aircraft from specified foreign manufacturers. Federal funding conditions may add further restrictions. These rules have been changing, so verify the current state of the law with counsel before you buy and before you fly.

Mutual aid and outside requests

Mutual aid is where policies quietly fail. Decide in writing, in advance:

Whose policy governs the flight. The common approach is that the operating agency's policy and its pilot's judgment govern the aircraft, while the requesting agency directs the mission objective.
Who is the records custodian for imagery captured for another jurisdiction, and whether a copy is retained by the operating agency at all.
That the flight appears in the operating agency's log with the requesting agency and their incident number recorded.
Limits on mission creep: a request for damage assessment does not become surveillance because the receiving agency later wants it to.
Cost recovery, insurance, and liability terms, ideally in an addendum to an existing mutual aid agreement rather than an informal understanding.

How to start, and what to ask vendors

Inventory what you already own and who has been flying it.
Draft the policy before the next purchase, using your state's model policies and your counsel's review.
Add flight logs and each imagery category to your retention schedule with the state archives or records authority.
Adopt the policy publicly, then publish it.
Audit after the first few months: pull the log, confirm every flight has an authorizing reference, and confirm deletion actually ran.

When evaluating software for flight logging, evidence storage, or imagery processing, ask vendors where data is stored and under whose control, whether retention periods are configurable per category and enforced automatically, whether deletion is verifiable and logged, what the access audit trail captures, what redaction capability exists, which subprocessors touch the data, and what a complete export in open formats looks like at contract end. Require those answers as contract terms rather than as statements in a proposal, and require notice before any change in storage location or subprocessor.

HQT works with state and local agencies on the systems side of programs like these, including records retention design, data integration, and public safety software.

Frequently asked questions

Are city or county drone flight logs public records?

In most states, flight logs created by a public agency are government records and are subject to both a retention schedule and public disclosure, though narrow exemptions may apply to active investigations or security sensitive details. The practical approach is to design the log assuming it will be released, and to keep investigative detail in the case file rather than in the log itself. Confirm the specific exemptions and retention periods with your state records authority and your counsel.

How long should an agency keep drone video and photos?

There is no single answer, because retention should follow the purpose of the imagery rather than the aircraft that captured it. Non-evidentiary operational video is commonly given a short default retention with automatic deletion, evidentiary imagery follows the retention rules for the associated case, and inspection or mapping products follow the asset records schedule. Add each category to your approved retention schedule rather than leaving deletion to staff discretion.

Do public agencies need FAA Part 107 certification to fly drones?

Most state and local agencies operate under Part 107 with certificated remote pilots, which is the simplest path for routine missions. Public agencies also have the option of operating as public aircraft operations under a Certificate of Waiver or Authorization, which shifts certain responsibilities to the agency. Federal requirements for remote identification, airspace authorization, and operations such as beyond visual line of sight change over time, so verify current rules with the FAA before relying on any summary.

Does a drone count as covered surveillance technology under a local ordinance?

Under most surveillance technology ordinances, coverage depends on whether the equipment is capable of collecting information that can identify people, not on the agency's intended use. That definition usually captures camera equipped drones even when they are used for bridge inspection or property assessment. The safer course is to assume the drone is covered, bring a written use policy to the governing body before acquisition, and plan for whatever periodic reporting the ordinance requires.

Whose policy applies when a drone is deployed for mutual aid?

This should be settled in writing before the first request, not during an incident. A common arrangement is that the operating agency's policy and its remote pilot govern how the aircraft is flown, while the requesting agency defines the mission objective within the limits of that policy. The agreement should also name the records custodian for any imagery, state whether the operating agency retains a copy, and require the flight to appear in the operating agency's log with the requesting agency's incident number.