ENR 1.8  Regional supplementary procedures

1.   Policy and procedures of Reduced Vertical Separation Minimum (RVSM)

1.1  General
1.1.1 From 17 November 2011 at 0001 UTC, Metric RVSM has been implemented in the Ulaanbaatar FIR between 8900m (29100ft) and 12500m (41100ft) inclusive. The Airspace between 8900m (29100ft) and 12500m (41100ft) is defined as RVSM airspace. Mongolia RVSM airspace is exclusive RVSM airspace, aircraft that are not RVSM compliant may not operate into Mongolia RVSM airspace between 8900m (29100ft) and 12500m (41100ft) except for the following situations as detailed in paragraph 1.8.4.
1.1.2 Mongolia RVSM Flight Level Allocation Scheme (FLAS) is based on Metric Flight Level. Mongolia RVSM Flight Level Allocation Scheme (FLAS) is included in ENR 1.7.
1.1.3 To prevent undesirable ACAS TA/RA triggering in RVSM airspace, most civil aircraft use FEET as the primary altitude reference with a minimum selectable interval of 100 feet. ATC will issue the Flight Level clearance in meters.
1.1.4 Pilots shall use the Mongolia RVSM FLAS Diagram to determine the corresponding flight level in feet. The aircraft shall be flown using the flight level in FEET.
1.1.5 Pilots should be aware that due to the rounding differences, the metric readout of the onboard avionics will not necessarily correspond to the cleared Flight Level in meters, however the difference will never be more than 30 meters.
1.1.6 Aircraft equipped with metric and feet altimeters such as the IL-96, IL-62, Tu-214 or Tu-154 shall use the feet altimeter within RVSM flight level band. When these aircraft operating outside of RVSM flight level band, the aircraft can use metric altimeter or feet altimeter. Aircraft equipped with the altimetry system not capable of flying in feet in accordance with paragraph 1.1.4 should not flight plan in the RVSM airspace and shall comply with paragraph 1.8 as required.
1.1.7 Operator shall make available to the pilots the conversion table for meter and feet in accordance with Mongolia RVSM FLAS Diagram when operating in Mongolia RVSM airspace.
1.2   Airworthiness and Operational Approval and Monitoring
1.2.1  Operators must obtain airworthiness and operational approval from the State of Registry or State of the Operator, as appropriate, to conduct RVSM operations. Relevant requirements will be contained in RVSM airworthiness and flight standards policies of Civil Aviation Authority of Mongolia.
1.2.2 Operators are required to participate in the RVSM aircraft monitoring program. This is an essential element of the RVSM implementation program in that it confirms that the aircraft altitude-keeping performance standard is being met. Monitoring Agency for Asia Region (MAAR) will process the results of monitoring. For further information on RVSM monitoring, the MAAR website can be accessed by:
  1. Accessing the ’MAAR (Monitoring Agency for Asia Region)’ section of AEROTHAI website and clicking ’Monitoring Program’;

  2. Using this Internet address: http://www.aerothai.co.th/maar/

1.3  Airspace Safety Assessment and Monitoring
1.3.1 In order to conduct the airspace safety assessment and monitoring required by the ICAO Doc 9574, large height deviation report will be collected. Information contained in the collected reports will not be used for other purposes than the airspace safety assessment and safety monitoring.
1.3.2 Large height deviation occurrences will be collected from the entire Ulaanbaatar FIR.
1.3.3 Large height deviation occurrences will be collected between 8900m (29100ft) and 12500m (41100ft).
1.3.4 Action taken by Pilot
1.3.4.1 Pilot of aircraft operating in accordance with IFR, when deviating for any reason by 90m (300ft) or more from cleared flight level by ATC in RVSM airspace, shall report to the relevant ATS unit concerned via radio or if available, data link as soon as practicable, on the level deviation. After completion of the flight, the pilot shall also report to the operator the details of deviation.
1.3.5 Action taken by State and Aircraft Operators
1.3.5.1 When large height deviation is reported by a pilot as described in paragraph 1.3.4, the State of Registry of the operator shall submit the report, in principle, using the table in 1.13.1, as soon as possible to the RMA (Regional Monitoring Agency) and copy to the following address:

Air Traffic Services Division
Civil Aviation Authority of Mongolia
Buyant-Ukhaa International Airport
P.O.Box-35,
Ulaanbaatar 17120,
Mongolia

AFS:ZMUBZRZX

Email:safety-atc@mcaa.gov.mn

Tel:976-71281174

Fax:976-11-379525

