25 OCT 13 AIR TRAFFIC CONTROL INDIA-1 q$i

INDIA - RULES AND PROCEDURES

GENERAL Jeppesen published minimums are not below
In general, the air traffic rules and procedures in force State minimums.
and the organization of the air traffic services are Approach Lighting Systems
in conformity with ICAO Standards, Recommended
FALS (Full Approach Light System) — Precision
Practices and Procedures.
approach CAT I lighting system (HIALS 720m and
Units of measurement used in all air and ground oper- more), distance coded centreline, barrette centreline.
ations are as listed in the following table. IALS (Intermediate Approach Light System) —
Simple approach lighting system (HIALS 420 –
MEASUREMENT OF UNIT 719m), single source barrette.
Distance used in Nautical Miles and BALS (Basic Approach Light System) — Any other
navigation, position Tenths approach lighting system (HIALS, MIALS or ALS 210
reporting, etc., generally – 419m).
in excess of 2 nautical
miles NALS (No Approach Light System) — Any other
approach lighting system (HIALS, MIALS, or ALS less
Relatively short Meters than 210m) or no approach lights.
distances such as those
relating to aerodromes Continuous Descent Final Approach (CDFA)
(e.g., runway lengths) A technique, consistent with stabilized approach pro-
Altitude, elevations, and Feet cedures, for flying the final approach segment of a
heights non-precision approach procedure as a continuous
Horizontal speed Knots descent, without level-off, from an altitude/height at or
including wind speed above the final approach fix altitude/height to a point
approximately 50ft above the landing runway thresh-
Vertical speed Feet per Minute old or the point where the flare manoeuvre should
Wind direction for landing Degrees Magnetic begin for the type of aircraft flown.
and take-off
All non-precision approaches shall be flown
Visibility including Kilometers or Meters using the Continuous Descent Final Approach
runway visual range technique unless otherwise approved by the
Altimeter setting Hectopascals DGCA for a particular approach to a particular
Temperature Degrees Celsius runway.
Weight Metric Tons or Kilograms When calculating the minimums the operator shall
Time Hours and minutes, ensure that the applicable minimum RVR is increased
beginning at midnight by 200m for CAT A/B aircraft and by 400m for CAT
UTC C/D aircraft for approaches not flown using the CDFA
technique, providing that the resulting RVR/CMV
WGS-84 IMPLEMENTATION STATUS value does not exceed 5000m.
WGS-84 compliant. Jeppesen charted non-precision RVR values not
labelled as CDFA, already take these increments into
FLIGHT PROCEDURES account.
HOLDING In case of the application of the CDFA technique,
Holding procedures comply with Jeppesen on many procedures the Derived Decision Alti-
ATC-Chapter “Flight Procedures (DOC 8168) - tude (DDA) may be used (as given in Ops Circular
Holding Procedures”, Table IV-1-1, Holding Speeds. 1/2005). Flight crews should add a prescribed
altitude increment of minimum 50ft to the pub-
PROCEDURE LIMITATIONS AND OPTIONS lished MDA(H) to determine the altitude at which
Instrument approach procedures are in accordance the missed approach should be initiated in order
with PANS-OPS, Document 8168. to prevent a descent below the MDA(H). There is
no need to increase the RVR/VIS for that approach.
AIRPORT OPERATING MINIMUMS Any turning manoeuvre associated with the missed
India publishes State Airport Operating Minimums approach should be initiated not earlier than the
(AOM) classified as either Normal AOM or Restricted MAP.
AOM. Normal AOM are for use by scheduled
Indian and International airline operators only and The Jeppesen charted MDA(H) is the minimum value
Restricted AOM are to be used by all other operators based on the procedure’s OCA(H) and the system
who have not applied for, or have not yet received minima as described below. It should be used when
approval for Normal AOM. adding the increment to determine the DDA accor-
ding to Ops Circular 1/2005.
The following paragraphs comprise existing Indian
provisions based on Civil Aviation Requirement Converted Meteorological Visibility (CMV)
(CAR) (Section 8, Series C, Part I) on All Weather A value equivalent to an RVR which is derived from
Operations regarding the methods to determine the reported meteorological VIS, as converted in
AOM. The regulations have to be adhered to by accordance with the specified requirements in the
pilots and all aircraft operators at Indian airports. CAR.

q$z

© JEPPESEN, 1991, 2013. ALL RIGHTS RESERVED.

 INDIA-2 AIR TRAFFIC CONTROL 25 OCT 13

INDIA - RULES AND PROCEDURES q$i

Table 1 must not be applied for Take-off or any other Jeppesen will publish only RVR values, except where
required RVR minimum less than 800m or when CMV or VIS values are published by the State as part
reported RVR is available. of the AOM.
NOTE: If the RVR is reported at being above the max-
imum value assessed by the airport operator, e.g.
“RVR more than 1500m”, it is not considered to be
a reported value for the purpose of this paragraph.

Table 1 Conversion of Reported MET VIS to CMV

CMV = Reported MET VIS x
Lighting Elements in Operation
Day Night
HIALS and HIRL 1.5 2.0
Any type of lighting installation
1.0 1.5
other than above
No lighting 1.0 Not applicable

EXAMPLE: Reported VIS 600M Day (HIALS and HIRL in use): CMV = 600m x 1.5 = 900m
Day (No lighting): CMV = 600m x 1.0 = 600m
Night (HIALS and HIRL in use): CMV = 600m x 2.0 = 1200m

Normal AOM Foreign operators are to be authorized by the State of

Normal AOM are for the use of scheduled operators.
An operator shall establish, for each airport planned
to be used, airport operating minimums. The method
of determination of such minimums must be approved
by the DGCA and shall be consistent with the pro-
vision of CAR and ICAO Doc 9365 (Manual of All
Weather Operations). Such minimums shall not be
lower than any that may be established for such air-
ports by the State of the airport, except when specif-
ically approved by the State of the airport.
the operator for the use of AOM. In no case may they
operate at Indian Airports at less than the Normal
AOM.
The Jeppesen charted minimums on approach and
airport charts are Normal AOM.
CAT I Precision, APV and Non-precision
Approaches
Decision Height (DH) and Minimum Descent
Height (MDH)

Table 2 System Minima vs Instrument Approach Procedures

