Circuit Patterns, Aerodrome Traffic and CTAF Awareness

The circuit is a mental traffic map

A circuit is the normal traffic pattern aircraft use around an aerodrome for take-off, landing and sequencing. A remote pilot does not need to fly that pattern, but they do need to picture it before operating nearby.

The practical question is simple: could a crewed aircraft be climbing, descending, joining, turning or tracking near the RPA site while the drone is airborne?

Top-down view, north up, of an aerodrome with runway 09/27 running east-west. A light aircraft takes off on runway 09 towards the east and flies a left-hand circuit: upwind, then a left turn onto crosswind, downwind back towards the west on the north side, a left turn onto base, and a left turn onto final to land on runway 09. Each leg is labelled as the aircraft enters it. The departure and final approach paths are then highlighted in red as the high-priority conflict areas. Buttons change the runway in use to 27 and the circuit direction to right-hand, which mirror the pattern.

• Final and departure paths are high-priority conflict areas.
• Downwind, base and crosswind legs help explain where training traffic may appear.
• Circuit direction, runway in use and local procedures must be checked from current sources.

Runway direction helps you picture traffic

Runway numbers are magnetic orientation cues. A runway marked 18/36 points roughly north-south; 09/27 points roughly east-west. That lets the crew visualise likely approach and departure directions before aircraft are seen or heard.

Runway orientation is not permission to operate. It is a situational-awareness tool that helps the remote pilot brief observers, set boundaries and recognise when the planned area may sit under a traffic path.

A top-down aerodrome with north at the top and one runway, 18/36, running north-south. A windsock and a wind arrow show the wind. Aircraft take off and land into wind, so a north wind puts runway 36 in use and a south wind puts runway 18 in use. The circuit is drawn for the runway in use: take-off, crosswind, downwind, base and final. Circuits are left-hand unless a right-hand circuit is published. An orange worksite sits south-west of the runway and does not move. With a north wind and a left-hand circuit, the worksite is under the base leg. With a south wind, the circuit moves to the other side of the runway. A right-hand circuit flips the side again. Where the worksite sits relative to the traffic depends on the runway in use. This is situational awareness, not permission to fly, and it gives no safe distance. Helicopters and non-standard joins may not follow the circuit.

• Ask which runway is likely in use based on wind and published information.
• Brief observers on where aircraft may appear first.
• Consider helicopters and non-standard joins, not just fixed-wing circuit traffic.
• Treat uncertainty about traffic flow as a reason to pause, not as a reason to launch.

The worksite may be outside the fence but inside the traffic picture

An RPA job does not need to be on an aerodrome to affect aerodrome traffic. Approach paths, departure paths, circuit legs, helicopter routes, training areas and local transit paths can all extend beyond the aerodrome boundary.

This is where map distance can mislead. A site can be outside a simple radius but still close to a real traffic path, especially near runway extended centreline, circuit area, low-level helicopter activity or published cautions.

Top-down schematic of a non-towered aerodrome with an east-west runway, a dashed aerodrome fence and a simple radius circle around it. A drone worksite sits to the east, outside both the fence and the circle. Step 1: 'Outside radius'. Step 2: the runway extended centreline is drawn through the worksite and a light aircraft on a straight-in final approach flies over it; the worksite ring turns red: 'Final approach'. Step 3: a left-hand circuit on the south side and a helicopter route passing near the worksite are drawn and flown: 'Circuit, helicopters'. Step 4: the drone lands early: 'Land or hold clear'. Back and Next step through the scene.

• Do not operate in a way that creates a collision hazard with aircraft.
• Land or hold clear early if a crewed aircraft path becomes uncertain.
• Use observers where the pilot cannot maintain a reliable traffic picture alone.

Read the Circuits and aerodrome traffic transcript

ERSA, CTAF and chart notes turn symbols into action

ERSA can provide aerodrome facts that matter to an RPA crew: runway directions, frequencies, remarks, cautions, operating hours, lighting, procedures and local notes. Charts show the structure; ERSA and NOTAMs explain the operational details.

CTAF awareness is about shared traffic awareness at non-controlled aerodromes. If the operation requires radio communication, the crew needs the correct qualification and equipment. Even where transmitting is not required, the remote pilot still needs a plan for hearing, seeing and responding to traffic.

A schematic top-down map of a non-towered aerodrome, using Kingaroy as the example, with a drone worksite outside the aerodrome boundary. A checklist on the right lights up one item at a time. Chart: the aerodrome appears as a chart symbol and a dashed line links it to the worksite. ERSA: the symbol turns into the runway, boundary and aerodrome name. CTAF: a left-hand circuit is drawn and a light aircraft flies it while broadcasting, and the worksite shows the crew's briefed radio plan (monitor only, transmit, or no radio required, where the crew still plans to see and hear traffic). Decision: the whole picture is framed and the question 'Go, modify or stop?' appears. Buttons step through the checks and choose the radio plan.

• Check current aerodrome information and NOTAMs close to flight time.
• Confirm the CTAF or frequency context from current sources, not memory.
• Brief radio assumptions clearly: monitor only, transmit, or no radio required under the approved procedure.
• Do not publish or use example calls operationally until reviewed by an aviation SME.

Controlled and non-controlled aerodromes are different problems

Near controlled aerodromes, the key question is authorisation and controlled-airspace interaction. Around non-controlled aerodromes, the key question is often traffic awareness, circuit conflict and whether the drone operation must give way, land, coordinate or stay clear.

CASA guidance, operator approvals and current aeronautical information must decide the exact pathway. For study, the durable habit is to recognise the trigger early and stop pretending an aerodrome-adjacent job is just a normal paddock job.

• Controlled aerodrome: check approval, airspace, movement area and approach/departure path restrictions.
• Non-controlled aerodrome: check circuit, CTAF, traffic, runway direction and published cautions.
• Any aerodrome: check NOTAMs and current operator procedures before launch.

Set clear traffic triggers before launch

A remote pilot should not wait until a crewed aircraft is close before deciding what to do. The crew brief should include triggers that produce a simple response: hold, land, remain below a lower height, move inside a tighter boundary, or do not launch.

This is study guidance, not legal advice. Verify current CASA rules, Airservices information, ERSA, NOTAMs, operator approvals and aviation reviewer advice before using any aerodrome-adjacent procedure.

• Aircraft heard or seen joining circuit: hold or land according to the brief.
• Aircraft on final or departure path near the worksite: land or remain clear early.
• Traffic picture uncertain: pause and resolve before launch or continue only if the procedure allows it.
• Radio or observer workload too high: simplify the task or stop.

Practice Questions