**INTERNATIONAL CIVIL AVIATION ORGANIZATION**

**ASIA AND PACIFIC OFFICE**

![](media/image1.wmf)

**REPORT OF THE SIXTH MEETING OF THE ICAO**

**REDUCED VERTICAL SEPARATION MINIMUM IMPLEMENTATION**

**TASK FORCE (RVSM/TF/6)**

SINGAPORE, 10-14 APRIL 2000

+-----------------------------------------------------------------------+
| The views expressed in this Report should be taken as those of the    |
|                                                                       |
| Task Force and not the Organization                                   |
+-----------------------------------------------------------------------+

Published by the ICAO Asia/Pacific Regional Office, Bangkok

Page

**History of the Meeting**

Introduction i

Attendance i

Officers and Secretariat i

Documentation and Working Language i

#### **Summary Report of the Meeting**

Agenda Item 1: Adoption of Agenda 1

Agenda Item 2: Operational Considerations 1

Agenda Item 3: Issues Relating to Airworthiness and Operation of
Aircraft 3

Agenda Item 4: Safety and Airspace Monitoring Considerations 5

Agenda Item 5: Implementation Management Considerations 7

Agenda Item 6: Review of Action Items 7

Agenda Item 7: Future Work -- Meeting Schedule 8

Agenda Item 8: Other Business 8

#### **Appendices**

Appendix A: Terms of Reference of the ICAO RVSM Implementation TF A-1

Appendix B: Terms of Reference of the ICAO RVSM TF Work Groups B-1

Appendix C: Agenda C-1

Appendix D: List of Participants D-1

Appendix E: Proposed Revisions to Doc 7030 -- Contingency Procedures E-1

Appendix F: Sample RVSM AIP Supplement F-1

Appendix G: Sample 12-18 Month Advance RVSM Implementation NOTAM G-1

Appendix H: Asia/Pacific Region RVSM Implementation Plans Status Report
H-1

Appendix I: Task List I-1

Appendix J: List of Papers J-1

Appendix K Large Altitude Deviation Report Form K-1

Appendix L: Duties and Responsibilities of the APARMO L-1

1.1 **Introduction**

1.1.1 The Sixth Reduced Vertical Separation Minimum Implementation Task
Force Meeting (RVSM/TF/6) was hosted by the Civil Aviation Authority of
Singapore and was held at the Singapore Aviation Academy from 10-14
April 2000.

1.1.2 The meeting reviewed and updated the Terms of Reference for the
Task Force and these are contained in Appendix A.

2.  **Attendance**

1.2.1 Fifty-seven participants attended the meeting from China, Hong
Kong China, Indonesia, Japan, Malaysia, Papua New Guinea, Philippines,
Republic of Korea, Sri Lanka, Singapore, Thailand, United States, Viet
Nam, IATA, IFATCA, ARINC and industry groups. A complete list of
participants is in Appendix D.

1.3 **Officers and Secretariat**

1.3.1 Ms. Leslie McCormick, International Program Officer, Federal
Aviation Administration, United States served as Chairperson of the Task
Force. Mr. Owen Dell, Regional Officer/Air Traffic Management from the
ICAO Regional Office, Bangkok served as the Secretary for the meeting.

1.3.2 Mr. Roy Grimes, CNS Specialist, Federal Aviation Administration,
United States served as Chairperson of the Aircraft Operations &
Airworthiness Working Group. Mr. Sydney Maniam, Senior ATC Manager
(Standards), Civil Aviation Authority of Singapore served as Chairperson
of the ATC Operations Working Group and Mr. Brian Colamosca, Manager,
NAS & International Airspace Analysis Branch, Federal Aviation
Administration Technical Center, United States served as Chairperson of
the Safety & Airspace Monitoring Working Group.

1.4 **Documentation and Working Language**

1.4.1 The working language of the meeting as well as all documentation
was in English.

1.4.2 Twelve Working Papers and four Information Papers were presented
to the meeting.

**Agenda Item 1: Adoption of Agenda**

1.1 The meeting reviewed the provisional agenda presented by the
Secretariat and adopted it as the agenda for the meeting. This agenda is
in Appendix C to the report.

**Agenda Item 2: Operational Considerations**

> **[Operational Implementation]{.underline}**

2.1 The Meeting reviewed the principles for the planning and
implementation of RVSM, as proposed by Singapore in WP10, with regard to
the application of the Flight Level Orientation Scheme, usable band of
RVSM levels, exclusion of non-approved aircraft and special provisions
for State and ferry/maintenance aircraft. The Meeting outlined a
provisional plan for the implementation of RVSM in the South China Sea
area. States were requested to indicate their initial operational
requirements and the target date of implementation. States would review
the plan, in consultation with their respective operators, for further
discussion at the next Task Force Meeting.

+-----------+--------+--------------------------+-------+------------+
| *         | **     | **Flight Level           | *     | **Phased   |
| *Flight** | Flight | Orientation Scheme       | *Excl | Implem     |
|           | Le     | (FLOS) (single alternate | usive | entation** |
| **Info    | vels** | / double alternate)**    | Airsp |            |
| rmation** |        |                          | ace** |            |
|           |        |                          |       |            |
| *         |        |                          |       |            |
| *Region** |        |                          |       |            |
+-----------+--------+--------------------------+-------+------------+
| Bangkok   | TBD    | Single alternate         | TBD   | 21 Feb     |
|           |        |                          |       | 2002       |
+-----------+--------+--------------------------+-------+------------+
| Hanoi     | 3      | Single alternate         | Yes   | TBD        |
|           | 50-390 |                          |       |            |
+-----------+--------+--------------------------+-------+------------+
| Ho Chi    | TBD    | Single alternate         | Yes   | TBD        |
| Minh      |        |                          |       |            |
+-----------+--------+--------------------------+-------+------------+
| Hong Kong | 2      | TBD                      | TBD   | 21 Feb     |
|           | 90-410 |                          |       | 2002       |
+-----------+--------+--------------------------+-------+------------+
| Jakarta   | 350-3  | Single alternate         | Yes   | 21 Feb     |
|           | 90[^1] |                          |       | 2002       |
|           |        |                          |       |            |
|           | 3      |                          |       |            |
|           | 10-390 |                          |       |            |
|           |        |                          |       |            |
|           | 2      |                          |       |            |
|           | 90-410 |                          |       |            |
+-----------+--------+--------------------------+-------+------------+
| Kota      | TBD    | Single alternate         | No    | 21 Feb     |
| Kinabalu  |        |                          |       | 2002       |
+-----------+--------+--------------------------+-------+------------+
| Kuala     | 3      | Single alternate         | Yes   | 21 Feb     |
| Lumpur    | 10-410 |                          |       | 2002       |
+-----------+--------+--------------------------+-------+------------+
| Manila    | 3      | Single alternate         | Yes   | 21 Feb     |
|           | 10-410 |                          |       | 2002       |
+-----------+--------+--------------------------+-------+------------+
| Naha      | 2      | Single alternate         | Yes   | Yes[^2]    |
| (Pacific  | 90-390 |                          |       |            |
| Oceanic)  |        |                          |       |            |
+-----------+--------+--------------------------+-------+------------+
| P         | TBD    | Single alternate         | TBD   | 21 Feb     |
| hnom-Penh |        |                          |       | 2002       |
+-----------+--------+--------------------------+-------+------------+
| Singapore | 3      | Single alternate         | Yes   | 21 Feb     |
|           | 10-410 |                          |       | 2002       |
+-----------+--------+--------------------------+-------+------------+
| Taegu     |        |                          |       |            |
+-----------+--------+--------------------------+-------+------------+
| Taipei    |        |                          |       |            |
+-----------+--------+--------------------------+-------+------------+
| Ujung     | 350-3  | Single alternate         | Yes   | 21 Feb     |
| Pandang   | 90[^3] |                          |       | 2002       |
|           |        |                          |       |            |
|           | 3      |                          |       |            |
|           | 10-390 |                          |       |            |
|           |        |                          |       |            |
|           | 2      |                          |       |            |
|           | 90-410 |                          |       |            |
+-----------+--------+--------------------------+-------+------------+
| Vientiane | TBD    | Single alternate on ATS  | TBD   | 21 Feb     |
|           |        | route A1                 |       | 2002       |
+-----------+--------+--------------------------+-------+------------+
| **Note:** |        |                          |       |            |
| "E        |        |                          |       |            |
| xclusive" |        |                          |       |            |
| means     |        |                          |       |            |
| non       |        |                          |       |            |
| -approved |        |                          |       |            |
| aircraft  |        |                          |       |            |
| may NOT   |        |                          |       |            |
| flight    |        |                          |       |            |
| plan into |        |                          |       |            |
| RVSM      |        |                          |       |            |
| a         |        |                          |       |            |
| ltitudes. |        |                          |       |            |
| Aircraft  |        |                          |       |            |
| that have |        |                          |       |            |
| not       |        |                          |       |            |
| received  |        |                          |       |            |
| State     |        |                          |       |            |
| RVSM      |        |                          |       |            |
| approval  |        |                          |       |            |
| may be    |        |                          |       |            |
| cleared   |        |                          |       |            |
| to        |        |                          |       |            |
| operate   |        |                          |       |            |
| in        |        |                          |       |            |
| airspace  |        |                          |       |            |
| where     |        |                          |       |            |
| RVSM may  |        |                          |       |            |
| be        |        |                          |       |            |
| applied   |        |                          |       |            |
| in        |        |                          |       |            |
| a         |        |                          |       |            |
| ccordance |        |                          |       |            |
| with      |        |                          |       |            |
| policy    |        |                          |       |            |
| and       |        |                          |       |            |
| p         |        |                          |       |            |
| rocedures |        |                          |       |            |
| es        |        |                          |       |            |
| tablished |        |                          |       |            |
| by the    |        |                          |       |            |
| ATS       |        |                          |       |            |
| Provider  |        |                          |       |            |
| States    |        |                          |       |            |
| provided  |        |                          |       |            |
| that      |        |                          |       |            |
| 2,000ft   |        |                          |       |            |
| vertical  |        |                          |       |            |
| s         |        |                          |       |            |
| eparation |        |                          |       |            |
| is        |        |                          |       |            |
| applied.  |        |                          |       |            |
| Some      |        |                          |       |            |
| States    |        |                          |       |            |
| may       |        |                          |       |            |
| choose to |        |                          |       |            |
| allow     |        |                          |       |            |
| non-RVSM  |        |                          |       |            |
| State     |        |                          |       |            |
| aircraft  |        |                          |       |            |
| to flight |        |                          |       |            |
| plan into |        |                          |       |            |
| RVSM      |        |                          |       |            |
| airspace. |        |                          |       |            |
+-----------+--------+--------------------------+-------+------------+

