Procedures for Handling of Flights
Module 1 • MATS-2 (VEGT) • Chapter 17 • Controller actions for arrivals, departures & special ops
Home

Arriving Flights Arrivals • Landing • Final

Controller must pass current landing information, except items the aircraft has already received.
Landing Information (to aircraft) Information TWR passes to APP
• Traffic pattern (left/right circuit)
• Runway in use
• Surface wind
• Altimeter (QNH)
• Supplementary information
• Clearance to land / expect late landing clearance
• Any significant VIS/RVR change
• Status of visual or non-visual aids
• Reports of low-level windshear
• Runway Condition Report / braking action 		• Arrival time if visual approach
• Missed approach / unreported / overdue aircraft
• Runway in use
• Current weather including QNH changes
Final approach — transmit if significant:
  • Changes in VIS / RVR
  • Significant changes in surface wind (min / max)
  • Runway surface condition changes
  • Strong wind / windshear reports on final

Departing Flights Departures • Start-up • Sequence

Before start-up — obtain:
  • Status of security check
  • Total persons on board (pax + crew)
Sequencing:
Clear departures by taxiing / holding-point sequence to minimise delay. Deviations are allowed for VVIP, ATFM requirement, or traffic reasons. Avoid keeping an aircraft waiting too long at the holding point without need.
Departure instruction:
If not an RNAV SID: issue the standard departure instructions (MATS-2 Para 17.8) or any heading/level instruction coordinated by Approach. These should be passed before RWY entry (via SMC/TWR).
Departure Information (prior to taxi):
  • Runway to be used
  • Current surface wind
  • QNH (or QFE if specifically requested)
  • Air temperature (for turbine engines)
  • Current visibility / RVR
  • Correct time

Transfer of Control Coordination • TWR↔SMC • APP↔TWR • ACC↔APP

Between TWR and SMC
ARR (TWR → SMC) DEP (SMC → TWR) Remarks
On taxiway At holding point of applicable taxiway SMC may release traffic to TWR before holding point for traffic management.
After vacating parallel taxiway At taxi TWR & SMC may mutually agree for management of IAF dispersal area traffic.
Between TWR and APP
Arrival (APP → TWR) Departure (TWR → APP)
• On final ≤ 11 NM for RWY 02 or ≤ 10 NM for RWY 20
• On downwind/base if VFR or visual approach 		• After airborne
Note: the next arrival on the same final is not released until the preceding aircraft has crossed 2 NM from touchdown and spacing is ensured.
Between ACC and APP
Arrival (ACC → APP) Departure (APP → ACC) Overflying Traffic VFR Traffic
At 50 NM and passing FL150 At 50 NM or passing FL140 Transiting ≤ FL140:
transfer at 50 NM 		At 40 NM from GGT

VFR / Helicopter Ops VFR • SVFR • Helicopter

Departure Routes:
  • Westbound: route via 10 NM west of VEGT, climb to 1000 ft.
  • Eastbound: route via 10 NM east of VEGT, climb to 1000 ft.
Arrival Procedure:
  • Route inbound via 10 NM east or west of VEGT.
  • APP passes the “10-mile check” to TWR.
  • RWY 02 restriction: due to surrounding hills, helicopters must not orbit on base leg; only downwind orbits are permitted.
Landing on Runway:
No dedicated civil helipad on AAI side. All helicopters land on the RWY at a point specified by the controller.
  • Prefer landing behind a backtracking aircraft, not in front.
  • If that’s not possible, use published dumbbell points (e.g. RWY 02 dumbbell).

Landing & Missed Approach Landing • Go-Around • Separation

Landing Clearance (Para 17.5):
A departure may start the take-off roll when the arrival is at least 4 NM from touchdown. Landing clearance for the arrival should normally be given no later than 2 NM final.
Controller-initiated Missed Approach (Para 17.6):
If the departure has not started the take-off roll by the time the arrival reaches the defined separation point (4 NM etc.), then:
  1. Cancel the take-off clearance for the departure.
  2. Instruct the arrival to go-around.
Contingency (Non-SDD environment):
  • RWY 02: use 4 ILS-DME or 7 VOR-DME as the trigger point
  • RWY 20: use 3 VOR-DME as the trigger point

Non-RNAV Departures Non-RNAV • Departure • Vector

Surface Movement Control (SMC) confirms whether an aircraft can fly the published RNAV SID. If not RNAV: Tower issues the appropriate standard instructions unless Approach has given a different specific heading/level.
Standard departure instructions:
Runway / Turn Climb / Heading / Level
RWY 02 LEFT TURN “Climb straight ahead 3000 ft, turn left heading 290, climb to 7000 ft. Request level change with RADAR.”
RWY 02 RIGHT TURN “Climb straight ahead 3000 ft, turn right heading 060, climb to 7000 ft. Request level change with RADAR.”
RWY 20 LEFT TURN “Turn left, climb on track 7000 ft. Request level change with RADAR.”
RWY 20 RIGHT TURN “Turn right, climb on track 7000 ft. Request level change with RADAR.”

Aircraft Spacing Spacing • Arrival • Departure

Suggestive spacing (NM). Depends on:
  • Runway in use
  • Whether first arrival will vacate with backtrack or without backtrack
  • Taxiway used for runway vacation (if backtrack)
  • Whether a departure is inserted between two arrivals
  • Where that departure is holding
