Study guide
13.2 Site Survey, Bystander Management, Emergencies and Giving Way
CASA Remote Pilot Licence RePL
Track your progress as you read
Finished sections get a check mark.
1 Introduction & Exam Overview
1.1 About the RePL Exam 1.2 How to Use This Guide & Build a Study Plan
2 RPA Air Law: Regulatory Framework & Standard Operating Conditions
2.1 CASR Part 101 and the Manual of Standards 2.2 Standard Operating Conditions (SOC) 2.3 The 120 m (400 ft) AGL Height Limit 2.4 VLOS, Daylight, Visibility and the One-RPA Rule
3 RPA Air Law: Licensing, Categories & Approvals
3.1 RePL vs ReOC: Pilot Licence vs Operator Certificate 3.2 Excluded Categories and Operator Accreditation 3.3 RPA Weight Categories and Registration 3.4 Operating Beyond the SOC: Approvals and the ReB1
4 Basic Aviation Knowledge (RBAK)
4.1 Direction, Wind Velocity and Aviation Time 4.2 Units of Measurement: Height, Altitude and Elevation 4.3 Aerodynamics: Lift, Drag, Thrust, Weight and Energy 4.4 Weight and Balance: Terms and Limits 4.5 Propellers and Rotors 4.6 Axes, Attitude and Flight Control Principles 4.7 The Remote Pilot Station
5 RPAS Systems: Platforms, C2 Link & Power
5.1 Multirotor vs Fixed-Wing Characteristics 5.2 Command-and-Control Link and Failsafes 5.3 Lithium-Polymer Battery Management and Safety
6 RPAS Systems: Sensors, Payload & Preflight
6.1 GNSS, Compass, IMU and Geofencing 6.2 Payload, Centre of Gravity and Pre-Flight Checks 6.3 Automated Flight Management Systems (RAFM)
7 Electrical & Electronic Systems (REES)
7.1 Electrical Terms and RPAS Electrical Components 7.2 Electric Motors, Kv and Current Draw 7.3 Battery Types, Specifications and Dangerous Goods 7.4 Charging, Discharging, Balancing and Battery Limitations 7.5 Radio Waves, Frequency Bands and Propagation 7.6 GPS Components, Errors and Electromagnetic Hazards
8 Multirotor Aerodynamics & Performance (RBKM)
8.1 Multirotor Airframe and Component Layout 8.2 Rotor Aerodynamics: Blade Design, Thrust, Drag and Torque 8.3 Hovering: Ground Effect, Recirculation and Translational Lift 8.4 Multirotor Flight Controls, Stabilisation and GPS Hold 8.5 Motor Failure, Rotor Direction and Abnormal Aerodynamics 8.6 Weight, Power, Wind and Climb Performance 8.7 Descent, Vortex Ring State and Landing
9 Navigation & Charts
9.1 Chart Fundamentals: Latitude, Longitude, Variation and Distance 9.2 Visual Terminal Charts and Visual Navigation Charts 9.3 Airspace Classes, Control Zones and CTA Steps 9.4 Restricted, Danger and Prohibited Areas and Obstacles 9.5 NOTAMs, the AIP and Chart Currency
10 Meteorology
10.1 Wind, Sea Breezes and Local Effects 10.2 Turbulence, Orographic Effects and Terrain 10.3 Thunderstorms, Fronts and Fog 10.4 Density Altitude, METAR/TAF and BoM Forecasts 10.5 Weather Observations: Reading the Sky and the Site
11 Human Factors
11.1 IMSAFE, Fatigue and Complacency 11.2 Situational Awareness, Fixation and External Pressure 11.3 Alcohol, Drugs and Crew Resource Management 11.4 Vision, Visual Limitations and Illusions 11.5 Stress and Stress Management 11.6 Threat and Error Management
12 Radio & AROC
12.1 Phonetic Alphabet, Phraseology and CTAF 12.2 The 121.5 MHz Emergency Frequency, Transponder Codes and the AROC
13 Risk & Operational Procedures
13.1 Job Safety Assessment, Risk Assessment and the Hierarchy of Controls 13.2 Site Survey, Bystander Management, Emergencies and Giving Way
14 Operations, Airworthiness & Reporting (RKOP)
14.1 Remote Pilot Responsibilities, Crew Briefing and Ground Operations 14.2 Operational, Remote Pilot and Technical Logs 14.3 Airworthiness, Serviceability and Defect Reporting 14.4 Role Equipment, Sensors and Payload Implications 14.5 Accident and Incident Reporting to the ATSB 14.6 Abnormal Operations, Fail-Safes and Flight Termination 14.7 Operating Near Aerodromes and Above 400 ft AGL
13.2 Site Survey, Bystander Management, Emergencies and Giving Way
Key Takeaways Explain This Topic AI
A site survey is a systematic reconnaissance of the operating area — on-site walk is authoritative — identifying powerlines, trees, terrain, people, animals, other airspace users, RF interference, forced-landing options, weather and sun angle.
For Standard Operating Category (SOC) operations the default bystander exclusion zone is at least 30 m from people not involved in the operation, enforced with marshals and signage.
Define emergency contingencies before takeoff: link loss (RTH/hover/land), motor failure, battery emergency, flyaway — and pre-select clear, flat, unpopulated forced-landing sites along the planned route.
Never fly over people in an emergency you cannot control — land in a tree or empty paddock rather than risk dropping the drone on a road or crowd.
An RPA must give way to manned aircraft; if a manned aircraft appears, land or manoeuvre clear and reduce altitude immediately, and maintain visual line of sight so you detect manned traffic early.
Last updated: August 2026
Site Survey and Hazard Identification
Before any flight, the remote pilot must conduct a site survey — a systematic reconnaissance of the operating area to identify every hazard that could affect the flight. The survey can be done on-site (a physical walk before takeoff) or, for pre-planning, remotely using maps, satellite imagery, charts, and apps. The on-site walk is the authoritative one: imagery may be out of date, and a tree that was not there in last year's satellite photo may be there now.
What the site survey looks for
Powerlines and cables — the single most common RPAS strike hazard; hard to see from the air and lethal to touch.
Trees and vegetation — grow into flight paths, block emergency landing options, and create turbulence on the lee side.
Buildings and structures — obstacles, wind rotors behind tall structures, and glass that reflects light and disorientates the pilot.
Terrain — slopes, drop-offs, and uneven ground that affect takeoff, landing, and forced-landing options.
People and animals — bystanders, children, dogs, livestock; all are unpredictable and must be kept clear of the operating area.
Other airspace users — manned aircraft, other drones, nearby aerodromes or helipads, and any temporary airspace restrictions.
RF (radio frequency) interference — communications towers, high-voltage lines, and industrial sites that can degrade your command-and-control link or GPS.
Forced-landing options — clear, flat, unpopulated areas along the planned route where you could land in an emergency.
Weather and sun angle — wind speed and direction at ground and altitude, gusts, precipitation, and low sun that blinds the pilot or camera.
Pre-flight hazard checklist
Run this at the site before takeoff, in addition to the aircraft checks:
Walk the area — confirm hazards match your pre-flight plan and note anything new since the imagery was captured.
Identify powerlines — trace their path and mark the crossing points on your route.
Map forced-landing spots — pick at least one clear, flat, unpopulated option along the route.
Check airspace — confirm no temporary restrictions and no manned traffic expected in the area.
Assess weather — wind at ground and altitude, gusts, precipitation, sun angle.
Scan for RF sources — towers, high-voltage lines, industrial emitters that could affect the link or GPS.
Confirm comms — control link stable, GPS lock solid, RTH set to the correct home point.
Bystander Management and the Exclusion Zone
People on the ground are the most important hazard to manage because they are the ones who get hurt. The standard control is the exclusion zone — a defined area around the operating point and under the flight path that bystanders must not enter.
For a Standard Operating Category (SOC) operation, the default exclusion zone is at least 30 m from people not directly involved in the operation.
Use marshals (crew members tasked with keeping people clear) and signage where the public may approach.
Brief the crew on who calls the abort if a person or animal enters the zone.
Never assume bystanders understand the risk — children and dogs will run toward a drone out of curiosity, and a landing drone is still spinning its props.
The exclusion zone is an administrative control, so combine it with higher-level controls where possible: route the flight away from people (eliminate), and keep the aircraft where a failure still lands it inside the zone.
Emergency and Forced-Landing Procedures
Emergencies are not predictable, but your response to them must be. The rule is to define your contingencies before takeoff , not invent them while the drone is falling.
Common RPAS emergencies
Link loss — the command-and-control link drops. Pre-configure the failsafe: Return-to-Home (RTH) , hover, or land in place, depending on the aircraft and environment. Know which mode your aircraft is set to before takeoff.
Motor failure — a motor stops. A multirotor may spin or drop; fly toward a pre-selected forced-landing site and land immediately.
Battery emergency — voltage drops faster than expected. Abort the mission, fly to the nearest safe landing point, and land.
Flyaway — the aircraft stops responding and flies off. Note the last known position, attempt to regain the link, and be ready to report to ATC or police if it enters controlled airspace or crosses a road.
Forced-landing sites
Before takeoff, pre-select forced-landing sites along the planned route — clear, flat, and unpopulated areas where you can put the aircraft down if something fails. The principle is that at every point along the route, you have a place to land that does not hurt anyone. Never fly over people in an emergency you cannot control — land it in a tree or an empty paddock rather than risk dropping it on a road, a house, or a crowd. The forced-landing decision is made before the flight, not during it.
Giving Way to Manned Aircraft
CASA's rule is unequivocal: an RPA must give way to manned aircraft . Drones are the lowest-priority users of the airspace, and a manned aircraft always has right of way.
If a manned aircraft appears in your operating area — a light aircraft, a helicopter, a rescue or police flight — the correct response is to land immediately or manoeuvre clear and reduce altitude so you are well below its flight path. Do not assume the manned pilot has seen you; they almost certainly have not. Maintain visual line of sight (VLOS) at all times so you can detect manned traffic early, and brief a spotter to call out any aircraft they see.
The same principle applies to other drones on the site: coordinate with any other RPAS operator, and never assume your link or GPS is more reliable than theirs. The smallest, lowest, and slowest aircraft yields — and that is always the drone.