Letter of Agreement for Coordination Procedures Between Kolkata and Nagpur ACC (VANP/ATM/2024/V1.01)

Document Identification and Objective

• Document Title: Letter of Agreement for coordination procedure between Kolkata and Nagpur.
• Document Reference Number: $VANP/ATM/2024/V1.01-LOA-VECC-VANP$.
• Date of Issue: $11/01/2024$.
• Effective Date: The provisions in this Letter of Agreement (LOA) shall be effective from the date $22.01.2024$.
• Objective: To define Air Traffic Services (ATS) coordination procedures for aircraft operating between the Kolkata Area Control Centre (ACC) and Nagpur Area Control Centre (ACC) to ensure a safe, orderly, and expeditious flow of air traffic.
• Controlled Copy Maintenance:
  • If the number is in $RED$ color: It is a "Controlled Copy".
  • If the number is in $BLACK$ color: It is an "Uncontrolled Copy".
  • Current Controlled Copy Number: $02$.

Scope and Jurisdictional Authority

• Supplementary Nature: The procedures contained within this LOA are supplementary to:
  • AIP India.
  • ICAO Standards and Recommended Practices (SARPs) contained in Annexes $2$ and $11$.
  • Procedures for Air Navigation Services (PANS) in Document $4444$.
  • Regional Supplementary Procedures (DOC $7030$).
  • Manual of Air Traffic Services-I (MATS-I).
  • The Asia/Pacific Regional Interface Control Document (ICD) version $3.0$ (September $2007$).
  • Relevant DGCA CARs and Air Traffic Management Circulars.
• General Responsibility: The responsibility for the provision of air traffic services lies with the respective Area Control Centres within their jurisdictions unless otherwise specified.
• Transfer of Responsibility: Transfer of responsibility for the provision of air traffic services lies between the Kolkata Area Control Centre and Nagpur Area Control Centre.

Amendment and Deviation Procedures

• Permanent Changes: Any permanent change, including amendment or cancellation, requires the consent of the appropriate ATS authorities, covering both the substance and the date of applicability.
• Written Amendment: Permanent amendments shall be effective only in the form of a written amendment duly signed by authorized representatives.
• Temporary Deviations:
  • May be agreed upon between the Watch Supervisory Officers (WSOs) concerned.
  • Permitted only in exceptional circumstances and with prior coordination on a case-to-case basis.
• Emergency Deviations: Any deviations arising due to an emergency situation or necessary to ensure safety must be immediately notified to other ATS units concerned and terminated as soon as the circumstances cease to exist.
• Conditions for Amendment:
  • Modification to standards and procedures approved by the ATS authority affecting this agreement.
  • Commissioning of new communication facilities or Air Traffic Service Systems.
• Initiation Procedure:
  • The ATS-in-Charge shall initiate modification procedures in case of changes in ATS procedures, new installations, or modifications to existing installations.
• Dissemination:
  • Normal dissemination occurs at least $30$ days before the effective date.
  • If less than $30$ days remain, the ATS-in-Charge may agree via telephone, followed by an email signed by all parties, and circulate changes via local instruction. Formal signed copies follow as soon as practicable.

Airspace Jurisdiction and Temporary Delegations

• Standard Jurisdiction: As published in e-AIP India, except where airspace is delegated by separate agreement.
• Temporary Airspace Delegation: The airspace bounded by "RIBRO – $203108N \, 0810523E$ – $182442N \, 0800523E$ – SAPNU – $170916N \, 0820800E$ – RIBRO", above $FL255$, is delegated to Kolkata temporarily.
• Area of Responsibility:
  • Respective ACCs/FICs (Flight Information Centres) shall provide traffic information to the concerned lower ACC.
  • The concerned lower ACC shall provide applicable ATS as per classification of airspace below their vertical limits.
  • The concerned ACCs/FICs must be informed if a lower ACC is unable to provide services.

Separation Minima and Flight Level Allocation

• General Standards: Separation standards specified in e-AIP India and MATS Part $1$ are applicable unless specified in this LOA.
• Reduced Horizontal Separation (RHS): RHS on specified routes shall be applicable as per e-AIP India.
• Flight Level Allocation Scheme (FLAS): The FLAS as specified in e-AIP India shall be applicable.