Instrument Approach Procedure Lowest DH/MDH
ILS/MLS/GLS CAT I 200ft
RNAV (LNAV/VNAV) with approved vertical guidance 200ft
LOC, LOC DME 250ft
SRA (terminating at ½nm) 250ft
SRA (terminating at 1nm) 300ft
SRA (terminating at 2nm) 350ft
RNAV (LNAV) without approved vertical guidance 300ft
VOR 300ft
VOR DME 250ft
NDB 350ft
NDB DME 300ft
VDF 350ft
NOTE: A lowest DH of 200ft for RNAV with approved RVR
vertical guidance approaches shall only be used if full The minimum RVR shall be the highest of the values
SBAS capability is available. Otherwise a DH of 250ft derived from Table 3 and Table 4, but not greater than
is required. the maximum values shown in Table 4 where applica-
ble.

Table 3 Lowest Straight-in Approach Minimums for Instrument Approach and Landing
Operations other than CAT II or CAT III
Class of Lighting Facility
DH or MDH (ft) FALS IALS BALS NALS
(metres)
200 – 210 550 750 1000 1200

q$z

© JEPPESEN, 1991, 2013. ALL RIGHTS RESERVED.

 25 OCT 13 AIR TRAFFIC CONTROL INDIA-3
INDIA - RULES AND PROCEDURES q$i

Table 3 Lowest Straight-in Approach Minimums for Instrument Approach and Landing
Operations other than CAT II or CAT III (continued)
Class of Lighting Facility
DH or MDH (ft) FALS IALS BALS NALS
(metres)
211 – 220 550 800 1000 1200
221 – 230 550 800 1000 1200
231 – 240 550 800 1000 1200
241 – 250 550 800 1000 1300
251 – 260 600 800 1100 1300
261 – 280 600 900 1100 1300
281 – 300 650 900 1200 1400
301 – 320 700 1000 1200 1400
321 – 340 800 1100 1300 1500
341 – 360 900 1200 1400 1600
361 – 380 1000 1300 1500 1700
381 – 400 1100 1400 1600 1800
401 – 420 1200 1500 1700 1900
421 – 440 1300 1600 1800 2000
441 – 460 1400 1700 1900 2100
461 – 480 1500 1800 2000 2200
481 – 500 1500 1800 2100 2300
501 – 520 1600 1900 2100 2400
521 – 540 1700 2000 2200 2400
541 – 560 1800 2100 2300 2500
561 – 580 1900 2200 2400 2600
581 – 600 2000 2300 2500 2700
601 – 620 2100 2400 2600 2800
621 – 640 2200 2500 2700 2900
641 – 660 2300 2600 2800 3000
661 – 680 2400 2700 2900 3100
681 – 700 2500 2800 3000 3200
701 – 720 2600 2900 3100 3300
721 – 740 2700 3000 3200 3400
741 – 760 2700 3000 3300 3500
761 – 800 2900 3200 3400 3600
801 – 850 3100 3400 3600 3800
851 – 900 3300 3600 3800 4000
901 – 950 3600 3900 4100 4300
951 – 1000 3800 4100 4300 4500
1001 – 1100 4100 4400 4600 4900
1101 – 1200 4600 4900 5000 5000
1201 and above 5000 5000 5000 5000

Table 4 Minimum and Maximum RVR for Instrument Approaches down to CAT I Minimums
Aircraft Category
Facility/Conditions RVR/CMV (m)
A B C D
ILS/MLS/GLS, PAR, and Min According to Table 3
RNAV with approved vertical Max 1500 1500 2400 2400
guidance

q$z

© JEPPESEN, 1991, 2013. ALL RIGHTS RESERVED.

 INDIA-4 AIR TRAFFIC CONTROL 25 OCT 13

INDIA - RULES AND PROCEDURES q$i

Table 4 Minimum and Maximum RVR for Instrument Approaches down to CAT I Minimums (continued)
Aircraft Category
Facility/Conditions RVR/CMV (m)
A B C D
NDB, NDB/DME, VOR, Min 750 750 750 750
VOR/DME, LOC, LOC/DME, Max 1500 1500 2400 2400
VDF, SRA, RNAV without
approved vertical guidance
with a procedure which fulfills
the criteria in paragraph
11.3.8(b)
For NDB, NDB/DME, VOR, Min 1000 1000 1200 1200
VOR/DME, LOC, LOC/DME, Max According to Table 3, if flown using the CDFA technique,
VDF, SRA, RNAV without otherwise an add-on of 200/400m applies to the values in
approved vertical guidance: Table 3 but not to result in a value exceeding 5000m.
– not fulfilling the criteria in
paragraph 11.3.8(b); or
– with a DH or MDH ≥ 1200ft

Paragraph 11.3.8 Criteria b. CAT I operations to runways without runway

touchdown zone lights and runway centreline
In order to qualify for the lowest allowable values of
lights with an approved HUDLS, or equivalent
RVR as detailed in Table 3, the instrument approach
approved system, or when conducting a cou-
procedures shall meet at least the following facility
pled approach or flight-director-flown approach
requirements and associated conditions:
to the DH; or
a. Instrument approach procedures with a desig-
c. RNAV with approved vertical guidance
nated vertical profile up to and including 4.5°
approach procedures to runways with FALS,
for CAT A and B aircraft, or 3.77° for CAT C
runway touchdown zone lights and runway cen-
and D aircraft, unless other approach angles are
treline lights when using an approved HUD.
approved by DGCA, where the facilities are:
1. ILS/MLS/GLS/PAR; or CAT II Precision Approaches
2. RNAV with approved vertical guidance; Decision Height (DH)
and where the final approach track is off- The decision height must not be lower than:
set by not more than 15° for CAT A and B
– the minimum decision height specified in the AFM;
aircraft or by not more than 5° for CAT C
or
and D aircraft.
– the minimum height to which the precision
b. Instrument approach procedures flown using
approach aid can be used without the required
the CDFA technique with a nominal vertical
visual reference; or
profile up to and including 4.5° for CAT A and
B aircraft, or 3.77° for CAT C and D aircraft, – the OCH; or
unless other approach angles are approved by – the decision height to which the flight crew is
DGCA, where the facilities are NDB, NDB/DME, authorized to operate; or
VOR, VOR/DME, LOC, LOC/DME, VDF, SRA – 100ft
or RNAV(LNAV), with a final approach segment
whichever is higher.
of at least 3NM, which also fulfill the following
criteria: RVR
1. the final approach track is offset by not
Table 5 RVR for CAT II Operations
more than 15° for CAT A and B aircraft or
by not more than 5° for CAT C and D air- Decision RVR for CAT
RVR CAT D
craft; and Height A, B & C
2. the FAF or another appropriate fix where 100ft – 120ft 300m 300m/350m1
descent is initiated is available, or distance 121ft – 140ft 400m 400m
to THR is available by FMS/RNAV or DME; 450m 450m
141ft – 199ft
and
3. if the MAPt is determined by timing, the dis-
1 For CAT D aircraft conducting an autoland, RVR
300m may be used.
tance from FAF to THR is less than 8NM.
An RVR as low as 550m as indicated in Table 3 may CAT III Precision Approaches
be used for: The lowest minima to be used by an operator for CAT
a. CAT I operations to runways with FALS, run- III operations depend on the decision height and air-
way touchdown zone lights and runway centre- craft systems as shown in Table 6 below.
line lights; or

