Published 2026-04-14 · 9 min read

Public Safety Drone Program Startup Checklist

Practical steps for standing up a drone program at a small police department, fire service, or volunteer SAR team. Not a sales pitch — a checklist written by a Part 107 pilot who has helped small agencies avoid the obvious mistakes.

The pattern most new public safety drone programs follow: buy an aircraft, assign a pilot, fly a few operations, then spend the next eighteen months retroactively solving policy, distribution, retention, and procurement problems that should have been solved first. This post is a pre-flight checklist — the things to settle before the first operational flight.

Before you buy hardware

1. Decide who owns the program

Every program needs a single accountable owner. Not "the UAS committee" — one person with authority to say yes and no. Usually a lieutenant, captain, or sergeant with operational credibility and the political capital to push through the first procurement cycle.

2. Define the mission

Write down, in two sentences, what the program is for. "Tactical overwatch for high-risk warrants and multi-agency mutual-aid coordination." "Wildland fire initial attack and structure fire size-up." "Lost-subject location and multi-team search coordination."

This sentence drives every downstream decision. An agency that wants tactical overwatch needs thermal imaging and rapid deployment; an agency that wants fire-ground situational awareness needs thermal and long endurance; an agency that wants search capability needs thermal and large-area mapping. Same sentence structure, very different aircraft choices.

3. Budget reality check

A real program budget for year one, at a small agency:

Total year-one realistic: $15,000–$40,000 for a small program. Grant-eligible (AFG, DHS, state UAS, regional foundation grants) in most cases.

Certification and pilots

4. FAA Part 107

Every operational pilot needs Part 107 certification. Study time is realistically 30–60 hours; test fee is about $175. Plan for three certified pilots minimum — programs with one pilot fail the moment that pilot is unavailable.

5. COA vs Part 107 waivers

Public safety agencies can operate under a blanket Certificate of Authorization (COA) or under Part 107 with specific waivers (night, BVLOS, over people). For most small agencies, Part 107 + a daylight waiver and night waiver covers 95% of real-world missions. Start there and expand as needed.

6. Recurrent training

The FAA requires Part 107 recurrent every 24 months. Your program should drill more often than that — ideally monthly flight time and quarterly scenario drills. Volunteer SAR teams typically train more than career agencies because they have to; that's a model worth copying.

Aircraft selection

7. Stick with the enterprise line

Unless you have a specific reason not to, DJI enterprise aircraft (Matrice 30T, 350 RTK, Mavic 3 Enterprise/Thermal) are the defaults. They integrate with the software ecosystem your peers run, have spare parts availability, and have training material everyone else is using.

8. Thermal for public safety

If the mission includes fire-ground, search, or night ops — get thermal. The M30T and Mavic 3T cover 95% of public safety thermal use cases. The marginal cost is worth it.

9. Don't buy two of different aircraft families

Pilot training, batteries, and software all break when you mix aircraft families. Pick one family and standardize.

Software stack

10. You need two platforms

Most public safety programs need:

Trying to force one platform to do both always compromises one or the other. Plan for two.

11. Pick the live video tier that fits IT capacity

Self-hosted if you have IT capacity. Managed if you do not. Here's the full decision framework. For most volunteer teams and small departments, Managed is the right answer even though it costs more monthly — it removes the operational burden.

Policy (write before the first flight)

12. Operational SOPs

Written SOPs for pre-flight checks, authorized missions, go/no-go criteria, LOS and BVLOS operations, night operations, weather limits, and chain of command during operations. IACP and NFPA have model policy templates worth starting from.

13. Privacy policy

Define what the drone can and cannot be used for, who authorizes missions, what recordings are retained, and who has access. This is the policy that gets litigated — get it reviewed before the first flight, not after.

14. Records retention

Figure out where recorded drone video lives, how long it is retained, and how public-records requests are handled. Integrate with existing agency records management.

15. Multi-agency sharing agreements

If you will share video with mutual-aid partners, write the sharing agreement now. Include revocation, retention on the receiving side, and post-incident disposition.

The first 90 days

16. Do non-operational flights first

Training flights, public-outreach demonstrations, and low-risk authorized missions. Build pilot hours and work out the kinks before the first high-consequence call.

17. Run a multi-viewer drill

Simulate an operation where the pilot is in the field, the IC is in the command vehicle, and a mutual-aid partner is in a neighboring jurisdiction. Practice the full video distribution workflow under realistic network conditions. This is where most programs discover gaps before they matter.

18. After-action every flight

Even training flights. Record the flight, review it with the pilot team, document lessons learned. This builds institutional knowledge that survives personnel turnover.

19. Build relationships with neighbors

Your drone program will graduate to multi-agency operations eventually. Start the relationships now — joint training, shared SOPs, mutual-aid pre-agreements. Public safety drone work is a small community; know your neighbors.

One thing programs routinely get wrong: treating the drone as "just another piece of equipment." It is operational technology that directly supports life-safety decisions. Plan, budget, and operate it with that rigor.

Vertical-specific reading

Starting a program and want to talk through the video-distribution layer with an actual pilot? No sales qualification.

Talk to Barnard HQ