ATC LOCAL PROCEDURES
MUMBAI FIR


GENERAL FREQUENCIES
Position Sector Callsign Frequency
Center North  VABF_N_CTR  132.700
South  VABF_S_CTR      125.350 **
** Will be opened depending of traffic
SQUAWK CODES
International Domestic
0300-0377
0473-0477
0240-0277
2671-2677
3300-3310
6300-6351

SECTOR FILE
Download here
The sector file is for all India.
Author: Sanjay Dutt
CHARTS
Due to copyright reasons, we can't publish the charts here. Anyway you can download the charts clicking here (AIP-MAP India).

Mumbai Airport - Chhatrapati Shivaji Intl - VABB/BOM

Local frequencies

Position Sector Callsign Frequency
Delivery  VABB_DEL  121.850
Ground  VABB_GND  121.900
Tower  VABB_TWR  118.100
 Approach  North  VABB_N_APP  127.900
South  VABB_S_APP  120.500
 Departure   VABB_DEP  119.300

Runways

Primary runway (09/27) available for takeoff and landing operations.
Secondary runway (14/32) available for landings ONLY.

SIDs

Here's an extract of only the importants SIDs for runway 27.

NORTHBOUND
Runway Name Identifier Transition
27   APANO   1A BVR
1B BODAR
1C SASRO
1D AAE
1E QQZ
SOUTHBOUND
Runway Name Identifier Transition
27   KABSO   1 GGO
  DARMI   DOMON
  ERVIS   ENKAR
  EPKOS   1A BBI
1B BBM
WESTBOUND
Runway Name Identifier Transition
27   BIMOT   1A BIDIX
1B SUGID
  BISET   1 ALGIS
EASTBOUND
Runway Name Identifier Transition
27   OPAKA   1A AAU
1B IBELA
1C APUSU
DOGAP 1 PUN
POSIN 1 IID
AAU 1 MIMAN

In case a SID does not exist for a particular runway, then give the name of the first outbound waypoint as vectors.
For example: AIC101, cleared to EGLL via vectors to EXOLU then as filed, climb FL070, sq 0300.

Position Working

Clearance Delivery

    All aircrafts to be handled on first come first serve basis. Make short clearances giving only the destination, SID or vectors, FL and squawk. Change them over to ground control as soon as clearance is issued. In conjunction with ground, commence gate hold procedure. This begins when there are more than 8 aircrafts waiting in queue for take-off.

Ground

    Aircrafts to be given taxi via taxiways to the active runway. Due to the existing wind conditions throughout the year, runway 27 is the primary runway used for takeoffs and landings. Only when the tailwind component increases to more than 10kts, operations from runway 09 begin. Hence, all aircrafts to be taxied to runway 27 for departure.

Tower

    Responsible for both runways. Use runway 27 for landing and takeoff and runway 14 for arrivals ONLY. Hand off departing traffic to approach immediately after takeoff. Handoff to ground control when the aircraft is clear of the active runway.

Approach

North Sector - VABB_N_APP - 127.900

    Mumbai North approach is responsible for all landing traffic onto runway 14. It accepts all traffic coming in from the west and north and guides them to SAMUD or MANDI entry points. In the sequence, the aircrafts are then vectored for ILS runway 14. Once established on ILS, hand them over to tower control.

South Sector - VABB_S_APP - 120.500

    Mumbai South approach is responsible for all landing traffic onto runway 27. It accepts all traffic coming in from the east and south quadrants and guides them to SHABA or KALAM entry points. In the sequence, vector each aircraft for ILS runway 27 .Once established on ILS, hand them over to tower control.

COORDINATION BETWEEN THE 2 APPROACHES

    Due to the unique nature of both the runways crossing each other, coordination for landing traffic on both runways is very important. Clearance to an aircraft will be given by either approach only after confirmation with the other. Use standard phrases in chat for this:

South approach -> BAW45. (means who app has cleared this aircraft for ILS)
North approach -> Standing by.
South approach -> Clear. (means BAW45 is 5 miles to touchdown)
North approach -> JAL101. (means who app has now cleared this aircraft for ILS)
South approach -> Standing by.

P.S.: We suggest the use of IVAO Intercom, when in this cases.

Departure

    All departing traffic will be handed over to you immediately on takeoff. All aircrafts will follow the SID allotted to them and climb initially to FL70. Monitor the lateral route and guide the aircraft by Vectors in case of crossing incoming traffic via quadrantal sectors like NW, SE etc and then join them back to their enroute plan.

Speed Control Procedures in the provision of Radar Control Service (Approach and Departure)

    All arriving aircraft below 10000 ft (FL100) shall maintain IAS MAX 250kt.
Arriving aircraft below 10000 ft (FL100) and between 30nm and 15nm to Bombay VOR (BBB) shall maintain 220kt or less.
Arriving aircraft within 15nm of BBB VOR shall maintain 170kt excluding final approach track and 150kt from 10nm to 4nm on final approach track.

Center

    Mumbai Center extends from FL150 to FL410 inclusive, from the FIR boundary to 50 miles to the Mumbai airport. It is divided into two sectors:


Mumbai North Centre ( VABF_N_CTR): Manages traffic NORTH of the extended east/west centreline of rwy 27.

Mumbai South Centre (VABF_S_CTR): Manages traffic SOUTH og the extended east/west centreline of rwy 27.

Incoming aircraft to follow flight plan till 50 DME BBB then to be routed to one of the arrival gates as shown above. Hand them over to approach at FL 150. Incase of heavy traffic , approach make ask you to hold handover for a while , during which you must keep the aircraft above FL 140 at all times. Make them hold at a suitable distance till approach is ready to accept them. If possible it would be nice to let the aircraft know about his arrival sequence. Say if an aircraft is no. 8 to land, then it should take him 8 * 3 =24 mins approx to land.


VABB_CTR is responsible for the sequencing of arrival afts into one stream via the gates with adequate spacing before releasing them to approach controller. For each arrival stream , an adequate spacing of 10 nms in-trail must be provided.

Important Note: Mumbai Center provide Oceanic Control, servicing on Ocean as a FSS (non-radar control), using High Frequency (HF) radio and SELCAL calls. On IVAO India, this is not simulated yet.


© IVAO India
Prepared by: Rohit Dalaya
Revised by: Filipe Fonseca