Fire department drone programs: getting started and staying compliant

A fire department drone program can change how a department sees an incident: a thermal view of a structure fire, an aerial search over water or rough terrain, a fast size-up of a hazardous materials scene without sending anyone in. The value is obvious once crews see it. What is less obvious to departments getting started is that a public safety drone program is a regulated aviation operation with real compliance obligations, not just a piece of gear the department bought. Standing one up well means deciding how the department will operate legally, building it on a recognized standard, and keeping records that survive scrutiny.

This guide covers the first decision every department faces about how it will fly legally, how a recognized public safety standard gives a program its backbone, how roles and incident access are managed as more people join, and the records that carry a program through an after-action review or a public records request. The goal is a program that holds up not only on a good call but on a bad one, when an outcome is questioned and someone asks exactly how the department was operating that day.

Deciding how the department will operate

The first real decision is the legal basis for flying. A public agency has two paths. It can operate under Part 107, the same small-drone rule that governs commercial operators, with pilots holding remote pilot certificates. Or it can apply for a public aircraft Certificate of Authorization, a COA, which suits some governmental operations and can allow flexibility Part 107 does not, at the cost of more administrative work and self-certification. Many departments start under Part 107 for its simplicity and move toward a COA as their mission set grows more demanding.

Whichever path a department chooses, the groundwork is the same. Pilots need to be trained and certificated, a written policy has to define who flies and under what conditions, and the program needs a plan for airspace, privacy, and data handling. Skipping straight to flying because the drone is exciting is how departments end up operating without clear authority or policy, which is a problem the day a flight draws a complaint or a lawyer's attention. The unglamorous setup work is what makes the capability defensible when it matters.

Building the program on a recognized standard

A department does not have to invent its program from scratch, and it should not try. There is a consensus standard written specifically for this, and building on it saves time and adds credibility. Following an established standard gives a young program a structure for training, deployment, maintenance, and recordkeeping that has already been vetted by the public safety community, rather than a set of habits invented on the fly. It also gives leadership something concrete to point to when a council, a chief, or the public asks how the program is run.

That standard is NFPA 2400, the standard for small unmanned aircraft systems used for public safety operations. It covers program development and deployment, the qualifications personnel should meet, maintenance, risk assessment, and integration with the incident command system, which is the language fire departments already run on. Aligning a program to it turns a scattered effort into something structured and auditable. A department that can say its drone program follows NFPA 2400 is speaking a language that regulators, insurers, and other agencies recognize, which matters far beyond the flight itself.

Roles, deployments, and who sees which incident

As a program grows past one or two pilots, managing roles and access becomes its own task. A fire department drone program can involve remote pilots, visual observers, incident commanders, and support personnel, and not everyone needs to see everything. Incident imagery and records can be sensitive, tied to injuries, investigations, or private property, and a department has to control who can open what. Loose access to every deployment's footage and reports is both a privacy exposure and a records-management problem when a public records request or an investigation arrives.

Scoping access to assignments keeps that under control. When the system can lock each operator to the incidents they were assigned, personnel see only the deployments they worked, and sensitive imagery does not circulate wider than it should. That protects the people in the footage, keeps the chain of custody clean, and makes it clear who accessed which incident. Combined with clear roles and a place to file each deployment, access control turns a growing program into one a department can still account for as its call volume climbs.

The records that carry a program through review

Public safety flying invites scrutiny that commercial work often does not. A deployment over a fire, a search, or a crime scene can end up in an after-action review, a public records request, or a courtroom, and the department has to be able to show how it operated. That means each deployment's records, the authorization it flew under, the crew involved, the aircraft used, and any incident during the flight, have to be captured and retrievable. A program that cannot reconstruct a specific flight months later is exposed exactly when accountability is demanded.

Keeping those records together, filed by incident, is what makes a program defensible over the long run. When an investigation or a records request comes in, the department pulls the deployment and everything attached to it rather than piecing the story together from memory and scattered phones. That same record supports the after-action review that makes the program better, showing what was flown, by whom, and how it went. For a public agency answerable to its community, the record is not paperwork but the account it owes when someone asks what happened.

Common mistakes in a fire department drone program

Flying before settling the legal basis. A department that starts flying without deciding between Part 107 and a public COA is operating on unclear authority. Choose the path, certificate the pilots, and put a written policy in place before the program responds to a real call.

Building the program without a standard. Inventing procedures from scratch leaves gaps and gives leadership nothing to point to. Aligning to NFPA 2400 provides a vetted structure for training, deployment, maintenance, and records that the public safety community already recognizes.

Treating incident footage as freely shareable. Deployment imagery can involve injuries, investigations, and private property. Letting everyone access every incident creates privacy and chain-of-custody problems. Scoping personnel to the incidents they worked keeps sensitive footage contained.

Neglecting pilot currency and training records. Certificates lapse and skills fade, and a program that does not track them can put an uncurrent pilot on a live incident. Keeping currency and training visible protects both the crew and the department's standing.

Failing to keep retrievable deployment records. When an after-action review or records request arrives, a program that cannot reconstruct a specific flight is exposed. Capturing each deployment's authorization, crew, aircraft, and incidents, filed and retrievable, is what carries the program through review.

FAQ

Does a fire department need Part 107 to fly drones?

It needs a legal basis, and Part 107 is the common one, with pilots holding remote pilot certificates. A department can instead operate under a public aircraft Certificate of Authorization, which fits some governmental missions but requires more administrative work and self-certification.

What is NFPA 2400?

It is the consensus standard for small unmanned aircraft systems used in public safety operations. It covers program development, personnel qualifications, deployment, maintenance, risk assessment, and recordkeeping, giving fire departments a vetted framework to build and run a drone program on.

Who can be on a fire department drone crew?

Typically a certificated remote pilot supported by visual observers and, on scene, an incident commander and support personnel. Roles and required training should be defined in policy, and access to incident records should match each person's role on the deployment.

Why does a public safety drone program need strict records?

Because its flights can end up in after-action reviews, public records requests, and court. The department must show how it operated on a given call, so each deployment's authorization, crew, aircraft, and incidents need to be captured and retrievable later.

Closing thought

A fire department drone program is a real aviation operation, and it succeeds on the parts that never make the highlight reel: a clear legal basis, a recognized standard, disciplined access, and records that survive review. Get those right and the capability holds up on the worst call, not just the best one.

If you are launching a fire department drone program, FlybyOps was built for the operational record problem at the center of regulated drone work. Incident reporting with an anonymous submission option, role-based access control, a project and job hierarchy with map-based scoping, and an append-only audit log are all part of how the platform keeps each deployment's authorizations, crew, and incident record filed together for the after-action review.