**Table 2.1 -- Operational Implementation Plan**

> **[Terms of Reference]{.underline}**

2.2 The meeting reviewed the Terms of Reference for the ATC Operations
Work Group. IATA proposed that the meeting should consider the
harmonisation of plans, when identifying the airspace in which RVSM
would be applied. The meeting agreed that the operational concept for
the implementation of RVSM should be based on the harmonisation of plans
between regions.

2.3 Philippines inquired on the need for procedures to be published to
facilitate the suspension of RVSM operations. The meeting decided that
this would be included as an action item in the RVSM Implementation Plan
Task List.

2.4 The meeting adopted the Terms of Reference for the ATC Operations
Work Group as shown in Appendix B.

**[RVSM Implementation Plan Status Report]{.underline}**

2.5 The meeting reviewed the status of the RVSM Implementation Plan for
the Asia Pacific Region. States present were requested to provide an
initial assessment of their readiness to meet the proposed
implementation date of February 2002 for the South China Sea area. The
meeting requested ICAO to liaise with States who were not present, to
ascertain their future plans with regard to implementing RVSM. The
meeting updated the Asia/Pacific Region RVSM Implementation Plans Status
Report as shown in Appendix H.

2.6 IATA inquired about the extension of RVSM operations to the Bay of
Bengal and beyond, to cater for westbound flights to Europe. The meeting
agreed that it would not be possible to decide on such an extension,
since not all the States involved were present. The meeting requested
ICAO to write to the States concerned, to ascertain their plans for the
implementation of RVSM operations. States who were keen to implement
RVSM would be urged to attend the next Task Force Meeting.

> **[RVSM TF Task List]{.underline}**

2.7 The meeting reviewed the action items, outlined in the task list for
the implementation of RVSM in the Asia Region. IATA proposed that in
addition to the traffic flow in South East Asia, traffic from Asia to
Europe south of the Himalayas should be considered, in the process of
identifying the operational need for RVSM. The meeting agreed that the
operational concept should include the two major traffic flows.

2.8 The meeting updated the action items and adopted the task list shown
in Appendix I for the implementation of RVSM in the Asia Pacific Region.

> **[Guidance Material for the Implementation of RVSM]{.underline}**

2.9 The meeting reviewed the draft Guidance Material for the
implementation of RVSM in the Asia Pacific Region (WP4). The document
would be presented to the APANPIRG ATS/AIS/SAR Sub-Group for adoption
and publication. States were requested to provide their comments or
proposed changes to the Chairperson of the Task Force by 30 May 2000.

> **[Format for AIP Supplement]{.underline}**

2.10 The meeting reviewed the proposed format to be used for AIP
Supplements relating to the implementation of RVSM. States were
requested to consider the basic information and related procedures that
were outlined, in the development of notices for the implementation of
RVSM in the region. The meeting agreed to address this issue in greater
detail at the next Task Force Meeting.

> **[Operations of Non-Approved Aircraft]{.underline}**

2.11 The meeting reviewed the proposed procedures relating to the
approval process for non-approved aircraft to operate in RVSM airspace.
States were requested to consider using the proposed procedures as a
guide in the development of specific procedures for the approval of
non-approved State aircraft, as well as non-approved civil aircraft, to
operate in RVSM airspace. The meeting agreed to review the specific
requirements for each State and the corresponding procedures to allow
non-approved aircraft to operate in RVSM airspace at the next Task Force
Meeting.

> **[90% Operator Approval Requirement]{.underline}**

2.12 The meeting discussed the need for at least 90% of operations to
obtain RVSM approval, before States could proceed to implement RVSM. The
meeting agreed that it was necessary to set a target for the region, to
ensure that RVSM operations could be fully supported. IATA agreed to
provide the status of operator approval in the region. The meeting
decided to review the approval status at the next Task Force Meeting,
before setting the target for the region.

> **[ICAO Doc 7030]{.underline}**

2.13 The meeting noted that the amendment to the ICAO Regional
Supplementary Procedures (Doc 7030), paragraph 6.5 (Vertical Separation)
to identify the FIRs where RVSM will be implemented, would be proposed
in early 2001 to facilitate the implementation of RVSM operations in the
South China Sea area in February 2002.

**[Suspension of RVSM Operations]{.underline}**

2.14 Philippines inquired whether there were procedures in place to
cater for the suspension of RVSM operations due to prolonged adverse
weather conditions. The meeting agreed that the existing contingency
procedures for RVSM operations could be applied. However, States
recognised that more work should be done to address the issue in greater
detail and include the procedures in the respective Letters of
Agreement. To this end, the Task Force Chairperson agreed to provide the
documentation currently used by Pacific ATS Providers for discussion at
the next Task Force Meeting.

2.15 The meeting agreed that there was a need for accurate
meteorological information to be provided to ensure that RVSM operations
would not be suspended unnecessarily. This matter will be discussed in
more detail at the next Task Force Meeting.

> **[Controller Involvement]{.underline}**

2.16 IFATCA requested that operational controllers be involved in the
planning and implementation of RVSM operations in the region. The
meeting acknowledged that it would be beneficial for controllers to
participate actively in the Task Force meetings. However, the selection
of personnel for such meetings would be left to individual States.
States agreed to raise the issue with their respective authorities.

**Agenda Item 3: Issues Relating to Airworthiness and Operation of
Aircraft**

**[RVSM Documentation and Web Site Information]{.underline}**

3.1 The meeting reviewed the published documentation and web site
information \<http:www.faa.gov/rvsm\> related to airworthiness and
aircraft operations. The meeting agreed to change all documentation to
reflect application to the Asia Pacific region instead of the Pacific
region. The meeting also agreed to make specific changes to a number of
documents.

3.2 **[Asia Pacific RVSM TF: Document Revisions]{.underline}**

a)  Documents and Process: Pacific RVSM Aircraft and Operator Approval:
    Revise title and all area references to "Asia Pacific" and add
    references to State AIPs and NOTAMs;

b)  Web site RVSM Documentation section: add section for new RVSM FIR's,
    as needed;