q$z

© JEPPESEN, 1991, 2013. ALL RIGHTS RESERVED.

 25 OCT 13 AIR TRAFFIC CONTROL INDIA-5
INDIA - RULES AND PROCEDURES q$i

Table 6 RVR for CAT III Operations

Roll-out Control/
Category Decision Height RVR
Guidance System
IIIA Less than 100ft Not required 175m
IIIB Less than 100ft Fail-passive 150m
IIIB Less than 50ft Fail-passive 125m
IIIB Less than 50ft or no DH Fail-operational 50m

The fail-operational system referred to may consist of
a fail operational hybrid system.
Circling Approach
Circling approach and associated minimums will be
authorized for operators by Flight Standards Direc-
torate as per the training programme implemented by
the operator.
Visual Approach
For a visual approach, an operator shall use the
higher of the associated non-precision approach
minimum or 2800m for CAT A & B, 3200m for CAT
C and 3600m for CAT D aircraft. If visual approach
is requested for a runway which has only a circling
approach, the ground visibility shall not be less than
5km.
Take-off
Take-off minimums established by the operator must
be expressed as VIS or RVR, taking into account all
relevant factors for each airport planned to be used.
Where there is a specific need to see and to avoid
obstacles a ceiling or climb gradient must be speci-
fied.
The commander shall not commence take-off unless
the weather conditions at the airport of departure are
equal to or better than applicable minimums for land-
ing at that airport unless a suitable take-off alternate
airport is available.
The take-off alternate weather (actual and forecast)
shall not be less than ILS CAT I minimums. The take-
off alternate airport should be located within the fol-
lowing distance from the airport of departure:
a. Aircraft with two engines: not more than a dis-
tance equivalent to one hour flight time at the
single engine cruise speed;
b. Aircraft with three or more engines: not more
than a distance equivalent to two hours flight
time at the one engine inoperative cruise speed.
Visual Reference
Take-off minimums must be determined to ensure
sufficient guidance to control the aircraft in case of
discontinued take-off in adverse circumstances or
during continued take-off after failure of the critical
power unit.
Required RVR/VIS
For multi-engine aircraft, whose performance is such
that in the event of a critical power unit failure at any
point during take-off the aircraft can either stop or
continue the take-off to a height of 1500ft above the
airport while clearing all obstacles by the required
margins, the take-off minimums established by an
operator must be expressed as RVR/VIS values not
lower than those in Table 7 below.
Table 7 RVR/VIS for Take-off (Commercial
Transport Aircraft)
Facilities RVR/VIS
Adequate visual reference (Day 500m
only)
Runway edge lights or runway 400m
centreline markings
Runway edge lights and runway 300m
centreline markings
Runway edge lights and runway 200m
centreline lights
Runway edge lights and runway 150m
centreline lights and relevant RVR
information
125m
High intensity runway edge lights
and runway centreline lights
(spacing 15m or less) and relevant
RVR information
NOTE 1: TDZ RVR/VIS may be assessed by the pilot.
NOTE 2: Adequate visual reference means, that the
pilot is able to continuously identify the take-off sur-
face and maintain directional control.
NOTE 3: For night operations at least runway edge
lights or centreline lights and runway end lights are
available.
NOTE 4: The required RVR must be achieved for all
relevant RVR reporting points (touchdown, mid-point
and stop-end/roll-out). The governing RVR shall be
the lowest of the reported RVRs.
Non-scheduled and general aviation operators shall
not conduct take-offs below RVR 500m.
Low Visibility Take-off Operations (LVTO)
Flight operations referring to a take-off on a runway
where the RVR is less than 400m.
Low Visibility Procedues (LVP)
Specific procedures applied at an aerodrome for
the purpose of ensuring safe operations during Cat-
egories II and III approaches and/or low visibility
take-offs.
LVTO Authorization
Use of take-off minimums less than 400m (LVTO)
requires authorization by DGCA. Scheduled opera-
tors may be authorized to LVTO minimum of 125m.
This requires that a 90m visual segment shall be
available from the cockpit at the start of the take-off
run. Foreign operators, who are authorized by their

q$z

© JEPPESEN, 1991, 2013. ALL RIGHTS RESERVED.

 INDIA-6 AIR TRAFFIC CONTROL
