Study guide

2.4 VLOS, Daylight, Visibility and the One-RPA Rule

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.4 VLOS, Daylight, Visibility and the One-RPA Rule

Key Takeaways Explain This Topic AI

VLOS (CASR 101.073) requires the RPA to be visible to the unaided eye throughout the flight; corrective lenses are permitted, but binoculars, telescopes, and FPV-only camera flight are not.

Daylight under the SOC means between morning civil twilight and evening civil twilight; night flight requires a CASA approval.

CASR 101.095 prohibits operation in cloud, thick fog, or insufficient visibility to maintain VLOS and see-and-avoid — standard RPA operations are always visual.

The one-RPA-per-pilot limit caps workload so the pilot can maintain see-and-avoid; multi-RPA/swarm operations need a CASA approval, typically via an ReOC.

Under CASR Part 101, an RPA must give way to manned aircraft because the consequence of a mid-air collision for a manned aircraft is potentially fatal.

Last updated: August 2026

VLOS, Daylight, Visibility and the One-RPA Rule

Three of the Standard Operating Conditions — Visual Line Of Sight (VLOS) , daylight , and one RPA per pilot — work together as the core see-and-avoid system for remote pilots. They are examined individually and in combination, so understanding the definitions and the reasoning behind them matters.

VLOS — Visual Line Of Sight (CASR 101.073)

Visual Line Of Sight (VLOS) means the remote pilot can see the RPA unaided throughout the flight and is close enough to maintain control of the aircraft in both normal and emergency manoeuvres. The key points:

Unaided eye only — you may not use binoculars, telescopes, or any optical magnification aid to maintain VLOS. The aircraft must be visible to the naked eye.

Corrective lenses are permitted — ordinary prescription glasses or contact lenses are not considered an "aid" that disqualifies VLOS. The rule targets magnification, not vision correction.

Maintain control — VLOS is not just about seeing the aircraft; the pilot must be close enough that, if something goes wrong, they can visually command the aircraft to a safe outcome.

First-person view (FPV) cameras alone are not VLOS — flying using only an onboard camera feed is Beyond Visual Line Of Sight (BVLOS) and requires an approval.

When the aircraft can no longer be seen unaided, the operation has crossed into EVLOS (Extended Visual Line Of Sight — using observers to extend the visual range) or BVLOS , both of which require CASA approval. EVLOS uses one or more visual observers to keep the RPA (or its surroundings) in sight; BVLOS relies on instruments, sensors, or cameras alone.

Daylight and Civil Twilight

The SOC require operations only during daylight — defined as the period between the beginning of morning civil twilight and the end of evening civil twilight at the location. Civil twilight is the period when the sun is below the horizon but its geometric centre is no more than 6° below it; there is enough light to see unaided and to conduct see-and-avoid. CASA publishes civil twilight times for Australian locations, and flight planning software calculates them automatically.

Operations at night are outside the SOC and require a specific CASA approval. The reasoning is twofold: the unaided eye cannot reliably see an RPA (or surrounding traffic) in darkness, and manned aircraft lighting and separation norms are built around daytime see-and-avoid. A night approval usually requires additional equipment (lights, observers), an ReOC, and an approved safety case.

Note the boundary: civil twilight is not the same as sunrise/sunset. Morning civil twilight begins roughly 20–30 minutes before sunrise (varies by latitude and season), and evening civil twilight ends roughly 20–30 minutes after sunset. A flight at 10 minutes after sunset may still be within evening civil twilight and therefore within the SOC, but a flight 40 minutes after sunset is almost certainly in darkness and outside the SOC. In the southern hemisphere summer at higher latitudes, civil twilight can be very short; in winter it is longer. Always check the published twilight times for the operating location and date rather than guessing.

Visibility: Clear of Cloud, No Fog

Complementary to daylight, CASR 101.095 requires that an RPA not be operated in cloud or in thick fog or in conditions of insufficient visibility to maintain VLOS and see-and-avoid. The practical test: if you cannot see the aircraft unaided, or cannot see surrounding sky well enough to detect manned traffic, you must not fly. Unlike manned instrument flying, RPA operations under the SOC are always visual — there is no "instrument meteorological conditions" capability for a standard RPA flight.

One RPA per Pilot

The SOC limit of one RPA per pilot means a single remote pilot may operate only one RPA at a time. The reasoning is workload and see-and-avoid:

Operating one RPA already demands continuous visual attention and control inputs.

Adding a second aircraft splits the pilot's scan, reduces the time each aircraft is in view, and increases the chance of a mid-air collision or loss of control.

Emergency handling (a motor failure, a fly-away, a low-battery landing) is near-impossible to manage for two aircraft simultaneously.

Operations involving more than one RPA per pilot — sometimes called multi-RPA or swarm operations — require a CASA approval, generally held by an ReOC operator, with a safety case demonstrating how workload is managed (e.g. autonomous waypoint missions with autonomous fail-safes, separate ground stations, or visual observers).

Give Way to Manned Aircraft

Under CASR Part 101, an RPA must give way to manned aircraft. This reflects the principle that unmanned operations yield to manned operations because the consequence of a mid-air collision for a manned aircraft is potentially fatal, whereas an RPA collision risk is generally to people and property on the ground. In practice, give way means: maintain visual scan for manned aircraft, descend or manoeuvre clear if a manned aircraft approaches, and never assume the manned pilot has seen the RPA — most manned aircraft have no detection capability for small RPA. If a collision risk develops, the RPA pilot acts first and decisively.

The give-way rule also means the RPA pilot should avoid operating at altitudes and locations where manned aircraft are known to transit — near aerodrome circuit patterns, along helicopter routes, over hospitals with helipads, and along coastlines where scenic helicopter flights occur. Even when operating within the 120 m AGL limit, an RPA pilot may encounter low-flying manned aircraft (helicopters, agricultural aircraft, emergency services) that are below 400 ft. The response is always the same: the RPA gives way, descends if practical, and lands or holds if a collision risk cannot be eliminated.

Putting the three conditions together — VLOS, daylight, one RPA — the standard remote pilot's operating loop is: keep the aircraft in unaided sight throughout the flight, fly only between morning and evening civil twilight, stay clear of cloud and fog, fly one aircraft at a time, and continuously scan for manned traffic to give way. Every SOC deviation from that loop requires a documented approval.