Escolar Documentos
Profissional Documentos
Cultura Documentos
q$z
All non-precision approaches shall be flown Any turning manoeuvre associated with the missed
using the Continuous Descent Final Approach approach should be initiated not earlier than the
technique unless otherwise approved by the MAP.
DGCA for a particular approach to a particular
The Jeppesen charted MDA(H) is the minimum value
runway.
based on the procedure’s OCA(H) and the system
When calculating the minimums the operator shall minima as described below. It should be used when
ensure that the applicable minimum RVR is increased adding the increment to determine the DDA accor-
by 200m for CAT A/B aircraft and by 400m for CAT ding to Ops Circular 1/2005.
C/D aircraft for approaches not flown using the CDFA
Converted Meteorological Visibility (CMV)
technique, providing that the resulting RVR/CMV
value does not exceed 5000m. A value equivalent to an RVR which is derived from
the reported meteorological VIS, as converted in
Jeppesen charted non-precision RVR values not accordance with the specified requirements in the
labelled as CDFA, already take these increments into CAR.
account.
Table 1 must not be applied for Take-off or any other
In case of the application of the CDFA technique, required RVR minimum less than 800m or when
on many procedures the Derived Decision Alti- reported RVR is available.
tude (DDA) may be used (as given in Ops Circular
NOTE: If the RVR is reported at being above the max-
1/2005). Flight crews should add a prescribed
imum value assessed by the airport operator, e.g.
altitude increment of minimum 50ft to the pub-
“RVR more than 1500m”, it is not considered to be
lished MDA(H) to determine the altitude at which
a reported value for the purpose of this paragraph.
the missed approach should be initiated in order
to prevent a descent below the MDA(H). There is Jeppesen will publish only RVR values, except where
no need to increase the RVR/VIS for that approach. CMV or VIS values are published by the State as part
of the AOM.
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
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
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
q$z
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)
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
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
The fail-operational system referred to may consist of b. Aircraft with three or more engines: not more
a fail operational hybrid system. than a distance equivalent to two hours flight
time at the one engine inoperative cruise speed.
Circling Approach
Circling approach and associated minimums will be Visual Reference
authorized for operators by Flight Standards Direc- Take-off minimums must be determined to ensure
torate as per the training programme implemented by sufficient guidance to control the aircraft in case of
the operator. discontinued take-off in adverse circumstances or
during continued take-off after failure of the critical
Visual Approach
power unit.
For a visual approach, an operator shall use the
higher of the associated non-precision approach Required RVR/VIS
minimum or 2800m for CAT A & B, 3200m for CAT For multi-engine aircraft, whose performance is such
C and 3600m for CAT D aircraft. If visual approach that in the event of a critical power unit failure at any
is requested for a runway which has only a circling point during take-off the aircraft can either stop or
approach, the ground visibility shall not be less than continue the take-off to a height of 1500ft above the
5km. airport while clearing all obstacles by the required
margins, the take-off minimums established by an
Take-off
operator must be expressed as RVR/VIS values not
Take-off minimums established by the operator must lower than those in Table 7 below.
be expressed as VIS or RVR, taking into account all
relevant factors for each airport planned to be used. Table 7 RVR/VIS for Take-off (Commercial
Where there is a specific need to see and to avoid Transport Aircraft)
obstacles a ceiling or climb gradient must be speci- Facilities RVR/VIS
fied.
Adequate visual reference (Day 500m
The commander shall not commence take-off unless only)
the weather conditions at the airport of departure are Runway edge lights or runway 400m
equal to or better than applicable minimums for land- centreline markings
ing at that airport unless a suitable take-off alternate
airport is available. Runway edge lights and runway 300m
centreline markings
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;
q$z
Table 7 RVR/VIS for Take-off (Commercial All arriving aircraft operating below 10000ft within
Transport Aircraft) (continued) 15NM Radius of VOR/DME serving the aerodrome
Facilities RVR/VIS to fly IAS not greater than 220KT. ATC may suspend
Runway edge lights and runway 200m speed control by using the phrase “No speed restric-
centreline lights tion”, when traffic conditions permit.
Runway edge lights and runway 150m Speed Control Procedures in the Provision
centreline lights and relevant RVR of Radar Control Service
information Purpose
High intensity runway edge lights 125m In order to facilitate safe and orderly flow of arriving
and runway centreline lights air traffic within terminal area under the radar environ-
(spacing 15m or less) and relevant ment, aircraft shall follow the speed in specified man-
RVR information ner as provided in table “Speed Control under Radar
NOTE 1: TDZ RVR/VIS may be assessed by the pilot. Environment for Arriving Aircraft” at the following air-
ports:
NOTE 2: Adequate visual reference means, that the
pilot is able to continuously identify the take-off sur- Ahmedabad, Bangalore (Intl), Chennai (Intl), Delhi
face and maintain directional control. (Indira Gandhi Intl), Hyderabad (Rajiv Gandhi Intl),
NOTE 3: For night operations at least runway edge Kolkata (Netaji Subhash Chandra Bose Intl) and
lights or centreline lights and runway end lights are Mumbai (Chhatrapati Shivaji Intl).
available. Requirement of Speed Control
NOTE 4: The required RVR must be achieved for all The speed control is applied for ATC separation pur-
relevant RVR reporting points (touchdown, mid-point poses and is mandatory in the interest of acquiring
and stop-end/roll-out). The governing RVR shall be accurate spacing.
the lowest of the reported RVRs.
Speed control is also necessary to achieve the
Non-scheduled and general aviation operators shall
desired separation minimum or spacing between
not conduct take-offs below RVR 500m.
the successive arrivals. This in turn would improve
Low Visibility Take-off Operations (LVTO) the utilization of airspace and enhance the runway
Flight operations referring to a take-off on a runway capacity to handle more number of aircraft.
where the RVR is less than 400m. The flight crew should be aware of the provisions
Low Visibility Procedues (LVP) specified in table “Speed Control under Radar Envi-
ronment for Arriving Aircraft” and plan the aircraft
Specific procedures applied at an aerodrome for
speed accordingly.
the purpose of ensuring safe operations during Cat-
egories II and III approaches and/or low visibility Adherence to Speed Control Procedure
take-offs. All the speed restrictions shall be complied with as
LVTO Authorization promptly as feasible and flown as accurately as pos-
sible within the limits of operational constraints.
Use of take-off minimums less than 400m (LVTO)
requires authorization by DGCA. Scheduled opera- Aircraft unable to comply with the specified speeds
tors may be authorized to LVTO minimum of 125m. must inform ATC and report minimum speed it is
This requires that a 90m visual segment shall be able to follow. In such cases controller shall apply the
available from the cockpit at the start of the take-off alternative method to achieve the desired spacing
run. Foreign operators, who are authorized by their between aircraft concerned.
State Regulatory Authority for LVTO, shall submit req-
The speeds specified in table “Speed Control under
uisite documents to DGCA for approval of LVTO at
Radar Environment for Arriving Aircraft” are within the
Indian airports.
limits of turboprops and turbojets aircraft performance
Restricted AOM based on the ICAO recommendations and best inter-
Restricted AOM shall be based on additives applied national practices and therefore should be accept-
to the Normal AOM as below: able. However it is the pilot’s responsibility and pre-
rogative to refuse speed restrictions that are consid-
– Restricted DA(H) = Normal DA(H) + 100ft;
ered excessive or contrary to the aircraft operating
– Restricted MDA(H) = Normal MDA(H) + 100ft; specifications.
– Restricted RVR = Normal RVR + 400m.
Penalties of Non-Confirmity of Speed Control
Restricted AOM are not charted on Jeppesen
Radar controller may remove an aircraft from the
approach and airport charts. Pilots are responsible
sequence for repositioning if it is observed that air-
to add the 100ft/400m increment to the charted
craft concerned is not following the speed restrictions
minima.
in the specified manner and closing-in with preceding
SPEED RESTRICTION aircraft or slowing down unnecessarily thus disrupt-
ing the traffic flow.
Speed Control Procedures under Non-radar
Environment Flights Exempted from Speed Control
All aircraft (including Arrivals and Departures) operat- Speed control shall not be applicable to aircraft:
ing below 10000ft to fly IAS not greater than 250KT. a. entering or established in holding pattern;
q$z
b. encountering the turbulent weather; d. For the same indicated air speed (IAS), the true
c. conducting the Cat II/III operations and within speed of aircraft will vary with altitude. A table
20NM from touch-down; representing indicated air speed versus true air
speed at different altitude is provided in table
d. within 5NM from touch-down;
“Indicated Airspeed (IAS) vs. True Airspeed
e. executing the published instrument approach (TAS) at different altitude at ISA +15°C”. Radar
procedure until interception of final approach controllers must be aware of speed differentials
track; between IAS and TAS;
f. carrying VVIP; and e. Simultaneous speed reduction and descent can
g. conducting priority/emergency landing. be extremely difficult, particularly for turbojet air-
Aircraft shall be advised as and when speed control craft. It may be necessary for the pilot to level off
restriction is not applicable or no longer required. temporarily and reduce speed prior to descend-
ing below 10000ft AMSL;
Additional Information for Better Understanding
f. Arriving aircraft would prefer to fly in clean con-
of Speed Control
figuration for as long as circumstances permit.
While applying the speed control, the following infor- Below 10000ft AMSL, speed not less than 210Kt
mation is provided as an additional information for IAS is considered as minimum speed of turbojet
controllers and pilots: aircraft in clean configuration;
a. Speed adjustments are not achieved instan- g. Speed adjustments requiring alternate
taneously. Aircraft configurations, altitude and decrease and increase shall be avoided partic-
speed determine the time and distance to ularly after the aircraft has reduced the speed
accomplish the adjustments; below 210kt. In such cases the Phraseology”,
b. Speed control shall not be assigned to an aircraft No ATC speed restriction”, or “Resume normal
at or above FL390 without pilot’s consent; speed” shall only be used.
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;
q$z
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 3000 172 193
q$z
Indicated Airspeed (IAS) vs. True Airspeed (TAS) JOINING OR CROSSING OF ATS ROUTES
at different altitude at ISA + 15°C (continued)
Aircraft shall not join or cross ATS routes without
Alti- IAS (KT) prior approval/ATC clearance from the ATS units con-
tude cerned. This approval/clearance shall be obtained at
160 180 210 220 240 250 260
(ft) least 10 minutes prior to entry into ATS routes if in
4000 174 196 229 239 direct contact on VHF and at least 20 minutes prior
5000 177 199 232 243 to such entry if contact is through enroute radio fre-
6000 202 236 247 quency.
8000 243 255 Ten (10) minutes prior to crossing an established ATS
10000 251 263 287 299 route, pilot-in-command shall transmit the following
12000 259 272 296 309 information to the ATC unit serving the airspace:
14000 268 281 306 319 a. Call-sign of the aircraft;
15000 308 321 b. Estimate time of crossing the route;
17000 322 335 c. Flight level;
20000 338 353
d. Position of crossing the route with reference to
21000 349 a navigational aid or geographical position on
24000 366 the route. Aircraft will join or cross ATS routes at
25000 372 or close to designated reporting points. Aircraft
26000 377 crossing the route shall do so at an angle of
28000 391 90°, to the direction of the route and at a level
30000 418 appropriate to the magnetic track.
31000 425 DATALINK SERVICES WITHIN CHENNAI
32000 432 AND KOLKATA FIR
34000 446
General
NOTE 1: Speeds rounded to nearest of 1KT.
Controller Pilot Datalink Communications (CPDLC)
NOTE 2: On a Standard Day, the Mach Number and Automatic Dependent Surveillance (ADS) are
equivalent to 250KT (IAS) is: operational within Chennai and Kolkata FIR.
FL240 - 0.60, Datalink services are available to all FANS 1/A
FL250 - 0.61, equipped aircraft operating in the Chennai and
Kolkata FIR on H24 basis.
FL260 - 0.62,
FL270 - 0.64, For ADS and CPDLC established aircraft, ADS will
be primary means of Surveillance and CPDLC will be
FL280 - 0.65, the primary means of communication outside Termi-
FL290 - 0.66. nal Control area. VHF/HF will be back-up for commu-
nication and position reporting.
ATS AIRSPACE CLASSIFICATIONS Applicability
India has adopted the ICAO ATS airspace classifi-
Controller Pilot Data Link Communications (CPDLC)
cation as listed in ATC-Chapter ‘ICAO ATS Airspace
and Automatic Dependent Surveillance (ADS)
Classifications - Annex 11’. Within Indian airspace,
datalink applications will be used to provide services
however, only the airspace classes “D”, “E”, “F” and
to FANS 1 (or other format compatible to FANS1)
“G” are used.
equipped aircraft, over the Bay of Bengal & Arabian
In Class “G” airspace, flight information service traffic Sea oceanic airspace and in particular on ATS routes
available only if requested. B466E, N877, P628, P762, P574, N571, N563, L759,
P646, L507, N895, G472, L301, L896, M770, L645,
SPECIAL REQUIREMENTS AND P518, M300, P570, UL425, UM551, P323, G450,
REGULATIONS G424, B459, G465, N628, A474 respectively.
COMMUNICATION Logon
Aircraft overflying from a foreign FIR into Indian FIR The AFN LOGON address for the Chennai FIR is
shall forward an FIR boundary estimate to the ATS VOMF.
unit providing Flight Information Service at least 10 The AFN LOGON address for the Kolkata FIR is
minutes prior to entry. VECF.
RECEIPT OF ATIS BROADCAST CPDLC Procedures
Pilots are required to acknowledge on initial contact Aircraft that have established datalink communica-
with APP/TWR the receipt of ATIS broadcast, includ- tions may transmit their Position reports by CPDLC
ing the designator. instead of HF RTF. However SELCAL check is
required to verify HFRT connectivity.
q$z
In Chennai FIR Remote controlled Air Ground The CONTACT (unit name) (frequency) message and
(RCAG 126.15MHz) will be used as primary back the END SERVICE message will be sent as sepa-
up frequency for CPDLC on routes P762 (between rate messages. The END SERVICE message will be
LULDA and BIKEN), N571 (between LAGOG and send as soon as possible after receipt of the WILCO
BIKEN), P628 (between IGREX and VATLA) and response to the CONTACT message.
N877 (between LAGOG and ORARA), Primary and
ADS Procedures
Secondary HF frequencies shall continue to be
back-up communication for the entire airspace. ADS Periodic contacts will be established automati-
cally on receipt of a LOGON. The periodic reporting
In Kolkata FIR Remote controlled Air Ground (RCAG rate is 27 minutes.
132.45MHz) will be used as primary back up fre-
quency for CPDLC on routes L759 (between LEMEX Aircraft logged on to ADS need not give position
and LIBDI), N895/G472 (between BBS and SAGOD), report on CPDLC HF/VHF outside TMA except at the
P628 (between LARIK and VATLA) and N877 boundary points.
(between VVZ and ORARA), L301 (between VVZ ADS contracts will be manually terminated by ATC at
and RINDA), P646 (between DOPID and IBITA), the FIR boundary.
M770/770A (between BUBKO and MEPEL) and
L507 (between ESDOT and TEBOV) Primary and Datalink Failure
Secondary HF frequencies shall continue to be back Pilots recognizing a failure of a CPDLC connection
up communication for the entire airspace. must immediately establish communications on the
appropriate voice frequency. When voice communi-
To ensure the correct synchronization of messages,
cations have been established, voice must continue
Controller/pilot dialogues opened by voice must be
to be used as the primary medium until a CPDLC con-
closed by voice.
nection has been re-established and the controller
The phraseology used is: has authorized the return to datalink.
– TRANSFER TO CHENNAI Oceanic Control ON In the event of an expected CPDLC shutdown, the
DATA LINK (position) controller will immediately advise all data link con-
MONITOR (VHF 126.15 ALTERNATE HF Pri- nected aircraft of the failure by voice. Instructions will
mary/secondary (Frequencies)) continue to be issued by voice until the return of the
Pilots should then down-link a CPDLC POSITION datalink system. The return of the system to an oper-
REPORT ational state will require a new AFN LOGON from the
affected aircraft.
or
– TRANSFER TO KOLKATA Control ON DATA LINK Flight planning/Position report
(position) For ADS/CPDLC in Kolkata FIR, all messages to be
MONITOR (VHF 132.45 / 120.7 ALTERNATE HF addressed to VECFZQZX, VECCZPZX, VECCZRZX
Primary/secondary (Frequencies)) and should include SSR code assigned.
Pilots should then down-link a CPDLC POSITION All west bound flights on L301/L301A, N571 and
REPORT P574 must report position at NOBAT, SUGID and
or BISET respectively to Mumbai Radio in addition to
Mumbai Area Control.
– TRANSFER TO MUMBAI Oceanic Control ON
DATA LINK (position) ADS/CPDLC WITHIN DELHI FIR
MONITOR (HF Primary/secondary (Frequen- ADS/CPDLC System is available within Delhi FIR
cies)) on segments of ATS routes A466, A589, G333,
Pilots should then down-link a CPDLC POSITION G452, L333, L509, M875, M890, P628, W30, W31,
REPORT W34, W36, W39. The service is available to all
aircraft suitably equipped with data link capability.
CPDLC Termination The ADS/CPDLC service will not affect the current
For aircraft inbound to Chennai/Mumbai/Kolkata Ter- procedure for non data link capable aircraft operating
minal Control Area (TMA), pilot should disconnect within Delhi FIR. The data link capable aircraft while
CPDLC after positive VHF voice communication is operating in Delhi FIR shall follow procedures as
established with Chennai/Kolkata ACC. given below:
For aircraft exiting Chennai FIR, Next Data Authority a. Data link and ADS capability shall be indicated
(NAD) will be notified via CPDLC 30 minutes prior in the FPL by indicating appropriate designators
to crossing FIR boundary. Transfer of communication in item 10 and 18;
shall be completed at the FIR boundary. b. The logon address of Delhi is VIDF;
For aircraft exiting Chennai FIR, Next Data Authority c. The arriving aircraft shall logon 20 minutes prior
(NAD) will be notified via CPDLC 20 minutes prior to entering Delhi FIR and in case flying time to
to crossing FIR boundary. Transfer of communication Delhi FIR is less than 20 minutes, immediately
shall be completed at the FIR boundary. after departure;
In case the next FIR does not have datalink services, d. Aircraft departing from aerodromes within Delhi
CPDLC connections will be terminated at the FIR FIR shall logon immediately after departure;
boundary position.
q$z
h. Aircraft without automatic offset tracking capa- All flights entering, leaving or crossing the territory
bility must fly the centerline of the ATS route of India are required to follow the ATS routes estab-
being flown. lished for international operations (For exceptions see
The segments of ATS routes where Strategic Lateral FLIGHT PLANNING below).
Offset Procedures are applicable are identified in the PPR for Connector Routes
tables below. However for ATC purposes the offset
Prior permission required by airlines to fly ATS con-
may be cancelled by the appropriate ATC unit.
nector routes (V012, V013, V014, V015, V016, V017,
CHENNAI FIR V018, V019, V020 and V021) between Mumbai FIR
and Male FIR from the ATS provider at least one week
L645 SAMAK SULTO in advance.
N563 MEMAK AKMIL NOTE: Aircraft operating on these connector routes
P574 NOPAK MMV VOR shall be ADS/CPDLC equipped.
N571 IGOGU GURAS Contact details:
N877 LAGOG ORARA Mumbai Watch Supervisory Officer (WSO)
P628 IGREX VATLA Tel: +91 22 26828088
L759 MIPAK NISUN Fax: +91 22 26828066
E-Mail: wsomum@aai.aero
P762 LULDA DUGOS
UL425 TVM VOR ANODA General Manager (ATM), Mumbai
Tel: +91 22 26828010
P570 TVM VOR POMAN Fax: +91 22 26828010
M300 CLC VOR IGAMA E-Mail: gmatmmum@aai.aero
ENROUTE OPERATIONS
Flying outside of ATS routes is prohibited within
Indian airspace.
q$z
Procedure Mumbai
The vertical limits of the India UPR Geographic Zone General Manager (ATM)
shall be FL280 to FL460. Airports Authority of India
Chhatrapati Shivaji International Airport, Mumbai
Flight Planning Fax: +91 22 26828010
– UPRs must be constructed via published way- E-Mail: gmatmmum@aai.aero
points, navigation aids, or positions designated
by latitudes and longitudes; or
– if the UPR is intersecting any ATS route within Watch Supervisory Officer (WSO), Mumbai
Mumbai/Chennai UPR zone the intersecting point Tel: +91 22 26828088
shall be mentioned in the route column of flight Fax: +91 22 26828066
plan as a position designated by latitude and lon- E-Mail: wsomum@aai.aero
gitude; Specific requirements within the Chennai
– time interval between waypoints shall not exceed and Mumbai FIRs
30 minutes; Within the Chennai and Mumbai FIRs the following
– UPRs may include ATS routes. flight planning requirements apply:
Access to UPR – Prior permission required at least seven days in
Airspace users may only file a flight plan user pre- advance for flight operators to fly UPR in Chen-
ferred route in the UPR Geographic Zone if they meet nai/Mumbai FIR. Permission may be requested for
the following minimum criteria: whole or part of Summer/Winter schedule for par-
ticular flight/s.
– RNAV10; and
– ADS-C/CPDLC equipped.
q$z
q$z