Before any small unmanned aircraft system (sUAS) leaves the ground under 14 CFR Part 107, the remote pilot in command (RPIC) bears full responsibility for ensuring the aircraft is in a safe operating condition. Unlike general aviation, there is no FAA-mandated universal checklist format for sUAS — but the regulatory expectation in 14 CFR §107.15 is unambiguous: the RPIC must verify that the sUAS is in a condition for safe operation before each flight. Skipping or rushing the pre-flight inspection is not only a safety risk; it is a regulatory violation. This article builds a practical, comprehensive inspection framework that satisfies §107.15, prepares you for the FAA knowledge test, and — more importantly — keeps your aircraft flyable and your operation legal.
The stakes are real. A loose propeller, a cracked airframe, or a battery at 20% charge can turn a routine inspection flight into a fly-away event or an uncontrolled descent. Professional remote pilots treat the pre-flight checklist the same way a Part 61 pilot treats the aircraft POH checklist: it is non-negotiable, it is thorough, and it is performed the same way every single time.
The Regulatory Foundation
14 CFR §107.15 states plainly that no person may operate an sUAS unless it is in a condition for safe operation. The rule further requires the RPIC to discontinue flight when a defect is observed that could endanger life or property. This creates a continuing airworthiness obligation — not just a pre-launch moment. §107.49 extends this duty by requiring the RPIC to ensure that all equipment necessary for the planned operation is functioning properly before flight. Together, these two provisions define the legal minimum for pre-flight preparation. Manufacturers' documentation, including any operator manual or quick-start guide, serves as the baseline reference for system-specific checks, much the way an aircraft POH governs general aviation pre-flights.
Pre-Flight Inspection: A System-by-System Framework
1. Airframe and Structural Integrity
Begin with a slow, methodical walk-around of the entire aircraft. Inspect the body or fuselage for cracks, dents, stress fractures, and delamination of composite or plastic materials. Pay particular attention to motor mounts, landing gear attachment points, and any area that sustained an impact during a previous flight. Even a minor crash landing can introduce invisible micro-cracks that worsen under vibration. Check that all access panels, payload bays, and battery doors are securely closed and latched. Loose panels create unpredictable aerodynamic drag and can separate in flight, becoming a hazard to people below.
2. Propellers and Rotors
Propellers are the most common source of pre-flight-detectable failures. Inspect each propeller blade for chips, nicks, cracks, warping, and erosion. A nicked leading edge disrupts laminar airflow and reduces efficiency; a cracked blade can shed material at operating RPM with catastrophic results. Confirm that each propeller is firmly seated and correctly torqued on its motor shaft — most multi-rotor systems use self-tightening nuts (one side clockwise, the other counter-clockwise) that must be matched to the correct motor direction. Verify that the correct propeller is installed on the correct motor; reversed props are a surprisingly common cause of uncommanded rolls or loss of control. Give each blade a gentle flex test — significant play at the hub indicates a loose fitting or worn adapter.
3. Motors and Electronic Speed Controllers (ESCs)
Spin each motor by hand before powering the system. The rotation should feel smooth and free with no grinding, roughness, or lateral wobble. Any gritty sensation suggests bearing wear or debris ingestion. Visually check motor bell housings for dents, and confirm that motor mounting screws are tight. After powering up the system, listen to the ESC initialization tones and the short idle spin-test that most modern flight controllers perform automatically — uneven tone pitch or a motor that fails to spin indicates an ESC or motor fault that grounds the flight.
4. Battery Inspection and State of Charge
Battery management is one of the most test-relevant and operationally critical steps. Inspect each LiPo or LiHV battery pack for swelling (puffing), punctures, torn wrapping, and damaged connectors. A swollen battery must be removed from service immediately — it indicates internal chemical damage and is a fire hazard. Never fly a damaged battery. Check that the connector pins are clean, free of carbon deposits, and fully seated. Verify the state of charge: most manufacturers recommend beginning a flight with a battery at 100% or near-full charge. Know your aircraft's low-battery warning thresholds and planned return-to-home voltage — and set your personal minimums conservatively, accounting for the planned flight duration plus a reserve margin. A common professional practice is to plan for no more than 80% of rated flight time to ensure a safe return and landing buffer.
5. Flight Controller, Sensors, and Avionics
Power on the aircraft and the remote controller in the sequence specified by the manufacturer (typically controller first, aircraft second). Confirm that the GPS fix is acquired and that the number of satellites meets the minimum required for the intended flight mode — usually 6 or more for stable GPS-assisted hovering. Verify that the compass calibration is current and that no compass errors are displayed; flying near metal structures or after shipping can require recalibration. Check that the inertial measurement unit (IMU) is properly initialized — most systems require the aircraft to remain still during the startup calibration sequence. Review any displayed warnings in the ground control software or onboard LED indicators before proceeding.
6. Remote Controller and Data Links
Inspect the remote controller for full battery charge, proper antenna orientation, and functional control sticks with no binding or dead zones. Confirm that the control link is established and that telemetry — if available — is displaying correct aircraft status. Check that return-to-home altitude is set to clear all obstacles in the operating area, not just the default value. If a tablet or phone is used for the flight display, confirm that it is charged, that display brightness is adequate for ambient lighting, and that airplane mode or do-not-disturb is enabled to prevent notifications from interrupting the display during flight.
7. Payload and Camera Systems
If a camera or sensor payload is attached, confirm that it is securely mounted with all attachment points fastened. A loose gimbal can vibrate free and shift the aircraft's center of gravity mid-flight. Verify that the gimbal moves freely through its full range of motion and returns to the expected neutral position. Check that memory cards are inserted and have sufficient storage space, and that lens filters — if used — are correctly seated. Confirm that payload weight and balance remain within the manufacturer's specified limits; adding a heavy payload changes hover dynamics and may reduce flight time significantly.
8. Operating Environment Assessment
A complete pre-flight inspection extends beyond the aircraft itself. Assess the launch and landing zone for hazards: bystanders, moving vehicles, overhead wires, and surface debris that could be ingested by rotors during takeoff. Check current and forecast weather conditions — wind speed at operating altitude, temperature extremes (which affect battery performance), precipitation, and visibility. Verify airspace authorization is current and active for the planned flight location and time window using tools such as LAANC or DroneZone. Confirm that your Remote ID system is functioning if required — under the FAA's Remote ID rule, the broadcast module or built-in Remote ID must be active and transmitting before flight.
Why the Pre-Flight Checklist Matters
Most sUAS accidents investigated by the FAA involve a contributing factor that a disciplined pre-flight inspection would have detected: a loose propeller, a failing motor bearing, an uncharged battery, or a compass error that was never cleared. Unlike manned aircraft where mechanical redundancy and pilot recovery options are substantial, a small multi-rotor has limited fault tolerance. A single motor failure can result in an immediate, uncontrolled descent. Pre-flight rigor is the primary defense against these events. Beyond safety, documented pre-flight records demonstrate the RPIC's exercise of due diligence — a factor the FAA considers in enforcement proceedings.
Key Numbers and Rules
- 14 CFR §107.15: RPIC must verify safe condition before each flight and discontinue flight when a defect is discovered.
- 14 CFR §107.49: RPIC must ensure all equipment is functioning properly before flight.
- Most manufacturers recommend a minimum of 6 GPS satellites acquired before entering GPS-stabilized flight mode.
- A swollen (puffed) LiPo battery must be removed from service — never flown.
- Return-to-home altitude must be set to clear the tallest obstacle in the operational area, not left at factory default.
- Remote ID broadcast must be active and verified prior to flight where required.
- Battery planning should include a reserve margin — many operators limit flights to 80% of rated endurance.
Common Test Traps
- "Airworthiness certificate" confusion: sUAS operated under Part 107 do not require an FAA airworthiness certificate — but the RPIC is still legally required to verify the aircraft is in a condition for safe operation. Do not confuse the absence of an airworthiness certificate with the absence of a safety obligation.
- "One inspection per day" misconception: §107.15 applies before each flight, not once per day. A battery change or crash landing between flights requires a new inspection before the next flight.
- Ignoring the remote controller: The FAA knowledge test treats the entire sUAS — including the controller and data link — as part of the system. A dead controller battery is a pre-flight defect.
- Weather as an afterthought: Environmental assessment is part of pre-flight. Launching into deteriorating conditions without a pre-flight weather check violates the spirit — and potentially the letter — of §107.15 and §107.51 operating limitation rules.
- Assuming manufacturer defaults are safe: Default return-to-home altitudes, low-battery warning thresholds, and geofencing settings may not be appropriate for your specific site. The RPIC is responsible for verifying and adjusting these parameters before flight.