1.4   ACAS II and Transponder Equipage
1.4.1 The ICAO Asia/Pacific RVSM Implementation Task Force recommends that those aircraft equipped with ACAS and operated in RVSM airspace shall be equipped with ACAS II. (TCAS II systems with Version 7.0 incorporated meet ICAO ACAS II standards).
1.4.2 Operators shall equip their aircraft with ACAS II and SSR transponder as required by AIP Mongolia.
1.5   In-flight Procedures within RVSM Airspace
1.5.1 Before entering RVSM airspace, the pilot should review the status of required equipment. The following equipment should be operating normally:
  1. Two primary altimetry systems;

    Note: Altimetry system requirement should be in accordance with paragraph 1.1.4 that aircraft shall be flown using the flight level in FEET.

  2. One automatic altitude-keeping device; and

  3. One altitude-alerting device.

1.5.2 In contingencies, the pilot must notify ATC whenever the aircraft:
  1. Is no longer RVSM compliant due to equipment failure; or;

  2. Experiences loss of redundancy of altimetry systems; or

  3. Encounters turbulence that affects the capability to maintain flight level.

1.5.3 Transition between FL’s
1.5.3.1 During cleared transition between levels, the aircraft should not overshoot or undershoot the assigned FL by more than 45m (150ft).
1.5.4 Pilot level call
1.5.4.1 Within RVSM airspace, pilots shall report reaching any assigned altitude.
1.5.5 Procedures for wake turbulence
1.5.5.1 Pilots encountering or anticipating wake turbulence in Mongolia RVSM airspace have the option of requesting FL change, or if capable, a vector, or a lateral offset.
1.5.6 Procedures for Strategic lateral offset (SLOP)
1.5.6.1  The flight crew may apply strategic lateral offset in remote continental airspace within the airspace of Mongolia when the aircraft is equipped with automatic offset tracking capability. The decision to apply a strategic lateral offset shall be the responsibility of the flight crew.
1.5.6.2  Within the airspace of Mongolia, the strategic lateral offset shall be established at a distance of 2 NM to the right of the centre line of the route relative to the direction of flight. Pilots are not required to inform ATC that a strategic lateral offset is being applied.
1.6   Transition areas
1.6.1 Transition areas and procedures for transition between Mongolia RVSM airspace and adjacent FIRs in Russian Federation are provided in 1.16.
1.7   Flight Planning Requirements
1.7.1 Unless special arrangement is made as detailed below, RVSM approval is required for operators and aircraft to operate within designated RVSM airspace. The operator must determine that the appropriate State authority has granted them RVSM operational approval and they will meet the RVSM requirements for the filed route of flight and any planned alternate routes. The letter "W" shall be inserted in Item 10 (Equipment) of the ICAO standard flight plan to indicate that both the aircraft and operator are RVSM approved. The request metric flight level within Mongolia RVSM airspace in Flight Plan shall be expressed as S followed by 4 figures (such as S1250, S1220 and S1190 represent 12500m, 12200m and 11900m respectively).
1.8   Procedures for Operation of Non-RVSM Approved Aircraft in RVSM Airspace
1.8.1 Flight priority
1.8.1.1 It should be noted that RVSM approved aircraft will be given priority for level allocation over non-RVSM approved aircraft.
1.8.2 Vertical separation applied
1.8.2.1 The vertical separation minimum between non-RVSM aircraft operating in the RVSM stratum and all other aircraft is 600m (2000ft).
1.8.3 Phraseology
1.8.3.1 Non-RVSM approved aircraft operating in RVSM airspace should use the phraseology contained in 1.14.
1.8.4 Special coordination procedures for cruise operation of Non-RVSM approved aircraft in RVSM airspace
1.8.4.1 Aircraft that are not RVSM compliant may not flight plan between 8900m (29100ft) and 12500m (41100ft), except for the following situations:
  1. The aircraft is being initially delivered to the State of Registry or Operator (see 1.10 for additional details and information); or

  2. The aircraft was RVSM approved but has experienced an equipment failure and is being flown to a maintenance facility for repairing in order to meet RVSM requirements and/or obtain approval; or

  3. The aircraft is being utilized for mercy or humanitarian purposes; or

  4. State aircraft (those aircraft used in military, custom and police services shall be deemed state aircraft).