c)  ICAO Regional Supplementary Procedures (Doc 7030) updates:

> A. Paragraph 6.5 (Vertical Separation):
>
> \(1\) Para 6.5.1: add FIR's where RVSM to be applied;
>
> \(2\) Para 6.5.5: provide for more general application of wake
> turbulence offset procedures to other events such as multiple TCAS
> TA's and Ground Proximity Warning events. Propose to change the
> paragraph heading to read: Special procedures to mitigate wake
> turbulence encounters or distracting multiple aircraft system alerts
> (e.g. ACAS, GPWS)
>
> B. Paragraph 4.0 (Special Procedures for In-flight Contingencies):
> update paragraphs related to pilot actions when deviating without a
> clearance, controller actions when clearance not available and
> climb/descent table. (The meeting agreed to propose the use of a 300ft
> climb or descent for contingency purposes.) The meeting is also
> reviewing the contingency procedures developed for application in
> European domestic airspace to determine if they can be applied in
> domestic airspace in the Asia Pacific region. (See Appendix E)

d)  ICAO Guidance Material on the Implementation of RVSM in the Airspace
    of the Asia Pacific Region: review for updates. The deadline for the
    submittal of revisions to APANPIRG is June 2000.

e)  Example Operator Application for Authority: update to show necessity
    to comply with policy/procedures published in NOTAMS and AIP's.

f)  Interim Guidance 91-RVSM: review Appendix 4 (Training Programs and
    Operating Practices and Procedures) and Appendix 5 (Specific
    Procedures for Oceanic Airspace) to determine if updates are
    necessary. Coordinate application of Appendix 5 with ATC/WG;

g)  Pacific RVSM Operational Policy/Procedures Revision. IP2 (Suggested
    Format for the RVSM Implementation AIP Supplement). A similar
    document will need to be developed for the Asia Pacific FIR's. All
    the policies contained in the draft document will need to be
    reviewed for applicability to the Asia Pacific FIRs. Coordinate
    revisions with the ATC Operations Group. (See Appendix F);

h)  Pacific RVSM Minimum Monitoring Requirements: re-title and update,
    as necessary, to show Asia Pacific monitoring requirements;

i)  Training Considerations for Using TCAS Version 6.04 in RVSM
    Airspace: FAA updating to include considerations for Change 7;

j)  12 to 18 Month Advance NOTAM/AIP: Publish, as soon as possible, the
    target date and airspace designated for implementation, in order for
    operators to plan aircraft engineering programs (see Appendix G,
    SAMPLE ADVANCE NOTAM);

k)  Aeronautical Chart Panels Containing Contingency Procedures: The
    OPS/AIR/WG Chairperson agreed to contact the chart publishers to
    recommend that more complete information be included on the chart
    panels. He will request support from the user community, as
    necessary.

3.3 **[General Tasks/Projects]{.underline}**

a)  Information dissemination: OPS/AIR/WG Chairman to contact editor of
    "Asian Aviation" (Barry Grindrod), the Association of Asia Pacific
    Airlines and regional representatives of business aviation to
    provide them with current information and invite them to future
    meetings;

b)  Monitoring: Identify operator/aircraft population and determine if
    monitoring assets are adequate;

c)  Policy for Suspension of RVSM due to Turbulence: Review current
    guidance published in ICAO RVSM Guidance Material and draft RVSM AIP
    Supplement (IP2: Suggested Format for the RVSM Implementation AIP
    Supplement), to determine if more specific wording is needed for the
    Asia-Pacific region;

d)  Continue to emphasize measures to mitigate pilots leveling at the
    incorrect flight level (see IP2 paragraph 4.4);

e)  Emphasize role of the OPS/AIR/WG in reviewing operational errors and
    identifying causes and recommended measures to prevent the
    reoccurrence of such errors;

f)  Strategic Lateral Offsets: Track development of strategic lateral
    offsets in RGCSP and establish an implementation program in Asia
    Pacific airspace, as necessary;

g)  Policy for Follow-On Monitoring: Track progress in meeting the goal
    of a census of all Pacific airframes in two years and track the
    results of repeat observations of individual airframes and
    operators.

## 

## 

## Agenda Item 4: Safety and Airspace Monitoring Considerations

4.1 The meeting considered WP/6 under this topic.

#### **[Safety & Airspace Monitoring Group Terms Of Reference]{.underline}**

4.2 The meeting considered the existing Terms of Reference for the
Safety and Airspace Monitoring Working Group (SAM/WG). It was observed
that the Terms of Reference should be updated to reflect the Task
Force\'s focus on introduction of the RVSM within airspace beyond its
original concentration. It was agreed that this expanded geographical
focus would best be reflected by changing current references to
\"Pacific\" RVSM to \"Asia Pacific Region.\" The meeting agreed to this
change and to other modifications to the Terms of Reference, with the
agreed text shown in Appendix B to this report.

#### **[Asia/Pacific Approvals Registry & Monitoring Organization]{.underline}**

4.3 The meeting reviewed the existing terms of reference of the
Asia/Pacific Approvals Registry and Monitoring Organization (APARMO) as
adopted by the Asia Pacific Air Navigation Planning and Implementation
Regional Group (APANPIRG). As with the SAM/WG Terms of Reference, the
Task Force agreed that the text should be modified to reflect interest
in the expanded introduction of the RVSM by substituting \"Asia Pacific
Region\" for \"Pacific.\" The agreed changes are reflected in the
modified APARMO Terms of Reference shown in Appendix L to this report.

4.4 The meeting noted with satisfaction that there are now over 4800
individual airframes in the APARMO database of State-RVSM-approved
aircraft, with more than 800 of these approved specifically in
connection with the recently implemented Pacific RVSM. In light of
planned January 2002 implementation of the RVSM in Continental European
airspace, the meeting also expressed satisfaction with the report that
the APARMO and EUROCONTROL will be sharing information on State
approvals in the near future.

4.5 It was agreed that, once information is available to identify
aircraft and operators likely to use the airspace where further Asia
Pacific Region RVSM implementation will take place, the APARMO should
review its listing of State authorities responsible for RVSM approvals
in order to identify those States for which contacts need to be
established. The meeting called on the APARMO to carry out this
assessment as soon as possible and to take steps to establish such
contacts.

4.6 The meeting recalled its adoption of monitoring requirements in
connection with application of the State approval process for Pacific
RVSM implementation. It was agreed that these requirements should also
be carried over to implementation of the RVSM in other portions of the
Asia Pacific Region, with review of the requirements to be an ongoing
task of its SAM/WG and OPS/AIR/WG.

4.7 The meeting was informed that the APARMO had obtained EUROCONTROL
forecasts of traffic likely to be monitored by the height monitoring
unit (HMU) being established near Linz, Austria in connection with
Continental European RVSM introduction. The meeting noted that this
information, and sharing of monitoring results by EUROCONTROL, would be
necessary, since the forecast indictes that a number of Asia Pacific
Region operators and aircraft would be monitored by the Linz HMU,
thereby contributing to satisfaction of monitoring requirements
associated with Asia Pacific Region RVSM implementation.

> **[Need For Information Describing Characteristics Of The Airspace
> Within Which Further Asia Pacific Region RVSM Implementation Will Take
> Place]{.underline}**

4.8 The meeting noted that several important tasks needed to be
completed by the SAM/WG and the APARMO prior to its next meeting.
Principal among these were seen to be the need for a preliminary
assessment of the benefits and costs associated with further RVSM
implementation within the Region and an early analysis of the proportion
of operations already being conducted by operators and aircraft with
State RVSM approval.

4.9 In order to complete these tasks, it was agreed that the SAM/WG and
the APARMO would require traffic data and operational characteristics of
the airspace. Accordingly, the meeting directed the APARMO to coordinate
with ATC providers in the Region, as identified by the chair of the
ATC/WG, soon after the close of the meeting for purposes of obtaining a
one-month sample of traffic movements from the airspace provisionally
identified by that Working Group for RVSM implementation. The meeting
agreed that the details of such coordination should be left to the
ATC/WG Chairperson and the APARMO.

###### **[Readiness & Safety Assessments]{.underline}**

4.10 The meeting agreed that the SAM/WG would be required to carry out
two principal tasks in connection with RVSM implementation: (1) an
assessment of the readiness of operators and aircraft, as reflected in
the proportion of operations which would be conducted by State-approved
operators and aircraft in the airspace where RVSM will be introduced and
(2) an assessment of the safety of RVSM implementation.

