Drone preflight checklist: what to check and what to record

Every commercial drone program has a preflight checklist somewhere. A laminated card in the equipment case, a page in the operations manual, a sequence the senior pilot runs from memory. The checks themselves are usually reasonable. The failure points sit on either side of them: checklists written once that no longer match the operations the program flies, and checks that finish without leaving any record they happened.

The second problem costs more than most programs expect. A preflight check that produced no record cannot support an insurance claim, an incident investigation, or a regulator's question about how a flight was authorized. This article covers what a working drone preflight checklist includes, where Part 107 sets the floor, and which items need to graduate from checkbox to record.

What Part 107 requires before every flight

The regulatory floor is 14 CFR 107.49, which covers preflight familiarization, inspection, and actions for aircraft operation. Before each flight, the remote pilot in command must assess the operating environment, including local weather conditions, local airspace and any flight restrictions, the location of people and property on the surface, and other ground hazards. The remote PIC must also brief everyone directly participating in the operation on operating conditions, emergency procedures, contingency procedures, roles and responsibilities, and potential hazards. On the equipment side, the rule requires working control links, enough available power for the intended operational time, and confirmation that anything attached or carried is secure and does not adversely affect flight characteristics or controllability. Operations over people add one more item: verifying the aircraft meets the requirements of its operational category.

The rule stops short of requiring a form: it mandates the assessment, the briefing, and the equipment verification, and says nothing about writing any of it down. The demonstration burden runs the other way. When an inspector, an insurer, or an attorney asks whether the preflight assessment happened before a specific flight, the only useful answer is a record.

Aircraft and battery checks

The equipment pass starts with the airframe: propellers free of chips and stress cracks, motors turning freely, gimbal and camera mounts tight, sensors clean, no damage picked up in transport. Batteries get their own line items because they fail differently. Charge level gets checked against planned flight time plus reserve, physical condition against swelling or connector damage, and cycle history wherever the program tracks it. Return-to-home altitude and failsafe behavior should be set for the site being flown, not the site flown last week.

These checks work better against the specific aircraft's history than against a generic list. An airframe approaching a maintenance interval, a battery with a recorded anomaly two jobs ago, a payload swapped since the last flight: each changes what the preflight should look at. Programs that keep an equipment registry with per-airframe hours and open issues put that context in front of the pilot at the moment it matters.

Site, weather, and airspace checks

Site checks are where generic checklists fail hardest, because every location carries its own hazards. The walk-through covers launch and recovery zones, overhead wires, structures and vegetation along the planned flight path, and where people and vehicles will be while the aircraft is up. Weather gets measured against the program's written minimums for wind, gusts, precipitation, and temperature, not the pilot's comfort level on the day.

Airspace and authorization deserve a same-day confirmation even when they were handled during planning. The class of airspace, the status of any required authorization, any temporary flight restrictions issued after the job was scheduled, and any NOTAMs relevant to the operating area all belong on the list. Restrictions change on shorter notice than job schedules do, and a flight plan approved two weeks ago says nothing about a TFR published this morning.

Crew, currency, and authorization checks

People checks carry the same weight as equipment checks. The remote pilot in command's certificate should be current, including the recurrent training that keeps it valid. Visual observers and ground staff should be briefed per 107.49 on roles, contingencies, and hazards, and the briefing should establish who does what when something goes wrong rather than simply confirm a conversation occurred.

The authorization check is the one most checklists skip: confirming the flight belongs to an approved job and that the people on site are the people assigned to it. On a three-pilot team the answer is obvious. At enterprise scale, with contractors, multiple crews, and several clients running through one platform, it stops being obvious, and the failure mode is a pilot flying a site they were never assigned to under a job scope they have never read. Access scoping closes that gap structurally. When pilots only see the jobs they are assigned to, an unassigned pilot cannot pull up the wrong mission in the first place, and the preflight confirmation becomes a check the system backs up rather than a manual cross-reference.

What to record, and why

The recording half of the checklist separates a program that ran preflight checks from a program that can prove it. Not every item needs to become a record. The ones that do share a property: someone may later need the answer.

A defensible preflight record typically captures who performed the check and when, which aircraft and batteries flew by identifier, the weather observed against minimums, the authorization the flight operated under, any anomalies found and how they were handled, and the go or no-go decision with the reasoning behind it. Timestamps and attribution matter as much as content. A record that cannot show when it was created or by whom invites the question of whether it was written after the fact.

Where the records live matters too. Paper checklists in a truck and photos on a pilot's phone are records in theory and unavailable in practice. Preflight records that land in the same system as the flight log, the equipment history, and the job file can be assembled when an investigator or insurer asks, and a tamper-evident trail behind them settles the after-the-fact question before anyone raises it.

Common mistakes in drone preflight checks

Running the same checklist for every operation. A list written for daytime mapping over open ground does not cover a night flight, a vertical structure inspection, or an operation near people. The 107.49 assessment is specific to each flight's environment, and the checklist should flex the same way.

Checking the aircraft and skipping the paperwork. Pilot currency, authorization status, insurance validity, and job assignment are preflight items with the same standing as propellers and batteries. The difference tends to surface at claim time, over a lapsed detail nobody looked at that morning.

Completing checks without creating a record. The work was done and nothing proves it. Months later, during an investigation or a claim, the absence of a record reads the same as the absence of a check.

Producing records that look identical every flight. All-green checklists with no anomalies, no notes, and no conditional decisions across hundreds of flights tend to signal box-ticking rather than perfection. The anomalies and the reasoning are where a record earns its keep.

Keeping preflight records disconnected from everything else. A checklist that cannot be tied to the aircraft's maintenance history, the pilot's currency, or the job it supported answers one narrow question. Records connected to the rest of the operational file answer the questions that follow it.

FAQ

Does Part 107 require a written preflight checklist?

No. Section 107.49 requires the preflight assessment, crew briefing, and equipment verification, but it does not mandate a written form or record retention. Programs document preflight checks anyway, because a record is the only practical way to demonstrate later that the required actions happened.

What should a drone preflight checklist include?

Aircraft and battery condition, control link function, available power for the planned flight, airspace and authorization status, weather against program minimums, site hazards, crew briefing and role assignments, payload security, and the go or no-go decision. What gets recorded should be defined alongside what gets checked.

Who is responsible for preflight checks under Part 107?

The remote pilot in command. Tasks can be delegated to crew members, but 107.49 places the obligation on the remote PIC, and accountability for the assessment, briefing, and equipment verification does not transfer with the task.

How long should preflight records be kept?

Part 107 sets no retention period for preflight records, so programs typically align them with their flight record retention policy and hold them for several years. Records tied to an incident should be kept longer, often for the life of any claim or investigation plus a margin.

Closing thought

A drone preflight checklist earns its place twice. On the ground, it catches the swollen battery, the fresh TFR, or the missing authorization before the motors spin. Months later, the record it produced answers a question nobody anticipated on flight day. Programs that treat the checklist as both a safety tool and a record-producing step get both benefits from the same few minutes of work.

If you are formalizing preflight checks across a commercial drone operation, FlybyOps was built for the operational record problem at the center of regulated drone work. An equipment registry with per-airframe hour rollups, a pilot registry that tracks certification and currency, a document vault that holds authorizations and insurance with expiration tracking, and an append-only audit log are all part of how the platform supports preflight discipline that holds up after the flight.