1 RVSM PROCEDURES IN THE SINGAPORE FIR
1.1 IMPLEMENTATION OF REVISED FLOS (FLIGHT LEVEL ORIENTATION SCHEME) AND FLAS (FLIGHT LEVEL ALLOCATION SCHEME) IN THE WESTERN PACIFIC/SOUTH CHINA SEA AREA
1.1.1 In order to minimise flight level transition requirements for flights entering and leaving the Western Pacific / South China Sea area, the following flight level arrangements will be implemented simultaneously and permanently:
a single alternate FLOS (i.e. ‘east odd flight levels, west even flight levels’) in compliance with the Table “RVSM-FEET” of Appendix 3 of ICAO Annex 2 and in accordance with the FLOS in surrounding areas;
special high capacity arrangements for six unidirectional parallel routes (L642, M771, N892, L625, N884 and M767) that involve managed use of odd and even flight levels in the same direction of flight; and
an associated FLAS agreed between affected ACCs to facilitate ATC ‘No-PDC’ operations.
1.1.2 To harmonise with RVSM operations within Jakarta FIR, RVSM operations within the Singapore FIR shall be conducted between FL290 and FL410 (inclusive) in the following areas:
| ATS Routes | Flight Level Assignment |
|---|
| A464 (S) Southbound | FL290, FL310, FL330, FL350, FL370, FL390, FL410 |
| A576 (S) Southbound | FL290, FL310, FL330, FL350, FL370, FL390, FL410 |
| B470 | FL290, FL300, FL310, FL320, FL330, FL340, FL350, FL360, FL370, FL380, FL390, FL400 and FL410 except for flights beyond Jakarta where only odd levels shall be assigned. |
| B469 (S) Southbound | FL290, FL310, FL330, FL350, FL370, FL390 and FL410 |
| N875/G464 (S) Southbound | FL290, FL330, FL370 and FL410 |
| W36 (S) Southbound | FL290, FL330, FL370 and FL410 |
| L644 (S) Southbound | FL290, FL330, FL370 and FL410 |
| R469 (W) Westbound | FL300, FL320, FL340, FL360, FL380 and FL400 |
| W22 (W) Westbound | FL300, FL320, FL340, FL360, FL380 and FL400 |
1.1.3 Non RVSM-approved aircraft shall fly below RVSM airspace unless prior approval has been obtained from the ACC concerned for such aircraft to operate in RVSM airspace. In the assignment of cruising level in RVSM airspace, RVSM-approved aircraft shall be given priority over non RVSM-approved aircraft.
1.1.4 When an RVSM-approved aircraft reports that it is no longer RVSM-compliant before the transfer of control point, the transferring ACC shall immediately notify the receiving ACC of this fact and provide conventional vertical separation of 2,000ft between this aircraft and the other aircraft.
1.2 AIRWORTHINESS 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. On behalf of the Pacific ATS providers, the FAA is maintaining a website containing documents and policy for RVSM approval. The Internet address is http://www.faa.gov/ats/ato/rvsm1.htm. In the “RVSM Documentation” section, under “Documents Applicable to All RVSM Approvals”, the “Aircraft /Operator Approval Events Outlines” for US and Non-US Operators provides an outline of approval process tasks with references to related documents.
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. The Asia Pacific Approvals Registry and Monitoring Organisation (APARMO) will process the results of monitoring. For further information on RVSM monitoring, the APARMO web site can be accessed by:
- accessing the “RVSM Documentation” section of the FAA RVSM website and clicking on the link to the APARMO website, or
- using this Internet address: http://www.tc.faa.gov/act500/rvsm/aparmo_intro.html
1.2.3 Monitoring accomplished for other regions can be used to fulfill the monitoring requirements for the Asia/Pacific region. The APARMO will coordinate with other monitoring agencies to access this information. For monitoring services in the Asia/Pacific region, operators should contact the APARMO monitoring contractor as follows:
Phone: +1 202 8632175
Fax: +1 202 862 2398
Email: monitor@cssiinc.com
1.3 ACAS II AND TRANSPONDER EQUIPAGE
1.3.1 The ICAO Asia/Pacific RVSM Implementation Task Force recommends that those aircraft equipped with ACAS and operated in RVSM airspace be equipped with ACAS II. (TCAS II systems with Version 7.0 incorporated meet ICAO ACAS II standards).
1.3.2 Operators must take action to inform themselves of ACAS II equipage requirements and plan for compliance. ICAO and individual States have established policies requiring ACAS II equipage and schedules for compliance. In addition, the APANPIRG has endorsed early ACAS II equipage in the region.
1.3.3 ICAO Annex 6, Part II, states that, starting 1 January 2000, International General Aviation (IGA) airplanes shall be equipped with a pressure altitude reporting transponder certified by the appropriate State authority as meeting the provisions of ICAO Annex 10.
1.4 IN-FLIGHT PROCEDURES WITHIN RVSM AIRSPACE
1.4.1 Before entering RVSM airspace, the pilot should review the status of required equipment. The following equipment should be operating normally:
- two primary altimetry systems;
- one automatic altitude-keeping device; and
- one altitude-alerting device.
1.4.2 The pilot must notify ATC whenever the aircraft:
- 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.
See pages ENR 1.8-8 to ENR 1.8-11 or Appendix 5 of FAA IG 91-RVSM for pilot and controller actions in contingency scenarios.
1.4.3 During cleared transition between levels, the aircraft should not overshoot or undershoot the assigned FL by more than 150ft (45m).
1.4.4 Except in an ADS or radar environment, pilots shall report reaching any altitude assigned within RVSM airspace.
1.4.5 Paragraphs 1.5, 1.6, 1.7 and 1.8 below contain procedures for in-flight contingencies that have been updated for RVSM operations. The contingency procedures in paragraphs 1.5 and 1.6 and the off-set procedures in paragraph 1.8 should be applied in Oceanic operations. The weather deviation procedures in paragraph 1.7 may be applied in all airspace in the region.
1.5 SPECIAL PROCEDURES FOR IN-FLIGHT CONTINGENCIES IN OCEANIC AIRSPACE IN THE SINGAPORE FIR
1.5.1 The following general procedures apply to both subsonic and supersonic aircraft and are intended as guidance only. Although all possible contingencies cannot be covered, they provide for cases of inability to maintain assigned level due to:
- weather;
- aircraft performance;
- pressurisation failure; and
- problems associated with high-level supersonic flight.
1.5.2 The procedures are applicable primarily when rapid descent and/or turn-back or diversion to an alternate airport is required. The pilot’s judgement shall determine the sequence of actions to be taken, taking into account specific circumstances.
1.5.3 If an aircraft is unable to continue flight in accordance with its air traffic control clearance, a revised clearance shall, whenever possible, be obtained prior to initiating any action, using a distress or urgency signal as appropriate.
1.5.4 If prior clearance cannot be obtained, an ATC clearance shall be obtained at the earliest possible time and, until a revised clearance is received, the pilot shall:
- if possible, deviate away from an organised track or route system;
- establish communications with and alert nearby aircraft by broadcasting, at suitable intervals: flight identification, flight level, aircraft position (including the ATS route designator or the track code) and intentions on the frequency in use, as well as on frequency 121.5MHz (or, as a back-up, the VHF inter-pilot air-to-air frequency 123.45MHz);
- watch for conflicting traffic both visually and by reference to ACAS (if equipped); and
- turn on all aircraft exterior lights (commensurate with appropriate operating limitations).
1.6 IN-FLIGHT CONTINGENCY PROCEDURES FOR SUBSONIC AIRCRAFT REQUIRING RAPID DESCENT, TURN-BACK OR DIVERSION IN OCEANIC AIRSPACE IN THE SINGAPORE FIR
Initial action
1.6.1 If unable to comply with the provisions of 1.5.3 to obtain a revised ATC clearance, the aircraft should leave its assigned route or track by turning 45 degrees right or left whenever this is possible. The direction of the turn should be determined by the position of the aircraft relative to any organised route or track system (for example, whether the aircraft is outside, at the edge of, or within the system). Other factors to consider are terrain clearance and the levels allocated to adjacent routes or tracks.
Subsequent action
1.6.2 An aircraft able to maintain its assigned level should acquire and maintain in either direction a track laterally separated by 15NM from its assigned route or track and once established on the offset track, climb or descend 500ft (150m).
1.6.3 An aircraft NOT able to maintain its assigned level should, whenever possible, minimise its rate of descent while turning to acquire and maintain in either direction a track laterally separated by 15NM from its assigned route or track. For subsequent level flight, a level should be selected which differs by 500ft (150m) from those normally used.
1.6.4 Before commencing a diversion across the flow of adjacent traffic, the aircraft should, while maintaining the 15NM offset, expedite climb above or descend below levels where the majority of aircraft operate (e.g. to a level above FL400 or below FL290) and then maintain a level which differs by 500ft (150m) from those normally used. However, if the pilot is unable or unwilling to carry out a major climb or descent, the aircraft should be flown at a level 500ft above or below levels normally used until a new ATC clearance is obtained.
1.6.5 If these contingency procedures are employed by a twin-engine aircraft as a result of an engine shutdown or a failure of an ETOPS critical system, the pilot should advise ATC as soon as practicable of the situation, reminding ATC of the type of aircraft involved and requesting expeditious handling.
1.7 WEATHER DEVIATION PROCEDURES IN THE SINGAPORE FIR
General procedures
1.7.1 The following procedures are intended to provide guidance. All possible circumstances cannot be covered. The pilot’s judgement shall ultimately determine the sequence of actions taken and ATC shall render all possible assistance.
1.7.2 If the aircraft is required to deviate from track to avoid weather and prior clearance cannot be obtained, an air traffic control clearance shall be obtained at the earliest possible time. In the meantime, the aircraft shall follow the procedures detailed in paragraph 1.7.9.
1.7.3 The pilot shall advise ATC when weather deviation is no longer required, or when a weather deviation has been completed and the aircraft has returned to the centreline of its cleared route.
1.7.4 When the pilot initiates communications with ATC, rapid response may be obtained by stating “WEATHER DEVIATION REQUIRED” to indicate that priority is desired on the frequency and for ATC response.
1.7.5 The pilot still retains the option of initiating the communications using the urgency call “PAN PAN” to alert all listening parties to a special handling condition, which may receive ATC priority for issuance of a clearance or assistance.
1.7.6 When controller-pilot communications are established, the pilot shall notify ATC and request clearance to deviate from track, advising, when possible, the extent of the deviation expected. ATC will take one of the following actions:
if there is no conflicting traffic in the horizontal dimension, ATC will issue clearance to deviate from track; or
if there is conflicting traffic in the horizontal dimension, ATC will separate aircraft by establishing vertical separation or, if unable to establish vertical separation, ATC shall:
- advise the pilot unable to issue clearance for requested deviation
- advise pilot of conflicting traffic
- request pilot’s intentions
SAMPLE PHRASEOLOGY:
“Unable (requested deviation), traffic is (callsign, position, altitude, direction), advise intentions.”
1.7.7 The pilot will take the following actions:
- advise ATC of intentions by the most expeditious means available,
- comply with air traffic control clearance issued, or
- execute the procedures detailed in 1.7.9 below, (ATC will issue essential traffic information to all affected aircraft.)
- if necessary, establish voice communications with ATC to expedite dialogue on the situation.
Actions to be taken if a revised air traffic control clearance cannot be obtained
1.7.8 The pilot shall take the actions listed below under the provision that the pilot may deviate from rules of the air (e.g. the requirement to operate on route or track centreline unless otherwise directed by ATC), when it is absolutely necessary in the interests of safety to do so.
1.7.9 If a revised air traffic control clearance cannot be obtained and deviation from track is required to avoid weather, the pilot shall take the following actions:
if possible, deviate away from an organised track or route system;
establish communications with and alert nearby aircraft by broadcasting, at suitable intervals: flight identification, flight level, aircraft position (including the ATS route designator or the track code) and intentions (including the magnitude of the deviation expected) on the frequency in use, as well as on frequency 121.5MHz (or, as a back-up, the VHF inter-pilot air-to-air frequency 123.45MHz).
watch for conflicting traffic both visually and by reference to ACAS (if equipped);
turn on all aircraft exterior lights (commensurate with appropriate operating limitations);
for deviations of less than 10NM, aircraft should remain at the level assigned by ATC;
for deviations of greater than 10NM, when the aircraft is approximately 10NM from track, initiate a level change based on the following criteria:
| Route centreline track | Deviations greater than 10NM | Level change |
EAST
000-179 magnetic | LEFT
RIGHT | DESCEND 300ft
CLIMB 300ft |
WEST
180-359 magnetic | LEFT
RIGHT | CLIMB 300ft
DESCEND 300ft |
Note: Items b) and c) call for the pilot to broadcast aircraft position and pilot’s intentions, identify conflicting traffic and communicate air-to-air with nearby aircraft.
If the pilot determines that there is another aircraft at or near the same FL with which his aircraft might conflict, then the pilot is expected to adjust the path of the aircraft, as necessary, to avoid conflict.
if contact was not established prior to deviating, continue to attempt to contact ATC to obtain a clearance. If contact was established, continue to keep ATC advised of intentions and obtain essential traffic information.
when returning to track, be at its assigned flight level when the aircraft is within approximately 10NM of centreline.
1.8 PROCEDURES TO MITIGATE WAKE TURBULENCE ENCOUNTERS AND DISTRACTING AIRCRAFT SYSTEM ALERTS IN THE OCEANIC AIRSPACE OF SINGAPORE FIR
1.8.1 The following special procedures are applicable to mitigate wake turbulence or distracting aircraft system alerts [e.g. ACAS, Ground Proximity Warning System (GPWS)] in Asia and Pacific airspace where RVSM is applied:
NOTE: In the contingency circumstances below, ATC will not issue clearances for lateral offsets and will not normally respond to actions taken by the pilots.
1.8.2 An aircraft that encounters wake vortex turbulence or experiences distracting aircraft system alerts shall notify ATC and request a flight level, track or speed change to avoid the condition. However, in situations where such a change is not possible or practicable, the pilot may initiate the following temporary lateral offset procedure with the intention of returning to centreline as soon as practicable:
the pilot should establish contact with other aircraft, if possible, on the appropriate VHF inter-pilot air-to-air frequency 123.45MHz, and
one (or both) aircraft may initiate lateral offset(s) not to exceed 2NM from the assigned track, provided that:
as soon as practicable to do so, the offsetting aircraft notify ATC that temporary lateral offset action has been taken and specify the reason for doing so (ATC will not normally respond); and
the offsetting aircraft notify ATC when re-established on assigned route(s) or track(s) (ATC will not normally respond).
1.9 FLIGHT PLANNING REQUIREMENTS
1.9.1 Unless special arrangement is made as detailed below, RVSM approval is required for aircraft to operate within designated RVSM airspace. The operator must determine that the appropriate State authority has approved the aircraft and 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 the aircraft is RVSM approved aircraft.
1.10 PROCEDURES FOR OPERATION OF NON-RVSM COMPLIANT AIRCRAFT IN RVSM AIRSPACE
1.10.1 It should be noted that RVSM approved aircraft will be given priority for level allocation over non- RVSM approved aircraft.
1.10.2 The vertical separation minimum between non-RVSM aircraft operating in the RVSM stratum and all other aircraft is 2,000ft.
1.10.3 Non-RVSM compliant aircraft operating in RVSM airspace should use the phraseology as contained in page ENR 1.8-12.
1.10.4 Non-RVSM compliant aircraft may be cleared to climb to and operate above FL290 or descend to and operate below FL410 provided that they:
- 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.
1.10.5 Non-RVSM compliant aircraft may not flight plan between FL290 and FL410 inclusive within RVSM airspace. After special coordination as detailed in paragraph 1.10.6 below, the following non-RVSM aircraft may flight plan at RVSM flight levels in the RVSM stratum:
- is being initially delivered to the State of Registry or Operator (see paragraph 1.11 for additional details and information); or
- was formally RVSM approved but has experienced an equipment failure and is being flown to a maintenance facility for repair in order to meet RVSM requirements and/or obtain approval; or
- is transporting a spare engine mounted under the wing; or
- 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).
1.10.6 The assignment of cruising level to non-RVSM compliant aircraft listed in paragraph 1.10.5 (a) to (e) shall be subject to an ATC clearance. Aircraft operators shall include “STS/CATEGORY (FERRY/ HUMANITARIAN/ MILITARY/ CUSTOMS/POLICE)/NON-RVSM COMPLIANT” in field 18 of the ICAO flight plan.
1.10.7 Contact details for approval request are as follows:
Watch Manager, Singapore Air Traffic Control Centre:
TEL: (65) 65412668
AFS: WSJCZRZX
FAX: (65) 65457526
1.10.8 This approval process is intended exclusively for the purposes indicated above and not as a means to circumvent the normal RVSM approval process.
1.11 DELIVERY FLIGHTS FOR AIRCRAFT THAT ARE RVSM COMPLIANT ON DELIVERY
1.11.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 authorisation approving the operation. State notification to the APARMO should be in the form of a letter, e-mail or facsimile documenting the one-time flight. The planned date of the flight, flight identification, registration number and aircraft type/series should be included.
1.12 PROCEDURES FOR SUSPENSION OF RVSM
1.12.1 Air traffic services will consider suspending RVSM procedures within affected areas of the Singapore 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 2,000ft.
1.13 GUIDANCE FOR PILOTS AND CONTROLLERS FOR ACTIONS IN THE EVENT OF AIRCRAFT SYSTEM MALFUNCTION OR TURBULENCE GREATER THAN MODERATE
1.13.1 See pages ENR 1.8-8 to ENR 1.8-11 for guidance in these circumstances.
1.14 PROCEDURES FOR AIR-GROUND COMMUNICATION FAILURE
1.14.1 The air-ground communication failure procedures specified in page ENR 1.6-3 in conjunction with ICAO PANS-ATM DOC 4444 should be applied.
The following paragraphs summarize pilot actions to mitigate the potential for conflict with other aircraft in certain contingency situations. They should be reviewed in conjunction with the expanded contingency scenarios detailed below which contain additional technical and operational details.
* Scenario 1 : The pilot is
unsure of the vertical position of the aircraft due to the loss or degradation of all primary altimetry systems, or
unsure of the capability to maintain cleared flight level (CFL) due to turbulence or loss of all automatic altitude control systems.
| The pilot should: | ATC can be expected to: |
|---|
Maintain CFL while evaluating the situation; | |
Watch for conflicting traffic both visually and by reference to ACAS, if equipped; | |
If considered necessary, alert nearby aircraft by a) Making maximum use of exterior lights; b) Broadcasting position, FL, and intentions on 121.5MHz (as a back-up, the VHF inter-pilot air-to-air frequency 123.45MHz may be used). | |
Notify ATC of the situation and intented course of action. Possible courses of action include: | Obtain the pilot’s intentions and pass essential traffic information. |
a) Maintaining the CFL and route provided that ATC can provide lateral, longitudinal or conventional vertical separation. | If the pilot intends to continue in RVSM airspace, assess traffic situation to determine if the aircraft can be accommodated through the provision of lateral, longitudinal, or conventional vertical separation, and if so, apply the appropriate minimum. |
b) Requesting ATC clearance to climb above or descend below RVSM airspace if the aircraft cannot maintain CFL and ATC cannot establish adequate separation from other aircraft. | If the pilot requests clearance to exit RVSM airspace, accommodate expeditiously, if possible. |
c) Executing the contingency manoeuvre shown in paragraphs 1.5 and 1.6 to offset from the assigned track and FL, if ATC clearance cannot be obtained and the aircraft cannot maintain CFL. | If adequate separation cannot be established and it is not possible to comply with the pilot’s request for clearance to exit RVSM airspace, advise the pilot of essential traffic information, notify other aircraft in the vicinity and continue to monitor the situation. |
| Notify adjoining ATC facilities/sectors of the situation. |
Scenario 2: There is a failure or loss of accuracy of one primary altimetry system (e.g. greater than 200ft difference between primary altimeters).
| The pilot should: |
|---|
| Cross check standby altimeter, confirm the accuracy of a primary altimeter system and notify ATC of the loss of redundancy. If unable to confirm primary altimeter system accuracy, follow pilot actions listed in the preceding scenario. |
|
|---|
|
|---|
| EXPANDED EQUIPMENT FAILURE AND TURBULENCE ENCOUNTER SCENARIOS |
|---|
Operators may consider this material for use in training programs.
* Scenario 1: All automatic altitude control systems failed (e.g. Automatic Altitude Hold).
| The pilot should: | ATC can be expected to: |
|---|
Initially,
Maintain CFL Evaluate the aircraft’s capability to maintain altitude through manual control Subsequently,
Watch for conflicting traffic both visually and by reference to ACAS, if equipped. | |
If considered necessary, alert nearby aircraft by: a) Making maximum use of exterior lights; b) Broadcasting position, FL, and intentions on 121.5MHz (as a back-up, the VHF inter-pilot air-to-air frequency 123.45MHz may be used). | |
Notify ATC of the failure and intended course of action. Possible courses of action include: | |
a) Maintaining the CFL and route, provided that the aircraft can maintain level. | If the pilot intends to continue in RVSM airspace, assess traffic situation to determine if the aircraft can be accommodated through the provision of lateral, longitudinal, or conventional vertical separation, and if so, apply the appropriate minimum. |
b) Requesting ATC clearance to climb above or descend below RVSM airspace if the aircraft cannot maintain CFL and ATC cannot establish lateral, longitudinal or conventional vertical separation. | If the pilot requests clearance to exit RVSM airspace, accommodate expeditiously, if possible. |
c) Executing the contingency manoeuvre shown in paragraphs 1.5 and 1.6 to offset from the assigned track and FL, if ATC clearance cannot be obtained and the aircraft cannot maintain CFL. | If adequate separation cannot be established and it is not possible to comply with the pilot’s request for clearance to exit RVSM airspace, advise the pilot of essential traffic information, notify other aircraft in the vicinity and continue to monitor the situation. |
| Notify adjoining ATC facilities/sectors of the situation |
* Scenario 2: Loss of redundancy in primary altimetry systems
| The pilot should: | ATC can be expected to: |
|---|
If the remaining altimetry system is functioning normally, couple that system to the automatic altitude control system, notify ATC of the loss of redundancy and maintain vigilance of altitude keeping. | Acknowledge the situation and continue to monitor progress. |
Scenario 3: All primary altimetry systems are considered unreliable or failed.
| The pilot should: | ATC can be expected to: |
|---|
Maintain CFL by reference to the standby altimeter (if the aircraft is so equipped). | |
Alert nearby aircraft by: a) Making maximum use of exterior lights; b) Broadcasting position, FL, and intentions on 121.5MHz (as a back-up, the VHF inter-pilot air-to-air frequency 123.45MHz may be used). | |
Consider declaring an emergency. Notify ATC of the failure and intended course of action. | Obtain pilot’s intentions and pass essential traffic information. |
Possible courses of action include: | |
a) Maintaining CFL and route provided that ATC can provide lateral, longitudinal or conventional vertical separation. | If the pilot intends to continue in RVSM airspace, assess traffic situation to determine if the aircraft can be accommodated through the provision of lateral, longitudinal, or conventional vertical separation, and if so, apply the appropriate minimum. |
b) Requesting ATC clearance to climb above or descend below RVSM airspace if ATC cannot establish adequate separation from other aircraft. | If the pilot requests clearance to exit RVSM airspace, accommodate expeditiously, if possible. |
c) Executing the contingency manoeuvre shown in paragraphs 1.5 and 1.6 to offset from the assigned track and FL, if ATC clearance cannot be obtained. | If adequate separation cannot be established and it is not possible to comply with the pilot’s request for clearance to exit RVSM airspace, advise the pilot of essential traffic information, notify other aircraft in the vicinity and continue to monitor the situation. Notify adjoining ATC facilities/sectors of the situation. |
Scenario 4: The primary altimeters diverge by more than 200ft (60m).
| The pilot should: |
|---|
Attempt to determine the defective system through established trouble-shooting procedures and/or comparing the primary altimeter displace to the standby altimeter (as corrected by the correction cards, if required). |
If the defective system can be determined, couple the functioning altimeter system to the altitude-keeping device. |
If the defective system cannot be determined, follow the guidance in Scenario 3 for failure or unreliable altimeter indications of all primary altimeters. |
Scenario 5: Turbulence (greater than moderate) which the pilot believes will impact the aircraft’s capability to maintain flight level.
| The pilot should: | ATC can be expected to: |
|---|
Watch for conflicting traffic both visually and by reference to ACAS, if equipped. | |
If considered necessary, alert nearby aircraft by: a) Making maximum use of exterior lights; b) Broadcasting position, FL, and intentions on 121.5MHz (as a back-up, the VHF inter-pilot air-to-air frequency 123.45MHz may be used). | |
Notify ATC of intended course of action as soon as possible. | |
Possible courses of action include: | |
a) Maintaining CFL and route, provided ATC can provide lateral, longitudinal or conventional vertical separation. | Assess traffic situation to determine if the aircraft can be accommodated through the provision of lateral, longitudinal, or conventional vertical separation, and if so, apply the appropriate minimum. |
b) Requesting flight level change, if necessary | If unable to provide adequate separation, advise the pilot of essential traffic information and request pilot’s intentions. |
c) Executing the contingency manoeuvre shown in paragraphs 1.5 and 1.6 to offset from the assigned track and FL, if ATC clearance cannot be obtained and the aircraft cannot maintain CFL. | Notify other aircraft in the vicinity and monitor the situation. |
| Notify adjoining ATC facilities/sectors of the situation. |
|
|---|
|
|---|
| CONTROLLER / PILOT PHRASEOLOGY |
|---|
| Phrases | Purpose |
|---|
(callsign) CONFIRM RVSM APPROVED | Used by the controller to ascertain the RVSM approval status of an aircraft. |
NEGATIVE RVSM* | Used by the pilot to report non-RVSM approval status: a) On the initial call on any frequency within the RVSM airspace (controllers shall provide a readback with this same phrase); and b) In all requests for flight level changes pertaining to flight levels within the RVSM airspace; and c) In all readback of flight level clearances pertaining to flight levels within the RVSM airspace. Additionally, except for State aircraft, pilots shall include this RTF phrase to read back flight level clearances involving the vertical transit through FL290 or FL410. |
AFFIRM RVSM* | Used by the pilot to report RVSM approval status. |
NEGATIVE RVSM STATE AIRCRAFT* | Used by the pilot of a non-RVSM approved State aircraft to report non-RVSM approval status in response to the RTF phrase (callsign) CONFIRM RVSM APPROVED. |
(callsign) UNABLE CLEARANCE INTO RVSM AIRSPACE, MAINTAIN [or DESCEND TO, or CLIMB TO] FLIGHT LEVEL (number) | Used to deny ATC clearance into the RVSM airspace. |
UNABLE RVSM DUE TURBULENCE* | Used by the pilot to report when severe turbulence affects the aircraft’s capability to maintain the height- keeping requirements for RVSM. |
UNABLE RVSM DUE EQUIPMENT* | Used by the pilot to report that the aircraft’s equipment has degraded below the MASPS (Minimum Aircraft Systems Performance Specification) required for flight within the RVSM airspace. |
READY TO RESUME RVSM* | Used by the pilot to report the ability to resume operations within the RVSM airspace after an equipment or weather-related contingency. |
REPORT ABLE TO RESUME RVSM | Used by the controller to confirm that an aircraft has regained its RVSM approval status or to confirm that the pilot is ready to resume RVSM operations. |
* indicates a pilot transmission
2 MACH NUMBER TECHNIQUE (MNT) AND AREA NAVIGATION (RNAV)
2.1 INTRODUCTION
2.1.1 RNAV is a method which permits aircraft navigation along any desired flight path within the coverage of the associated navigation aids, or within the limits of the capability of self-contained aids, or a combination of these methods. RNAV equipment is considered to be that equipment which operates by automatically determining aircraft position from one, or a combination of the following sensors with the means to establish and follow a desired path: VOR/DME, DME/DME, INS, LORAN C, GNSS.
2.1.2 Only aircraft equipped with RNAV systems would be able to operate on the RNAV routes in the revised South China Sea ATS route structure which forms part of the Singapore FIR. Aircraft that are not RNAV compliant will only be cleared to operate on non-RNAV routes.
2.1.3 The requirements for conduct of RNAV operations are stated in ICAO Doc 9613 (Manual on Required Navigation Performance) and FAA AC 90-45 (Approval of Area Navigation Systems for use in the US National Airspace System).
2.1.4 Minimum longitudinal separation of 10 minutes between RNAV equipped aircraft based on Mach Number Technique is applied on ATS routes A464, A576, B470, G334, L625, L642, L644, M646, M751, M753, M758, M761, M767, M768, M771, M772, M774, N875, N884, N891 and N892 in accordance with DOC 7030/4. MNPS criteria is not required. If item 10 of the flight plan does not include any of the following equipment designators “G”, “I” or “R”, operators shall insert “NAV/NON-RNAV” in item 18 of the flight plan.
2.1.5 Operators of aircraft to which the Mach Number Technique and RNAV procedures will be applied must ensure that the equipment carried on their aircraft have been calibrated in accordance with the applicable airworthiness practices.
2.1.6 An 80NM RNAV distance-based longitudinal separation minima, with Mach Number Technique being applied, is permanently implemented on ATS routes within the oceanic portion of the Singapore FIR.
2.2 MACH NUMBER IN A FLIGHT PLAN
2.2.1 Aircraft are required to include their true Mach Number in item 15 of the ICAO flight plan as follows:
- True airspeed and level preceding the entry point.
- True Mach Number and level at entry point.
Example: Item 15 of a flight plan for a flight from Kuala Lumpur to Kota Kinabalu:
0460F330 M758 VPK/M072F330 M758
2.2.2 Westbound departure flights from Singapore Changi Airport proceeding beyond Indonesia, Malaysia and Thailand shall include Mach Number in item 18 of the flight plan.
2.3 ATC CLEARANCE
2.3.1 The ATC clearance shall include the filed Mach Number which is to be maintained, whether climbing, descending or on level flight.
Example: An ATC clearance for a flight from Kuala Lumpur to Kuching, issued by Lumpur ATC to aircraft:
MAS 518 CLEARED TO KUCHING VIA AIRWAY MIKE 761, MAINTAIN FL290, AT VPK MAINTAIN SPEED OF MACH POINT SEVEN TWO TILL AGOBA. SSR CODE A2215.
2.4 MAINTENANCE/CHANGE OF MACH NUMBER
2.4.1 Aircraft will be cleared to maintain their Mach numbers from the point of entry to the exit point. Pilots shall adhere strictly to the last assigned Mach number and notify ATC of any variation to the cleared (filed) Mach number. Application of longitudinal separation between aircraft when the Mach Number Technique is used is based on the assumption that the assigned Mach number will be maintained at all times. In the event that for operational reasons it is not feasible to do so, the pilot must inform ATC at the time initial clearance or when subsequent clearances are issued or requested.
2.4.2 The current true Mach number shall be included in routine position reports.
2.4.3 When reporting a change in Mach number, pilots should use the following phraseology:
Example
SINGAPORE RADAR, THIS IS MAS 524, SPEED NOW REDUCED (INCREASED) TO MACH POINT SEVEN ZERO
2.5 LONGITUDINAL SEPARATION ON ATS ROUTES M758 AND M761
2.5.1 Longitudinal Separation Minimum
The minimum longitudinal separation between RNAV equipped aircraft on ATS routes M758 and M761 is 10 minutes based on MNT.
2.5.2 Separation of aircraft when the following aircraft is faster
When the following aircraft is faster, for each 600m in distance between the entry and exit points of the area where the Mach Number Technique is used, 1 minute is added for each 0.01 difference in Mach number between the two aircraft concerned to compensate for the fact that the second aircraft is overtaking the first aircraft according to the table in Appendix A (see page ENR 1.8-16).
2.5.3 Separation of aircraft when the preceding aircraft is faster
When the preceding aircraft is maintaining a greater Mach number than the following aircraft, the following separation shall be applied:
- 9 minutes if the preceding aircraft is Mach 0.02 faster than the following aircraft;
- 8 minutes if the preceding aircraft is Mach 0.03 faster than the following aircraft;
- 7 minutes if the preceding aircraft is Mach 0.04 faster than the following aircraft;
- 6 minutes if the preceding aircraft is Mach 0.05 faster than the following aircraft; and
- 5 minutes if the preceding aircraft is Mach 0.06 faster than the following aircraft.
2.6 LONGITUDINAL SEPARATION ON ATS ROUTES A464, A576, B470, G579, L625, L642, L644, M646, M751, M753, M767, M768, M771, M772, N875, N884, N891 AND N892
2.6.1 Requirements
The Mach Number Technique is applied on approved ATS routes between RNAV equipped aircraft.
2.6.2 Separation of aircraft with the same Mach number
10 minutes longitudinal separation shall be applied between aircraft with the same Mach number.
2.6.3 Separation of aircraft when the following aircraft is faster
The same buffer as stated in para 2.5.2 shall be applied.
2.6.4 Separation of aircraft when the preceding aircraft is faster
The separation minima specified in para 2.5.3 shall apply.
2.6.5 15 minutes longitudinal separation minimum
15 minutes longitudinal separation minimum shall be applied on these ATS routes between aircraft which cannot comply with RNAV procedures mentioned in para 2.6.1.
Note: The longitudinal separation minimum for aircraft operating between Singapore and Jakarta airports on airways B470 and G579 is 10 minutes irrespective of whether they are RNAV-equipped.
|
|
|
| APPENDIX A |
|
|
| Table |
|
|
APPLICATION OF MACH NUMBER TECHNIQUE WHEN THE FOLLOWING
AIRCRAFT IS THE FASTER
(BASED ON 10 MINUTES LONGITUDINAL SEPARATION) |
|
|
DIFFERENCE
IN MACH | DISTANCE TO FLY AND SEPARATION (IN MINUTES)
REQUIRED AT ENTRY POINT |
|---|
001-600
(NM) | 601-1200
(NM) | 1201-1800
(NM) | 1801-2400
(NM) | 2401-3000
(NM) |
|---|
| 0.01 | 11 | 12 | 13 | 14 | 15 |
| 0.02 | 12 | 14 | 16 | 18 | 20 |
| 0.03 | 13 | 16 | 19 | 22 | 25 |
| 0.04 | 14 | 18 | 22 | 26 | 30 |
| 0.05 | 15 | 20 | 25 | 30 | 35 |
| 0.06 | 16 | 22 | 28 | 34 | 40 |
| 0.07 | 17 | 24 | 31 | 38 | 45 |
| 0.08 | 18 | 26 | 34 | 42 | 50 |
| 0.09 | 19 | 28 | 37 | 46 | 55 |
| 0.10 | 20 | 30 | 40 | 50 | 60 |
MACH NUMBER TECHNIQUE (MNT) AND AREA NAVIGATION (RNAV)
1 INTRODUCTION
1.1 RNAV is a method which permits aircraft navigation along any desired flight path within the coverage of the associated navigation aids, or within the limits of the capability of self-contained aids, or a combination of these methods. RNAV equipment is considered to be that equipment which operates by automatically determining aircraft position from one, or a combination of the following sensors with the means to establish and follow a desired path: VOR/DME, DME/DME, INS, LORAN C, GNSS.
1.2 Only aircraft equipped with RNAV systems would be able to operate on the RNAV routes in the revised South China Sea ATS route structure which forms part of the Singapore FIR. Aircraft that are not RNAV compliant will only be cleared to operate on non-RNAV routes.
1.3 The requirements for conduct of RNAV operations are stated in ICAO Doc 9613 (Manual on Required Navigation Performance) and FAA AC 90-45 (Approval of Area Navigation Systems for use in the US National Airspace System).
1.4 Minimum longitudinal separation of 10 minutes between RNAV equipped aircraft based on Mach Number Technique is applied on ATS routes A464, A576, B470, G334, L625, L642, L644, M646, M751, M753, M758, M761, M767, M768, M771, M772, M774, N875, N884, N891 and N892 in accordance with DOC 7030/4. MNPS criteria is not required. If item 10 of the flight plan does not include any of the following equipment designators “G”, “I” or “R”, operators shall insert “NAV/NON-RNAV” in item 18 of the flight plan.
1.5 Operators of aircraft to which the Mach Number Technique and RNAV procedures will be applied must ensure that the equipment carried on their aircraft have been calibrated in accordance with the applicable airworthiness practices.
1.6 An 80NM RNAV distance-based longitudinal separation minima, with Mach Number Technique being applied, is permanently implemented on ATS routes within the oceanic portion of the Singapore FIR.
2 MACH NUMBER IN A FLIGHT PLAN
2.1 Aircraft are required to include their true Mach Number in item 15 of the ICAO flight plan as follows:
- True airspeed and level preceding the entry point.
- True Mach Number and level at entry point.
Example: Item 15 of a flight plan for a flight from Kuala Lumpur to Kota Kinabalu:
0460F330 M758 VPK/M072F330 M758
2.2 Westbound departure flights from Singapore Changi Airport proceeding beyond Indonesia, Malaysia and Thailand shall include Mach Number in item 18 of the flight plan.
3 ATC CLEARANCE
3.1 The ATC clearance shall include the filed Mach Number which is to be maintained, whether climbing, descending or on level flight.
Example: An ATC clearance for a flight from Kuala Lumpur to Kuching, issued by Lumpur ATC to aircraft:
MAS 518 CLEARED TO KUCHING VIA AIRWAY MIKE 761, MAINTAIN FL290, AT VPK MAINTAIN SPEED OF MACH POINT SEVEN TWO TILL AGOBA. SSR CODE A2215.
4 MAINTENANCE/CHANGE OF MACH NUMBER
4.1 Aircraft will be cleared to maintain their Mach numbers from the point of entry to the exit point. Pilots shall adhere strictly to the last assigned Mach number and notify ATC of any variation to the cleared (filed) Mach number. Application of longitudinal separation between aircraft when the Mach Number Technique is used is based on the assumption that the assigned Mach number will be maintained at all times. In the event that for operational reasons it is not feasible to do so, the pilot must inform ATC at the time initial clearance or when subsequent clearances are issued or requested.
4.2 The current true Mach number shall be included in routine position reports.
4.3 When reporting a change in Mach number, pilots should use the following phraseology:
Example
SINGAPORE RADAR, THIS IS MAS 524, SPEED NOW REDUCED (INCREASED) TO MACH POINT SEVEN ZERO
5 LONGITUDINAL SEPARATION ON ATS ROUTES M758 AND M761
5.1 Longitudinal Separation Minimum
The minimum longitudinal separation between RNAV equipped aircraft on ATS routes M758 and M761 is 10 minutes based on MNT.
5.2 Separation of aircraft when the following aircraft is faster
When the following aircraft is faster, for each 600m in distance between the entry and exit points of the area where the Mach Number Technique is used, 1 minute is added for each 0.01 difference in Mach number between the two aircraft concerned to compensate for the fact that the second aircraft is overtaking the first aircraft according to the table in Appendix A (see page ENR 1.8-16).
5.3 Separation of aircraft when the preceding aircraft is faster
When the preceding aircraft is maintaining a greater Mach number than the following aircraft, the following separation shall be applied:
- 9 minutes if the preceding aircraft is Mach 0.02 faster than the following aircraft;
- 8 minutes if the preceding aircraft is Mach 0.03 faster than the following aircraft;
- 7 minutes if the preceding aircraft is Mach 0.04 faster than the following aircraft;
- 6 minutes if the preceding aircraft is Mach 0.05 faster than the following aircraft; and
- 5 minutes if the preceding aircraft is Mach 0.06 faster than the following aircraft.
6 LONGITUDINAL SEPARATION ON ATS ROUTES A464, A576, B470, G579, L625, L642, L644, M646, M751, M753, M767, M768, M771, M772, N875, N884, N891 AND N892
6.1 Requirements
The Mach Number Technique is applied on approved ATS routes between RNAV equipped aircraft.
6.2 Separation of aircraft with the same Mach number
10 minutes longitudinal separation shall be applied between aircraft with the same Mach number.
6.3 Separation of aircraft when the following aircraft is faster
The same buffer as stated in para 2.5.2 shall be applied.
6.4 Separation of aircraft when the preceding aircraft is faster
The separation minima specified in para 2.5.3 shall apply.
6.5 15 minutes longitudinal separation minimum
15 minutes longitudinal separation minimum shall be applied on these ATS routes between aircraft which cannot comply with RNAV procedures mentioned in para 2.6.1.
Note: The longitudinal separation minimum for aircraft operating between Singapore and Jakarta airports on airways B470 and G579 is 10 minutes irrespective of whether they are RNAV-equipped.
|
|
|
| APPENDIX A |
|
|
| Table |
|
|
APPLICATION OF MACH NUMBER TECHNIQUE WHEN THE FOLLOWING
AIRCRAFT IS THE FASTER
(BASED ON 10 MINUTES LONGITUDINAL SEPARATION) |
|
|
DIFFERENCE
IN MACH | DISTANCE TO FLY AND SEPARATION (IN MINUTES)
REQUIRED AT ENTRY POINT |
|---|
001-600
(NM) | 601-1200
(NM) | 1201-1800
(NM) | 1801-2400
(NM) | 2401-3000
(NM) |
|---|
| 0.01 | 11 | 12 | 13 | 14 | 15 |
| 0.02 | 12 | 14 | 16 | 18 | 20 |
| 0.03 | 13 | 16 | 19 | 22 | 25 |
| 0.04 | 14 | 18 | 22 | 26 | 30 |
| 0.05 | 15 | 20 | 25 | 30 | 35 |
| 0.06 | 16 | 22 | 28 | 34 | 40 |
| 0.07 | 17 | 24 | 31 | 38 | 45 |
| 0.08 | 18 | 26 | 34 | 42 | 50 |
| 0.09 | 19 | 28 | 37 | 46 | 55 |
| 0.10 | 20 | 30 | 40 | 50 | 60 |
3 RNP 10 NAVIGATION REQUIREMENTS
3.1 INTRODUCTION
3.1.1 ATC will apply 50NM lateral separation minima to aircraft which are approved for RNP 10 operations on RNAV routes:
| L625 | - BTN TOMAN and MEVIN |
| L642 | - BTN CHEUNG CHAU and MERSING |
| L649 | - BTN DAKIX and LAXOR |
| M767 | - BTN JOMALIG and TOMAN |
| M771 | - BTN MERSING and CHEUNG CHAU |
| N884 | - BTN MERSING and MANILA |
| N892 | - BTN HENGCHUN and MERSING |
3.1.2 ATC will apply 60NM lateral separation minima to aircraft which are approved for RNP 10 operations on RNAV routes:
| L644 | - BTN DUDIS and KIKOR |
| M772 | - BTN ASISU and LAXOR |
3.1.3 Pilots shall inform ATC of any deterioration or failure of the navigation systems below the navigation requirements for RNP 10. ATC shall then provide alternative separation and / or alternative routing.
3.1.4 Pilots of aircraft meeting RNP 10 navigation requirements must indicate /R at Item 10 of the ICAO Flight Plan.
3.2 OPERATIONS BY AIRCRAFT NOT MEETING RNP 10 REQUIREMENTS
3.2.1 An aircraft that is unable to meet the minimum navigational requirements for RNP 10 must file flight plan at FL280 or below. Operations above FL280 for these aircraft will be subject to ATC approval, in accordance with the provisions of paragraph 3.2.3.
3.2.2 Pilots of such aircraft wishing to operate on ATS routes specified in paragraph 3.1.1, at or above FL290, must indicate their level requirements at Item 18 of the ICAO Flight Plan as RMK/REQ FL (insert level). Approval to operate at the preferred level will be subject to ATC co-ordination and clearance. Flights that are not approved will be required to operate at FL280 or below or via alternative routes.
3.2.3 ATC units receiving a request for a non-RNP 10 approved aircraft to operate on ATS routes specified in paragraph 3.1.1, at or above FL290, will co-ordinate with adjacent ATC units affected by the flight. In deciding whether or not to approve the flight, each ATC unit will take into consideration:
- traffic density;
- communications, including the non-availability of normal communications facilities;
- weather conditions en-route; and
- any other factors pertinent at the time.
3.3 SAFETY ASSESSMENT CRITERIA
3.3.1 The safety criteria associated with the introduction of the reduced lateral separation minima of 60NM will be in accordance with the requirements for RNP 10 navigation performance, i.e. aircraft navigation performance shall be such that the standard deviation of lateral track errors shall be less than 8.7km (4.7NM).
3.4 MONITORING OF AIRCRAFT NAVIGATION PERFORMANCE
3.4.1 Monitoring of aircraft navigation performance is a joint responsibility between operators, States of Registry or States of Operators (as applicable), regulatory authorities and the ATS providers. The detection and reporting of non-conformance with the navigation requirements against the following parameters will rely primarily on radar monitoring by ATC units:
Lateral Deviations
- a deviation of 15NM or more from track centreline based on radar observations;
Longitudinal Deviations
- where time separation is applied by ATC - when the reported separation based on ATC verified pilot estimates varies by 3 minutes or more from the expected separation at the reporting point; or
- where a distance based standard is applied by ATC based on ADS, radar observation or RNAV distance reports - when the distance varies by 10NM or more from the expected distance.
3.4.2 ATC will advise the pilot-in-command when such deviations are observed and implement the required investigation procedures.
3.4.3 The ATC authority will investigate the causes of such deviations in conjunction with the aircraft operator and the State of Registry, or the State of the Operator, as applicable.
3.5 SEPARATION MINIMA
3.5.1 Lateral Separation Minima
A lateral separation minima of 60NM will be applied between aircraft equipped in accordance with RNP 10 navigation requirements, operating at FL290 or above, on ATS routes L644 and M772 (see paragraph 3.1.2). 50NM lateral separation minima will be applied between aircraft which are approved for RNP10 operations on ATS routes L625, L642, L649,M767, M771, N884 and N892 (see paragraph 3.1.1).
When an aircraft not meeting the RNP 10 navigation requirements is approved to operate at or above FL290, on the ATS routes shown in paragraphs 3.1.1 and 3.1.2, vertical separation shall be applied with aircraft operating on adjacent routes.
3.5.2 Longitudinal Separation
3.5.2.1 80NM RNAV or 10 minutes (or less) Mach Number Technique (MNT) separation minima may be applied between aircraft.
3.5.2.2 50NM longitudinal separation may be applied between RNP10 approved aircraft on ATS routes L642 and M771 which either LOGON to CPDLC or are within VHF radio range.
3.5.3 Vertical Separation
3.5.3.1 A vertical separation minima of 2,000ft, including the use of non-standard levels, will be applied between aircraft operating at FL290 or above, on the ATS routes shown in paragraph 3.1.1.
3.6 OPERATORS’ PROCEDURES
3.6.1 The operator shall ensure in-flight procedures, crew manuals and training programmes are established in accordance with RNP 10 navigation requirements.
3.7 CONTINGENCY PROCEDURES (including WEATHER DEVIATION)
4 NO-PRE-DEPARTURE CO-ORDINATION (NO PDC) PROCEDURES
4.1 INTRODUCTION
4.1.1 No Pre-Departure Co-ordination (No PDC) procedures apply to flights departing from airports within the Bali, Bangkok, Hanoi, Ho Chi Minh, Hong Kong, Jakarta, Kota Kinabalu (including Brunei), Kuala Lumpur, Manila, Phnom Penh, Sanya, Singapore, Taipei and Vientiane FIRs operating on RNAV and ATS routes over the South China Sea.
4.1.2 No Pre-Departure Co-ordination (No PDC) levels and FPL route shall be omitted in content of ATC clearance for departures from Singapore Changi Airport on ATS routes A457, B466 and B469/M752 to destinations in Peninsular Malaysia and Thailand, as well as to Medan Polonia.
4.2 NO PDC FLIGHT LEVEL ALLOCATION
4.2.1 Flight Level Allocation Scheme (FLAS) for Western Pacific / South China Sea Area:
| ATS Route | No-PDC Flight Levels
(Other levels available with prior approval) | Remarks |
|---|
| G334 | Eastbound - FL250, FL270
Westbound - FL260, FL280 | |
|---|
| G580 | Eastbound - FL270, FL290, FL330
Westbound - FL280, FL300, FL340 | |
|---|
| L517 | FL280, FL300, FL340 | Uni-directional |
|---|
| L625 | FL310, FL320, FL350, FL360, FL390, FL400 | Uni-directional |
|---|
| L642 | FL310, FL320, FL350, FL360, FL390, FL400 | Uni-directional |
|---|
| L644 | Southbound - FL330, FL410 | |
|---|
| L759 | Aircraft requesting FL280, FL300 and FL320 will be cleared to FL280. Succeeding aircraft on the same route will be cleared to FL280 with 10 min longitudinal separation provided there is no closing speed with the preceding aircraft. Additional longitudinal separation as appropriate shall be provided by ATC for the faster aircraft following a slower aircraft on the same route. | The first aircraft from either Singapore or Kuala Lumpur to be over GUNIP on N571 or N571/N877, the Kuala Lumpur/ Bangkok FIR BDRY on M770 or L759 and VPL on P628, can expect its requested flight level. |
|---|
| B469 / M751 | FL280, FL300, FL320, FL340, FL360, FL380, FL400 | For flights to/from airports within Bangkok FIR |
|---|
| M753 | Northbound - FL260, FL300, FL380
Southbound - FL270, FL330 | |
|---|
| M754 | Northbound - FL300, FL340, FL380
Southbound - FL290, FL330, FL370, FL410 | |
|---|
| M758 | Eastbound - FL270, FL290, FL330
Westbound - FL280, FL300, FL340 | |
|---|
| M761 | Eastbound - FL270, FL290, FL330
Westbound - FL280, FL300, FL340 | |
|---|
| M767 | FL310, FL320, FL350, FL360, FL390, FL400 | Uni-directional |
|---|
| M768 | Eastbound - FL270, FL330, FL410
Westbound - FL300, FL380 | |
|---|
| M770 | Aircraft requesting FL280, FL300 and FL320 will be cleared to FL280. Succeeding aircraft on the same route will be cleared to FL280 with 10 min longitudinal separation provided there is no closing speed with the preceding aircraft. Additional longitudinal separation as appropriate shall be provided by ATC for the faster aircraft following a slower aircraft on the same route. | The first aircraft from either Singapore or Kuala Lumpur to be over GUNIP on N571 or N571/N877, the Kuala Lumpur/ Bangkok FIR BDRY on M770 or L759 and VPL on P628, can expect its requested flight level. |
|---|
| M771 | FL310, FL320, FL350, FL360, FL390, FL400 | Uni-directional |
|---|
| M772 | Northbound - FL300, FL380 | |
|---|
N571
N877 | Aircraft requesting FL280, FL300 and FL320 will be cleared to FL280. Succeeding aircraft on the same route will be cleared to FL280 with 10 min longitudinal separation provided there is no closing speed with the preceding aircraft.
Additional longitudinal separation as appropriate shall be provided by ATC for the faster aircraft following a slower aircraft on the same route. | The first aircraft from either Singapore or Kuala Lumpur to be over GUNIP on N571 or N571/N877, the Kuala Lumpur/Bangkok FIR BDRY on M770 or L759 and VPL on P628, can expect its requested flight level. |
|---|
| N875 | Eastbound - FL290, FL330, FL370
Westbound - FL300, FL340, FL380 | |
|---|
| N884 | FL310, FL320, FL350, FL360, FL390, FL400 | Uni-directional |
|---|
| N891 | Northbound - FL260, FL300, FL380
Southbound - FL330 | |
|---|
| N892 | FL310, FL320, FL350, FL360, FL390, FL400 | Uni-directional |
|---|
| P628 | Aircraft requesting FL280, FL300 and FL320 will be cleared to FL280. Succeeding aircraft on the same route will be cleared to FL280 with 10 min longitudinal separation provided there is no closing speed with the preceding aircraft.
Additional longitudinal separation as appropriate shall be provided by ATC for the faster aircraft following a slower aircraft on the same route. | The first aircraft from either Singapore or Kuala Lumpur to be over GUNIP on N571 or N571/N877, the Kuala Lumpur/Bangkok FIR BDRY on M770 or L759 and VPL on P628, can expect its requested flight level. |
|---|
4.2.2 FLAS for Large Scale Weather Deviations (LSWD) in Western Pacific / South China Sea Area as applicable by Singapore ACC:
| Flight Level Allocation (LSWD) | ATS Route and Direction of Flight |
|---|
| L642 | M771 | N892 | L625 | N884 | M767 |
|---|
| SW | NE | SW | NE | NE | SW |
| 410 | | | | | | |
| 400 | 400 | | 400 | | | 400 |
| 390 | | 390 | | 390 | 390 | |
| 380 | | | | | | |
| 370 | | | | | | |
| 360 | 360 | | 360 | | | 360 |
| 350 | | 350 | | 350 | 350 | |
| 340 | | | | | | |
| 330 | | | | | | |
| 320 | 320 | | 320 | | | 320 |
| 310 | | 310 | | 310 | 310 | |
| 300 | | | | | | |
| 290 | | | | | | |
NO-PRE-DEPARTURE CO-ORDINATION (NO PDC) PROCEDURES
1 INTRODUCTION
1.1 No Pre-Departure Co-ordination (No PDC) procedures apply to flights departing from airports within the Bali, Bangkok, Hanoi, Ho Chi Minh, Hong Kong, Jakarta, Kota Kinabalu (including Brunei), Kuala Lumpur, Manila, Phnom Penh, Sanya, Singapore, Taipei and Vientiane FIRs operating on RNAV and ATS routes over the South China Sea.
4.1.2 No Pre-Departure Co-ordination (No PDC) levels and FPL route shall be omitted in content of ATC clearance for departures from Singapore Changi Airport on ATS routes A457, B466 and B469/M752 to destinations in Peninsular Malaysia and Thailand, as well as to Medan Polonia.
2 NO PDC FLIGHT LEVEL ALLOCATION
2.1 Flight Level Allocation Scheme (FLAS) for Western Pacific / South China Sea Area:
| ATS Route | No-PDC Flight Levels
(Other levels available with prior approval) | Remarks |
|---|
| G334 | Eastbound - FL250, FL270
Westbound - FL260, FL280 | |
|---|
| G580 | Eastbound - FL270, FL290, FL330
Westbound - FL280, FL300, FL340 | |
|---|
| L517 | FL280, FL300, FL340 | Uni-directional |
|---|
| L625 | FL310, FL320, FL350, FL360, FL390, FL400 | Uni-directional |
|---|
| L642 | FL310, FL320, FL350, FL360, FL390, FL400 | Uni-directional |
|---|
| L644 | Southbound - FL330, FL410 | |
|---|
| L759 | Aircraft requesting FL280, FL300 and FL320 will be cleared to FL280. Succeeding aircraft on the same route will be cleared to FL280 with 10 min longitudinal separation provided there is no closing speed with the preceding aircraft. Additional longitudinal separation as appropriate shall be provided by ATC for the faster aircraft following a slower aircraft on the same route. | The first aircraft from either Singapore or Kuala Lumpur to be over GUNIP on N571 or N571/N877, the Kuala Lumpur/ Bangkok FIR BDRY on M770 or L759 and VPL on P628, can expect its requested flight level. |
|---|
| B469 / M751 | FL280, FL300, FL320, FL340, FL360, FL380, FL400 | For flights to/from airports within Bangkok FIR |
|---|
| M753 | Northbound - FL260, FL300, FL380
Southbound - FL270, FL330 | |
|---|
| M754 | Northbound - FL300, FL340, FL380
Southbound - FL290, FL330, FL370, FL410 | |
|---|
| M758 | Eastbound - FL270, FL290, FL330
Westbound - FL280, FL300, FL340 | |
|---|
| M761 | Eastbound - FL270, FL290, FL330
Westbound - FL280, FL300, FL340 | |
|---|
| M767 | FL310, FL320, FL350, FL360, FL390, FL400 | Uni-directional |
|---|
| M768 | Eastbound - FL270, FL330, FL410
Westbound - FL300, FL380 | |
|---|
| M770 | Aircraft requesting FL280, FL300 and FL320 will be cleared to FL280. Succeeding aircraft on the same route will be cleared to FL280 with 10 min longitudinal separation provided there is no closing speed with the preceding aircraft. Additional longitudinal separation as appropriate shall be provided by ATC for the faster aircraft following a slower aircraft on the same route. | The first aircraft from either Singapore or Kuala Lumpur to be over GUNIP on N571 or N571/N877, the Kuala Lumpur/ Bangkok FIR BDRY on M770 or L759 and VPL on P628, can expect its requested flight level. |
|---|
| M771 | FL310, FL320, FL350, FL360, FL390, FL400 | Uni-directional |
|---|
| M772 | Northbound - FL300, FL380 | |
|---|
N571
N877 | Aircraft requesting FL280, FL300 and FL320 will be cleared to FL280. Succeeding aircraft on the same route will be cleared to FL280 with 10 min longitudinal separation provided there is no closing speed with the preceding aircraft.
Additional longitudinal separation as appropriate shall be provided by ATC for the faster aircraft following a slower aircraft on the same route. | The first aircraft from either Singapore or Kuala Lumpur to be over GUNIP on N571 or N571/N877, the Kuala Lumpur/Bangkok FIR BDRY on M770 or L759 and VPL on P628, can expect its requested flight level. |
|---|
| N875 | Eastbound - FL290, FL330, FL370
Westbound - FL300, FL340, FL380 | |
|---|
| N884 | FL310, FL320, FL350, FL360, FL390, FL400 | Uni-directional |
|---|
| N891 | Northbound - FL260, FL300, FL380
Southbound - FL330 | |
|---|
| N892 | FL310, FL320, FL350, FL360, FL390, FL400 | Uni-directional |
|---|
| P628 | Aircraft requesting FL280, FL300 and FL320 will be cleared to FL280. Succeeding aircraft on the same route will be cleared to FL280 with 10 min longitudinal separation provided there is no closing speed with the preceding aircraft.
Additional longitudinal separation as appropriate shall be provided by ATC for the faster aircraft following a slower aircraft on the same route. | The first aircraft from either Singapore or Kuala Lumpur to be over GUNIP on N571 or N571/N877, the Kuala Lumpur/Bangkok FIR BDRY on M770 or L759 and VPL on P628, can expect its requested flight level. |
|---|
2.2 FLAS for Large Scale Weather Deviations (LSWD) in Western Pacific / South China Sea Area as applicable by Singapore ACC:
| Flight Level Allocation (LSWD) | ATS Route and Direction of Flight |
|---|
| L642 | M771 | N892 | L625 | N884 | M767 |
|---|
| SW | NE | SW | NE | NE | SW |
| 410 | | | | | | |
| 400 | 400 | | 400 | | | 400 |
| 390 | | 390 | | 390 | 390 | |
| 380 | | | | | | |
| 370 | | | | | | |
| 360 | 360 | | 360 | | | 360 |
| 350 | | 350 | | 350 | 350 | |
| 340 | | | | | | |
| 330 | | | | | | |
| 320 | 320 | | 320 | | | 320 |
| 310 | | 310 | | 310 | 310 | |
| 300 | | | | | | |
| 290 | | | | | | |
5 STRATEGIC LATERAL OFFSET PROCEDURES
5.1 INTRODUCTION
5.1.1 Studies and safety analyses conducted by the ICAO Separation and Airspace Safety Panel (SASP) have shown that the application of a strategic lateral offset by aircraft from route centre line would result in an overall increase in safety of operations in remote and oceanic airspace.
5.2 STRATEGIC LATERAL OFFSETS IN EN-ROUTE AIRSPACE
5.2.1 Offsets may be applied outside surveillance cover in en-route airspace within the Singapore FIR.
5.2.2 Offsets may only be applied by aircraft with automatic offset tracking capability.
5.2.3 The following requirements may apply to the use of the offset:
The decision to apply a strategic lateral offset is the responsibility of the flight crew;
The offset shall be established at a distance of one or two nautical miles to the right of the centre line relative to the direction of flight. Offsets are not to exceed two nautical miles right of centre line;
The strategic lateral offset procedure has been designed to include offsets to mitigate the effects of wake turbulence of preceding aircraft. If wake turbulence needs to be avoided, offsets to the right of the centreline relative to the direction of flight in tenths of a nautical mile up to a maximum of 3.7km (2nm) shall be used.
Pilots may contact other aircraft on the air to air frequency, 123.45MHz, as necessary, to coordinate the best wake turbulence offset option. As noted below, it is not necessary to notify air traffic control of approved offsets;
In airspace where the use of lateral offsets has been authorized, ATC clearance is not required for this procedure and pilots are not required to inform ATC that an offset is being applied;
Position reports are based on the current ATC clearance and not the exact coordinates of the offset position.
An example of a position report made by a pilot when passing reporting point TODAM while being offset from track is:
“Singapore Radio, Singapore 871, position TODAM 0930 Flight Level 380, estimate.....etc”.
6 CHANGI FLOW MANAGEMENT PROCEDURES
6.1 INTRODUCTION
6.1.1 The objectives of the procedures are to improve the efficiency of Singapore’s air traffic service by minimising radar vectoring as well as improving airspace capacity.
6.1.2 The procedures require the holding of Changi arrivals over established holding areas.
6.2 ENTRY AND EXIT GATES
6.2.1 ‘Entry gates’ and ‘Exit gates’ are established to ensure segregation between arriving and departing aircraft operating at Singapore Changi Airport. These gates (waypoints) are incorporated in the RNAV SIDs/STARs which have been implemented to support the flow management procedures. The ‘entry’ and ‘exit’ gates are shown below:
| Entry Gate | | Coordinates |
|---|
| BOBAG | | 010230N 1032954E |
| PASPU | | 015915N 1040618E |
| REMES | | 004342N 1035735E |
| LAVAX | | 010950N 1042714E |
6.3 ARRIVING AIRCRAFT TO SINGAPORE CHANGI AIRPORT
6.3.1 STANDARD INSTRUMENT ARRIVAL (STAR)
IFR flight should expect a Standard Instrument Arrival (STAR). Changi arrivals via ATS route A464 shall flight plan BOBAG 1 Alpha or BOBAG 1 Bravo as STAR route. BOBAG 1 Kilo, BOBAG 1 Lima and LELIB 2 Bravo STAR would be issued to pilots when traffic permits.
6.3.2 ENTRY GATE TIME
To regulate the flow of traffic into the Approach airspace, ATC will issue, when necessary, a time restriction at an entry gate associated with the inbound route of the flight into Singapore Changi Airport.
6.3.3 DESCENT PROFILE
Pilots shall plan their descent profile in accordance to the published STAR procedures.
6.3.4 SPEED CONTROL
Speed control restrictions are incorporated into the STARs toenhance predictability and planning of air traffic in the Approach airspace. Pilots shall adhere to the speed control restrictions published in the STAR procedures unless otherwise advised. ATC may issue further speed adjustment during the different phases of the flight if traffic situation warrants.
6.4 APPROACH AIRSPACE HOLDING PROCEDURES
6.4.1 ENTRY PROCEDURE
The entry into the holding patterns shall be in accordance with the three-sector entry procedure as prescribed in ICAO Doc 8168 - OPS/611 Edition 1993.
6.4.2 RATE OF TURN
All turns are to be made at a bank angle of 25° or at a rate of 3° per second, whichever requires the lesser bank.
6.4.3 DESCENT PROCEDURE
When instructed to join a holding pattern, pilots shall reach their assigned altitudes prior to arriving at the holding point. This will allow appropriate traffic sequencing and the reduction of step-descents in the holding pattern.
DETAILS OF APPROACH AIRSPACE HOLDING AREAS
| Holding Fix / ID / Co-ordinates | Inbound Track °M | Direction of Turn | MAX HLDG Speed (IAS) | Time (MIN) | MNM-MAX HLDG Level | Controlling Unit and Frequency |
|---|
| 1 | 2 | 3 | 4 | 5 | 6 | 7 |
NYLON
013657N 1040624E | 203° | Left | 220 knots | 1 | FL140
3,000ft | Singapore Approach
124.05MHz (PRI)
132.15MHz (SRY) |
LAVAX
010950N 1042714E | 269° | Left | 220 knots | 1 | FL140
7,000ft | Singapore Approac
124.05MHz (PRI)
132.15MHz (SRY) |
REMES
004342N 1035735E | 348° | Right | 220 knots | 1 | FL140
6,000ft | Singapore Approach
124.6MHz (PRI)
132.15MHz (SRY) |
BOBAG
010230N 1032954E | 083° | Right | 220 knots | 1 | FL140
6,000ft | Singapore Approac
124.6MHz (PRI)
132.15MHz (SRY) |
6.4.5 ALTERNATE HOLDING AREAS
In the event of inclement weather or capacity constraints rendering a specific holding area unusable, arrivals may be cleared to an alternate holding area for re-sequencing. To ensure smooth transition to alternate holding area, all arrivals bound for Singapore Changi Airport shall have their FMS programmed with all the four promulgated holding areas (paragraph 6.4.4)
6.5 EXPECTED TIME TO LEAVE HOLDING AREA
6.5.1 If arrival delay is processed by means of holding, pilots will be informed of the expected time to leave the respective holding area.
6.5.2 The expected time to leave is issued to serve as an early notification of the probable holding duration as well as for unforeseen circumstance such as radio failure (see page ENR 1.6-4). Subsequently, a specified time to leave the holding area will be issued to pilots to resume the flight according to the assigned RNAV STARs.
6.6 DEPARTING AIRCRAFT FROM SINGAPORE CHANGI AIRPORT
6.6.1 DEPARTURE SPEED CONTROL
Departing aircraft shall not exceed IAS 230 knots below 4,000 feet AMSL or at the waypoints specified in the SID and not exceed IAS 250 knots below 10,000 feet AMSL. Pilots shall also comply with speed control restrictions according to published SIDs.
7 AUTOMATIC DEPENDENT SURVEILLANCE BROADCAST (ADS-B) OUT EXCLUSIVE AIRSPACE WITHIN PARTS OF THE SINGAPORE FIR
7.1 ADS-B BASED SURVEILLANCE AIRSPACE AND AIRCRAFT OPERATOR APPROVAL
7.1.1 Aircraft that operates on ATS routes L642, M771, N891 M753, L644, N892 and M904 within airspace bounded by 073605N 1090045E, 040713N 1063543E, 041717N 1061247E (MABLI), 044841N 1052247E (DOLOX), 045223N 1041442E (ENREP), 045000N 1034400E, thence north along the Singapore FIR boundary to 070000N 1080000E at or above FL290 must carry serviceable ADS-B transmitting equipment that has been certified as meeting EASA AMC 20-24, or FAA AC No. 20-165A - Airworthiness Approval of ADS-B, or meets the equipment configuration standards in Appendix XI of Civil Aviation Order 20.18 of the Civil Aviation Safety Authority of Australia.
7.1.2 Aircraft that does not comply with the requirements stipulated in paragraph 7.1.1 will not be accorded priority n the delineated airspace and flight level assignments would be subjected to air traffic conditions.
7.1.3 If an aircraft carries ADS-B transmitting equipment but does not comply with the requirements stipulated in paragraph 7.1.1, the aircraft must not fly in the delineated airspace unless the equipment is deactivated or set to transmit only a value of zero for the Navigation Uncertainty Category (NUCp) or Navigation Integrity Category (NIC).
7.1.4 Flights operating in the delineated airspace are to contact Singapore Radar on 134.35MHz (primary frequency) and 133.6MHz (secondary frequency).
7.2 FLIGHT PLANNING REQUIREMENTS
7.2.1 Aircraft operators complying with the requirements stipulated in paragraph 7.1.1 are to indicate the appropriate ADS-B designator in Item 10 of the ICAO flight plan:
| B1 | ADS-B with dedicated 1090 MHz ADS-B “out” capability |
| B2 | ADS-B with dedicated 1090 MHz ADS-B “out” and “in” capability |
7.2.2 Aircraft operators are to include the aircraft address (24 Bit Code) in hexadecimal format in Item 18 of the ICAO flight plan as per the following example:
7.2.3 Aircraft Identification (ACID) not exceeding 7 characters must be accurately indicated in Item 7 of the ICAO flight plan and replicated exactly when set in the aircraft avionics (for transmission as Flight ID) as follows:
| either | |
| |
| a) | The three-letter ICAO designator of the aircraft operator followed by the flight number (e.g. SIA123, MAS123, GIA123), when radiotelephony callsign consists of the associated ICAO telephony designator for the aircraft operator followed by the flight number (e.g. SINGAPORE 123, MALAYSIAN 123, INDONESIA 123). |
| |
| or | |
| |
| b) | The aircraft registration (e.g. N555AB, 9VABC) when the radiotelephony callsign consists of the aircraft registration. |
| |
Important: ACID entered should not have any leading zeros unless it is part of the flight number as indicated in Item 7 of the ICAO flight plan. Hyphens, dashes or spaces are NOT to be used.7.3 STATE AIRCRAFT
7.3.1 The conditions stipulated apply to STATE aircraft intending to operate within the delineated airspace.
7.4 INFLIGHT CONTINGENCIES
7.4.1 The pilot-in-command, upon awareness of an onboard ADS-B equipment failure, must inform ATC as soon as possible. ATC would then provide the necessary clearance to ensure separation with other flights operating in the delineated airspace.
7.5 ATC-PILOT PHRASEOLOGIES
7.5.1 Aircraft operators and pilots are to note the following phraseologies when operating in the delineated airspace:
| Circumstances | Phraseologies |
|---|
| 1 | To request the capability of the ADS-B equipment | | a) | ADVISE ADS-B CAPABILITY | | *b) | ADS-B TRANSMITTER (data link) | | *c) | ADS-B RECEIVER (data link) | | *d) | NEGATIVE ADS-B | | * | Denotes pilot transmission |
|
| 2 | To request reselection of aircraft identification | RE-ENTER ADS-B AIRCRAFT IDENTIFICATION |
| 3 | To request the operation of the IDENT feature | TRANSMIT ADS-B IDENT |
| 4 | To request transmission of pressure-altitude | TRANSMIT ADS-B ALTITUDE |
| 5 | To request termination of transponder and / or ADS-B transmitter operation | a) STOP SQUAWK [TRANSMIT ADS-B ONLY]
b) STOP ADS-B TRANSMISSION [SQUAWK (code) ONLY] |
| 6 | To request termination of pressure-altitude transmission because of faulty operation | STOP ADS-B ALTITUDE TRANSMISSION [WRONG INDICATION, or reason] |
| 7 | Confirmation of ADS-B operations | ADS-B TRANSMISSION NOT RECEIVED, CONFIRM ADS-B OPERATIONAL |
| 8 | To inform an aircraft that its ADS-B transmitter appears to be inoperative or malfunctioning | ADS-B TRANSMITTER APPEARS TO BE INOPERATIVE / MALFUNCTION |
| 9 | ATS ADS-B surveillance system ground equipment un-serviceability | ADS-B OUT OF SERVICE (appropriate information as necessary) |