4.11 It was noted that, in light of Pacific RVSM implementation
experience, it would not be possible to conduct a readiness assessment
until the date for RVSM implementation was more proximate.

4.12 The meeting recalled the importance of information concerning large
height deviations in conducting a comprehensive safety assessment. The
meeting also recalled that the ICAO Asia and Pacific Regional Office
issued State Letter T 3/10.1.7 - AP - ATM0586 on 23 September 1998,
which requested that States, operators and flight crews report instances
of large height deviations within Pacific airspace where the RVSM would
be applied. A companion International NOTAM requested the same
information. Both documents contained as an attachment a form,
reproduced as Appendix K to this report, which details the information
required and specifies the APARMO as its recipient.

4.13 The meeting agreed that the ICAO Asia and Pacific Region Office
should take steps at the earliest opportunity to issue a similar State
Letter in connection with further RVSM implementation in the Asia
Pacific Region.

## Agenda Item 5: Implementation Management Considerations

### 

**[Task Force Work Groups]{.underline}**

5.1 The meeting continued with the decision that in order to accomplish
the tasks in the action plan, the Task Force should be divided into
smaller work groups. The following Work Groups continued their work:

a)  Safety & Airspace Monitoring;

b)  ATC Operations; and

c)  Aircraft Operations & Airworthiness

5.2 The terms of reference of the Work Groups were reviewed and updated
and are in Appendix B to the report and the discussion from these groups
is contained under Agenda Items 2, 3 and 4.

**Agenda Item 6: Review of Action Items**

6.1 The meeting developed an RVSM Implementation Plan Task List. The
Task List is in Appendix I to the report.

## Agenda Item 7: Future Work -- Meeting Schedule

7.1 The meeting agreed on the following schedule of Task Force meetings:

> RVSM TF/7: 17-18 April 2000 in Honolulu (Pacific Review focus)
>
> RVSM TF/8: 28 August -- 1 September 2000 location TBA (Asia focus)
>
> RVSM TF/9: 4 days January 2001 location TBA (Asia focus)
>
> RVSM TF/10 3 days February 2001 in Auckland (Pacific Review focus)
>
> RVSM Seminar/4: 2 days February 2001 location TBA (Asia focus)
>
> RVSM TF/11: 3 days May 2001 location TBA (Asia focus)
>
> RVSM TF/12: 3 days August 2001 location TBA (Asia focus)
>
> RVSM TF/13: 2 days December 2001 location TBA (Asia focus)
>
> (Target Implementation Western Pacific/South China Sea AIRAC date 21
> February 2002)

**[RVSM Implementation Status]{.underline}**

### 

### 7.2 The meeting reviewed the Asia Pacific Region RVSM Implementation Status Report, based on information available from the States in attendance at the meeting. The Status Report is at Appendix H and will continue to be updated at future meetings of the Task Force. 

### 

### 

## Agenda Item 8: Other Business

1.  No other business was identified.

The terms of reference for the RVSM Implementation Task Force are as
follows:

-   To develop strategic, benefits-driven implementation plans (based on
    cost benefit studies), in concert with airspace users, for RVSM
    operations within selected areas and airspace of the Asia Pacific
    Region, ensuring inter-regional harmonisation;

-   To consider any amendments to RVSM guidance material that may be
    proposed by States and international organizations;

-   To address any other matters as appropriate and relevant to the
    implementation of RVSM; and

-   The Task Force will include participation from States and
    International Organizations that are considering or involved with
    the implementation of RVSM.

-   The Task Force will report to the ATS/AIS/SAR Sub-Group.

. . . . . .

The Terms of Reference of the RVSM Implementation Task Force Work Groups
are as follows:

**[Safety & Airspace Monitoring Work Group (SAM/WG)]{.underline}**

The SAM/WG is responsible for mathematical and statistical analysis to
assist with the maintenance and on-going monitoring of safety through
the assessment of collision risk for Asia Pacific Region RVSM and other
tasks as agreed with the RVSM Task Force. The main tasks of the SAM/WG
are:

-   To develop a monitoring program to ensure that the quantity and
    quality of data are collected to allow an assessment of vertical
    collision risk;

-   To review existing mathematical and statistical techniques to assure
    their appropriateness for Asia Pacific Region RVSM;

-   To ensure the transferability of aircraft data collected from other
    airspace regions;

-   To support the assessment of the safety of RVSM prior to and during
    the Verification and Operational Trials by the production of
    collision risk assessments based on height deviation incidents and
    height monitoring data to determine whether the TLS is being met;

-   To devise suitable methodologies for incorporating the effects of
    projected traffic increases and system changes on occupancy and
    collision risk in the future environment;

-   To identify those elements which are critical in the assessment of
    collision risk and suggest areas where improvements might be
    effective in reducing risk;

-   To establish a policy for investigating those errors that may
    jeopardise satisfaction of the Target Level of Safety (TLS);

-   To estimate periodically the vertical occupancies (traffic
    densities, passing frequencies, etc.) in the Asia Pacific Region;
    and

-   To perform periodically other data collections (e.g. ASE stability)
    in order to ensure that the parameter values used in the
    mathematical collision risk models remain current.

> **[ATC Operations Work Group (ATC/WG)]{.underline}**

The ATC/WG is responsible for addressing all matters relating to air
traffic services within the RVSM and transition airspace, to include the
following:

-   To identify airspace in which RVSM will be applied based on
    statement of application and develop a regional operational concept,
    ensuring inter-regional harmonisation;

-   To develop procedures to mitigate wake turbulence;

-   To establish transition areas and develop transition procedures;

```{=html}
<!-- -->
```
-   To develop contingency procedures; and

```{=html}
<!-- -->
```
-   To consider workload issues and identify the need for controller
    simulations.

> **[Aircraft Operations & Airworthiness Work Group
> (OPS/AIR/WG)]{.underline}**

The OPS/AIR/WG is responsible for addressing pilot operations,
airworthiness, and aircraft approval issues, and:

-   To harmonize policy on operations and airworthiness issues related
    to RVSM;

-   To develop and harmonize guidance related to the implementation of
    RVSM and coordinate on issues which may arise in the application of
    the RVSM Minimum Aircraft System Performance Specifications (MASPS);

-   To initiate necessary action to amend aeronautical charts to reflect
    navigational requirements related to RVSM;

-   To develop policy for use of Airborne Collision Avoidance Systems
    (ACAS) as it relates to RVSM; and

-   To review monitoring data prior to implementation and after
    implementation.

**INTERNATIONAL CIVIL AVIATION ORGANIZATION**

**ASIA AND PACIFIC OFFICE**

**SIXTH MEETING OF THE ICAO RVSM IMPLEMENTATION TASK FORCE**

**(RVSM/TF/6)**

(Singapore, 10-14 April 2000)

**AGENDA**

Agenda Item 1: Adoption of Agenda

Agenda Item 2: Operational Considerations

Agenda Item 3: Issues Relating to Airworthiness and Operation of
Aircraft

Agenda Item 4: Safety and Airspace Monitoring Considerations

Agenda Item 5: Implementation Management Considerations

Agenda Item 6: Review of Action Items

Agenda Item 7: Future Work -- Meeting Schedule

Agenda Item 8: Other Business

Appendix D List of Participants---separate file

7030Para4.doc. REV 0: 4 APRIL 00

***[DRAFT]{.underline}***

**[*PROPOSED UPDATES TO* ICAO PACIFIC & MID-ASIA]{.underline}**

**[REGIONAL SUPPLEMENTARY (DOC 7030) PROCEDURES]{.underline}**

NOTE: PROPOSED WORD CHANGES ARE IN BOLD AND ITALICS.

**4.0 SPECIAL PROCEDURES FOR IN-FLIGHT CONTINGENCIES.**

**4.1 General Procedures**

4.1.1 The following general procedures apply to both subsonic and
supersonic aircraft and are intended for guidance only. Although all
possible contingencies cannot be covered, they provide for cases of
inability to maintain assigned level due to weather, aircraft
performance, pressurization failure and problems associated with
high-level supersonic flight. They are applicable primarily when rapid
descent and/or turn-back or diversion to an alternate airport are
required. The pilot's judgment shall determine the sequence of actions
taken, taking into account specific circumstances.

4.1.2 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.

***4.1.3 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:***

