Drone Preflight Checklist: What to Check Before Every Part 107 Flight (2026)

Last Updated: October 13, 2026

A drone preflight checklist helps you confirm that your aircraft, flight location, and crew are ready before takeoff. For U.S. Part 107 pilots, it should cover airspace, weather, people and obstacles, aircraft condition, batteries, control links, Remote ID, and the final go/no-go decision.

A charged battery isn’t a flight plan. And a green indicator in your flight app doesn’t prove the operation is legal. Good preflight preparation connects the equipment checks to the place you’re flying—and gives you a clear reason to stop when something doesn’t add up.

Key Takeaways
– Check the drone’s condition for safe operation before every flight, not just at the start of the day.
– Separate FAA duties from aircraft-manual instructions and your own operating procedures.
– Verify the applicable Remote ID compliance path; don’t launch with an unresolved required-system fault.
– Recheck relevant items after battery swaps, configuration changes, or changing site conditions.
– Treat HOLD and NO-GO as useful decisions, not failures to finish the job.

TL;DR: Plan the mission, assess the site, inspect the powered-off aircraft, verify systems after startup, brief the crew, and make the launch decision. Keep a short checklist handy, but adapt it to the aircraft and operation. An unresolved safety or compliance issue means you aren’t ready to fly.

This guide covers ordinary U.S. Part 107 operations in 2026. It supplements your aircraft manual and operating procedures; applicable waivers, authorizations, and specialized operations may require additional checks.

What should a drone preflight checklist cover?

A useful drone preflight checklist follows the order you actually prepare to fly: plan the mission, assess the site, inspect the aircraft, verify powered systems, brief participants, and decide whether to launch. It should cover the operation as well as the hardware, with extra items for your aircraft and mission.

Start with a repeatable core, then add what the job needs. A roof-inspection flight may need special attention to obstacles and people below. A mapping mission also needs its automated route and capture settings checked. Neither makes batteries, control links, or weather less important.

The remote pilot in command, or PIC, has final responsibility for the operation. Someone else can help inspect equipment, but the PIC still needs to be satisfied that the aircraft and flight are ready. That’s the responsibility established by Part 107—not a responsibility transferred to the app. 1

Which preflight checks does Part 107 actually require?

Part 107 requires a safe-condition check before each flight and specific preparation for the operating environment, participants, control links, power, and payload. It doesn’t prescribe one universal written checklist. Your checklist is a practical way to perform those duties consistently, alongside aircraft-specific instructions and any requirements that apply to your operation.

Two provisions do much of the work. Section 107.15 requires the PIC to check that the system is in a condition for safe operation before each flight. Section 107.49 requires assessment of weather, airspace and restrictions, people and property, and ground hazards. It also covers participant briefings, functioning control links, sufficient power, secure loads, and applicable aircraft eligibility for operations over people. 1

Don’t confuse those duties with somebody else’s preferred setup:

What should you check before leaving for the flight site?

Before leaving, confirm that the mission is feasible, your pilot qualifications and aircraft documents are in order, and you have the equipment to complete the job. Review airspace, restrictions, weather, permissions, and contingencies early. Resolve maintenance or software issues before travel rather than discovering them beside the launch pad.

Check your remote pilot certificate and aeronautical-knowledge recency. Part 107 requires a qualifying test or training within the previous 24 calendar months to exercise PIC privileges. The certificate itself doesn’t simply expire at that interval; see our Part 107 renewal guide for the training process. 1

Confirm aircraft registration and any required authorizations. All aircraft operated under Part 107 need registration, including drones weighing less than 250 grams. Keep relevant documents accessible. 1

Then pack for the actual mission: healthy batteries, controller and display, cables, storage media, appropriate spares, and any required payload or lighting. Check that authorization conditions match the planned location, time, and altitude.

Avoid untested last-minute firmware changes. Follow manufacturer instructions, but give yourself time to validate a changed setup before relying on it for a client flight.

How do you check airspace, weather, and the launch area?

At the site, reassess the conditions you will actually fly in—not just the forecast or map you checked earlier. Confirm the applicable airspace authorization and restrictions, evaluate weather at the control station, and inspect the flight area for people, vehicles, obstacles, and suitable landing options before you prepare to launch.

Under §107.41, prior ATC authorization is required in Class B, C, and D airspace, and within airport-designated Class E surface areas. Not every Class E location has that requirement. Check current restrictions and relevant notices, including temporary flight restrictions. A geofence unlock isn’t FAA authorization. 1

For standard Part 107 operations, §107.51 sets minimum flight visibility of 3 statute miles from the control station, plus cloud clearance of 500 feet below and 2,000 feet horizontally. Meeting those numbers doesn’t settle the wind, temperature, precipitation, or battery-performance question. Check your aircraft limits and the actual mission conditions too. 1

Walk the launch and landing area. Look for wires, trees, moving traffic, changing terrain, animals, and people who could enter the flight path. Plan to maintain visual line of sight and yield to other aircraft. Identify an alternate landing area you can use without creating another hazard.