1.8.4.2 Aircraft operators requesting that approval shall, if departing from an airport within Ulaanbaatar FIR, obtain approval from the Air Traffic Flow Management Division. Air Traffic Flow Management Division will provide notification of approval via AFTN, SITA or e-mail as appropriate; and
1.8.4.3 The assignment of cruising levels to non-RVSM approved aircraft listed in paragraph 1.8.4.1 (a) to (d) shall be subject to an ATC clearance. Aircraft operators shall include the ’STS/Category of operations (i.e. FERRY/HUMANITARIAN/MILITARY/CUSTOMS/POLICE/STATE) / NON-RVSM COMPLIANT’ in Field 18 of the ICAO Flight Plan;
1.8.4.4 This approval process is intended exclusively for the purposes indicated above and not as a means to circumvent the normal RVSM approval process.
1.9  Continuous Climb/Descent of Non-compliant Aircraft through RVSM Airspace
1.9.1 Non-RVSM compliant aircraft may be cleared to climb to and operate above 12500m (41100ft) or descend to and operate below 8900m (29100ft) provided that they:
  1. Do not climb or descend at less than the normal rate for the aircraft; and

  2. Do not level off at an intermediate level while passing through the RVSM stratum.

1.10  Delivery Flights for Aircraft that are RVSM Compliant on Delivery
1.10.1 An aircraft that is RVSM compliant on delivery may operate in RVSM airspace provided that the crew is trained on RVSM policies and procedures applicable in the airspace and the responsible State issues the operator a letter of authorization approving the operation. State notification to MAAR should be in the form of a letter, e-mail or fax documenting the one-time flight. The planned date of the flight, flight identification, registration number and aircraft type/series should be included.
1.11   Procedures for Suspension of RVSM
1.11.1 Air traffic services will consider suspending RVSM procedures within affected areas of Ulaanbaatar FIR when there are pilot reports of greater than moderate turbulence. Within areas where RVSM procedures are suspended, the vertical separation minimum between all aircraft will be 600m (2000ft).
1.12   Procedures for Air-Ground Communication Failure
1.12.1 The air-ground communication failure procedures specified in ICAO PANS-ATM Doc 4444 should be applied, in conjunction with AIP Mongolia.
1.13  Large Height Deviation Report

Name of FIR:

Please complete Section I or II as appropriate:

If there were no reports of large altitude deviation, only Section I should be finished.

If there were reports of large altitude deviation, please finish both Section I and Section II. If there were more than one report, each report should write a separate piece of Table B.

Section I:

There were no reports of large altitude deviation for the month of........................................

Section II:

There was/were ........................ report(s) of an altitude deviation of 90m (300ft) or more between 8900m and 12500m. Details of the altitude deviation can be found in table in 1.13.1.

(Please use a separate table for each report of large height deviation).

Section III:

When complete, please return to the following e-mail: safety-atc@mcaa.gov.mn

1.13.1  Report of an Altitude Deviation of 90m (300ft) or more between 8900m and 12500m

(Please use a separate table for each report of large height deviation).

This is the ................................... large height event reported this month.

Reporting agency: ...........................................................................................

Location of Deviation

ATS Route: ............................................... / .........................................................

• Fixes (Fixes between the locations of deviation): ...........................................................

Date of Occurrence (UTC: yyyy-mm-dd): .........................................................

Flight Identification and Type: ..............................................................

Flight Level Assigned (Record in the picture is also admitted): ...........................................

Observed/Reported Final Level Mode C/Pilot Report: (Record in the picture is also admitted):

.................................................................... / ...................................................................................

Cause of Deviation: ....................................................

Other traffic: ...............................................................

Crew comments (if any, when noted): ..................................................................

Remarks: ...................................................................................................................................................................................................... .............................................................................................................................................................................................................................

Duration at Flight Level: .................................................................................................

1.14  Phraseology related to RVSM operations for controller-pilot
MessagePhraseology
For a controller to ascertain the RVSM approval status of an aircraft: (call sign) CONFIRM RVSM APPROVED

For a pilot to report non-RVSM approval status:

i) On the initial call on any frequency within the RVSM airspace (controller shall provide a read-back with the same phrase); and

ii) In all requests for flight level changes pertaining to flight levels within the RVSM airspace; and

iii) In all read-backs to flight level clearances pertaining to flight levels within the RVSM airspace.

Additionally, except for State aircraft, pilots shall include this phrase to read back flight level clearances involving the vertical transit through 8900m or 12500m.

See examples that follow.

NEGATIVE RVSM

For a pilot to report RVSM approval status: AFFIRM RVSM
For a pilot of a non-RVSM approved State aircraft to report non-RVSM approval status, in response to the phrase (call sign) CONFIRM RVSM APPROVED: NEGATIVE RVSM, STATE AIRCRAFT

Denial of clearance into the RVSM airspace:

(call sign) UNABLE ISSUE CLEARANCE INTO RVSM AIRSPACE, MAINTAIN [or DESCEND TO, or CLIMB TO] FLIGHT LEVEL

For a pilot to report when severe turbulence affects the aircraft’s capability to maintain the height-keeping requirements for RVSM:

UNABLE RVSM DUE TURBULENCE