> ***a) broadcast, at suitable intervals, flight identification, flight
> level, aircraft position, (including the ATS route designator or the
> track code, as appropriate) and intentions on the frequency in use, as
> well as on frequency 121.5 MHz (or, as a back-up, the VHF inter-pilot
> air-to-air frequency );***
>
> ***b) watch for conflicting traffic both visually and by reference to
> ACAS (if equipped); and***
>
> ***c) turn on aircraft exterior lights.***

**4.2 Special Procedures for subsonic aircraft requiring rapid descent
and/or turn-back or diversion to an alternate airport due to aircraft
system malfunction or other contingencies**

1.  Initial action

4.2.1.1 If unable to comply with the provisions of 4.1.2 to obtain a
revised ATC clearance, the aircraft should leave its assigned route or
track by turning 90 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 organized route or track system, e.g. 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.

4.2.2 Subsequent action

4.2.2.1 AIRCRAFT ABLE TO MAINTAIN LEVEL. An aircraft able to maintain
its assigned level should acquire and maintain in either direction a
track laterally separated by 25 NM from its assigned route or track and
once established on the offset track, climb or descend 500 ft (150 m).

4.2.2.2 AIRCRAFT UNABLE TO MAINTAIN LEVEL. An aircraft NOT able to
maintain its assigned level should, whenever possible, **minimize its
rate of descent** while turning to acquire and maintain in either
direction a track laterally separated by

25 NM from its assigned route or track. For subsequent level flight, a
level should be selected which differs by 500 ft (150 m) from those
normally used.

4.2.2.3 DIVERSION ACROSS THE FLOW OF ADJACENT TRAFFIC. Before commencing
a diversion across the flow of adjacent traffic, the aircraft should,
while maintaining the 25 NM offset, expedite climb above or descent
below levels where the majority of Pacific oceanic traffic operate
(e.g., to a level above FL 400 or below

FL 290) and then maintain a level which differs by 500 ft (150 m) 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 500 ft (150 m) above or below levels normally used until a new ATC
clearance is obtained.

4.2.2.4 EXTENDED RANGE OPERATIONS BY TWO-TURBINE POWER UNITS (ETOPS)
AIRCRAFT. 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.

**4.3 Weather deviation procedures for oceanic-controlled airspace**

4.3.1 General

4.3.1.1 The following procedures are intended to provide guidance. All
possible circumstances cannot be covered. The pilot's judgment shall
ultimately determine the sequence of actions taken and ATC shall render
all possible assistance.

***4.3.1.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
4.3.4 below.***

4.3.1.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 center line of its cleared route.

4.3.2 Obtaining priority from ATC when weather deviation is required

4.3.2.1 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.

4.3.2.2 The pilot still retains the option of initiating the
communications using the urgency call "PAN PAN" three times to alert all
listening parties to a special handling condition which will receive ATC
priority for issuance of a clearance or assistance.

4.3.3 Actions to be taken when controller-pilot communications are
established

a)  Pilot notifies ATC and requests clearance to deviate from track,
    advising, when possible, the extent of the deviation expected.

b)  ATC takes one of the following actions:

```{=html}
<!-- -->
```
1)  if there is no conflicting traffic in the horizontal dimension, ATC
    will issue clearance to deviate from track; or

2)  if there is conflicting traffic in the horizontal dimension, ATC
    separates aircraft by establishing vertical separation ; or

> 3\) if there is conflicting traffic in the horizontal dimension and
> ATC is unable to establish vertical separation, ATC shall:

i)  ***advise the pilot unable to issue clearance for requested
    deviation***

ii) ***advise pilot of conflicting traffic***

    ***iii) request pilot's intentions***

> ***SAMPLE PHRASEOLOGY:***
>
> ***"Unable (requested deviation), traffic is (call sign, position,
> altitude, direction), advise intentions."***
>
> c\) Pilot will take the following actions:

1)  ***Advise ATC of intentions to...***

2)  ***Comply with air traffic control clearance issued or...***

3)  ***To execute the procedures detailed in 4.3.4.1 below. (ATC will
    issue essential traffic information to all affected aircraft).***

4)  ***If necessary, establish voice communications with ATC to expedite
    dialogue on the situation***

4.3.4 Actions to be taken if controller-pilot communications not
established or revised air traffic control clearance not available

4.3.4.1 If contact cannot be established or revised air traffic control
clearance is not available and deviation from track is required to avoid
weather, the pilot shall take the following actions:

a)  if possible, deviate away from an organized track or route system;

> b\) ***broadcast, 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.5 MHz
> (or, as a back-up, the VHF inter-pilot air-to-air).***

c\) watch for conflicting traffic both visually and by reference to ACAS
(if equipped);

> d\) turn on aircraft exterior lights;
>
> e\) for deviations of less than 10 NM or operations within the
> ??***CENTRAL EAST PACIFIC??,*** aircraft should remain at a level
> assigned by ATC;
>
> f\) ***for deviations of more than 10NM and operations not in the
> Central East Pacific,*** when the aircraft is approximately 10 NM from
> track, initiate a level change based on the following criteria:

+-----------------------+-----------------------+-----------------------+
| Route centre line     | Deviations \>10 NM    | Level change          |
| track                 |                       |                       |
+-----------------------+-----------------------+-----------------------+
| EAST                  | LEFT                  | DESCEND ??? ft        |
|                       |                       |                       |
| 000-179 magnetic      | RIGHT                 | CLIMB ??? ft          |
+-----------------------+-----------------------+-----------------------+
| WEST                  | LEFT                  | CLIMB ??? ft          |
|                       |                       |                       |
| 180-359 magnetic      | RIGHT                 | DESCEND ??? ft        |
+-----------------------+-----------------------+-----------------------+

g\) when returning to track, be at its assigned level, when the aircraft
is within approximately 10 NM of centre line; and

> h\) 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.

# XX/2000

***Pacific Ocean RVSM implementation***

***Effective: 24 February 2000, 0700Z***

## 1.0 Introduction

1.1 The International Civil Aviation Organization (ICAO) Third Asia/
Pacific Regional Air Navigation meeting recommended that Reduced
Vertical Separation Minimum (RVSM) should be introduced in the Pacific
region after successful implementation in the North Atlantic region.
This is also due to the significant benefits to be gained by aircraft
operators and air traffic services (ATS) providers. ICAO Document 9574,
*Manual on Implementation of a 300 m \[1 000 ft\] Vertical Separation
Minimum Between FL 290 and FL 410 Inclusive* contains an explanation of
RVSM.

1.2 Benefits to be gained from RVSM include:

a)  adoption of an ICAO endorsed navigation requirement;

b)  improved utilization of airspace for ATC conflict resolution; and

c)  fuel savings of ≈ 1% for flight closer to optimum cruise altitude.

## 2. Application of RVSM airspace

2.1. Australia, Fiji, New Zealand, Tahiti, the United States, Japan, and
Papua New Guinea will simultaneously implement RVSM within specified
areas of their Flight Information Regions (FIR).

2.2 Effective 0700, 24 February 2000 UTC, RVSM airspace is prescribed
within the XXXXX FIR within controlled airspace between FL XXX and FL
XXX inclusive. The flight level orientation scheme (FLOS) is single
alternate, per ICAO Annex 2, Appendix 3a.

## 3.0 Airworthiness and Operational Approval and Monitoring

3.1 Operators must obtain operational and airworthiness approval from
the State of Registry of the aircraft or of the aircraft operator, as
appropriate, to conduct RVSM operations. On behalf of the Pacific Air
Traffic Service Providers, the FAA is maintaining a website containing
documents and policy for RVSM approval. Address is:
www.faa.gov/ats/ato/rvsm1.htm. In the Pacific RVSM Documentation
section, "Documents and Process for Pacific RVSM Aircraft and Operator
Approval" provides an outline of approval process events with references
to related documents.

3.2 If TCAS is installed in RVSM compliant aircraft, the equipment
should be updated to Change 7, or a later approved version, for optimum
performance in RVSM airspace.

3.3 An essential part of the implementation of RVSM is the ability to
monitor aircraft height to ensure that the aircraft height-keeping
performance standard is being met. The Asia Pacific Approvals Registry
and Monitoring Organization (APARMO) will process the results of
monitoring. For further information on RVSM monitoring the APARMO web
site is: http://www.tc.faa.gov/act500/rvsm/aparmo_intro.html

## 4.0 In-flight procedures within RVSM airspace