RUNWAY VACATING TAXIWAY
(WITH BACKTRACK)		 VACATING TAXIWAY
(WITHOUT BACKTRACK)		 DEPARTURE TAXIWAY
HOLDING POSITION		 SPACING (NM)
ONLY ARRIVALS DEPARTURE BETWEEN
TWO ARRIVALS
02 E, F, L3 E, F, L2 E, F, L2 12 16
02 — Any (E, F, L3, G) E, F 8 16
02 — — G 25 32
02 — — H, J — 32
20 E, F, L2 / G E, F, L3 / E, F, L2, L1 E, F, L3 / G / J, H 8 / 16 / 20 10 / 20 / 32
Notes on Spacing
  • Spacing may be reduced for intersection departures.
  • Spacing may be reduced for a succeeding slow-moving aircraft (e.g. HN74, H/C).
  • In all reduced spacing scenarios, the 4 NM controller-initiated missed approach procedure (17.6) must still be protected.
Spacing Calculator (Training Aid)

Barapani (Shillong) Ops Barapani • Shillong • Transfer

Coordination flow:
  • ACC passes ETA to Barapani ATC.
  • ACC passes estimate BPN / abeam BPN / VENUM when ≤ 9000 ft.
  • APP descends arrivals to 9000 ft.
  • APP releases arrivals clear of all conflicting traffic.
  • If sequencing is required, next release only after previous has landed.
  • Deconflict with Barapani departures as coordinated.
Cautions:
Maintain separation from known traffic including helicopters. Refer to AIP charts and LOA. In non-radar environment, the pilot is responsible for terrain clearance.

Runway Ops Runway Change • Reciprocal • Taxi/Tow

Runway Changeover (MATS-2 17.18):
  • TSO selects runway based on wind, weather, and aid availability.
  • TWR informs aircraft and agencies (after consulting APP).
  • Plan the change in advance; avoid surprise switches.
Use of Reciprocal Runway (17.18.8):
Controller shall not assign/use the reciprocal runway. Aircraft are to use only the declared runway-in-use.
Taxiing / Towing on Active RWY (17.23):
  • For taxi from TWY G to Apron I: ensure 16 NM spacing between arrivals, or 20 NM if a departure is in between.
  • For towing between Apron I ↔ Apron II: allow only when no traffic expected for next ~30 minutes; two-way comm is mandatory; conduct runway inspection after towing.

Defence Microlight Ops Microlight • IAF • Bird Hazard

IAF microlight (e.g. Virus SW-80) may be used for bird hazard and obstruction survey near the aerodrome.
Restrictions:
  • Not permitted when VIS < 1500 m
  • Allowed only from sunrise to sunset
Procedures:
  • May orbit mid-downwind or proceed to a defined survey sector.
  • Preferred western sector, left-hand circuit RWY 02.
  • Circuit/landing permitted only if Tower has visual contact with the microlight.

Radio Comm Failure (RCF) RCF • Contingency • No Comms

General:
  • It is possible that pilot's Rx is working but Tx is not.
If two-way comms fail:
  • Ask aircraft to IDENT or carry out a specified manoeuvre to confirm it’s receiving.
  • If still no positive acknowledgement: protect separation assuming RCF.
  • Track the aircraft on radar/situation display if available.
  • Inform all affected ATS units down the chain.
Quick Action Checklist (RCF):
  1. Try contact on all available frequencies / via relay aircraft.
  2. Ask aircraft to IDENT / manoeuvre for acknowledgement.
  3. Protect separation per RCF profile.
  4. Continue to monitor on the situation display.
  5. Call / inform relevant ATS units and coordinate downstream sectors.

Pushback & Taxiing Apron I • Apron II • Pushback

Stand Allotment (17.22.2):
  • Allotment handled by AOCC for scheduled flights.
  • SMC / TSO coordinate with AOCC if the planned stand is not available.
  • Aim to avoid last-minute changes.
Apron I Pushback (17.22.3):
  • Pushback is toward marked positions (X1 / X2 or Y1 / Y2).
  • Example: Stands 01–02 → push to Y1/Y2. Stands 03–07 → push South (Y1/Y2) if RWY 02 departure, push North (X1/X2) if RWY 20 departure. Stands 08–09 → push North (X2/X1).
Apron II Taxi (17.22.3):
  • Taxi-in Stands 21–26: TWY G & H
  • Taxi-in Stands 27–31: TWY G & J
  • Taxi-out Stands 21–26: TWY H/J & G
  • Taxi-out Stands 27–31: TWY J & G
Apron I Restrictions (17.22.4):
  • If B739/A320/A321 is holding at TWY E or F, nobody should taxi behind it.
  • Pushback at Y1 blocks stands 4–5.
  • Pushback at X2 blocks stands 5–6.

Special Ops Laser • Drone / RPAS • Unlawful Interference

Laser Beam / Non-Aeronautical Lights (17.24):
Follow the published SOP for laser / light interference at LGBI. Controllers must treat reported laser illumination as a safety event and capture details for report.
RPAS / UAV / Drone Operations (17.25):
Follow the RPAS / Drone SOP for LGBI Airport. This covers local approvals, altitude blocks, and how to warn traffic in the vicinity.
Unlawful Interference (17.26):
Follow the Anti-Hijacking Contingency Plan and the ATCO SOP for acts of unlawful interference. Treat immediately as emergency priority.