For a pilot to report that the aircraft’s equipment has degraded enroute below that required MASPS Minimum Aviation System Performance Standards for flight within the RVSM airspace:

(This phrase is to be used to convey both the initial indication of the non-MASPS compliance, and henceforth, on initial contact on all frequencies within the lateral limits of the RVSM airspace until such time as the problem ceases to exist, or the aircraft has exited the RVSM airspace.)

UNABLE RVSM DUE EQUIPMENT

For a pilot to report the ability to resume operations within the RVSM airspace after an equipment or weather-related contingency:

READY TO RESUME RVSM

For a controller to confirm that an aircraft has regained its RVSM approval status or to confirm that the pilot is ready to resume RVSM operations:

REPORT WHEN ABLE TO RESUMERVSM

Example 1:

A non-RVSM approved aircraft, maintaining 7800m (FL256), subsequently requests a climb to 9800m (FL321):

Pilot: (call sign) REQUEST 9800m (FL321), NEGATIVE RVSM

Controller: (call sign) CLIMB TO 9800m (FL321)

Pilot: (call sign) CLIMB TO 9800 m (FL321), NEGATIVE RVSM

Example 2:

A non-RVSM approved aircraft, maintaining 11000m (FL361), subsequently requests a climb to 11600m (FL381):

Pilot: (call sign) REQUEST 11600m (FL381), NEGATIVE RVSM

Controller: (call sign) CLIMB TO 11600m (FL381)

Pilot: (call sign) CLIMB TO 11600m (FL381), NEGATIVE RVSM

Example 3:

A non-RVSM approved civil aircraft maintaining 8400m (FL276), subsequently requests a climb to 9800m (FL321).

Pilot: (call sign) REQUEST 9800m (FL321), NEGATIVE RVSM

Controller: (call sign) UNABLE ISSUE CLEARANCE INTO RVSM AIRSPACE, MAINTAIN 8400m (FL276)

Example 4:

Air traffic controller instructs a RVSM approved civil aircraft to maintain 9200m, but he finds the aircraft is actually flying FL302. ATC will inform the Pilot to use the Mongolia RVSM Diagram to determine the corresponding flight level in feet.

Controller: (call sign) MAINTAIN 9200m

Pilot: (call sign) MAINTAIN 9200m

Controller: (call sign) MAINTAIN 9200m, CONVERT ALTITUDE WITH MONGOLIA RVSM FLIGHT LEVEL CHART.

The Pilot shall use the Mongolia RVSM Diagram to determine that, for 9200m, the corresponding flight level in feet is FL301, then flies the aircraft at FL301, and then:

Pilot: (call sign) MAINTAIN 9200m

Coordination between ATS units

Para

Message

Phraseology

1

To verbally supplement an automated estimate message exchange which does not automatically transfer Item 18 flight plan information:

NEGATIVE RVSM or NEGATIVE RVSMSTATE AIRCRAFT [as applicable]
2

To verbally supplement estimate messages of non-RVSM approved aircraft:

NEGATIVE RVSM or NEGATIVE RVSM STATE AIRCRAFT [as applicable]
3

To communicate the cause of a contingency relating to an aircraft that is unable to conduct RVSM operations due to severe turbulence or other severe weather-related phenomenon [or equipment failure, as applicable]:

UNABLE RVSM DUE TURBULENCE [or EQUIPMENT, as applicable]

Pronunciation of Flight Levels

Flight Level

English Pronunciation

