Joining and leaving the circuit (TWR)
Objective
Integrate aircraft into the circuit with predictability and visual separation.
Joining the circuit (practical standard without VAC)
Typical options the TWR can use, in a staggered manner:
| Method | When to use | Advantages | Risks / precautions |
|---|---|---|---|
| Joining the downwind leg (join downwind) | most common standard | makes sequencing easier | avoid cutting base/final |
| Joining base | low and manageable traffic | reduces time in the circuit | risk of "cutting off" the traffic ahead |
| Straight-in final (straight-in) | when there is no conflict | fast | may conflict with the circuit; require spacing |
| Orbit / "remain" outside the circuit | saturation | safe | increases radio workload; define point/altitude |
Leaving the circuit (departures)
After takeoff, the TWR may:
- keep runway heading up to an altitude and then release the turn towards the route,
- release an early/late turn to avoid circuit traffic.
| Departure type | When to use | Instruction example |
|---|---|---|
| Standard departure | light traffic | "after departure, proceed…" |
| Departure with heading restriction | traffic in the circuit | "maintain runway heading until …" |
| Departure via the crosswind leg | organise flow | "turn right/left crosswind…" |
Critical point: crossing final/base
Without a VAC, treat this as a higher-risk situation:
- avoid authorising a crossing if there is traffic on final/base.
- if unavoidable, require a visual report and apply time separation (e.g. "cross after the landing traffic on final").
When in doubt
When in doubt, hold the traffic (hold/orbit) and reorder.