|
1
|
Use of aircraft stand identification signs, taxiway guidelines and visual docking/parking guidance system at aircraft stands
|
Continuous nose-wheel guide lines available at
MARS (Multiple Aircraft Ramp System) Centre
stands for use of wide body aircraft and in single
aircraft stands. Broken nose-wheel guide lines of
left & right MARS stand for narrow bodied
ACFT. All stands are provided with stand
identification signs. Nose-wheel guide lines at
apron. Taxing guidance signages are provided on
all TWY intersections, straight section and
holding positions as per ICAO Annex-14
Advanced Visual Docking Guidance System
(AVDGS) are provided by Safegate available on
nose-in parking stands of T-3 AVDGS not
available at following contact stands at T-3:
(1) L & R stands of A08, A10, A12, A14, A01,
A03
(2) Central stands of C27, C28, C29, C30, C31,
C32 and 34.
(3) Remote stands except R02 and R03. Docking
of aircraft is done with the help of marshaller at
remote parking stands and other contact stands
where AVDGS is not provided at Apron I, II, III
and cargo.
|
|
2
|
Runway and taxiway markings and lights
|
RWY
Markings
Designation, THR, TDZ,Center line, Edge, Ends
Lights
THR, TDZ, Centre Line, Edge, Ends, Wing Bars, RETIL, Stop way (RWY 11)
TWY
Marking
Centerline, Holding position, ( Pattern A & B ) TWY Edge, Intermediate Holding Position, Enhanced RWY Holding Position markings
Lights
Edge LGTS on curves except E1, F1 and F4, Intermediate Holding Position TWY S2 north of TWY Z, TWY S4 north of TWY Z and TWY S5 north of TWY Z. Runway crossing lights between TWY C & W, M & D, N & K and vice versa & CL LGTS.
|
|
3
|
Stop bars (if any)
|
At TWY C, D (RHP28), E (RHP28), E4, K (RHP28), P1, W, M, M2, N, CE1, CE2, S4, S5, Z1, Z2, Z3, Z4, Z5, Z6, Z7, Z8, Z9, Y (AT two locations EAST OF CW1/Y intersection and west OF CW2/Y intersection), T (east of CW1/T intersection), CW1(south OF S/CW1 intersection),CW2 (at two locations: north of T/CW2 intersection, south of S/CW2 intersection)
|
|
4
|
Remarks
|
1. RWY guard lights are provided at each RWY and TWY
intersection.
2.TWY Center lines LGT of RWY 09/27 are uniformly offset to the
south side of RWY CL with a lateral separation of 15m BTN LGT.
3.TWY Edge LGT AVBL on curved portion of TWY S, E2, E, E4, B,
C, F, D, D1, R, R1, L1, M1, L, V, W, P1, E3, E5, N, C1, A, M and K.
4. An illuminated wind direction indicator in the form of truncated
cone made of fabric of black and white colour in bands has been
installed between TWY D and K (Coordinates 283401.9N
0770529.7E) near RWY10.
|
|
1
|
Name of the associated meteorological office
|
Delhi
|
|
2
|
Hours of service and, where applicable, the designation of the responsible meteorological office outside these hours
|
H24
|
|
3
|
Office responsible for preparation of TAFs and periods of validity and interval of issuance of the forecasts
|
Delhi
9 and 24HR
|
|
4
|
Availability of the trend forecast for the aerodrome and interval of issuance
|
Trend
30 Min
|
|
5
|
Information on how briefing and/or consultation is provided
|
Provided
|
|
6
|
Types of flight documentation supplied and language(s) used in flight documentation
|
Chart form and Tabular form English
|
|
7
|
Charts and other information displayed or available for briefing or consultation
|
S,U85,U70,U50,U30,U25,U15,U10, P30, P25, P20 SW [ UPTO FL460]
|
|
8
|
Supplementary equipment available for providing information on meteorological conditions, e.g. weather radar and receiver for satellite images;
|
Telex, Telefax, Satellite display work Station
|
|
9
|
The air traffic services unit(s) provided with meteorological information
|
VIDP Delhi ATC AND ACS
|
|
10
|
Additional information, e.g. concerning any limitation of service.
|
1. Integrated Aviation METROLOGICAL System at RWY 27 AVBL. The System will provide following information on Digital Display:
PAGE 1:
I Wind Direction 2 Minute Average
II Wind Speed 2Minute Average
III RVR Actual Reading below 2000 M and 2001M when it exceeds above 2000M
PAGE 2:
I Wind Direction: 2 Minute Max
II RVR Optimal: Actual Reading
III RVR Trend: U for up, D for down, N for no change.
PAGE3:
I Air Temperature: Actual Dry Bulb Temperature
II Humidity: Actual Humidity in Percent
III DEW Point Temperature: In Degree Celsius PAGE4:
I Air Pressure: on HPA
II QNH: in HPA.
2. Transmissometer at TDZ RWY 09 AVBL. RVR displayed actual reading between 50 to 2000M
3. RVR System DRISHTI installed at RWY29 beginning and RWY11 beginning. The system will provide RVR and MOR data displaced on PC monitor as follows:
I.) RVR: Actual reading displayed from 50m to 2000m in following steps:
000M to 800M in step of 25M
800M to 1200M in step of 50M
1200M to 2000M in step of 100M
A value of 2000M is displayed when RVR is equal to or above 2000M.
A value of 25M is displayed when RVR is less than 50M.
II.) RVR TREND: Displayed upward arrow for uptrend and downward arrow for down trend.
1. MOR: Actual MOR is displayed from 50M to
2. 3000M in following steps.
000M to 800M in step of 25M
800M to 1200M in step of 50M
1200M to 2000M in step of 100M
A value of 3000M is displayed when MOR is equal to or above 3000M
5.LASER ceilometers installed near TDZ RWY 28.The system will provide the height of base of low cloud (in Meters/Feet) in two layers as well as vertical visibility, Laser ceilometers will give height of base of low cloud from 10M up to 7500M with resolution of 10M.
|
|
1
|
Location, characteristics and hours of operation of aerodrome beacon/identification beacon (if any)
|
ABN
|
283337N 0770536E, Rotating green /white beacon on top of Apron
Management service tower (Apron- II). FLG W AND G, 24FPM, 400,000
Cd, SUNSET TO SUNRISE
|
|
IBN
|
NIL
|
|
2
|
Location and lighting (if any) of anemometer/landing direction indicator;
|
LDI
|
On west of TWY C and north of RWY 10/28
|
|
Anemometer
|
1. 390M from THR28, Lighted 2. 300M from THR10, Lighted
3. 780M from THR27, Lighted. 4. 460M from THR29, Lighted
5. 480M from THR11, Lighted
|
|
3
|
Taxiway edge and taxiway centre line lights;
|
Edge
|
All TWY curves except TWY J and TWY H which have reflective edge markers
|
|
Centre Line
|
TWY P, N,M,M1,M2,L,L1,L2,R,R1,R2
,R3,R4,S,U,V,W,P1,K,D,D1,C,C1,B,B2,B3,E2,E3,E4
E5,F,F2,F3,A,RWY 27/09 and All Taxiways Of Terminal-3
|
|
4
|
Secondary power supply including switch-over time;
|
SECONDARY POWER SUPPLY TO ALL LIGHTING.
SWITCH OVER TIME :
CAT- IIIB : 1 SEC
CAT- II : 2 SEC
CAT- I : 15 SEC
ONLINE UPS AVBL FOR CRITICAL CIRCUITS.
|
|
5
|
Remarks
|
CAT-III A/B BSES supply through online UPS as primary source and DG supply as secondary source.
|
|
Aircraft Stands
|
Procedure
|
|
RWY in use 28
|
RWY in use 09/27/11/29/10
|
|
Front Apron 1
|
|
1-12
|
The aircraft shall be pushed back
onto taxilane facing South and to
be towed up to tug disconnecting
point X1(1-4), X2(5-9), X3(10-12) respectively and follow further instructions from ATC
|
The aircraft shall be pushed back onto taxilane facing North and to be towed up to tug disconnecting point Y1(1-4) or Y2(5-9) or Y3(10-12) respectively and follow further instructions from ATC
|
|
15-17
|
The aircraft shall power out onto
taxilane facing South and follow
further instructions from ATC
|
The aircraft shall power out onto taxi lane facing North and follow further instructions from ATC
|
|
19-30
|
The aircraft shall power out onto
taxi lane facing South, follow
further instructions from ATC
|
The aircraft shall power out onto taxi lane facing North, follow further instructions from ATC
|
|
31-40C
|
The aircraft shall power out onto taxi lane facing South follow further
instructions from ATC
|
|
Satellite Apron 1
|
|
120-132
|
The aircraft shall power out onto
taxi lane facing South-East, follow further instructions from ATC
|
The aircraft shall power out onto taxi lane facing North-West, follow further instructions from ATC
|
|
135-142
|
The aircraft shall be pushed back
onto taxilane facing South East and to be towed up to tug disconnecting point X4, follow further instructions from ATC
|
The aircraft shall be pushed back onto taxilane facing North West and to be towed up to tug disconnecting point Y4, follow further instructions from ATC
|
|
143-147
|
The aircraft shall be pushed back
onto taxilane, facing South East
and to be towed up to tug
disconnecting point X5, follow
further instructions from ATC
|
The aircraft shall be pushed back onto taxilane, facing North West and to be towed up to tug disconnecting point Y5, follow further instructions from ATC
|
|
148-152
|
The aircraft shall be pushed back
onto taxilane facing South East and to be towed up to tug disconnecting point X6, follow further instructions from ATC
|
The aircraft shall be pushed back onto taxilane facing North West and to be towed up to tug disconnecting point Y6, follow further instructions from ATC
|
|
General Aviation Apron
|
|
161-188
|
The aircraft shall power out onto central taxilane joining F4, follow further instructions from ATC
|
|
APRON-II
|
|
Aircraft Stands
|
Procedure
|
|
41-44, 45L43
|
The aircraft shall be pushed back onto TWY R1 facing North north and to be towedbe
towed abeam stand 43 42 and follow further instructions from ATC.
|
|
44,45L,45R, 46L, 46R
|
The aircraft shall be pushed back onto TWY R3 R1 facing East or west as per thenorth and to be
RWY in use towed abeam stand 45L and follow further instructions from ATC.
(Aircraft taxing towards east on TWY R3 shall hold at IHP on TWY
R3-R4 junction and aircraft taxing towards west on TWY R3 shall
hold at IHP on TWY M1/R1/ R3 junction while aircraft is pushing back
from stands 45R and 46L . Simultaneous pushback from stands 46L
and 81R , 81L, 82R not allowed ).
|
|
46R,47L/,47R, ,48
|
The aircraft shall be pushed back onto TWY R2 facing North-East and to be
The aircraft shall be pushed back onto TWY R2 facing north-east and to be towed abeam stand 47R and follow further instructions from ATC.
(Aircraft taxing towards east on TWY R3 shall hold at IHP on TWY R3-R4 junction and aircraft taxing towards WEST on TWY R3 shall hold at IHP on TWY M1/R1/ R3 Junction while aircraft is pushing back from stands 46 R. Simultaneous pushback from stands 46R and 81R to 83R not allowed . Also simultaneous pushback from stands 47L and 82L, 82R not allowed.)
|
|
49
|
The aircraft shall be pushed back onto TWY R4 facing South-east and to be
towed abeam stand 47R and follow further instructions from ATC.
|
|
81R-92
|
The aircraft shall be pushed back onto Taxiway R3 facing East or West as per
the RWY in use and follow further instructions from ATC.
Simultaneous pushback from stands A12,A12R, A14, A14L, A14R and
88 TO 92 not allowed
|
|
Note:
i. On stands 41 - 45L 43 (Block 1), only one pushback allowed at a time.
ii. On stands 45R, 44-46L and 46R (Block 2), only one pushback allowed at a time
iii. On stands 47L 46R - 49 (Block 3), only one pushback allowed at a time.
iv. On stands 41-46L and 81R-92, Pushback clearance is to be separated by three stands.
|
|
CARGO APRON
|
|
AIRCRAFT
STANDS
|
PROCEDURE
|
|
Departure via TWY L2
|
|
98, 99, 100, 104 & 105
|
Push back on to taxiway R facing east and tow up to tug disconnect point CA1. Only one push back is allowed from these stands at a time.
|
|
101, 102, 103 & 106
|
Push back on to taxiway R facing east and tow up to tug disconnect point CA2. Only one push back is allowed from these stands at a time.
|
|
Departure via TWY L1
|
|
98, 99, 100,104 & 105
|
Push back on taxiway R facing west and tow up to tug disconnect point CA3. Only one push back is allowed from these stands at a time.
|
|
101, 102, 103 & 106
|
Push back on taxiway R facing west and tow up to tug disconnect point CA4. Only one push back is allowed from these stands at a time.
|
|
AIRCRAFT
STANDS
|
PROCEDURE
|
|
RWY IN USE 10-28 OR 11-29
|
|
APRON 31
|
|
A06 TO A14
|
The aircraft shall be pushed back onto taxilane facing North West and to be towed up to tug disconnecting point A1, follow further instructions from ATC
|
|
APRON 32
|
|
A07 TO A13
|
The aircraft shall be pushed back onto taxi lane facing North West and to be towed up to tug disconnecting point A2 , Taxi via W3, follow further instructions from ATC
|
|
A01 TO 03
|
The aircraft shall be pushed back onto taxilane facing North and to be towed up to tug disconnecting point A3, Taxi via W3, follow further instructions from ATC
|
|
B15 TO B21
|
The aircraft shall be pushed back onto taxilane, facing North East and to be towed up to tug disconnecting point A4, Taxi via W3, follow further instructions from ATC
|
|
R01 TO R02
|
The aircraft shall be pushed back onto taxilane facing North West and to be towed up to tug disconnecting point A2, Taxi via W3, follow further instructions from ATC
|
|
R03 TO R04
|
The aircraft shall be pushed back onto taxilane, facing North East and to be towed up to tug disconnecting point A4, Taxi via W3, follow further instructions from ATC
|
|
APRON 33
|
|
B18 TO B22
|
The aircraft shall be pushed back onto taxi lane facing South West and to be towed up to tug disconnecting point B1, Taxi via W1, follow further instructions from ATC
|
|
B24 TO B26
|
The aircraft shall be pushed back onto taxi lane facing South West and to be towed up to tug disconnecting point B2, Taxi via W1, follow further instructions from ATC
|
|
C28 TO C30
|
The aircraft shall be pushed back onto taxilane, facing South West and to be towed up to tug disconnecting point C1, Taxi via T3, follow further instructions from ATC
|
|
C32 TO C36
|
The aircraft shall be pushed back onto taxilane facing South West and to be towed up to tug disconnecting point C2, Taxi via T3, follow further instructions from ATC
|
|
APRON 34
|
|
C27 TO C33
|
RWY IN USE 28/29
|
|
The aircraft shall be pushed back onto taxilane facing North East and to be towed up to tug disconnecting point D5; Taxi via S3, follow further instructions from ATC
|
|
RWY IN USE 10/11
|
|
The aircraft shall be pushed back onto taxilane facing South West and to be towed up to tug disconnecting point C3; Taxi via T2, follow further instructions from ATC
|
|
D37 TO D41
|
RWY IN USE 28/29
|
|
The aircraft shall be pushed back onto taxilane facing East and to be towed up to tug disconnecting point D4, Taxi via S3, follow further instructions from ATC
|
|
RWY IN USE 10/11
|
|
The aircraft shall be pushed back onto taxilane facing West and to be towed up to tug disconnecting point C4, Taxi via T2, follow further instructions from ATC
|
|
D43 TO D55
|
RWY IN USE 28/29
|
|
The aircraft shall be pushed back onto taxilane facing South East and to be towed up to tug disconnecting point D3, Taxi via S3, follow further instructions from ATC.
|
|
RWY IN USE 10/11
|
|
The aircraft shall be pushed back onto taxilane facing North West and to be towed up to tug disconnecting point C5, Taxi via T2, follow further instructions from ATC.
|
|
R05 TO R06
|
RWY IN USE 28/29
|
|
The aircraft shall be pushed back onto taxilane facing North East and to be towed up to tug disconnecting point D5; Taxi via S3, follow further instructions from ATC
|
|
RWY IN USE 10/11
|
|
The aircraft shall be pushed back onto taxilane facing South West and to be towed up to tug disconnecting point C3; Taxi via T2, follow further instructions from ATC
|
|
R07 TO R08
|
RWY IN USE 28/29
|
|
The aircraft shall be pushed back onto taxilane facing East and to be towed up to tug disconnecting point D4, Taxi via S3, follow further instructions from ATC
|
|
RWY IN USE 10/11
|
|
The aircraft shall be pushed back onto taxilane facing West and to be towed up to tug disconnecting point C4, Taxi via T2, follow further instructions from ATC
|
|
R09
|
RWY IN USE 28/29
|
|
The aircraft shall be pushed back onto taxilane facing South East and to be towed up to tug disconnecting point D3, Taxi via S3, follow further instructions from ATC
|
|
RWY IN USE 10/11
|
|
The aircraft shall be pushed back onto taxilane facing North West and to be towed up to tug disconnecting point C5, Taxi via T2, follow further instructions from ATC
|
|
APRON 35
|
|
RWY IN USE 10-28 OR 11-29
|
|
D46 TO D52
|
The aircraft shall be pushed back onto taxilane facing South East and to be towed up to tug disconnecting point D1, Taxi via T1, follow further instructions from ATC
|
|
D54 TO D62
|
The aircraft shall be pushed back onto taxilane facing South East and to be towed up to tug disconnecting point D2, Taxi via T1, follow further instructions from ATC
|
|
E64 TO E68
|
The aircraft shall be pushed back onto taxilane facing South East and to be towed up to tug disconnecting point E1, Taxi via T1A, follow further instructions from ATC
|
|
E70 TO E72
|
The aircraft shall be pushed back onto taxilane facing South East and to be pulled forward up to tug disconnecting point E1, Taxi via T1A,follow further instructions from ATC
|
|
E74 TO E84
|
The aircraft shall be pushed back onto taxilane behind the stand facing South East, Taxi via T1A, follow further instructions from ATC
|
|
•
Note:
i. PCN Value of aprons 31 to 35 is revised to 110/R/C/W/T
ii. Location of TDPs (Tug Disconnect Points)
a) Apron 31
A1: Behind Stand A12
b) Apron 32
A2: BTN stands A09 & A1 B3: Behind stand B17R
A3: Behind stand A03 B4: Behind stand A01
A4: Behind stand B15 B5: Behind stand A07
c) Apron 33A
B1: Behind Stand B22L B2: Behind stand B26L
d) Apron 33B
C1: Behind stand C32 C2: Behind stand C36
e) Apron 34
C3: BTN stands C29L D3: Behind stand D51
C4: Behind stand D37 D4: Behind stand D41
C5: Behind stand D45 D5: Behind stand C27L
f) Apron 35
D1: Behind stand D54
D2: Behind stand D62
E1: Behind stand E70
g) Push-back of both Wide-body and Narrow-body Aircraft from Bays A14, A12, A13, A11, B19, B21, C33, C31, D53 and D55 onto Aprons infringe the taxi clearance strip for S, CW1 and T taxiways respectively with either Tail or Wingtip. Arriving aircraft will taxi on outside Taxiways CW2 and Y and these aircraft may be required to hold short of adjoining taxiways such as R5, W3, W2, T2 and S3 on CW2 or Y. Departing aircraft taxiing R3-S-CW1-T may be required to hold short of the adjoining taxiways such as R5, W3, W2, T2 and S3 on CW1 or T respectively until tail / wing-tip of push back aircraft has cleared the intersections. Additional CCTV feeds to monitors in the tower will assist SMC in ensuring that affected taxiways are clear of obstructions prior to instructing holding aircraft to proceed.
|
|
h) For a Wide-body Code D/E/F aircraft pushing back from an aircraft bay, there should always be 2 Code E/F stands (respectively) separation from another aircraft pushing back from adjacent bays. AOCC will not allocate an adjacent aircraft bay to aircraft requiring push-back within 20 minutes of an another aircraft push-back within 2 parking stands.
i) In case of APU failure, aircraft may be permitted to start one/both starboard side engines on idle power, at the parking stand itself with the aerobridge attached.
j) In case of corner stands A06, A13, B21, B18, C28, C33, D55 and D46 in T3 apron, aircraft can start 01 engine at idle power only while being pulled forward to the respective Tug Disconnect Point. No engine start up permitted during push back.
k) No Cross-Bleed start by aircraft is permitted during push back. It is permissible only after the towing of the aircraft (push back and pull forward) is complete.
l) During LVP, start up with idle power during push back is not permitted.
m) With respect to Corner Parking Stands, the following limitations for push-back instructions are to be observed by ATCOs when Code E/F aircraft is pushing back from the following stands:
iii. Push-Back from B15:
• To TDP A4, stand A01 shall not push-back (A03 to push-back to A3)
• To TDP B4, stand A01 and A03 shall not push-back
iv. Push-Back from B18/C28L:
• Simultaneous push-back from stands B18 and C28L not allowed.
v. Push-back from A01:
|
|
• To TDP A: A03, B15 and B17 shall not push-back (B15 & 17 can push-back to TDP A4 once aircraft on A01 has completed pushed back and pulled to A3)
• To TDP B4: B15, A03 & A07 shall not push-back (A07 can push back to TDP B5 once A01 has completed pushed back and pulled to B4)
vi. Push-back from A03:
• To TDP A3: A01, B15 may not push-back (B15 may push-back to A4 once aircraft from A03 has completed pushed back and pulled to A3)
• To TDP B4: B15, A01, A07 and A09 may not push-back (A07 & A09 may push-back to B5 once A03 has completed pushed back and pulled to B4)
vii. Push-back from A07:
• To TDP A2: A01, A03 and A09 shall not pushback (A01 & A03 can push-back to TDP A3 once aircraft on A07 has completed pushed back and pulled to A2)
• To TDP B: A03 & A09 shall not push-back
viii. Push-back from C27:
• To TDP D5: C29 and D37 shall not pushback (D39 can push back to D4 once aircraft on C27 has completed pushed back and pulled to D5)
• To TDP C: D37, D39 shall not push-back (D37 or D39 can push-back to C4 once C27 has completed pushed back and pulled to C3)
ix. Push-back from D37:
• To TDP D: C27, C29 and D39 shall not pushback (D39 can push-back to D4 once aircraft on C27 has completed pushed back and pulled to D5)
• To TDP C3: D37, D39 shall not push back (D37 or D39 can push back to C4 once C27 has completed pushed back and pulled to C3)
x. Push-back from D39:
• To TDP D4: D41, D37 and C27 shall not pushback (C27 can push back to D5 once aircraft on D39 has completed pushed back and pulled to D4)
|
|
• To TDP C4: D43, D41, D37 and C27 shall not pushback (D41 & D43 can push back to C5 once D39 has completed pushed back and pulled to C4)
xi. Push-back from D41:
• To TDP D4: D43, D39 shall not push back (D37 can push back to D5 once aircraft on D41 has completed pushed back and pulled to D4)
• To TDP C4: D43, D45, D39 and D37 shall not pushback (D43/D45 can push back to C5 once D41 has completed pushed back and pulled to C4)
xii. For all other Code C stands, there should be at least 2 Code C stands (1 Code E/F MARS Stand) separating push-backs.
xiii. From Apron-a. From APRON 33A, only one Code - code E aircraft can push back pushback at one a time.
b. From APRON 33B, only one code E aircraft can pushback at a time.
c. Simultaneous pushback of code E aircraft on TDP B1 and C1 not allowed.
d. Simultaneous pushback of code E aircraft on TDP B2 and C2 not allowed.
xiv. For Apron 35-
a. Only one push back from stands E64 to E72 is permitted at a time
b. In case of push back of A320 or equivalent aircraft on E64 -E68, no push back/pull forward is permitted for aircraft parked on D46 to D56 and E70 and E72.
c. When aircraft on stand D46 to D56 will push back, no push back is allowed from E64 to E68.
d. Simultaneous push back from adjacent parking stands is not permitted
e. Similar restriction on leaving one adjacent stand will be applicable between arrival/arrival and arrival/pushing back aircraft.
f. The aircraft taxiing in/out on stands D46 to D62 shall use taxilane T1
g. Aircraft taxiing in/out stands E68 to E84 shall use taxilane T1A
h. Arriving aircraft to stands E64 to E66 shall use T1
4. A-320 HANGAR
i. TDPs (Tug Disconnect Point)
GA4: On TWY-J between service road and A-320 dispersal area
ii. Start -up procedure:
Fixed wing aircraft/ Helicopter
At TDP GA4, facing north
TWY-P will be available
|
|
iii. Engine Run up at Idle Power:
Fixed wing aircraft
a) On any of the vacant parking stands, to be allocated by AOCC, or
b) At TDP GA4, nose facing north
c) At the run up bay adjacent to stand-1 in apron-1, or
d) At dumbbell of TWY-T, east of TWY-Z2
Helicopter
On GA4, nose facing north
iv. Engine run up at high power:
Fixed wing aircraft/Helicopter
a) At the run up bay adjacent to stand-1 in apron-1, up to type code C or
b) At dumbbell of TWY -T, east of TWY-Z2, up to type code F
5. STANDS 801, 802
|
|
|
C33, C31L,C31R, C29L,C29R, C27L,C27R
|
WESTERLY MODE
|
*Ensure no aircraft is at transition
lane Q1 before permitting any push-back from stands C27R, 27L and C29R.
*When aircraft is positioned on TDP BC1, arrival aircraft can taxi-in to other stands of Block-1except C29L, C29R, and C27L.
|
|
|
|
|
|
|
D37L, D37R,
D39L, D39R,
D41
|
WESTERLY MODE
|
*Ensure no aircraft is at transition lanes Q1 & Q2 before permitting any push-back from Block-2.
*When aircraft is positioned on TDP BC2, arrival aircraft can taxi-in to other stands of Block-2 except D37R, D39L and D39R.
|
taxi-lane facing East and to be towed up to
tug disconnecting point BC2; Taxi via S3,
follow further instructions from ATC
|
|
|
taxi-lane facing West and to be towed up to
tug disconnecting point BC2; Taxi via T2,
follow further instructions from ATC
|
D43, D45,
D47, D49,
D51, D53,
D55
|
WESTERLY MODE
|
*Ensure no aircraft is at transition lane
Q2 before permitting any push-back
from stands D43, D45 and D47.
*When aircraft is positioned on TDP
BC3, arrival aircraft can taxi in to
other stands of Block-3 except D45,
D47 and D49.
|
|
|
|
|
|
|
R05, R06
|
WESTERLY MODE
|
*Ensure no aircraft is at transition lane Q1 before permitting any push-back from Block-4.
*When aircraft is holding on TDP OC1, no arrival aircraft can taxi into stands of Block-4.
|
|
|
|
|
|
|
R07L, R07R,
R08L, R08R
|
WESTERLY MODE
|
*Ensure no aircraft is at transition lanes Q1 & Q2 before permitting any push-back from Block-5.
* When aircraft is holding on TDP OC2, arrival aircraft can taxi into other stands of Block-5 except R07R and R07L and R08R.
|
from ATC.
|
|
|
|
|
R09
|
WESTERLY MODE
|
*Ensure no aircraft is at transition lane Q2 before permitting any push-back from Block-6.
*When aircraft is holding on TDP OC3, no arrival aircraft can taxi into stands of Block-6.
|
|
|
|
|
|
|
|
|
|
|
|
|
T2 Blue Lane
|
T2 Orange Lane
|
REMARKS
|
C31R
|
Use central taxi-lane to stand
|
Whenever an aircraft
is permitted to enter
via TWY T2 to any
of the dual taxi-lanes,
no aircraft shall be
allowed to push-back
from Block 1 and
Block 4.
|
C27L, C27R
|
Enter apron via T2 Blue
taxi-lane to stand
|
Not permitted
|
D39L, D39R
|
Enter apron via T2 Blue
taxi-lane to stand
|
Enter apron via T2 Orange taxi-lane and use transition lane Q1 to stand
|
D47, D49, D51
|
Enter apron via T2 Blue
taxi-lane to stand
|
Enter apron via T2 Orange taxi-lane and use transition lanes Q1 or Q2 to stand
|
|
|
Enter apron via T2 Blue
taxi-lane and use central
|
taxi-lane to stand
Enter apron via T2 Orange
taxi-lane and use central
taxi-lane to stand
|
|
|
Not permitted
|
Enter apron via T2 Orange taxi-lane to stand
|
R08L, R08R
|
Enter apron via T2 Blue
taxi-lane and use transition lane Q1 to stand
|
Enter apron via T2 Orange taxi-lane to stand
|
|
|
Enter apron via T2 Blue taxi-lane and use transition lanes Q1 or Q2 to stand
|
Enter apron via T2 Orange taxi-lane to stand
|
|
|
|
|
T2 Blue Lane
|
T2 Orange Lane
|
REMARKS
|
|
|
Enter apron via T2Blue
taxi-lane and use central
taxi-lane to stand
|
Enter apron via T2 Orange taxi-lane and use central taxi-lane to stand
|
Whenever an aircraft
is permitted to enter
via TWY S3 to any
of the dual taxi-lanes,
no aircraft shall be
allowed to push-back
from Block 3 and
Block 6.
|
C29R, C27L,
C27R
|
Enter apron via T2 Blue
taxi-lane to stand
|
Enter apron via T2 Orange lane and use transition lanes Q1 or Q2 to stand
|
D39L, D39R,
D41
|
Enter apron via T2 Blue
taxi-lane to stand
|
Enter apron via T2 Orange taxi-lane and use transition lane Q2 to stand
|
D49
|
Enter apron via T2 Blue
taxi-lane to stand
|
Not permitted
|
|
|
Use central taxi-lane to stand
|
|
|
Enter apron via T2 Blue
taxi-lane and use transition lanes Q1 or Q2 to stand
|
Enter apron via T2 Orange
taxi-lane to stand
|
R08L, R08R
|
Enter apron via T2 Blue
taxi-lane and use transition lane Q2 to stand
|
Enter apron via T2 Orange taxi-lane to stand
|
|
|
Not permitted
|
Enter apron via T2 Orange taxi-lane to stand
|
i. Aircraft pushing back from stands C33, C31L, C31R, D53 and D55 would infringe into TWY-T.
ii. Transition lanes Q1 and Q2 can be used for transition between dual taxi-lanes, provided all the push-back/ taxiing
aircraft are positioned at respective TDPs as specified in para 2.8 & 2.9 above. However, in case, where immediate
transition between dual taxi-lanes is required anywhere other than transition lanes Q1 & Q2, to resolve or to
expedite the traffic; Follow-Me service will be provided for transition among the dual taxi-lanes.
|
|
NOTE: If required by ATC the length of intermediate segment may be reduced to less than 5 NM.
II. RADIO COMMUNICATION FAILURE PROCEDURE
1. INTRODUCTION:
Radio communication failure procedures are described in Para 15.3 of ICAO PANS ATM DOC 4444, 15th edition 2007. Based on these provisions, following radio communication failure procedures are established, to standardize the actions to be taken by the pilot of arriving and departing aircraft at IGI airport.
2. GENERAL:
2.1. All Transponder equipped aircraft experiencing Radio Communication failure shall set transponder to Mode A/C code 7600 as soon as practicable.
(Note: This Requirement of Setting transponder to Mode A/C code 7600 in no way imposes any restriction on the pilot’s decision to set transponder to Mode A/C code 7500 or 7700, whenever required).
2.2. Pilot shall not overfly VIP 89 (Prohibited area) situated 5.8 NM North East of Delhi Airport under any circumstances.
|
|
3. ASSIGNED RUNWAY AND ITS AVAILABILITY FOR RCF AIRCRAFT:
3.1. In case of arriving aircraft, when Runway for landing has already been advised to the aircraft by ATC, such runway shall be considered as assigned runway, except as given in para 3.3 below. In case arriving aircraft has not been advised any runway, Runway 28 shall be considered as assigned runway for such arrival. During the period of notified periods of maintenance/closure of Runway 28, Runway 29 shall be considered as assigned Runway.
3.2. In case of departures from Delhi returning on account of RCF, the departure runway of such aircraft shall be considered as assigned runway for landing, except as given in para 3.3 below.
3.3. Runway 09 or 27 is not to be used by RCF aircraft except as under para 3.4 & 3.5 below. Runway 28, therefore, shall be treated as assigned Runway for aircraft to which Runway 27 had been assigned previously as per para 3.1 and departure from Runway 27 as per para 3.2 above. Similarly, Runway 10 shall be treated as assigned Runway for aircraft to which Runway 09 had been assigned previously as per para 3.1 and departure from Runway 09 as per para 3.2 above.
3.4. Notwithstanding anything contained in para 3.3 above, if Radio communication failure occurs after the final/interception turn, the aircraft may continue its approach to land on such Runway.
3.5. It is reiterated for clarity, aircraft experiencing RCF shall not make an approach for Runway 27 or Runway 09 unless final turn/interception heading has already been given to aircraft for Runway 27 or Runway 09 (see para 3.4).
3.6. Runway lights and Approach lights in ‘SWITCHED ON’ position shall indicate the availability of such Runway for aircraft experiencing RCF.
3.7. Irrespective of visibility/weather conditions, Runway and Approach lights in ‘SWITCHED OFF’ position shall indicate non- availability of such Runway for aircraft experiencing RCF. In such cases, alternate runway shall be made available for such aircraft. Runway 29 shall be alternate to Runway 28 and Runway 11 shall be alternate to Runway 10. Accordingly, Runway 28 shall be alternate to Runway 29 and Runway 10 shall be alternate to Runway 11.
3.8. In strong tail wind conditions for assigned Runway, aircraft experiencing RCF will carry out a missed approach on assigned runway and after following complete missed approach for such approach, aircraft will carry out published ILS/VOR DME ARC approach procedure for the runway which is in opposite direction to the assigned Runway. For example, Runway 10 in case of Runway 28 and Runway 11 in case of Runway 29 and vice versa.
|
|
4. PROCEDURE FOR ARRIVALS:
4.1. ARRIVING AIRCRAFT - STAR-ASSIGNED
When STAR has been assigned to arrival:
4.1.1 Except when descend clearance has already been received from ATC, pilot shall not commence descend before 100 NM from ‘DPN VOR’. Aircraft shall continue on assigned STAR following all level and speed restrictions applicable to STAR, as far as practicable. This allows ATC to resolve any possible traffic conflict.
4.1.2 At the end of the STAR, descend to 2600 ft and take a convenient turn to intercept localizer or final approach track of the published procedure for the assigned runway.
4.2. ARRIVING AIRCRAFT - STAR NOT ASSIGNED
Aircraft to which a STAR has not been assigned by ATC, on experiencing radio communication failure, shall
4.2.1. Continue on ATS route, (Re-join ATS route if given heading or flying offset), maintaining/descending to cleared flight level or FL 70 whichever is higher. At 40 miles to ‘DPN VOR’, take a turn (avoiding VIP 89) to proceed direct to ‘SKA’ VOR. If higher, descend to FL 70 in ‘SKA’ hold.
4.2.2. If RCF takes place within 40 NM of ‘DPN VOR’, continue to ‘DPN VOR’ and at 10 miles to ‘DPN VOR’ take a turn (avoiding VIP 89) to proceed direct to ‘SKA’ VOR maintaining last assigned level or FL 70 whichever is higher. If below FL 70, climb and reach FL 70 before crossing 25 NM outbound from ‘DPN VOR’. If higher, descend to FL 70 in ‘SKA’ hold.
4.2.3. Leave ‘SKA VOR’ at FL 70 to carry out published ILS/VOR DME ARC approach procedure for assigned runway.
4.3. ARRIVING AIRCRAFT BEING RADAR VECTORED
Aircraft being radar vectored for approach, on experiencing RCF, shall maintain last assigned level and heading for 3 minutes after detecting RCF or selecting MODE A/C 7600, whichever is later, and then take a convenient turn (Avoiding VIP 89) to proceed direct to ‘SKA’ climbing/maintaining last assigned level, or FL 70 whichever is higher.
|
|
If below FL 70, climb and reach FL 70 before crossing 25 NM outbound from ‘DPN VOR’. If higher, descend to FL 70 in ‘SKA’ hold
4.3.1. Leave ‘SKA’ VOR at FL70 to carry out published ILS/VOR DME ARC approach procedure for assigned runway.
5. PROCEDURE FOR DEPARTURES:
5.1. DEPARTURE INTENDING TO CONTINUE TO DESTINATION
Any departing aircraft experiencing RCF and intending to continue to its filed plan destination shall:
5.1.1. Continue on assigned SID or heading climbing to or maintaining cleared level or FL70, whichever is higher.
5.1.2. Three minutes after setting Mode A/C code 7600 or reaching FL 70 or cleared Flight level (if higher than FL70) whichever is later:
i. If following ‘SID’, continue on SID to join ATS route and climb to filed Flight level and continue as per the filed flight plan.
ii. If following Radar heading, turn (avoiding VIP 89) to join ATS route by shortest route maintaining cleared flight level/FL 70 as per para 5.1.1. After joining ATS route, climb to filed Flight level and Continue as per the filed flight plan
5.2 DEPARTURE INTENDING TO LAND BACK AT DELHI:
Any departing aircraft experiencing RCF after departure and intending to land back at IGI Airport shall
5.2.1 Continue on assigned SID or heading climbing to or maintaining cleared level or FL70, whichever is higher.
5.2.2 Three minutes after setting Mode A/C code 7600 or reaching FL70 or cleared Flight level (if higher than FL70) whichever is later, take a turn (avoiding VIP 89) to proceed direct to ‘SKA’ VOR.
5.2.3 If higher, descend to FL70 in ‘SKA’ hold.
5.2.4 If required, Jettison fuel while in ‘SKA’ hold, taking all necessary precautions.
5.2.5 Leave ‘SKA’ VOR at FL70 to carry out published ILS/VOR DME ARC approach procedure for assigned runway.
NOTE :-
1.In Case Of Non-availability Of SKA VOR aircraft required to hold at SKA VOR may hold at following FIX/WAY POINT:
A. R186/43 D (116.1 DPN)
B. 275054N 0770030E
|
|
III. ARRIVAL, DEPARTURE PROCEDURE AND RUNWAY CAPACITY ENHANCEMENT MEASURES
The traffic has been growing at Delhi Airport at a faster rate which necessitates the optimum use of resources to meet our requirement of safe, efficient and expeditious handling of air traffic. Runway Occupancy Time has been one of the important factors affecting such requirement. The following procedures and important Aerodrome data are published (TORA/LDA from different entry/exit TWYs) which will facilitate the Airlines/Pilots in achieving minimum Runway Occupancy Time for common goal of enhancing runway capacity utilizing the existing available resources.
1. DEPARTURE PROCEDURE
1.1. The aircraft should be in a position to commence its taxi not more than five minutes after the issue of start-up clearance failing which the start-up clearance will be cancelled and the aircraft will lose its priority and be considered for start-up depending upon the traffic situation and subject to delay.
1.2. Taxiing aircraft should maintain a minimum taxiing speed of not less than 15 Knots on the straight portion of taxiways and between 8-12Kts during turning manoeuvres
1.3. Any aircraft if observed, by the Controller, to be too slow taxiing and thereby adversely affecting the efficient aircraft movement shall be taken out of the sequence and will be considered for departure as a last priority depending upon the traffic situation subject to delay.
1.4. Based on the aircraft type and its performance characteristics, ATC will issue taxiing instructions so as to depart from the nearest runway intersection from where adequate take off run is available for departure. Pilots unable to accept departure from intersection may request ATC for alternate take off position. Pilots requiring departure from the beginning of runway should make such request at the time of Push back/Start-up. However, such requests will be considered by ATC subject to delay.
1.5. Pilot shall complete all mandatory pre-departure checks before entering the active runway for departure so that the aircraft is in a position to take off immediately upon receipt of take-off clearance.
|
|
1.6. When the aircraft is issued with a line-up and take-off clearance at the taxi holding position it shall be in a position to line up and affect an immediate take- off in one continuous movement.
1.7. When the aircraft is issued with a take- off clearance after lining up on the runway it shall commence take-off roll immediately upon receipt of take- off clearance.
1.8. If the Controller observes a delay in respect of the departing aircraft commencing its take off run after issuance of take- off clearance, the take- off clearance will be cancelled and the aircraft be advised to vacate the runway immediately at the nearest taxiway to make way for the subsequent arrival or departure. Necessary entries in this regard shall be recorded in the Log Book.
1.9. Refer AD 2.24 for charts related to Take-off Run Available from different intersections.
NOTE: With the objective of expediting the flow of traffic, ATC may authorize Departure from intersections also.
2. ARRIVALS
2.1 Pilots are reminded that rapid exit from the runway enables ATC to apply minimum spacing on final approach that will achieve maximum runway utilisation and will minimise the occurrences of 'go around’.
2.2 Pilots of small and medium aircraft are requested to consider which Rapid Exit Taxiway offers the best opportunity for a safe and expeditious exit from the runway in order to reduce delays and maximise utilisation.
2.3 Aircraft are expected to vacate the runway via first available RET depending on aircraft performance.
2.4 Refer AD 2.24 for charts related to the locations of exit taxiways with respect to threshold for all the runways.
IV. DELHI AIRPORT COLLABORATIVE DECISION MAKING (DA-CDM)
1 BACKGROUND
1.1 The Delhi Airport - Collaborative Decision Making (DA-CDM) undertaken at IGI Airport is a joint programme among all airport partners -
• Air Navigation Service Provider (ATC)
• Airline Operators (AO)
|
|
• Air Traffic Flow Management Unit (ATFMU)*
• Delhi International Airport Pvt. Limited (DIAL)
• Ground Handlers (GH)
• Support services (Police, Customs and Immigration, Air Force Movement Liaison Unit, etc.)
All the partners are required to work in close collaboration to ensure the successful operation of DA-CDM.
1.2 The efficiency of the Air Transport System is highly dependent on traffic predictability. DA-CDM effectively enhances predictability (this reduces buffer times for resource planning and flight times), overall efficiency and punctuality by linking and sharing of accurate and timely information amongst Airlines, Airport Operator, ATC, etc.
1.3 The primary objective of DA-CDM is to facilitate the sharing of operational data for a better informed, well planned and transparent decision making to ensure more precise overall operational processes. It leads to an optimized utilization of resources, an efficient turn round process and everyone has a common awareness of the situation.
1.4 Through implementation of DA-CDM, long-lasting benefits can be reaped.
Benefits of DA-CDM are:
• Improved overall efficiency of the operation
• Reduced delays and increased punctuality
• Reduced ATFM slot wastage*
• Optimized en-route capacity
• Optimized use of the airport infrastructure
• Reduced apron and taxiway congestion
• Cost savings
• Reduction of carbon emission and noise pollution
• Enhanced predictability
• Optimized use of ground handling resources
• Optimized use of stands, gates and terminals
• Enables flexible pre-departure planning
2 TERMS AND ABBREVIATIONS
All Acronyms are time parameters which have a standard length of four characters and have been arranged as per aircraft movement sequence.
[While developing the DA-CDM procedures, the guidance material published by Euro control, ICAO and other Organizations has been used].
|
|
|
|
S. NO.
|
ACRONYMS
|
DEFINITION
|
EXPLANATION
|
|
2.1
|
ELDT
|
Estimated Landing Time
|
The estimated time that an aircraft will touchdown on the runway.
(Equivalent to ATC ETA = Estimated Time of Arrival = landing).
|
|
2.2
|
TLDT
|
Target Landing Time
|
Targeted Time from the Arrival management process at the threshold, taking runway sequence and constraints into account. It is not a constraint but a progressively refined planning time used to coordinate between arrival and departure management processes.
Each TLDT on one runway is separated from other TLDT or TTOT to represent vortex and/or SID separation between aircraft.
|
|
2.3
|
ALDT
|
Actual Landing Time
|
The time that an aircraft lands on a runway.
(Equivalent to ATC ATA = Actual Time of Arrival = landing, ACARS = ON).
|
|
2.4
|
EXIT
|
Estimated Taxi-In Time
|
The estimated taxi time between landing and in-block.
|
|
2.5
|
AXIT
|
Actual Taxi-In Time
|
AXIT = AIBT - ALDT
|
|
2.6
|
SIBT
|
Scheduled In-Block Time
|
The time that an aircraft is scheduled to arrive at its first parking position.
|
|
2.7
|
EIBT
|
Estimated In-Block Time
|
The estimated time that an aircraft will arrive in-blocks.
(Equivalent to Airline/Handler ETA = Estimated Time of Arrival).
|
|
2.8
|
AIBT
|
Actual In-Block Time
|
The time that an aircraft arrives in-blocks.
(Equivalent to Airline/Handler ATA = Actual Time of Arrival, ACARS = IN).
|
|
2.9
|
ACGT
|
Actual Commence of Ground Handling Time
|
The time when ground handling on an aircraft starts, can be equal to AIBT (to be determined locally)
|
|
2.10
|
ASBT
|
Actual Start Boarding Time
|
Time passengers are entering the bridge or bus to the aircraft.
|
|
2.11
|
AEGT
|
Actual End of Ground handling Time
|
The time when ground handling on an aircraft ends, can be equal to ARDT (to be determined locally)
|
|
2.12
|
AGHT
|
Actual Ground Handling Time
|
The total duration of the ground handling of the aircraft.
AGHT = ACGT - AEGT
|
|
2.13
|
STTT
|
Scheduled Turn-round Time
|
STTT = SOBT - SIBT
|
|
2.14
|
ETTT
|
Estimated Turn-round Time
|
The time estimated by the AO/GH on the day of operation to turn-round a flight taking into account the operational constraints.
|
|
2.15
|
MTTT
|
Minimum Turn-round Time
|
The minimum turn-round time agreed with an AO/GH for a specified flight or aircraft type.
|
|
2.16
|
ATTT
|
Actual Turn-round Time
|
ATTT = AOBT - AIBT
|
|
2.17
|
ASRT
|
Actual Start Up Request Time
|
Time the pilot requests start up clearance.
|
|
2.18
|
TSAT
|
Target Start Up Approval Time
|
The time provided by ATC taking into account TOBT, CTOT* and/or the traffic situation that an aircraft can expect start-up / push back approval.
Note: The actual start up approval (ASAT) can be given in advance of TSAT.
|
|
2.19
|
ASAT
|
Actual Start Up Approval Time
|
Time that an aircraft receives its start-up approval.
|
|
2.20
|
SOBT
|
Scheduled Off-Block Time
|
The time that an aircraft is scheduled to depart from its parking position.
|
|
2.21
|
EOBT
|
Estimated Off-Block Time
|
The estimated time at which the aircraft will start movement associated with departure (ICAO).
|
|
2.22
|
TOBT
|
Target Off-Block Time
|
The time that an Aircraft Operator or Ground Handler estimates that an aircraft will be ready, all doors closed, boarding bridge removed, push back vehicle available and ready to start up / push back immediately upon reception of clearance from the SMC (GROUND).
|
|
2.23
|
AOBT
|
Actual Off-Block Time
|
Time the aircraft pushes back / vacates the parking position.
(Equivalent to Airline / Handlers ATD = Actual Time of Departure & ACARS = OUT)
|
|
2.24
|
ARDT
|
Actual Ready Time
(for Movement)
|
When the aircraft is ready for start-up/push back or taxi immediately after clearance delivery, meeting the requirements set by the TOBT definition.
|
|
2.25
|
EXOT
|
Estimated Taxi-Out Time
|
The estimated taxi time between off-block and take off. This estimate includes any delay buffer time at the holding point prior to take off.
|
|
2.26
|
AXOT
|
Actual Taxi-Out Time
|
AXOT = ATOT - AOBT
|
|
2.27
|
ETOT
|
Estimated Take Off Time
|
The estimated take off time taking into account the EOBT plus EXOT.
|
|
2.28
|
CTOT*
|
Calculated Take Off Time*
|
A time calculated and issued by the appropriate Central Management unit, as a result of tactical slot allocation, at which a flight is expected to become airborne. (ICAO Doc 7030/4 - EUR, Table 7)*
|
|
2.29
|
TTOT
|
Target Take Off Time
|
The Target Take Off Time taking into account the TOBT/TSAT plus the EXOT. Each TTOT on one runway is separated from other TTOT or TLDT to represent vortex and/or SID separation between aircraft.
|
|
2.30
|
ATOT
|
Actual Take Off Time
|
The time that an aircraft takes off from the runway.
(Equivalent to ATC ATD = Actual Time of Departure, ACARS = OFF).
|
|
3 TWO KEY PARAMETERS OF DA-CDM: TOBT and TSAT.
3.1 TARGET OFF-BLOCK TIME (TOBT)
3.1.1 Definition: The time that an Aircraft Operator or Ground Handler estimates that an aircraft will be ready, all doors closed, boarding bridge removed, push back vehicle available and ready to start up/push back immediately upon reception of clearance from the SMC (GROUND).
3.1.2 Purpose: It is a fact that Air Traffic Management (ATM), based on FPL-data only, is insufficient to guarantee smooth and efficient operations on the ground and in the air. The main reason for this is the incorrect updating/no updating at all, of the Estimated Off-Block Time (EOBT) of the flight plan. The result is that airport partners have an incorrect idea about the actual status of that specific flight.
Target Off-Block Time (TOBT) is the dynamic target on the operational readiness of a flight thus, more accurate than the static departure time of a flight plan and is therefore, an ideal milestone to be used by all airport partners.
3.1.3 When/How to calculate TOBT: In order to create an initial time reference, at EOBT - 45 minutes, TOBT will be calculated by adding Estimated In-block Time (EIBT) + Minimum Turn-round Time (MTTT) for distribution and to derive further updates.
When the aircraft arrives on stand at Actual In-Block Time (AIBT), TOBT is updated by AO/GH based on MTTT or the Scheduled Off-Block Time (SOBT). These MTTT’s are regularly updated and Aircraft Operators are consulted for the most accurate times.
Refining of TOBT (Example)
TOBT based on EOBT [At EOBT - 45 minutes]
TOBT = EIBT (ELDT issued at ELDT-20 minutes + EXIT) + MTTT
TOBT = EIBT (ELDT at 10NM from touchdown + EXIT) + MTTT
TOBT = EIBT (ALDT + EXIT) + MTTT
TOBT = AIBT + MTTT
3.1.4 Originator(s): Airlines Operator/Ground Handler.
3.1.5 Communication of Target Off Block Time (TOBT):
(i) AO/GH shall update their TOBTs via DA-CDM portal.
|
|
(ii) If there is no input in DA-CDM portal, EOBT itself will be treated as TOBT.
3.1.6 When to update: The aim of the Target Off-Block Time (TOBT) is to provide a timely, accurate and reliable estimate to the DA-CDM partners, of an aircraft's off block time. Accurate TOBTs enhance operations on the ground as they provide all airport partners with a clear picture of the intentions of aircraft on the ground.
TOBTs only need to be updated if the time that the aircraft will be ready to leave stand changes.
Once Target Start-up Approval Time (TSAT) is allocated by ATC at TOBT- 20 minutes, the TOBT may be updated thrice (equal to or less than TSAT).
3.1.7 Accuracy: TOBTs must be updated to an accuracy of +/- 5 minutes.
3.2 TARGET START UP APPROVAL TIME (TSAT)
3.2.1 Definition: The time provided by ATC taking into account TOBT, CTOT* and/or the traffic situation that an aircraft can expect start-up/push back approval.
Note: The actual start up approval (ASAT) can be given in advance of TSAT.
3.2.2 Purpose: TSATs provide an optimized start-up sequence, leading to Pre-Departure sequence. TSATs reduce queuing times at the runway holding points, while maintaining a high degree of runway utilization. ATC will continue to maximize departure rates and optimize the departure order for creating the right mix of traffic.
3.2.3 How to calculate/generate TSAT: The TSAT is calculated by taking into account TOBT, Calculated Take-Off Time (CTOT)*, wake vortex, Standard Instrument Departure (SID) routing, variable taxi times, and any capacity constraints such as Low Visibility Procedures.
ELDT + EXIT = EIBT
EIBT + MTTT = TOBT
TOBT + EXOT + Constraints = TTOT
TTOT - EXOT = TSAT
ELDT : Estimated Landing Time
EXIT : Estimated Taxi-In Time
EIBT : Estimated In-Block Time
MTTT : Minimum Turn-round Time
TOBT : Target Off-Block Time
EXOT : Estimated Taxi-Out Time
TTOT : Target Take Off Time
TSAT : Target Start Up Approval Time
|
|
Note: A re-assessment of a flight on the network (re-calculation of CTOT) will be done if the TTOT is outside the Slot Tolerance Window (STW = CTOT-5 till CTOT+10 minutes). The Calculated Take-Off Time becomes tailor-made where possible.*
3.2.4 Originator(s): ATC.
3.2.5 When to issue TSAT: At TOBT - 20 minutes by ATC in DA-CDM portal.
3.2.6 Communication of Target Start-up Approval Time (TSAT): The Target Start-up Approval Time (TSAT) will be displayed in the DA-CDM portal. Pilots will be informed of their Target Start-up Approval Time (TSAT) through DA-CDM portal and any changes to it by ATC. The AO/GH shall advise flight crew of TSAT, displayed in the DA-CDM portal.
3.2.7 When to update: The factors that may cause a revision of TSAT include but not limited to:
(i) Change of runway
(ii) Change in taxi time
(iii) Revised TOBT
(iv) Change of route (SID)
(v) Change of aircraft type
(vi) Application of ATFM regulation or ATC restriction resulting in new CTOT or start up delay*
(vii) Inclement Weather
(viii) Priority handling
(ix) Bird activity
(x) Unusual Occurrences, etc.
In case of TSAT revision, ATC will re-calculate a new TSAT and an alert in the DA-CDM portal will notify the AO/GH. The pilot will be informed by ATC of any revised TSAT if there is a delay to TSAT in excess of 5 minutes.
3.2.8 Accuracy: TSAT +/- 5 minutes.
3.3 Co-ordination with the Air Traffic Flow Management Unit (ATFMU)*
3.3.1 A permanent and fully automatic data exchange with the ATFMU will be established. The data transfer will enable highly accurate early predictions of landing and departure times.*
|
|
3.3.2 Furthermore, it allows for more accurate and efficient CTOT calculations due to the use of more accurate local target take-off times.*
4 TOBT and TSAT based DA-CDM Start-up/Push-back procedures
4.1 A Flight Plan Check shall be performed by DA-CDM Cell, to the extent possible, two hours prior to SOBT/EOBT to verify the consistency between SOBT and EOBT. The EOBT must correspond to the SOBT. If the EOBT deviates from the SOBT, the relevant contact person will be informed by DA-CDM Cell and advised to adjust the times accordingly. AO/GH shall be responsible to obtain ADC number from IAF-MLU.
4.2 Estimated Landing Time (ELDT): ATC will input Estimated Landing Time (ELDT) at ELDT - 20 minutes on DA-CDM portal. At 10 NM to touchdown, report is generated automatically by ATC automation system [AutoTrac III (AT3)] and sent to DIAL through AODB link.
4.3 Estimated In-block Time (EIBT): This estimate will be calculated by adding Variable Taxi Time (VTT) [Estimated Taxi-In Time (EXIT)] from the RWY to the Stand/Gate automatically by DA-CDM portal using VTT matrix.
4.4 Pre-Departure Sequence: Pre-Departure sequence is the order, in which the ATC plans the aircraft to depart from their Gate/Stands (Push-off blocks). It should not be confused with the Pre-Take-off sequence where ATC decides on the order in which the aircraft at holding points of the runway will depart.
4.5. Data link clearance facility is operational at IGI airport,DELHI. In accordance with best equipped best served policy the flights receiving clearance through data link may contact relevant SMC/GROUND frequency directly as per the TSAT(TArget Start-up Approval Time) issued.
4.5 Start-Up and Push-Back Procedure
i. The pilot should contact Clearance Delivery (CLD) to request en-route clearance and SID between TOBT - 15 minutes to TOBT - 5 minutes.
ii. The aircraft must be ready to Start-up/Push-back at TOBT and request SMC (GROUND) for Start-up/Push-back at TOBT.
(Note: TSAT can be preponed up to TOBT)
iii. If at TOBT +5 minutes, ATC has not received Start-up/Push-back request, the aircraft may lose its position in sequence.
a. ATC will advise the pilot that a new TOBT is required.
b. On receipt of new TOBT, the flight will be re-sequenced according to new TOBT and a new TSAT with a subsequent delay will be issued.
|
|
iv. ATC should normally be able to issue start-up/push-back at TSAT. Pilots will be informed by ATC of any revised TSAT if there is a delay to TSAT in excess of 5 minutes.
v. Taxi clearance must be requested within 5 minutes of Start-up/Push-back approval time.
(Note: If this has not occurred, SMC (GROUND) must be notified of the extent of delay. In such cases, aircraft may lose its departure slot and a new TOBT may be required in DA-CDM portal. AO/GH shall be responsible to obtain new ADC number from IAF-MLU).
vi. The Pre-Departure (Off- block) Sequence will be determined in accordance with Target Start up Approval Time (TSAT) and NOT in accordance with the Start-up Request. Pre-Departure Sequence will not have any bearing on Actual Departure sequence.
(Note: Actual Departure sequence may differ from pre-departure sequence in order to optimize the Runway and Airspace utilization.)
* [Future provision kept for incorporating with India - Central Air Traffic Flow Management]
|
|
V. INORMATION REGARDING INTERSECTION DEPARTURES
A During non-availability period of all the entry TWY Z1, CE1, CE2 and Z2 to RWY29, Rapid Exit TWY of RWY 11 Z3 and
Z4 can be used as entry TWY for Aircraft intending to depart from RWY 29 under the following conditions.
i. In day time only when visibility is above 2000m
ii. up to CODE C Aircraft only.
iii. Simultaneous use of RET Z3 and Z4 not permitted.
1. New entry taxi routes via Z3 and Z4 for Runway 29 are:
i. TWYS2- TWY Z- TWY Z3- RWY 29.
ii. TWY S2- TWY Z- TWY Z4- RWY 29.
iii. TWY Z- TWY Z4- RWY29.
2. Holding point markings and stop bars provided on TWY S2 short of TWY Z
and on Z short of TWY Z4 (west side) but during operation the stop bars on
these TWYs may be kept in off mode
3. Necessary signage boards have been placed.
|
|
VI. Speed control Procedure
a) Speed control Procedure under non Radar environment shall be as specified in ENR1.1 para 2.5 of eAIP India.
b) Speed control procedure under Radar environment refer ENR 1.6 para 8 of eAIP India.
b) Arriving ACFT passing F290, to maintain speed 270KTS and thereafter follow the speed restrictions as published in
STAR,unless otherwise superceded by ATC instructions.
VII. IMPLEMENTATION OF TACTICAL AIR TRAFFIC FLOW PROCEDURES (T-ATFP)
1 Introduction
1.1 In order to reduce airspace congestion, arrival delays and holding in Delhi TMA, Tactical Air Traffic Flow Control Procedure (T-ATFP) is introduced. For this purpose, sequenced entry into airspaces is established and maintained.
1.2 T-ATFP is applied to aircraft landing at Delhi airport, classified as follows:
1.2.1 Arrivals from airports within Delhi FIR;
1.2.2 Arrivals from airports outside Delhi FIR but within 10 min flying time from Delhi FIR boundary;
1.2.3 Arrivals from airports other than those in 1.2.1 & 1.2.2
2 Acronyms used in the document and associated expansion
AAO Airline and aircraft operators
CTO Calculated Time Over
ETO Estimated Time Over
RTO Required Time Over
T-ATFP Tactical Air Traffic Flow Procedures
TM Traffic Manager (for the purpose of T-ATFP)
3 Terminology and their meaning
3.1 AAO (Airline and aircraft operators) - includes all aircraft operators including defence, State Govt., paramilitary etc.
|
|
3.2 Block Time - Time required for arriving over runway THR following a STAR flight path and adhering to STAR speed restrictions.
3.3 Calculated Time Over (CTO) - Time at which departure from airports at 1.2.1 & 1.2.2 should arrive over the arrival holding fix to fit into established arrival sequence. By back calculation, the time of takeoff can be computed.
3.4 Required Time Over (RTO) - Time at which arrivals in 1.2.3 should arrive over the arrival holding fix to avoid joining the holding.
4 Traffic Manager (TM)
4.1 The Traffic Manager (TM) position is established within Delhi ATC for the implementation of T-ATFP. TM will have access to flight plans and estimates and revisions to estimates of all arrivals landing at Delhi airport.
4.2 Functions of TM
4.2.1 Establishing a sequence of arrivals landing at Delhi airport based on touchdown time.
4.2.2 Assign landing runways to arrivals; whenever more than one runway is available for landing.
4.2.3 Advise CTO/RTO to ACC Sector controller.
4.2.4 Advise CTO/RTO, arrival sequence and assigned landing runway to Approach (Arrival) Controller.
4.3 For effective and efficient management of arrival sequence, TM shall:
4.3.1 Make available a CTO arrival holding fix for the departures from airports as in 1.2.1 & 1.2.2.
4.3.2 Provide information to arrivals as in 1.2.3, regarding RTO arrival holding fix.
4.4 Based on the ETO at arrival holding fix, sequence of arrivals will be determined by TM.
5 Essential requirements
5.1 Arrivals landing at Delhi airport shall flight plan via arrival route (STAR) appropriate to the ATS route. To maintain arrival sequence, non-RNAV arrivals to expect routing/vectors along RNAV STAR.
|
|
5.2 All flight-plans for landing at Delhi airport shall provide ETO arrival holding fix - AKBAN, SAM, SSB & SAPLO as appropriate, for determination of arrival sequence based on time required to reach runway touchdown point from the arrival holding fix.
5.3 Departures from airports within Delhi FIR and within 10 min flying time from Delhi FIR shall coordinate with TM for CTO. Uncoordinated departure from such airports shall be refused entry into Delhi TMA or will be subject to extended delays.
6 Tactical Flow Management Process
6.1 For ensuring efficient flow during T-ATFP, speed management of sequenced aircraft is a critical factor. Approach (Arrival) Controller shall enforce adherence to speed restrictions.
6.2 Delhi ACC Sector controllers will clear all arrivals via STAR. Delhi Radar shall vector Non-RNAV arrivals along appropriate STAR route segment with speed control instructions consistent with STAR segment, so as to ensure that the arrival sequence computed by TM is maintained.
6.3 The arrival sequence is calculated based on the Block Time plus separation at touchdown point between successive arrivals. During the initial phases of T-ATFP implementation; the separation over touchdown point will be 2 min.
6.3.1 The separation over touchdown point is dependent on dynamic factors such as:
• Weather
• Equipment outage
• Runway closure
• Airspace closure
• Contingency such as RCF, Unlawful interference etc
6.4 TM shall advise Delhi ACC sector controller and Approach (Arrival) controller information on RTO. Accordingly, arrivals will be advised of RTO thereby facilitating in gaining/losing time so as to arrive over arrival holding fix at RTO.
6.5 For ensuring efficient flow based on the arrival sequence, speed management is critical. Approach (Arrival) controller may enforce speed control based on the STAR restrictions and on final approach.
|
|
6.6 Safety being primary, minimal radar vectoring may be resorted thereby permitting aircraft to adhere to FMS managed flight profile/path of RNAV STAR.
6.7 The arrival runway allocation and sequence established by TM, may not be altered by Delhi Approach; as far as practicable, except during emergency, RCF, unlawful interference or during events requiring priority handling.
6.8 When adverse conditions such as weather, equipment outage, runway closure and/or airspace closure etc affect Delhi airport/Delhi TMA, the capacity of the airport and TMA could be severely degraded, resulting in unoptimised traffic flows. Therefore, in order to avoid excessive holding, airborne delay and congestion during such events; following T-ATFP measures will be implemented:
6.8.1 Departure airport ATS units shall be advised of the restricted arrival capacity at Delhi and CTO to be provided for all departures before start-up based on flight-plan ETD. Any delay beyond flight-plan ETD will require revised CTO arrival holding fix to be obtained.
6.8.2 During events enumerated in Para 6.8, departures from airports within Delhi FIR and within 10 min flying time from Delhi FIR do not have the option to take-off and absorb delay enroute or by holding within Delhi TMA.
7 AAO responsibility
7.1 AAOs are to ensure they are fully informed on the following procedures:
7.1.1 AAOs shall adhere to the speed control restrictions of the STAR or speed control instructions issued by Delhi ATC.
7.1.2 AAOs shall arrange the departure of their flights to comply with the CTO issued.
7.1.3 Non-adherence to CTO may result re-sequencing. TM will issue RTO which may result in disproportionate arrival delay.
8 ATS Unit responsibility
8.1 ATS Units shall make every effort to enable departing flights to comply with CTO.
8.2 ATC shall provide all possible assistance to AAOs to meet CTO/RTO.
9 Arrivals exempted from T-ATFP
9.1 The following flights are exempted from T-ATFP:
|
|
9.1.1 Arrival in a state of emergency, including flights subject to unlawful interference
9.1.2 Arrival conducting search and rescue operations
9.1.3 Arrival carrying notified VIP
9.1.4 Arrival with medical emergencies
VIII. FOR TRANSPONDER OPERATING PROCEDURES ON GROUND
1. Introduction:
Advanced Surface Movement Guidance and Control System (A-SMGCS) using Mode-S Multi-lateration has been commissioned at Bangalore, Chennai, Delhi, Hyderabad, Kolkata & Mumbai International Airports.
The Aircraft Transponder Operating Procedures, particularly in the movement area of the airport(s), where A-SMGCS has been commissioned, is as given below:
2. DEPARTURE
i. At the Gate/Stand:
Select STBY
Enter the discrete SSR code received from Clearance Delivery/Surface Movement Control. Enter the three letter ICAO designator followed by the flight identification number (e.g. AIC748) through the FMS or the Transponder control panel, depending on the avionics.
ii. On requesting Pushback/Taxi (whichever is earlier):
Select Transponder or equivalent and AUTO if available
This action will enable the aircraft ID, used as the Call sign by ATC, to be displayed on the surveillance display of ATC. ATC can verify the data and use it for necessary identification.
iii. When Lining up:
Select TCAS
Select TCAS only after receiving the clearance to line up, to ensure that the performance of systems based on SSR frequencies (including airborne TCAS units, SSR and A-SMGCS) is not compromised.
|
|
3. ARRIVAL
1. When on the Runway:
Keep TCAS selected
2. After vacating the Runway:
Select Transponder or equivalent and AUTO if available
There is a need that the Transponder remains able to exchange data with the A-SMGCS system. However, to ensure that the performance of systems based on SSR frequencies (including airborne TCAS Unit, SSR & A-SMGCS) is not compromised, TCAS shall be deselected when vacating the Runway.
3. Parked on Stand:
Select STBY
The Transponder will not reply to interrogation. The discrete SSR Code given to that particular flight can now be recycled for other flights.
Note: When on ground the aircraft must squawk Mode C, in order to provide the altitude information to the surveillance system, and thereby prevent
i) clutter on Terminal Approach Radar Display (and)
ii) false automatic detection of departure for aircraft still on ground.
|
WESTERLY FLOW
|
RWY 29
|
To Terminal 1
|
Vacate via TWY S5, taxi via T, CW2, S,
R3,
R, M1, M2, Cross RWY 28, E4, E2 and via
i. A for stands 1-12
ii. C1 for stands 15-17
iii. E, B3 for stands 20-22
iv. B2 for stands 23-30
v. F2 for stands 135-142
|
RWY 29
|
To Terminal 2 and
Terminal 3
|
Vacate via TWY S5 taxi via TWY T and via
i. T1/T1A for Apron 35
ii. T2 for Apron 34
iii. CW2, W1 for Apron 33A
iv. T3 for Apron 33B
v. CW2, W2 for Apron 32
vi. CW2, S, R5 for Apron 31
vii. CW2, S, R4/R3/R1/R2 for stands 41-49
viii. CW2, S, R3 for stands 81L to 83R, 88 & 89
ix. CW2, S, R3, R for cargo 98-106
|
RWY 28
|
To Terminal 1
|
Vacate via TWY D1 taxi via D, E2 and via
i. A for stands 1-12
ii. C1 for stands 15-17
iii. E, B3 for stands 20-22
iv. B2 for stands 23-30
v. F2 for stands 135-142
Note:
1. If RWY 28 is vacated via E4, then taxi via E2 and taxi further as above.
2. In case the aircraft is not able to vacate on D1/D/E4, then vacate via TWY N and then taxi via S, R3, R, M1, M2, Cross RWY 28, E4, E2 and taxi further as above.
|
RWY 28
|
To Terminal 2 and
Terminal 3
|
Vacate via TWY N taxi via S, OR Vacate via M taxi via P, N, S
i. CW1, T, T1/T1A for Apron 35
ii. CW1, T, T2 for Apron 34
iii. CW1, W1 for Apron 33A
iv. CW1, T, T3 for Apron 33B
v. CW1, W2 for Apron 32
vi. R5 for Apron 31
vii. R4/R3/R1/R2 for stands 41-49
viii. R3 for stands 81L to 83R, 88 & 89
ix. R3, R for Cargo 98-106
|
RWY 29
|
From Terminal 1
|
i. Stands 1-12: A, RWY 27, K, cross RWY 28, N, S, CW1, T, Z2/(Z, CE1)
NOTE: In case of RWY 28 departure, push back facing south, and in case of RWY 29 departure push back facing north. Controller to exercise caution while giving push back for departures.
ii. Stands 15-17: A, RWY 27, K, cross RWY28, N, S, CW1, T, Z2/ (Z, CE1)
iii. Stands 20-30: C1, RWY 27, K, cross RWY 28, N, S, CW1, T, Z2/ (Z, CE1)
iv. Stands 135-142: F3, F, E, RWY 27, K, cross RWY 28, N, S, CW1, T, Z2/ (Z, CE1)
|
RWY 29
|
From Terminal 2 and
Terminal 3
|
i.Apron 35: T1/T1A, T, Z2/ (Z, CE1)
ii. Apron 34: S3, T, Z2/ (Z, CE1)
iii. Apron 33A: W1, CW1, T, Z2/ (Z, CE1)
iv. Apron 33B: T3, T, Z2/ (Z, CE1)
v. Apron 32: W3, CW1, T, Z2/ (Z, CE1)
vi. Apron 31: R5, S, CW1, T, Z2/ (Z, CE1)
vii. Stands 41-49: R1/R2, M1, P, N, S, CW1, T, Z2/ (Z, CE1)
viii. Stands 81L to 83R, 88 & 89: R3, M1, P, N, S, CW1, T,
Z2/(Z, CE1)
ix. Cargo 98-106: R, L1, P, N, S, CW1, T, Z2/ (Z, CE1)
|
RWY 28
|
From Terminal 1
|
i. Stands 1-12: A, C
ii. Stands 15-17: Push back and taxi via C1,C
iii. Stands 20-30: C1, C
iv. Stands 135-142: F3, F, B3, stand 19, C
|
RWY 28
|
From Terminal 2 and
Terminal 3
|
i. Apron 35: T1/T1A,Y,CW2,S, R3, R, L1, P, TWY P1
ii. Apron 34: S3, Y, CW2, S, R3, R, L1, P, TWY P1
iii. Apron 33A: W1, CW2, S, R3, R, L1, P, TWY P1
iv. Apron 33B: T3, Y, CW2, S, R3, R, L1, P, TWY P1
v. Apron 32: W3, CW2, S, R3, R, L1, P, TWY P1
vi. Apron 31: R5, R3, R, L1, P, TWY P1
vii. Stands 41-49: R3/R2/R1, R, L1, P, TWY P1
viii. Stands 81L to 83R, 88 & 89: R3, R, L1, P
ix. Cargo 98-106: R, L2, P, TWY P1
|
Table: 3
|
EASTRERLY FLOW
|
RWY 11
|
For Terminal 1
|
Vacate via TWY Z2, taxi via Y, CW2, N, P
i. Cross RWY 10 from W to C, taxi lane A
for stands 1-12
ii. Cross RWY 10 from W to C, C1 for
stands 15-17
iii. Cross RWY 10 from W TO C, E2, [F2,
F3, F, B3 for Stands 20-22]/[B2 for stands
23-30]
iv. Cross RWY 10 from W to C, E2, F2 for
stands 135-142
|
RWY 11
|
For Terminal 2 and
Terminal 3
|
Vacate via TWY Z2, taxi via Y
i. T1/T1A for Apron 35
ii. S3 for Apron 34
iii. CW2, W1 for Apron 33A
iv. T3 for Apron 33B
v. CW2, W2 for Apron 32
vi. CW2, S, R5 for Apron 31
vii. CW2, N, P, M1, R3/R2/R1 for Stands 41-
49
viii. CW2, N, P, M1, R3, for Stands 81L to
83R, 88 & 89
ix. CW2, N, P, L2, R for Cargo 98-106
|
DEPARTURE
|
RWY 11
|
From Terminal 1
|
i. Stands 1-12: A, RWY 27, D, cross RWY
10 from D to M,M1,R3, S, CW1, Y, S5
ii. Stands 15-17: A, RWY 27, D, cross RWY
10 from D to M,M1,R3, S, CW1, Y, S5
iii. Stands 20-30: C/C1, RWY 27, D, cross
RWY 10 from D to M, M1, R3, S, CW1,Y, S5
iv. Stands 135-142: F3, F, E, RWY 27, D,
cross RWY 10 from D to M, M1, R3, S,CW1, Y, S5
|
RWY 11
|
From Terminal 2 and
Terminal 3
|
i. Apron 35: T1/T1A, Y, S5
ii. Apron 34: T2, Y, S5
iii. Apron 33A: W1, CW1, Y, S5
iv. Apron 33B: T3, Y, S5
v. Apron 32: W3, CW1, Y, S5
vi. Apron 31: R5, S, CW1, Y, S5
vii. Stands 41-49: R1/R2/R3, S, CW1, Y, S5
viii.Stands 81L to 83R, 88 & 89: R3/S, CW1,
Y, S5
ix. Cargo 98-106: R, R3/S, CW1, Y, S5
|
RWY 10
|
From Terminal 1
|
i. Stands 1-12: A, RWY 27, K
ii. Stands 15-17: A, RWY 27, K
iii. Stands 20-30: C/C1, RWY 27, K
iv. Stands 135-142: F3, F, E RWY 27, K
|
RWY 10
|
From Terminal 2 and
Terminal 3
|
i. Apron 35: T1/T1A, Y, CW2, S, N
ii. Apron 34: T2, Y, CW2, S, N
iii. Apron 33A: W1, CW2, S, N
iv. Apron 33B: T3, Y, CW2, S, N
v. Apron 32: W3, CW2, S, N
vi. Apron 31: R5, S, N
vii. Stands 41-49: R1/R2/R3, S, N
viii.Stands 81L to 83R, 88 & 89: R3, S, N
ix. Cargo 98-106: R, R3, S, N
|
5.1.4 RVR is reported in the following scales:
a) From 2000m to 1200m, increments of 100m
b) From 1200m to 800m, increments of 50m
c) From 800m to 50m, increments of 25m
5.1.5 Equipment serviceability for CAT II/CAT IIIA/CAT IIIB operations:
a) For CAT II operations TDZ and MID RVR shall be available.
b) For CAT III A/ IIIB operations TDZ, MID and END RVR shall be available.
5.2 Aeronautical Ground Lighting (AGL) System
5.2.1 The Precision Approach lighting system for CAT II/CAT IIIA/CAT IIIB operations are installed on RWY 28, RWY 29, and RWY 11 at IGI Airport.
5.2.2 During LVP operation irrespective of the RVRs, the state electricity board (BSES) power supply will be the primary source through online UPS for the systems which require a maximum of one second switchover time and the DGs shall be in auto operation mode to meet the requirements in case of power failure. The power changeover for the other systems
which are not covered with UPS backup shall be getting the power supply through DGs within 15 seconds from the time of power failure. For the systems covered with UPS back up, the changeover will be zero seconds. There is no specific requirement for keeping the DG source as primary source when BSES power source is available during the LVP
operations.
|
5.2.3 The following taxiways have CAT III A/IIIB standard taxiway lighting:
Taxiway P,P1, L, L1, L2, M, M1, M2, N, S, R, R1, R2, R3, R5, W, CE1, CE2, CW1, CW2, W1, W2, W3, S3, S4, S5, T, T1, T1A, T2, T3, Y, Z, Z1, Z2, Z3, Z4, Z5, Z6, Z7, Z8, Z9 Taxiway A, B, B2, B3, C, C1, D, D1, E, E2, E3, E4, E5, F, F2, F3, K, RWY 09-27, Taxi-lane A and taxi-lane joining C1 and C.
5.2.4 The following parking stands have been provided with the Cat IIIA / IIIB Centerline lighting system:
a) Parking stand 1 to 12, 15 to 17, 20 to 30 and 135 to 142 in Apron-1
b) Parking stand 41 to 44, 45L/45R, 46L/46R, 47L/47R, 48, 49, 81L to 83R, 88, 89 and 98 to 106 in Apron-II
c) Parking stands in Apron 31-Apron 35
Table: 5
|
APRON
|
AIRCRAFT STAND
NUMBER
|
TOTAL AIRCRAFT
STANDS
|
APRON 31
|
A06, A08, A10
|
3
|
APRON 32
|
A01, A03, A07, A07L, A07R,
A09, A09L, A09R, B15,
B15L, B15R, B17, B17L,
B17R, R02, R03
|
12
|
APRON 33A
|
B18, B20, B20L, B20R, B22,
B22L,B22R, B24, B24L,
B24R, B26, B26L, B26R,
|
9
|
APRON 33B
|
C28L, C28R, C30L, C30R,
C32L, C32R, C34L, C34R,
C36
|
9
|
APRON 34
|
C27L, C27R, C29L, C29R,
D37, D37L, D37R, D39,
D39L, D39R , D41, D43,
D45, D47, D49, D51
|
14
|
APRON 35
|
D46, D48, D50, D52, D54,
D56, D58, D60, D62, E70,
E72, E74, E76, E78, E80,
E82, E84
|
17
|
|
Total including MARS stands
|
64
|
|
Total not including MARS stands
|
54
|
Note: Remote Stands in T3 apron (except R02, R03) do not have stand manoeuvring guidance lights.
|
5.2.5 Stop Bar: Stop bars have been provided on the following taxi tracks:
-- N, M, P1, W, CE1, CE2, CW1, CW2, S4, S5, T, Y (Short of CW2), Z, Z1, Z2, Z3,Z4, Z8, Z9
-- K, D, E4, C, E5.2.6 No clearance bar has been provided.
5.2.7 The alternate yellow and green lights have been provided on the undermentioned taxi tracks. When the aircraft has crossed these alternate yellow and green lights the aircraft is clear of ILS sensitive areas:
a) Rwy 28/10: D, D1, E4, K, N, M, L, U, V, F, E, C, B, W and P1
b) Rwy 29/11: Z3, Z4, Z5, Z6, Z7, Z8, S4 and S5
5.2.8 RWY 10-28 crossing light have been provided at the following points:
a) W-C
b) M-D
c) N-K
and vice versa
|
5.2.9 Intermediate Holding Position (IHP) lights have been provided on the following taxi track:
R1 (Short of intersection of R, M1 and R3)
M1 (Short of intersection of R, R1 and R3)
S (Short of R3/R4)
M1 (Short of P)
P (West Short of intersection of M and M1)
P (East Short of intersection of M and M1)
P (Short of L2 east side)
P (Short of L2 west side)
P Short of N
L1 (Short of intersection P and L)
L2 (Short of P)
R [Short of L1 (East of L1)]
ON TWY 'Z': East & West of Z3
East & West of Z4
East & West of Z5
East of Z6
East of Z7
Short of intersection S4 (Eastern side S4)
S4 North of S4 intersection Y
S5 North of S5 intersection Y&T
Y Short of intersection S4, short of Y5 both sides & Short of CW2
T Short of intersection S5, short of Y5 both sides, short of CW2 & short of CW1
CW1, CW2 Both sides short of W1, W2 & W3
CW1, CW2 At intersection TWY S
A (Short of RWY27)
B (Short of C)
E2 West of taxiway „D? (Short of intersection E2 and D)
E2 East of taxiway „D? (Short of intersection E2 and D)
E2 (West of intersection of E, E2)
E2 (Short of intersection of E4, E3)
E Short of RWY-27
F West of TWY E- intersection E& F
F Short of F3 (west side)
C1 South of E2 short of E2
E2 West of B2 short of intersection E2 & B2
E2 West of C1 short of intersection E2 & C1
E2 East of C1 short of intersection E2 & C1
E2 Short of F2 (west side)
N Short of P
T Short of CW2
T Short of Y5 (west)
N Short of P
S5 Short of Y
CW2 Short of Y
Y Short of T1
5.2.10 When LVP is in force the AGL must comply with the minimum serviceability
requirement: -
Table: 6
|
AGL Facility Unserviceability
|
CAT II/CATIIIA/CATIIIB
|
Restrictions
|
Approach Lights
|
The inner 450 meters- more than
5 % of all lights
|
Suspend CAT II / CAT IIIA
/ CAT IIIB operations
|
Beyond 450 meters more than
15% of all lights
|
Runway Edge lights
|
More than 5% of all Lights
|
Suspend CAT II / CATIIIA
/ CAT IIIB operations
|
Two adjacent lamps
|
Runway Center-line lights
|
More than 5% of all Lights
|
Suspend CAT II / CATIIIA
/ CAT IIIB operations
|
Two adjacent lamps
|
Touchdown Zone lights
|
More than 10% of all Lights
|
Suspend CAT II / CATIIIA
/ CAT IIIB operations
|
Two lamp in Barrette
|
Threshold lights
|
More than 5% of all Lights
|
Suspend CAT II / CATIIIA
/ CAT IIIB operations
|
Two adjacent lamps
|
Runway End lights
|
More than 25% of all Lights
|
Suspend CAT II / CATIIIA
/ CAT IIIB operations
|
Two adjacent lamps
|
Taxiway Centre-line lights
|
Not applicable to CAT II
operation
|
Close affected taxiways,
use alternate taxi route.
|
Two adjacent lamps
|
Standby Generators
|
Generators in any one
substation.
|
Suspend CAT II / CATIIIA
/ CAT IIIB operations in the
affected Runway.
|
8. ACTIONS TO BE TAKEN BY VARIOUS AGENCIES
8.1. Before commencement of winter season, a meeting will be held by Chief Operating Officer, Delhi International Airport Private Ltd. and Regional Executive Director (Northern Region)/ GM (ATM), IGI Airport, AAI in the month of November every year to inform all airlines and agencies operating at airport about their roles/ responsibilities and create awareness to ensure cooperation for safe airport operations during periods of low visibility.
8.2. All the agencies shall ensure that staff and drivers are suitably trained during CAT III operations.
8.3. Action by Watch Supervisory Officer (WSO), AAI
8.3.1 Implementing Safeguarding Procedures - When RVR is less than 1200m and visibility is forecast to deteriorate 800m or below and/or the cloud ceiling is 400ft and is forecast to fall to 200ft or less, WSO will inform -
a) AOCC,
b) Communication/ Technical supervisor (SSO), AAI
c) Tower Supervisor, AAI -for implementation of Safeguarding Procedures.
8.3.2 Implementing LVP
8.3.2.1 WSO shall implement Low Visibility Procedures when either
a) TDZ, MID or END RVR is less than 800m; and/or
Cloud ceiling is less than 200ft.
AND
c) Safeguarding Procedures (SP) have been completed and the airport is safeguarded.
8.3.2.2 WSO shall inform Aerodrome Tower Controller and Approach/Radar Controller,Duty Met. Officer and Communication/Technical Shift Supervisor Officer (SSO) and to ensure that “LOW VISIBILITY PROCEDURE IN FORCE” is included in ATIS broadcast.
8.3.3 WSO may terminate LVP when;
a) Meteorological conditions improve and TDZ, MID & END RVR are 800 m or more and the cloud ceiling is 200 ft or higher, and trend is for improvement for both runways.
b) Facilities, equipment and services necessary for CAT II/CAT III operations are degraded and/or the prevailing conditions are considered unsafe for such operations.
8.3.3.1 WSO will intimate Aerodrome Tower Controller, Approach/Radar Controller and Communication Technical Shift Supervisory Officer (SSO) regarding the Termination of LVP operation.
8.4. Action by Tower Supervisor:
8.4.1 On being notified by WSO that ILS CAT II/CAT III Low Visibility Procedures are to commence, the Aerodrome Tower Controller will:
a) inform Aerodrome Rescue & Fire Fighting Services & AOCC,
b) check ILS status
c) check lighting is correctly selected and operating properly
d) check transmissometer displays
e) check ASMGCS (for operations below RVR 350 m)
8.4.2 After the commencement of ILS CAT II/CAT III operations, the Aerodrome Tower Controller shalla) Check ATIS broadcast and include the message that “ILS CAT II/CAT III Low Visibility Procedures in Force”.
b) Give landing clearance to aircraft not later than 2NM from touchdown.
c) Inform changes in RVR readings to the landing aircraft.
d) Give an unimpeded taxi route to arriving aircraft to allow it to clear the Localizer Sensitive Area expeditiously.
e) Inform pilots of all failures of ILS, lighting system, transmissometers relevant to ILS CAT II/ CAT III Low Visibility Operations.
f) Initiate emergency action if aircraft on CAT II/CAT III ILS is not seen (on radar display or otherwise) or is not in radio contact, as expected.
8.4.2.1 Record of the above actions with time be maintained and signed by the officer taking action.
|
8.5. Action by Approach/Radar Controller
8.5.1 On being advised by WSO that ILS CAT II/CAT III Low Visibility Procedures are in force, the Approach/Radar Controller shall:-
a) Inform the arriving aircraft “ILS CAT II/CAT IIIA/CAT IIIB “Low VisibilityProcedures in Force”.
(Note: Ensure that Pilot acknowledges of being cleared for ILS CAT II/CAT IIIA/CAT IIIB approach.)
b) Inform TDZ RVR to arriving aircraft and in addition:
(i) For CAT II operations - If TDZ RVR is below 550m then MID RVR shall also be passed.
(ii) For CAT IIIA operations - If TDZ is below 300m, then MID & End RVR readings shall also be passed.
(iii) For CAT IIIB operations - If TDZ is below 175m then MID and END RVR shall be passed.
NOTE: After an aircraft is 8NM from Touch Down or has passed outer marker, RVR observations need not be passed unless there is changes in RVR values.
c) vector the aircraft to intercept the localizer not less than 10NM from touchdown.
d) Not subject an aircraft to any speed control when within 20NM from touchdown.
e) issue landing clearance to arriving aircraft not later than 2NM from touchdown.
8.6. Action by Surface Movement Controller
6.1 During the period the Low Visibility Procedures are effective the Surface Movement Controller shall:
a) Monitor all surface movement of aircraft and vehicles on the manoeuvring area.
b) Inform all taxiing aircraft of the preceding taxiing or holding aircraft.
c) Hand over only one aircraft at a time to Tower Controller.
d) Permit only the vehicles equipped with transponder in the manoeuvring area during Cat IIIB operations. However, other vehicles crossing taxiway crossings on service road shall be regulated by official of Airside Operations, DIAL by
deploying man power.
8.7. Action by Communication/Technical/Electronics Shift Supervisory Officer (SSO)
8.7.1 On receipt of “Outlook for LVP” from the WSO, the Communication/Technical/Shift Supervisory Officer [SSO] will inform the Duty Officer, Equipment Room and have the ILS equipment and its status indicators in ATC units checked up. He will inform WSO of any unserviceability in the equipment which is likely to affect ILS CAT II/CAT III operation.
8.7.2 On receipt of “Advisory Message” from WSO that LVP are to be made effective SSO will maintain continuous watch on the performance of ILS equipment and will inform WSO of any un-serviceability which may affect ILS CAT II/CAT III
operation.
9. Action by AOCC & Airside Operations, DIAL:
9.1 Action by Manager, AOCC
9.1.1 On receipt of advice from WSO to implement Low Visibility Procedures, the Duty Manager AOCC, will immediately inform the following:
a) Airport Duty Manager (Shift)
b) Operations Duty Manager
c) Shift Engineer (electrical) on company channel
d) Manager (Civil), Operational Area Maintenance to ensure that all civil works in progress in manoeuvring area, are stopped and that the work area is restored in complete serviceable condition and confirm to ODM/Apron Control
accordingly. During ILS CAT II/CAT III Low Visibility Operations, no equipment, manpower or material shall be present in sensitive areas of localizer and glide path.
e) Central Industrial Security Force (CISF) Control Room Cargo at 25601051
f) Domestic and International airlines via e-mail/SITA network.
9.2 Action by Operations Duty Manager/Apron Control
9.2.1 Operations Duty Manager/ Apron Control shall deploy manpower at barrier near gate no.2 to stop vehicular movement on the perimeter road around Runway 28 approach, except DIAL operational vehicles fitted with R/T and Transponders and
operating with prior clearance from ATC.
|
9.2.2 Operations Duty Manager shall ensure through follow me vehicle that vehicles do not operate on the service road beyond Gate No. 2. Signboards indicating CAT II/ CAT III operations shall be switched “ON”.
9.2.3 ODM/Apron Control shall deploy manpower at barrier on service road parallel to taxiway "P" for closing the barrier and stopping the vehicular movement.
9.2.4 During CAT II/CAT III operations, ODM/ Apron Control may authorize operations of vehicles, equipped with VELO, on manoeuvring area, including the crossing of taxiways, with the prior permission from ATC Tower. However, the vehicles, not equipped with VELO, crossing taxiway crossings on service road shall be regulated by official of Airside Operations, DIAL by deploying man power.
NOTE: Barrier near Gate No. 2 shall be in lowered position whenever LVP is in progress.
9.3 Follow-me vehicles:
9.3.1 Such vehicles shall ensure that
a) No vehicle/person enters or is present in the sensitive/critical areas of localizer and glide path.
b) All civil/electrical works in progress are to be stopped in the manoeuvring area immediately and men/material/equipment to be removed from the sensitive/critical areas of localizer and glide path.
9.3.2 After ensuring above, Follow-me vehicles will confirm the same to the ODM.
9.3.3 Subsequently, follow-me vehicle shall remain available in apron and will maintain listening watch on their respective frequencies, i.e., R/T 121.625 MHz, 121.90 Mhz and 121.75 MHz frequency.
9.3.4 On receipt of information about unserviceability of any of the runway visual aids or power supply system, ODM through AOCC will immediately inform ATC Tower accordingly.
9.3.5 No vehicles shall enter/cross in the vicinity of runway without permission from ATC Control Tower. Such vehicles shall be equipped with VELO and able to communicate with ATC. The vehicles of the ARFF services, civil, electrical
division or of any other agency which are not equipped with VELO and/ or RT but has to enter the runway or taxi track for urgent operational requirement shall be escorted by the follow me jeep all the time.
9.3.6 None of the workers/vehicles of grass cutting contractor, garbage removal contractor, and electrical/civil contractor shall enter the manoeuvring area during the operations of ILS CAT II/CAT III Low Visibility Procedures.
9.3.7 All coordination with DIAL units and ATC shall be carried out by AOCC.
9.3.8 ODM would advise ATC Tower/Watch Supervisory Officer when all actions are completed for commencement of LVP.
9.4 Action by Shift Engineers (Electrical)
9.4.1 On receipt of advice to implement Low Visibility Procedures from AOCC, respective Shift Engineer of T1, T2 & T3 (Electrical) along with ODM, will check that following visual aids associated with RWY28/29/11 are serviceable and can be
operated at full intensity.
a) Approach lighting system
b) Approach supplementary lighting
c) Runway edge lights
d) Runway threshold and end lights
e) Runway centre line lights
f) Runway touchdown zone lights
g) Stop Bar Lights
h) Intermediate holding position lights
i) RWY guard lights
j) TWY C/L lights
k) Stand manoeuvring lights
(NOTE - No adjustment in light intensity shall be made without permission from ATC Tower during LVP)
9.4.2 They shall ensure that no electrical maintenance works is carried out during LVP either in power house or on any other electrical facilities used during CAT II/CAT III operations.
9.4.3 They will ensure that runway switch room is manned and position themselves at CCR halls for standby power supply requirements and will maintain a listening watch on company frequency. They will ensure availability of power supply to meet CAT III requirement.
|
9.4.4 They will inform the un-serviceability or any change in status of any facility/systems to OMD immediately.
.
9.5 Action by Airport Duty Manager (ADM) - shift
9.5.1 ADM will be overall responsible for ensuring smooth coordination between all DIAL units and other concerned agencies. He shall inform regarding implementation of LVP to
a) Terminal Duty Manager, Terminal ID
b) Terminal Duty Manager, Terminal III
9.6 Action by Terminal Duty Manager-III To inform:
• CISF Control Room
•Duty Officer Cargo
• PRO Customs
• AFRRO (Assistant Foreigners Regional Registration Officer)
• Inspector, Delhi Traffic Police
9.7 Action by Fire Station-3 and Fire Station-1
9.7.1 Station Duty officer II will ensure that ARFF (Airport Rescue and Fire Fighting) vehicles equipped with serviceable transponder take predetermined positions. Following predetermined positions will be taken by ARFF vehicles:-
a) One CFT North of RWY28/10 near TWY D1
b) One CFT North of RWY 28/10 near TWY E.
c) One CFTs North of Z opposite Z5.
10. Action by Airport Security Police (CISF)
10.1 Chief Airport Security Officer shall ensure by deploying adequate manpower that power house and other vital electrical installations are properly secured and protected against any unauthorized intrusion.
10.2 The Inspector in charge, Control Room cargo, on receipt of advice to implement Low Visibility Procedures, will immediately inform all access gates and CISF posts under their respective controls in operational area to restrict and guide all the vehicles to use the service road towards RWY10 side only, for proceeding to Terminal-II and vice versa, till such time he is informed of termination of ILS CAT II / CAT III Low Visibility Procedures. They will not permit labour to enter
operational area while LPV are in force.
10.3 For carrying out security checks of their security personnel on RWY28 side, Inspector In-Charge of CISF Control Room I/II would be escorted by “Follow-Me Vehicles” equipped with transponder during CAT IIIB operations for which they would liaise with ODM.
11. Action by Duty Officer (Meteorological Office)
11.1 Duty Meteorological Officer would issue an 'Outlook for Low Visibility Procedures' to the Watch Supervisory Officer [WSO] of air traffic services whenever he expects that the RVR and/or cloud ceiling will fall below 800 m and/or
200ft or less respectively.
11.2 Whenever Duty Meteorological Officer visualizes that RVR is likely to fall below 800 m and/or cloud ceiling to 200ft or less within next 2 hours, he will issue an 'Advisory Message' to WSO to this effect.
11.3 When the RVR and/or cloud ceiling are 800m and/or 200ft respectively and the trend is towards improvement in these elements of weather Conditions the Duty Met Officer may, when requested by WSO, advise him about such improving
weather conditions for the purpose of termination of LVP.
11.4 The Duty Met Officer would ensure that the RVR displays in ATC units in the Control Tower and Approach Control are serviceable. He would also ensure that RVR/visibility recorders of Touch-down zone, Mid-point and end positions are
serviceable.
NOTE: Due to high variability of meteorological elements in space and time and the limitations of forecasting techniques available, it may not be always possible to issue a precise forecast of RVR particularly in case of transient weather phenomenon within two hours.
|
12. Action by Other agencies at airport such as - Airlines, Re-fuelling Companies,Catering Agencies, Airport Police, Customs, Immigration, Health
12.1 All agencies operating in the operational area shall ensure that minimum number of their vehicles, as are absolutely essential for aircraft operations, operate in the operational area. The drivers of these vehicles should keep a look out for taxing aircraft and other vehicles to prevent incident/ accidents. During CAT IIIB operations only vehicles equipped with serviceable transponder shall be permitted to operate in manoeuvring area.
12.2 All the vehicles must have their obstruction/ anti-collision lights “ON” during operation of low visibility procedures.
12.3 All vehicles operating between Terminal-I & Terminal-II/III shall use service road around RWY10 approach only.
12.4 Follow all instructions/sign boards provided on vehicular movement area/ service roads.
12.5 No vehicle/equipment/personnel shall enter in and around the vicinity of the runways or taxi-tracks except with prior permission of ODM, who in turn shall coordinate with aerodrome control tower.
13. TERMINATION OF LOW VISIBILITY PROCEDURES
13.1 When met conditions improve and TDZ, MID and END RVR are 800m or moreand the cloud ceiling is 200ft or higher and trend shows improvement, the WSO would terminate operation of LVP. He may obtain advice from Duty Met Officer,
as provided at Para 10.3, about the improving weather conditions for the purpose of termination of LVP operations.
13.2 The WSO will intimate the following regarding termination of LVP operations
a) Aerodrome Tower Supervisor
b) Approach/Radar Controller
c) Communication/Technical Shift Supervisory Officer (SSO)
13.3 Aerodrome Tower Supervisor will in turn inform AOCC, who will advise all thepreviously notified personnel to resume normal operations.
X. MODES OF OPERATION
1. INTRODUCTION:
IGI Airport, New Delhi has three runways i.e. 09/27, 10/28 and 11/29. These runways are used in various modes for optimal use of available ground and air resources. Particular mode of operation to be implemented is decided by ATC considering various factors including the prevalent weather conditions, visibility/RVR, serviceability of navigation & landing aids, ground infrastructure, traffic density and its composition, noise abatement requirements etc.
One/Two/ Three runway modes of operations shall be tactically utilized during low/high density traffic situations so as to attain the optimal capacity at all times.
2. OPERATING PRINCIPLES
a. The runway assignment to a particular flight is primarily done based on the concept of Proximity to the arrival/departure terminal. However, ATC may deviate from this principle of near terminal arrival/departure due to ground infrastructure constraints and/or load balancing to meet the objective of least average delay.
b. Change of runway to arrivals if any, will be intimated before the aircraft is at least 20 NM from touchdown. Within 20 NM of touchdown, change of runway will be affected only with the consent of Pilot-in-Command.
c. Independent arrivals on any two runways are not permitted. The sequence of arrivals on any two runways is considered as one stream for the purpose of separation and sequencing.
d. In case of dependent modes, the operation on two runways will be in the form of in-trail operations wherein a movement on arrival runway is considered as movement on departure runway and vice-versa for the purpose of applying relevant separation.
e. In independent mode for departures, simultaneous departures are permitted from both runways.
f. Simultaneous departures are not permitted from RWY 27 and RWY 28. Similarly, simultaneous departures are not permitted from RWY 09 and RWY 10.
3. MODES OF OPERATIONS
Three runways available at IGI airport are used in various modes. A particular mode of operation is employed depending upon various factors such as the prevalent weather conditions, visibility/RVR, serviceability of navigation & landing aids,
|
The available Runways can be used in following combination.
a. Westerly Flow: Various modes of operations in westerly flow are as under.
|
|
IV. OTHER DETAILS OF DOMESTIC TWYS
1. TWY W: Shoulder 17.5m on either side AVBL.
2. The Apron taxi lane behind the bays 1-13, is designated as ‘A’. Apron Taxi lane, suitable up to code letter ‘C’ aircraft.
3. TWY ‘A’ is north of stand No.1 joining RWY 27/09.
4. TWY E3 and E4: Shoulder width is 10.5M either side.
5. Rapid exit TWY E5: AVBL for RWY27.Distance 2100m from beginning of RWY 27, Angle of turn30 DEG, Radius of turn off curve 550m, fillets adequate for rapid exit, shoulder 10.5m either side, length 379m.Suitable for aircraft upto code letter E.
|
|
6. Rapid exit TWY D1: for RWY28, DIST from beginning of RWY28 2250M, angle of turn 30deg, radius of turn off curve 550m, fillets adequate for rapid exit, Shoulder 10.5M either side, LEN 460m, Suitable for code letter A, B, C, ACFT.
7. TWY F1: Connects TWY E2 to stand 133 front side. LEN 134.75M, shoulder 7.5M either side.
8. TWY F2: Connects TWY E2 to stand 133 rear side, LEN 52.525m, Shoulder 7.5M either side
9. TWY B3: Joins TWY E with domestic APRON, LEN 54m, Shoulder 11.5M either side, Suitable for code letter up to C aircraft
10. Exit TWY B: Connects to RWY 10 leading to domestic main APRON, Cross TWY E & merges old TWY B, distance from THR RWY10 2875m, Angle of turn 30 deg, Radius of turn off curve:160m, Shoulders 10.5M on both sides. Suitable for letter A, B, C, D, E. Dist. from C/L C TO C/L E 216M, from RWY 10-28 C/L to C/L E 108M, Total LEN 324m
11. TWY E2: Parallel to RWY 09/27, at a DIST 250 from CL RWY 09/27, towards south side of RWY 09/27, beginning from TWY E AVBL, LEN 1925m, Shoulders 10.5m either side, C/L LGT CAT-III. Due to presence of open drains on TWY strips all code letter E ACFT to exercise caution while taxing.
12. Extended portion of TWY E2: TWY E2 extended towards east from TWY E/E2 junction up to TWY A
Distance of TWY C1/E2 junction is 165M from centreline RWY27.
Distance of TWY A/E2 junction is 168 M from centerline RWY 27.
Surface: Concrete, Length: 798M, Width: 18M, Shoulders: 3.5M either side, PCN: 64/R/C/W/T.
Markings: Centerline, Edge, Lights: Centerline, Edge lights only on the curves suitable for Code A, B, C Aircraft
|
|
13. Link TWY B2: joins the extended portion of TWY E2 with taxi lane behind stand NR 31 to 40C.Surface: Concrete, Length: 65M, Width: 18M, PCN: 64/R/C/W/T. Markings: Centerline, Edge, Lights: Centerline, Edge lights only on the curves suitable for Code A, B, C Aircrafts
14. TWY F: Connects RWY 10 to TWY E & further leads to domestic APRON, for code letter C, Dist. from RWY 10 to THR 2350m, LEN 571M, Angle of turn 30 deg., Radius of Exit Curve 160m, Radius of Turn off Curve 160m, Width of TWY23m, Shoulder 10.5m on both sides, PCN: 64/R/C/W/T, entry to general aviation managed via. TWY F4. TWYF4 for code letter B.
15. TWY U: Rapid exit, suitable fillet AVBL, DIST. From RWY 10 THR 2350 M, 2875M, LEN 408M from RWY centerline up to TWY centerline P. Rigid Pavement. Shoulders 10.5m on both sides. Radius of turn off curve 550M. Angle of turn 30 degree. Compatibility code letter E. Fillets are AVBL for turning right to join TWY P.
16. TWY V: Rapid exit, suitable fillet AVBL, DIST: from RWY 10 THR 2875M., LEN 408M from RWY centerline up to TWY centerline P. Rigid Pavement. Shoulders 17.5m on both sides. Radius of turn off curve 550M. Angle of turn 30 deg. Compatibility code letter F aircraft. Fillets are AVBL (at intersection with TWY P) for turning right to join TWY P.
17. Taxiway M2 commissioned Length: 201.37, Width: 23M, Width of shoulder: 10.5M, Angle with RWY 115W/65E, Turning Radius: 50m, distance between TWY C/L lights: 15M on straight portion and 7.5M on curves, Pavement: Flexible, PCN:135/F/B/W/T, Transverse Slope:1.5%, Longitudinal Slope: Less than 1.5%, Coordinates: 283357.54N 0770524.91E Intersection with CL of RWY 28, 283350.07N 070527.59E Intersection with CL of TWY P.
18. Taxiway L2 commissioned Length: 277M, Width: 25M, Width of shoulder: 10.5M, Angle with TWY P 90 DEG, Turning Radius: 50m W/50m E, distance between TWY C/L lights: 15M on straight portion and 7.5M on curves, Pavement: Concrete, PCN:103/R/B/W/T, Transverse Slope: less than 1.5%, Longitudinal Slope: Less than 1%, Coordinates: 283339.19N 0770614.93E Intersection point of CL of TWY P & TWY L2, 283329.72N 0770612.13E Intersection point of CL of TWY R & TWY L2.
19.Taxiway P1 commissioned Length: 181.3 M, Width: 25M, Width of shoulder: 17.5M, Angle with RWY - 90 DEG, Turning Radius:48.75 M (C/L), Pavement: Rigid, PCN:101/R/B/W/T, Transverse Slope on Main :0.81 % (W), Carriage Way-0.65 % (E), Transverse Slope on Shoulder 2.5%.Aircraft Sutability: Upto Code letter ‘F’ Aircraft, Standard CAt II/CAT IIIB lights provided.
|
|
|
2. Link TWY S3 joining TWY Z at coordinates 283239.82N 0770511.80E with TWY Y at coordinates 283253.03N 0770515.43E. Length: 418M TWY Z CL to TWY Y CL, Width: 25M, Shoulders: 17.5M either side, PCN: 93/F/C/W/T Suitable for Aircraft: CODE F, Light: Centre Line, Edge Light: provided only at curves, Markings: Edge Line, Centre line, Intermediate Taxi Holding.
3. Existing TWY Y extended towards east up to a distance of 3632m from junction of TWY CW1 and TWY Y. Length of extended portion: 3632M, Width: 25M, Shoulders: 17.5m either side, PCN: 93/F/C/W/T, Suitable for aircraft: code F, Light: centreline, Edge light provided only at curves, Markings: edge line, centreline, intermediate Taxi Holding.
4. Existing TWY Z2 extended towards North up to a distance of 717M from junction of TWY Z2 and TWY Z. Length of extended portion: 717M, Width: 25M, Shoulders: 17.5M either side, PCN: 93/F/C/W/T Suitable for Aircraft: Code F, Light: Centre Line, Edge Light: Provided only at curves
|
|
Markings: Edge line, Centre line, Intermediate TAXI Holding.
5. Link TWY S2 joining TWY Z at coordinates 283231.84N 0770549.00E with TWY Y at coordinates 283244.47N 0770552.48E and with TWY T at coordinates 283247.54N 0770553.39E.
Length : 498M TWY Z CL to TWY T CL, Width: 25M, Shoulders: 17.5M either side, PCN: 93/F/C/W/T Suitable for Aircraft: Code F, Light: Centre Line, Edge Light: Provided only at curves.
Markings: Edge line, Centre Line, Intermediate TAXI Holding.
6. Portion of TWY T BTN TWY Z2 and S2, parallel to extended portion of TWY Y, starting from junction with extended TWY Z2 coordinates 283240.97N 0770621.81E towards West up to a distance of 800M. Length: 800M, Width: 25M, Shoulders: 17.5M either side, PCN: 93/F/C/W/T
Suitable for Aircraft: CODE F, Light: Centre Line, Edge Light Provided only at curves
Markings: Edge line, Centre line, Intermediate TAXI holding.
VI. SUITABILITY AND OTHER INFORMATION ABOUT AIRCRAFT PARKING STANDS
1. Apron I
i. Refer Aircraft Parking/Docking Chart
2. Terminal - II
i. Refer Aircraft Parking/Docking Chart
3. Aerobridges
i. One Aerobridge for L-2 door on stand nos. 44, 46, 47 & 49.
ii. Two Fingers (L1 & L2) doors on stand numbers 42, 43, 45 and 48.
iii. Aerobridges: Available on stands 41, 42, 43, 44, 48 & 49
4. Visual Docking Guidance System
i. Available on stands 41 to 44, 48 &49
5. Parallax Aircraft Parking Aids (PAPA)/Ground Markings Nose wheel bars/Marking for the following types of aircraft is also provided on stands 41 to 49.
i. Stand 41: B763, B762/DC10, A300, A310, and A330/340.
ii. Stand 42: B747, B763, B777, A300, A310, IL96, and A330/340.
iii. Stand 43: B747, B74S, B757, B763, B762/DC10, B777, A310, A320/ B737, A330/340.
|
|
iv. Stand 44: B747, B74S, B757, B767, A310, B777, and A330/340.
v. Stand 45: B747, B74S, B757, B767, B763, A320, and A330/340.
vi. Stand 46: B747, A310, A320, B737, IL96, and B777.
vii. Stand 47: B747, B757, B767, A300, A310, B777, DC10, IL96, A330/340, and A346.
viii. Stand 48: B747, B74S, B767, A300, A310, A330/340, A346,B747-300
ix. Stand 49: B747, B74S, B767, A300, A310, A320/B737, DC10, and A330/A340,B747-300.
x. Stand 88-92:B747-400.
6. Cargo Aron
i. Refer Aircraft Parking/Docking Chart
7. Apron 31-35
i. Refer respective Aircraft Parking/Docking Charts
8. Aircraft Stands 801, 802.
i. Refer related Aircraft Parking/Docking Charts
|