Accessing the ’MAAR (Monitoring Agency for Asia Region)’ section of AEROTHAI website and clicking ’Monitoring Program’;
Using this Internet address: http://www.aerothai.co.th/maar/
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
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.
One automatic altitude-keeping device; and
One altitude-alerting device.
Is no longer RVSM compliant due to equipment failure; or;
Experiences loss of redundancy of altimetry systems; or
Encounters turbulence that affects the capability to maintain flight level.
The aircraft is being initially delivered to the State of Registry or Operator (see 1.10 for additional details and information); or
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
The aircraft is being utilized for mercy or humanitarian purposes; or
State aircraft (those aircraft used in military, custom and police services shall be deemed state aircraft).
Do not climb or descend at less than the normal rate for the aircraft; and
Do not level off at an intermediate level while passing through the RVSM stratum.
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 |
(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: ................................................................................................. |
Message | Phraseology |
---|---|
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 |
---|---|
600m | SIX HUN-dred METERS |
900m | NIN-er HUN-dred METERS |
1200m | WUN TOU-SAND TOO HUN-dred METERS |
1500m | WUN TOU-SAND FIFE HUN-dred METERS |
1800m | WUN TOU-SAND AIT HUN-dred METERS |
2100m | TOO TOU-SAND WUN HUN-dred METERS |
2400m | TOO TOU-SAND FOW-er HUN-dred METERS |
2700m | TOO TOU-SAND SEV-en HUN-dred METERS |
3000m | TREE TOU-SAND METERS |
3300m | TREE TOU-SAND TREE HUN-dred METERS |
3600m | TREE TOU-SAND SIX HUN-dred METERS |
3900m | TREE TOU-SAND NIN-er HUN-dred METERS |
4200m | FOW-er TOU-SAND TOO HUN-dred METERS |
4500m | FOW-er TOU-SAND FIFE HUN-dred METERS |
4800m | FOW-er TOU-SAND AIT HUN-dred METERS |
5100m | FIFE TOU-SAND WUN-HUN-dred METERS |
5400m | FIFE TOU-SAND FOW-er HUN-dred METERS |
5700m | FIFE TOU-SAND SEV-en HUN-dred METERS |
6000m | SIX TOU-SAND METERS |
6300m | SIX TOU-SAND TREE HUN-dred METERS |
6600m | SIX TOU-SAND SIX HUN-dred METERS |
6900m | SIX TOU-SAND NIN-er HUN-dred METERS |
7200m | SEV-en TOU-SAND TOO HUN-dred METERS |
7500m | SEV-en TOU-SAND FIFE HUN-dred METERS |
7800m | SEV-en TOU-SAND AIT HUN-dred METERS |
8100m | AIT TOU-SAND WUN HUN-dred METERS |
8400m | AIT TOU-SAND FOW-er HUN-dred METERS |
8900m | AIT TOU-SAND NIN-er HUN-dred METERS |
9200m | NIN-er TOU-SAND TOO HUN-dred METERS |
9500m | NIN-er TOU-SAND FIFE HUN-dred METERS |
9800m | NIN-er TOU-SAND AIT HUN-dred METERS |
10100m | WUN ZE-RO TOU-SAND WUN HUN-dred METERS |
10400m | WUN ZE-RO TOU-SAND FOW-er HUN-dred METERS |
10700m | WUN ZE-RO TOU-SAND SEV-en HUN-dred METERS |
11000m | WUN WUN TOU-SAND METERS |
11300m | WUN WUN TOU-SAND TREE HUN-dred METERS |
11600m | WUN WUN TOU-SAND SIX HUN-dred METERS |
11900m | WUN WUN TOU-SAND NIN-er HUN-dred METERS |
12200m | WUN TOO TO-SAND TOO HUN-dred METERS |
12500m | WUN TOO TO-SAND FIFE HUN-dred METERS |
13100m | WUN TREE TOU-SAND WUN HUN-dred METERS |
13700m | WUN TREE TOU-SAND SEV-en HUN-dred METERS |
14300m | WUN FOW-er TOU-SAND TREE HUN-dred METERS |
14900m | WUN FOW-er TOU-SAND NIN-er HUN-dred METERS |
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. |
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)
Attempt to establish radio communication on emergency frequency 121.5MHz and backup 5680kHz;
Inform supervisor, shift technical engineers and adjacent control positions or ATC units of the failure without delay;
Appraise such positions or units of the current traffic situation;
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;
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;
Take action of determining the cause of the radio communication failure.
Attempt to identify the aircraft concerned;
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;
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.
Correct any false or deceptive instructions or clearances which have been transmitted;
Advise all aircraft on the affected frequency(ies) that false and deceptive instructions or clearances are being transmitted;
Instruct all aircraft on the affected frequency(ies) to verify instructions and clearances before taking action to comply;
If practical, instruct aircraft to change to another frequency;
Advise all aircraft affected when the false and deceptive instructions or clearances are no longer being transmitted.
STCA indicator – PR (prediction)
STCA indicator -VI (violation)
Controller shall give STCA generated aircraft’s traffic information and instruct flight crew to maintain safe flight level immediate.
Essential traffic information can be given to an aircraft that is unable to maintain vertical separation new heading is instructed for lateral separation.
Essential traffic information can be given to an aircraft and speed control instruction for longitudinal separation.
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.
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.
If near other aircraft: TCAS CLIMB (or DESCENT);
Controller shall verify ;
If passed other aircraft: TRAFFIC CLEAR, RETURNING TO (FL, route);
Controller could give new instruction if necessary.