VECC |
AD 2.2 |
|
CTR: Circular area centered on ARP VECC (223914N 0882648E) within a 25NM radius. | ||
|
Airspace from 4000 FT AMSL and above is Classified as Class ‘C’. |
|
International Voice SAR On Scene Frequency 123.1MHZ Is Operational | ||
|
Type of aids, magnetic variation and type of supported operation for ILS/MLS, basic GNSS, SBAS and | |||
|---|---|---|---|
|
LLZ inner coverage is restricted to 30 DEG on 150HZ side, no restriction on | |||
1.3 A-CDM application is developed in-house by Airports Authority of India.1.4 A-CDM system processes and utilizes the following information from the various sources mentioned below:a) AFTN:i) Flight plan dataii) EOBTiii) ATDiv) ETAsv) NOTAMsvi) METARsvii) ADC Numbersb) Airport Operations Data Base (AODB) of Kolkatai) Parking stand of Aircraftii) Registration markingiii) Boarding status of departing aircraftiv) Actual “Off Block” Timesv) Actual “In-Block” Timesc) A-CDM system databasei) Arrival and Departure Taxi timings from each parking standii) Runway-in-Use and Closuresiii) Hourly handling capacity of runwaysiv) Priority of flights e.g. VVIP and Emergencies etc.v) Flight schedules1.5 A-CDM is a Common Information Sharing Platform introduced to process timely and accurate information for quick and precise decision making. A-CDM takes into consideration the ETAs of arriving aircraft, Target Off Block Times of departures, Runway-in-use and the handling capacity of the runway and determines the arrival and departure sequence. Based on the sequence and the parking position, it calculates the Target Take-Off Times & Target Start up Times of departures and Target In-Block Times for arrivals.1.6 Implementation of ACDM will result in considerable benefits to stakeholders. The various benefits of A-CDM includes are as follows:• Improvement in efficiency of operations• Reduction of delays to departures at holding point.• Orderly flow of traffic.• Reduction in wastage of Aviation fuel.• Reduction in Carbon Emission, reduction in Environmental Pollution.• Optimization of airport and airspace capacity Reduction of R/T congestion• Enhancement of safety due to reduced R/T congestion.• Better Situational Awareness and increased confidence amongst ACDM Partners.• Adherence to ADC (Air Defence Clearance) by stake holders. |
• Better Passenger experience.• Optimized use of ground handling resources• Optimized use of parking stands, gates and terminals.• Reduced apron and taxiway congestion• Access to current MET information.2. TWO KEY PARAMETERS OF A-CDM, Kolkata: TOBT and TSAT2.1 TARGET OFF-BLOCK TIME (TOBT)2.1.1 Definition: The time that an Aircraft Operator 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). It is the real time target of ensuring readiness of an aircraft and therefore, more accurate than the static departure time mentioned in the flight plan and hence, an ideal milestone to be used by all airport partners.2.1.2 Purpose: Air Traffic Management (ATM) based on only FPL-data 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 aircraft. The result is that airport partners will have an incorrect idea about the actual status of that specific aircraft. The purpose of Target Off-Block Time (TOBT) is to provide a timely, accurate and reliable estimate of an aircraft's off block time to the A-CDM, Kolkata partners. 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.2.1.3 Communication of TOBT: Aircraft Operators shall revise their EOBTs via AFTN using CHG/ DLA message or inform ARO for revised EOBT, who in turn will originate CHG / DLA message for transmission through AFTN.2.1.3.1 In case No delay is expected: If there is no revision of EOBT, EOBT will be treated as the TOBT. For such cases there is no need of any communication from the Aircraft Operator to the ARO.2.1.3.2 In case delay is expected:a) When Air Defence Clearance (ADC) is valid: If delay is within the validity period of ADC, EOBT should berevised through CHG/DLA message. Optionally TOBT can be changed in ACDM interface. But if due to somereason coordination is not possible by both the above methods then EOBT can be revised by informing ARO/MCD.b) When Air Defence Clearance ADC is NOT valid:i) If delay is outside the validity period of ADC, EOBT shall be revised through CHG/DLA message or afterhaving coordinated with MLU and obtaining the revised ADC number, by informing ARO/MCD aboutrevised EOBT and ADC. (Option of change of TOBT will not be available in this case).ii) ADC Validity Period: (-) 15 minutes to (+) 45 minutes of EOBT in RPL/FPL or subsequent revision of EOBTby DLA/CHG message.Note: Once Target Start-up Approval Time (TSAT) is allocated by ATC at TOBT - 30 minutes, the TOBT can beupdated thrice.2.1.4 Accuracy: TOBTs must be updated to an accuracy of +/- 5 minutes. |
2.2 TARGET START UP APPROVAL TIME (TSAT)2.2.1 Definition: The time is calculated by A-CDM application taking into account TOBT, CTOT* and/or the traffic situation that an aircraft can expect to start-up/push back for departure.Note: In case there is no congestion, ATC may allow the aircraft to start, where Actual Start-up Approval Time(ASAT) will be before the TSAT.2.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 ensuring optimised utilisation of the runway. ATC will continue to optimize the departure order for creating the right mix of traffic.2.2.3 Calculation of TSAT: TSAT is calculated automatically by A-CDM Application. The TSAT is calculated by taking into account TOBT, priority of aircraft, variable taxi times, and the runway capacity. Any revision of EOBT will trigger the A-CDM application to recalculate a new TSAT for that flight as well as to re-allocate earlier TSAT to next flight which meets the requisite conditions. TSAT is displayed in various ACDM interfaces in the following colour coded information.Blue colour: TSAT -15 minutes up to TSAT -5 minutes’ Green colour: TSAT -5 minutes up to TSAT +5 minutes Red colour: After TSAT +5 minutes.2.2.4 Generation of TSAT: TSAT is generated by ACDM interface at TOBT - 30 minutes.2.2.5 Communication of TSAT: TSAT will be displayed in various A-CDM interfaces. The AO/GHA shall advise flight crew of TSAT, displayed in the A-CDM interface.2.2.6 Priorities for generation of TSAT:The following aircraft will be accorded priority by A-CDM application at the time of generating TSATs:a) VVIP flightsb) Aircraft in emergencyc) Ambulance aircraftd) Aircraft in relief missionse) Aircraft returning to stand after push back/taxiing out for any reason.2.2.7 Airlines/GHAs are required to monitor the A-CDM interface regularly to get information on the revised TSAT if any, in respect of their aircraft. It may please be noted that the earlier allocated TSAT may get changed due to the following reasons:i) Change of runwayii) Change in taxi timesiii) Revised TOBT of the subject aircraftiv) Cancellation/ revision in TOBT of other aircraft in the departure sequence.v) Priority handlingvi) Unusual Occurrences, etc.vii) Change of aircraft type*viii) Application of ATFM regulation or ATC restriction resulting in new CTOT or start up delay*ix) Inclement Weather* |
x) Bird activity*xi) Change of route (SID)*2.2.8 Accuracy: The TSAT will remain valid for +/- 5 minutes.3 Co-ordination with the Central Air Traffic Flow Management Unit (CATFMU)*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.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 A-CDM, Kolkata Start-up/Push-back procedures4.1 Pre-Departure Sequence: Pre-Departure sequence is the order, in which the ATC plans the aircraft to depart from their Gate/Stands. 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.2 Start-Up and Push-Back Procedure:i. The pilot will contact Clearance Delivery (CLD) to request en-route clearance and SID between TSAT - 15minutes to TSAT - 5 minutes. Blue Zone.ii. The aircraft must be ready to Start-up/Push-back at TOBT and request SMC (GROUND) for Start-up/Push-back at TSAT - 5 minutes and TSAT + 5 minutes. Green Zone.(Note: The system may prepone TSAT up to TOBT)iii. In case for Schedule Flight, “Boarding” has not started at or before TSAT - 5 Minutes, allotted TSAT will becancelled and associated slot will be allocated to next eligible aircraft.a. A new TOBT is required from Airlines Operator.b. On receipt of new TOBT, the flight will be re-sequenced according to new TOBT and a new TSAT with a subsequentdelay will be issued.iv. If at TSAT +5 minutes: Red Zone, ATC has not received Start-up/Pushback request, the aircraft will lose itsposition in sequence.a. A new TOBT is required from Airlines Operator.b. On receipt of new TOBT, the flight will be re-sequenced according to new TOBT and a new TSAT with a subsequentdelay will be issued.v. ATC should normally be able to issue start-up/push-back at TSAT. Pilots will be informed by ATC of any revisedTSAT if there is a delay to TSAT in excess of 5 minutes.vi. Taxi clearance must be requested within 5 minutes of Start-up/Pushback approval time.(Note: If this has not occurred, SMC (GROUND) must be notified of the extent of delay. In such cases, aircraft maylose its departure slot and a new TOBT may be required in A-CDM, Kolkata interface. AO shall be responsible toobtain new ADC number from IAF-MLU).vii. 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 onActual Departure sequence. |
(Note: Actual Departure sequence may differ from pre-departure sequence in order to optimize the Runway andAirspace utilization.)* [Future provision kept for incorporating with India - Central Air Traffic Flow Management]5 TERMS AND ABBREVIATIONSAll Acronyms are time parameters which have a standard length of four characters and have been arranged as peraircraft movement sequence.[While developing the A-CDM, Kolkata procedures, the guidance material published by Euro control, ICAO A-CDM andother Organizations has been used]. |
S.NO. |
ACRONYMS |
DEFINITION |
EXPLANATION |
5.1 |
ELDT |
Estimated LandingTime |
The estimated time that an aircraft will touchdown on the runway. (Equivalent to ATC ETA = Estimated Time of Arrival = landing). |
5.2 |
ALDT |
Actual LandingTime |
The time that an aircraft lands on a runway. (Equivalent to ATC ATA = Actual Time of Arrival = Landing, ACARS = ON). |
5.3 |
EXIT |
Estimated Taxi- InTime |
The estimated taxi time between landing and inBlock. |
5.4 |
AXIT |
Actual Taxi-InTime |
AXIT = AIBT - ALDT |
5.5 |
SIBT |
Scheduled InBlock Time |
The time that an aircraft is scheduled to arrive at its first parking position. |
5.6 |
EIBT |
Estimated InBlock Time |
The estimated time that an aircraft will arrive inblocks.(Equivalent to Aircraft Operator’s ETA = Estimated Time of Arrival). |
5.7 |
AIBT |
Actual In-BlockTime |
The time that an aircraft arrives in-blocks. (Equivalent to Aircraft Operator’s ATA = Actual Time of Arrival, ACARS = IN). |
5.8 |
STTT |
ScheduledTurnaround Time |
STTT = SOBT - SIBT |
5.9 |
ETTT |
EstimatedTurnaround Time |
The time estimated by the AO/GH on the day of operation to turnaround a flight taking into account the operational constraints. |
5.10 |
MTTT |
MinimumTurnaround Time |
The minimum turnaround time agreed with an AO/GH for a specified flight or aircraft type. |
5.11 |
ATTT |
ActualTurnaround Time |
ATTT = AOBT - AIBT |
5.12 |
ASRT |
Actual Start UpRequest Time |
Time the pilot requests start up clearance. |
5.13 |
TSAT |
Target Start UpApproval 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. |
5.14 |
ASAT |
Actual Start UpApproval Time |
Time that an aircraft receives its start-up approval. |
5.15 |
SOBT |
Scheduled OffBlock Time |
The time that an aircraft is scheduled to depart from its parking position. |
5.16 |
EOBT |
Estimated OffBlock Time |
The estimated time at which the aircraft will start movement associated with departure (ICAO) |
5.17 |
TOBT |
Target OffBlock Time |
The time that an Aircraft Operator 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). |
5.18 |
AOBT |
Actual OffBlock Time |
Time the aircraft pushes back / vacates the parking position. (Equivalent to Aircraft Operator’s ATD = Actual Time of Departure & ACARS = OUT) |
5.19 |
ARDT |
Actual ReadyTime(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. |
5.20 |
EXOT |
Estimated TaxiOut 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. |
5.21 |
AXOT |
Actual Taxi-OutTime |
AXOT = ATOT - AOBT |
5.22 |
ETOT |
Estimated TakeOff Time |
The estimated takeoff time taking into account the EOBT plus EXOT. |
5.23 |
CTOT* |
Calculated TakeOff 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)* |
5.24 |
TTOT |
Target Take OffTime |
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. |
5.25 |
ATOT |
Actual Take OffTime |
The time that an aircraft takes off from the runway. (Equivalent to ATC ATD = Actual Time of Departure, ACARS = OFF). |
|
DOPID N205503.2 E 0891216.1 - 339 DEG/112NM ---CEA VOR N223842.6 E0882710.4 | |
|
BUBKO N191103.7 E0883950.5 - 349 DEG/151NM -- |
|
The last cleared and acknowledged level or FL230/ FL220, (appropriate to the direction of the flight) whichever is lower. | |
|
Stop climb at the next level appropriate to the direction of the flight. |
VECC |
ADDITIONAL INFORMATION |
I PARKING STANDS |
II. TAXIWAYS |
II. TAXIWAYS | |||||
Designation |
Width |
Surface |
PCN |
Edge Lights (EL) / Centre Line lights(C/L) |
Other lights available |
A |
23 |
BITUMEN |
55/F/C/W/T |
C/L |
Guard Lights & Stop Bar |
B |
23 |
CONCRETE |
35/R/C/W/T |
E/L |
Guard Lights |
C |
23 |
BITUMEN |
39/F/C/W/T |
E/L |
Guard Lights & Stop Bar |
D |
23 |
CONCRETE |
|
C/L |
Guard Lights & Stop Bar |
E |
15.5 |
BITUMEN |
27/F/C/W/T |
E/L |
|
F |
23 |
CONCRETE |
50/R/C/W/T |
E/L |
|
F1 |
23 |
CONCRETE |
50/R/C/W/T |
C/L |
Apron taxilane |
F2 |
23 |
CONCRETE |
103/R/C/W/T |
C/L |
Apron taxilane |
H |
25 |
CONCRETE |
100/R/C/W/U |
E/L |
|
H1 |
25 |
CONCRETE |
100/R/C/W/U |
E/L & C/L |
|
J |
25 |
CONCRETE |
100/R/C/W/U |
E/L |
|
J1 |
25 |
CONCRETE |
100/R/C/W/U |
E/L & C/L |
|
K |
23 |
CONCRETE |
100/R/C/W/T |
E/L & C/L |
Guard Lights |
R |
23 |
CONCRETE |
80/R/C/W/U |
E/L |
|
A Extd. Port. |
25 |
CONCRETE |
100/R/C/W/U |
E/L |
|
Type of Operation |
RVR | ||
|
|
Touch-downZone |
Mid zone |
Roll-out zone |
CAT I |
550 m |
125 m |
125 m |
CAT II |
300 m |
125 m |
125 m |
CAT III A |
175 m |
125 m |
125 m |
CAT III B (withroll-out guidance) |
75/50 m |
75/50 m |
75/50 m |
Table 4-1 |
Table 4-2 |
RWY 19L(When portion of A north of TWY C not available) |
Arrival taxi routes to Apron2 &Apron3 |
Vacate via TWY D, taxi via Rwy 19R, J, J1, andthen via:i. F1 to stand 48 to 56L (Apron2)ii. F2 to stand 57 to 61L (Apron3) |
Departure taxi routes fromApron2 & Apron3 |
Taxi to CAT II holding point RWY 19L viai. Stands 48 to 56L (Apron2)- F1, H1, A, Cii. Stands 57 to 61L (Apron3)- F2, H1, A, C | |
Hotspot |
i. Junction of F1, F2, H1, J1 | |
Bidirectional taxi routes |
i. F1ii. F2 | |
RWY 19L(When TWY F not available) |
Arrival taxi routes to Apron2 &Apron3 |
Vacate via TWY D, taxi via Rwy 19R, J, J1, andthen via:i. F1 to stand 48 to 56L (Apron2)ii. F2 to stand 57 to 61L (Apron3) |
Departure taxi routes fromApron2 & Apron3 |
Taxi to CAT II holding point RWY 19L viai. Stands 48 to 56L (Apron2)- F1, H1, A, Kii. Stands 57 to 61L (Apron3)- F2, H1, A, KNote: Aircraft may be permitted to enter Runway 19L via taxiway A, when pilot informs about his intention to depart from ‘A’ intersection or when taxiway K is not available. | |
Hotspot |
i. Junction of F1, F2, H1, J1 | |
Bidirectional taxi routes |
i. F1ii. F2 |
Table 4-3 |
ANNEXURE “A”ACTIONS TO BE TAKEN BY VARIOUS AGENCIES6.1 Before commencement of winter season, a meeting will be held by Airport Director NSCBI Airport, AAI along with all stake-holders, 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.6.2 All the agencies shall ensure that staff and drivers are suitably trained during LVP operations.6.3 ACTION BY WATCH SUPERVISORY OFFICER (WSO), AAI6.3.1 Implementation of 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 shall initiate Safeguarding Procedures and inform:a) AOCCb) Communication/ Technical supervisor (SSO)c) Tower Supervisor (TSO).d) Duty Met Officer6.3.2 Implementation of LVP6.3.2.1 WSO shall implement Low Visibility Procedures when eithera) TDZ, MID or END RVR is less than 800m; and/or Cloud ceiling is less than 200ft.andb) Safeguarding Procedures (SP) have been completed and the airport is configured for Low Visibility Operations.6.3.2.2 WSO shall inform:a) Aerodrome Tower Supervisor (TSO).b) Approach Radar Controller (TAR)c) Communication/Technical Shift Supervisory Officer (SSO)d) Duty Met. Officer6.3.3 Termination of LVP/ SP:6.3.3.1. WSO may terminate LVP when;a) Meteorological conditions improve and TDZ, MID & END RVR are 800 m or moreand the cloud ceiling is 200 ft or higher, and trend is for improvement for both runways, orb) Facilities, equipment and services necessary for CAT II/CAT III operations are degraded and/or the prevailing conditions are considered unsafe for such operations. |
6.3.3.2. WSO should intimate cancellation of LVP to:a) Aerodrome Tower Supervisor (TSO).b) Approach Radar Controller (TAR)c) Communication/Technical Shift Supervisory Officer (SSO)6.3.3.3. In case SP has been completed, but LVP is not initiated and subsequently meteorological conditions improve such that the visibility/RVR is more than 1200m, cloud ceiling is 400 ft or higher and both are forecast to remain above the required SP criteria, WSO may cancel SP.6.4 ACTION BY TOWER SUPERVISOR:6.4.1 On being notified by WSO that Safeguarding Procedures have been initiated, TSO shall:a) inform Aerodrome Rescue & Fire Fighting Services,b) check ILS statusc) check that AGL is correctly selected and operating properlyd) check RVR displayse) check ASMGCS status (for operations below RVR 350 m )6.4.2 On commencement of Low Visibility Procedures, TSO shall:a) inform Aerodrome Rescue & Fire Fighting Services & AOCCb) Check ATIS broadcast and include the message that “ILS CAT II/CAT III Low Visibility Procedures in Force”.c) Ensure that record of all actions pertaining to ATC is maintained with time and signed by the officer taking action.6.4.3 TSO shall promptly inform SSO and/or AOCC, as appropriate, of any unserviceability of ILS/ AGL observed or reported.6.4.4 On cancellation of LVP by WSO, TSO shall inform all concerned agencies and include “LOW VISIBILITY PROCEDURES ARE CANCELLED” in the subsequent two ATIS broadcasts.6.5 ACTION BY TOWER CONTROLLER6.5.1 After the commencement of Low Visibility Procedures, Tower Controller shall:a) Give landing clearance to aircraft not later than 2NM from touchdown.b) Inform changes in RVR readings to the landing aircraft.c) Give an unimpeded taxi route to arriving aircraft to allow it to clear the Localizer Sensitive Area expeditiously.d) Inform pilots about failures of ILS, lighting system, transmissometer relevant to ILS CAT II/ CAT III Low Visibility Operations.e) Initiate emergency action if aircraft on CAT II/ CAT III ILS is not seen (on radar display or otherwise) or not in radio contact, as expected. |
6.6 ACTION BY SURFACE MOVEMENT CONTROLLER6.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 squids in the manoeuvring area during CAT IIIB operations. However, other vehicles crossing taxiway-service road crossings, shall be regulated by AOCC.6.6.2 Pilots need additional guidance and information when taxiing during periods of reduced visibility. The view from the cockpit of the aircraft is very limited. Therefore, taxi instructions and essential traffic information should be passed in a clear and concise manner.6.6.3 Aircraft should be assigned taxi-routes in accordance Tables 4-1 & 4-2, as far as practicable. However, due to infrastructural constraints at NSCBI Airport, Kolkata, there are some conflicting taxiway intersections as well as overlapping portions in arrival and departure taxi routes in Table 4-1& 4-2. Sometimes, it may be necessaryto route aircraft via alternative taxiways due to operational reasons.6.7 ACTION BY APPROACH/RADAR CONTROLLER6.7.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 Visibility Procedures 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 also be passedNOTE: 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) Provide suitable spacing so as to ensure that landing clearance can be issued to arriving aircraft not later than 2NM from touchdown. |
6.8 ACTION BY CNS SHIFT SUPERVISORY OFFICER (SSO)6.8.1 On receipt of “Outlook for LVP” from the WSO/TSO, SSO shall:a) inform the Duty Officer, Equipment Roomb) check the status of:i. Main and standby ILS system (LLZ/Glide Path/ILS-DME); andii. Indicators in the ATC units.iii. ASMGCSc) Inform WSO/Tower Supervisor of any un-serviceability in the equipment which is likely to affect ILS CAT-II/CAT-IIIA/CAT-III-B operation.6.8.2 On receipt of “Advisory Message” from WSO that LVP are to be made effective SSO shall maintain continuous monitor the performance of ILS equipment and will inform WSO of any un-serviceability which may affect ILS CAT II/CAT III operation.6.9 ACTION BY DUTY OFFICER, METEOROLOGICAL OFFICE6.9.1 Duty Met Officer shall issue an 'Outlook for Low Visibility Procedures' to the Watch Supervisory Officer [WSO] whenever RVR Runway 19L/01R is 1200m or less and visibility/RVR is forecast to deteriorate to 800 meters or less and/or cloud ceiling is 400 ft or less and expected to fall to 200 feet or less.6.9.2 Whenever RVR Runway 19L/01R is likely to fall below 800 meters and/or cloud ceiling is likely to fall to 200 feet or less within next two hours, the Duty Met Officer shall issue an 'Advisory Message' to WSO. (All the relevant transmissometer are serviceable.6.9.3 Whenever the RVR and/or cloud ceiling are 800 meter or more and/or 200 feet or more respectively with trend towards improvement, the Duty Met Officer shall advise WSO about such improving weather conditions for the purpose of termination of LVP operation.6.9.4 The Duty Met Officer shall ensure that the all the Met equipment including RVR displays in ATC units in the Control Tower and Approach Control are serviceable. He shall also ensure that RVR/visibility recorders of Touch down zone, Mid-Point and Roll-out 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. |
6.10 ACTION BY AOCC:6.10.1 ACTION BY DUTY MANAGER, APRON CONTROL/ AOCC6.10.1.1 On receipt of instruction regarding implementing Safeguarding Procedure (SP) from ATC, duty Manager Apron Control/AOCC shall initiate following actions:a. Inform all users of apron (airlines/stakeholders) regarding initiation of SP through email by using the following text: "SAFEGUARDING PROCEDURE IMPLEMENTATION IN PROGRESS".b. Restrict vehicular traffic on movement area. This shall be achieved by advising CISF Control Room (39874573) to stop entry of vehicles through vehicle entry gate nos. 01, 05 and 07.c. Close the available gates on perimeter road leading to critical / sensitive area of navigational aids:-i. Gate opposite watch tower no. 04ii. Gate opposite watch tower no. 07iii. Gate near glide path RWY 19L (opposite watch tower no. 11)iv. Provide temporary barriers to stop the vehicular traffic on outer perimeter road:v. Near Bakra gate no. 07 (towards Cargo apron).vi. Near watch tower no. 02.d. Temporary barriers to stop the' movement of vehicular traffic on Apron be provided at the following locations:i. On vehicular lane junction opposite Air India hanger.ii. On vehicular lane adjacent to parking stand no. 6l.iii. On vehicular lane in between parking stand no. 56 and 57;iv. On vehicular lane leading to Apron (in between stand no, 46 and 48),v. On vehicular lane leading to Apron (in between stand no. 43 and 44).vi. On vehicular lane adjacent to stand no. 41.vii. On vehicular lane opposite parking stand no. C-2e. Vehicles fitted with Squid shall only be permitted to operate on maneuvering area.f. Inform AGL shift supervisor over walkie-talkie to check and confirm serviceability/availability of UPS & Generator and keep the DG Set in to Auto operation mode. |
g. Inform Civil and Electrical Maintenance Division to suspend all works in progress in operational area and removal of men, machinery and material from the work site, if in progress.h. Inspect following facilities with AGL Shift supervisor to ensure serviceability / availability:-i. RWY 01R ALS (CAT-III B),ii. Runway edge lights,iii. Runway threshold and end lights,iv. Runway Centre line lights,v. Runway touchdown lights,vi. Runway guard light and stop bar lights,vii. Taxiway edge lights and taxiway centre line lights,viii. Taxi-holding position lightsi. Inform WSO/TSO regarding completion of Safeguarding Proceduresj. Inform all users of Apron (airlines/stakeholders) regarding completion of safeguard procedure and/or enforcement of Low Visibility Procedure through e-mail by using the following text-"Safeguard Procedure Implemented”, and/ or “Low Visibility Procedure Enforced" respectively and thereafter confirm compliance to ATC Tower.k. In case of continuous departure (gap between the departures is 10 minutes or less) or otherwise, as and when aircraft is pushed back for departure under LVP, ensure that AGL is running on UPS and Genset in Auto Mode.l. Switch-off secondary power supply in co-ordination with ATC Tower if there is no arrival and/or departurem. Ensure availability of 'Follow Me' service to aircraft as and when requested by ATC.n. No vehicle on Apron shall enter / cross in the vicinity of runway or any taxiway without permission from ATC tower.o. Positive co-ordination to be ensured with ATC tower, if any vehicle of Fire Services, Civil/Electrical Division or any other agency has to enter the runway or taxiways for urgent operational requirement.p. As and when ATC notify tor withdrawal of Safeguard Procedure, all concerned may be intimated through e-mail by using the following text."SAFEGUARD PROCEDURE WITHDRAWAL IN PROGRESS”q. When Safeguard Procedure is withdrawn, cancellation of LVP shall be intimated to all concerned through e-mail by using the following text -"SAFEGUARD PROCEDURE WITHDRAWN AND LOW VISIBILITY PROCEDURE CANCELLED"and confirm compliance to ATC Tower. |
6.11 ACTION BY SHIFT ENGINEERS (ELECTRICAL)6.11.1 On receipt of notification to implement Safeguarding Procedures / Low Visibility Procedures from AOCC/Apron Control, AGL Shift Supervisor will initiate following actions:a. Check in co-ordination with Apron Control that following visual aids associated with RWY 01R/ RWY 19L are serviceable and can be operated at full intensity.i. RWY 01R ALS (CAT-III B)/ RWY 19L ALS (CAT - II),ii. Runway edge lights,iii. Runway threshold and end lights,iv. Runway Centre line lights,v. Runway touchdown lights,vi. Runway guard light and stop bar lights,vii. Taxiway edge lights and taxiway centre line lights,viii. Taxi-holding position lights,Note: No adjustment of light intensities shall be made without permission from Control Tower.b. Inform the serviceability of above visual lighting aids to Airport Manager, AOCC.c. Ensure that AFL Sub Station and CCR Hall is manned and position himself at CCR Hall AGL SCADA Monitoring Station and ensure the power supply arrangements as specified at Para 5.2.3 above.d. Inform the un-serviceability or any change in status of any facility/systems to Airport Manager, Apron Control/AOCC immediately.e. 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 operationsf. Maintain a constant listening watch on R/T 146.2 MHz6.12 ACTION BY SHIFT ENGINEERS (CIVIL)6.12.1 On receipt of notification to implement Safeguarding procedure / Low Visibility Procedures from AOCC/Apron Control, Shift Engineer, Civil Section will initiate following actions and confirm to AOCC/apron Control.a. Stop the work, if in progress, in the operational area.b. Remove men, machinery and material from the work site and ensure that they should leave the operational area.c. Resuming of work shall only be initiated after obtaining positive clearance from Apron Control/ AOCC. |
6.13 ACTION BY AIRPORT MANAGER (DEPARTURE)6.13.1 The Airport Manager (departure) will be overall responsible for ensuring smooth coordination between all AAI units and other concerned agencies. He will also ensure that all entry/exit through NTS gates to airside are restricted and all gates shall remain closed during LVP6.14 ACTION BY AIRPORT RESCUE & FIRE FIGHTING SERVICE (ARFFS)6.14.1 On receipt of notification of implementation of safeguarding procedures/LVP, Airport Rescue arid Fire Fighting Service (ARFFS) will proceed to Pre-determined Positions (PDPs) after obtaining positive clearance from ATC prior before entering maneuvering area. ADC and SMC should provide the maximum assistance in directing ARFFS to required location6.15 ACTION BY AIRPORT SECURITY POLICE (CISF)6.15.1 On receipt of notification from Apron Control that safeguarding procedure is being implemented, CISF Control Room shall initiate following actions: |
a. Inform all access gates leading to operational area and CISF Posts under their respective controls in operational area to STOP entry of vehicles/personnel.b. Confirm compliance on above to Apron Control.c. Only essential vehicles may be permitted to use service road.d. For carrying out security checks of CISF security personnel, security vehicles will be escorted by Follow-me service in co-ordination with Apron Control.e. The Inspector in-charge shall ensure that movement of security personnel is restricted through NTB gate only Officer shall ensure by deploying adequate manpower that power house and other vital electrical installations are properlysecured and protected against any unauthorized intrusion.6.16 ACTION BY OTHER AIRPORT AGENCIES (AIRLINES, REFUELING COMPANIES, CATERING AGENCIES, AIRPORT POLICE, CUSTOMS, IMMIGRATION, HEALTH ETC.) :6.16.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 taxiing aircraft and other vehicles to prevent accidents.6.16.2 All the vehicles must have their obstruction lights "ON" during operation of low visibility procedures.6.16.3 Follow all instructions/sign boards provided for vehicular movement area/service roads.6.16.4 No vehicle/equipment/personnel shall enter in and around the vicinity of the runways or taxi-tracks except with prior permission of AAI Apron Control who in turn shall coordinate with aerodrome control tower. |
|
|
|
|
|
IV TRANSPONDER OPERATING PROCEDURESFor Departure:1.At The Gate/Stand: Select Stby and enter the Discrete SSR Code received from Clearance Delivery and the three letter ICAO Designator followed by the Flight Identification Number through the FMS or the Transponder Control Panel,depending on the Airborne Equipment.2.On requesting Pushback/Taxi (Whichever is earlier): Select Transponder or equivalent and auto if available3.When Lining Up: Select TCAS only after receiving the clearance to Line UpFor Arrival:1.When on the Runway keep TCAS(TA/RA) selected2.After vacating the Runway: Select Transponder or equivalent and Auto if available TCAS shall be deselected when vacating the Runway.3.Parked on Stand: Select Stby:Note:When on ground the aircraft must squawk Mode C,in order to provide the altitude information to the Surveillance System. |