The supplementary procedures in force are given in their entirely; "differences" are printed in capital letters.
Unless otherwise specified in 10.5 or authorized by the area Air Traffic Services Units cruising levels to be assigned to IFR flight within controlled airspace will be as given in the table in Appendix 3 to Annex 2.
All aircraft on VFR flights and aircraft on IFR flights outside controlled airspace, must maintain a watch on a radio station furnishing communications for the Bangkok Area Control Centre and file that station information as to their position unless not equipped with suitable two-way radio communications or unless otherwise authorized. The last position reported before passing from Bangkok Flight Information Region to an adjacent Flight Information Region must also be addressed to the Air Traffic Services Unit providing Flight Information Service or Air Traffic Control Service within the Flight Information Region the aircraft is entering.
The procedures for "Alerting Service" detailed in the PAN-RAC (Doc 4444/RAC 501) Part VII, paragraph 2 are applicable to:
flights operated more than 100 NM from the shore line; and
all flights with the exception of such local flights as may be exempted by Air Traffic Control.
Note: For the purpose of sub-para v (b), a local flight is a flight wholly conducted in the immediate vicinity of an aerodrome. Provision must be made in the detailed plan for the conduct of search and rescue to provide, to the extent possible, servicing and refuelling. facilities to aircraft, vessels, and vehicles made available for search and rescue operations for other States upon request.
In so far as practicable Air Traffic Services units responsible for the provision of Flight Information Service over water areas must include, at the pilot's request, any available information regarding surface vessels such as radio call signs, positions, true track, speed etc. Responsibility for Flight Information Service passes from Centre to Centre at the time the aircraft crosses the Flight Information Region boundary. When adequate point-to-point communications do not exist with adjacent Flight Information Regions, Flight Information Service will be provided as far as practicable by the Centre to an aircraft leaving Bangkok FIR until reliable communication contact has been established with the Centre whose Flight Information Region it is entering
Coordination procedures are in accordance with Regional Supplementary Procedures, supported by detailed local Letters of Agreement.
All instructions to aircraft from Air Traffic Services units, excluding aerodrome and approach control instructions, are transmitted by a communication network designated by the government. Instructions to aircraft from aerodrome and approach control Air Traffic Services units are routed through a government owned radio network. All area control service information or instructions issued to aircraft are made available to an operator or this designated representative as agreed between the operator and the Air Traffic Services units concerned.
Flight plan messages are transmitted to the appropriate Air Traffic Services units and communication stations immediately after the flight plan is filed. The flight plan will be combined with the departure message only if it is reasonably certain that it will reach the addresses in good time, in which case it is transmitted immediately after the departure of the aircraft. For a flight through an intermediate stop the flight plan message originated by the Air Traffic Services unit at the aerodrome of initial departure is considered as a single message, i.e. the number of addressees which may be requested by the operator is limited to two in addition to the one at the aerodrome of aircraft departure and to the one at each aerodrome of intended landing.
When the departure of an aircraft is delayed for more than 10% of the scheduled flight time, but in no case less than 30 minutes after the proposed time of departure contained in the flight plan, ATC will originate a delay message addressed to all recipients of the flight plan message. When a flight plan has been filed through intermediate stop, a departure message will be sent, on the departure of the aircraft from each intermediate stop, to the Air Traffic Services unit of next intended point of landing and to all interested area control or flight information centres. NUMBER OF PERSONS ON BOARD AND FUEL ARE NOT GIVEN IN THE FLIGHT PLAN.
When aeronautical communications are available and when an arrival report is received by an ATC Unit serving the aerodrome of destination, an arrival message will be transmitted to the point of departure. Arrival reports may be filed at points where the absence of communication facilities precludes the transmission of arrival messages. It should be noted, however, that Bangkok ACC does not transmit arrival messages except in accordance with paragraph 10.2 Part 1, Doc 7030 - "Regional Supplementary Procedures".
Based on current and anticipated atmospheric pressure distribution, Bangkok ACC coordinates where required the lowest flight level to be used.
Note: suggested phraseology
Standard separation not available deviate at pilot's discretion suggest climb to FL 340 parallel traffic 50 miles north at FL 350 report deviation complete.
Operators must obtain airworthiness and operational approval from their States of Registry or States of Operator, as appropriate, to conduct RVSM operations.
Information regarding the process for RVSM approval is contained, for commercial air transport operations, in Notification of The Civil Aviation Authority of Thailand publication, Air Certificate Requirements, Issue 02, Revision 00, dated 30 April 2021.
Additionally, The Monitoring Agency for Asia Region (MAAR) details approval requirements for operators and specifies the RVSM approval flow. This information may be found at https://www.aerothai.co.th/maar/
Guidance Material for the Continued Safety Monitoring of the Asia-Pacific RVSM Airspace is published by the Asia and Pacific Office of ICAO. The purpose of this document is to describe safety monitoring activities for RVSM airspace, including the respective roles and responsibilities of States and Regional Monitoring Agencies (RMAs).
With respect to requirements for Thai operators, full details on the monitoring requirements and available monitoring services are available from MAAR at the website listed above.
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.
two primary altimetry systems. A cross-check between the primary altimeters should be made. A minimum of two will need to agree within ±60m (±200FT). Failure to meet this condition will require that the altimetry system be reported as defective and air traffic control (ATC) notified;
one automatic altitude-keeping device;
one altitude-alerting device; and
one altitude operating transponder
| Message | Phraseology |
| For a controller to ascertain the RVSM approval status of an aircraft | (call sign) CONFIRM RVSM APPROVED |
| For a pilot to report RVSM approval status | AFFIRM RVSM |
For a pilot to report non-RVSM approval status:
Additionally, except for State aircraft, pilot shall include this phrase to read back flight level clearances involving the vertical transit through FL 290 or FL 410 | NEGATIVE 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 |
| For a controller to deny of clearance into the RVSM airspace | (call sign) UNABLE CLEARANCE INTO RVSM AIRSPACE, MAINTAIN [or DESCEND TO, or CLIMB TO] FLIGHT LEVEL (number) |
| 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 en-route below that required for flight within the RVSM airspace. (See Appendix A) (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 controller to request an aircraft to provide information as soon as RVSM-approved status has been regained or the pilot is ready to resume RVSM operations | REPORT WHEN ABLE TO RESUME RVSM |
| For a controller to request confirmation that an aircraft has regained RVSM-approved status or a pilot is ready to resume RVSM operations | CONFIRM ABLE TO RESUME RVSM |
| 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 |
Example 1:
A non-RVSM approved aircraft, maintaining FL 260, subsequently requests a climb to FL 320.
Pilot: (call sign) REQUEST FL 320, NEGATIVE RVSM
Controller: (call sign) CLIMB TO FL 320
Pilot: (call sign) CILMB TO FL 320, NEGATIVE RVSM
Example 2:
A non-RVSM approved aircraft, maintaining FL 260, subsequently requests a climb to FL 430.
Pilot: (call sign) REQUEST FL 430, NEGATIVE RVSM
Controller: (call sign) CLIMB TO FL 430
Pilot: (call sign) CILMB TO FL 430, NEGATIVE RVSM
Example 3:
A non-RVSM approved aircraft, maintaining FL 360, subsequently requests a climb to FL380.
Pilot: (call sign) REQUEST FL 380, NEGATIVE RVSM
Controller: (call sign) CLIMB TO FL 380
Pilot: (call sign) CILMB TO FL 380, NEGATIVE RVSM
Example 4:
A non-RVSM approved civil aircraft, maintaining FL 280, subsequently requests a climb to FL320.
Pilot: (call sign) REQUEST FL 320, NEGATIVE RVSM
Controller: (call sign) UNABLE CLEARANCE INTO RVSM AIRSPACE, MAINTAIN FL 280
When informed by the pilot of an RVSM-approved aircraft operating in RVSM airspace that the aircraft’s equipment no longer meets the RVSM requirements, ATC shall consider the aircraft as non-RVSM-approved.
The pilot shall inform ATC, as soon as practicable, of any restoration of the proper functioning of equipment required to meet the RVSM requirements.
The first ACC to become aware of a change in an aircraft’s RVSM status shall coordinate with adjacent ACCs, as appropriate.
Scenario 1: All automatic altitude control systems fail (e.g., Automatic Altitude Hold).
| The Pilot should | ATC can be expected to |
| Initially, maintain CFL and 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
| |
| Notify ATC of the failure and intended course of action. Possible courses of action include: | Obtain pilot’s intentions, and pass essential traffic information. |
|
|
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 fail
| 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
| |
| Consider declaring an emergency. Notify ATC of the failure and intended course of action. Possible courses of action include: | Obtain pilot’s intentions, and pass essential traffic information. |
|
|
Scenario 4: The primary altimeters diverge by more than 200 FT (60 m)
| The Pilot should |
| Determine the defective system through the normal airplane integrated comparator warning system or in the absence of such a system, establish trouble-shooting procedures comparing the primary altimeters to the standby altimeter (corrected using the correction card) |
| If the defective system can be determined, couple the functioning altimeter to the altitude keeping device in use. |
| If the defective system cannot be determined, follow the guidance in Scenario 3 for failure or unreliable altimeter indications of all primary altimeters |
When a meteorological forecast is predicting severe turbulence, ATC shall determine whether RVSM should be suspended and, if so, for how long and for which specific flight level(s) and/or area.
In cases where RVSM will be suspended, the ACC suspending RVSM shall coordinate with adjacent ACCs with regard to the flight levels appropriate for the transfer of traffic; unless a contingency flight level allocation scheme has been determined by letter of agreement. The ACC suspending RVSM shall also coordinate applicable sector capabilities with adjacent ACCs as appropriate.
When an aircraft operating in RVSM airspace encounters severe turbulence due to weather or wake vortex that the pilot believes will impact the aircraft’s capability to maintain its cleared flight level, the pilot shall inform ATC. ATC shall establish either an appropriate horizontal separation or an increased minimum vertical separation.
ATC shall, to the extent possible, accommodate pilot requests for flight level and/or route changes and shall pass on traffic information as required.
ATC shall solicit reports from other aircraft to determine whether RVSM should be suspended entirely or within a specific flight level band and/or area.
ACC suspending RVSM shall coordinate such suspension(s) with, and any required adjustments to, sector capabilities with adjacent ACCs, as appropriate, to ensure an orderly progression to the transfer of traffic.
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
| |
| Notify ATC of intended course of action as soon as possible. Possible courses of action include: | |
|
|
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.
The aircraft is being initially delivered to the State of Registry or Operator; or
The aircraft was 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
The aircraft is transporting a spare engine mounted under the wing; 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)
Note: The procedures are intended exclusively for the purposes indicated and not as a means to circumvent the normal RVSM approval process.
| ATS Route |
No-Pre-Departure Coordination (No-PDC) Flight Levels Other levels available with prior approval |
|---|---|
|
L880 / L628 (EB) L628 | EB – FL330, FL370, FL410 WB – FL280, FL340 |
| N891 |
SB – FL330 NB – FL260, FL300, FL380 |
| A1 |
EB – FL290, FL330, FL370, FL390, FL410 WB – FL280, FL300, FL340, FL380, FL400 |
|
N506 / M768 (EB) M768 |
EB – FL270, FL330, FL410 WB – FL300, FL380 |
| A202 |
EB – FL290, FL330, FL370, FL390, FL410 WB – FL280, FL300, FL340, FL380, FL400 |
When a loss of normal communications requires TIBA procedures to be implemented, pilots shall make broadcasts in English on 128.95 MHz as follows:
At the time the loss of normal communications is recognized;
10 minutes before entering a designated airspace when it is known in advance that normal communications will not be available within that airspace or, for a pilot taking off from an aerodrome located within the lateral limits of the designated airspace, as soon as appropriate after take-off;
10 minutes prior to crossing a reporting point;
10 minutes prior to crossing or joining an ATS route;
at 20 minutes intervals between distant reporting points;
2 to 5 minutes, where possible, before a change in flight level;
at the of a change in flight level; and
at any other time considered necessary by the pilot.
Note: Normal position reporting procedures should be continued at all times, regardless of any action taken to initiate or acknowledge a traffic information broadcast.
TIBA broadcasts should be made using the following phraseology:
For other than those indicating changes in flight level:
ALL STATIONS (call sign) FLIGHT LEVEL (number) [of CLIMBING TO FLIGHT LEVEL (number)] (direction) (ATS route) [or DIRECT FROM (position) TO (position) POSITION] (position) AT (time) ESTIMATING (next reporting point, or the point of crossing or joining a designated ATS route) AT (time) (call sign) FLIGHT LEVEL (number) (direction)
Example: “ALL STATIONS WINDAR 671 FLIGHT LEVEL 380 NORTHWEST BOUND A464 POSITION 80 MILES SOUTH EAST OF KEVOK AT 2358 ESTIMATING KOBAS AT 0020 WINDAR 671 FLIGHT LEVEL 380 NORTHWEST BOUND OUT”
Note: For broadcasts made when the aircraft is not near an ATS significant point, the position should be given as accurately as possible and in any case to the nearest 30 minutes of latitude and longitude.
Before a change in flight level:
ALL STATIONS (call sign) (direction) (ATS route) [or DIRECT FROM (position) TO (position)] LEAVING FLIGHT LEVEL (number) FOR FLIGHT LEVEL (number) AT (position and time)
At the time of a change in flight level:
ALL STATIONS (call sign) (direction) (ATS route) [or DIRECT FROM (position) TO (position)] LEAVING FLIGHT LEVEL (number) NOW FOR FLIGHT LEVEL (number) followed by: ALL STATIONS (call sign) MAINTAINING FLIGHT LEVEL (number)
When reporting a temporary flight level change to avoid an imminent collision risk:
ALL STATIONS (call sign) LEAVING FLIGHT LEVEL (number) NOW FOR FLIGHT LEVEL (number) followed as soon as practicable by: ALL STATIONS (call sign) RETURNING TO FLIGHT LEVEL (number) NOW
TIBA broadcasts should not be acknowledged unless a potential collision risk is perceived.
If, on receipt of a traffic information broadcast from another aircraft, a pilot decides that immediate action is necessary to avoid an imminent collision risk, and this cannot be achieved in accordance with the right-of-way provisions of Annex 2 to the Chicago Convention, the pilot should:
unless an alternative manoeuvre appears more appropriate, immediately descend 150 m (500 ft), or 300 m (1 000 ft) if above FL 290 in an area where a vertical separation minimum of 600 m (2 000 ft) is applied:
display all available aircraft lighting which would improve the visual detection of the aircraft;
as soon as possible, reply to the broadcast advising action being taken;
notify the action taken on the appropriate ATS frequency and
as soon as practicable, resume normal flight level, notifying the action on the appropriate ATS frequency.
When implementing TIBA procedures, pilots shall operate aircraft transponders on Mode A and C at all time. In the absence of alternative instructions from the appropriate ATS unit, aircraft not assigned a discrete code should squawk code 3300.
Unless otherwise directed by an appropriate authority, pilots should operate TCAS in TA/RA Mode at maximum range setting during the cruise phase of flight and at a range setting appropriate to the traffic situation when in the departure or terminal phases of flight.
Specific aircraft may need to be involved in special operations during the period when a FIR is an activated contingency zone. These aircraft may therefore be unable to utilize the contingency route structure for a significant period of their flights, Aircraft that will be classified as special operations are as follows:
Special operations of State aircraft
Aircraft in emergency situations or operating with significant reduction in operating efficiency
Mercy flights and aircraft engaged in search and rescue, medical evacuation, and
coastal surveillance operations.
This procedure shall be included in AIP Supplements or NOTAM on TIBA procedures and will be cancelled by NOTAM.