s2-training

S2 Training Document

Document Identification
Type Training Material
Version 1.0
Issue Date 13th August 2024
Effective Date 13th August 2024

Revision Records

Revision Date Description of Change Author
1.0 13th August 2024 Initial draft Amir G.

Purpose

This document is published for the purpose of S2 Training. This Guideline shall be adhered to by all Iran vACC resident controllers.

This document is only used for VATSIM Virtual ATC training purposes. DO NOT use this document for Real World ATC training or whatsoever. VATSIM Iran vACC shall NOT be held responsible and accountable for the usage of this document in all Real-World ATC training and Real-World Flying Activities.

S2 Controller (ADC) Overview

  1. As an S2 Controller (ADC), the Area of Responsibility has expanded. Controllers shall have jurisdiction over:

    • Surface movement on the ground.
    • Issuing ATC clearances.
    • Traffic on the runway(s).
    • Traffic in the immediate surrounding airspace.

  2. The surrounding airspace is known as a Control Zone (CTR). A Control Zone is defined as controlled airspace extending upwards from the surface of the earth to a specified upper limit.

  3. Control Zones are usually an airspace of 5 to 20 nautical miles centered on the aerodrome reference point or the airport navigation ground aid VOR Station, extending up till 1500 feet. Most Control Zones in Iran are Class D airspaces.

  4. ADC are responsible for: a. Air Traffic on the ground. b. Air Traffic entering or leaving the Control Zone (via VFR lanes or other routings). c. Air Traffic intending to land or take off from an aerodrome. d. Air Traffic in the circuit pattern.

  5. At some aerodromes with no approach control (radar) service, ADC may be required to perform combined duties, but for the purpose of VATSIM, it is rarely simulated.

  6. An ADC Controller shall carry out both SMC (Ground) and ACD (Clearance Delivery) responsibilities only when in the absence of these positions.

Control of Visual Circuit Traffic

  1. A circuit is the most basic pattern that a pilot learns during flight training. As an ADC Controller, you must be familiar with all positions in the circuit and how to control circuit traffic.

  2. The visual aid below shows a normal VFR Circuit pattern.

    • The side on which the circuit is active is called the "Live Side".
    • The non-active side is called the "Dead Side".

    (Diagram reference from original document - See page 4)

  3. Each segment is called a "Leg". There are 5 legs in a circuit pattern:

    • Upwind
    • Crosswind
    • Downwind
    • Base
    • Final

  4. A common circuit height for most fixed-wing aircraft is between 1000 feet and 1500 feet, depending on aircraft and performance. For helicopters and light aircraft, it can be as low as 500 feet. For jet aircraft such as B787 and A320, it could be as high as 2000 feet.

  5. Circuit height and direction will also differ depending on local regulations. Controllers must refer to the AIP for regulations procedures if necessary.

  6. Mandatory reporting points in a circuit are Downwind and Final leg. Controllers shall instruct the pilot to report when established on said position should the pilot forget.

  7. The crosswind, downwind and base legs can be further divided into 3 sections: EARLY, MID, and LATE. Controllers may instruct a pilot to report those positions for traffic planning, but it is not commonly done as VATSIM controllers perform ATC duties using a radar scope.

  8. A Practiced Force Landing (PFL) is a general handling exercise where a pilot simulates a glide approach into the runway without any power. Usually, a PFL would require the pilot to fly overhead the runway before cutting power at between 2000 feet and 2500 feet.

Long vs. Short Final

  • "Long Final" is anywhere beyond 8 NM to the runway.
  • "Short Final" is less than 4 NM to the runway.

Unless the pilot specifies the number of circuits, the controller must ask the pilot for their intention each time they report downwind or final.

Example: a. EPPOL: "Tower, EPPOL is on final runway 29L." b. ADC: "EPPOL, say intention." c. EPPOL: "Request for touch and go / go around / low approach / full stop landing"

ATC Clearances

ATC Clearances for traffic operating within the Control Zone or departing via VFR routes are slightly different from usual IFR flights.

  1. ATC Clearance for Circuit & Landing Traffic:

    • Situation: EPPOL (DHC6 Twin Otter) intends to perform left circuits at 1000 feet at Mehrabad Runway 29L.
    • Clearance example: "EPPOL, Cleared for left hand circuit runway 29L, 1000 feet, squawk 7000."

  2. ATC Clearance for VFR Traffic Proceeding Beyond Controlled Airspace:

    • Situation: EPPOL (C172) OIIO - OIIP DCT 1500 FT.
    • Clearance example: "EPPOL cleared to leave Mehrabad Control Zone Boundary (CTR) en-route to Payam, 1500 feet, Squawk 7000."

Circuit Traffic Separation

Separation between circuit traffic can be achieved by:

  1. Vertical separation - restricting each circuit traffic to a different altitude.

    • Example:
      • Traffic A : EP-POL 1000 FT
      • Traffic B : EP-POY 2000 FT

  2. Holding traffic at different positions in the circuit.

    • Only same General Aviation Light Training Aircraft could hold on the same downwind leg.
    • Only one Large Commercial Jet Aircraft can occupy the circuit at one time.

  3. Asking aircraft to sight each other to maintain own visual separation. If one or both aircraft sight each other, this method may be applied.

