2.2.
|
Take-off and Climb
|
2.2.1.
|
QNH altimeter setting is made available to aircraft in taxi clearance prior to take off.
|
2.2.2.
|
Vertical positioning of aircraft during climb is expressed in terms of altitude until reaching the transition altitude above which vertical positioning is expressed in terms of flight levels.
|
|
|
2.3.
|
Vertical Separation Enroute
|
2.3.1.
|
Vertical separation during enroute flight shall be expressed in terms of flight level at all times. Except when flying in the vicinity of an aerodrome at or below transition altitude.
|
2.4.
|
Approach and Landing
|
2.4.1.
|
A QNH altimeter setting is made available in the routine approach and landing instructions. The altimeter setting obtained on radio telephone shall be read back to the ATS unit.
|
2.4.2.
|
Vertical positioning of aircraft during approach is controlled by reference to flight levels until reaching the transition level below which vertical positioning is controlled by reference to altitude.
|
|
|
2.5.
|
Missed Approach
|
2.5.1.
|
The relevant portions of 2.1.2, 2.2 and 2.4 shall be applied in the case of a missed approach.
|
|
|
3.
|
Procedures applicable to operators (including pilots)
|
3.1.
|
Flight Planning
|
3.1.1.
|
The levels at which a flight is to be conducted shall be specified in a flight plan -
|
|
i) in terms of flight level if the flight is to be conducted at or above the transition level, and
|
|
ii) in terms of altitude if the flight is to be conducted in the vicinity of an aerodrome and at or below the transition altitude.
|
|
|
3.2.
|
Minimum Flight Altitude
|
3.2.1.
|
Pilot must ensure that in Instrument Meteorological Conditions and at night an aircraft is not descended below the minimum safe en-route altitude until over a known aid at the aerodrome, the only exception being when the position of the aircraft is positively established by reference to a Radio/ATS Radar aid within the initial approach area, where the initial approach altitude or associated sector altitude apply.
|
|
|
4.
|
System of Cruising level
|
4.1.
|
All VFR flights above 3,000 Ft from the ground and water and all IFR flights, when in level cruising flight levels appropriate to their magnetic tracks in accordance with the table set forth hereunder.
|
4.2.
|
In controlled airspace, the correlation of levels to track as prescribed in Tables of cruising levels shall not apply whenever otherwise indicated in Air Traffic Control Clearances.
|
4.3.
|
All flights shall be conducted in accordance with Instrument Flight Rules when operated at or above FL 150. However, Indian Military aircraft may operate VFR flights between FL 150 and FL 285 at appropriate levels given in Table of cruising levels when flying-
|
|
i) In VMC
|
|
ii) Outside controlled airspace and
|
|
iii) Unable to establish contact with appropriate ATS units.
|
|
|
5.
|
Changing levels
|
5.1.
|
A pilot-in-command shall read back level clearance.
|
5.2.
|
When required, the pilot-in-command may be instructed to reach an assigned level by a specified time or position and at a specified rate of climb or descend. The pilot-in-command shall advise ATC immediately if he is doubtful whether the assigned level can be reached as instructed.
|
5.3.
|
An aircraft may be required to change level at a time, place or rate specified by ATC. The pilot-in-command shall effect a level change as soon as possible but not later than 1 minute after the time specified.
|
5.4.
|
A pilot-in-command shall report:
|
|
i). at the time of leaving a level for newly assigned level
|
|
ii). When leaving or passing through such other levels as may be specified by ATC
|
|
iii). On reaching an assigned level.
|
|
S No
|
City/Aerodrome
|
Transition altitude in Feet
|
|---|
0
|
|
|
|---|
1.
|
Agartala
|
4000
|
2.
|
Agatti
|
4000
|
3.
|
Agra
|
4000
|
4.
|
Ahmedabad
|
4000
|
5.
|
Akola
|
4000
|
6.
|
Ambikapur
|
7000
|
7.
|
AligarhAmravati
|
4000
|
8.
|
AmritsarAligarh
|
40005000
|
9.
|
AurangabadAmritsar
|
50004000
|
10.
|
AyodhyaAurangabad
|
40005000
|
11.
|
AzamgarhAyodhya
|
4000
|
12.
|
BagdograAzamgarh
|
130004000
|
13.
|
BalurghatBagdogra
|
400013000
|
14.
|
Barapani (Shillong)Balurghat
|
90004000
|
15.
|
Behala
Barapani (Shillong)
|
40009000
|
16
|
Bengaluru (VOBL)Behala
|
70004000
|
17
|
Bengaluru (HALVOBL)
|
7000
|
18
|
Bilaspur
Bengaluru (HAL)
|
50007000
|
19.
|
BelagaviBilaspur
|
60005000
|
20.
|
BhavnagarBelagavi
|
40006000
|
21.
|
BhopalBhavnagar
|
50004000
|
22.
|
BhubaneswarBhopal
|
40005000
|
23.
|
BhujBhubaneswar
|
4000
|
24.
|
BilaspurBhuj
|
50004000
|
25.
|
BokaroBilaspur
|
60005000
|
26.
|
BurnpurBokaro
|
40006000
|
27.
|
CalicutBurnpur
|
100004000
|
28.
|
ChakuliaCalicut
|
400010000
|
29.
|
ChandigarhChakulia
|
100004000
|
30.
|
ChennaiChandigarh
|
400010000
|
31.
|
ChitrakootChennai
|
4000
|
32.
|
Cochin InternationalChitrakoot
|
110004000
|
33.
|
CoimbatoreCochin International
|
11000
|
34.
|
Cooch BeharCoimbatore
|
800011000
|
35.
|
DamanCooch Behar
|
40008000
|
36.
|
DaparizoDaman
|
4000
|
37.
|
DarbhangaDaparizo
|
4000
|
38.
|
DatiaDarbhanga
|
4000
|
39.
|
DehradunDatia
|
120004000
|
40.
|
DeesaDehradun
|
400012000
|
41.
|
DeogharDeesa
|
50004000
|
42.
|
Dibrugarh (Mohanbari)Deoghar
|
80005000
|
43.
|
Dimapur
Dibrugarh (Mohanbari)
|
110008000
|
44.
|
DiuDimapur
|
400011000
|
45.
|
DurgapurDiu
|
4000
|
46.
|
GayaDurgapur
|
4000
|
47.
|
GoaGaya
|
60004000
|
48.
|
GondiaGoa
|
50006000
|
49.
|
GorakhpurGondia
|
40005000
|
50.
|
GuwahatiGorakhpur
|
90004000
|
51.
|
GwaliorGuwahati
|
40009000
|
52.
|
HindanGwalior
|
50004000
|
53.
|
HollongiHindan
|
120005000
|
54.
|
HubballiHollongi
|
600012000
|
55.
|
HisarHubballi
|
50006000
|
56.
|
HyderabadHisar
|
70005000
|
57.
|
IGI Airport, DelhiHyderabad
|
50007000
|
58.
|
Imphal (Tulihal)IGI Airport, Delhi
|
110005000
|
59.
|
Indore
Imphal (Tulihal)
|
500011000
|
60.
|
JabalpurIndore
|
5000
|
61.
|
JagdalpurJabalpur
|
60005000
|
62.
|
JaipurJagdalpur
|
6000
|
63.
|
JaisalmerJaipur
|
40006000
|
64.
|
JalgaonJaisalmer
|
50004000
|
65.
|
JammuJalgaon
|
110005000
|
66.
|
JamnagarJammu
|
400011000
|
67.
|
JamshedpurJamnagar
|
50004000
|
68.
|
JhansiJamshedpur
|
40005000
|
69.
|
JharsugdaJhansi
|
70004000
|
70.
|
JodhpurJharsugda
|
40007000
|
71.
|
JorhatJodhpur
|
80004000
|
72
|
JPNI Airport,PatnaJorhat
|
40008000
|
73.
|
Juhu
JPNI Airport,Patna
|
4000
|
74.
|
Junagarh (Keshod)Juhu
|
6000
|
75
|
Kadapa
Junagarh (Keshod)
|
50006000
|
76
|
KalaburagiKadapa
|
40005000
|
77.
|
KailashaharKalaburagi
|
4000
|
78.
|
KamalpurKailashahar
|
4000
|
79.
|
KandlaKamalpur
|
4000
|
80.
|
KangraKandla
|
210004000
|
81.
|
KannurKangra
|
1000021000
|
82.
|
Kanpur (Chakeri)Kannur
|
400010000
|
83.
|
Kishangarh
Kanpur (Chakeri)
|
60004000
|
84.
|
KhajurahoKishangarh
|
40006000
|
85.
|
KhandwaKhajuraho
|
50004000
|
86.
|
KolhapurKhandwa
|
60005000
|
87.
|
KolkataKolhapur
|
40006000
|
88.
|
KotaKolkata
|
4000
|
89.
|
Kullu (Bhuntar)Kota
|
230004000
|
90.
|
Kurnool
Kullu (Bhuntar)
|
500023000
|
91
|
KushinagarKurnool
|
40005000
|
92.
|
LalitpurKushinagar
|
50004000
|
93.
|
LehLalitpur
|
240005000
|
94.
|
LengpuiLeh
|
900024000
|
95.
|
LucknowLengpui
|
40009000
|
96.
|
LudhianaLucknow
|
4000
|
97.
|
MaduraiLudhiana
|
60004000
|
98.
|
MaldaMadurai
|
6000
|
99.
|
MangaloreMalda
|
9000
|
100.
|
MopaMangalore
|
60009000
|
101.
|
MoradabadMopa
|
40006000
|
102.
|
MuirpurMoradabad
|
4000
|
103.
|
Mumbai, C.S.I
Muirpur
|
4000
|
104.
|
Mumbai,Juhu
Mumbai, C.S.I
|
40006000
|
105
|
Mundra
|
4000
|
106.
|
Muzaffarpur
|
4000
|
107.
|
Mysuru
|
6000
|
108.
|
Nanded
|
4000
|
109
|
Nagpur
|
5000
|
110
|
NeyveliNavi Mumbai
|
40006000
|
111
|
North Lakhimpur (Lilabari)Neyveli
|
120004000
|
112
|
PakyongNoida
|
----5000
|
113.
|
Panagarh
North Lakhimpur (Lilabari)
|
400012000
|
114.
|
PantnagarPakyong
|
11000
----
|
115.
|
PassighatPanagarh
|
4000
|
116.
|
PrayagrajPantnagar
|
400011000
|
117.
|
PuducherryPassighat
|
4000
|
118.
|
PorbandarPrayagraj
|
60004000
|
119.
|
Port BlairPuducherry
|
4000
|
120.
|
PunePorbandar
|
70006000
|
121.
|
PuttaparthiPune
|
50007000
|
122.
|
RaipurPuttaparthi
|
5000
|
123.
|
RajahmundryRaipur
|
5000
|
124.
|
RajkotRajahmundry
|
40005000
|
125.
|
RamnadRajkot
|
4000
|
126.
|
RanchiRamnad
|
60004000
|
127.
|
RatnagiriRanchi
|
6000
|
128.
|
RewaRatnagiri
|
4000
|
129.
|
RourkelaRewa
|
60004000
|
130.
|
RupsiRourkela
|
40006000
|
131.
|
Safdarjung,DelhiRupsi
|
50004000
|
132.
|
Salem
Safdarjung,Delhi
|
70005000
|
133.
|
SatnaSalem
|
40007000
|
134.
|
ShimlaSatna
|
130004000
|
135.
|
ShirdiShimla
|
700013000
|
136
|
ShivamoggaShirdi
|
90007000
|
137.
|
SholapurShivamogga
|
50009000
|
138.
|
ShravastiSholapur
|
5000
|
139.
|
Silchar (Kumbhigram)Shravasti
|
80005000
|
140.
|
Sindhudurg
Silchar (Kumbhigram)
|
60008000
|
141.
|
SrinagarSindhudurg
|
200006000
|
142.
|
SuratSrinagar
|
400020000
|
143.
|
Thanjavur
Sri Vijaya Puram
|
4000
|
144.
|
TezpurSurat
|
70004000
|
145.
|
TezuThanjavur
|
180004000
|
146.
|
ThiruvananthapuramTezpur
|
90007000
|
147.
|
TiruchirappalliTezu
|
400018000
|
148.
|
TirupatiThiruvananthapuram
|
80009000
|
149.
|
Udaipur (Dabok)Tiruchirappalli
|
60004000
|
150.
|
UttarlaiTirupati
|
40008000
|
151.
|
Vadodara
Udaipur (Dabok)
|
40006000
|
152.
|
VaranasiUttarlai
|
4000
|
153.
|
VelloreVadodara
|
50004000
|
154.
|
VijayawadaVaranasi
|
4000
|
155.
|
VijayanagarVellore
|
5000
|
156.
|
VishakhapatnamVijayawada
|
70004000
|
157.
|
WarangalVijayanagar
|
40005000
|
|
|
Vishakhapatnam
|
7000
|
|
|
Warangal
|
4000
|
8.
|
Position reporting
|
8.1.
|
Transmission of position report
|
8.1.1.
|
The pilot shall report position as soon as possible after the aircraft has passed over each designated reporting point of ATS route defined by designated significant points. Additional reports over other points may be requested by ATC when so required for air traffic management (ATM) purposes.
|
8.1.2.
|
On routes not defined by designated significant points, position reports shall be made after the first half hour of flight and at hourly interval thereafter. Additional reports at shorter intervals of time may be requested by ATC units when so required for ATS purposes.
|
8.1.3.
|
The position reports required by 8.1.1 and 8.1.2 shall be made to the ATS unit serving the airspace in which the aircraft is operated on appropriate VHF RTF frequency/CPDLC. When outside VHF RTF range, the pilot-in-command shall report positions on HFRT/CPDLC in addition, the last position report before passing from one flight information region or control area to an adjacent flight information region or control area shall be made to the ATS unit serving the airspace about to be entered.
|
8.1.4.
|
Flights may be exempted from making position reports at each designated reporting point or interval, if adequate flight progress data is available from radar.
|
8.1.5.
|
All aircraft transiting from one FIR to another FIR shall transmit for FIR boundary and flight level to the ATS unit serving the FIR to be entered at least 10 minutes prior to entry.
|
|
NOTE-
|
|
This provision will not apply to aircraft transiting from one Indian FIR to another Indian FIR. Provisions will continue to apply to all aircraft, when transiting from a foreign FIR to an Indian FIR except where specifically indicated otherwise against an ATS route.
|
8.1.6.
|
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-
|
|
i) Call-sign of the aircraft
|
|
ii) Estimate time of crossing the route
|
|
iii) Flight level
|
|
iv) 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 Degrees, to the direction of the route and at a level appropriate to the magnetic track.
|
8.1.7.
|
Listening watch shall be maintained on appropriate communication frequency throughout the flight along the ATS routes.
|
|
|
9.
|
Content of the position report
|
9.1.
|
When reporting their position, pilots shall transmit the word ‘POSITION’ either immediately before or after the call-sign of their aircraft.
|
|
|
9.2.
|
Position reports shall have the following elements of information-
|
|
i) aircraft identification
|
|
ii) position
|
|
iii) time
|
|
iv) flight level or altitude
|
|
v) next position and time over
|
|
vi) ensuing significant point
|
|
|
9.3.
|
Routine air-report
|
9.3.1.
|
Pilots shall give the following meteorological information once in each FIR along with position report at designated MET reporting points on international and national ATS routes as detailed on page GEN 3.5-6.
|
|
|
9.3.2.
|
Meteorological information
|
|
i) air temperature
|
|
ii) wind direction
|
|
iii) wind speed
|
|
iv) turbulence
|
|
v) aircraft icing
|
|
vi) humidity (if available)
|
9.4.
|
Special air-report
|
9.4.1.
|
Special air-report shall be made by all aircraft whenever anyone or more of the following conditions are encountered or observed-
|
|
i) Clear air turbulence
|
|
ii) Severe turbulence
|
|
iii) Severe icing
|
|
iv) Severe mountain wave
|
|
v) Thunder storms without hail that are obscured, embedded, widespread or in squall-lines
|
|
vi) Thunder storm with hail that are obscured, embedded, widespread or in squall-lines
|
|
vii) Heavy dust storm or heavy sandstorm
|
|
viii) Volcanic ash cloud
|
|
ix) Pre-eruption volcanic activity or a volcanic eruption
|
|
|
9.5.
|
Transmission of ADS report
|
9.5.1.
|
The position report shall be made automatically to the air traffic service unit serving the airspace in which the aircraft is operating. The requirement for transmission and content of ADS report shall be established by the controlling ATC unit on the basis of current operational conditions and communicated to the aircraft and acknowledged through an ADS agreement.
|
9.5.2.
|
Content of the ADS report
|
9.5.2.1.
|
ADS report shall be composed of data-blocks selected from the following
|
|
i) Basic ADS - Latitude, Longitude, Altitude, Time, Figure of merit
|
|
ii) Ground vector - Track, Ground speed, Rate of climb or descent
|
|
iii) Air vector - Heading, Mach or IAS, Rate of climb or descent
|
|
iv) Projected profile - Next way-point, Estimated altitude at next way-point, Estimated time at next way-point, (Next+1) way-point, Estimated altitude at (Next+1) way-point, Estimated time at (Next+1) way-point
|
|
v) Meteorological information - Wind speed, Wind direction, Temperature, Turbulence (if available), Humidity (if available)
|
|
vi) Short-term intent - Latitude at projected intent point, Longitude at projected intent point, Altitude at projected intent point, Time of projection
|
|
vii) If an altitude, track or speed change is predicted to occur between the aircraft’s current position and the projected intent point, additional information would be provided in an intermediate intent block as - Distance from current point to change point, Track from current to change point, Altitude at change point, Predicted time to change point.
|
|
viii) Extended projected profile (in response to an interrogation from the ground system) - Next way-point, Estimated altitude at the next way-point, Estimated time at next way-point, (Next+1) way-point, Estimated altitude at (Next+1) way-point, Estimated time at (Next+1) way-point, (Next+2) way-point, Estimated altitude at (Next+2) way-point, Estimated time at (Next+2) way-point (repeated fir upto [Next+128] waypoints).
|
9.5.3.
|
The basic ADS data block shall be required from all ADS equipped aircraft. Remaining ADS data blocks shall be included as necessary. In addition to any requirement concerning its transmission for ATS purposes, data block at v) Meteorological information shall be transmitted in accordance with Annex 2, para 5.4.1.
|
9.5.4.
|
In addition to the above data blocks, other information shall be transmitted, including a block identifier, aircraft identification and 24-bit aircraft address.
|