Drone Preflight Checklist
The checklist that catches problems on the ground, where they are an inconvenience, instead of in the air, where they are not.
Researched from published specifications and verified owner reviews · updated 2026
The short answer
A complete drone preflight checklist runs through firmware, physical inspection, battery health, GPS and compass status, and airspace authorization, in that order, and takes under five minutes once it becomes routine.
Most drone incidents that get blamed on a "malfunction" trace back to something a two-minute preflight check would have caught: a hairline-cracked prop, a firmware update that never finished installing, a compass that needed recalibrating after air travel, or airspace that needed authorization before launch. This is the routine in the order that catches the most problems for the least time spent, built for both recreational and Part 107 flying.
The night before or at home: 1 through 4
- Check and install firmware updates. Open the app with the aircraft and controller connected and let it check for updates before you leave the house, not at the field on cellular data. Firmware updates fix real bugs, including ones tied to GPS lock, Remote ID broadcast and obstacle sensing.
- Charge batteries to full and check pack age. Confirm packs read a true full charge, not a storage-level charge left over from between sessions, and check the cycle count in the app against what you know about the pack's age. A pack nearing 200 cycles needs closer attention to voltage sag during flight.
- Format the memory card. Format inside the aircraft's own app rather than on a computer, which clears fragmented file structures a computer format can leave behind and that occasionally cause a recording to fail mid-flight.
- Check the forecast, not just the current conditions. Wind speed and gust spread, precipitation chance and temperature at your flight window matter more than what the sky looks like right now. A handheld unit like the anemometer entries in our wind meter roundup reads ground conditions on site, which the wind margin calculator can translate into an estimate at altitude.
On site, before power on: 5 through 8
- Check airspace authorization. Open a current LAANC-enabled app or the FAA DroneZone site and confirm your exact location and altitude are cleared, and check for active TFRs. This step is covered in full in our LAANC guide.
- Inspect propellers by hand. Run a fingernail along each blade edge feeling for a nick, and flex each blade slightly checking for a hairline crack near the hub, which is invisible from a glance but is the most common point of in-flight failure.
- Inspect the airframe and gimbal. Confirm the gimbal moves freely through its full range with no grinding, check that the gimbal clamp or cover has been removed, and look over the arms and landing gear for cracks from a prior hard landing.
- Choose and clear a launch and recovery spot. Pick flat, debris-free ground away from loose gravel, tall grass that can foul props, and bystanders. A folding 30 inch waterproof folding landing pad keeps dust and debris out of the motors on unpaved ground and gives downward sensors a clean surface to read.
Power on, before takeoff: 9 through 12
- Power the controller first, then the aircraft. This order lets the aircraft bind to a controller that is already broadcasting, which avoids the occasional failed link that can happen powering on in the reverse order.
- Let GPS lock stabilize. Wait for a strong satellite count, not just any lock, before takeoff. A weak or fresh lock is more prone to position drift in the first minute of flight than one that has had thirty seconds to settle.
- Watch for a compass or IMU calibration prompt, and run it if asked. Do not calibrate reflexively on every flight, only when prompted or when you notice drift; the full procedure and what interference looks like is covered in our calibration guide.
- Confirm control response with a low hover. Lift to a few feet, hold position for several seconds, and check for unexpected drift, unusual vibration, or an alarm before committing to a full flight. This is the last, cheapest point to abort if something is wrong.
| # | Check | Where | Why it matters |
|---|---|---|---|
| 1 | Firmware update | Home, before departure | Fixes GPS, Remote ID and sensing bugs |
| 2 | Battery charge and cycle count | Home | Catches a weak or aging pack early |
| 3 | Card format | Home or field | Prevents mid-flight recording failure |
| 4 | Wind and weather forecast | Home | Sets a go/no-go before you drive out |
| 5 | Airspace authorization | Field, before power on | Legally required in controlled airspace |
| 6 | Propeller inspection | Field | Catches the top cause of in-flight failure |
| 7 | Airframe and gimbal inspection | Field | Catches prior crash damage |
| 8 | Launch site selection | Field | Protects sensors and bystanders |
| 9 | Power-on order | Field | Avoids a failed controller link |
| 10 | GPS lock | Field | Reduces early-flight position drift |
| 11 | Compass and IMU calibration if prompted | Field | Corrects sensor drift before flight |
| 12 | Low hover check | Field | Last chance to abort cheaply |
What a failed check means
Not every failed check is a scrub. A single nicked prop is a five minute fix if you carry spares. A firmware update that will not finish over field data is a reason to fly on the current version if it is not a mandatory safety update, and check for a proper connection at home afterward. But a failed compass self-test, a GPS lock that will not stabilize, or airspace that is not authorized are all hard stops. The entire point of running the list in order is that the cheap checks happen first and catch most problems before you have invested any time in the checks that take longer.
Adapting the checklist for different flying purposes
A backyard recreational flight and a paid commercial job draw on the same underlying checklist, but the emphasis shifts. A short recreational flight in a familiar, open field can reasonably compress steps 1 through 4 into a quick mental check rather than a formal ritual, since the risk profile of a five minute hover over your own backyard is low. A commercial job on an unfamiliar client site deserves the opposite: run every step deliberately, in order, and consider printing or keeping a digital copy of the list specifically for that job, since a client watching you skip steps reads as unprofessional even if the flight itself would have been fine.
Mapping and inspection flights add a layer on top of the standard list: confirming the mission plan itself, whether overlap and altitude settings in a flight planning app or a manually flown grid pattern, matches what the job requires, and confirming any ground control points are placed and surveyed before launch rather than realizing partway through the flight that they were never set. This mission-specific layer is covered in full in how to plan a mapping mission, which sits on top of, rather than replacing, the standard preflight routine above.
What to do when a flight gets interrupted partway through the checklist
Occasionally something interrupts a preflight routine partway through, a phone call, a curious passerby, a sudden gust of wind. When that happens, resist the urge to resume from memory at whatever step you think you were on. Restart the checklist from the beginning, or at minimum from the last clearly completed step, rather than trusting an interrupted memory of where you left off. This costs at most another minute or two and removes a surprisingly common source of a skipped check: not carelessness, but a genuine, understandable gap in memory after an interruption that felt minor at the time.
Building the habit
Pilots who fly often eventually run this list from memory in under two minutes, but new pilots benefit from printing it or keeping it as a phone note for the first several dozen flights. Commercial operators under Part 107 should keep a written log of preflight checks alongside flight records, both because insurers ask for it and because a documented routine is the strongest evidence of due diligence if an incident is ever investigated. Pair this checklist with mission planning for commercial flights, and review the FAA rules quick reference if any step above raises a question about what is legally required versus simply good practice.
Questions people ask
+ What is the single most skipped preflight check?
Firmware and app update checks. Most pilots visually inspect props and check battery level out of habit, but skip confirming the aircraft and controller firmware are current, and an outdated firmware version is a common hidden cause of odd flight behavior, delayed Remote ID broadcast, or a failed compass calibration prompt mid-flight.
+ Do I need to calibrate the compass before every flight?
No, only when the app prompts you, when you have traveled a significant distance since the last flight, or when you notice erratic yaw or a toilet-bowl drift in a hover. Calibrating unnecessarily near magnetic interference can actually make things worse. Do calibrate the IMU on a level surface any time the aircraft reports drift or tilt inconsistency.
+ How do I check airspace before flying without an app?
You should not; a current airspace app is the standard tool for this. LAANC-enabled apps and the FAA UAS Facility Map both show controlled airspace boundaries, grid ceilings and active TFRs for your exact coordinates in real time, which a printed sectional or memory cannot reliably replicate for a specific day.
+ What wind speed is too much for a beginner drone?
Most sub-250 gram aircraft become genuinely hard to control smoothly above roughly 15 to 20 mph sustained wind, well before their published maximum wind resistance rating, because that rating usually describes the point where the aircraft can still hold position, not where footage still looks good. Heavier aircraft like the Air 3S handle more before it becomes visible in the shot.
+ Should I do a preflight check even for a five minute backyard flight?
Yes, in abbreviated form. Battery level, prop condition, GPS lock and a clear takeoff and landing spot take under a minute to confirm and catch the overwhelming majority of preventable incidents. The checks that take longer, like a full compass calibration or an app airspace review, matter more the farther you are flying from home or the more people are nearby.
+ What should I do if the aircraft fails a self-test during preflight?
Do not launch. A failed IMU, compass or vision-sensor self-test is the aircraft telling you it cannot trust its own sensor data, and flying anyway is how controlled hovers turn into unexplained drift or a fly-away. Restart the aircraft and controller, retry the self-test away from metal and magnetic interference, and if it fails again, do not fly until it passes.