4.1 Before entering RVSM airspace, the pilot should review the status of
required equipment. (See Appendix 4 of FAA Interim Guidance 91-RVSM (or
appropriate State documentation) for pilot RVSM procedures). The
following equipment should be operating normally:

a)  two primary altimetry systems:

b)  one automatic altitude-keeping device; and

c)  one altitude-alerting device.

4.2 The pilot must notify ATC whenever the aircraft:

a)  is no longer RVSM compliant due to equipment failure; or

b)  experiences loss of redundancy of altimetry systems; or

c)  encounters turbulence that affects the capability to maintain flight
    level.

(See Appendix 5 of FAA Interim Guidance 91-RVSM (or appropriate State
documentation) for pilot and controller actions in such contingencies).

## 4.3 During cleared transition between levels, the aircraft should not overshoot or undershoot the assigned FL by more than 150 ft (45 m). 

4.4 Except in an ADS or radar environment, pilots shall report reaching
any altitude assigned within RVM airspace.

###  *General procedures*

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:

a)  weather;

b)  aircraft performance;

c)  pressurization failure; and

d)  problems associated with high-level supersonic flight.

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.

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.

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**:

a)  broadcast, at suitable intervals, flight identification, flight
    level, aircraft position, (including the ATS route designator or the
    track code, as appropriate) and intentions on the frequency in use,
    as well as on frequency 121.5 MHz (or, as a back-up, the VHF
    inter-pilot air-to-air frequency );

b)  watch for conflicting traffic both visually and by reference to
    TCAS/ACAS (if equipped); and

c)  turn on aircraft exterior lights.

## 

## 6.0 Subsonic aircraft requiring rapid descent, turn-back or diversion

###  *Initial action*

6.1 If unable to comply with the provisions of paragraph 5.3 to obtain a
revised ATC clearance, the aircraft should leave its assigned route or
track by turning 90 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*

6\. 2 AIRCRAFT ABLE TO MAINTAIN LEVEL. An aircraft able to maintain its
assigned level should acquire and maintain in either direction a track
laterally separated by 25 NM from its assigned route or track and once
established on the offset track, climb or descend 500 ft (150 m).

6.3 AIRCRAFT UNABLE TO MAINTAIN LEVEL. 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 25 NM from its assigned route or track. For
subsequent level flight, a level should be selected which differs by 500
ft (150 m) from those normally used.

6.4 DIVERSION ACROSS THE FLOW OF ADJACENT TRAFFIC. Before commencing a
diversion across the flow of adjacent traffic, the aircraft should,
while maintaining the 25 NM offset, expedite climb above or descent
below levels where the majority of Pacific oceanic traffic operate (for
example, to a level above FL400 or below FL290) and then maintain a
level which differs by 500 ft (150 m) 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 500 ft above or below
levels normally used until a new ATC clearance is obtained.

6.5 ETOPS AIRCRAFT. 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.

## 7.0 Weather deviation procedures

###  *General procedures*

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.

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 paragaph 7.8 below.

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.

###  *Obtaining ATC priority*

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.

7.5 The pilot still retains the option of initiating the communications
using the urgency call \"PAN PAN PAN\" to alert all listening parties to
a special handling condition which may receive ATC priority for issuance
of a clearance or assistance.

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:

a)  if there is no conflicting traffic in the horizontal dimension, ATC
    will issue clearance to deviate from track; or

b)  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:

> i\) advise the pilot that standard separation cannot be applied;
>
> ii\) provide essential traffic information for all affected aircraft;
> and
>
> iii\) if possible, suggest a course of action. ATC may suggest that
> the pilot:

-   if operating in an airspace where a 2,000 ft vertical separation
    minimum is applied, climb or descend 1, 000 ft from the assigned
    level;

-   if operating in an airspace where a 1,000 ft vertical separation
    minimum is applied, climb or descend 500 ft from the assigned level;
    or

-   if operating in an airspace where composite separation is applied,
    remain at the assigned level.

7.7 The pilot will take the following actions:

a)  comply with any ATC clearance issued; or

b)  maintain a level suggested by ATC when approximately 10 NM from
    track, along with the procedures detailed in paragraph 7.8 a),
    b), c) and d); or

c)  execute the procedures detailed in paragraph 7.8 below. The pilot
    shall immediately inform ATC of intentions and ATC will issue
    essential traffic information to all affected aircraft.

###  *Communications not established or revised ATC clearance not available*

7.8 If contact cannot be established or revised air traffic control
clearance or advisory is not available and deviation from track is
required to avoid weather, the pilot shall take the following actions:

a)  if possible, deviate away from an organised track or route system;

b)  broadcast, 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.5 MHz
    (or, as a back-up, the VHF inter-pilot air-to-air).

c)  watch for conflicting traffic both visually and by reference to
    TCAS/ACAS (if equipped);

d)  turn on aircraft exterior lights;

e)  for deviations of less than 10 NM and when specified for operations
    within certain route systems , aircraft should remain at the level
    assigned by ATC.

f)  when the aircraft is approximately 10 NM from track, initiate a
    level change based on the following criteria:

+-------------------------+---------------------+----------------------+
| ***Route centreline     | ***Deviations\>     | ***Level Change***   |
| track***                | 10 NM***            |                      |
+-------------------------+---------------------+----------------------+
| EAST                    | LEFT                | DESCEND 500 ft       |
|                         |                     |                      |
| 000-179^o^ magnetic     | ### **RIGHT**       | ### **CLIMB 500 ft** |
+-------------------------+---------------------+----------------------+
| WEST                    | LEFT                | CLIMB 500 ft         |
|                         |                     |                      |
| 180-359^o^ magnetic     | ## RIGHT            | DESCEND 500 ft       |
+-------------------------+---------------------+----------------------+

g)  when returning to track, be at its assigned level, when the aircraft
    is within approximately 10 NM of centreline; and

h)  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.

## 8. Wake turbulence

8.1 An aircraft that encounters wake turbulence should notify ATC and
request a revised clearance. However, in situations where a revised
clearance is not possible or practicable:

a)  the pilot should establish contact with other aircraft, if possible,
    on the appropriate VHF inter-pilot air to air frequency; and

b)  one or both aircraft may initiate lateral offset(s) not to exceed 2
    NM from the assigned track, provided that:

> i\) 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; and
>
> ii\) the offsetting aircraft notify ATC when re-established on
> assigned route(s) or track(s).
>
> ***Note**: in this contingency circumstance, ATC will not issue
> clearances for lateral offsets and will not normally respond.*

## 9. Transition areas

9.1 Transition areas from RVSM to non-RVSM airspace within the XXXX
XXXXX FIR XXXXXXXXXXXXX.

## 10. Flight planning

10.1 RVSM approval is required for aircraft to operate within 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 RVSM approved aircraft.

10.2 Non-RVSM civil aircraft may not flight plan between FLXXX and FLXXX
inclusive within RVSM airspace, except non-RVSM civil aircraft unable to
fly to an appropriate destination at or below FLXXX and unable to fly at
or above FLXXX may flight plan at RVSM flight levels in the RVSM stratum
provided the aircraft:

a)  is being initially delivered to the State of Registry or Operator;
    or

b)  was formerly 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

c)  is being utilised for mercy or humanitarian purposes.

10.3 Aircraft operators requesting approval as above shall:

a)  if departing within XXX FIR, obtain approval from the XXX Oceanic
    Control Centre normally not more than 12 hrs and not less than 4 hrs
    prior to the intended departure time; or

```{=html}
<!-- -->
```
b)  if transiting XXX FIR, notify the XXX Oceanic Control Centre after
    approval is received from the first affected Centre and prior to
    departure. (note that filing of the flight plan is not appropriate
    notification), and

```{=html}
<!-- -->
```
c)  include the remarks "APVD non-RVSM" in Field 18 of the ICAO Flight
    Plan.

10.4 Contact details for approval request or notification are as
follows:

> Telephone:
>
> TELETYPE:
>
> FAX:

10.5 Non-RVSM aircraft operating in the RVSM stratum will be separated
from all other aircraft by a minimum 2000 ft vertical separation.

10.6 This approval process is intended exclusively for the purposes
indicated above and not as a means to circumvent the normal RVSM
approval process.

## 

## 11. State aircraft