600mSIX HUN-dred METERS
900mNIN-er HUN-dred METERS
1200mWUN TOU-SAND TOO HUN-dred METERS
1500mWUN TOU-SAND FIFE HUN-dred METERS
1800mWUN TOU-SAND AIT HUN-dred METERS
2100mTOO TOU-SAND WUN HUN-dred METERS
2400mTOO TOU-SAND FOW-er HUN-dred METERS
2700mTOO TOU-SAND SEV-en HUN-dred METERS
3000mTREE TOU-SAND METERS
3300mTREE TOU-SAND TREE HUN-dred METERS
3600mTREE TOU-SAND SIX HUN-dred METERS
3900mTREE TOU-SAND NIN-er HUN-dred METERS
4200mFOW-er TOU-SAND TOO HUN-dred METERS
4500mFOW-er TOU-SAND FIFE HUN-dred METERS
4800mFOW-er TOU-SAND AIT HUN-dred METERS
5100mFIFE TOU-SAND WUN-HUN-dred METERS
5400mFIFE TOU-SAND FOW-er HUN-dred METERS
5700mFIFE TOU-SAND SEV-en HUN-dred METERS
6000mSIX TOU-SAND METERS
6300mSIX TOU-SAND TREE HUN-dred METERS
6600mSIX TOU-SAND SIX HUN-dred METERS
6900mSIX TOU-SAND NIN-er HUN-dred METERS
7200mSEV-en TOU-SAND TOO HUN-dred METERS
7500mSEV-en TOU-SAND FIFE HUN-dred METERS
7800mSEV-en TOU-SAND AIT HUN-dred METERS
8100mAIT TOU-SAND WUN HUN-dred METERS
8400mAIT TOU-SAND FOW-er HUN-dred METERS
8900mAIT TOU-SAND NIN-er HUN-dred METERS
9200mNIN-er TOU-SAND TOO HUN-dred METERS
9500mNIN-er TOU-SAND FIFE HUN-dred METERS
9800mNIN-er TOU-SAND AIT HUN-dred METERS
10100mWUN ZE-RO TOU-SAND WUN HUN-dred METERS
10400mWUN ZE-RO TOU-SAND FOW-er HUN-dred METERS
10700mWUN ZE-RO TOU-SAND SEV-en HUN-dred METERS
11000mWUN WUN TOU-SAND METERS
11300mWUN WUN TOU-SAND TREE HUN-dred METERS
11600mWUN WUN TOU-SAND SIX HUN-dred METERS
11900mWUN WUN TOU-SAND NIN-er HUN-dred METERS
12200mWUN TOO TO-SAND TOO HUN-dred METERS
12500mWUN TOO TO-SAND FIFE HUN-dred METERS
13100mWUN TREE TOU-SAND WUN HUN-dred METERS
13700mWUN TREE TOU-SAND SEV-en HUN-dred METERS
14300mWUN FOW-er TOU-SAND TREE HUN-dred METERS
14900mWUN FOW-er TOU-SAND NIN-er HUN-dred METERS
1.15  Contingency actions for weather encounters and aircraft system failures

Initial Pilot Actions in Contingency Situations

Initial Pilot Actions when unable to maintain flight level (FL) or unsure of aircraft altitude-keeping capability:

Notify ATC and request assistance as detailed below.

Maintain cleared flight level, to the extent possible, while evaluating the situation.

Maintain watch for conflicting traffic both visually and by reference to TCAS.

Alert nearby aircraft by illuminating exterior lights.

If unable to contact ATC, broadcast position, flight level and intention on 121.5MHZ (or, as a backup 5680KHZ).

Severe Turbulence and/or Mountain Wave Activity (MWA) Induced Altitude Deviations of Approximately 60m (200ft)

Pilot will:

• When experiencing severe turbulence and/or MWA induced altitude deviations of approximately 60m (200ft) or greater, pilot will contact ATC and state ’Unable RVSM Due (state reason)’ (e.g., turbulence, mountain wave).

• If not issued by the controller, request vector clear of traffic at adjacent FL’s.

• If desired, request FL change.

• Report location and magnitude of turbulence or MWA to ATC.

Controller will:

• Assess the traffic situation to determine if the aircraft can be accommodated through the provision of lateral, longitudinal or increased vertical separation and, if so, apply the appropriate minimum.

• Advise pilot of conflicting traffic.

• Issue FL change, traffic permitting.

• Issue PIREP to other aircraft.

Mountain Wave Activity (MWA) Encounters - General

Note: MWA encounters do not necessarily result in altitude deviations on the order of 60m (200ft). The guidance below is intended to address less significant MWA encounters.

Pilot actions:

• Contact ATC and report experiencing MWA.

• Report location and magnitude of MWA to ATC.

• If so desired, pilot may request a FL change or deviation from the intended route.

Controller actions:

• Advise pilot of conflicting traffic at adjacent FL.

• If pilot requests, vector aircraft to avoid merging target with traffic at adjacent RVSM flight levels, traffic permitting.

• Issue FL change or re-route, traffic permitting.

• Issue PIREP to other aircraft.

Wake Turbulence Encounters

Pilot should:

• Contact ATC and request vector, FL change or, if capable, a lateral offset to right 2NM.

Controller should:

• Issue clearance of vector, FLchange or lateral offset to right 2NM, traffic permitting.

Unable RVSM Due Equipment (Failure of Automatic Altitude Control System, Altitude Alerter or All Primary Altimeters)

Pilot will:

• Contact ATC and state "Unable RVSM Due Equipment".

• Request clearance out of RVSM airspace unless operational situation dictates otherwise.

Controller will:

• Provide 600m (2000ft) vertical separation or appropriate horizontal separation.

• Clear aircraft out of RVSM airspace unless operational situation dictates otherwise.

One Primary Altimeter Remains Operational

Pilot will:

• Cross check stand-by altimeter.

• Notify ATC of operation with single primary altimeter.

