Skip to content

2.3 Circuit Traffic

2.3.1 General

Circuit traffic operates in close proximity to the aerodrome and requires continuous monitoring by the Tower Controller.

The controller shall ensure that:

  • Adequate spacing is maintained between aircraft
  • Traffic is sequenced safely and efficiently
  • Instructions are clear, timely, and unambiguous

Circuit operations shall be managed to prevent conflicts and maintain an orderly flow of traffic.

2.3.2 Circuit Positions

Standard circuit positions include:

  • Upwind
  • Crosswind
  • Downwind
  • Base
  • Final

The Tower Controller shall maintain awareness of all aircraft positions within the circuit at all times.

2.3.3 Joining the Circuit

Aircraft may join the circuit via:

  • Direct join (e.g. downwind/base/final)
  • Overhead join (where applicable)

The Tower Controller shall:

  • Issue clear joining instructions
  • Specify runway and circuit direction
  • Integrate joining traffic with existing circuit traffic

Example Phraseology:

GFA123, join left downwind runway 27, report downwind.

2.3.4 Sequencing Circuit Traffic

The Tower Controller shall sequence aircraft to maintain safe spacing.

This includes:

  • Assigning sequence positions (e.g. “number two”)
  • Providing traffic information
  • Adjusting spacing as required

The controller shall ensure that:

  • Aircraft on final are prioritised
  • Spacing allows for safe landing and runway vacating
  • Following aircraft have the preceding traffic in sight where applicable

Example Phraseology:

GFA123, number two, follow traffic on final.

2.3.5 Spacing Techniques

The Tower Controller may use the following techniques to achieve spacing:

  • Extend downwind
  • Delay base turn
  • Issue orbit instructions (if appropriate)

These instructions shall be issued early to avoid last-minute corrections.

Example Phraseology:

GFA123, extend downwind, I will call base.  
GFA123, orbit right, report established downwind.

Orbit instructions shall not be used when:

  • Aircraft are on short final
  • Terrain or airspace restrictions make it unsafe
  • Pilot workload may be excessive

2.3.6 Integration of IFR and VFR Traffic

The Tower Controller shall integrate IFR and VFR traffic within the circuit.

The controller shall:

  • Ensure IFR aircraft are not adversely affected by VFR traffic
  • Provide adequate spacing for instrument approaches
  • Issue traffic information to both IFR and VFR aircraft

VFR aircraft may be instructed to:

  • Extend downwind
  • Orbit
  • Give way to IFR traffic

2.3.7 Go-Around Considerations

The Tower Controller shall be prepared to instruct a go-around when:

  • Separation cannot be maintained
  • Runway occupancy is not assured
  • Circuit spacing becomes unsafe

Go-arounds shall be issued early to maintain safety and minimise disruption.

2.3.8 Key Principle

Circuit traffic shall be managed proactively.

The Tower Controller shall:

  • Anticipate conflicts
  • Sequence traffic early
  • Avoid reactive or last-minute instructions

If spacing cannot be safely maintained, the controller shall take immediate corrective action.

---GFA123, wind 270 degrees 8 knots, runway 27, cleared touch and go.GFA123, wind 270 degrees 8 knots, runway 27, cleared touch and go.GFA123, extend downwind, I will call base. GFA123, number two, follow traffic on final. GFA123, cleared touch and go runway 27. 

---

## 2.3.4 Go-Around

A go-around shall be instructed when:

- The runway is occupied  
- Separation cannot be maintained  
- The approach becomes unstable  
- Any unsafe situation develops  

Example:

```text
GFA123, go around, I say again go around.

2.3.5 Key Principle

Effective circuit management is based on early sequencing, maintaining situational awareness, and issuing clear, timely instructions.