Our sectional-chart guide and Part 107 weather guide explain the airspace and weather checks in more detail.

How do you inspect the drone, propellers, and batteries?

Inspect the aircraft with power off, following the manufacturer’s sequence and precautions. Look for damage, loose components, improperly installed propellers, insecure batteries, and unsecured payloads. Confirm that the available energy suits the planned flight and return. A component that looks questionable deserves investigation before launch, not a hopeful test in the air.

Work methodically around the drone. Inspect arms, body, landing gear, propellers, mounts, and relevant fasteners. Check for cracks, chips, deformation, contamination, or damage that could affect operation. Don’t handle propellers while motors are energized.

Inspect batteries for swelling, damage, leakage, or abnormal condition. Verify secure installation and the model’s battery-status information. Include the controller and any display device in the power check. The FAA requires enough available power for the intended operation; it doesn’t give every drone the same starting percentage. 2

Secure the payload and confirm it won’t adversely affect flight characteristics or controllability. Remove transport restraints as directed, inspect sensors and lenses, and verify recording capacity where the mission needs it. 2

Calibration isn’t automatically a before-every-flight task. Follow the aircraft’s instructions and investigate warnings; don’t use repeated calibration to disguise an unexplained fault.

What should you verify after powering on the drone?

After startup, verify the controller connection, aircraft status, navigation readiness, mission settings, and applicable Remote ID operation. Check the home point and failsafe behavior against the actual site. Resolve unexplained warnings before takeoff; a successful power-on or live camera feed alone doesn’t establish that the full system is ready to fly.

Use the model’s documented status checks. Confirm the working control link, readable telemetry, correct flight mode, and any required navigation or sensor readiness. There isn’t one FAA satellite-count minimum that establishes readiness for every aircraft.

Check return-to-home settings and lost-link behavior. The return route and altitude must suit obstacles and applicable operating limits. Don’t assume a default altitude, obstacle sensor, or automatic return function can solve every site problem.

For Remote ID, determine the lawful compliance path: a Standard Remote ID aircraft, an eligible broadcast-module setup, operation within a recognized FRIA under its conditions, or another applicable FAA authorization. A commercial worksite isn’t automatically a FRIA. 3

Verify required Remote ID functionality using the manufacturer’s procedure. Broadcast-module users have an explicit pre-takeoff functioning check under §89.115. Standard Remote ID equipment must function from takeoff to shutdown. If required broadcasting stops in flight, the person manipulating the controls must land as soon as practicable. 3

Example: Your airspace authorization is valid, but the required Remote ID system reports an unresolved fault. That authorization doesn’t cure the fault. Hold the launch, investigate, and only proceed once the operation meets the applicable requirements.

How do you brief the crew and make a go/no-go decision?

Before launch, make sure direct participants understand the flight plan, hazards, roles, communications, emergency procedures, and contingency procedures. The PIC makes the final decision. Launch only when required conditions are satisfied and unresolved problems are addressed; client pressure, a tight schedule, or a nearly finished checklist doesn’t make an unsafe flight acceptable.

A briefing can be short without being vague. Identify who controls the aircraft, who watches for traffic or people, what calls require immediate attention, and where you can land if the plan changes. A visual observer isn’t required for every standard Part 107 flight, but any participating observer needs a clear role. 1

Discuss lost-link behavior, navigation anomalies, low-power warnings, and unexpected aircraft activity using your aircraft-specific procedures. Don’t invent a universal emergency action for every model.

If appropriate for the aircraft and location, perform the manufacturer’s controlled initial flight checks in a clear area. A hover check is already flight—it doesn’t replace the inspection and legal checks required before takeoff.

What should you recheck between flights and after landing?

Treat each new flight as a new readiness decision. Recheck aircraft condition and relevant systems after battery swaps, payload or configuration changes, abnormal events, and material changes in weather or site conditions. After landing, inspect for new defects and follow the manufacturer’s shutdown, battery-care, and storage instructions before the next operation.

A fresh battery doesn’t mean everything else stayed ready. Verify battery condition and engagement, system status, home point where relevant, mission settings, and required Remote ID operation. Reassess people, obstacles, weather, and authorization conditions for the next flight.

Repeat relevant checks after a long pause, software change, hard landing, or crew change too. The obligation to check safe condition applies before each flight. 1

Post-flight, preserve mission data and record defects or corrective actions in your operating records where appropriate. Don’t charge, store, or reuse a questionable battery simply to keep the job moving. Logs help trace recurring issues, but the cited preflight rules don’t impose a universal written inspection-log format.

Can you copy this drone preflight checklist for your next flight?

Yes—use the template below as a starting point, then adapt it to your aircraft manual, mission, and operating procedures. Keep steps in the order you perform them. Mark an item not applicable only when you can explain why, and resolve safety or compliance issues before treating the aircraft as ready to launch.

Drone Launch Academy editorial template — version 1.0, October 13, 2026. This isn’t an FAA-approved form or a substitute for aircraft-specific procedures.

Mission: __ Aircraft/model: _ PIC:
Location/date/time: Crew: Authorization/operating limits: ___