INDIA - RULES AND PROCEDURES
State Regulatory Authority for LVTO, shall submit req-
uisite documents to DGCA for approval of LVTO at
Indian airports.
Restricted AOM
Restricted AOM shall be based on additives applied
to the Normal AOM as below:
– Restricted DA(H) = Normal DA(H) + 100ft;
– Restricted MDA(H) = Normal MDA(H) + 100ft;
– Restricted RVR = Normal RVR + 400m.
Restricted AOM are not charted on Jeppesen
approach and airport charts. Pilots are responsible
to add the 100ft/400m increment to the charted
minima.
SPEED RESTRICTION
Speed Control Procedures under Non-radar
Environment
All aircraft (including Arrivals and Departures) operat-
ing below 10000ft to fly IAS not greater than 250KT.
All arriving aircraft operating below 10000ft within
15NM Radius of VOR/DME serving the aerodrome
to fly IAS not greater than 220KT. ATC may suspend
speed control by using the phrase “No speed restric-
tion”, when traffic conditions permit.
Speed Control Procedures in the Provision
of Radar Control Service
Purpose
In order to facilitate safe and orderly flow of arriving
air traffic within terminal area under the radar environ-
ment, aircraft shall follow the speed in specified man-
ner as provided in table “Speed Control under Radar
Environment for Arriving Aircraft” at the following air-
ports:
Ahmedabad, Bangalore (Intl), Chennai (Intl), Delhi
(Indira Gandhi Intl), Hyderabad (Rajiv Gandhi Intl),
Kolkata (Netaji Subhash Chandra Bose Intl) and
Mumbai (Chhatrapati Shivaji Intl).
Requirement of Speed Control
The speed control is applied for ATC separation pur-
poses and is mandatory in the interest of acquiring
accurate spacing.
Speed control is also necessary to achieve the
desired separation minimum or spacing between
the successive arrivals. This in turn would improve
the utilization of airspace and enhance the runway
capacity to handle more number of aircraft.
The flight crew should be aware of the provisions
specified in table “Speed Control under Radar Envi-
ronment for Arriving Aircraft” and plan the aircraft
speed accordingly.
Adherence to Speed Control Procedure
All the speed restrictions shall be complied with as
promptly as feasible and flown as accurately as pos-
sible within the limits of operational constraints.
q$z
25 OCT 13
q$i
Aircraft unable to comply with the specified speeds
must inform ATC and report minimum speed it is
able to follow. In such cases controller shall apply the
alternative method to achieve the desired spacing
between aircraft concerned.
The speeds specified in table “Speed Control under
Radar Environment for Arriving Aircraft” are within the
limits of turboprops and turbojets aircraft performance
based on the ICAO recommendations and best inter-
national practices and therefore should be accept-
able. However it is the pilot’s responsibility and pre-
rogative to refuse speed restrictions that are consid-
ered excessive or contrary to the aircraft operating
specifications.
Penalties of Non-Confirmity of Speed Control
Radar controller may remove an aircraft from the
sequence for repositioning if it is observed that air-
craft concerned is not following the speed restrictions
in the specified manner and closing-in with preceding
aircraft or slowing down unnecessarily thus disrupt-
ing the traffic flow.
Flights Exempted from Speed Control
Speed control shall not be applicable to aircraft:
a. entering or established in holding pattern;
b. encountering the turbulent weather;
c. conducting the Cat II/III operations and within
20NM from touch-down;
d. within 5NM from touch-down;
e. executing the published instrument approach
procedure until interception of final approach
track;
f. carrying VVIP; and
g. conducting priority/emergency landing.
Aircraft shall be advised as and when speed control
restriction is not applicable or no longer required.
Additional Information for Better Understanding
of Speed Control
While applying the speed control, the following infor-
mation is provided as an additional information for
controllers and pilots:
a. Speed adjustments are not achieved instan-
taneously. Aircraft configurations, altitude and
speed determine the time and distance to
accomplish the adjustments;
b. Speed control shall not be assigned to an aircraft
at or above FL390 without pilot’s consent;
c. Speed control should be expressed in multiples
of 10kt based on indicated airspeed (IAS). At
or above FL250 the adjustments should be
expressed in multiples of 0.01 Mach;
d. For the same indicated air speed (IAS), the true
speed of aircraft will vary with altitude. A table
representing indicated air speed versus true air
speed at different altitude is provided in table
“Indicated Airspeed (IAS) vs. True Airspeed
(TAS) at different altitude at ISA +15°C”. Radar
controllers must be aware of speed differentials
between IAS and TAS;
© JEPPESEN, 1991, 2013. ALL RIGHTS RESERVED.
 25 OCT 13 AIR TRAFFIC CONTROL INDIA-7
INDIA - RULES AND PROCEDURES q$i

e. Simultaneous speed reduction and descent can g. Speed
be extremely difficult, particularly for turbojet air-
craft. It may be necessary for the pilot to level off
temporarily and reduce speed prior to descend-
ing below 10000ft AMSL;
f. Arriving aircraft would prefer to fly in clean con-
figuration for as long as circumstances permit.
Below 10000ft AMSL, speed not less than 210Kt
IAS is considered as minimum speed of turbojet
aircraft in clean configuration;
adjustments requiring alternate
decrease and increase shall be avoided partic-
ularly after the aircraft has reduced the speed
below 210kt. In such cases the Phraseology”,
No ATC speed restriction”, or “Resume normal
speed” shall only be used.

Speed Control under Radar Environment for Arriving Aircraft

IAS
Phase of Flight Status Remarks
Turboprop Turbojet
Enroute and initial N/A 250KT or actual Optional/as per Speed less than
descent up to FL290 speed whichever is refquirement of ATC 250KT will be subject
higher to concurrence of
pilot
Below FL290 and up 250KT or actual 250KT or actual Optional/ Speed less than
to FL150 speed whichever is speed whichever is 250KT will be subject
lower higher to concurrence of
pilot
As per requirement Below FL210 speed
of ATC may be reduced to
240KT by ATC with
the concurrence of
pilot
Below FL150 & 220KT or actual 220KT or minimum Mandatory Below 10000ft AMSL
within 25DME to speed whichever is clean speed speed may be
20NM (30DME to lower whichever is higher reduced to 210KT
20NM in case of by ATC subject to
straight-in) or on concurrence of pilot
downwind
Within 20NM from 180KT 180KT Mandatory Speed may be
touch-down further reduced to
170KT by ATC
Intercept leg 180 - 160KT 180 - 160KT Mandatory Speed to be reduced
or 12NM from to 160KT during the
touch-down in case intercept leg
of straight-in
10 - 5NM from 160 - 150KT 160 - 150KT Mandatory Turboprop aircraft
touch-down1 unable to maintain
the specified speed
must inform ATC as
early as possible
preferably during
intercept leg or
when 12NM from
touchdown1
Within 5NM from N/A N/A N/A
touch-down
1 At the time approach clearance is issued, speed restrictions shall remain applicable unless withdrawn by ATC.

q$z

© JEPPESEN, 1991, 2013. ALL RIGHTS RESERVED.

 INDIA-8 AIR TRAFFIC CONTROL 25 OCT 13

INDIA - RULES AND PROCEDURES q$i

NOTE: Subject to aircraft performance limitations a

radar controller may assign a specific speed to the
aircraft in order to maintain/achieve required spacing.

1357658792605

Indicated Airspeed (IAS) vs. True Airspeed Indicated Airspeed (IAS) vs. True Airspeed (TAS)
(TAS) at different altitude at ISA + 15°C at different altitude at ISA + 15°C (continued)
Alti- IAS (KT) Alti- IAS (KT)
tude tude
160 180 210 220 240 250 260 160 180 210 220 240 250 260
(ft) (ft)
2000 169 190 31000 425
3000 172 193 32000 432
4000 174 196 229 239 34000 446
5000 177 199 232 243 NOTE 1: Speeds rounded to nearest of 1KT.
6000 202 236 247
NOTE 2: On a Standard Day, the Mach Number
8000 243 255 equivalent to 250KT (IAS) is:
10000 251 263 287 299
12000 259 272 296 309 FL240 - 0.60,
14000 268 281 306 319 FL250 - 0.61,
15000 308 321 FL260 - 0.62,
17000 322 335
FL270 - 0.64,
20000 338 353
FL280 - 0.65,
21000 349
24000 366 FL290 - 0.66.
25000 372
26000 377
28000 391
30000 418

q$z

© JEPPESEN, 1991, 2013. ALL RIGHTS RESERVED.

 25 OCT 13 AIR TRAFFIC CONTROL
