Skip to content

Decision: Straight-in final vs Joining the Downwind leg (TWR) + Full script (3 aircraft)

Decision table — when to allow a Straight-in Final

Use this table as a practical rule when there is no VAC or when there is no local procedure that explicitly addresses the "straight-in".

Operational principle

Predictability > convenience.
If the decision increases the risk of conflict with the circuit, do not authorise a straight-in final.

Quick matrix

Condition Allow straight-in final? Recommended action (TWR) Notes
Empty circuit / 1 well-spaced traffic ✅ Yes "straight-in approved, report final" keep awareness of wind/runway occupancy
There is traffic established in the circuit (downwind/base) ⚠️ It depends prefer "join downwind leg" straight-in only with clear separation
Traffic on base/short final ❌ No "remain outside / orbit / join downwind leg" avoids convergence and "cut-in"
Performance mix (jet behind piston) ❌ Prefer not if authorised, increase spacing reordering is usually better
Marginal visibility / low ceiling (degraded VMC) ❌ No standardise joining the downwind leg and reports reduces surprises and loss of SA*
Pilot without traffic in sight (when "follow" would be needed) ❌ No resequence with extension/orbit without visual contact, do not "fit it in" by eye
Aerodrome with likely obstacles/sensitive area ❌ No join downwind leg as per standard without a VAC, do not assume safe routes
Runway may change (variable wind) ❌ No remain outside until the runway is stable avoids traffic coming "the wrong way"

SA = Situational Awareness

SA stands for Situational Awareness (in Portuguese, Consciência Situacional).

Implementation rules (short and objective)

  • Straight-in final only when you can guarantee:

1) separation (time/lateral) from the circuit;
2) zero conflict with base/final;
3) predictability (no multiple simultaneous joinings). - If you authorise a straight-in final at an aerodrome with traffic in the circuit: - state the sequence ("number 2 after…"), - require a visual report (if applicable), - use extend downwind leg or an orbit to create spacing.

Full script — sequence of 3 aircraft (PT/EN)

Scenario

  • Runway in use: RWY 16
  • Circuit: left-hand
  • Aircraft:
  • PT-ABC (piston) — standard circuit 1000 ft AAL
  • PR-JET (jet) — high circuit 1500 ft AAL
  • PR-HLX (helicopter) — low circuit 500 ft AAL, dedicated route to the south

Objective: show a realistic radio sequence with organisation, separation and mitigation of mixed traffic.

Focus of this script

What matters here is the controller's decision: in which order to place the aircraft and how to create spacing. The transmissions are written in abbreviated form for quick reading.

On frequency, the unit is always TORRE followed by the location name, the registration is read letter by letter and numbers digit by digit. The complete phraseology, in Portuguese, English and Spanish, is in the VFR Phraseology Manual.

1) Piston joining and establishing in the circuit

  • PILOTO: "TORRE, PT-ABC, 5 milhas ao norte, 1500 pés, para pouso."
  • TWR: "PT-ABC, autorizado para o circuito de tráfego, pista 16, circuito à esquerda, vento ___, QNH ___, reporte perna do vento."
  • PILOTO: "Autorizado para o circuito de tráfego, pista 16, circuito à esquerda, QNH ___, reportará perna do vento, PT-ABC."
  • PILOT: "TOWER, PT-ABC, 5 miles north, 1500 feet, inbound to land."
  • TWR: "PT-ABC, cleared to traffic pattern, runway 16, left-hand circuit, wind ___, QNH ___, report downwind leg."
  • PILOT: "Cleared to traffic pattern, runway 16, left-hand circuit, QNH ___, will report downwind leg, PT-ABC."

2) Jet approaching — keep separated from the piston

  • PILOTO: "TORRE, PR-JET, 8 milhas a leste, 2500 pés, para pouso."
  • TWR: "PR-JET, pista 16, circuito à esquerda, mantenha 1500 pés AAL, ingresse na perna do vento, reporte na perna base."
  • PILOTO: "Circuito à esquerda, 1500 pés AAL, reportarei na perna base, PR-JET."
  • PILOT: "TOWER, PR-JET, 8 miles east, 2500 feet, inbound to land."
  • TWR: "PR-JET, runway 16, left-hand circuit, maintain 1500 feet AAL, join downwind leg 2 miles, report downwind leg."
  • PILOT: "Left-hand circuit, maintaining 1500 feet AAL, joining downwind leg, will report downwind, PR-JET."

