Standard (rectangular) circuit when there is no VAC
Basic circuit geometry
Without published restrictions, use a simple rectangle around the runway:
| Leg | Function | Point of attention |
|---|---|---|
| Upwind leg (upwind) | Parallel to the runway, offset from the centreline, in the landing direction | avoid crossing/entering the opposite circuit |
| Crosswind (crosswind) | Transition to the circuit side | start the turn according to altitude/profile |
| Downwind leg (downwind) | Parallel to the runway, opposite to the landing direction | where the TWR organises the sequence |
| Base leg (base) | Final turn for alignment | adjust separation with the traffic ahead |
| Final | On the extended centreline, approach and landing | stabilisation, clearance, go-around |
Standard direction per runway (no publication)
- Left-hand turns for the runway in use.
- If there is an operational reason (obstacles, city, noise, heliport, etc.), this is a local restriction and must be treated as a specific procedure (publication/instruction).
Circuit side (practical notion)
- "Left-hand circuit RWY XX": the pilot makes all turns to the left.
- "Right-hand circuit RWY XX": the pilot makes all turns to the right.
Runway in use (no VAC)
Recommended (practical) criteria:
- prioritise headwind, runway conditions, safety and flow.
- avoid frequent runway changes if this degrades the sequence and increases conflict.
Example of a quick TWR briefing (standard)
- Runway in use: RWY 16
- Circuit: right-hand
- Reports: downwind / base / final
- Restrictions: (if any) "avoid overflying area X", "maintain 1000 ft AAL in the circuit", etc.
Local information
If local information appears (through any official means), replace the standard immediately.