Before travel
– [ ] Mission, pilot qualifications, registration, documents, and applicable permissions checked.
– [ ] Airspace, restrictions, authorization conditions, and weather reviewed.
– [ ] Aircraft configuration validated; batteries, equipment, and required spares packed.

At the site
– [ ] Actual weather and aircraft operating limits acceptable.
– [ ] Flight path, people, vehicles, obstacles, and visual-line-of-sight plan assessed.
– [ ] Launch, landing, and contingency landing areas suitable.
– [ ] Direct participants briefed on roles, hazards, communications, and contingencies.

Power off
– [ ] Airframe, propellers, mounts, and relevant components inspected.
– [ ] Healthy battery securely installed; sufficient aircraft/controller/display power available.
– [ ] Payload secure; transport restraints removed as directed; mission storage ready.

Power on and final decision
– [ ] Control link, status, telemetry, and navigation readiness verified per manual.
– [ ] Home point, flight mode, mission route, and failsafe settings suitable.
– [ ] Applicable Remote ID functionality verified; unresolved warnings addressed.
– [ ] Operating conditions still acceptable; launch area clear; PIC decision recorded if required.

Recheck and closeout
– [ ] Relevant checks repeated before the next flight and after material changes.
– [ ] Post-flight defects, data, battery care, and maintenance needs addressed.

Decision: GO / HOLD / NO-GO
Issue found, corrective action, and reason for any N/A: ______

For mapping, inspection, night flight, or specialized payloads, add the specific procedures and eligibility checks the operation needs. For example, night operations have training and anti-collision-lighting requirements under §107.29; ordinary navigation lights alone don’t establish compliance. 1

How can you build better judgment beyond the checklist?

A checklist is most useful when you understand why each item matters. Training helps you interpret airspace, weather, aircraft performance, and crew responsibilities rather than just tick boxes. Pair that knowledge with your aircraft manual and a repeatable inspection routine, then practice recognizing when the right decision is to wait or cancel.

Drone Launch Academy’s Part 107 prep course covers regulations, airspace, weather, flight performance, and crew resource management. Its founder and chief instructor, David Young, is identified in the course biography as an FAA-certified Advanced Ground Instructor and Remote Pilot. 5

What questions do pilots ask about drone preflight checks?

Pilots often need clarity on written checklists, aircraft-specific limits, battery swaps, Remote ID faults, and recordkeeping. The answers below distinguish the cited FAA operating duties from useful procedures you can customize. They apply to standard U.S. Part 107 operations; your aircraft manual, operating authorization, and organizational requirements may add further conditions.

Does Part 107 require a written preflight checklist?

The cited preflight rules require actions, not one universal written form. Section 107.15 requires a safe-condition check before each flight, and §107.49 specifies preparation duties. A written checklist helps you perform them consistently. Your company procedures, contract, waiver, or authorization may impose additional documentation requirements. 1

What battery percentage or satellite count is required before takeoff?

There isn’t a universal Part 107 battery percentage or satellite-count minimum for every aircraft. You need enough power for the intended operation and a system in safe operating condition. Follow the aircraft’s energy and navigation instructions, assess mission conditions, and investigate warnings rather than relying on somebody else’s generic number. 1

Do I need a separate checklist for each drone model?

Use a shared operational core, but tailor equipment and system checks to each model. Battery installation, propeller mounting, navigation indicators, calibration procedures, failsafe behavior, and Remote ID verification can differ. A model-specific supplement lets you keep the main workflow simple without assuming that one aircraft’s instructions apply to another.

Should I repeat preflight checks after changing a battery?

Yes. Before the next flight, check safe operating condition again and repeat the relevant readiness items. That includes battery health and secure engagement, system status, mission settings, home point where applicable, and required Remote ID operation. Also reassess weather, people, obstacles, and any authorization conditions that could have changed. 1

Can I fly if required Remote ID isn’t working?

Don’t launch under a compliance path that requires functioning Remote ID when that requirement isn’t met. Investigate the fault using manufacturer guidance. If required broadcasting stops during flight, land as soon as practicable. FRIA operations and specific FAA authorizations have separate conditions; they aren’t automatic exemptions for an ordinary worksite. 3

Should I log my preflight inspection?

Logging can help track defects, corrective actions, aircraft configuration, and flight decisions. The cited preflight provisions don’t require every operator to use a universal inspection-log form. Follow any applicable authorization, contract, maintenance, or organizational recordkeeping requirements, and use a format that makes unresolved issues easy to identify before another flight. 1

Where can you verify the FAA rules behind this checklist?

Use current FAA and eCFR sources to verify operating requirements, then consult the manual for the aircraft you actually fly. Revisit the checklist when regulations, equipment, software, or operating procedures change. A revision date helps identify the version; it doesn’t make an old checklist permanently reliable for a new mission.

References

• Current Part 107 operating rules
• Preflight duties in §107.49
• Remote ID operating requirements
• FAA Remote ID guidance
• Drone Launch Academy course and instructor biographies