3) Helicopter — low circuit/dedicated route without crossing final

  • PILOTO: "TORRE, PR-HLX, pátio sul, para decolagem e circuito."
  • TWR: "PR-HLX, autorizado decolagem, mantenha circuito baixo 500 pés AAL ao sul, não cruze a final, reporte base."
  • PILOTO: "Autorizado decolagem, 500 pés AAL ao sul, sem cruzar final, reportarei base, PR-HLX."
  • PILOT: "TOWER, PR-HLX, south apron, ready for departure and circuits."
  • TWR: "PR-HLX, cleared for takeoff, maintain low circuit 500 feet AAL south of the aerodrome, do not cross final, report base."
  • PILOT: "Cleared for takeoff, 500 feet AAL south, will not cross final, will report base, PR-HLX."

4) Sequencing the piston traffic for landing

  • PILOTO: "PT-ABC, na perna do vento."
  • TWR: "PT-ABC, número 1, reporte na perna base."
  • PILOTO: "Número 1, reportarei base, PT-ABC."
  • PILOTO: "PT-ABC, na perna base."
  • TWR: "PT-ABC, pista 16, pouso autorizado, vento ___."
  • PILOTO: "Pouso autorizado, pista 16, PT-ABC."
  • PILOT: "PT-ABC, downwind leg."
  • TWR: "PT-ABC, number 1, report base leg."
  • PILOT: "Number 1, will report base leg, PT-ABC."
  • PILOT: "PT-ABC, on base leg."
  • TWR: "PT-ABC, runway 16, cleared to land, wind ___."
  • PILOT: "Runway 16, cleared to land, PT-ABC."

5) Managing the jet to avoid closing up on the piston (spacing)

  • PILOTO: "PR-JET, na perna do vento."
  • TWR: "PR-JET, número 2 após PT-ABC, mantenha tráfego à vista, alongue perna do vento, aguarde autorização para ingresso na perna base."
  • PILOTO: "Número 2 após PT-ABC, tráfego à vista, vai alongar a perna do vento, aguardará autorização para a perna base, PR-JET."
  • TWR (quando aplicável): "PR-JET, gire base, reporte na final pista 16."
  • PILOTO: "Gira base, reportará na final pista 16, PR-JET."
  • PILOTO: "PR-JET, na final pista 16."
  • TWR: "PR-JET, pista 16, pouso autorizado, vento ___."
  • PILOTO: "Pouso autorizado, pista 16, PR-JET."
  • PILOT: "PR-JET, downwind leg."
  • TWR: "PR-JET, number 2 after PT-ABC, report traffic in sight and follow, extend downwind leg, standby for further instructions for turning base."
  • PILOT: "Number 2 after PT-ABC, traffic in sight, extending downwind, waiting for base clearance, PR-JET."
  • TWR (when appropriate): "PR-JET, turn base and report on final runway 16."
  • PILOT: "Turning base and will report on final runway 16, PR-JET."
  • PILOT: "PR-JET on final runway 16"
  • TWR: "PR-JET, runway 16, cleared to land, wind ___."
  • PILOT: "Runway 16, cleared to land, PR-JET."

6) Helicopter integrating without crossing final

  • PILOTO: "PR-HLX, girando base (circuito baixo sul)."
  • TWR: "PR-HLX, autorizado aproximação/POUSO (conforme área designada), mantenha separado do eixo da pista, reporte no solo."
  • PILOTO: "Autorizado, manterei separado do eixo, reportarei no solo, PR-HLX."
  • PILOT: "PR-HLX, base leg (low circuit south)."
  • TWR: "PR-HLX, cleared approach/landing (as assigned), remain clear of runway centerline, report on the ground."
  • PILOT: "Cleared, will remain clear of centerline, will report on the ground, PR-HLX."

Note

If you prefer to keep the helicopter using the "runway" (touch-and-go), rewrite it to integrate with the fixed-wing traffic only when the circuit is light.

Final notes

This script demonstrates:

  • Altitude separation between the piston (1000 ft), the jet (1500 ft) and the helicopter (500 ft)
  • Downwind extension to create adequate spacing and avoid "closing up" on the traffic ahead
  • Dedicated helicopter route keeping it off the fixed-wing traffic axis and without crossing final
  • Explicit sequencing ("number 1", "number 2 after...") for clarity
  • Consistent reports supporting situational awareness
  • Standardised phraseology in PT/EN

Practical application

Use this script as a reference for training and standardising communications in circuit operations with multiple aircraft of different categories, especially when separation between aircraft of different performance needs to be managed.