11.1 Operators of State aircraft (military, customs or police service)
may flight plan within XXXXXXX FIR RVSM airspace in accordance with the
requirements of paragraph 10.3. The United States requires operators of
State aircraft within the Anchorage Oceanic and Oakland Oceanic flight
information regions to notify under paragraph 10.3 (a) not more than 72
hours and not less than 12 hrs prior to the intended departure time. If
transiting XXX FIR, notify the XXX Oceanic Control Centre of intentions
prior to departure. (Note that filing of the flight plan is not
appropriate notification. notification constitutes approval).

11.2 The requirements of 10.3 (b) may not be applicable in other flight
information regions for State aircraft, dependent on requirements for
those flight information regions.

## 12. Operation of non-RVSM aircraft within RVSM airspace

12.1 It should be noted that RVSM approved aircraft will be given
priority for level allocation over non-RVSM approved aircraft. The
vertical separation minimum between non-RVSM aircraft operating in the
RVSM stratum and all other aircraft is 2,000 ft.

12.2 ATC may clear non-RVSM approved aircraft not meeting paragraph 10.2
requirements to climb or descend through RVSM airspace, provided they do
not climb or descend at less than standard rate, or level off while
passing through the RVSM stratum.

*Optional text* 12.3 On pilot request and at ATC discretion, non-RVSM
approved aircraft that do not meet the requirements of paragraph 10.2
within the XXXX FIR may be cleared to cruise at an RVSM level, after
consideration of ATC workload, conflicting traffic and the priority of
RVSM approved aircraft.

## 13. Procedures for suspension of RVSM

13.1 Air traffic services will consider suspending RVSM procedures
within affected areas of the XXXXXX FIR when there pilot reports of
greater than moderate turbulence. Within areas where RVSM procedures are
suspended, the vertical separation minimum between all aircraft will be
2,000 ft.

Notam-us.doc

[SAMPLE 12-18 MONTH ADVANCE NOTAM]{.underline}

Where/What: Asia Pacific RVSM

When: XX/XX/XXXX

Type: Permanent

This NOTAM serves as Notice of Intent to implement RVSM in the XXX FIRs
on XXX

Reduced Vertical Separation Minimum (RVSM) is vertical separation of
aircraft by 1,000 ft above FL 290. By XXX, Pacific operators should have
received RVSM aircraft (airworthiness) and operational approval from the
appropriate State authority. Pacific operator/aircraft approval by XXX
will enable air traffic to plan for orderly RVSM implementation.

Starting XXX, only RVSM compliant aircraft will be cleared to operate in
the XXX FIR and the XXX FIR between FLs 290 and 390 (inclusive).
Aircraft that are not RVSM compliant (e.g., State aircraft, ferry and
maintenance flights) will only be cleared to operate in the XXX FIR and
the XXX FIR between FLs 290 and 390 (inclusive) after prior coordination
with the appropriate Center. 2,000 ft vertical separation will be
applied to such aircraft. XXX Center contacts will be published on web
sites and in follow-up NOTAMS.

RVSM will be implemented in the XXX FIRs in accordance with ICAO
regional agreements. ICAO recommends that State authorities and
operators use FAA Interim Guidance 91-RVSM, Change 1 (30 June 1999),
Joint Airworthiness Authorities Temporary Guidance Leaflet 6 or
equivalent State documents as the basis for approving aircraft and
operator programs for RVSM. Current information and RVSM approval
documents, including revisions, can be found on the web site maintained
by the FAA on behalf of ICAO and on individual State web sites. To
access the FAA web site, type:

http:/www.faa.gov/ats/ato/rvsm1.htm

For questions on the aircraft and operator approval process, the
following contacts may be used:

[FAA:]{.underline}

Roy Grimes: Ph 1-202-267-3734; fax 1-202-267-5086; roy.grimes@faa.gov

Bob Hanson: Ph 1-202-267-3739; fax 1-202-267-5086;
robert.g.hanson@faa.gov

Bob Miller: Ph 1-202-484-3359; fax 1-202-863-2398; rmiller@cssiinc.com

[CAA New Zealand]{.underline}

Chris Lamain: Ph 64-4-560-9418; fax 64-4-560-9452; lamainc@caa.govt.nz

[IATA Singapore]{.underline}

Neil Jonasson: Ph 65-239-7262; fax 65-536-6267; jonassonn@iata.org

Operators must begin coordination with the appropriate State authority
as soon as possible to ensure that they are RVSM approved by XX.

**Asia Pacific Region RVSM Implementation Plans Status Report**

+-----------------------+-----------+----------------------------------+
| FIR                   | RVSM      | Comments                         |
|                       | Imple     |                                  |
|                       | mentation |                                  |
|                       | Date      |                                  |
+=======================+===========+==================================+
| Anchorage Arctic      | 24 Feb    | RVSM Transition Airspace only    |
|                       | 2000      |                                  |
+-----------------------+-----------+----------------------------------+
| Anchorage Continental | 24 Feb    | RVSM Transition Airspace only    |
|                       | 2000      |                                  |
+-----------------------+-----------+----------------------------------+
| Anchorage Oceanic     | 24 Feb    |                                  |
|                       | 2000      |                                  |
+-----------------------+-----------+----------------------------------+
| Auckland Oceanic      | 24 Feb    |                                  |
|                       | 2000      |                                  |
+-----------------------+-----------+----------------------------------+
| Bali                  | Not       | Subject to Indonesia upper       |
|                       | a         | airspace consolidation           |
|                       | pplicable |                                  |
+-----------------------+-----------+----------------------------------+
| Bangkok               | 21 Feb    |                                  |
|                       | 2002      |                                  |
+-----------------------+-----------+----------------------------------+
| Beijing               |           |                                  |
+-----------------------+-----------+----------------------------------+
| Biak                  | Not       | Subject to Indonesia upper       |
|                       | a         | airspace consolidation           |
|                       | pplicable |                                  |
+-----------------------+-----------+----------------------------------+
| Bombay                |           |                                  |
+-----------------------+-----------+----------------------------------+
| Brisbane              | 24 Feb    | Oceanic East of Australia 24 Feb |
|                       | 2000      | 2000                             |
|                       |           |                                  |
|                       |           | Remainder of FIR March 2001      |
+-----------------------+-----------+----------------------------------+
| Calcutta              |           |                                  |
+-----------------------+-----------+----------------------------------+
| Colombo               |           |                                  |
+-----------------------+-----------+----------------------------------+
| Dhaka                 |           |                                  |
+-----------------------+-----------+----------------------------------+
| Delhi                 |           |                                  |
+-----------------------+-----------+----------------------------------+
| Guangzhou             |           |                                  |
+-----------------------+-----------+----------------------------------+
| Hanoi                 | To be     |                                  |
|                       | d         |                                  |
|                       | etermined |                                  |
+-----------------------+-----------+----------------------------------+
| Ho-Chi-Minh           | To be     |                                  |
|                       | d         |                                  |
|                       | etermined |                                  |
+-----------------------+-----------+----------------------------------+
| Hong Kong             | 21 Feb    |                                  |
|                       | 2002      |                                  |
+-----------------------+-----------+----------------------------------+
| Honiara               | 24 Feb    |                                  |
|                       | 2000      |                                  |
+-----------------------+-----------+----------------------------------+
| Jakarta               | 21 Feb    |                                  |
|                       | 2002      |                                  |
+-----------------------+-----------+----------------------------------+
| Karachi               |           |                                  |
+-----------------------+-----------+----------------------------------+
| Kathmandu             |           |                                  |
+-----------------------+-----------+----------------------------------+
| Kota Kinabalu         | 21 Feb    |                                  |
|                       | 2002      |                                  |
+-----------------------+-----------+----------------------------------+
| Kuala Lumpur          | 21 Feb    |                                  |
|                       | 2002      |                                  |
+-----------------------+-----------+----------------------------------+
| Kunming               |           |                                  |
+-----------------------+-----------+----------------------------------+
| Lahore                |           |                                  |
+-----------------------+-----------+----------------------------------+
| Lanzhou               |           |                                  |
+-----------------------+-----------+----------------------------------+
| Madras                |           |                                  |
+-----------------------+-----------+----------------------------------+
| Male                  |           |                                  |
+-----------------------+-----------+----------------------------------+
| Manila                | 21 Feb    |                                  |
|                       | 2002      |                                  |
+-----------------------+-----------+----------------------------------+
| Melbourne             | March     |                                  |
|                       | 2001      |                                  |
+-----------------------+-----------+----------------------------------+
| Nadi                  | 24 Feb    |                                  |
|                       | 2000      |                                  |
+-----------------------+-----------+----------------------------------+
| Naha                  | 24 Feb    | Pacific Oceanic (non-exclusive   |
|                       | 2000      | RVSM airspace) Further phased    |
|                       |           | implementation planned           |
+-----------------------+-----------+----------------------------------+
| Nauru                 | 24 Feb    |                                  |
|                       | 2000      |                                  |
+-----------------------+-----------+----------------------------------+
| New Zealand           | 13 July   | Non-exclusive                    |
| (Domestic)            | 2000      |                                  |
+-----------------------+-----------+----------------------------------+
| Oakland Oceanic       | 24 Feb    |                                  |
|                       | 2000      |                                  |
+-----------------------+-----------+----------------------------------+
| Phnom-Penh            |           |                                  |
+-----------------------+-----------+----------------------------------+
| Port Moresby          | 13 Apr    |                                  |
|                       | 2000      |                                  |
+-----------------------+-----------+----------------------------------+
| Pyongyang             |           |                                  |
+-----------------------+-----------+----------------------------------+
| Shanghai              |           |                                  |
+-----------------------+-----------+----------------------------------+
| Shenyang              |           |                                  |
+-----------------------+-----------+----------------------------------+
| Singapore             | 21 Feb    |                                  |
|                       | 2002      |                                  |
+-----------------------+-----------+----------------------------------+
| Taegu                 |           |                                  |
+-----------------------+-----------+----------------------------------+
| Tahiti                | 24 Feb    | Non-exclusive RVSM airspace      |
|                       | 2000      |                                  |
+-----------------------+-----------+----------------------------------+
| Taibei                |           |                                  |
+-----------------------+-----------+----------------------------------+
| Tokyo                 | 24 Feb    | Oceanic                          |
|                       | 2000      |                                  |
+-----------------------+-----------+----------------------------------+
| Ujung Pandang         | 21 Feb    |                                  |
|                       | 2002      |                                  |
+-----------------------+-----------+----------------------------------+
| Ulan Bator            |           |                                  |
+-----------------------+-----------+----------------------------------+
| Urumqi                |           |                                  |
+-----------------------+-----------+----------------------------------+
| Vientiane             |           |                                  |
+-----------------------+-----------+----------------------------------+
| Wuhan                 |           |                                  |
+-----------------------+-----------+----------------------------------+
| Yangon                |           |                                  |
+-----------------------+-----------+----------------------------------+