• If unable to confirm primary altimeter accuracy, follow actions for failure of all primary altimeters.

Controller will:

• Acknowledge operation with single primary altimeter.

Note: Aircraft are able to operate in RVSM airspace at this situation except that pilot report unable RVSMdue equipment.

• Relay to other controllers or facilities who will subsequently handle the aircraft and any special handling requirement or being provided.

Transponder Failure

Pilot will:

• Contact ATCand request authority to continue to operate at cleared flight level.

• Comply with revised ATC clearance, if issued.

Controller will:

• Consider request to continue to operate at cleared flight level.

• Issue revised clearance, if necessary.

Contingency Procedures for Aircraft Requiring Rapid Descent

Pilot will:

• Notify ATCof aircraft location and request FL change as required.

• Upon declaring an emergency a pilot may exercise his right and change his assigned flight level. He shall notify ATC immediately and submit a report upon arrival at the destination.

• If unable to contact ATC and rapid descent required:

a) Deviation procedure for level change: 30° right and track out 20km (i.e. deviate right of airway centerline by 10km or 5NM), then turn left to track parallel the original route, then climb or descend to the new level, and then return to the original one (when appropriate).

Note: When return to the original route, it is possible to have conflict traffic on that route.

b) Establish communications with and alert nearby aircraft by broadcasting, at suitable intervals: flight identification, flight level, aircraft position and intention on the frequency in use, as well as on frequency 121.5MHZ (or, as a backup 5680KHZ).

c) Establish visual contact with conflicting traffic.

d) Turn on all aircraft exterior lights.

Controller will:

• Issue ATC clearance to change flight level.

1.16  Flight level transition procedures between different FLAS system

Transition procedure between Muren ACC and Barnaul ACC (NOPUS)


Transition procedure between Sainshand ACC and Chita ACC (SULOK)


Transition procedure between Muren ACC and Krasnoyarsk ACC (GINOM)


Transition procedure between Muren ACC and Krasnoyarsk ACC (DARNO)


Transition procedure between Muren ACC and Krasnoyarsk ACC (NIGOR)


Transition procedure between Ulaanbaatar ACC and Irkutsk ACC (SERNA)


Transition procedure between Ulaanbaatar ACC and Irkutsk ACC (LETBI)


Transition procedure between Ulaanbaatar ACC and Irkutsk ACC (AMUTA)


Transition procedure between Muren ACC and Irkutsk ACC (BAMUK)


2.  PROCEDURES RELATED TO EMERGENCY, COMMUNICATION FAILURE AND OTHER CONTINGENCY

2.1  SURVEILLANCE PROCEDURE
2.1.1 SURVEILLANCE FAILURE
2.1.1.1 In the event of complete failure of the ATC surveillance system, controller shall establish procedural control separation between the aircraft and immediately inform the supervisor and technical engineers.
2.1.1.2 Limit the number of aircrafts permitted to enter the area if necessary and continue with procedural control ensuring emergency separation.
2.1.2 SURVEILLANCE DISPLAY FAILURE
2.1.2.1 In the event of surveillance display stuck or malfunctioned the controller shall move to back up surveillance display and if necessary will provide procedural control.
2.1.2.2 If back up surveillance display is stuck or malfunctioned the controller shall provide procedural control separation between aircraft.
2.1.3 AIRCRAFT IDENTIFICATION LOST
2.1.3.1 If aircraft identification does not appear in the situation display for more than 24 seconds it is considered as identification lost.
2.1.3.2 When identification lost is believed to be not caused by ATC surveillance system, controller could request flight crew to check transponder by performing SQUAWK IDENT or to change squawk code.
2.1.3.3 Aircraft with identification lost shall have procedural separation between other concerning flights with same altitude and route. If necessary, limit the number of aircraft permitted to enter the area.
2.1.3.4 In the event of identification lost is not caused by aircraft equipment, supervisor shall inform adjacent ATC unit, sector and technical engineers without delay and every assistance shall be provided.
2.2  PROCEDURE DURING AIR-GROUND RADIOCOMMUNICATION FAILURE
2.2.1 AIR-GROUND RADIOCOMMUNICATION FAILURE
2.2.1.1  In the event of complete failure of the radio equipment used for ATC, the controller shall:
  1. Attempt to establish radio communication on emergency frequency 121.5MHz and backup 5680kHz;

  2. Inform supervisor, shift technical engineers and adjacent control positions or ATC units of the failure without delay;

  3. Appraise such positions or units of the current traffic situation;

  4. If practicable, request their assistance, in respect of aircraft which may establish communications with those positions or units, in establishing separation between and maintaining control of such aircraft;

  5. Instruct adjacent control positions or ATC units to hold or re-route all controlled flights outside the area of responsibility of the position or ATC unit that has experienced the failure until such time that the provision of normal services can be resumed;

  6. Take action of determining the cause of the radio communication failure.