INDIA - RULES AND PROCEDURES
ATS AIRSPACE CLASSIFICATIONS
India has adopted the ICAO ATS airspace classifi-
cation as listed in ATC-Chapter ‘ICAO ATS Airspace
Classifications - Annex 11’. Within Indian airspace,
however, only the airspace classes “D”, “E”, “F” and
“G” are used.
In Class “G” airspace, flight information service traffic
available only if requested.
SPECIAL REQUIREMENTS AND
REGULATIONS
COMMUNICATION
Aircraft overflying from a foreign FIR into Indian FIR
shall forward an FIR boundary estimate to the ATS
unit providing Flight Information Service at least 10
minutes prior to entry.
RECEIPT OF ATIS BROADCAST
Pilots are required to acknowledge on initial contact
with APP/TWR the receipt of ATIS broadcast, includ-
ing the designator.
JOINING OR CROSSING OF ATS ROUTES
Aircraft shall not join or cross ATS routes without
prior approval/ATC clearance from the ATS units con-
cerned. This approval/clearance shall be obtained at
least 10 minutes prior to entry into ATS routes if in
direct contact on VHF and at least 20 minutes prior
to such entry if contact is through enroute radio fre-
quency.
Ten (10) minutes prior to crossing an established ATS
route, pilot-in-command shall transmit the following
information to the ATC unit serving the airspace:
a. Call-sign of the aircraft;
b. Estimate time of crossing the route;
c. Flight level;
d. Position of crossing the route with reference to
a navigational aid or geographical position on
the route. Aircraft will join or cross ATS routes at
or close to designated reporting points. Aircraft
crossing the route shall do so at an angle of
90°, to the direction of the route and at a level
appropriate to the magnetic track.
DATALINK SERVICES WITHIN CHENNAI
AND KOLKATA FIR
General
Controller Pilot Datalink Communications (CPDLC)
and Automatic Dependent Surveillance (ADS) are
operational within Chennai and Kolkata FIR.
Datalink services are available to all FANS 1/A
equipped aircraft operating in the Chennai and
Kolkata FIR on H24 basis.
For ADS and CPDLC established aircraft, ADS will
be primary means of Surveillance and CPDLC will be
the primary means of communication outside Termi-
nal Control area. VHF/HF will be back-up for commu-
nication and position reporting.
q$z
INDIA-9
q$i
Applicability
Controller Pilot Data Link Communications (CPDLC)
and Automatic Dependent Surveillance (ADS)
datalink applications will be used to provide services
to FANS 1 (or other format compatible to FANS1)
equipped aircraft, over the Bay of Bengal & Arabian
Sea oceanic airspace and in particular on ATS routes
B466E, N877, P628, P762, P574, N571, N563, L759,
P646, L507, N895, G472, L301, L896, M770, L645,
P518, M300, P570, UL425, UM551, P323, G450,
G424, B459, G465, N628, A474 respectively.
Logon
The AFN LOGON address for the Chennai FIR is
VOMF.
The AFN LOGON address for the Kolkata FIR is
VECF.
CPDLC Procedures
Aircraft that have established datalink communica-
tions may transmit their Position reports by CPDLC
instead of HF RTF. However SELCAL check is
required to verify HFRT connectivity.
In Chennai FIR Remote controlled Air Ground
(RCAG 126.15MHz) will be used as primary back
up frequency for CPDLC on routes P762 (between
LULDA and BIKEN), N571 (between LAGOG and
BIKEN), P628 (between IGREX and VATLA) and
N877 (between LAGOG and ORARA), Primary and
Secondary HF frequencies shall continue to be
back-up communication for the entire airspace.
In Kolkata FIR Remote controlled Air Ground (RCAG
132.45MHz) will be used as primary back up fre-
quency for CPDLC on routes L759 (between LEMEX
and LIBDI), N895/G472 (between BBS and SAGOD),
P628 (between LARIK and VATLA) and N877
(between VVZ and ORARA), L301 (between VVZ
and RINDA), P646 (between DOPID and IBITA),
M770/770A (between BUBKO and MEPEL) and
L507 (between ESDOT and TEBOV) Primary and
Secondary HF frequencies shall continue to be back
up communication for the entire airspace.
To ensure the correct synchronization of messages,
Controller/pilot dialogues opened by voice must be
closed by voice.
The phraseology used is:
– TRANSFER TO CHENNAI Oceanic Control ON
DATA LINK (position)
MONITOR (VHF 126.15 ALTERNATE HF Pri-
mary/secondary (Frequencies))
Pilots should then down-link a CPDLC POSITION
REPORT
or
– TRANSFER TO KOLKATA Control ON DATA LINK
(position)
MONITOR (VHF 132.45 / 120.7 ALTERNATE HF
Primary/secondary (Frequencies))
Pilots should then down-link a CPDLC POSITION
REPORT
or
© JEPPESEN, 1991, 2013. ALL RIGHTS RESERVED.
 INDIA-10 AIR TRAFFIC CONTROL
