Use a mission system, not memory
Define the mission
Client question, deliverable, location, altitude, route, people, aircraft, payload, crew, and permissions.
Survey the site and airspace
Controlled airspace, TFRs, NOTAMs, traffic, obstacles, launch/recovery, RF sources, people, vehicles, and emergency landing areas.
Inspect aircraft and batteries
Structure, props, fasteners, payload, firmware/configuration, control link, sensors, home point, lost-link action, and battery condition.
Brief the crew
Roles, scan sectors, standard calls, emergency actions, handoff, sterile periods, and abort criteria.
Monitor and debrief
Weather, traffic, battery, link, workload, public movement, anomalies, maintenance, and corrective action.
Automation needs supervision
Return-to-home, obstacle avoidance, geofencing, and waypoint functions have limitations. A low return altitude can hit obstacles; a high setting can waste battery, encounter stronger wind, or violate authorization. Confirm home point, route, overhead clearance, and recovery behavior before launch.
Human factors
- Task saturation: workload exceeds capacity and cues are missed.
- Confirmation bias: the pilot favors information supporting the launch decision.
- Get-there-itis: schedule or client pressure narrows judgment.
- Fixation: attention stays on one display or problem while other hazards grow.
- Good CRM: invites clear challenge, cross-checking, and early abort decisions.
Remote ID and registration
Part 107 aircraft are generally registered individually. Required registered drones must comply with Remote ID through standard Remote ID, a registered broadcast module within its limitations, or an applicable FRIA/exception. A certificate does not replace registration or Remote ID.
Emergency priorities
Protect people and other aircraft before equipment. Know how to respond to lost link, navigation degradation, motor/prop damage, battery failure, flyaway, bird conflict, weather change, and an unexpected person or vehicle entering the area.