Drone safety checklist: site checks that go beyond preflight

A drone safety checklist and a preflight checklist get treated as the same document, and the overlap is where gaps hide. The preflight checklist confirms the aircraft is ready to fly. A drone safety checklist covers everything around the flight that can injure a person or damage property: the site, the people on it and beside it, the crew running the operation, and the conditions that shift while the aircraft is airborne. The two lists share a few items and part ways on most.

The remote pilot in command carries this responsibility, and it does not begin at takeoff or end at landing. It runs from the site walk before anyone opens a case to the last person clearing the launch zone after the aircraft is down. This article covers what belongs on a drone safety checklist beyond the aircraft preflight, where the regulatory floor sits, and which safety checks need to leave a record that survives the flight.

Where the safety checklist starts and the preflight ends

The aircraft preflight answers one question: whether this airframe is airworthy for this flight right now. A drone safety checklist answers a wider one: whether this operation is safe to run at this site, with these people, under these conditions. The preflight is a subset of the safety checklist, not a synonym for it.

The practical split is easy to draw. Propeller condition, battery charge, control link, and available power belong to the preflight. The exclusion zone around the launch point, the plan for keeping bystanders out of it, the crew's roles when something goes wrong, and the trigger for calling a flight off all belong to the safety checklist. Programs that fold both into one undifferentiated list tend to run the airframe checks carefully and treat the site and crew checks as a formality, which inverts the actual risk. Many drone incidents that hurt someone trace to the operation around the aircraft rather than the aircraft itself.

Site, perimeter, and bystander checks

Site checks are the core of a safety checklist because every location carries its own hazards. The walk-through covers launch and recovery zones, overhead wires, structures and vegetation in the flight path, surface conditions underfoot, and the movement of people and vehicles through the area during the operation. A site that was clear during planning can hold a delivery truck, a dog walker, or a maintenance crew on the day.

The perimeter is where site knowledge turns into action. Establishing an exclusion zone sized to the operation, marking it, and assigning someone to keep it clear is a safety control, not a suggestion. Programs flying near people should define in advance who watches the crowd line, how the aircraft behaves if someone crosses it, and at what point the operation pauses. A checklist that names the exclusion distance and the person responsible for holding it turns an abstract intention into a task with an owner.

Crew, roles, and the accountability line

People checks carry the same weight as equipment checks, and 14 CFR 107.19 sets the frame: the remote pilot in command is directly responsible for and the final authority over the operation, and must ensure the aircraft poses no undue hazard to people, other aircraft, or property in the event of a loss of control. That responsibility is personal to the remote PIC and does not transfer with delegated tasks.

The crew checks confirm the responsibility is backed by structure. Every person on site should know their role before the aircraft leaves the ground: who is the remote PIC, who manipulates the controls if that is a different person, who serves as visual observer, and who manages the perimeter. The briefing should establish communication, the signal to abort, and the emergency and contingency procedures for the specific site. A crew that has confirmed roles and a shared abort signal responds faster than one discovering the plan mid-incident.

Conditions that change while the aircraft is up

A safety checklist run once at setup goes stale the moment conditions move, and conditions move constantly. Weather is the obvious one: wind and gusts build, light drops, precipitation arrives ahead of forecast. Each should be measured against the program's written minimums rather than the crew's tolerance on the day, and the minimums should sit on the checklist so the decision is made against a number rather than a mood.

Airspace and ground conditions drift too. A temporary flight restriction can publish after the crew arrives, an authorization can lapse against a longer-than-planned operation, and the surface picture changes as the public moves through. In-flight monitoring belongs on the checklist as an ongoing task, not a one-time confirmation: someone watching the airspace, someone watching the perimeter, and a shared understanding of what conditions end the flight early. The go decision at setup is provisional, and a safety checklist that treats it as final removes the crew's permission to stop.

Post-flight and incident-ready checks

The checklist does not close at touchdown. Post-flight checks cover securing the aircraft and batteries, noting any anomalies observed in flight, confirming the exclusion zone is cleared safely, and recording the outcome of the operation. Batteries that behaved oddly, a control link that stuttered, or a near-miss with a bird or a person all belong in a note while the detail is fresh, because these are the leading indicators a program uses to prevent the next event.

The record matters most when the flight did not go cleanly. If an aircraft came down hard, a person entered the zone, or property was touched, the useful evidence is captured in the minutes after, not reconstructed weeks later from memory. A safety checklist that ends with a recorded outcome, attributed and timestamped, gives the program something to review and gives any later investigation or claim something to work from. Safety checks that leave no trace give a program nothing to learn from and give an investigator no reason to believe they happened.

Common mistakes in drone safety planning

Treating the aircraft preflight as the whole safety check. The airframe passing its checks says nothing about whether the site is controlled or the crew is briefed. A safety checklist has to cover the operation around the aircraft, which is where most injuries originate.

Running one safety checklist for every site. A rooftop, an open field, and a job beside a public sidewalk carry different hazards and demand different exclusion zones and crew positions. A generic list that never changes cannot flex to the site it is used on.

Setting an exclusion zone with no one assigned to hold it. A marked perimeter that nobody watches drifts inward as the operation runs and people wander. The control only works when a named person owns it and has the authority to pause the flight.

Locking in the go decision at setup. Conditions change after the crew arrives, and a checklist run once removes the crew's license to stop when wind builds or a restriction publishes. The go decision should be treated as provisional and revisited in flight.

Closing the operation without capturing what happened. Anomalies and near-misses noted at touchdown feed the program's risk picture, while the same details reconstructed weeks later are guesswork. A safety checklist that ends without a recorded outcome discards its most useful output.

FAQ

Is a drone safety checklist required under Part 107?

Part 107 does not mandate a written safety checklist. It requires the preflight assessment and briefing under 107.49 and places final authority with the remote pilot in command under 107.19. Programs build safety checklists anyway, because a written control is the only reliable way to run and prove one.

What is the difference between a preflight checklist and a safety checklist?

The preflight checklist confirms the aircraft is airworthy for the flight: airframe, batteries, control link, and power. The safety checklist covers the operation around it: site hazards, the exclusion zone, crew roles, changing conditions, and the abort plan. The preflight is one part of the larger safety check.

Who is responsible for drone operational safety?

The remote pilot in command. Under 14 CFR 107.19, the remote PIC is directly responsible for and the final authority over the operation. Crew members can be assigned specific tasks, but accountability for the safe conduct of the flight stays with the remote PIC.

How often should a drone safety checklist be updated?

Whenever the operation changes and on a regular review cycle regardless. A new site type, a new aircraft, a payload change, or a lesson from a near-miss should each prompt a revision. Many programs also review their safety checklists on a fixed schedule to catch drift.

Closing thought

A drone safety checklist covers the ground the aircraft preflight leaves out, and that ground is where operations hurt people. The site, the perimeter, the crew, and the shifting conditions each carry hazards that a propeller check will never surface. A checklist that names those hazards, assigns an owner to each control, and stays open to a mid-operation stop protects the people on site and the program behind them.

If you are building repeatable safety practices across a commercial drone operation, FlybyOps was built for the operational record problem at the center of regulated drone work. Role-based access control, incident reporting with an anonymous submission option, a risk register that tracks identified hazards and their mitigations, and an append-only audit log are all part of how the platform gives operational safety a record that lasts.