INDIA - RULES AND PROCEDURES
– TRANSFER TO MUMBAI Oceanic Control ON
DATA LINK (position)
MONITOR (HF Primary/secondary (Frequen-
cies))
Pilots should then down-link a CPDLC POSITION
REPORT
CPDLC Termination
For aircraft inbound to Chennai/Mumbai/Kolkata Ter-
minal Control Area (TMA), pilot should disconnect
CPDLC after positive VHF voice communication is
established with Chennai/Kolkata ACC.
For aircraft exiting Chennai FIR, Next Data Authority
(NAD) will be notified via CPDLC 30 minutes prior
to crossing FIR boundary. Transfer of communication
shall be completed at the FIR boundary.
For aircraft exiting Chennai FIR, Next Data Authority
(NAD) will be notified via CPDLC 20 minutes prior
to crossing FIR boundary. Transfer of communication
shall be completed at the FIR boundary.
In case the next FIR does not have datalink services,
CPDLC connections will be terminated at the FIR
boundary position.
The CONTACT (unit name) (frequency) message and
the END SERVICE message will be sent as sepa-
rate messages. The END SERVICE message will be
send as soon as possible after receipt of the WILCO
response to the CONTACT message.
ADS Procedures
ADS Periodic contacts will be established automati-
cally on receipt of a LOGON. The periodic reporting
rate is 27 minutes.
Aircraft logged on to ADS need not give position
report on CPDLC HF/VHF outside TMA except at the
boundary points.
ADS contracts will be manually terminated by ATC at
the FIR boundary.
Datalink Failure
Pilots recognizing a failure of a CPDLC connection
must immediately establish communications on the
appropriate voice frequency. When voice communi-
cations have been established, voice must continue
to be used as the primary medium until a CPDLC con-
nection has been re-established and the controller
has authorized the return to datalink.
In the event of an expected CPDLC shutdown, the
controller will immediately advise all data link con-
nected aircraft of the failure by voice. Instructions will
continue to be issued by voice until the return of the
datalink system. The return of the system to an oper-
ational state will require a new AFN LOGON from the
affected aircraft.
Flight planning/Position report
For ADS/CPDLC in Kolkata FIR, all messages to be
addressed to VECFZQZX, VECCZPZX, VECCZRZX
and should include SSR code assigned.
q$z
25 OCT 13
q$i
All west bound flights on L301/L301A, N571 and
P574 must report position at NOBAT, SUGID and
BISET respectively to Mumbai Radio in addition to
Mumbai Area Control.
ADS/CPDLC WITHIN DELHI FIR
ADS/CPDLC System is available within Delhi FIR
on segments of ATS routes A466, A589, G333,
G452, L333, L509, M875, M890, P628, W30, W31,
W34, W36, W39. The service is available to all
aircraft suitably equipped with data link capability.
The ADS/CPDLC service will not affect the current
procedure for non data link capable aircraft operating
within Delhi FIR. The data link capable aircraft while
operating in Delhi FIR shall follow procedures as
given below:
a. Data link and ADS capability shall be indicated
in the FPL by indicating appropriate designators
in item 10 and 18;
b. The logon address of Delhi is VIDF;
c. The arriving aircraft shall logon 20 minutes prior
to entering Delhi FIR and in case flying time to
Delhi FIR is less than 20 minutes, immediately
after departure;
d. Aircraft departing from aerodromes within Delhi
FIR shall logon immediately after departure;
e. Aircraft departing/transiting from/within Delhi
FIR shall logon next data authority 15 minutes
prior to leaving the Delhi TMA limits;
f. Position reporting requirement to communicate
with ATC units on VHF/HF remain unchanged;
g. SELCAL checking is required to verify the HFRT
connectivity;
h. Pilots unable to establish Data link connection
shall inform appropriate ATS unit through voice
communication on VHF.
ADS/CPDLC WITHIN MUMBAI FIR
ADS/CPDLC System is available within Mumbai
FIR on segments of ATS routes N519, L301, L505,
L516, N571, P574, N563, M300, P570, L894, P751,
UL425, UM551, P323, G450, G424, B459, T940,
A474, G465, N628, R461, L875, L756 over Arabian
sea Oceanic airspace. The service is available to all
aircraft suitably equipped with data link capability.
The ADS/CPDLC service will not affect the current
procedure for non data link capable aircraft operating
within Mumbai FIR. The data link capable aircraft
while operating in Mumbai FIR shall follow proce-
dures as given below:
a. Data link and ADS capability shall be indicated
in the FPL by indicating appropriate designators
in item 10 and 18;
b. The logon address of Mumbai FIR is VABF;
c. The arriving aircraft shall logon 10 minutes prior
to entering Mumbai FIR;
d. Aircraft departing/transiting from/within Mumbai
FIR shall login within 15 minutes prior to leaving
the Mumbai TMA limits;
e. When operating in Mumbai OCC (Outside Mum-
bai TMA) CPDLC will be the primary means of
communication and VHF/HF will be secondary
means of communication for the aircraft suc-
© JEPPESEN, 1991, 2013. ALL RIGHTS RESERVED.
 25 OCT 13 AIR TRAFFIC CONTROL INDIA-11
INDIA - RULES AND PROCEDURES q$i

cessfully logged on to ADS/CPDLC. When oper- N571, N877, N895, P323, P570, P574, P628, P646,
ating inside Mumbai TMA VHF shall be the pri- P762, R325, R458, R461, R472, R594, UL425, W92,
mary means of communication for the aircraft; W93, W103, W122N/S, W123, W124.
f. During the period when aircraft is logged on to Minimum 50NM longitudinal separation applicable
ADS/CPDLC, voice PSN REP will be to supple- based on Mach Number Technique:
ment CPDLC PSN REP only when requested by
ATC; Q1, Q2, Q3, Q4, Q5, Q6, Q7, Q8, Q9, Q10, Q11.
g. SELCAL checking is required to verify the HFRT Minimum 10 minutes longitudinal separation applica-
connectivity; ble:
h. Voice positioning shall be resumed in case A325, A462, A791, B345, G208, G333, G335,
of ADS/CPDLC link failure. Pilots unable to G336, G348, G451, G452, G590, G59, R325, R344,
establish Data link connection shall inform R457, R458, R460, R581, R598, W13N/S, W15N/S,
appropriate ATS unit through voice commu- W17N/S, W18, W19, W20N/S, W25, W26, W27,
nication on VHF 132.7, 125.35MHz, or HF W28, W29, W38, W41, W42N/S, W43N/S, W44,
10018/13288/10084/5658/5601/3467/6661/ W46, W47N/S, W49, W57N/S, W70, W71N/S, W72,
4675/8879/3476/2872KHz. W81, W88, W91, W93, W96, W98, W101E/W, W103,
DATALINK SERVICES W104, W114, W115, W116, W117, W118N/S, W119,
W121, W218.
Provision of Air Traffic Services, through datalink, is
implemented in the following functional areas: ATC will apply 50NM longitudinal separation min-
a. Departure Clearance (DCL) services at Mum- ima between suitably equipped aircraft which are
bai, Delhi, Kolkata, Chennai, Bangalore and approved for RNP10 operations on those segments
Hyderabad; of the routes which fall within the Chennai, Mumbai
FIRs:
b. D-ATIS messages from airports to be notified
through NOTAM; – N571, IGOGU to PARAR W-bound, PARAR to
IDASO E-bound;
c. D-VOLMET messages from Mumbai and
Kolkata airport. – P762, DUGOS to LULDA;
Airlines that intend to use the DCL service at Indian – L301, RINDA to RASKI;
airports are requested to send the following informa- – L507, TEBOV to CEA;
tion: – L509, GGC to ASARI;
– ACARS on-board equipment (Equipment manu- – L510, EMRAN to IBANI;
facturer, type, and part number) and appropriate – L759, MIPAK to DPN;
aircraft type(s);
– M300, ATETA to LOTAV;
– ICAO and IATA designators for aircraft operating
agencies. – M770, MEPEL to JJS;
Contact address: – N563, MEMAK to REXOD;
– N877, LAGOG to PRA;
Executive Director (ATM)
E-Mail: edatm@aai.aero – N895, SAGOD to PARTY;
– P570, BASUR to KITAL;
LONGITUDINAL SEPARATION
– P574, NOPEK to TOTOX;
A longitudinal separation minimum of 15 (fifteen) min-
– P628, IGREX to VIKIT;
utes shall be applicable between the aircraft flying on
same track, at the same level, climbing or descending – P646, IBITA to BBN.
through the level of another aircraft, flying in the same REQUIRED NAVIGATION PERFORMANCE
direction unless otherwise specified in the remarks
column of relevant ATS route. RNAV5 Routes
Unless otherwise specified longitudinal separation – Q1, BBB to DPN;
minimum based on time for aircraft flying on crossing – Q2, DPN to BBB;
tracks whether at the same cruising level or climb- – Q3, AAE to JJP;
ing/descending through the level of another aircraft – Q4, ADBUK to AAE;
shall be 15 (fifteen) minutes if the tracks are not
crossing over navigational aids. – Q5, NIKOT to UUD;
– Q6, QQZ to EGUGU;
The Mach Number Technique (MNT) with 10 min-
utes or 80NM longitudinal separation between air- – Q7, AGRIX to QQZ;
craft may be applied to aircraft meeting RNAV criteria – Q8, MMV to BBB;
on the same track whether in flight level, climbing or – Q9, BBB to MMV;
descending on the following routes: – Q10, MMV to CEA;
A201, A347, A465, A466, A474, A589, A599, B465, – Q11, CEA to MMV;
B593, G210, G336, G463, G472, L301, L333, L507, – Q12, TVM to BBB;
L645, L759, M300, M638, M770, M890, N519, N563,
– Q13, BBB to TVM.