Aircraft Handoff Sequence Flow

  1. Departing aircraft will be transferred to ADC (Tower) by SMC (Ground) at a pre-determined position. Before clearing an aircraft for take-off, ADC shall ensure:

    • Aircraft has Squawk Mode C and reported ready for departure.
    • No inbound aircraft within 5 NM from touchdown.
    • The departure path is clear.
    • Runway is vacant and clear from any other aircraft or vehicle.

  2. ADC controller shall hand off traffic to APP or ACC Controller as soon as airborne.

  3. ADC Controller shall not assume control of the aircraft while it is still on the runway.

  4. Arriving aircraft shall be transferred to ADC by APP or ACC. Before giving landing clearance, ADC Controller shall ensure:

    • There is no other preceding traffic on final.
    • Runway is clear from any other aircraft.
    • An aircraft previously cleared for take-off prior to the arrival is already airborne.

  5. ADC Controller shall provide runway vacating instructions together with frequency change instructions. If needed, ADC may issue additional taxi instructions.

  6. Both ADC and SMC Controllers are expected to always be in sync with each other in regard to issuing parking or taxi instructions.

Standard Phraseology

Engine Start, Pushback, and Taxi

Situation Phraseology
Issuing engine start clearances START APPROVED
START AT (time)
EXPECT START UP AT (time)
START APPROVED AT OWN DISCRETION
EXPECT DEPARTURE AT (time) START APPROVED AT OWN DISCRETION
Issuing pushback clearances PUSHBACK / PUSH AND START APPROVED
FACE (direction) / EXIT VIA (taxiway) RUNWAY xx
For pushback from bays with only one possible direction PUSHBACK / PUSH AND START APPROVED
RUNWAY xx
When there will be a delay for pushback PUSHBACK AT OWN DISCRETION
STANDBY FOR PUSHBACK
EXPECT xx MINUTES DELAY DUE (reason)
Issuing conditional pushback clearance ONCE CLEAR OF (traffic information), PUSH AND START APPROVED FACE (direction) / EXIT VIA (taxiway) RUNWAY xx
Issuing taxi instructions TAXI TO HOLDING POINT xx RUNWAY xx VIA (taxi route)
TAXI VIA (taxi route) HOLD SHORT OF RUNWAY xx / (taxiway name)
TAXI VIA RUNWAY xx
TAXI TO TERMINAL (or other locations) VIA (taxi route)
Taxi to follow behind another aircraft TAXI NUMBER TWO BEHIND (traffic information)

Helicopter Taxi

Situation Phraseology
Issuing taxi instructions for helicopter REQUEST AIR-TAXI FROM / VIA TO (location or routing)
AIR-TAXI TO / VIA (direct, as requested, or a specific route)

After Landing

Situation Phraseology
After landing REQUEST BACKTRACK
BACKTRACK APPROVED
BACKTRACK RUNWAY xx
General taxi instructions REQUEST TAXI TO (destination or point on aerodrome)
TAXI STRAIGHT AHEAD GIVE WAY TO (description and / or position of other aircraft)
FOLLOW (description and / or position of other aircraft)
VACATE RUNWAY VIA (taxiway or intersection)
EXPEDITE TAXI (with reason)
[CAUTION] TAXI SLOWER (with reason)

Holding and Crossing

Situation Phraseology
Holding HOLD (direction) OF (position) (runway, etc)
HOLD POSITION
HOLD SHORT OF (position)
To cross runway REQUEST CROSS RUNWAY xx
CROSS RUNWAY xx [REPORT VACATED]
EXPEDITE CROSSING RUNWAY xx TRAFFIC (aircraft type) (distance) MILES FINAL

Take-off

Situation Phraseology
Preparation for take-off UNABLE TO ISSUE / APPROVE (designator) DEPARTURE (with reason)
REPORT WHEN READY [FOR DEPARTURE]
ARE YOU READY FOR DEPARTURE?
ARE YOU READY FOR IMMEDIATE DEPARTURE?
Clearance to enter runway and await take-off clearance LINE UP [AND WAIT] RUNWAY xx
LINE UP RUNWAY xx
LINE UP RUNWAY xx BE READY FOR IMMEDIATE DEPARTURE
Take-off clearance RUNWAY xx CLEARED FOR TAKEOFF [REPORT AIRBORNE]

Delaying, Missed Approach, and Wake Turbulence

Situation Phraseology
Delaying aircraft CIRCLE THE AERODROME
ORBIT RIGHT / LEFT [FROM PRESENT POSITION]
MAKE ANOTHER CIRCUIT
Missed approach GO AROUND (go around instructions if any)
Wake turbulence information CAUTION WAKE TURBULENCE FROM ARRIVING / DEPARTING (type of aircraft)
(additional information if required)

Runway Vacating and Comms

Situation Phraseology
Runway vacating instructions WHEN VACATED CONTACT GROUND (frequency)
EXPEDITE VACATING
TAKE / TURN LEFT / RIGHT AND CONTACT GROUND (frequency)
Runway vacating & comms after landing (helicopter) AIR TAXI TO (helicopter stand or parking position)
CLEARED FOR DISPERSAL AT (apron / parking area)

END OF DOCUMENT