Flight Planning, Site Survey and Pre-Flight Inspection
This domain tests whether you can build a defensible plan before the aircraft leaves the case: information gathering, physical site reconnaissance, and a documented inspection with a crew briefing.
Pre-flight information
NOTAMs, METAR and TAF, forecast wind at operating height, sunrise and sunset, airspace and landowner permission, local hazards (powerlines, cell towers, birds of prey), GNSS interference, expected spectators, and the emergency response plan with nearest hospital and access route.
Site survey
- Takeoff and landing areas: clear approach and departure paths, an alternate landing site, slope, loose material that becomes FOD, dust and reflective surfaces.
- Obstacles: measure height and distance to the tallest object within the operating radius; note that wires are frequently unmarked.
- Magnetic environment: rebar, transformers, parked vehicles and steel structures corrupt compass calibration.
- Signal environment: buildings and terrain shadow the control link; check for microwave and broadcast antennas.
Inspection and briefing
A written checklist covering airframe, propellers, motors, battery health and internal resistance, firmware version, calibration status, link range check, RTH altitude, geofence, payload security, crew roles and handover signals.
Worked example
A 60 m tower stands 300 m from the planned launch point. Maximum planned height is 100 m AGL, so the tower is laterally clear - but the default RTH height of 80 m would climb the aircraft into the tower's band if it triggered directly overhead. Reasoning: RTH altitude must clear every obstacle inside the geofence radius, not just the ones near the launch pad. Set RTH to 120 m or shrink the geofence.
Traps
Leaving default RTH altitude; calibrating beside a steel gate; treating a site visit as optional because satellite imagery exists.