q$z

© JEPPESEN, 1991, 2013. ALL RIGHTS RESERVED.

 INDIA-12 AIR TRAFFIC CONTROL 25 OCT 13

INDIA - RULES AND PROCEDURES q$i

RNP10 Routes STRATEGIC LATERAL OFFSET

– L301, RINDA to RASKI; PROCEDURES (SLOP)
– L333, KKJ to TIGER; The following basic requirements apply to the use of
– L505, BUSBO to NOBAT; the Strategic Lateral Offset Procedures (SLOP):
– L507, TEBOV to CEA; a. Strategic Lateral Offset Procedures shall be
applied only by aircraft with automatic offset
– L509, GGC to ASARI; tracking capability;
– L510, EMRAN to IBANI; b. The decision to apply a strategic offset is the
– L516, ELKEL to KITAL; responsibility of the flight crew;
– L518, HIA to SADAP; c. The offset shall be established at a distance of
– L626, ONISA to DPN; 1 or 2NM to the RIGHT of the centerline of the
– L645, SAMAK to SULTO; ATS route relative to the direction of flight;
– L756, CLAVA to RULSA; d. The offsets shall not exceed 2NM right of the
centerline of the ATS route;
– L759, MIPAK to DPN;
e. The Strategic Lateral Offset Procedure has
– L760, AGG to DPN; been designed to include offsets to mitigate the
– L875, VUTAS to MMV; effects of wake turbulence of preceding aircraft.
– L894, KITAL to BIBGO; If wake turbulence needs to be avoided, one of
– L896, DUGOS to MMV; the three available options (centerline, 1NM or
2NM right offset) shall be used;
– M300, ATETA to LOTAV;
f. In airspace where the use of lateral offsets has
– M638, SAPNA to BBB; been authorized, pilots are not required to inform
– M641, MDI to BIKOK; ATC that an offset is being applied;
– M770, MEPEL to JJS; g. Aircraft transiting areas of radar coverage in
– M773, BUBKO to CEA; airspace where offset tracking is permitted may
– M875, KAKID to BUTOP; initiate or continue an offset;
– M890, LLK to SAMAR; h. Aircraft without automatic offset tracking capa-
bility must fly the centerline of the ATS route
– N519, BBB to SAPNA; being flown.
– N563, MEMAK to REXOD; The segments of ATS routes where Strategic Lateral
– N564, DUGOS to AKMIL; Offset Procedures are applicable are identified in the
– N571, IGOGU to PARAR W-bound, PARAR to tables below. However for ATC purposes the offset
IDASO E-bound; may be cancelled by the appropriate ATC unit.
– N628, LATIK to BUSUX; CHENNAI FIR
– N640, TVM to BIKOK;
L645 SAMAK SULTO
– N877, LAGOG to PRA;
N563 MEMAK AKMIL
– N893, TELEM to AAE;
P574 NOPAK MMV VOR
– N895, SAGOD to PARTY;
N571 IGOGU GURAS
– P323, GIDAS to DONSA;
N877 LAGOG ORARA
– P518, NOBAT to KABIM;
P628 IGREX VATLA
– P570, BASUR to KITAL;
L759 MIPAK NISUN
– P574, NOPEK to TOTOX;
P762 LULDA DUGOS
– P628, IGREX to VIKIT;
UL425 TVM VOR ANODA
– P646, IBITA to BBN;
P570 TVM VOR POMAN
– P762, DUGOS to LULDA;
M300 CLC VOR IGAMA
– T1, BPL to BBS;
– T2, PPT to LOTPU; KOLKATA FIR
– V30, ADKIT to TTR;
N877 ORARA VVZ VOR
– V31, ATETA to TTR.
L301 RINDA VVZ VOR
An aircraft that is unable to meet the minimum navi-
P628 VATLA LARIK
gational requirements for RNP10 must file flight plan
at or below minimum flight level of the route. How- L759 LIBDI LEMAX
ever operations of these aircraft will be subject to M770 MEPEL KAKID
ATC approval, in accordance with the provisions men- M773 BUBKO LEGOS
tioned below, if not approved will be required to file a
flight plan to operate via alternate route. N895 SAGOD BBS VOR
P646 IBITA DOPID
L507 TEBOV CEA VOR

q$z

© JEPPESEN, 1991, 2013. ALL RIGHTS RESERVED.

 25 OCT 13 AIR TRAFFIC CONTROL INDIA-13
INDIA - RULES AND PROCEDURES q$i

MUMBAI FIR payload capacity of more than 3 tonne, if flying in

UL425 ANODA ASPUX Indian airspace, shall be equipped with mode S
transponder.
P570 POMAN KITAL
M300 IGAMA LOTAV ACAS II/TCAS II REQUIREMENTS
N563 KAKIB REXOD Unless otherwise authorized by DGCA, no person
shall acquire for the purpose of operation:
P574 OKILA TOTOX
a. an aircraft having a maximum certified passen-
N571 crossing 072 deg PARAR ger seating configuration of 20 to 30 or a max-
East imum certified take-off mass of 5700kg, if such
L505 EXOLU NOBAT aircraft is not equipped with an approved ACAS
L301 AKTIV RASKI II;
M638 NOBAT SAPNA b. an aircraft having a maximum certified passen-
ger seating configuration of 10 to 19 or a maxi-
A451 BISET ANGAL
mum certified take-off mass of less than 5700kg,
G450 DARMI DOGOD if such aircraft is not equipped with approved
UM551 DONSA ANGAL ACAS I;
B459 GUNDI UBDOR c. a twin jet engined aircraft having a maximum
A474 ERVIS POPET certified seating configuration of less than 10
and a maximum certified take-off mass of less
R456 BIBGO KITAL
than 5700kg, if such aircraft is not equipped with
P323 DONSA GIDAS an approved ACAS I.

