Professional Documents
Culture Documents
ATC Pages India
ATC Pages India
Converted Meteorological Visibility (CMV) Table 1 must not be applied for Take-off or any other
A value equivalent to an RVR which is derived from required RVR minimum less than 800m or when
the reported meteorological visibility, as converted in reported RVR is available.
accordance with the specified requirements in the NOTE: If the RVR is reported at being above the maxi-
CAR. mum value assessed by the aerodrome operator,e.g.:
“RVR more than 1500m”, it is not considered to be a
AOM are generally expressed in RVR or CMV. If
reported RVR in this context and the conversion table
only meteorological visibility is reported, the charted
may be used.
RVR/CMV value can be substituted by reported mete-
orological VIS for Straight-in Instrument Approaches Jeppesen will publish all RVR values above 2000m as
as shown in Table 1. CMV, except for NDB procedures, where State Min-
ima requires VIS.
EXAMPLE: Reported VIS 600M Day (HIALS and HIRL in use): RVR/CMV = 600m x 1.5 = 900m
Day (No lighting): RVR/CMV = 600m x 1.0 = 600m
Night (HIALS and HIRL in use): RVR/CMV = 600m x 2.0 = 1200m
d. For the same indicated air speed (IAS), the true f. Arriving aircraft would prefer to fly in clean con-
speed of aircraft will vary with altitude. A table figuration for as long as circumstances permit.
representing indicated air speed versus true air Below 10000ft AMSL, speed not less than 210Kt
speed at different altitude is provided in table IAS is considered as minimum speed of turbojet
“Indicated Airspeed (IAS) vs. True Airspeed aircraft in clean configuration.
(TAS) at different altitude at ISA +15°C”. Radar g. Speed adjustments requiring alternate
controllers must be aware of speed differentials decrease and increase shall be avoided partic-
between IAS and TAS. ularly after the aircraft has reduced the speed
e. Simultaneous speed reduction and descent can below 210kt. In such cases the Phraseology”,
be extremely difficult, particularly for turbojet air- No ATC speed restriction”, or “Resume normal
craft. It may be necessary for the pilot to level off speed” shall only be used.
temporarily and reduce speed prior to descend-
ing below 10000ft AMSL.
approach clearance
is issued, speed
restrictions shall
remain applicable
unless withdrawn by
ATC
Within 5NM from N/A N/A N/A
touch-down
NOTE: Subject to aircraft performance limitations a
radar controller may assign a specific speed to the
aircraft in order to maintain/achieve required spacing.
q$z
q$z
ADS/CPDLC WITHIN MUMBAI FIR d. Pilots unable to establish data link connection
ADS/CPDLC system is available within Mumbai FIR shall inform appropriate ATS unit through voice
on segments of ATS routes A474, B459, G424, G450, communication on 132.45/120.7/120.1/126.1
G465, L301, L505, L894, M300, N519, N563, N571, and 125.9MHz or HF on 2947/10066/2872/
N628, P323, P570, P574, P751, R461, T940, UL425, 5580/6583/8861/8906/2923/6484/10051/6556
UM551 over Arabian Sea Oceanic Airspace. and 3491kHz.
e. ADS will be the primary means of surveillance
The service is available to all aircraft suitably
for suitably equipped and data link established
equipped with data link capability. The ADS/CPDLC
aircraft outside control areas on above routes
service will not affect the current procedures for non
and voice position reporting will be a backup.
data link capable aircraft operating within Mumbai
FIR. The data link capable aircraft while operating in f. CPDLC will be the primary means of communi-
Mumbai FIR shall follow procedures as given below. cation outside control areas and VHF/HF RTF
will be a backup.
a. Data link and ADS capability shall be indicated
in the FPL by indicating appropriate designator g. SELCAL checking is required to verify the RTF
in item 10 and 18. serviceability.
b. The logon address of Mumbai FIR is VABF. h. Pilots recognizing failure of data link commu-
nication shall immediately establish commu-
c. The arriving aircraft shall logon 10 min prior to
nication using appropriate voice frequency.
entering Mumbai FIR.
The voice communication shall continue until
Aircraft departing/transiting from/within Mumbai CPDLC connection is re-established and the
FIR shall login within 15 min prior to leaving the controller has authorized to return to data link
Mumbai TMA limits. communication.
d. CPDLC will be the primary means of commu-
nication and VHF/HF will be secondary means ADS/CPDLC WITHIN CHENNAI FIR
of communication for the aircraft successfully New ATM Automation system is available in shadow
logged on to ADS/CPDLC when operating in mode. The logon address for the new Automation
Mumbai OCC. system is VOMM. FANS 1/A equipped aircraft oper-
During the period when aircraft is logged on to ating within Chennai FIR over Bay of Bengal Oceanic
ADS/CPDLC, voice position reporting will be to Airspace on ATS routes B466E, L645, N563, N571,
supplement CPDLC position report only when N877, P574, P628, P761, P762, and L645 desiring
requested by ATC. Data-Link service are required to logon to the address
VOMM and VOMF. CPDLC will be available only with
e. Selcal checking is required to verify the HF/RT AFN logon address VOMM.
connectivity.
f. Voice Positioning shall be resumed in case New ATM Automation system is available to all FANS
of ADS/CPDLC link failure. Pilots unable to 1/A equipped aircraft operating in the Arabian Sea
establish Data Link Connection shall inform and Indian Oceanic airspaces within Chennai FIR on
appropriate ATS unit through voice com- ATS routes G325, M300, M641, N640, P570, UL425,
munication on VHF 132.7 and 125.35MHz, R429 and R461 as a backup to Chennai UACC freq
or HF 10018/13288/10084/5658/5601/3467/ 134.425 and 132.5MHz. The AFN logon address
6661/4675/3443/8879/5634/3476/4657 and is VOMM. HF frequencies shall also continue to be
2872kHz. available.
The introduction of ADS/CPDLC service will not affect
ADS/CPDLC WITHIN KOLKATA FIR
the current procedure for non-data link capable air-
This service is available to all aircraft suitably craft. The data link capable aircraft while operating on
equipped with Data Link capability on ATS routes the above routes shall follow procedures given below:
G472, L301, L507, L759, M770, N877, N895, P628
a. Data and ADS capability shall be indicated in the
and P646 over oceanic airspace in Bay of Bengal.
FPL inserting appropriate designators in item 10
The introduction of ADS/CPDLC service will not affect and 18.
the current procedure for non-data link capable air- b. The aircraft shall logon 10min prior to entering
craft. The data link capable aircraft while operating on the FIR.
the above routes shall follow procedures given below:
c. Pilots unable to establish data link connection
a. Data and ADS capability shall be indicated in the shall inform appropriate ATS unit through voice
FPL inserting appropriate designators in item 10 communication on 118.9/125.7/126.15/132.5
and 18. and 134.425MHz or HF on 3470/6655/11285/
b. The logon address of Kolkata FIR is VECF. 17907 and 13318kHz.
c. The aircraft shall logon 10min prior to entering d. ADS will be the primary means of surveillance
the FIR. For aircraft exiting Kolkata FIR, Next for suitably equipped and data link established
Data Authority (NDA) will be notified via CPDLC aircraft outside control areas on above routes
20 minutes prior to crossing FIR boundary. and voice position reporting will be a backup.
Transfer of communication shall be completed e. CPDLC will be the primary means of communi-
at the FIR boundary. cation outside control areas and VHF/HF RTF
will be a backup.
q$z
f. SELCAL checking is required to verify the RTF W70, W71N/S, W72, W81, W88, W91, W96, W98,
serviceability. W101E/W, W104, W116, W117, W118N/S, W119,
g. Pilots recognizing failure of data link commu- W121, W218.
nication shall immediately establish commu- REQUIRED NAVIGATION PERFORMANCE
nication using appropriate voice frequency.
The voice communication shall continue until 80NM Longitudinal Separation
CPDLC connection is re-established and the Longitudinal separation minima of 80NM RNAV or
controller has authorized to return to data link 10 minutes based on MNT is applied between air-
communication. craft equipped in accordance with RNP 10 navigation
requirements: L333, L505, L516, L626, L645, L760,
ADS/CPDLC WITHIN DELHI FIR
L896, M638, M773, M875, M890, N519, N564, N571,
ADS/CPDLC System is available within Delhi FIR on N893, P323, P518, P761, P762.
segments of ATS routes A466, A589, G333, G452,
L333, L509, M875, M890, W30, W31, W34, W36, 50NM Longitudinal Separation
W39. The service is available to all acft suitably Longitudinal separation minima of 50NM RNAV or 10
equipped with data link capability. The ADS/CPDLC minutes is applied between aircraft approved for RNP
service will not affect the current procedure for non 10 operations on those segments of following routes:
data link capable acft operating within Delhi FIR. The – L301 - (RINDA - RASKI);
data link capable acft while operating in Delhi FIR
– L507 - (TEBOV - CEA);
shall follow procedures as given below:
– L509 - (GGC - ASARI);
a. Data link and ADS capability shall be indicated
in the FPL by indicating appropriate designators – L510 - (EMRAN - IBANI);
in item 10 and 18. – L759 - (MIPAK - DPN);
b. The logon address of Delhi is VIDF. – M300 - (ATETA - LOTAV);
c. The arriving acft shall logon 20 minutes prior – M770 - (MEPEL - JJS);
to entering Delhi FIR and in case flying time to – N563 - (MEMAK - REXOD);
Delhi FIR is less than 20 minutes, immediately
– N571 - (IGOGU - PARAR W-bound, PARAR -
after departure.
IDASO E-bound);
d. Acft departing from aerodromes within Delhi FIR
– N877 - (LAGOG - PRA);
shall logon immediately after departure.
– N895 - (SAGOD - PARTY);
e. Aircraft departing/transiting from/within Delhi
FIR shall logon next data authority 15 minutes – P570 - (BASUR - KITAL);
prior to leaving the Delhi TMA limits. – P574- (NOPEK - TOTOX);
f. Position reporting requirement to communicate – P628 - (IGREX - VIKIT);
with ATC units on VHF/HF remain unchanged. – P646 - (IBITA - BBN);
g. SELCAL checking is required to verify the HFRT – P762 - (DUGOS - LULDA).
connectivity.
An aircraft that is unable to meet the minimum navi-
h. Pilots unable to establish Data link connection gational requirements for RNP 10 must file flight plan
shall inform appropriate ATS unit through voice at or below minimum flight level of the route. How-
communication on VHF. ever operations of these aircraft will be subject to
MACH NUMBER TECHNIQUE ATC approval, in accordance with the provisions men-
tioned below, if not approved will be required to file a
The MNT with 10 minutes longitudinal separation flight plan to operate via alternate route.
between aircraft may be applied to aircraft meeting
RNAV criteria on the same track whether in flight ATC units receiving a request for a non-RNP 10
level, climbing or descending on the following routes: approved aircraft to operate on ATS routes N571
(IGOGU - PARAR W-bound, PARAR - IDASO
A201, A347, A465, A466, A474, A589, A599, B465, E-bound) at or above FL280 and P762 (DUGOS
B593, G210, G463, G472, R325, R458, R460, R461, - LULDA) at or above FL260, will coordinate with
R472, R594, UL425, W92, W93, W103, W122N/S, adjacent ATC units affected by the flight.
W123, W124.
STRATEGIC LATERAL OFFSET
LONGITUDINAL SEPARATION
PROCEDURES (SLOP)
A minimum longitudinal separation of 10 minutes
The following basic requirements apply to the use of
shall apply between aircraft flying at the same level
the Strategic Lateral Offset Procedures (SLOP):
and in the same direction and climbing descending
through the level of another aircraft flying in the same a. Strategic Lateral Offset Procedures shall be
direction on following ATS routes: applied only by aircraft with automatic offset
tracking capability.
A325, A462, A791, B345, G208, G333, G335, G336,
b. The decision to apply a strategic offset is the
G348, G451, G452, G590, G598, R344, R580, R598,
responsibility of the flight crew.
W13N/S, W15N/S, W17S/N, W18, W19, W20N/S,
W25, W26, W27, W28, W29, W38, W41, W42N/S, c. The offset shall be established at a distance of
W43N/S, W44, W45, W46, W47N/S, W49, W57N/S, 1 or 2 NM to the RIGHT of the centerline of the
ATS route relative to the direction of flight.
q$z
d. The offsets shall not exceed 2 NM right of the MUMBAI FIR (continued)
centerline of the ATS route. M638 NOBAT SAPNA
e. The Strategic Lateral Offset Procedure has A451 BISET ANGAL
been designed to include offsets to mitigate the DARMI
G450 DOGOD
effects of wake turbulence of preceding aircraft.
If wake turbulence needs to be avoided, one of UM551 DONSA ANGAL
the three available options (centerline, 1 NM or B459 GUNDI UBDOR
2NM right offset) shall be used. A474 ERVIS POPET
f. In airspace where the use of lateral offsets has R456 BIBGO KITAL
been authorized, pilots are not required to inform
P323 DONSA GIDAS
ATC that an offset is being applied.
G424 ALATO LADUP
g. Aircraft transiting areas of radar coverage in
airspace where offset tracking is permitted may
initiate or continue an offset. ENROUTE OPERATIONS
h. Aircraft without automatic offset tracking capa- Flying outside of ATS routes is prohibited within
bility must fly the centerline of the ATS route Indian airspace.
being flown. All flights entering, leaving or crossing the territory
The segments of ATS routes where Strategic Lateral of India are required to follow the ATS routes estab-
Offset Procedures are applicable are identified in the lished for international operations (For exceptions see
tables below. However for ATC purposes the offset FLIGHT PLANNING below).
may be cancelled by the appropriate ATC unit. PPR for connector routes
CHENNAI FIR Prior permission required by airlines to fly ATS con-
nector routes (V012, V013, V014, V015, V016, V017,
L645 SAMAK SULTO V018, V019, V020 and V021) between Mumbai FIR
N563 MEMAK AKMIL and Male FIR from the ATS provider at least one week
P574 NOPAK MMV VOR in advance.
N571 IGOGU GURAS NOTE: Aircraft operating on these connector routes
N877 LAGOG ORARA shall be ADS/CPDLC equipped.
P628 IGREX VATLA Contact details:
L759 MIPAK NISUN Mumbai Watch Supervisory Officer (WSO)
Tel: +91 22 26828088
P762 LULDA DUGOS
Fax: +91 22 26828066
UL425 TVM VOR ANODA E-Mail: wsomum@aai.aero
P570 TVM VOR POMAN
General Manager (ATM), Mumbai
M300 CLC VOR IGAMA Tel: +91 22 26828010
Fax: +91 22 26828010
KOLKATA FIR E-Mail: gmatmmum@aai.aero
N877 ORARA VVZ VOR FLIGHT PLANNING
L301 RINDA VVZ VOR Scheduled international flights are permitted to
P628 VATLA LARIK flight plan using domestic ATS routes segments
L759 LIBDI LEMAX to/from destination, departure and approved alter-
nate airports in India which are not connected by
M770 MEPEL KAKID
international ATS route.
M773 BUBKO LEGOS
N895 SAGOD BBS VOR ACAS II/TCAS II REQUIREMENTS
P646 IBITA DOPID Unless otherwise authorized by DGCA, no person
shall acquire for the purpose of operation:
L507 TEBOV CEA VOR
a. an aircraft having a maximum certified passen-
ger seating configuration of 20 to 30 or a max-
MUMBAI FIR
imum certified take-off mass of 5700kg, if such
UL425 ANODA ASPUX aircraft is not equipped with an approved ACAS
P570 POMAN KITAL II.
M300 IGAMA LOTAV b. an aircraft having a maximum certified passen-
ger seating configuration of 10 to 19 or a maxi-
N563 KAKIB REXOD
mum certified take-off mass of less than 5700kg,
P574 OKILA TOTOX if such aircraft is not equipped with approved
N571 crossing 072 deg PARAR ACAS I.
East
L505 EXOLU NOBAT
L301 AKTIV RASKI
q$z
q$z