Study guide
2.2 Standard Operating Conditions (SOC)
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
2.2 Standard Operating Conditions (SOC)
Key Takeaways Explain This Topic AI
The Standard Operating Conditions (SOC) under CASR 101.238 are the baseline operating limits every RPA flight must comply with unless an approval, authorisation, or exemption allows otherwise.
Seven core SOC limits: 120 m AGL height; daylight/VLOS clear of cloud; at least 30 m from uninvolved people (15 m for ReOC holders with consent); at least 3 NM (5.5 km) from a controlled aerodrome's movement area; one RPA per pilot; no flight over populous areas; no prohibited or RA3 restricted areas.
SOC apply directly to micro and excluded RPA, and to included operations unless an approval permits a deviation.
An ReOC does not automatically remove the SOC; it qualifies the operator to apply for approvals that let individual pilots deviate.
Each SOC limit maps to a specific safety risk: vertical separation from manned aircraft, see-and-avoid, injury risk to people on the ground, and protection of high-density traffic and secure airspace.
Last updated: August 2026
Standard Operating Conditions (SOC)
The Standard Operating Conditions (SOC) are the baseline operating limits defined in CASR 101.238 . They exist to keep unmanned aircraft clear of crewed aircraft, people on the ground, and sensitive airspace, and they form the default operating envelope that a Remote Pilot Licence (RePL) holder works within.
When the SOC Apply — and to Whom
CASA divides commercial RPA work into three operation types : micro RPA operations, excluded RPA operations, and included RPA operations.
For excluded RPA operations (defined in CASR 101.237 ), AC 101-01 describes the SOC as unalterable rules . An excluded operator cannot apply to exceed them. That is the trade-off for not needing a RePL or ReOC.
Micro RPA operations (250 g or less) are a standalone class requiring neither a ReOC nor a RePL. They are still bound by the general Part 101 operating rules, and micro RPA cannot presently be operated under a ReOC — although a micro operator may apply to CASA for a flight authorisation such as BVLOS.
For included operations (a RePL holder flying under a ReOC), the same substantive limits apply as general flight rules, but a ReOC holder can apply to CASA to be authorised outside them.
A common exam trap is assuming a RePL alone lets you exceed the SOC; it does not. Exceeding a SOC limit requires an approval or authorisation held by the ReOC, and the pilot must be trained and assessed competent for that operation.
The SOC, Condition by Condition
AC 101-01 sets out the SOC as follows. The RPA is operated:
- # Condition Value Regulation
- 1 Only in Australian territory Including within 12 NM (22 km) of the coastline CASR 101.238
2 Within visual line of sight Pilot can see the RPA at all times and is close enough to control it in normal and emergency situations CASR 101.073
3 No higher than 400 ft (120 m) AGL Measured from the surface directly below the RPA CASR 101.085
And the RPA is not operated:
# Prohibition Detail Regulation
4 Closer than 30 m from people not associated with the flight Measured both from the RPA and from the point on the ground directly below it CASR 101.245
5 In a prohibited area or a restricted area Excluded operations can never be permitted in a prohibited area or an RA3 restricted area CASR 101.065
6 Over a populous area See CASR 101.025 for the definition CASR 101.280 / 101.025
7 Within 3 NM (5.5 km) of the movement area of a controlled aerodrome A controlled aerodrome is one with an operating control tower CASR 101.238 / 101.075
8 In the area of a public safety operation Not without the approval of the person in charge of that operation CASR 101.238
- 9 More than one RPA per pilot Only 1 RPA flown per pilot at any one time CASR 101.238
- Where "day only" actually comes from
Candidates routinely list "daylight only" as a tenth SOC item. Read the regulation carefully: the night prohibition is a separate rule, not part of the CASR 101.238 list. Unless otherwise approved by CASA, an RPA must not be operated at night , where night means the period between the end of evening civil twilight and the beginning of the following morning civil twilight . Weather limits — not operating in cloud, or in visibility too poor to maintain VLOS — come from CASR 101.095 . The practical effect is the same (a standard flight is a day, visual flight), but knowing which rule carries which limit is exactly the sort of distinction an examiner can test.
How the aerodrome distance is measured
The 3 NM / 5.5 km figure is measured from the aerodrome's published measurement point — for a runway, the midpoint between the two threshold centrepoints — not from the fence line or the terminal. Two refinements matter:
Micro RPA may be flown within 5.5 km of the measurement point of the runway of a controlled or non-controlled aerodrome up to 45 m height, provided they stay out of the movement area, out of the approach and departure paths, outside the aerodrome boundary (for a controlled aerodrome), and create no collision hazard.
At a non-controlled aerodrome, an excluded RPA may operate within 5.5 km when no crewed aircraft are operating . The moment a crewed aircraft begins to taxi for departure, or is approaching, the RPA must be landed and kept on the ground until the aircraft has departed or landed and taxied clear.
Outside tower hours , a controlled aerodrome is treated as a non-controlled aerodrome.
The excluded category ( CASR 101.237 ) deserves special attention because it is the most common source of SOC confusion. AC 101-01 defines an excluded RPA operation as one flown in compliance with the SOC that is also either:
in an RPA of not more than 2 kg ; or
in an RPA of not more than 150 kg operated over land owned or leased by the RPA owner (the landholder rule); or
in an RPA of not more than 150 kg operated solely for training or experience .
Excluded operators do not need a RePL or a ReOC (with one exception — the medium landholder case still needs a RePL). The trade-off for the lighter licensing burden is a rigid operating envelope: excluded operations cannot be approved beyond the SOC at all. If an excluded operator needs to exceed any SOC limit, they must move into the included regime — hold a RePL, fly for a ReOC holder, and obtain the relevant approval.
Why Each Limit Exists
Each SOC limit maps to a specific safety risk:
120 m AGL keeps RPA below the altitude where most crewed aircraft operate in the circuit and on approach, providing vertical separation.
VLOS and the day-only rule ensure the pilot can see the aircraft and surrounding traffic — see-and-avoid is the primary collision-avoidance method at low altitude.
30 m from people reduces injury risk if control is lost. ReOC holders may operate closer than 30 m but not closer than 15 m , and only where the person has given consent after being briefed on the risks; a risk assessment and mitigators are expected first. Going inside 15 m requires a CASA authorisation under CASR 101.245 plus an exemption from CASR 101.280.
3 NM from a controlled aerodrome protects instrument approach and circuit traffic at towered aerodromes where crewed aircraft density is highest.
One RPA per pilot caps cognitive and visual workload so the pilot can maintain effective see-and-avoid.
No populous areas limits third-party risk over crowds and built-up areas where a failure could cause mass casualties.
No prohibited/RA3 areas protects high-security or high-risk zones. Australia currently has no permanently prohibited areas — temporary ones are notified by NOTAM — but there are many permanent restricted areas, categorised RA1, RA2 and RA3 , with the category published in ERSA (permanent) or AIP SUP (temporary).
ReOC Holders and SOC Deviations
A Remote Operator's Certificate (ReOC) does not automatically remove the SOC. It qualifies the operator to apply for authorisations that let individual pilots operate outside them. Typical approvals cover BVLOS, EVLOS, above-400 ft operations (via Form 101-09, RPA Flight Authorisation ), operations inside an aerodrome no-fly zone, multi-RPA, and populous-area flight. Each usually requires a safety case, documented practices and procedures, and sometimes additional equipment. Night is the notable shortcut: CASA has already issued a night approval ( CASA 01/17 ) to all ReOC holders, so an operator whose documented procedures match the CASA sample operations manual does not need a further night application. For the exam, remember the direction of the logic: SOC is the default; authorisations are exceptions , and the authorisation sits with the operator, not with the individual RePL.
A useful exam shorthand for the SOC: territory, sight, height, people, airspace, populous, aerodrome, public-safety, one-RPA . If a scenario describes an RPA flight, walk that list and check each one. Many scenario questions embed more than one SOC breach (e.g. a pilot flying at night, within 2 NM of a towered aerodrome, over a populous area) and ask whether the flight is legal — it is not, because any SOC breach makes the operation outside the standard envelope, regardless of whether the other limits are respected.