CAAP RPA Controller common mistakes
CAAP RPA Controller · Understand the traps and how to avoid them.
Treating the CAAP RPAS rules as a single blanket set of limits and applying the same altitude, distance, and visual-line-of-sight ceiling to every operation, instead of distinguishing between the standard operating limitations and the conditions attached to specific categories or approvals.
Candidates study a summary sheet that compresses several provisions into one line, so they memorise one number for maximum altitude or lateral distance and then apply it regardless of the operation type, location, or approval held. The compressed summary hides the qualifiers that the exam tests.
What to do instead
Rebuild your notes as a table with one row per operating limitation and separate columns for the default rule, the conditions that modify it, and the approval or notification required. For each row, write the exact circumstance in which the number changes, and practise restating the rule in a full sentence that includes its qualifier rather than reciting a bare figure.
Answering airspace questions by naming the class letter only, without stating the associated requirements for clearance, equipment, and pilot qualification, or misapplying controlled airspace rules to aerodrome traffic zones and restricted or prohibited areas.
Class letters are easy to memorise in isolation, so candidates learn the A-to-G ladder as a sequence of letters and never attach the operational meaning to each rung. When a question describes a scenario near an aerodrome, they recall the letter but not the entry conditions.
What to do instead
For each airspace class, write three lines: who may enter and on what authority, what communication and surveillance equipment is required, and what the RPAS operator must do before flight. Then draw a sketch map of a fictitious aerodrome with its traffic zone, control zones, and a nearby restricted area, and label each boundary with the rule that applies when crossing it.
Producing a flight plan or site survey that lists items without evaluating them, for example noting that obstacles exist but not recording their bearing, distance, and height, or omitting the emergency landing areas and the local noise and privacy sensitivities.
Candidates confuse a checklist with an assessment. They tick boxes to show the item was considered, but the exam scenario asks them to use the surveyed information to make a decision, and a bare tick gives them nothing to reason with.
What to do instead
Practise writing site surveys as a short narrative with numbers: for each hazard give bearing from the launch point, horizontal distance, height above launch, and the resulting maximum safe operating altitude. Add a named emergency landing area with its coordinates and a note on local sensitivities. Then answer practice questions using only your own survey notes, so you feel the difference between a list and an assessment.
Confusing the functions of the flight controller, the electronic speed controller, the inertial sensors, and the GNSS receiver, and attributing a described in-flight symptom to the wrong subsystem.
The subsystems are taught as a block diagram, so candidates remember that the components exist and are connected but not what each one alone is responsible for. Symptom-based questions then defeat them because they cannot trace a behaviour back to a single component.
What to do instead
For each subsystem, write its input, its output, and one failure symptom that is unique to it. Build a fault tree: start from an observed behaviour such as drifting in attitude hold or refusing to arm, and list the components that could cause it in order of likelihood. Test yourself by covering the component names and naming them from the symptoms alone.
Describing battery and powerplant management in general terms such as checking the battery before flight, rather than stating the specific pre-flight voltage and internal resistance checks, the effect of cold soak on available capacity, and the in-flight voltage sag that limits available power.
Battery knowledge is often learned from hobby practice, where the habit is to charge fully and fly until the low-voltage warning. That habit does not translate into the numerical, cause-and-effect answers the exam expects.
What to do instead
Learn the relationships rather than the habits: how internal resistance rises with age and cold, how that produces voltage sag under load, and how sag reduces usable capacity before the nominal cutoff. Work through numbers for a representative pack, and write a pre-flight power check procedure that states what you measure, the threshold, and the action if the threshold is not met.
Applying surface weather observations directly to the operating altitude, ignoring how wind gradient, mechanical turbulence over buildings and trees, and temperature lapse change conditions between ground level and the low-level operating band.
Candidates read the aerodrome observation or the nearest station report and treat it as valid at the drone. The reports are for a different height and often a different surface, and the exam specifically probes that gap.
What to do instead
For each weather element, write how it changes with height over the surfaces you fly near: wind speed and direction with gradient, turbulence intensity downwind of obstacles, and temperature with lapse rate. Practise converting a surface report into an estimate at your operating height and state your confidence. Learn to recognise the cloud, visibility, and stability cues that signal low-level wind shear or fog formation.
Mixing coordinate reference systems, map datums, and units when plotting a position or reporting it, so that a position is reported in the wrong datum or a distance is computed in the wrong unit.
Mapping tools default to different datums and formats, and candidates copy coordinates from one tool into another without checking. The error is silent because the numbers look plausible, and it only surfaces in a question that asks for a position report or a distance calculation.
What to do instead
Adopt one working datum, normally the one used by the national mapping authority, and state it in every note you write. Practise converting between decimal degrees and degrees, minutes, and seconds, and between metres and feet, until the conversions are automatic. Before any calculation, write the datum and units at the top of your working, and check that every input matches.
Using radio phraseology loosely, omitting the station called, the callsign of the caller, and the readback, and failing to distinguish an instruction from a request or an advisory.
Candidates rehearse radio calls as scripts and reproduce the words in the right order without understanding the function of each element. Under exam pressure they drop the readback because it feels like repetition rather than confirmation.
What to do instead
Learn each transmission as a structure: who is called, who is calling, where you are, what you want, and what you will do. Practise writing out calls for entering and leaving an area, reporting a position, and declaring an emergency, then read them aloud and check that each element is present. For every call type, note what must be read back and what may be acknowledged briefly.
Answering human factors questions with attitude and personality labels, such as saying the pilot was complacent or overconfident, instead of identifying the specific mechanism such as plan continuation, channelised attention, or normalisation of deviance, and the countermeasure that addresses it.
Everyday language offers ready-made labels for poor performance, and candidates reach for them because they sound like an explanation. The labels describe an impression rather than a cause, so they cannot support a question that asks what went wrong and how to prevent it.
What to do instead
Build a vocabulary of specific mechanisms with a definition, a typical precursor, and a countermeasure for each. For every accident or incident example you study, write the mechanism in one sentence and the countermeasure in another, then check that the countermeasure attacks the mechanism rather than the label. Practise rejecting your first label-based answer and replacing it with a mechanism-based one.
Treating lost link and emergency procedures as a single sequence, without distinguishing the programmed lost-link behaviour from the pilot's immediate actions, and without stating the order of priorities and the decision points for each contingency.
Candidates memorise one list of emergency steps and apply it to every scenario, so they cannot say which actions the aircraft performs autonomously, which the pilot performs, and in what order. They also skip the pre-flight step of programming and verifying the lost-link behaviour.
What to do instead
Write separate flowcharts for lost control link, lost GNSS, low battery, fly-away, and airspace infringement. For each, mark the automatic aircraft behaviour, the pilot's immediate actions in order, the decision points, and the post-incident reporting duty. Rehearse each flowchart aloud as a timed drill, and include the pre-flight verification that the programmed behaviour matches the plan.