RPAS Advanced common mistakes
RPAS Advanced · Understand the traps and how to avoid them.
Classifying a flight as a basic operation when the aircraft will pass within 30 m (100 ft) horizontally of bystanders, or pass over them, instead of recognizing it as an advanced operation requiring an Advanced Pilot Certificate, a safety assurance declaration for the aircraft, and a site survey.
Candidates memorise 'basic = the easy one' without holding onto the three-part test that actually defines a basic operation (uncontrolled airspace, at least 30 m horizontally from any person not involved in the operation, never over such persons). They then apply only the 'uncontrolled airspace' part and get the certificate question wrong.
What to do instead
Before answering, write out the three tests and check each one explicitly. If any test fails - controlled airspace, closer than 30 m horizontally, or overhead flight - the operation is advanced, and the certificate, aircraft declaration and site-survey obligations follow automatically.
Assuming an Advanced Pilot Certificate authorises any flight the pilot wants, then answering that flight beyond visual line-of-sight, above 400 ft AGL, or from a moving vehicle is permitted under Part IX without further authorisation.
Candidates generalise from 'advanced certificate = most permissions' and never build a list of what still requires a Special Flight Operations Certificate or another authorisation. Exam items that describe an unusual mission (BVLOS, autonomous flight,高于 400 ft, launching from a moving vehicle) then get the 'permitted' answer.
What to do instead
Keep a short written list of operations that remain outside the standard Part IX rules and require an SFOC or equivalent authorisation, and check every scenario question against that list before choosing an answer.
Treating Class E as controlled airspace requiring an ATC clearance, or treating Class G surface airspace as controlled because an aerodrome is nearby, when asked whether a proposed flight needs permission.
Candidates learn the A–G letters as a list but never attach the operational meaning to each one, so they answer from the letter's position in the alphabet or from a vague memory that 'E is the edge case'.
What to do instead
Build a one-page table with a column for each class showing whether it is controlled, whether a clearance is required, and what the RPAS pilot must do. Class A–E are controlled, Class F is special-use (advisory or restricted), Class G is uncontrolled - recite the table before answering any airspace question.
Planning a flight from a VNC or from memory of the local area and never checking NOTAMs, then answering that a site is usable during a period when restricted airspace is active (forest-fire area, airshow, parachute drop, published altitude reservation).
Candidates treat airspace as a static printed map feature and forget that restrictions appear and disappear by NOTAM, which can activate Class F restricted airspace or close an area with no change to the chart at all.
What to do instead
Make 'brief NOTAMs for the site and time window' a mandatory step in every planning question, and remember that a NOTAM can create restrictions that no chart shows - if the question gives a time window, look for the NOTAM.
Converting coordinates incorrectly - writing 47°30' as 47.30, or entering longitude before latitude - and then selecting the waypoint or grid square that matches the wrong number.
Degrees-minutes-seconds notation looks like decimal notation to anyone who has not drilled the base-60 conversion, and many apps accept coordinates in either order without complaint, so the error is silent.
What to do instead
Always convert explicitly: minutes divided by 60 plus degrees (47°30' = 47.500). State latitude first and longitude second, and sanity-check the result against a known landmark or the chart's grid before answering.
Using the GPS-reported altitude as the height above ground when judging the 400 ft AGL limit, and assuming GPS position is continuously accurate and available.
Handheld and consumer GPS units display altitude prominently, and candidates do not distinguish ellipsoidal/GPS altitude from height above the surface, nor consider satellite geometry, jamming, spoofing or loss of signal.
What to do instead
Answer altitude questions using a local ground reference (site survey, barometric or takeoff-point reference), treat GPS altitude as unreliable for AGL limits, and build a contingency that assumes position data can degrade or disappear.
Reading only the prevailing conditions in a TAF or METAR and ignoring TEMPO, BECMG, PROB30/PROB40 groups, or the actual validity period, then declaring the flight window suitable.
Candidates scan for the first wind and visibility group, recognise familiar numbers, and stop reading. Temporary and probability groups, plus the from/to times, sit after the part they already understood.
What to do instead
Decode the product field by field in a fixed order - issue time, validity, wind, visibility, weather, cloud, temperature/dewpoint, pressure, then every trend group - and ask whether any trend group overlaps the planned flight window.
Continuing a flight in the answer because the mission is short, the client is waiting, or the aircraft is already airborne - despite a reported hazard, fatigue, or a deteriorating trend - rather than choosing to hold, land or cancel.
Plan-continuation bias and get-there-itis feel like normal commitment to the task, and candidates answer as the pilot 'would' rather than as the pilot 'should'. The cost of the wrong answer is invisible in the moment being described.
What to do instead
Apply an explicit decision model (for example DECIDE or IMSAFE) to every human-factors scenario, and treat 'the mission is nearly done' or 'the customer is waiting' in a question stem as a signal that the correct answer is to stop.
Skipping the site survey and answering emergency questions with a single generic action ('land immediately') instead of a planned sequence covering lost link, fly-away, battery failure and an identified emergency landing area.
Candidates study the normal flight profile and treat emergencies as one undifferentiated event, so they never build separate procedures for each failure mode or consider obstacles, people and alternate landing sites during planning.
What to do instead
For every flight-operations question, run a short checklist: hazards and obstacles, people and access, emergency landing areas, lost-link behaviour programmed into the aircraft, and the decision point for each failure mode. Expect the exam to test the pre-planned contingency, not improvisation.
Making the initial radio call without the full sequence, or omitting the readback of a clearance containing a hold-short instruction, an altitude, or a frequency change.
Candidates learn phraseology as words to recognise rather than as a structure to produce, and they underestimate how much of the mark depends on readback discipline - especially hold-short instructions, which must always be read back.
What to do instead
Use the fixed initial-call sequence every time (station called, own identification, position, altitude, intentions) and treat any clearance touching a runway, an altitude or a frequency as mandatory readback, including the word 'hold short'.