ENROUTE OPERATIONS AVOIDANCE OF UNNECESSARY

Flying outside of ATS routes is prohibited within TCAS WARNINGS
Indian airspace. Procedure for avoiding false TCAS Resolution
All flights entering, leaving or crossing the territory Advisories (RA)
of India are required to follow the ATS routes estab- Reduce the aircraft rate of climb or descent as appli-
lished for international operations (For exceptions see cable to 1500ft per minute or less when the airplane
FLIGHT PLANNING below). is 2000ft to level off altitude.
PPR for Connector Routes Pilots Responsibility in Case of RA
Prior permission required by airlines to fly ATS con- a. Respond immediately to RA by disengaging
nector routes (V012, V013, V014, V015, V016, V017, the auto pilot and commencing a climb/descent
V018, V019, V020 and V021) between Mumbai FIR maneuver as called for;
and Male FIR from the ATS provider at least one week b. Look out for traffic;
in advance. c. Do not let visual sighting reverse the TCAS
NOTE: Aircraft operating on these connector routes instructions;
shall be ADS/CPDLC equipped. d. If pilots simultaneously receive instructions to
Contact details: maneuver from ATC and RA which are in con-
Mumbai Watch Supervisory Officer (WSO) flict, the pilots should follow the RA;
Tel: +91 22 26828088 e. Return to required flight path on cessation of RA;
Fax: +91 22 26828066 f. Inform ATC about the RA;
E-Mail: wsomum@aai.aero g. Raise a RA Form as soon as practicable.
General Manager (ATM), Mumbai
Tel: +91 22 26828010
DEPARTING AIRCRAFT
Fax: +91 22 26828010 Pilots shall report total number of persons on board,
E-Mail: gmatmmum@aai.aero including crew, and confirm the completion of security
check to aerodrome control tower when requesting
FLIGHT PLANNING start-up clearance.
Scheduled international flights are permitted to
flight plan using domestic ATS routes segments
USER PREFERRED ROUTES
to/from destination, departure and approved alter- To reduce the environmental impact of aviation
nate airports in India which are not connected by the members of the Indian Ocean and Arabian
international ATS route. Sea Strategic Partnership to Reduce Emissions
(INSPIRE) are collaborating to allow airspace users
Secondary Surveillance Radar (SSR) access to User Preferred Routes (UPR) across
All aeroplane having maximum certified take-off the Arabian Sea, Indian and Southern Oceans and
mass of 5700kg and above and having maximum adjoining airspaces.
certified passenger seating configuration (excluding Procedure
any pilot seats) of more than 30 seats or maximum
The vertical limits of the India UPR Geographic Zone
shall be FL280 to FL460.

q$z

© JEPPESEN, 1991, 2013. ALL RIGHTS RESERVED.

 INDIA-14 AIR TRAFFIC CONTROL 25 OCT 13

INDIA - RULES AND PROCEDURES q$i

Flight Planning or
– UPRs must be constructed via published way- Watch Supervisory Officer (WSO), Mumbai
points, navigation aids, or positions designated Tel: +91 22 26828088
by latitudes and longitudes; Fax: +91 22 26828066
– if the UPR is intersecting any ATS route within E-Mail: wsomum@aai.aero
Mumbai/Chennai UPR zone the intersecting point
Specific requirements within the Chennai
shall be mentioned in the route column of flight
and Mumbai FIRs
plan as a position designated by latitude and lon-
gitude; Within the Chennai and Mumbai FIRs the following
flight planning requirements apply:
– time interval between waypoints shall not exceed
30 minutes; – Prior permission required at least seven days in
advance for flight operators to fly UPR in Chen-
– UPRs may include ATS routes.
nai/Mumbai FIR. Permission may be requested for
Access to UPR whole or part of Summer/Winter schedule for par-
Airspace users may only file a flight plan user pre- ticular flight/s.
ferred route in the UPR Geographic Zone if they meet
the following minimum criteria:
DIFFERENCES FROM ICAO
– RNAV10; and
STANDARDS AND PROCEDURES
– ADS-C/CPDLC equipped. ICAO REFERENCE
The minimum criteria listed above must be notified ANNEX 2
in the Flight Plan. The flight shall log on to Chen-
3.3.1.2 Flight plans are required for all flights.
nai ADS-C/CPDLC VOMF or Mumbai ADS-C/CPDLC
VABF as appropriate, prior to entering UPR zone. 4.4a VFR flights shall not be operated above
FL150.
The transition from a conventional ATS route to User
Preferred Route or vice versa at the northern bound-
ary of Chennai UPR zone shall take place at any of
the waypoints on ATS routes P570. At the northern
boundary of Mumbai UPR zone the transition from a
conventional ATS route to User Preferred Route or
vice versa shall take place at any of the waypoints
south of METIP on ATS routes P570 or G450.
In case the UPR is not entering or exiting Chen-
nai/Mumbai FIR over a waypoint on the eastern/west-
ern or southern boundary of Chennai/Mumbai UPR
zone the coordinates of the point at which the UPR
is entering or exiting Chennai/Mumbai FIR shall be
mentioned in the route field of the flight plan, except
that entry/exit at Mumbai/Male and Chennai/Male
FIR boundaries shall be via waypoints LATIK, ELKEL,
MANAP, RULSA, OVPUK, IPNEB, OMLEV, ESLAV,
BIBGO, POXOD, NODOL, NOKID and SEBLO.
Questions and assistance should be directed to
Chennai
General Manager (ATM)
Airports Authority of India
Chennai International Airport, Chennai
Fax: +91 44 22561740
E-Mail: gmaerochennai@aai.aero
or
Watch Supervisory Officer (WSO), Chennai
Tel: +91 44 22560894
Fax: +91 44 22561365
E-Mail: wso_mm@aai.aero
Mumbai
General Manager (ATM)
Airports Authority of India
Chhatrapati Shivaji International Airport, Mumbai
Fax: +91 22 26828010
E-Mail: gmatmmum@aai.aero

q$z

© JEPPESEN, 1991, 2013. ALL RIGHTS RESERVED.