Communication Systems and Failure Protocols

• Priority of Communication (in order):
  1. ATS Inter-facility Data Communication (AIDC).
  2. ATS direct speech circuits.
  3. Available telephone system.
  4. Any other means (Mobile Phone, Fax, etc.).
  5. AFTN.
• Mobile Phone Usage: When a mobile phone is used, a recorded landline must be used at one ATS unit (Mobile to Landline or vice versa). Mobile-to-mobile usage in extreme contingencies must be recorded in logbooks.
• Complete Communication Failure Protocols: If there is a complete failure of communication between Kolkata ACC and Nagpur ACC, the transferring unit shall:
  • Attempt to relay Flight Movement & Control Data through all available means.
  • Clear the aircraft to a "Clearance Limit" within its airspace.
  • Inform the aircraft of the absence of coordination.
  • Instruct the aircraft to establish contact with the accepting unit at least $10$ minutes before the Transfer of Control Point (TCP) to obtain entry clearance and report back.

Coordination General Principles

• Estimate Coordination: Both ACCs shall coordinate the estimate normally $30$ minutes prior to the coordination point.
• Minimum Lead Time: In cases where $30$ minutes is not possible, coordination must occur at least $10$ minutes prior to the coordination point.
• Revision of Estimate: Any revision shall be coordinated if it differs by $\pm 03 \, \text{minutes}$ or more.

Area Control Centre Coordination Table

• Note: * indicates acceptance basis. # indicates Speed restriction (MNT).

Near Boundary Operations

• Definition: Operations within $20 \, NM$ either side of the FIR/common boundary.
• Requirement: Controlling-ATSU must coordinate with the Adjacent-ATSU for aircraft flying near the boundary even if they are not penetrating the adjacent airspace. Control transfer is not involved.

Transfer of Control and AIDC

• Method: As per AIDC LOA. In case of AIDC outage, TCP shall be as per Annexure $1$.
• Approval: Transferring-ATSU must take approval from Accepting-ATSU for any level change within $10 \, minutes$ prior to the Change of Position (COP).
• AIDC Success: Voice coordination is not required if AIDC messaging is successful.
• Receiving Controller Rights: The receiving controller may initiate voice coordination if AIDC conditions are unacceptable. Voice coordination always supersedes AIDC coordination.
• Conditions Requiring Mandatory Voice Coordination:
  • Weather deviations.
  • Offset track.
  • VVIP flights.
  • NON RVSM flights.
  • Unusual occurrences (RCF / EMG / Unlawful Interference).
  • Application of Mach number technique.
  • After receiving a MAC message (to confirm flight status).
  • Any other circumstances warranting verbal communication.

Specific Coordination: Eastbound Traffic (Nagpur to Kolkata)

• Spacing: Converging traffic at ASOPO/JJB, OPONI, TEGIG, SADEV, DOVIR, ELBAB, MEPIP, and specific crossings ($Q19$ & $T1/W140$, $J67/Q16$ & $N877/L524/L301$) will be provided with at least $20 \, NM$ spacing under surveillance coverage.
• Nagpur ACC Responsibilities:
  • Pass estimate AKSIX to LBN and Kolkata for eastbound flights via $V15$.
  • Separate eastbound traffic converging near TEGIG via routes $L510$, $G450$, and $Q19$.
  • Provide $20 \, NM$ surveillance-based separation for eastbound traffic via $G450$, $T1$, $W140$, and $Q19$ over/near OPONI.
  • Provide $20 \, NM$ surveillance-based separation for eastbound traffic via $Q16$, $L510$, and $N895$ over SADEV.
  • Provide $20 \, NM$ surveillance-based separation for eastbound traffic via $L510$ and $L524$ over ELBAB.
  • Pass estimate TEGIG ($W108$), VEMPI ($W140$), and SADEV ($J67$) to Kolkata.
  • Obtain level clearance from Kolkata for eastbound landing at VERP (for descent below $FL210$) or other airfields within $20 \, NM$ of the boundary.
  • Obtain level clearance from Kolkata for eastbound flights via $L301$ and $N877$.
  • For $FL255$ and below: Pass estimate and obtain level clearance from Kolkata for routes $V73$ and $J4$.
  • Obtain level clearance from Kolkata/Varanasi ACC and effect level change before $20 \, NM$ of the boundary for northbound flights at ASOPO via $W99$-JJB-$W66$.

