RPAS Basic common mistakes
RPAS Basic · Understand the traps and how to avoid them.
Answering airspace and distance questions from memory of the 'drone rules' only, ignoring the underlying manned-aviation structure (controlled vs uncontrolled airspace, classes, and the vertical/horizontal limits that define where the RPAS rules actually apply).
Candidates learn the operational limits (e.g. maximum altitude, distance from people) as isolated numbers and never build a mental map of the airspace system those numbers sit inside, so questions that reframe the same limit in airspace terms feel unfamiliar.
What to do instead
Before memorising limits, draw a one-page map of the national airspace structure: controlled vs uncontrolled, the boundary altitudes and distances, and where each RPAS limit attaches. Rehearse by explaining aloud where a given flight would and would not be permitted and why.
Treating right-of-way as a single ranked list and applying the top rule without checking the specific encounter geometry (head-on, converging, overtaking, or a landing aircraft).
Study guides present right-of-way as a memorised hierarchy, so candidates recall 'who wins' but not the manoeuvre each situation requires, and they default to the highest-priority rule regardless of the scenario described.
What to do instead
Learn right-of-way as four separate scenarios, each with its own required action, and practise classifying short scenario stems into one of the four before choosing an answer. State the geometry first, then the rule.
Confusing the units and reference points used in traffic-pattern and circuit questions, mixing altitude above ground with altitude above mean sea level, or mixing magnetic with true directions.
The same numbers appear in different contexts and candidates memorise values without the reference datum attached, so a question that changes the datum or the unit looks like a contradiction.
What to do instead
Annotate every altitude and direction you memorise with its datum and unit (AGL vs AMSL, magnetic vs true). For each practice question, write the datum and unit next to the figure before selecting an answer.
Selecting a multirotor or fixed-wing configuration based on the mission description alone without checking whether the stated endurance, payload or wind tolerance is physically consistent with that configuration.
Candidates match keywords in the stem ('long range', 'hover') to an airframe type and stop there, ignoring the quantitative constraints that should eliminate the option.
What to do instead
For airframe-selection questions, list the quantitative constraints in the stem first (endurance, payload, wind, hover requirement), then eliminate options that fail any one constraint. Only then use qualitative fit to choose among survivors.
Mixing up the roles of the components in the propulsion chain, for example attributing current limiting to the flight controller, voltage regulation to the ESC, or thermal protection to the battery, rather than assigning each function to the correct component.
The propulsion chain is learned as a block diagram with vague arrows, so functions blur between battery, power distribution, ESC, motor and controller, and plausible-sounding but wrong pairings survive.
What to do instead
Build a component-function table with one row per component and columns for input, output and protective function. Test yourself by covering a column and reciting it, and specifically practise distinguishing ESC functions from flight-controller functions.
Answering battery and electrical-system questions using nominal voltage and ignoring the difference between nominal, fully charged and cut-off voltages, or ignoring how current draw changes with load.
Candidates memorise a single voltage per cell (or per pack) and apply it to every scenario, so energy, endurance and low-voltage-cutoff questions produce systematically wrong numbers.
What to do instead
Memorise the three voltage states per cell (nominal, full charge, minimum safe) and the relationship between capacity, current and endurance. Work numerical practice problems using each state explicitly and check that the units and states match the question.
Applying a single 'safe distance' or 'look-out' rule to every see-and-avoid question instead of reasoning about scan technique, blind spots and the limits of human vision at the stated range and closure rate.
Human-factors content is treated as common sense, so candidates answer from intuition rather than from the specific perceptual and attentional limitations the question is testing.
What to do instead
Study see-and-avoid as a set of concrete limitations: field of view, effective detection range, empty-field myopia, motion camouflage and the effect of a structured scan. For each question, identify which limitation the stem is describing before answering.
Assuming that because the remote pilot is on the ground, fatigue, stress and workload do not apply, and answering human-factors questions as if only physical flying skills matter.
The remote setting feels detached from the aircraft, so candidates underestimate cognitive workload, vigilance decrement and the effect of automation on attention.
What to do instead
Reframe human factors as applying to the operator's task, not the aircraft's motion: attention, monitoring, decision-making under time pressure and crew coordination. Practise identifying the specific human-factor mechanism in each scenario rather than judging whether the pilot is 'in' the aircraft.
Reading a weather report or forecast and pulling out the headline value (wind speed or cloud cover) without interpreting the associated qualifiers such as gusts, direction variability, visibility groups, or the difference between forecast and observed conditions.
Candidates learn the format of reports but not how to decode the qualifiers, so they answer from the most visually prominent number and miss the element the question targets.
What to do instead
Decode reports element by element in a fixed order (wind, visibility, weather, cloud, temperature, pressure, trend) and write each decoded element in plain language before answering. Practise questions that hinge on a qualifier rather than the headline value.
Treating meteorological hazards as isolated facts and failing to connect a reported condition to its operational consequence for a small RPAS, such as how a temperature/dewpoint spread, a gust factor or a wind gradient changes flight risk.
Weather is memorised as definitions (what is fog, what is a gust) rather than as a chain from observation to effect on a light, low-inertia aircraft, so applied questions expose the gap.
What to do instead
For each hazard, memorise the observation that signals it and the specific effect on a small RPAS (loss of control authority, reduced visibility, icing, density-altitude effects on performance). Practise converting each reported value into a go/no-go judgement with a stated reason.