2.2.2  ATC BLOCKED FREQUENCY
2.2.2.1 In the event that the control frequency is inadvertently blocked by an aircraft transmitter, the following additional steps should be taken:
  1. Attempt to identify the aircraft concerned;

  2. If the aircraft blocking the frequency is identified, attempts should be made to establish communication with that aircraft on the emergency frequency 121.5MHz, backup frequency 5680kHz, 123.45MHz, by SELCAL, through the aircraft operator’s company frequency if applicable, on any VHF frequency designated for air-to-air use by flight crews or any other communication means or, if the aircraft is on the ground, by direct contact;

  3. If communication is established with the aircraft concerned, shall instruct the flight crew to take immediate action to stop inadvertent transmissions on the affected control frequency and not to repeat the action.

2.2.3 UNAUTHORIZED USE OF ATC FREQUENCY
2.2.3.1 During false and deceptive transmissions on ATC frequencies which may impair the safety of aircraft and security the ATC unit concerned should:
  1. Correct any false or deceptive instructions or clearances which have been transmitted;

  2. Advise all aircraft on the affected frequency(ies) that false and deceptive instructions or clearances are being transmitted;

  3. Instruct all aircraft on the affected frequency(ies) to verify instructions and clearances before taking action to comply;

  4. If practical, instruct aircraft to change to another frequency;

  5. Advise all aircraft affected when the false and deceptive instructions or clearances are no longer being transmitted.

2.2.3.2 Flight crews shall challenge or verify with the ATC unit concerned any instruction or clearance issued to them which they suspect may be false or deceptive.
2.2.3.3 Shall notify appropriate authority when the transmission of false or deceptive instructions and clearances is detected.
2.3  EMERGENCY SEPARATION
2.3.1 If, during the surveillance system failure of ATC unit, it is not possible to ensure that the applicable horizontal separation can be maintained, emergency separation of half the applicable vertical separation minimum may be used, 150m between aircraft airspace where vertical separation minimum of 300m is applied, and 300m between aircraft in airspace where a 600m vertical separation minimum applied until procedural vertical separation is applied.
2.3.2 When emergency separation is applied the flight crews concerned shall be advised that emergency separation is being applied and informed of the actual minimum used and all flight crew shall be provided with essential traffic information.
2.4  SHORT-TERM CONFLICT ALERT (STCA) PROCEDURES
2.4.1 The objective of the short-term conflict alert (STCA) function in an ATC system monitors current and predicted three-dimensional positions of aircraft and if predicted to be reduced to less than the defined applicable separation minima within a specified time period, an acoustic and/or visual alert will be generated to and warning controller to prevent air collision.
2.4.2 Alert of STCA generates in the following two stages:
  1. STCA indicator – PR (prediction)

  2. STCA indicator -VI (violation)

2.4.3 In the event of STCA, confirmation of concerning aircraft’s flight level is made and following action taken to ensure separation:
  1. Controller shall give STCA generated aircraft’s traffic information and instruct flight crew to maintain safe flight level immediate.

  2. Essential traffic information can be given to an aircraft that is unable to maintain vertical separation new heading is instructed for lateral separation.

  3. Essential traffic information can be given to an aircraft and speed control instruction for longitudinal separation.

2.4.4 During STCA alert flight crew reports controller of following traffic collision alert system (TCAS) instruction to climb or descent, this regulation’s 2.4.3 does not apply.
2.4.5 The event of STCA generated ATC system registers and informs supervisor when local operation manual’s separation minimum is infringed and controller is required to complete and air traffic incident report.
2.5  MINIMUM SAFE ALTITUDE WARNING (MSAW) PROCEDURES
2.5.1 The minimum safe altitude warning (MSAW) function in an ATC system is to determine terrain and minimum safe altitude within responsibility area where an aircraft can operate safely, acoustic and/or visual alert will be generated to and warning controller for possible infringement of a minimum safe altitude.
2.5.2  MSAW indicator displays MS for an infringement of minimum safe altitude.
2.5.3 Controller shall inform flight crew which MSAW is being generated, check altitude, instruct flight crew for climb from terrain to safe altitude and shall complete air traffic incident report.
2.5.4 Terrain and elevation shall be taken into account and descent instruction shall be avoided to be given below minimum safe altitude during vectoring.
2.6  TRAFFIC COLLISION AVOIDANCE SYSTEM (TCAS)
2.6.1 Traffic collision avoidance system (TCAS) is independent non ground equipment, which automatic transponder determining aircraft’s current and future position and alerts flight crew possible threat of collision in mid-air with acoustic and visual alert for climb or descent or maintains current flight level.
2.6.2 TCAS generates in the following two stages:
  1. Traffic alert (TA) is warning given 45 seconds before possible collision avoidance instruction, flight crew identify conflicting traffic visually and shall inform ATC unit of generated TA.

  2. Resolution advisory (RA) is given 30 seconds before possible collision for avoidance instruction, which flight crew shall follow TCAS instruction by climbing, descending or maintaining flight level.