Specific Coordination: Westbound Traffic (Kolkata to Nagpur)

• Spacing: Converging traffic at ASOPO/JJB, BEDUX, GURVI, TEGIG, RUXAL, and crossing of $Q20$ & $N895$ will be provided with at least $20 \, NM$ spacing under surveillance coverage.
• Kolkata ACC Responsibilities:
  • Separate westbound traffic converging over TEGIG via routes $G450$ and $L510$.
  • Allocate levels to eastbound traffic converging over SADEV (via $L510$, $N895/G472$, and $J67$) and DOVIR (via $L524$) with respect to traffic on route $W136$.
  • Take level clearance from Nagpur for westbound flights departing VERP (for climb above $FL200$) or other airfields within $20 \, NM$ of the boundary.
  • Ensure $10 \, Min$ separation over MEPIP for westbound flights via $W136$, $J4$, and $V75$ at or below $FL255$.
  • Ensure $10 \, min$ separation over UXENA and crossing route $J67$ & $V73$ at or below $FL255$.
  • Obtain level clearance for westbound flights on $J67$ and $L301$.
  • Do not change levels on $L301$ and $N877$ after estimate is passed to Nagpur unless coordinated.
  • Responsible for separation of westbound traffic crossing via $J67$ and $N877$ over crossing point in Nagpur TMA.
  • Provide alternate route advice for aircraft flying below level published in AUP/UUP on route $L639$ as advised by Nagpur ACC.
  • Allocate levels to eastbound flights on routes $G590/W40/W68/Q15$ and $W139$ and separate traffic over KKJ.
  • Separate westbound traffic operating via $P628$, $A791$, $W139$, and $W99$ crossing over ASOPO and GOLOX.
  • Obtain level clearance from Nagpur for westbound flights via $W40/W68/G590/Q14$ and $W139$.

General Surveillance and Radar Procedures

• Spacing Threshold: $20 \, NM$ surveillance-based RHS is applicable only for flights operating at or above $FL280$.
• Requirements for 20 NM MNT Spacing:
  • One or both aircraft landing in India, Nepal, Bangladesh, or Bhutan; OR
  • Both aircraft from VABB oceanic airspace maintaining $20 \, NM$ separation before entering Nagpur (VANP) ACC.
• Trial Protocol: Kolkata ACC may initiate $20 \, NM$ longitudinal separation for participating westbound traffic between $0530$ to $0730 \, UTC$ during trial operations of S-ADS-B and CPDLC on routes $L301$ and $A791/L639$.
• Radar Handover: Transferring unit shall not terminate RADAR service; accepting unit should use "RADAR CONTACT" on first contact.
• Transfer of Identification: May be accomplished via AIDC, Voice, or other means per DOC $4444$.
• Procedural Reversion: In case of surveillance or VHF failure, units must revert to procedural separation and inform adjacent units immediately. Estimates will then be on an acceptance basis.

Pre-Calculated Levels (PCL)

• Kolkata Coordination Failure: In case of no coordination, $FL260$ shall be PCL on routes $W68/W40/G590$ and $W139$ in coordination with Kolkata.
• Nagpur Coordination Failure: In case of no coordination, $FL270$ shall be PCL on routes $W68/W40/G590/Q15$ and $W139$.

Frequency Table (Nagpur Sector)

Authorized Signatories

• For Kolkata ACC:
  • Paramesh Bandyopadhyay
  • Jt. G.M. (ATM-SQMS), Kolkata
  • Signature Date: $11/01/2024$
  • Phone: $033-25119966$
• For Nagpur ACC:
  • Laly Mary Francis
  • GM (ATM), Nagpur
  • Signature Date: $11/01/2024$
  • Phone: $0712-2807501$