Revised Task List (Separate file)

**LIST OF WORKING AND INFORMATION PAPERS**

+-------+-------------------------------------------------+-----------+
| **Num | **Working Papers**                              | **        |
| ber** |                                                 | Presented |
|       |                                                 | by**      |
+=======+=================================================+===========+
| 1     | Provisional Agenda                              | Ch        |
|       |                                                 | airperson |
|       |                                                 | &         |
|       |                                                 | Se        |
|       |                                                 | cretariat |
+-------+-------------------------------------------------+-----------+
| 2     | RVSM Task Force Task List                       | Ch        |
|       |                                                 | airperson |
+-------+-------------------------------------------------+-----------+
| 3     | Considerations in the Development of an         | Ch        |
|       | Operational Concept for the Next Phase of RVSM  | airperson |
|       | Implementation in the Asia Pacific Region       |           |
+-------+-------------------------------------------------+-----------+
| 4     | Guidance Material on the Implementation of RVSM | Ch        |
|       | in the Airspace of the Asia Pacific Region      | airperson |
+-------+-------------------------------------------------+-----------+
| 5     | Agenda for the Operations/Airworthiness Working | OPS/AIR   |
|       | Group                                           | WG        |
|       |                                                 |           |
|       |                                                 | Ch        |
|       |                                                 | airperson |
+-------+-------------------------------------------------+-----------+
| 6     | Pacific RVSM Minimum Monitoring Requirements as | OPS/AIR   |
|       | of 7 June 1999                                  | WG        |
|       |                                                 |           |
|       |                                                 | Ch        |
|       |                                                 | airperson |
+-------+-------------------------------------------------+-----------+
| 7     | Agenda for the ATC Operations Working Group     | ATC WG    |
|       |                                                 |           |
|       |                                                 | Ch        |
|       |                                                 | airperson |
+-------+-------------------------------------------------+-----------+
| 8     | Asia /Pacific RVSM Implementation Plans Status  | Se        |
|       | Report                                          | cretariat |
+-------+-------------------------------------------------+-----------+
| 9     | Agenda for the Safety and Airspace Monitoring   | SAM WG    |
|       | Working Group                                   | Ch        |
|       |                                                 | airperson |
+-------+-------------------------------------------------+-----------+
| 10    | Principles for the Implementation of the RVSM   | Singapore |
|       | in the South China Sea Area                     |           |
+-------+-------------------------------------------------+-----------+
| 11    | Safety & Airspace Monitoring Considerations     | United    |
|       |                                                 | States    |
+-------+-------------------------------------------------+-----------+
| 12    | Reporting of Large Height Deviations in the     | United    |
|       | Asia Pacific Region -- Need for Continued       | States    |
|       | Emphasis                                        |           |
+-------+-------------------------------------------------+-----------+

  ---------------------------------------------------------------------------
  **Number**   **Information Papers**                           **Presented
                                                                by**
  ------------ ------------------------------------------------ -------------
  1            Proposed Order of Business                       Chairperson

  2            Suggested Format for the RVSM Implementation AIP Chairperson
               Supplement                                       

  3            Suggested Format for NOTAMs Advising the         Chairperson
               Implementation of RVSM                           

  4            ICAO Implementation RVSM Task Force Terms of     Chairperson
               Reference                                        
  ---------------------------------------------------------------------------

Message format for a report to the Asia/Pacific Approvals Registry and
Monitoring Organization of an altitude deviation of 300ft or more,
including those due to TCAS, turbulence and contingency events

**REPORT OF AN ALTITUDE DEVIATION OF 300FT OR MORE**

**BETWEEN FL290 & FL410**

> \(1\) Reporting agency
>
> \(2\) Location of deviation
>
> \(3\) NOPAC/CENPAC/CEP/SOPAC/Japan-Hawaii/South China Sea/Other
>
> \(4\) Flight identification and type
>
> \(5\) Flight level assigned
>
> \(6\) Observed/reported final level Mode C/Pilot report
>
> \(7\) Duration at flight level
>
> \(8\) Cause of deviation
>
> \(9\) Other traffic
>
> \(10\) Crew comments, if any, when noted
>
> \(11\) Remarks

When complete please return to the following address:

> William J Hughes Technical Center (WJHTC)
>
> NAS & International Airspace Analysis Branch (ACT-520)
>
> Atlantic City International Airport
>
> Atlantic City, NJ 08405
>
> Telephone: +1 609-485-5475
>
> Fax: +1 609-485-5117
>
> E-Mail: APARMO@.tc.faa.gov

[Duties and Responsibilities of the APARMO]{.smallcaps}

The Asia/Pacific Approvals Registry and Monitoring Organization (APARMO)
has the following duties and responsibilities:

a)  to establish and maintain a central registry of State RVSM approvals
    of operators and aircraft using the Asia Pacific Region airspace
    where RVSM will be applied;

b)  to facilitate the transfer of approval data to and from other RVSM
    regional monitoring agencies;

c)  to establish and maintain a data base containing the results of
    height keeping performance monitoring and all altitude deviations of
    300 ft or more within Asia Pacific Region airspace*,* and to include
    in the database the results of APARMO requests to operators and
    States for information explaining the causes of observed large
    height deviations;

d)  provide timely information on changes of monitoring status of
    aircraft type classifications to State authorities and operators;

e)  to assume overall responsibility for

    i\) administration of the Global Positioning System Monitoring
    System (GMS) and

    ii\) assessing compliance of operators and aircraft with RVSM
    height-keeping performance requirements

    in conjunction with RVSM introduction in the Asia Pacific Region;

f)  to provide the means for identifying non-RVSM approved operators
    using Asia Pacific airspace where RVSM is applied; and notifying the
    appropriate State approval authority; and

g)  to develop the means for summarizing and communicating the content
    of relevant databases to ICAO RVSM Task Force decision makers for
    use in agreeing on the timing and extent of RVSM application within
    the airspace under their administration.

[^1]: Phased flight level implementation

[^2]: ^2^ Phase 1: East of A590 (Sep 2000); Phase 2: A590 (Apr 2001);
    Phase 3: West of A590 (21 Feb 2002)

[^3]: ^1^