Navigation and Flight Planning for UAS
Planning a flight you can actually fly
UAS navigation blends map reading, coordinate systems, GNSS behavior, and contingency planning. You must be fluent in latitude/longitude formats (degrees-minutes-seconds versus decimal degrees) because a transposed coordinate is a real accident cause, and in WGS-84 as the datum used by GNSS and most mapping products. Know the difference between true and magnetic heading and how magnetic variation in Brazil changes by region.
Concepts to master
- GNSS limitations: multipath near buildings, ionospheric effects, and the fact that a lost fix may trigger failsafe RTH. Know what your aircraft does on loss of GNSS and on loss of control link - these are different failsafes.
- Flight planning elements: area survey, takeoff/landing zones, alternate landing areas, obstacle survey, emergency landing sites, and a defined lost-link behavior (hover, land, or return).
- Geofencing and altitude limits: set them before flight; know that a geofence is a planning aid, not a legal authorization.
- Mission types: waypoint, corridor, and grid mapping. For grid mapping, plan overlap and account for wind drift between passes.
- Time and coordination: UTC versus local time (Brazil has multiple zones); NOTAM validity times are in UTC.
Traps and a rule of thumb
Traps: converting DMS to decimal incorrectly (e.g., 23°30'00" = 23.5°, not 23.30°); assuming RTH altitude clears all obstacles; and planning a route that crosses a restricted area because the straight line looked shorter.
Rule of thumb: plan every mission with a named alternate landing site and a lost-link plan written before takeoff. Fly the plan you briefed; if wind drift exceeds your overlap tolerance, abort and re-plan rather than stretching the battery.