2.6.3 When a pilot reports an ACAS resolution advisory (RA) of climbing or descending or maintaining flight level, the controller shall not attempt to modify or cancel its action. The controller shall resume responsibility for providing separation for other traffic within the responsibility area.
2.6.4 During RA maneuver flight crew have the right to avoid controller instructions and reply on radio. Controller shall comply with TCAS procedure manual. Flight crew report RA to controller in following steps:
  1. If near other aircraft: TCAS CLIMB (or DESCENT);

  2. Controller shall verify ;

  3. If passed other aircraft: TRAFFIC CLEAR, RETURNING TO (FL, route);

  4. Controller could give new instruction if necessary.

2.7  CHANGE OF RADIOTELEPHONY CALL SIGN FOR AIRCRAFT
2.7.1 An ATC unit may instruct an aircraft to change its type of RTF call sign, in the interests of safety, when similarities between two or more aircraft RTF call signs are such that confusion is likely to occur.
2.7.2 Any such change to the type of call sign shall be temporary and shall be applicable only within the airspace(s) where the confusion is likely to occur.
2.7.3 To avoid confusion, the ATC unit should, if appropriate, identify the aircraft which will be instructed to change its call sign by referring to its position and/or level.
2.7.4 When an ATC unit changes the type of call sign of an aircraft, that unit shall ensure that the aircraft reverts to the call sign indicated by the flight plan when the aircraft is transferred to another ATC unit, except when the call sign change has been coordinated between the two ATC units concerned.
2.7.5 Phraseology to change the RFC call sign “CHANGE YOUR CALLSIGN TO” …. [UNTIL FURTHER ADVICE] is used. Phraseology to revert to the call sign indicated by the flight plan “REVERT TO FLIGHT PLAN CALL SIGN” is used.
2.8  AIRCRAFT TRANSPONDER FAILURE
2.8.1 When an aircraft experiencing transponder failure in en-route or flight after departure is operating or expected to operate in an area where the carriage of a functioning transponder is mandatory aircraft may then be required to return to the departure aerodrome or to land at the nearest suitable aerodrome acceptable to the operator concerned and to ATC.
2.8.2 In case of a transponder failure which is detected before departure from an aerodrome where it is not practicable to effect a repair, the aircraft concerned should be permitted to proceed, as directly as possible, to the nearest suitable aerodrome where repair can be made. When granting clearance to such aircraft, ATC should take into consideration the existing or anticipated traffic situation and may have to modify the time of departure, flight level or route of the intended flight. Subsequent adjustments may become necessary during the course of the flight.
2.8.3 Aircraft with failed transponder shall be informed to adjacent ATC unit and sectors.
2.9  EMERGENCY DESCENT
2.9.1 Emergency descent is process of rapid descent leaving flight level for appropriate safe altitude when aircraft experiences decompression, cabin pressure system failure, window break, window crack, door break, and other emergency procedure. During emergency descent vertical speed can be up to 2100-4500 metre per minute where flight crew have oxygen mask on which makes radio transmission noisy.
2.9.2  ATC unit shall immediately confirm flight crew’s emergency descent report and broadcast emergency message informing aircrafts affected by the descent instructing to leave route and stop transmitting on the radio.
2.9.3 Aircraft will descent according to its company’s manual of emergency descent procedure even when ATC unit does not confirm on flight crew’s emergency descent report. Location of the flight on emergency descent shall be identified by air traffic controller and traffic information should be informed to other flights.
2.9.4  ATC unit shall immediately broadcast emergency situation through appropriate radio communication equipment and if necessary by use of other means of communication available.
2.9.5 Aircrafts which are instructed to leave route or received radio silence shall comply and remain on the current frequency for further instruction.
2.9.6 Controller shall inform emergency descent to supervisor perform according to emergency descent procedure of emergency situation checklist.
2.9.7 If flight crew request for emergency landing, controller shall give aerodrome information such as QNH, minimum safe altitude, runway length and direction, available navigation aid frequency(ies) and weather information.
2.9.8 Controller shall inform Flight crew of operational local standby of ambulance and SAR as well as concerning ATC unit and sectors during emergency landing.