**FINAL REPORT**

**of the**

**THIRTEENTH MEETING**

**of the**

**INFORMAL SOUTH PACIFIC AIR TRAFFIC SERVICES**

**COORDINATING GROUP**

**(ISPACG/13)**

**Auckland, New Zealand**

**7-11 December 1998**

**OVERVIEW OF ISPACG**

**PURPOSE**

To promote a cost effective South Pacific Air Traffic Services aviation
environment that is responsive to change, meets the needs of the
aviation industry, is economically sustainable and maintains or enhances
present levels of safety.

**PRINCIPLES**

In the conduct of the activities of the Informal South Pacific ATS
Coordinating Group (ISPACG), the forum will apply the following
principles:

1\. Promote an ATS system that is responsive to and meets the needs of
our customers.

2\. Ensure that the introduction of new technology and procedures
maintains or

enhances the present levels of safety.

3\. Harmonize ATS practices and procedures consistent with regional and
global

activity.

4\. Undertake activities and provide outputs that are cost effective and
efficient

for both customers and service providers.

5\. Promote advantages in new technology where benefits can be derived.

6\. Achieve a cooperative customer/service provider environment.

**PRIMARY OBJECTIVE**

To implement an Air Traffic Management (ATM) concept of operations that
includes an evolutionary development towards Free Flight operations,
starting with the ATS supplied Dynamic Aircraft Reroute Program (DARP)
and progressing to individual user/airline defined optimum routes with
the ability to perform multiple user defined reroutes anywhere in the
region.

**TABLE OF CONTENTS**

> **Page No.**

Table of Contents 3

Background of the Meeting 4

ISPACG/13 Open Action Items 5

List of Participants 10

Meeting Agenda 15

Summary of the Meeting 17

**Appendix A - Meeting Documentation** 23

**Appendix B - Report of the FIT Working Group** 24

**Appendix** **C - Report of the DARP Working Group** 49

**Appendix D - Report of the Separation Working Group** 61

**Appendix E - Acronyms** 71

**BACKGROUND OF THE MEETING**

**1. PLACE AND DURATION**

1.1 The thirteenth meeting of the Informal South Pacific Air Traffic
Services (ATS) Coordinating Group (ISPACG) was held at the Sheraton
Auckland Hotel, Auckland,

New Zealand, during the period 7-11 December 1998.

**2. ATTENDANCE**

2.1 The meeting was attended by participants drawn from States,
airlines, the International Civil Aviation Organization (ICAO), the
International Air Transport Association (IATA), international aviation
organizations, representatives from communications service providers,
and airline/equipment manufacturers. A list of participants is included
as part of this report.

**3. OFFICERS AND SECRETARIAT**

3.1 Kathy Roil of the Airways Corporation of New Zealand (Airways),
Adrian Dumsa of the Airservices Australia (ASA), and Charles Reavis of
the United States Federal Aviation Administration (FAA) were the
co-chairs for ISPACG/13. Kathy Roil presided over the meeting throughout
its duration.

2.  Nancy Tarawhiti of Airways Corporation and Carolyn Ryan of the FAA
    provided

    secretariat services to the meeting.

    **ISPACG/13 OPEN ACTION ITEMS**

    **NOTE:** *The numbering of this list refers to the ISPACG/11
    Report. Items closed*

    *during this meeting are not shown on this following list.*

+-----------------------+------------------+---------+-----------------+
| **Action Item**       | **Action With**  | *       | **Action**      |
|                       |                  | *ISPACG |                 |
|                       |                  | A       |                 |
|                       |                  | ction** |                 |
|                       |                  |         |                 |
|                       |                  | *       |                 |
|                       |                  | *With** |                 |
+=======================+==================+=========+=================+
| 2\. ATS automation    | ATS Providers    | FIT     | Awaiting        |
| systems supporting    |                  |         | Implementation  |
| CPDLC                 |                  |         |                 |
+-----------------------+------------------+---------+-----------------+
| 5\. Introduce AIDC    | ATS Providers    | FIT     | Work commenced  |
| via AFTN              |                  |         |                 |
+-----------------------+------------------+---------+-----------------+
| 7\. Monitor and       | RTCA             | FIT     | Work ongoing    |
| report on the status  |                  |         |                 |
| of industry           |                  |         |                 |
| initiatives re        |                  |         |                 |
| SATVOICE              |                  |         |                 |
+-----------------------+------------------+---------+-----------------+
| 8\. Guidance material |                  | FIT     | Work ongoing    |
| for the use of        |                  |         |                 |
| SATVOICE              |                  |         |                 |
+-----------------------+------------------+---------+-----------------+
| 14\. Examine          | CAA (Aust),      | Sep     | RNP10 planning  |
| feasibility of        | (AIRWAYS), CAA   | aration | progressing     |
| introducing RNP in    | NZ and affected  |         | towards         |
| the Tasman Sea        | operators        |         | implementation  |
| airspace, in          |                  |         | on 23 April     |
| conjunction with the  |                  |         | 1998            |
| introduction of 60NM  |                  |         |                 |
| lateral separation    |                  |         |                 |
+-----------------------+------------------+---------+-----------------+
| 20\. DARP Phase 1     | Test DOTS        | DARP    | Work ongoing.   |
|                       | upgrade          |         |                 |
|                       |                  |         |                 |
|                       | Implement        |         |                 |
|                       | Southbound       |         |                 |
|                       | tracks           |         |                 |
|                       |                  |         |                 |
|                       | Implement        |         |                 |
|                       | Northbound       |         |                 |
|                       | tracks subject   |         |                 |
|                       | to:              |         |                 |
|                       |                  |         |                 |
|                       | -   OCS          |         |                 |
|                       |                  |         |                 |
|                       |    consolidation |         |                 |
|                       |                  |         |                 |
|                       |     DOTS         |         |                 |
|                       |     Software     |         |                 |
|                       |     Enhancement  |         |                 |
+-----------------------+------------------+---------+-----------------+
| 32\. Introduction of  |                  | Sep     | On-going - some |
| 50NM RNAV             |                  | aration | agreement on    |
| longitudinal /50NM    |                  |         | implementation  |
| lateral separation    |                  |         | areas, and      |
|                       |                  |         | further         |
|                       |                  |         | validation work |
|                       |                  |         | required for    |
|                       |                  |         | weather         |
|                       |                  |         | deviation       |
|                       |                  |         | areas.          |
|                       |                  |         | Agreement on    |
|                       |                  |         | possible        |
|                       |                  |         | applications -- |
|                       |                  |         | tactical and    |
|                       |                  |         | strategic,      |
|                       |                  |         | subject to      |
|                       |                  |         | validation of   |
|                       |                  |         | CPDLC           |
|                       |                  |         | performance     |
+-----------------------+------------------+---------+-----------------+
| 33\. Introduction of  |                  | Sep     | On-going -      |
| 30NM                  |                  | aration | discussion at   |
| longitudinal/30NM     |                  |         | this meeting on |
| lateral separation    |                  |         | progressing the |
| between FANS 1        |                  |         | 30/30 proposal. |
| equipped aircraft     |                  |         | Proposed        |
|                       |                  |         | establishing a  |
|                       |                  |         | Safety Case     |
|                       |                  |         | including       |
|                       |                  |         | further data    |
|                       |                  |         | analysis and    |
|                       |                  |         | risk            |
|                       |                  |         | assessment.     |
+-----------------------+------------------+---------+-----------------+
| 34\. In-trail climb   |                  | Sep     | On-going - no   |
| using distance based  |                  | aration | further work at |
| information           |                  |         | this meeting.   |
+-----------------------+------------------+---------+-----------------+
| 37\. Review weather   | ATS Providers    | Sep     | Doc 7030        |
| deviation procedures  | and users        | aration | amendment       |
|                       |                  |         | proposal has    |
|                       |                  |         | been circulated |
|                       |                  |         | and approved -  |
|                       |                  |         | likely to be    |
|                       |                  |         | included as a   |
|                       |                  |         | 7030 amendment  |
|                       |                  |         | in the next few |
|                       |                  |         | weeks - further |
|                       |                  |         | discussion at   |
|                       |                  |         | this meeting on |
|                       |                  |         | controller      |
|                       |                  |         | phraseologies.  |
+-----------------------+------------------+---------+-----------------+
| 38\. Use of distance  | ATS Providers    | Sep     | Lateral         |
| based information to  |                  | aration | separation      |
| determine lateral     |                  |         | values          |
| separation entry/exit |                  |         | incorporated    |
| points in OCA         |                  |         | into ICAO       |
|                       |                  |         | Airspace        |
|                       |                  |         | Planning        |
|                       |                  |         | Methodology     |
|                       |                  |         | which will be   |
|                       |                  |         | published later |
|                       |                  |         | this year.      |
+-----------------------+------------------+---------+-----------------+
| 39\. Development of a |                  | Sep     | On-going.       |
| plan for the conduct  |                  | aration | Agreement in    |
| of a RVSM operational |                  |         | plenary to join |
| demonstration         |                  |         | with IPACG in   |
|                       |                  |         | forming a joint |
|                       |                  |         | ISPACG/IPACG    |
|                       |                  |         | RVSM Task       |
|                       |                  |         | Force.          |
+-----------------------+------------------+---------+-----------------+
| 43\. Develop future   |                  | Sep     | Future work     |
| ATM backup procedures |                  | aration |                 |
| and policies          |                  |         |                 |
+-----------------------+------------------+---------+-----------------+
| 56\. Arrange          |                  | Sep     | To be           |
| promulgation and use  |                  | aration | promulgated in  |
| of weather deviation  |                  |         | a few weeks.    |
| procedures as the     |                  |         |                 |
| basis of a Doc 7030   |                  |         |                 |
| amendment proposal.   |                  |         |                 |
| Bruce Kivi to provide |                  |         |                 |
| advice to Roy Grimes  |                  |         |                 |
| on outcome of IFALPA  |                  |         |                 |
| CRM evaluation        |                  |         |                 |
+-----------------------+------------------+---------+-----------------+
| 57\. Implement data   |                  | Sep     | Some data       |
| collection and        |                  | aration | gathered in     |
| analysis plan to      |                  |         | Tasman for 60   |
| support the (50/50)   |                  |         | lateral can be  |
| verification trial,   |                  |         | used to verify  |
| and to assist ICAO to |                  |         | assumptions for |
| justify the           |                  |         | 50/50. 30/30    |
| introduction of a     |                  |         | work will be    |
| 30NM longitudinal and |                  |         | carried through |
| a 30NM lateral        |                  |         | the proposed    |
| separation minima     |                  |         | Safety Case.    |
| between aircraft      |                  |         |                 |
| approved to RNP 4 or  |                  |         |                 |
| better.               |                  |         |                 |
+-----------------------+------------------+---------+-----------------+
| 58\. Review           |                  | Sep     | To be           |
| implementation of RNP |                  | aration | implemented on  |
| 10 in the Tasman at   |                  |         | 23 April 1998   |
| ISPACG/10.            |                  |         |                 |
+-----------------------+------------------+---------+-----------------+
| 67\. Implement DARP   | Publish          | DARP    | Airways to      |
| Phase 2 & 3           | procedures in    |         | complete Feb 99 |
|                       | SPOM - Airways   |         |                 |
|                       |                  |         | Work Ongoing    |
|                       | All ATSUs        |         |                 |
|                       |                  |         | **Phase 2 Step  |
|                       | FIT              |         | 1:**            |
|                       |                  |         |                 |
|                       | All ATSU's       |         | Review and      |
|                       |                  |         | co-ordinate     |
|                       | Airways          |         | flight planning |
|                       |                  |         | requirements    |
|                       | Oakland          |         |                 |
|                       |                  |         | Agree to common |
|                       | Airservices      |         | flight planning |
|                       |                  |         | requirements    |
|                       | CAAF             |         |                 |
|                       |                  |         | Publish flight  |
|                       | All ATSUs        |         | planning        |
|                       |                  |         | requirements in |
|                       | ALL              |         | SPOM and AIP's  |
|                       |                  |         | or equivalent   |
|                       |                  |         | as appropriate  |
|                       |                  |         |                 |
|                       |                  |         | OCS             |
|                       |                  |         | consolidation   |
|                       |                  |         |                 |
|                       |                  |         | Reach labour    |
|                       |                  |         | agreement       |
|                       |                  |         |                 |
|                       |                  |         | **Phase 2 Step  |
|                       |                  |         | 2:**            |
|                       |                  |         |                 |
|                       |                  |         | TAAATS          |
|                       |                  |         | consolidation   |
|                       |                  |         |                 |
|                       |                  |         | EASY            |
|                       |                  |         | consolidation   |
|                       |                  |         |                 |
|                       |                  |         | AIDC            |
|                       |                  |         |                 |
|                       |                  |         | **Phase 3**     |
|                       |                  |         |                 |
|                       |                  |         | [Consolidation  |
|                       |                  |         | of Phase 2 Step |
|                       |                  |         | 2               |
|                       |                  |         | procedur        |
|                       |                  |         | es]{.smallcaps} |
+-----------------------+------------------+---------+-----------------+
| 68\. ACAS/TCAS        | All members      | Sep     | Collate and     |
|                       | through Len      | aration | distribute      |
|                       | Wicks (CAA NZ)   |         | information     |
|                       |                  |         | from each State |
|                       | All WG members   |         | regarding       |
|                       |                  |         | TCAS/ACAS       |
|                       |                  |         | implementation  |
|                       |                  |         | programme,      |
|                       |                  |         | including pilot |
|                       |                  |         | and controller  |
|                       |                  |         | training and    |
|                       |                  |         | procedures,     |
|                       |                  |         | regulatory      |
|                       |                  |         | requirements    |
|                       |                  |         | etc --          |
|                       |                  |         |                 |
|                       |                  |         | End of March    |
|                       |                  |         | 1999.           |
|                       |                  |         |                 |
|                       |                  |         | Examine ATS     |
|                       |                  |         | procedures and  |
|                       |                  |         | identify        |
|                       |                  |         | differences,    |
|                       |                  |         | deficiencies,   |
|                       |                  |         | etc --          |
|                       |                  |         |                 |
|                       |                  |         | End of June     |
|                       |                  |         | 1999.           |
|                       |                  |         |                 |
|                       |                  |         | Develop         |
|                       |                  |         | harmonised ATS  |
|                       |                  |         | procedures, in  |
|                       |                  |         | accordance with |
|                       |                  |         | ICAO plans for  |
|                       |                  |         | ACAS            |
|                       |                  |         | implementation  |
|                       |                  |         | -- TBD          |
|                       |                  |         |                 |
|                       |                  |         | Develop         |
|                       |                  |         | implementation  |
|                       |                  |         | strategy for    |
|                       |                  |         | harmonised      |
|                       |                  |         | procedures -    |
|                       |                  |         | TBD             |
+-----------------------+------------------+---------+-----------------+
| 69\. Ads Procedures   | Separation       | Adrian  | Distribute      |
|                       |                  | Dumsa   | ADSP/RGCSP      |
|                       |                  |         | material on ADS |
|                       |                  | All WG  | Operating       |
|                       |                  | members | Context.        |
|                       |                  |         |                 |
|                       |                  | All WG  | Review ADS      |
|                       |                  | members | operating       |
|                       |                  |         | procedures      |
|                       |                  |         |                 |
|                       |                  |         | Align local ADS |
|                       |                  |         | operating       |
|                       |                  |         | procedures with |
|                       |                  |         | draft ADSP      |
|                       |                  |         | material, as    |
|                       |                  |         | required.       |
|                       |                  |         |                 |
|                       |                  |         | Develop         |
|                       |                  |         | harmonised ADS  |
|                       |                  |         | operating       |
|                       |                  |         | procedures      |
+-----------------------+------------------+---------+-----------------+
| 70\. Actual C, N and  | All WG members   | Sep     | Conduct         |
| S Performance         |                  | aration | research into   |
|                       |                  |         | the possibility |
|                       |                  |         | of using the    |
|                       |                  |         | actual or       |
|                       |                  |         | certified       |
|                       |                  |         | performance of  |
|                       |                  |         | C, N or S       |
|                       |                  |         | capabilities of |
|                       |                  |         | aircraft in the |
|                       |                  |         | determination   |
|                       |                  |         | of separation   |
|                       |                  |         | minima and air  |
|                       |                  |         | traffic service |
|                       |                  |         | provisions --   |
|                       |                  |         |                 |
|                       |                  |         | End of April    |
|                       |                  |         | 1999            |
|                       |                  |         |                 |
|                       |                  |         | Develop draft   |
|                       |                  |         | concept of      |
|                       |                  |         | operations for  |
|                       |                  |         | the potential   |
|                       |                  |         | use of this     |
|                       |                  |         | information --  |
|                       |                  |         |                 |
|                       |                  |         | End of June     |
|                       |                  |         | 1999            |
|                       |                  |         |                 |
|                       |                  |         | Collate draft   |
|                       |                  |         | concepts -- End |
|                       |                  |         | of Sept 1999    |
|                       |                  |         |                 |
|                       |                  |         | Develop concept |
|                       |                  |         | and set         |
|                       |                  |         | programme for   |
|                       |                  |         | associated      |
|                       |                  |         | minima --       |
|                       |                  |         | ISPACG 14       |
+-----------------------+------------------+---------+-----------------+

**PARTICIPANT LIST**

+----------+----------+------------+--------------+------------------+
| **NAME** | *        | **         | **ADDRESS**  | **PHONE/FAX      |
|          | *TITLE** | COMPANY/** |              | NUMBERS &**      |
|          |          |            |              |                  |
|          |          | **ORGA     |              | **INTERNET**     |
|          |          | NIZATION** |              |                  |
+==========+==========+============+==============+==================+
| Al       |          | USAF /     | 1535 Command | +1-240-857-4390  |
| exander, |          | AFFSA /    | Drive        |                  |
| Kenneth  |          | XAX        |              | +1-240-857-3194  |
|          |          |            | Suite 4D -   | Fax              |
|          |          |            | 309          |                  |
|          |          |            |              | alexander.ke     |
|          |          |            | Andrews AFB, | n@andrews.af.mil |
|          |          |            | MD           |                  |
|          |          |            |              |                  |
|          |          |            | 20762--7002  |                  |
|          |          |            | USA          |                  |
+----------+----------+------------+--------------+------------------+
| Alley,   | D        | ARINC      | 6011         | +1-925-294-8400  |
| James    | irector, |            | Industrial   |                  |
|          | Pacific  |            | Way          | +1-925-294-9597  |
|          | Region   |            |              | Fax              |
|          |          |            | Livermore,   |                  |
|          |          |            | CA 94550     | JWA@ARINC.COM    |
|          |          |            |              |                  |
|          |          |            | USA          |                  |
+----------+----------+------------+--------------+------------------+
| Barclay, | Air      | FAA -      | 5125 Central | +1-510-745-3301  |
| Tom      | Traffic  | Oakland    | Ave          |                  |
|          | Manager  | ARTCC      |              | +1-510-745-3538  |
|          |          |            | Freemont, CA | Fax              |
|          |          |            | 94536        |                  |
|          |          |            |              |                  |
|          |          |            | USA          |                  |
+----------+----------+------------+--------------+------------------+
| Bertin,  | FANS A   | Aero       | B0403        | +                |
| Lionel   | Engineer | spatiale - |              | 33-5-61-93-62-93 |
|          |          | Airbus     | 316 Route de |                  |
|          |          | Operations | Bayonne      | +                |
|          |          |            |              | 33-5-61-93-80-06 |
|          |          |            | 31060        | Fax              |
|          |          |            | Toulouse     |                  |
|          |          |            | Cedex 03     | lion             |
|          |          |            | France       | el.bertin@avions |
|          |          |            |              | .aerospatiale.fr |
+----------+----------+------------+--------------+------------------+
| B        | A        | Airbus     | Rond Point   | +                |
| ousquie, | ssistant | Industrie  | Maurice      | 33-5-61-93-47-04 |
| Jean-    | to Vice  |            | Bellonte     |                  |
| Francois | Pr       |            |              | +                |
|          | esident, |            | 31707        | 33-5-61-93-48-47 |
|          | Eng      |            | Blagnac      | Fax              |
|          | ineering |            | Cedex France |                  |
|          | Op       |            |              |                  |
|          | erations |            |              |                  |
+----------+----------+------------+--------------+------------------+
| Bra      | CNS/ATM  | Civil      | P.O. Box     | +64-4-5609400    |
| cefield, | Project  | Aviation   | 31441        |                  |
| Rodney   | Manager  | Authority  |              | +64-4-5665030    |
|          |          | of New     | Lower Hutt   | Fax              |
|          |          | Zealand    |              |                  |
|          |          |            | New Zealand  | bracef           |
|          |          |            |              | ieldr@caa.gov.nz |
+----------+----------+------------+--------------+------------------+
| Broome,  | IFATCA   | NZALPA     | P.O. Box     | +64-9-5231191    |
| Kevin    | Rep      |            | 74347        |                  |
|          |          |            |              | +64-9-524-4525   |
|          |          |            | Market Road  | Fax              |
|          |          |            |              |                  |
|          |          |            | Auckland,    | offi             |
|          |          |            | New Zealand  | ce@nzalpa.org.nz |
+----------+----------+------------+--------------+------------------+
| Cameron, | Manager, | United     | P. O. Box    | +1-847-700-3004  |
| Gene     | Flight   | Airlines   | 66100        |                  |
|          | Dispatch |            |              | +1-847-364-0717  |
|          | S        |            | Chicago, IL  | Fax              |
|          | tandards |            | 60666 USA    |                  |
|          | and      |            |              | gene             |
|          | Training |            |              | .cameron@ual.com |
+----------+----------+------------+--------------+------------------+
| C        | ATC      | SEAC       | BP 6011      | +689-86-1148     |
| laustre, | Op       | Polynesie  |              |                  |
| Georges  | erations | Francaise  | Faaa         | +689-86-1049 Fax |
|          | Tahiti   |            | Aeroport     |                  |
|          | ACC      |            |              | claustre         |
|          |          |            | Tahiti 98702 | _georges@seac.pf |
|          |          |            |              |                  |
|          |          |            | French       |                  |
|          |          |            | Polynesia    |                  |
+----------+----------+------------+--------------+------------------+
| Cornell, | Lead     | Boeing     | PO Box 3707  | +1-425-294-0540  |
| Brad     | En       | Airplane   | Ms-02-JH     |                  |
|          | gineer - | Services   |              | +1-425-294-0515  |
|          | Flight   |            | Seattle WA   | Fax              |
|          | Crew     |            |              |                  |
|          | Opns     |            | 98124-2207   | bradley.d.co     |
|          |          |            | USA          | rnell@boeing.com |
+----------+----------+------------+--------------+------------------+
| Coutin,  | Air      | SEAC       | BP6011       | +689-86-1021     |
| Annie    | Na       | French     |              |                  |
|          | vigation | Polynesia  | Tahiti       | +689-86-1029     |
|          | Service  |            |              |                  |
|          | Manager  |            | 98702 FAAA - | coutin@seac.pf   |
|          |          |            | Aeroport     |                  |
+----------+----------+------------+--------------+------------------+
| Cuddy,   | S        | United     | 7401 Martin  | +1-303-780-5979  |
| Mike     | tandards | Airlines   | Luther King  |                  |
|          | Captain, |            | Blvd         | +1-303-780-5665  |
|          | Flight   |            |              | Fax              |
|          | S        |            | Denver       |                  |
|          | tandards |            | Colorado     | cud              |
|          | and      |            | 80207 USA    | dy@ualfltctr.com |
|          | Op       |            |              |                  |
|          | erations |            |              |                  |
+----------+----------+------------+--------------+------------------+
| Dell,    | Regional | ICAO Asia/ | P.O. Box 11, | +662-537-8189    |
| Owen     | T        |            | Samyaek      |                  |
|          | echnical | Pacific    |              | +662-537-8199    |
|          | Officer  | Office     | Ladprao,     | Fax              |
|          | ATM      |            | Bangkok      |                  |
|          |          |            | 10901        | del              |
|          |          |            | Thailand     | lo@loxinfo.co.th |
+----------+----------+------------+--------------+------------------+
| Di       |          | FAA AUA -  | 800          | +1-202-366-5005  |
| Bartolo, |          | 600        | Independence |                  |
| Adam     |          |            | Ave, SW.     | +1-202-366-7565  |
|          |          |            |              | Fax              |
|          |          |            | Washington,  |                  |
|          |          |            | DC 20591 USA | adam.d           |
|          |          |            |              | ibartolo@gaa.gov |
+----------+----------+------------+--------------+------------------+
| Dryden,  | Supv     | F          | 5125 Central | +1-510-745-3234  |
| Carol    | Traffic  | AA/Oakland | Avenue       |                  |
|          | Ma       | ARTCC      |              | +1-510-745-3628  |
|          | nagement |            | Fremont, CA  | Fax              |
|          | Coo      |            | 94536 USA    |                  |
|          | rdinator |            |              | caro             |
|          |          |            |              | l.dryden@faa.gov |
+----------+----------+------------+--------------+------------------+
| Dugail,  | ATC      | SEAC       | BP 6011      | +689-86-1041     |
| Roland   | Op       | Polynesie  |              |                  |
|          | erations | Francaise  | Faaa         | +689-86-1049 Fax |
|          | Tahiti   |            | Aeroport     |                  |
|          | ACC      |            |              | dugai            |
|          |          |            | Tahiti       | l_roland@seac.pf |
|          |          |            | French       |                  |
|          |          |            | Polynesia    |                  |
+----------+----------+------------+--------------+------------------+
| Dumsa,   | Manager, | A          | GPO Box 367  | +61-2-6268-4178  |
| Adrian   | National | irservices |              |                  |
|          | Op       | Australia  | Canberra ACT | +61-2-6268-5695  |
|          | erations |            | 2601         | Fax              |
|          | S        |            | Australia    |                  |
|          | tandards |            |              | adrian.dumsa@ai  |
|          |          |            |              | rservices.gov.au |
+----------+----------+------------+--------------+------------------+
| Elaisa,  |          | CAA Fiji   | NAP 0354     | +679-721555      |
| Moagrava |          |            |              |                  |
|          |          |            | Nadi Airport | +679-721500      |
|          |          |            |              |                  |
|          |          |            | FIJI         | cts@caaf.org.fj  |
+----------+----------+------------+--------------+------------------+
| Foreman, | C        | IFALPA     | 5351 Parker  | +1-250-658-8045  |
| Capt.    | hairman, |            | Avenue       | Phone/Fax        |
| Peter    | Air      |            |              |                  |
|          | Traffic  |            | Victoria,    | 71534.232        |
|          | Services |            | B.C.         | 3@compuserve.com |
|          | C        |            |              |                  |
|          | ommittee |            | V8Y2N1       |                  |
|          |          |            | Canada       |                  |
+----------+----------+------------+--------------+------------------+
| Goodall, | Pr       | (AIRWAYS)  | PO Box 53093 | +64-9-275-3109   |
| Mark     | ocedures |            |              |                  |
|          | Auckland |            | Auckland     | +64-9-275-3106   |
|          | Oceanic  |            | I            | Fax              |
|          |          |            | nternational |                  |
|          |          |            | Airport      | goodal           |
|          |          |            |              | lm@airways.co.nz |
|          |          |            | Auckland New |                  |
|          |          |            | Zealand      |                  |
+----------+----------+------------+--------------+------------------+
| Graham,  |          | FAA        | 400 7th      | +1-202-366-5316  |
| Nancy    |          |            | Street, S W  |                  |
|          |          |            | PL-200       | +1-202-366-7565  |
|          |          |            |              | Fax              |
|          |          |            | Washington,  |                  |
|          |          |            | DC 20590     |                  |
|          |          |            |              |                  |
|          |          |            | USA          |                  |
+----------+----------+------------+--------------+------------------+
| Gray,    | Oceanic  | Airways    | P O Box      | +64-9-275 3109   |
| Hamish   | Sector   | C          | 53093        |                  |
|          | Manager  | orporation |              | +64-9-275 3106   |
|          |          |            | Auckland     |                  |
|          |          |            | I            | h.gr             |
|          |          |            | nternational | ay@airways.co.nz |
|          |          |            | Airport      |                  |
|          |          |            |              |                  |
|          |          |            | Auckland New |                  |
|          |          |            | Zealand      |                  |
+----------+----------+------------+--------------+------------------+
| Grimes,  | CNS      | FAA        | 800          | +1-202-267-3734  |
| R. Roy   | Sp       | HQ/AFS-400 | Independence |                  |
|          | ecialist |            | Ave SW       | +1-202-267-5086  |
|          |          |            |              | Fax              |
|          |          |            | Washington   |                  |
|          |          |            | DC 20591 USA | ro               |
|          |          |            |              | y.grimes@faa.gov |
+----------+----------+------------+--------------+------------------+
| Grimm,   | Systems  | FAA        | 400 7th      | +1-202-366-5132  |
| Kevin    | Engineer | HQ/AUA-600 | Street SW    |                  |
|          | AOAS     |            |              | +1-202-366-7565  |
|          | Build 1  |            | Suite 200    | Fax              |
|          |          |            |              |                  |
|          |          |            | Washington   | kev              |
|          |          |            | DC 20591 USA | in.grimm@faa.gov |
+----------+----------+------------+--------------+------------------+
| Gur      | Regional | IFALPA     | Intrpilot    | +612-9948-7532   |
| sanscky, | VP South |            | House        |                  |
| Toby     | Pacific  |            | Gogmore Lane | gursan           |
|          | Ops      |            |              | scky@bigpond.com |
|          |          |            | Chertsey,    |                  |
|          |          |            | Surrey       |                  |
|          |          |            |              |                  |
|          |          |            | KT16 9AP,    |                  |
|          |          |            | England      |                  |
+----------+----------+------------+--------------+------------------+
| H        | Oceanic  | FAA        | 800          | +1-202-267-9467  |
| awrysko, | & Int'l  | HQ/ATO-150 | Independence |                  |
| Coleen   | Sp       |            | Ave SW       | +1-202-267-5305  |
|          | ecialist |            |              | Fax              |
|          |          |            | Washington   |                  |
|          |          |            | DC 20591 USA | coleen.          |
|          |          |            |              | hawrysko@faa.gov |
+----------+----------+------------+--------------+------------------+
| Homans,  |          | ARINC      | 2551 Riva    | +1-410-266-4178  |
| Al       |          |            | Road         |                  |
|          |          |            |              | +1-410-573-3106  |
|          |          |            | Annapolis MD | Fax              |
|          |          |            |              |                  |
|          |          |            | 21401-7465   | a                |
|          |          |            | USA          | homans@arinc.com |
+----------+----------+------------+--------------+------------------+
| Jo       | Avionics | Boeing     | 3855         | +1-562-593-7037  |
| hnstone, | Mods     | Airplane   | Lakewood     |                  |
| Randolph | Manager  | Services   | Blvd         | +562-497-6367    |
|          |          |            |              | Fax              |
|          |          |            | M/C          |                  |
|          |          |            | DO35-0035    | randy.john       |
|          |          |            |              | stone@boeing.com |
|          |          |            | Long Beach   |                  |
|          |          |            | CA, 90846    |                  |
|          |          |            |              |                  |
|          |          |            | USA          |                  |
+----------+----------+------------+--------------+------------------+
| J        | A        | IATA       | 77 Robinson  | +65-239-7262     |
| onasson, | ssistant |            | Road         |                  |
| Neil     | Director |            |              | +65-536-6267 Fax |
|          | Infras   |            | 05-00 SIA    |                  |
|          | tructure |            | Building     | jo               |
|          | Asia     |            |              | nassonn@iata.org |
|          | /Pacific |            | Singapore    |                  |
|          |          |            | 068896       |                  |
+----------+----------+------------+--------------+------------------+
| Joyce,   | Inter    | CSSI Inc   | 1817 W.      | +1-602-855-0407  |
| Kim      | national |            | Raven Dr     |                  |
|          | Sp       |            |              | k                |
|          | ecialist |            | Chandler, AZ | imtjoyce@aol.com |
|          |          |            | 85248        |                  |
|          |          |            |              |                  |
|          |          |            | USA          |                  |
+----------+----------+------------+--------------+------------------+
| Kelly,   | Na       | Air New    | Private Bag  | +64-9-2563433    |
| Steve    | vigation | Zealand    | 92007        |                  |
|          | Services |            |              | +64-9-2563936    |
|          | Officer  |            | Auckland 1   | Fax              |
|          |          |            |              |                  |
|          |          |            | New Zealand  | steve.k          |
|          |          |            |              | elly@airnz.co.nz |
+----------+----------+------------+--------------+------------------+
| Kraft,   | NRS for  | FA         | 1601 Lind    | +1-425-227-2129  |
| Tom      | Aero     | A/ANM-114N | Avenue, SW   |                  |
|          | nautical |            |              | +1-425-227-1181  |
|          | Commu    |            | Renton, WA   | Fax              |
|          | nication |            | 98055-4056   |                  |
|          |          |            | USA          | t                |
|          |          |            |              | om.kraft@faa.gov |
+----------+----------+------------+--------------+------------------+
| Lamain,  |          | CAA New    | P O Box      | +64-4-560 9400   |
| Chris    |          | Zealand    | 31441        |                  |
|          |          |            |              | +64-4-569 2024   |
|          |          |            | Lower Hutt   |                  |
|          |          |            |              | lam              |
|          |          |            | New Zealand  | ainc@caa.govt.nz |
+----------+----------+------------+--------------+------------------+
| Lawso    | Director | La         | 9 Ennis      | +61-2-625        |
| n-Smith, |          | wson-Smith | Place        | 83174(Phone/Fax) |
| Gary     |          | Associates |              |                  |
|          |          | Pty Ltd.   | Melba ACT    | +61-04           |
|          |          |            | 2615         | 19491547(Mobile) |
|          |          | (IATA      |              |                  |
|          |          | Observer)  | Australia    | garylawsonsmit   |
|          |          |            |              | h@ozemail.com.au |
+----------+----------+------------+--------------+------------------+
| Ma       |          | ARINC      | 2551 Riva    | +1-410-266-4563  |
| cLellan, |          |            | Road,        |                  |
| Sarah    |          |            | Annapolis    | +1-410-573-3106  |
|          |          |            |              | Fax              |
|          |          |            | MD           |                  |
|          |          |            | 21401-7465   | slm@arinc.com    |
|          |          |            |              |                  |
|          |          |            | USA          |                  |
+----------+----------+------------+--------------+------------------+
| Maiolla, | Senior   | SITA       | 770          | +1-514-982-3636  |
| Vaughn   | Manager, |            | Sherbrooke   |                  |
|          | Air      |            | St. W.,      | +1-514-847-3350  |
|          | Traffic  |            |              | Fax              |
|          | Services |            | Suite 1400   |                  |
|          |          |            |              |                  |
|          |          |            | Montreal,    |                  |
|          |          |            | Quebec H3A   |                  |
|          |          |            | 1G1 / Canada |                  |
+----------+----------+------------+--------------+------------------+
| Mattai,  | Systems  | Rockwell   | 400 Collins  | +1-319-295-2002  |
| Roy      | Project  | Collins    | Rd, NE       |                  |
|          | E        |            |              | +1-319-295-3775  |
|          | ngineer, |            | Cedar        | Fax              |
|          | GATM     |            | Rapids, IOWA |                  |
|          | Systems  |            | 52498        | rmattai@coll     |
|          |          |            |              | ins.rockwell.com |
+----------+----------+------------+--------------+------------------+
| M        | FANS     | F          | 400 7th      | +1-202-366-5797  |
| cCarron, | Initial  | AA/AUA-600 | Street SW,   |                  |
| John     | National |            | Suite 200    | +1-202-366-7565  |
|          | Ca       |            |              | Fax              |
|          | pability |            | Washington   |                  |
|          | Product  |            | DC 20591 USA | john.            |
|          | Team     |            |              | mccarron@faa.gov |
|          | Leader   |            |              |                  |
+----------+----------+------------+--------------+------------------+
| M        | ATS      | Airways    | P O Box      | +64-3-358 1620   |
| cConway, | Policy   | C          | 14-131       |                  |
| John     | and      | orporation |              | +64-3-358 9071   |
|          | S        |            | Christchurch | Fax              |
|          | tandards |            |              |                  |
|          | Manager  |            | New Zealand  | mcconw           |
|          |          |            |              | aj@airways.co.nz |
+----------+----------+------------+--------------+------------------+
| Mc       | Inter    | FAA        | 800          | +1-202-267-7646  |
| Cormick, | national | HQ/AAT-30  | Independence |                  |
| Leslie   | Program  |            | Ave SW       | +1-202-267-5120  |
|          | Officer  |            |              | Fax              |
|          |          |            | Washington   |                  |
|          |          |            | DC 20591 USA | leslieM1@csi.com |
+----------+----------+------------+--------------+------------------+
| Miller,  | P        | FAA/CSSI   | 600 Maryland | +1-202-484-3359  |
| Robert   | rincipal |            | Ave, SW,     |                  |
|          | Engineer |            | Suite 890    | +1-202-863-2398  |
|          |          |            |              | Fax              |
|          |          |            | Washington   |                  |
|          |          |            | DC, 20024    | rmi              |
|          |          |            |              | ller@cssiinc.com |
|          |          |            | USA          |                  |
+----------+----------+------------+--------------+------------------+
| Nezer,   | Manager, | FAA        | 800          | +1-202-267-7940  |
| Gus      | Oceanic  | HQ/ATO-150 | Independence |                  |
|          | Op       |            | Ave SW       | +1-202-267-5305  |
|          | erations |            |              | Fax              |
|          | and      |            | Washington,  |                  |
|          | Pr       |            | DC 20591 USA | g                |
|          | ocedures |            |              | us.nezer@faa.gov |
|          | Branch   |            |              |                  |
+----------+----------+------------+--------------+------------------+
| Norrish, | Manager, | INMARSAT   | 99 City Road | +44-171-728 1071 |
| Lindsay  | Aero     |            |              |                  |
|          | nautical |            | London       | +44-171-728 1193 |
|          | Safety   |            |              | Fax              |
|          | Services |            | ECIY IAX,    |                  |
|          |          |            | England      | Lindsay_Norr     |
|          |          |            |              | ish@inmarsat.org |
+----------+----------+------------+--------------+------------------+
| O\       | H        | Honeywell  | P O Box 203  | +61-2-6254 7055  |
| 'Keeffe, | oneywell |            |              |                  |
| Brian    | Co       |            | Civic Square | +61-2-6278 3660  |
|          | nsultant |            | ACT 2608     | Fax              |
|          |          |            |              |                  |
|          |          |            | Australia    |                  |
+----------+----------+------------+--------------+------------------+
| Oliver,  | G.M.     | QANTAS     | 203 Coward   | +61-2-9691 1158  |
| David    | Flight   |            | St, M/S QCC2 |                  |
|          | T        |            |              | +61-2-9691 1235  |
|          | echnical |            | Mascot NSW   | Fax              |
|          |          |            |              |                  |
|          |          |            | 2020,        | doliv            |
|          |          |            | Australia    | er@qantas.com.au |
+----------+----------+------------+--------------+------------------+
| Owens,   | ACARS    | ARINC      | 2551 Riva Rd | +1-410-266-4946  |
| Jerry    | T        |            |              |                  |
|          | echnical |            | Annapolis MD | +1-410-573-3026  |
|          | Director |            |              | Fax              |
|          |          |            | USA          |                  |
|          |          |            |              | Jowens@ARINC.COM |
+----------+----------+------------+--------------+------------------+
| Pattie,  |          | CAA New    | P O Box      | +64-4-560-9400   |
| David    |          | Zealand    | 31441        |                  |
|          |          |            |              | +64-4-569-2024   |
|          |          |            | Lower Hutt   | Fax              |
|          |          |            |              |                  |
|          |          |            | New Zealand  | pa               |
|          |          |            |              | ttie@caa.govt.na |
+----------+----------+------------+--------------+------------------+
| Pawson,  | ATS      | Airways    | P O Box      | +64-3-358-1554   |
| Bryan    | Op       | C          | 14-131       |                  |
|          | erations | orporation |              | +64-3-358-9071   |
|          | Sp       |            | Christchurch | Fax              |
|          | ecialist |            |              |                  |
|          |          |            | New Zealand  | pawso            |
|          |          |            |              | nb@airways.co.nz |
+----------+----------+------------+--------------+------------------+
| Radford, | ATS      | (AIRWAYS)  | PO Box 53093 | +64-9-275-3109   |
| Paul     | Spec     |            |              |                  |
|          | ialist - |            | Auckland     | +64-9-275-3106   |
|          | OCS      |            | I            | Fax              |
|          | Project  |            | nternational |                  |
|          |          |            | Airport      | radfor           |
|          |          |            |              | dp@airways.co.nz |
|          |          |            | Auckland New |                  |
|          |          |            | Zealand      |                  |
+----------+----------+------------+--------------+------------------+
| Reavis,  | Manager, | FAA        | 800          | +1-202-267-9313  |
| Charles  | ATS      | HQ/AAT-30  | Independence |                  |
|          | Inter    |            | Ave SW       | +1-202-267-5120  |
|          | national |            |              | Fax              |
|          | Staff    |            | Washington   |                  |
|          |          |            | DC 20591 USA | chuc             |
|          |          |            |              | k.reavis@faa.gov |
+----------+----------+------------+--------------+------------------+
| Roberts, | Datalink | Melbourne  | P.O. Box     | +61-3-9235-7362  |
| Craig    | Sp       | Centre     | 1093         |                  |
|          | ecialist | Operations |              | +61-3-9235-2742  |
|          |          |            | Tullamarine  | Fax              |
|          |          | A          | Vic 3043     |                  |
|          |          | irservices |              | craig.roberts@ai |
|          |          | Australia  | Australia    | rservices.gov.au |
+----------+----------+------------+--------------+------------------+
| Roil,    | Business | Airways    | PO Box 294   | +64-4-4714746    |
| Kathy    | Manager  |            |              |                  |
|          | Oceanic  |            | Wellington   | +64-25-990278    |
|          |          |            |              | Mob              |
|          |          |            | New Zealand  |                  |
|          |          |            |              | +64-4-4715817    |
|          |          |            |              | Fax              |
|          |          |            |              |                  |
|          |          |            |              | roi              |
|          |          |            |              | lk@airways.co.nz |
+----------+----------+------------+--------------+------------------+
| Rougier, | CNS/ATM  | AIRSYSATM  | 780          | +61-3-9341-3799  |
| Marc     | Product  |            | Elizabeth    |                  |
|          | Manager  |            | Street       | +61-3-9347-2018  |
|          |          |            |              | Fax              |
|          |          |            | Melbourne    |                  |
|          |          |            |              |                  |
|          |          |            | Victoria     |                  |
|          |          |            | 3000         |                  |
|          |          |            |              |                  |
|          |          |            | Australia    |                  |
+----------+----------+------------+--------------+------------------+
| Ryan,    | Inter    | FAA        | 800          | +1-202-267-9353  |
| Carolyn  | national | HQ/AAT-30  | Independence |                  |
|          | Program  |            | Ave SW       | +1-202-267-5120  |
|          | Officer  |            |              | Fax              |
|          |          |            | Washington   |                  |
|          |          |            | DC 20591 USA | ca               |
|          |          |            |              | rol.ryan@faa.gov |
+----------+----------+------------+--------------+------------------+
| Sega,    | Chief    | CAA Fiji   | NAP 0354     | +67-9-721555     |
| Inia     | ATS      |            |              |                  |
|          |          |            | Nadi Airport | +67-9-721500 Fax |
|          |          |            |              |                  |
|          |          |            | Fiji         | chie             |
|          |          |            |              | fats@caaf.org.fj |
+----------+----------+------------+--------------+------------------+
| S        |          | Air New    | Private Bag  | +64-9-256-3328   |
| hepherd, |          | Zealand    | 92007        |                  |
| Mark     |          |            |              | +64-9-256-3935   |
|          |          |            | Auckland 1   | Fax              |
|          |          |            |              |                  |
|          |          |            | New Zealand  | sheph            |
|          |          |            |              | erdm@airnz.co.nz |
+----------+----------+------------+--------------+------------------+
| Spencer, | Manager, | A          | GPO Box 367  | +61-2-6268-4863  |
| Jeff     | Industry | irservices |              |                  |
|          | and      | Australia  | Canberra ACT | +61-2-6268-4365  |
|          | Business |            | 2            | Fax              |
|          | Dev      |            | 601Australia |                  |
|          | elopment |            |              | jeff.spencer@ai  |
|          |          |            |              | rservices.gov.au |
+----------+----------+------------+--------------+------------------+
| Ste      |          | SITA       | Level 11, 37 | +61-2-9240-1427  |
| phenson, |          |            | Pitt Street  |                  |
| Karen    |          |            |              | +61-2-9247-9330  |
|          |          |            | Sydney, NSW  | Fax              |
|          |          |            |              |                  |
|          |          |            | Australia    | sydlms           |
|          |          |            |              | x@typeb.sita.int |
+----------+----------+------------+--------------+------------------+
| Ta       | Admini   | Airways    | P O Box      | +64-9-275-3109   |
| rawhiti, | stration | C          | 53093        |                  |
| Nancy    | M        | orporation |              | +64-9-275-3106   |
|          | anager - |            | Auckland     | Fax              |
|          | Auckland |            | I            |                  |
|          |          |            | nternational | n.tarawhi        |
|          |          |            | Airport      | ti@airways.co.nz |
|          |          |            |              |                  |
|          |          |            | Auckland New |                  |
|          |          |            | Zealand      |                  |
+----------+----------+------------+--------------+------------------+
| Thomas,  | Team     | A          | P O Box      | +61-7-386 63483  |
| Pat      | Leader,  | irservices | 10023        |                  |
|          | Pr       | Australia  |              | pat.thomas@ai    |
|          | ocedures |            | Brisbane     | rservices.gov.au |
|          |          |            | Adelaide     |                  |
|          | Brisbane |            | Street       |                  |
|          | Ocean    |            |              |                  |
|          |          |            | Queensland   |                  |
|          |          |            | 4000         |                  |
|          |          |            |              |                  |
|          |          |            | Australia    |                  |
+----------+----------+------------+--------------+------------------+
| Tueli,   | Air      | CAA Fiji   | Private Mail | +67-9-721555     |
| Inia     | Traffic  |            | Bag          |                  |
|          | Co       |            |              | +67-9-721500 Fax |
|          | ntroller |            | NAP 0354     |                  |
|          |          |            |              |                  |
|          |          |            | Nadi Airport |                  |
|          |          |            | Fiji         |                  |
+----------+----------+------------+--------------+------------------+
| Varcoe,  | Chief    | Air New    | Private Bag  | +64-9-256-3328   |
| Ian      | T        | Zealand    | 92007        |                  |
|          | echnical |            |              | +64-9-256-3935   |
|          | C        |            | Auckland 1   | Fax              |
|          | aptain - |            |              |                  |
|          | Flight   |            | New Zealand  | ian.va           |
|          | Op       |            |              | rcoe@airnz.co.nz |
|          | erations |            |              |                  |
|          | Inter    |            |              |                  |
|          | national |            |              |                  |
+----------+----------+------------+--------------+------------------+
| W        | Project  | Qantas     | Qantas       | +612-95894567    |
| arfield, | Captain  | Airways    | Centre       | (ph/fax)         |
| Captain  | CNS/ATM  | Limited    | Building C/2 |                  |
| Murray   |          |            |              | +1-414-884121 -  |
|          |          |            | 203 Coward   | Mobile           |
|          |          |            | Street       |                  |
|          |          |            |              | warfiel          |
|          |          |            | Mascot 2020  | d@ozemail.com.au |
|          |          |            | Australia    |                  |
+----------+----------+------------+--------------+------------------+
| Wasique, | Program  | ARINC      | 2551 Riva    | +1-410-266-2322  |
| Mohammad | Manager  |            | Road         |                  |
|          | Aviation |            |              | +1-410-573-3106  |
|          | Inf      |            | Annapolis MD | Fax              |
|          | ormation |            | 21061        |                  |
|          | Services |            |              | mxw@arinc.com    |
|          |          |            | USA          |                  |
+----------+----------+------------+--------------+------------------+
| Wicks,   | ATS      | CAA New    | P O Box      | +64-4-560-9454   |
| Len      | A        | Zealand    | 31441        |                  |
|          | pprovals |            |              | +64-4-569-9452   |
|          |          |            | Lower Hutt   | Fax              |
|          |          |            |              |                  |
|          |          |            | New Zealand  | wi               |
|          |          |            |              | cksl@caa.govt.nz |
+----------+----------+------------+--------------+------------------+
| W        | ATS      | A          | GPO Box 367  | +61-2-626 84564  |
| oodford, | Sp       | irservices |              |                  |
| Naomi    | ecialist | Australia  | Canberra ACT | +61-2-626 85695  |
|          |          |            |              | Fax              |
|          |          |            | 2601         |                  |
|          |          |            | Australia    | n                |
|          |          |            |              | aomi.woodford@ai |
|          |          |            |              | rservices.gov.au |
+----------+----------+------------+--------------+------------------+

**AGENDA**

**[Sunday, 6 December]{.underline}**

***1600 -- 1700 Registration***

**[Monday, 7 December]{.underline}**

***0800 - 0900 Registration***

**0900 - 0945 Plenary**

-   Administration

```{=html}
<!-- -->
```
-   Opening Remarks by Co-Chairs

```{=html}
<!-- -->
```
-   Introductions

```{=html}
<!-- -->
```
-   Approval of the ISPACG/13 Agenda and ISPACG/12 Minutes

```{=html}
<!-- -->
```
-   FANS 1/A Implementation Status

-   Open Action Items from ISPACG/12

-   Information and Working Papers

-   Working Group Terms of Reference and Tasks

    ***1030 - 1100 Break***

**1100 - 1230 Working Groups Convene**

***1230 - 1330 Lunch***

**1330 - 1500 Working Groups Convene**

***1500 - 1530 Break***

**1530 - 1700 Working Groups Convene**

***1700 Adjourn for the day***

**[Tuesday, Wednesday and Thursday, 8-10 December]{.underline}**

**0800 - 0830 Reserved for Individual Delegation Meetings**

**0830 - 0900 Executive Session: Co-Chairs and Group Chairmen**

**0900 - 1015 Working Groups Convene**

***1015 - 1045 Break***

**1045 - 1200 Working Groups Convene**

***1200 - 1315 Lunch***

**1315 - 1500 Working Groups Convene**

***1500 - 1530 Break***

**1530 - 1700 Working Groups Convene (Plenary Tuesday Only)**

***1700 Adjourn for the day***

**[Friday, 11 December]{.underline}**

**0830 - 0900 Reserved for individual delegation meetings**

**0900 - 1015 Review ISPACG/13 Draft Report**

-   Plenary Session to discuss the Draft Report

    ***1015 - 1045 Break***

    **1045 - 1130 Review ISPACG/13 Draft Report (cont'd)**

    **1130 -- 1200 Closing**

```{=html}
<!-- -->
```
-   Closing remarks from the floor

-   Closing remarks from the Co-Chairs

***1200 ISPACG/13 adjourns***

**SUMMARY OF THE MEETING**

**Day 1 - Monday, 7 December 1998**

**1. AGENDA ITEM 1 - ADMINISTRATION**

1.1 The thirteenth meeting of the Informal South Pacific ATS
Coordinating Group (ISPACG/13) was opened by Kathy Roil, Airways
Corporation of New Zealand (Airways). Following her opening remarks,
Kathy introduced the co-chairs, Adrian Dumsa, Airservices Australia
(ASA), and Charles Reavis of the Federal Aviation Administration (FAA).

2.  **Kathy Roil** welcomed the participants, applauded the work that
    has been

accomplished since ISPACG/12, and hopes this week to reaffirm the
commitment of the ISPACG participants to deliver ongoing benefits to the
airlines. She reminded the meeting of the need to look into the future
and focus on deriving maximum benefits from the technology available.
Further, this week it will be important to ensure outcomes in three
areas in particular: an RVSM operations concept; an implementation plan
for DARP; and that all barriers to technology identified by the FIT are
resolved, or a schedule is agreeable to their resolution.

3.  **Adrian Dumsa** remarked that TAAATS and the business
    transformation that ASA has

been undergoing focus on the need to provide benefits for the customers.

1.4 **Charles Reavis** thanked Kathy Roil, Mark Goodall, and Nancy
Tarawhiti for their planning and assistance for ISPACG/13. He also
stated that Brian Kendall will be missed as the Australian Co-chair, and
an appropriate way of thanking Brian would be agreed upon during the
course of the week.

1.5 Participants introduced themselves. A list of participants is
included in this report.

1.6 The report from the ISPACG/12 which was held in Honolulu, Hawaii,
during the period

19-23 January 1998 was approved. A letter from IFATCA which contested
the outcome of a Separation Working Group issue was noted. The agenda
for this ISPACG/13 was accepted with no additional items being proposed.

**2. AGENDA ITEM 2 - FANS 1/A IMPLEMENTATION STATUS**

2.1 **Anne Coutin, SEAC,** reported that the VIVO system with CPDLC has
been operational for almost 3 years; HMI problems have been resolved;
concerns about time and energy involved in DARP were raised; ADS is to
be delivered next month, site acceptance and testing in

March 1999.

2.2 **Craig Roberts, ASA,** gave an update on TAAATS Technology. Now
operational in Brisbane; issues on AIDC are being resolved; Melbourne
TAAATS with CPDLC/ADS will be online December 12, but no controllers
have been trained. [Important]{.underline} that airlines
[not]{.underline} log on to YMMM UFN.

2.3 **Paul Radford, Airways,** provided an update on the OCS at
Auckland. OCS should be operational in March/April 1999. Testing is in
progress and will try to organize tours for those with specific
interest. Radar sectors are relocating from Auckland to Christchurch in
2000, but the oceanic operation will remain in Auckland.

2.4 **Carol Dryden, FAA,** briefed on Oakland Center. RNP-10 on 3
December between /R aircraft. Tracks can be reduced to 1° on westbound
tracks to Japan if no forecast convective weather. Oceanic datalink
software testing completed; appreciate cooperation of users. MS ODL
being expanded to other sectors in February 1999.

2.5 **Nancy Graham, FAA,** stated that the survey of available equipment
for ADS has been done and there will be a decision of how to provide ADS
segment by early January. Y2K end-to-end testing ongoing through March
1999. Working Group established to address FANS to ATN transition and
encouraged IATA participation.

6.  **Inia Sega and Inia Tueli, CAAF,** briefed on **WP/6, *Update of
    CNS/ATM***

***Developments in Fiji***.

2.7 **Murray Warfield, QANTAS,** discussed the ITASPS trans-polar
routes; much of the work is based on ISPACG; Iran is bringing CPDLC
onboard; he encouraged the participants to \"keep up the good work\".

2.8 **Adrian Dumsa, ASA,** stated that RNP-10 is now in use across the
Tasman and will be implemented across the entire FIR next year. 20/20
with RNP-10 and 10/10 with RNP-4 domestically are planned to be
implemented next year.

2.9 **Owen Dell, ICAO,** provided an update on ICAO Y2K contingency
plans/program within the Asia/Pacific Region.

**3. AGENDA ITEM 3 - OPEN ACTION ITEMS FROM ISPACG/12**

3.1 Open action items were referred to the appropriate Working Groups
for closer examination and action.

**4. AGENDA ITEM 4 - INFORMATION AND WORKING PAPERS**

4.1 Presentation and an overview of the working papers followed. A
complete list of the documentation provided for this meeting is
available at Appendix A. Working papers were referred to the appropriate
Working Groups for closer examination and action.

**5. AGENDA ITEM 5 - WORKING GROUP TERMS OF REFERENCE AND TASKS**

5.1 Working Group Chairs were agreed as follows:

-   Separation WG: Gus Nezer/Adrian Dumsa

```{=html}
<!-- -->
```
-   DARP WG: Mark Goodall

-   FIT WG: Brad Cornell

5.2 The Working Group Chairs were then asked to develop a schedule of
tasks for the week, including the open action items from ISPACG/12, and
the Information and Working papers. Issues to be addressed by each group
were as follows:

+-----------------------------------+-----------------------------------+
| [Separation WG]{.underline}       | [DARP WG]{.underline}             |
+-----------------------------------+-----------------------------------+
| i\. Weather Deviation --          | i\. Establishment of an ATS       |
| Phraseology                       | supplied single                   |
|                                   |                                   |
| ii\. RVSM Implementation Strategy | group reroute: LAX-SYD SYD/LAX    |
|                                   | AKL-                              |
| iii\. Proposed Vertical Collision |                                   |
| Risk Model                        | LAX LAX/AKL                       |
|                                   |                                   |
| Associated with Formation Flights | ii\. Providers and users to       |
| in PAC                            | develop procedures                |
|                                   |                                   |
| RVSM Airspace                     | for user supplier DARP            |
|                                   |                                   |
| iv\. Proposed Collision Risk      | iii\. DARP Procedures -- Phase 1  |
| Model for Two                     |                                   |
|                                   | iv\. DARP Procedures -- Phase 2   |
| Aircraft in Vertical Alignment    | and 3                             |
| for their                         |                                   |
|                                   |                                   |
| Entire PAC Oceanic Crossing       |                                   |
|                                   |                                   |
| v\. Develop future ATM backup     |                                   |
| procedures                        |                                   |
|                                   |                                   |
| and policies                      |                                   |
+-----------------------------------+-----------------------------------+
| [FIT WG]{.underline}              |                                   |
|                                   |                                   |
| i\. ATS automation systems        |                                   |
| supporting                        |                                   |
|                                   |                                   |
| CPDLC                             |                                   |
|                                   |                                   |
| ii\. Introduce AIDC via AFTN      |                                   |
|                                   |                                   |
| iii\. Monitor and report on the   |                                   |
| status of                         |                                   |
|                                   |                                   |
| industry initiatives re SATVOICE  |                                   |
|                                   |                                   |
| iv\. Guidance material for the    |                                   |
| use of                            |                                   |
|                                   |                                   |
| SATVOICE                          |                                   |
|                                   |                                   |
| v\. FIT Work Activity             |                                   |
|                                   |                                   |
| vi\. Interoperability             |                                   |
| Requirements for ATS              |                                   |
|                                   |                                   |
| Application                       |                                   |
+-----------------------------------+-----------------------------------+

5.3 Following a short break after which a schedule was presented and
agreed, the plenary adjourned to allow the Working Groups to convene to
plan the week\'s activities.

**6. Days 2, 3 and 4 - Tuesday, 8 December through Thursday, 10
December**

6.1 Working Groups convened to progress their work. The ISPACG co-chairs
met with the working group Chairs on an \"as required\" basis. These
meetings provided the opportunity for the working group Chairs to update
the Co-chairs on the activities of the individual groups, and to ensure
that coordination occurred between the working groups.

6.2 A plenary session was convened on Tuesday, 8 December, at 1530, to
update the meeting on the overall progress of the working groups. The
working group Chairs provided briefings on progress, and the following
new issues were identified and discussed for consideration as a part of
the future work program.

6.2.1 General. The ISPACG work program has been largely focused on
FANS-1 deliverables for the past few years. The ISPACG charter focuses
on all users however, and now that the FANS-1 program is well in hand,
it was suggested that ISPACG needs to consider wider issues of benefit
to all airspace users. The commitment to delivering on the FANS-1
program will remain.

6.2.2 FMS arrival/departure procedures. The airlines requested that
ISPACG develop some broad principles for implementation by service
providers in their approach areas.

6.2.3 Communication standards for non high-tech aircraft. It was
proposed that the HF service provided to non-datalink aircraft could be
reviewed, with a view to identifying areas where the service delivered
by the different States could be further standardized and improved.

6.2.4 Elimination of ATS routes; move toward random routes. The DARP
program should be extended to an end goal that delivers random routes to
all aircraft, including those that are not FANS 1/A equipped.

6.2.5 Joint use of military airspace. The airlines requested that ISPACG
look into military exclusive airspace within the region with a view to
coordinating more access to the airspace at times when it is not
required by the military authority.

6.2.6 Regional Planning Documents. The region at this stage does not
have a regional contingency plan, concept of operations plan, and
implementation plan through mid-term. It was proposed that ISPACG
consider adding these three documents to the future work program

6.2.7 Future airspace design issues. The airlines and the USAF requested
that a standard be developed for future airspace and procedures design.
Such a standard could consider issues such as individual aircraft speed
restrictions affecting faster following aircraft, the elimination of
fixed routes once random routes were widely available, and the need to
accommodate varying aircraft technology standards.

6.2.8 The continuation of the Boeing contribution to FIT, or an
alternative. The Boeing representative advised that Boeing is reviewing
their support of the FIT. This group has been critical in the resolution
of ongoing issues with communication interoperability and is seen as
equally as critical to future progress. In future, consideration will
also need to be given to ongoing monitoring of other technical
performance issues.

6.3 The plenary closed at 1630 with the co-chairs agreeing to consider
the issues raised for the future work program.

**7. AGENDA ITEM 7 - REVIEW ISPACG/13 DRAFT REPORT**

7.1 ISPACG/13 reconvened in plenary at 0900, Friday, 11 December, to
review the draft report of the meeting. Appropriate amendments were made
to the draft as required.

7.2 Each of the working group chairs reported on the achievements of the
individual groups.

7.3 The co-chairs reported back on the issues raised in the Tuesday
plenary session and noted in section 6 of this report as follows:

7.3.1 General. It is agreed that the ISPACG work program should focus on
the wider group of airlines that operate in the region. Participants are
encouraged to submit work papers in future that will provide benefits
not only to the FANS 1/A aircraft, but also the wider customer group.

7.3.2 FMS arrival/departure procedures. The airlines are requested to
submit a working paper at ISPACG/14 describing their needs in this area.

7.3.3 Communication standards for non high-tech aircraft. Any issues in
this area are seen as specific to individual providers, and the airlines
are encouraged to raise them directly with the providers.

7.3.4 Elimination of ATS routes; move toward random routes. The DARP
working group were tasked with considering the wider application of DARP
to all aircraft. They have included the outcomes of their work in the
DARP program.

7.3.5 Joint use of military airspace. This is also seen as specific to
individual states and should be raised by the airlines with individual
states where appropriate.

7.3.6 Regional Planning Documents. ASA will prepare a concept paper for
ISPACG/14.

7.3.7 Future airspace design issues. The co-chairs consider that these
issues generally do not require consideration as a separate work item.
ISPACG members are encouraged to consider these issues as a part of
their ongoing work. Fixed routes were considered as a part of the DARP
work program and are covered in the DARP WG report.

7.3.8 The continuation of the Boeing contribution to FIT, or an
alternative. ISPACG noted with thanks the extremely valuable
contribution made by Boeing in support of the FIT program. It is
considered important that this work continue. To this end, ISPACG
participants were requested to ensure that their organizations are aware
of the contribution that Boeing has made.

The co-chairs advised the meeting that a letter has been prepared from
ISPACG to Boeing to thank them for their support.

**8. AGENDA ITEM 8 - CLOSING**

8.1 Closing remarks were made by each of the co-chairs, noting the work
of the group and the maintenance and outcomes that had been reached
during the meeting.

8.2 ISPACG noted the significant contribution of Brian Kendal to the
ISPACG organization, and to ANS delivery in the region in general. The
co-chairs have written a letter of thanks and commendation to Brian on
behalf of ISPACG and will present a plaque to him recognizing this
contribution.

3.  Closing remarks from the floor were taken. Of particular note are
    the following

comments made by Captain Ken Alexander:

-   Normally, state aircraft are not addressed or a remark exempting
    state aircraft is included

in implementing regulations for equipage requirements.

-   The term "exempted" sometimes misrepresents the actual situation and
    expectations of

the nation issuing the regulation.

\- When equipage is not mandatory, often at some point in time,
non-equipage results in a reduced level of access, service, or even
exclusion from some portions of the affected airspace.

\- Often the nation states have specific expectations for the equipage
of particular categories of state aircraft.

**-** It is essential to military planning and operations that the
nation states make known their intentions for military aircraft and the
consequences of non-equipage.

\- If your nation\'s firm expectation is state aircraft will be equipped
or the operator will incur restrictions in level of service or access to
airspace, clearly state your expectations for both transport and
tactical aircraft and identify how the regulation applies or does not
apply to that category of aircraft in the implementing documents.

\- Encourage the nations to issue a notice of proposed rulemaking a
minimum of 7 years in advance of actual implementation.

\- Propose the nations recognize in their implementing regulations a
blanket exemption permitting an additional 5 years past the civil
implementation date for state aircraft to equip.

\- It is also essential the implementing regulations and exemption
procedures be harmonized to the maximum extent possible with the other
ICAO regions.

\- With provisions described above, then the military can properly plan
for funding and implementation to not only not be a hazard to the
operation of your civil aircraft but to take advantage of the
capabilities these new CNS systems offer.

\- On behalf of the USAF and DOD, Col Alexander thanked the members of
the ISPACG for supporting this forum\--a forum where issues can be
discussed early on and plans can be developed to resolve potential
problems\--and he also thanked New Zealand Airways for hosting the
meeting.

8.4 With regard to the continuing activities of the group, the co-chairs
proposed the next meeting, ISPACG/14, to be held in Australia in
September 1999. Exact dates will be advised by ASA.

3.  ISPACG/13 was formally closed at 1030, Friday, 11 December 1998.

**MEETING DOCUMENTATION**

  ----------- ------------------------------------------- ----------------
  **Paper**   **Title**                                   **Presented by**

  WP/1        Dynamic Airborne Route Planning (DARP)      United States
              Procedures -- Phase 2 and 3                 

  WP/2        Dynamic Airborne Route Planning (DARP)      United States
              Implementation -- Phase 1                   

  WP/3        FANS Interoperability Team (FIT) Work       New Zealand
              Activity                                    

  WP/4        Interoperability Requirements for ATS       RTCA/EUROCAE
              Applications                                

  WP/5        Pacific Reduced Vertical Separation Minimum United States
              (RVSM) Implementation Strategy              

  WP/6        CNS/ATM Developments                        Fiji

  WP/7        Proposed Vertical Collision Risk Model      United States
              Associated with Formation Flights in PAC    
              RVSM Airspace                               

  WP/8        Proposed Collision Risk Model for Two       United States
              Aircraft in Vertical Alignment for their    
              Entire PAC Oceanic Crossing                 

  WP/9        Estimating the Probability and Duration of  United States
              Horizontal Overlaps Experienced by          
              Airplanes Traveling on Intersecting Oceanic 
              Routes                                      

  WP/10       Progress in the Development of a Model for  United States
              Estimating the Risk of Collision at         
              Intersections of Oceanic Air Routes         

  WP/11       Y2K Contingency Plan                        Fiji

  WP/12       Longitudinal Distance-Based Separation      Australia
              Minima in an RNP RNAV Environment: Papers   
              Relating to a Proposal to Extend the Range  
              of Applicable Minima                        

  WP/13       Operating Context for Use of ADS in the     Australia
              Provision of Air Traffic Services           

  WP/14       On the Display of ADS Position Information  Australia
              in a Screen-Based ATS Environment           

  WP/15       Report on the Implementation of RNP 10 in   Australia
              the Tasman Sea Airspace                     

  WP/16       Updated Information on the ADS Operating    Australia
              Context PANS-RAC Doc 4444 Amendment         
              Proposal                                    

                                                          

  IP/1        ACAS (TCAS) In-Trail Climb (ITC)In-Trail    United States
              Descent (ITD)                               

  IP/2        Status of the Operational Trials and        United States
              Demonstrations Utilizing 10-Minute          
              Longitudinal Separation Without Mandatory   
              Mach Number Technique (MNT) in the Oakland  
              FIR                                         

  IP/3        Weather Deviation -- Phraseology            New Zealand

  IP/4        Reduced Vertical Separation Minima          ICAO Bangkok

  IP/5        Assurance of Safe RVSM Implementation       United States

  IP/6        Guidance Material for the Use of SATVOICE   Qantas Airways
                                                          Ltd

  IP/7        Inmarsat Year 2000 Project                  Inmarsat

  IP/8        Draft Guidance on Operational Accommodation Australia
              of FANS-1/A Systems in an ATN SARPs         
              Environment                                 
  ----------- ------------------------------------------- ----------------

**REPORT**

**of the**

**FIT WORKING GROUP**

**[FIT WORKGROUP REPORT]{.underline}**

**Requests For Change (RFCs)**

The following RFC proposals for amending the SPOM were processed. The
RFC forms are included as an attachment.

+-------+-------------------------------------------------+-----------+
| **RFC | **Description**                                 | **A       |
| \#**  |                                                 | ccepted** |
+-------+-------------------------------------------------+-----------+
| 98/12 | Combined with 98/22                             |           |
+-------+-------------------------------------------------+-----------+
| 98/20 | Modify CPDLC message to add, "MAINTAIN (present | Yes       |
|       | altitude)" to conditional clearances. Modify    |           |
|       | the procedure for conditional clearances to     |           |
|       | proceed UL messages 21,22,24 and 25 with UL 19. |           |
|       | The proposed format is "Maintain X. At Y, do Z. |           |
|       | For example (UL 19 followed By UL 22) "MAINTAIN |           |
|       | FL 310. AT 150W CLIMB TO AND MAINTAIN FL350."   |           |
+-------+-------------------------------------------------+-----------+
| 98/22 | Refer DARP Group report                         |           |
+-------+-------------------------------------------------+-----------+
| 98/23 | Clarification of SPOM. Emergency free text on   | Yes       |
|       | Airbus aircraft. FANS A implementation for      |           |
|       | downlink message element 68 (free text with D   |           |
|       | Urgency Attribute) is the same as that of       |           |
|       | FANS-1 . Downlink message element 68 is only    |           |
|       | accessible via the emergency page on Airbus     |           |
|       | aircraft.                                       |           |
+-------+-------------------------------------------------+-----------+
| 98/24 | Editorial corrections.                          | Yes       |
+-------+-------------------------------------------------+-----------+
| 98/25 | Editorial correction.                           | Yes       |
+-------+-------------------------------------------------+-----------+
| 98/26 | Editorial correction.                           | Yes       |
+-------+-------------------------------------------------+-----------+
| 98/27 | Update description of flight crew display and   | Yes       |
|       | airborne architecture for FANS A.               |           |
+-------+-------------------------------------------------+-----------+
| 98/28 | Controllers shall append the REPORT REACHING    | Yes       |
|       | message element to any vertical change          |           |
|       | clearance so that flight crews have access to   |           |
|       | the pre-formatted downlink report.              |           |
|       |                                                 |           |
|       | Add to the SPOM CPDLC section.                  |           |
+-------+-------------------------------------------------+-----------+

**[Network Performance Summary]{.underline}**

Perth GES is running three low speed channels on the Indian Ocean Region
(IOR) with one high speed channel awaiting cutover and two low speed
channels on the Pacific Ocean Region (POR) also with a high speed
channel awaiting cutover. Aero I/H+ fax and pcdata capability was
installed on 9 December 1998.

SITA exceeded 95% performance figures for Sept, Oct, and Nov. October
figures show 98.09% aggregate uplink success rate. ARINC exceeded 95%
performance figures for Sep, Oct, and Nov. October figures show 98.01%
aggregate uplink success rate.

The performance differential between DSPs is now negligible and would
indicate that recent efforts by the DSPs to improve performance have
been successful. Combined uplink/downlink performance has improved above
the 95% requirement since the last FIT meeting.

Arinc has a dedicated team analyzing messages on a daily basis. Where
possible, Problem Reports are being written on every problem found since
mid-October 1998. Arinc recognises the importance of writing PRs for the
FIT.

SITA has a global customer support team with three customer support
people in Asia/Pacific region. They investigate and report back to the
airline and CAA customer and the CRA on every FANS fault reported. In
addition to existing FANS support, SITA is adding more staff to form a
dedicated FANS team. SITA recognises the importance of writing PRs for
the FIT.

Regular telecons have been scheduled between SITA and ARINC; both DSPs
are confident that significant issues are being addressed and progress
is being made on major action items.

The revised performance figures developed at FIT 4 (Fiji) were
promulgated as requirements, however the DSPs understood the figures to
be targets only. Boeing and the ATS providers reiterated the position
and the DSPs now accept the new performance figures as requirements.
There was some speculation from the group that ATS providers may
eventually write these performance figures into future contractual
arrangements. Some concern was voiced by the DSPs that the higher
figures might not be met consistently for reasons beyond a DSP\'s
control, such as problem avionics.

The FIT acknowledged that DSPs can run at 100% for periods of time, but
just one aircraft with avionics problems can significantly lower the
system performance figures for the period of time that the aircraft
continues to operate, especially when the relatively low numbers of
uplink messages currently being processed are considered.

Processes for the identification and notification to the airlines of
problem aircraft are in place and being optimized. The DSPs acknowledge
the need to notify airlines of these aircraft in a timely manner. Once
notified, the airlines have a responsibility to remove problem aircraft
from the system as soon as possible.

One aircraft was identified by ARINC as suffering serious avionics
problems. The appropriate airline was notified, but it took more than a
week for the aircraft to be taken out of service. The DSPs were advised
to raise a new PR if the problem still exists after the relevant airline
has been notified. Statistics are currently being gathered on the number
of problems seen. A measure by which to base a decision on removing a
particular problem aircraft from service needs to be developed.

If the performance requirements cannot be met consistently, then the
individual components (DSPs, avionics, ground systems etc.) responsible
for degrading the system need to be identified so that long standing
problems can be rectified.

Both DSPs have seen a large number of intercepts during analysis. Charts
were presented showing comparisons of intercepts. Results indicate that
definite progress is being made in solving network problems.

A request was submitted for Arinc pie charts that track intercepts
continue to be disseminated. SITA produced a similar pie chart. SITA and
ARINC agree to the monthly reporting of data.

ARINC's FANS Router will be upgraded to include NACK intercept handling.
Messages that are NACK'd on one DSP media (e.g., ARINC VHF) will be
forwarded to the second DSP media (e.g., SITA SATCOM) for delivery.

**Action Item - Airlines** to provide the relevant contact information
for DSP notification of aircraft suffering avionics problems.

**[Problem Reports (PRs)]{.underline}**

The FIT considered the list of current PRs. Nineteen PRs were closed. A
number of current PRs remain open pending further audit data.

**Action Item arising from PRs -**

**Kevin Grimm** to investigate auto-handoff timers between Oakland and
Tahiti.

**Boeing** to confirm part numbers with Qantas\' vendor regarding a
particular MU that experienced problems on a specific day.

**Paul Radford** to check if NZ system automatically uplinks an error
message in response to a duplicate message.

**Paul Radford** will provide a working paper be presented to the next
FIT for a decision on AIDC messages to accommodate Block altitudes and
offsets/weather deviations. ATS providers will need to discuss the
issues prior to the meeting so that a binding decision can be made.

**Craig Roberts** to check ADIS and TAAATS responses to duplicate
messages. Is an error message automatically sent? When? (A software
change has been proposed for TAAATS to look at the CRCs and decide
whether a particular message is a duplicate).

**Georges Claustre** to check VIVO system to find out when an error
message is automatically transmitted in response to a duplicate
downlink.

**[Eurocae SC-189 Interoperability Requirements for
FANS-1/A]{.underline}**

Several FIT members have been involved in the development of this paper.
The FIT recommends that the Eurocae SC-189 Interoperability paper be
adopted by ISPACG.

**[End-to-End Configuration Management]{.underline}**

An end-to-end configuration management process was proposed at the FIT
meeting in Fiji. One purpose of a configuration management process is to
establish and maintain the configuration identification of system
component configuration items in use (e.g., hardware / software) that
provide the desired end-to-end system performance. Another equally
important purpose of a configuration management process is to develop
and document the procedures used to ensure that the introduction of any
change into the end-to-end system does not compromise the desired
end-to-end system performance.

The FIT group approved the first version of the FANS 1/A configuration
control document, which is provided as attachment 1 to this report.

**[AIDC]{.underline}**

Some operational information, such as block levels, offsets and weather
deviations, cannot currently be accommodated by the AIDC message set.

The options are to propose a change to field 14 to allow two optional
fields to cover block levels and weather deviations or to leave the AIDC
message set as it is and to continue using voice for coordinating these
specific items.

Airways Corp. proposed that a working paper be presented to the next FIT
for a decision. ATS providers will need to discuss the issues prior to
meeting so that a binding decision can be made.

ABI and CPL messages are required for DARPS, as the EST message does not
contain the route field.

The airlines are concerned that any delay in the full implementation of
AIDC may adversely affect the introduction of DARPS phases 2 and 3.

A bilateral agreement between NZ and Australia is intended to be in
place by the end of the first quarter of 1999.

**[SATCOM]{.underline}**

As a \"get home strategy\" following an HF set failure, the airlines
want to be able to dispatch aircraft with only one operational HF set,
using SATCOM voice as the back-up communications medium. If the
remaining HF set fails then SATCOM voice would be used for ATS comms.
Dual HF failures are extremely infrequent.

To enable this operating scenario a change is required to the AFM
limitation (SATCOM can only be used in emergency or unusual situations),
and the MMEL policy.

Further more, the FIT recommends adopting SC-165 \"Betty\".

**Action Items - Tom Kraft** and **Roy Grimes** to investigate the
feasibility of revising AFM and MMEL policy to allow SATCOM voice as an
alternate to HF voice in this situation.

**SITA (Vaughan Maiolla)** to notify customers of the process for
acquiring a PIN for secure SATCOM use.

**Lindsay Norrish** will continue to advise ATSUs of aircraft telephone
numbers when authorized by the airlines.

**[Airline Ops Approval]{.underline}**

The FIT recommends that an operational approval process and guidance
material for CPDLC be developed similar to the information recently
developed for RNP 10. Tom Kraft provided the group with a copy of
AC120.COM that provides guidance on Ops approval process for comments.

**ATTACHMENT 1**

**FANS-1/A Configuration Management**

**Document**

**FANS 1/A End-To-End Configuration Management List**

**1. BACKGROUND**

1.1 The FANS 1/A system consists of several individual components that
must work together end-to-end (pilot to controller) to achieve the
required level of performance. If all the components are working
together as required, flight crews and controllers will have optimum
communication and surveillance tools.

1.2 FANS 1/A end-to-end system performance, stability, and reliability
can be affected by changes to individual components of the system. A
comprehensive system component configuration management process is
required to ensure FANS 1/A maintains the desired end-to-end
performance.

1.3 One purpose of a configuration management process is to establish
and maintain configuration identification of system component
combinations (e.g., hardware / software) in use, or alternative
configurations which provide the desired end-to-end system performance.
Another equally important purpose of a configuration management process
is to develop and document the procedures to be used to ensure that the
introduction of change into the end-to-end system does not reduce system
performance below the required level.

1.4 Each stakeholder has a responsibility to conduct configuration
management. In addition, we propose that the CRA maintains for reference
the current methodology by which each stakeholder ensures configuration
identification and configuration management within their system segment.
The CRA will also receive and make available within the FIT the most
recent notification of major system component change, as issued by the
responsible stakeholder. The CRA will assist in coordinating end-to-end
system testing, if requested. In cases where end-to-end testing is not
practical or required, the stakeholder making the change must indicate
that internal testing and/or simulation has been accomplished or
analysis has been done which shows end-to-end testing is unnecessary.

**2. AIRCRAFT MANUFACTURE**

2.1 **Boeing**

2.1.1 Flight Management Computer - FMC

> Following is a list of the FMC hardware and software part numbers
> recommended for FANS operations. Operators who wish to submit problem
> reports to the FIT must ensure aircraft meet the recommended
> configuration.
>
> 737 - Not yet implemented
>
> 747 - Load 14 (note get full P/N)
>
> 75767 - Pegasus \# (note get full P/N)
>
> 777 - AIMS software BP 98 (note get full P/N)

2.2 **ACARS**

2.2.1 Following is a list of the ACARS management unit hardware and
software part numbers recommended for FANS operations. It is recommended
that operators ensure aircraft are fitted with these part numbers prior
to FANS operations.

Vendor Hardware s/w version

Collins 622-9496-003 003

Honeywell: 7516100-18033 N/A

2.3 **SATCOM**

2.3.1 Following is a list of the SATCOM satellite data unit hardware and
software part numbers that will provide optimal performance. It is
recommended that operators ensure aircraft are fitted with these part
numbers prior to FANS operations.

Collins: 622-8848-002

Collins: 622-8848-001

Honeywell: 7516100-20050

2.4 **Airbus**

2.4.1 A list of Airbus ATS components will be added when they are
certified.

**3. DATA LINK SERVICE PROVIDERS**

3.1 **ARINC**

3.1.1 The key components within ARINC's segment of the FANS 1/A system
which will be listed in the configuration control list include the FANS
router, the Central Processing System (CPS) Back-End Processor (BEP),
and the Ground Earth Station (GES).

3.2.1 FANS router

An update for the FANS router is scheduled for first quarter 1999.

3.2.2 Central Processing System Back-End Processor

Configuration information will added when the next change occurs.

3.2.3 Ground Earth Station

> Following is the list of all the GESs in the ARINC consortium.
> Configuration information to be provided.

-   **Santa Paula**

-   **Southbury**

-   **Eik**

-   **Goonhilly**

-   **Yamaguchi**

-   **Sentosa**

-   **Nonthaburi (pending)**

3.2 **SITA**

3.2.1 The key components within SITA's segment of the FANS 1/A system
which will be listed in the configuration control list include the
AIRCOM Service Processor (ASP), VHF AIRCOM Service Processor (VASP),
Satellite AIRCOM Service Processor (SASP), Direct Host Processor (DHP),
CAA Server (CAAS), and the GES's.

3.2.2 AIRCOM Service Processor (ASP)

Configuration information will be added when the next change occurs.

3.2.3 VHF AIRCOM Service Processor (VASP)

Configuration information will be added when the next change occurs.

3.2.4 Satellite AIRCOM Service Processor (SASP)

Configuration information will be added when the next change occurs.

3.2.5 Direct Host Processor (DHP), CAA Server (CAAS)

Configuration information will be added when the next change occurs.

3.2.6 Ground Earth Station

Following is a complete configuration list for all the GESs in the SITA
consortium.

> **Perth GES (Australia)**

Indian Ocean Region (IOR): 1 Psmc 600, 2 Pd 600, 1 Pd 10,500 (installed
but not active.

> Pacific Ocean Region (POR): 1 Psmc 600, 1 Pd 600, 1 Pd 10,500
> (installed but not active.
>
> **Aussaguel GES (France)**

Atlantic Ocean Region East (AORE): TBA

Atlantic Ocean Region West (AORW): TBA

For backup purposes, on the

POR: KDD Yamaguchi GES (Japan): TBA

**4. AIR TRAFFIC SERVICE PROVIDERS**

4.1 This portion of the configuration list will document any changes to
the Air Traffic Service Provider\'s hardware or software that may affect
ATS message traffic.

4.1.1 Oakland,

New "Multi sector" software was installed on November 24^th^ 1998.

4.1.2 Tahiti,

> A software change which adds Automatic Dependent Surveillance (ADS) is
> scheduled for March 1999.

4.1.3 Fiji,

> A new "dual sector oceanic and local area" ATS system is scheduled for
> activation in June 1999

4.1.4 Brisbane,

A new ATS system, TAAATS, is scheduled to come online March 1999.

4.1.5 New Zealand

A new ATS system, OCS, is scheduled to come online March/April 1999.

**ATTACHMENT 2**

**RFCs PROPOSED FOR THE SPOM**

+-----------------------------------------------------+-------+-------+
| # Request For Change form                           | **RFC | 98020 |
|                                                     | Nr:** |       |
+-----------------------------------------------------+-------+-------+

To be used whenever requesting a change to any part of SPOM. This form
may be photocopied as required.

<table style="width:100%;">
<colgroup>
<col style="width: 19%" />
<col style="width: 6%" />
<col style="width: 1%" />
<col style="width: 6%" />
<col style="width: 4%" />
<col style="width: 4%" />
<col style="width: 24%" />
<col style="width: 3%" />
<col style="width: 13%" />
<col style="width: 16%" />
</colgroup>
<tbody>
<tr class="odd">
<td><strong>1. SUBJECT:</strong></td>
<td colspan="9"></td>
</tr>
<tr class="even">
<td colspan="10">Modify CPDLC message to add, “MAINTAIN (present
altitude)” to conditional clearances.</td>
</tr>
<tr class="odd">
<td colspan="5"><strong>2. REASON FOR CHANGE:</strong></td>
<td colspan="5"></td>
</tr>
<tr class="even">
<td colspan="10">Some flight crews have missed the restriction “AT” in a
CPDLC clearance.</td>
</tr>
<tr class="odd">
<td colspan="10"><strong>3. DESCRIPTION OF PROPOSAL: [attach additional
pages if necessary]</strong></td>
</tr>
<tr class="even">
<td colspan="10"><p>Modify the procedure for conditional clearances to
proceed UL messages 21,22,24 and 25 with UL 19. The proposed format is
“Maintain X. At Y, do Z. For example (UL 19 followed By UL 22) “MAINTAIN
FL 310. AT 150W CLIMB TO AND MAINTAIN FL350.”</p>
<p>Due to continuing problems with conditional clearances we have
contracted with Dr. Peter Polson, Department of Psychology, University
of Colorado, to assist in the resolution of this issue. The following
memo is the result of this collaboration and provides the rational for
the proposed change.</p>
<blockquote>
<p>Many recent incidents of clearance violations by CPDLC system
equipped aircraft have involved conditional clearances. The goal of this
memo is to make the case that the wording of these clearances should be
modified for use with datalink. The argument is based on a model of the
mental processes involved in receiving and responding to datalink and
voice clearances. The next section describes the proposed modified
wording for conditional, datalink clearances. The following section
describes the model. The final section employs the model to make the
case for these changes.</p>
<p>Proposes Change in Wording of Conditional Clearances</p>
<p>The following description of the proposed changes just focuses on
altitude clearances that are conditional on reaching a waypoint or
longitude. The proposal can easily be generalized to deal with other
types of clearances.</p>
<p>The current format of conditional altitude clearance is<br />
“AT 150W, CLIMB TO AND MAINTAIN FL350.”</p>
</blockquote>
<p>The proposed format is<br />
“MAINTAIN FL310. AT 150W CLIMB TO AND MAINTAIN FL350.”</p>
<blockquote>
<p>Generalizing the above, we obtain<br />
“Maintain X. At Y, do Z.”</p>
<p>We do not expect our proposed modifications to impose significant
additional workload on a controller.</p>
<p>Responding to Voice and Datalink Clearances</p>
<p>Processing a clearance requires the rapid execution of a complex
sequence of mental processes. These processes can be divided into three
stages:<br />
(1) perceiving, (2) understanding, and (3) responding.</p>
<p>The perceiving stage takes a physical input (audio signal or text on
a display) and constructs a mental representation of the words and
numbers in a message. The understanding stage takes this sequence of
words and numbers as input and generates representations of the meaning
of each element of the clearance. The responding stage takes the
representation of a clearance created by the understanding stage and
generates an action plan to comply with it.</p>
<p>Our argument for the changes in wording of conditional clearances
focuses on the perceiving stage since the largest differences between
voice and datalink are in this initial stage of processing. Speech
recognition and printed word recognition are very different skills, and
each has its own characteristic failure modes. Once the words in a voice
or datalink clearance have been perceived, the skills and knowledge
required to understand and respond to a clearance share a large number
of common elements. There two major differences in the last two stages.
The first is that a voice clearance must be stored in long term memory.
The second is that there is no equivalent of a readback in the datalink
environment.</p>
<p><em>Perception of a Voice Clearance</em>. In a voice environment, ATC
has control over the pilot’s initial perception of the clearance. The
clearance is transmitted one word at a time to the pilot. The
controller’s voice inflection patterns may be used to communicate
importance, intent, and structure of the message.</p>
<p>Two essential features of handling a voice clearance are forced by
the ephemeral nature of the information. First, all other activities in
the cockpit are interrupted, and the pilots’ focus their full attention
on the ATC message. Second, the initial processing of a voice clearance
requires that it be successfully stored in the PNF’s memory and read
back to the controller. Thus, both PF and the controller can verify the
PNF’s initial understanding of and memory for the clearance.</p>
<p><em>Perception of a Datalink Clearance</em>. The initial perception
of a clearance presented on a visual display is under the control of the
pilot. Each word in the message must be fixated for at least 1/5 of a
second in order to be understood. Skilled readers have a strong tendency
to skip short function words, such as “at”, which could cause the
misunderstanding of conditional clearances. In addition, a text message
can be skimmed, skipping elements of a clearance as a pilot looks for
expected contents. The controller has no opportunity to verify the
crew’s initial understanding of a datalink clearance since there is no
equivalent of a readback.</p>
<p>Pilots who have extensive experience with the CPDLC system will
develop specialized reading skills for clearances that cause them to
fixate every word in a text presented on the CDU display. However, under
conditions of stress, distraction and/or fatigue, even experienced users
may revert to normal skilled reading patterns skipping short function
words or skimming the text looking for expected contents.</p>
<p>Analysis of the New Wording of Conditional Clearances</p>
<p>In a voice clearance, the “At” is the first word of a sentence and
would be inflected by the controller. Furthermore, a controller would
detect a missing conditional clause in a readback and correct the
pilot’s misunderstanding of the clearance.</p>
<p>In a datalink environment, the conditional nature of the clearance is
signaled by a short function word, which tend to be skipped during
skilled reading because they are redundant in typical texts. Skilled
readers tend to skip short function words, such as “at”, and skimming
texts just increases the likelihood of skipping function words.</p>
<p>This error can be prevented by modifying the terminology of a
conditional clearance in the datalink environment. The new terminology
should be, “Maintain X. At Y, do Z. “ “Maintain” signals a conditional
clearance and is a much larger target for the rapidly moving focus of
the eyes. After perceiving the “Maintain…” clause, pilots would be
expecting the “At Y,” clause. Thus, it is much less likely that the “At”
would be skipped.</p>
<p>Conclusions</p>
<p>There are major differences in speech perception and the initial
perceptual processes in skilled reading. Function words are often
skipped in skilled reading, and texts can be skimmed looking for
expected contents.</p>
<p>The SOPs for handling voice clearances and the wording of these
clearances have evolved over many years. Pilots have extensive
experience with voice clearances and are well aware of possible failure
modes. However, reading is a very different skill than listening. The
format of displays, the phraseology of datalink clearances, and training
are going to have to evolve to reflect those differences.</p>
</blockquote></td>
</tr>
<tr class="odd">
<td colspan="2"><strong>4. REFERENCE(S):</strong></td>
<td colspan="8"></td>
</tr>
<tr class="even">
<td colspan="4"><strong>5. PERSON INITIATING:</strong></td>
<td colspan="4">Mike Cuddy</td>
<td><strong>DATE:</strong></td>
<td>7 October, 1998</td>
</tr>
<tr class="odd">
<td colspan="3"><strong>ORGANISATION:</strong></td>
<td colspan="3">UAL</td>
<td><strong>TEL/FAX/EMAIL:</strong></td>
<td colspan="3">Mike.cuddy@ual.com</td>
</tr>
</tbody>
</table>

<table style="width:100%;">
<colgroup>
<col style="width: 4%" />
<col style="width: 22%" />
<col style="width: 4%" />
<col style="width: 4%" />
<col style="width: 7%" />
<col style="width: 19%" />
<col style="width: 1%" />
<col style="width: 19%" />
<col style="width: 0%" />
<col style="width: 16%" />
</colgroup>
<tbody>
<tr class="odd">
<td colspan="5"><strong>6. CHAIRPERSON ISPACG WG:</strong></td>
<td colspan="2">Mark Goodall</td>
<td><strong>DATE REC’D:</strong></td>
<td colspan="2">8 Oct 98</td>
</tr>
<tr class="even">
<td colspan="4"><strong>7. CONSULTATION</strong></td>
<td colspan="5"><strong>RESPONSE DUE BY DATE:</strong></td>
<td>ISPACG/13</td>
</tr>
<tr class="odd">
<td></td>
<td><strong>Organisation</strong></td>
<td colspan="4"><strong>Name</strong></td>
<td colspan="3"><strong>Agree/Disagree</strong></td>
<td><strong>Date</strong></td>
</tr>
<tr class="even">
<td></td>
<td><p><strong>FAA</strong></p>
<p><strong>CAAF</strong></p>
<p><strong>SEAC</strong></p>
<p><strong>Airways</strong></p>
<p><strong>Airservices</strong></p>
<p><strong>QANTAS</strong></p>
<p><strong>ANZ</strong></p></td>
<td colspan="4"><p><strong>Karen Doherty</strong></p>
<p><strong>Inia Sega</strong></p>
<p><strong>Georges Claustre</strong></p>
<p><strong>Mark Goodall</strong></p>
<p><strong>Ron Rigney</strong></p>
<p><strong>Murray Warfield</strong></p>
<p><strong>Ian Varcoe</strong></p></td>
<td colspan="3"></td>
<td></td>
</tr>
<tr class="odd">
<td colspan="3"><strong>8. ACTION REQUIRED:</strong></td>
<td colspan="7"></td>
</tr>
</tbody>
</table>

  ------------------------- -- ------------------ ---------- ----------- -----------
  **9. CHAIRPERSON ATM                            **DATE                 
  WG:**                                           REC'D:**               

  **10 FEEDBACK PASSED                                       **DATE:**   
  TO:**                                                                  
  ------------------------- -- ------------------ ---------- ----------- -----------

+-----------------------------------------------------+-------+-------+
| # 1. Request For Change form                        | **RFC | 98023 |
|                                                     | Nr:** |       |
+-----------------------------------------------------+-------+-------+

To be used whenever requesting a change to any part of SPOM. This form
may be photocopied as required.

<table style="width:100%;">
<colgroup>
<col style="width: 19%" />
<col style="width: 6%" />
<col style="width: 1%" />
<col style="width: 6%" />
<col style="width: 4%" />
<col style="width: 4%" />
<col style="width: 24%" />
<col style="width: 3%" />
<col style="width: 13%" />
<col style="width: 16%" />
</colgroup>
<tbody>
<tr class="odd">
<td><strong>1. SUBJECT:</strong></td>
<td colspan="9">CPDLC Procedures</td>
</tr>
<tr class="even">
<td colspan="10"></td>
</tr>
<tr class="odd">
<td colspan="5"><strong>2. REASON FOR CHANGE:</strong></td>
<td colspan="5"></td>
</tr>
<tr class="even">
<td colspan="10">Emergency free text on Airbus aircraft.</td>
</tr>
<tr class="odd">
<td colspan="10"><strong>3. DESCRIPTION OF PROPOSAL: [attach additional
pages if necessary]</strong></td>
</tr>
<tr class="even">
<td colspan="10"><p>FANS A implementation for downlink message element
68 (free text with D Urgency Attribute) is the same as that of
FANS-1 :</p>
<p>Downlink message element 68 is only accessible via the emergency page
on Airbus aircraft.</p></td>
</tr>
<tr class="odd">
<td colspan="2"><strong>4. REFERENCE(S):</strong></td>
<td colspan="8">Section 10.8, page P1-45, first para after
definitions.</td>
</tr>
<tr class="even">
<td colspan="4"><strong>5. PERSON INITIATING:</strong></td>
<td colspan="4">Lionel Bertin</td>
<td><strong>DATE:</strong></td>
<td>19 November 98</td>
</tr>
<tr class="odd">
<td colspan="3"><strong>ORGANISATION:</strong></td>
<td colspan="3">Aerospatiale</td>
<td><strong>TEL/FAX/EMAIL:</strong></td>
<td colspan="3">See page C-13</td>
</tr>
</tbody>
</table>

  ---------------- ------------------ ---------- --- ------------ ------------- -------------------- ------------- ---------- -----------
  **6. CHAIRPERSON                                                M Goodall                          **DATE        25/11/98   
  ISPACG WG:**                                                                                       REC'D:**                 

  **7.                                               **RESPONSE                                                               
  CONSULTATION**                                     DUE BY                                                                   
                                                     DATE:**                                                                  

                   **Organisation**   **Name**                                  **Agree/Disagree**                            **Date**

                   **ISPACG/13**                                                                                              

  **8. ACTION                                                                                                                 
  REQUIRED:**                                                                                                                 
  ---------------- ------------------ ---------- --- ------------ ------------- -------------------- ------------- ---------- -----------

  ------------------------- -- ------------------ ---------- ----------- -----------
  **9. CHAIRPERSON ATM                            **DATE                 
  WG:**                                           REC'D:**               

  **10 FEEDBACK PASSED                                       **DATE:**   
  TO:**                                                                  
  ------------------------- -- ------------------ ---------- ----------- -----------

+-----------------------------------------------------+-------+-------+
| # 1. Request For Change form                        | **RFC | 98024 |
|                                                     | Nr:** |       |
+-----------------------------------------------------+-------+-------+

To be used whenever requesting a change to any part of SPOM. This form
may be photocopied as required.

<table style="width:100%;">
<colgroup>
<col style="width: 19%" />
<col style="width: 6%" />
<col style="width: 1%" />
<col style="width: 6%" />
<col style="width: 4%" />
<col style="width: 4%" />
<col style="width: 24%" />
<col style="width: 3%" />
<col style="width: 13%" />
<col style="width: 16%" />
</colgroup>
<tbody>
<tr class="odd">
<td><strong>1. SUBJECT:</strong></td>
<td colspan="9">CPDLC Procedures</td>
</tr>
<tr class="even">
<td colspan="10"></td>
</tr>
<tr class="odd">
<td colspan="5"><strong>2. REASON FOR CHANGE:</strong></td>
<td colspan="5"></td>
</tr>
<tr class="even">
<td colspan="10">Editorial corrections</td>
</tr>
<tr class="odd">
<td colspan="10"><strong>3. DESCRIPTION OF PROPOSAL: [attach additional
pages if necessary]</strong></td>
</tr>
<tr class="even">
<td colspan="10"><p>Section 6.4, P1-13: « ATS Com Off » should be
replaced by « ATC Com Off ».</p>
<p>Section 6.4, P1-14, last bullet : « ATS provider » is used although
« ATS system » or « ATS unit » is suggested by Editing conventions (page
0-5, Introduction).</p>
<p>Section 6.4, P1-15, first bullet : same remark as above.</p>
<p>Section 8.2.2, P1-21, 1<sup>st</sup> para (<strong>) </strong>: does
it refer to data link or voice (or both) pilot-controller
communications ?</p></td>
</tr>
<tr class="odd">
<td colspan="2"><strong>4. REFERENCE(S):</strong></td>
<td colspan="8"></td>
</tr>
<tr class="even">
<td colspan="4"><strong>5. PERSON INITIATING:</strong></td>
<td colspan="4">Lionel Bertin</td>
<td><strong>DATE:</strong></td>
<td>19 November 98</td>
</tr>
<tr class="odd">
<td colspan="3"><strong>ORGANISATION:</strong></td>
<td colspan="3">Aerospatiale</td>
<td><strong>TEL/FAX/EMAIL:</strong></td>
<td colspan="3">See page C-13</td>
</tr>
</tbody>
</table>

  ---------------- ------------------ ---------- --- ------------ ------------- -------------------- ------------- ---------- -----------
  **6. CHAIRPERSON                                                M Goodall                          **DATE        25/11/98   
  ISPACG WG:**                                                                                       REC'D:**                 

  **7.                                               **RESPONSE                                                               
  CONSULTATION**                                     DUE BY                                                                   
                                                     DATE:**                                                                  

                   **Organisation**   **Name**                                  **Agree/Disagree**                            **Date**

                   **ISPACG/13**                                                                                              

  **8. ACTION                                                                                                                 
  REQUIRED:**                                                                                                                 
  ---------------- ------------------ ---------- --- ------------ ------------- -------------------- ------------- ---------- -----------

  ------------------------- -- ------------------ ---------- ----------- -----------
  **9. CHAIRPERSON ATM                            **DATE                 
  WG:**                                           REC'D:**               

  **10 FEEDBACK PASSED                                       **DATE:**   
  TO:**                                                                  
  ------------------------- -- ------------------ ---------- ----------- -----------

+-----------------------------------------------------+-------+-------+
| # 1. Request For Change form                        | **RFC | 98025 |
|                                                     | Nr:** |       |
+-----------------------------------------------------+-------+-------+

To be used whenever requesting a change to any part of SPOM. This form
may be photocopied as required.

<table style="width:100%;">
<colgroup>
<col style="width: 19%" />
<col style="width: 6%" />
<col style="width: 1%" />
<col style="width: 6%" />
<col style="width: 4%" />
<col style="width: 4%" />
<col style="width: 24%" />
<col style="width: 3%" />
<col style="width: 13%" />
<col style="width: 16%" />
</colgroup>
<tbody>
<tr class="odd">
<td><strong>1. SUBJECT:</strong></td>
<td colspan="9">DARP Procedures</td>
</tr>
<tr class="even">
<td colspan="10"></td>
</tr>
<tr class="odd">
<td colspan="5"><strong>2. REASON FOR CHANGE:</strong></td>
<td colspan="5"></td>
</tr>
<tr class="even">
<td colspan="10">Correct terminology</td>
</tr>
<tr class="odd">
<td colspan="10"><strong>3. DESCRIPTION OF PROPOSAL: [attach additional
pages if necessary]</strong></td>
</tr>
<tr class="even">
<td colspan="10"><p>Section 4, page P2-6 :</p>
<p>To be consistent with tables below (and with DO-219), the second
bullet should refer to <strong><span
class="smallcaps">Request</span></strong>
<strong>[routeclearance]</strong> rather than <strong><span
class="smallcaps">Request route clearance rte[x]</span></strong> for
message 24.</p></td>
</tr>
<tr class="odd">
<td colspan="2"><strong>4. REFERENCE(S):</strong></td>
<td colspan="8"></td>
</tr>
<tr class="even">
<td colspan="4"><strong>5. PERSON INITIATING:</strong></td>
<td colspan="4">Lionel Bertin</td>
<td><strong>DATE:</strong></td>
<td>19 November 98</td>
</tr>
<tr class="odd">
<td colspan="3"><strong>ORGANISATION:</strong></td>
<td colspan="3">Aerospatiale</td>
<td><strong>TEL/FAX/EMAIL:</strong></td>
<td colspan="3">See page C-13</td>
</tr>
</tbody>
</table>

  ---------------- ------------------ ---------- --- ------------ ------------- -------------------- ------------- ---------- -----------
  **6. CHAIRPERSON                                                M Goodall                          **DATE        21/11/98   
  ISPACG WG:**                                                                                       REC'D:**                 

  **7.                                               **RESPONSE                                                               
  CONSULTATION**                                     DUE BY                                                                   
                                                     DATE:**                                                                  

                   **Organisation**   **Name**                                  **Agree/Disagree**                            **Date**

                   **ISPACG/13**                                                                                              

  **8. ACTION                                                                                                                 
  REQUIRED:**                                                                                                                 
  ---------------- ------------------ ---------- --- ------------ ------------- -------------------- ------------- ---------- -----------

  ------------------------- -- ------------------ ---------- ----------- -----------
  **9. CHAIRPERSON ATM                            **DATE                 
  WG:**                                           REC'D:**               

  **10 FEEDBACK PASSED                                       **DATE:**   
  TO:**                                                                  
  ------------------------- -- ------------------ ---------- ----------- -----------

+-----------------------------------------------------+-------+-------+
| # 1. Request For Change form                        | **RFC | 98026 |
|                                                     | Nr:** |       |
+-----------------------------------------------------+-------+-------+

To be used whenever requesting a change to any part of SPOM. This form
may be photocopied as required.

  ------------------- ------------ -- -------------- -------- ------------ -------------------- ------ ----------- -----------
  **1. SUBJECT:**     ADS                                                                                          
                      Procedures                                                                                   

                                                                                                                   

  **2. REASON FOR                                             Editorial                                            
  CHANGE:**                                                   correction                                           

                                                                                                                   

  **3. DESCRIPTION OF                                                                                              
  PROPOSAL: \[attach                                                                                               
  additional pages if                                                                                              
  necessary\]**                                                                                                    

  Section 1.3, page                                                                                                
  7-3 : « predicted                                                                                                
  route » (DO 212                                                                                                  
  terminology) should                                                                                              
  be used rather than                                                                                              
  « projected route »                                                                                              
  (SARPs                                                                                                           
  terminology).                                                                                                    

  **4.                                                                                                             
  REFERENCE(S):**                                                                                                  

  **5. PERSON                                        Lionel                                            **DATE:**   19 November
  INITIATING:**                                      Bertin                                                        98

  **ORGANISATION:**                   Aerospatiale                         **TEL/FAX/EMAIL:**   See                
                                                                                                page               
                                                                                                C-13               
  ------------------- ------------ -- -------------- -------- ------------ -------------------- ------ ----------- -----------

  ---------------- ------------------ ---------- --- ------------ ------------- -------------------- ------------- ---------- -----------
  **6. CHAIRPERSON                                                M Goodall                          **DATE        21/11/98   
  ISPACG WG:**                                                                                       REC'D:**                 

  **7.                                               **RESPONSE                                                               
  CONSULTATION**                                     DUE BY                                                                   
                                                     DATE:**                                                                  

                   **Organisation**   **Name**                                  **Agree/Disagree**                            **Date**

                   **ISPACG/13**                                                                                              

  **8. ACTION                                                                                                                 
  REQUIRED:**                                                                                                                 
  ---------------- ------------------ ---------- --- ------------ ------------- -------------------- ------------- ---------- -----------

  ------------------------- -- ------------------ ---------- ----------- -----------
  **9. CHAIRPERSON ATM                            **DATE                 
  WG:**                                           REC'D:**               

  **10 FEEDBACK PASSED                                       **DATE:**   
  TO:**                                                                  
  ------------------------- -- ------------------ ---------- ----------- -----------

+-----------------------------------------------------+-------+-------+
| # 1. Request For Change form                        | **RFC | 98027 |
|                                                     | Nr:** |       |
+-----------------------------------------------------+-------+-------+

To be used whenever requesting a change to any part of SPOM. This form
may be photocopied as required.

<table style="width:100%;">
<colgroup>
<col style="width: 19%" />
<col style="width: 6%" />
<col style="width: 1%" />
<col style="width: 6%" />
<col style="width: 4%" />
<col style="width: 4%" />
<col style="width: 24%" />
<col style="width: 3%" />
<col style="width: 13%" />
<col style="width: 16%" />
</colgroup>
<tbody>
<tr class="odd">
<td><strong>1. SUBJECT:</strong></td>
<td colspan="9">CPDLC Procedures</td>
</tr>
<tr class="even">
<td colspan="10"></td>
</tr>
<tr class="odd">
<td colspan="5"><strong>2. REASON FOR CHANGE:</strong></td>
<td colspan="5"></td>
</tr>
<tr class="even">
<td colspan="10">Update description of flight crew display and airborne
architecture for FANS A</td>
</tr>
<tr class="odd">
<td colspan="10"><strong>3. DESCRIPTION OF PROPOSAL: [attach additional
pages if necessary]</strong></td>
</tr>
<tr class="even">
<td colspan="10"><p>P1-28, Table Flight Crew Display, row Airbus :</p>
<p>« In response to an uplink message that requires a response element
(<strong><span class="smallcaps">Wilco</span></strong>, <strong><span
class="smallcaps">Roger</span></strong>, <strong><span
class="smallcaps">Affirm</span></strong>, <strong><span
class="smallcaps">Unable</span></strong> or <strong><span
class="smallcaps">Negative</span></strong>), the pilot is presented with
prompts corresponding to the response elements permitted by DO-219 for
this specific uplink message. E.g., prompts presented upon receipt of an
uplink clearance are <span class="smallcaps"><strong>Wilco</strong>,
<strong>Unable</strong></span> and <span
class="smallcaps"><strong>Standby</strong>. »</span></p>
<p>P1-29, Figure Overview of CPDLC system:</p>
<p><img src="media/image1.wmf" /></p>
<p>(Only the Airbus architecture is modified in the figure proposed
above)</p></td>
</tr>
<tr class="odd">
<td colspan="2"><strong>4. REFERENCE(S):</strong></td>
<td colspan="8">section 10.2.1.1 of SPOM</td>
</tr>
<tr class="even">
<td colspan="4"><strong>5. PERSON INITIATING:</strong></td>
<td colspan="4">Lionel Bertin</td>
<td><strong>DATE:</strong></td>
<td>19 November 98</td>
</tr>
<tr class="odd">
<td colspan="3"><strong>ORGANISATION:</strong></td>
<td colspan="3">Aerospatiale</td>
<td><strong>TEL/FAX/EMAIL:</strong></td>
<td colspan="3">See page C-13</td>
</tr>
</tbody>
</table>

  ---------------- ------------------ ---------- --- ------------ ------------- -------------------- ------------- ---------- -----------
  **6. CHAIRPERSON                                                Mark Goodall                       **DATE        21/11/98   
  ISPACG WG:**                                                                                       REC'D:**                 

  **7.                                               **RESPONSE                                                               
  CONSULTATION**                                     DUE BY                                                                   
                                                     DATE:**                                                                  

                   **Organisation**   **Name**                                  **Agree/Disagree**                            **Date**

                   **ISPACG/13**                                                                                              

  **8. ACTION                                                                                                                 
  REQUIRED:**                                                                                                                 
  ---------------- ------------------ ---------- --- ------------ ------------- -------------------- ------------- ---------- -----------

  ------------------------- -- ------------------ ---------- ----------- -----------
  **9. CHAIRPERSON ATM                            **DATE                 
  WG:**                                           REC'D:**               

  **10 FEEDBACK PASSED                                       **DATE:**   
  TO:**                                                                  
  ------------------------- -- ------------------ ---------- ----------- -----------

+-----------------------------------------------------+-------+-------+
| # 1. Request For Change form                        | **RFC | 98028 |
|                                                     | Nr:** |       |
+-----------------------------------------------------+-------+-------+

To be used whenever requesting a change to any part of SPOM. This form
may be photocopied as required.

<table style="width:100%;">
<colgroup>
<col style="width: 19%" />
<col style="width: 6%" />
<col style="width: 1%" />
<col style="width: 6%" />
<col style="width: 4%" />
<col style="width: 4%" />
<col style="width: 24%" />
<col style="width: 3%" />
<col style="width: 13%" />
<col style="width: 16%" />
</colgroup>
<tbody>
<tr class="odd">
<td><strong>1. SUBJECT:</strong></td>
<td colspan="9">Armable messages</td>
</tr>
<tr class="even">
<td colspan="10"></td>
</tr>
<tr class="odd">
<td colspan="5"><strong>2. REASON FOR CHANGE:</strong></td>
<td colspan="5"></td>
</tr>
<tr class="even">
<td colspan="10">To take advantage of FMC armable messages in vertical
change clearances</td>
</tr>
<tr class="odd">
<td colspan="10"><strong>3. DESCRIPTION OF PROPOSAL: [attach additional
pages if necessary]</strong></td>
</tr>
<tr class="even">
<td colspan="10"><p>Add to the SPOM CPDLC section</p>
<p>Controllers shall append the REPORT REACHING message element to any
vertical change clearance so that flight crews have access to the
pre-formatted downlink report.</p></td>
</tr>
<tr class="odd">
<td colspan="2"><strong>4. REFERENCE(S):</strong></td>
<td colspan="8"></td>
</tr>
<tr class="even">
<td colspan="4"><strong>5. PERSON INITIATING:</strong></td>
<td colspan="4">Ian Varcoe</td>
<td><strong>DATE:</strong></td>
<td>7 Dec 98</td>
</tr>
<tr class="odd">
<td colspan="3"><strong>ORGANISATION:</strong></td>
<td colspan="3">ANZ</td>
<td><strong>TEL/FAX/EMAIL:</strong></td>
<td colspan="3"></td>
</tr>
</tbody>
</table>

  ---------------- ------------------ ---------- --- ------------ ------------- -------------------- ------------- --------- -----------
  **6. CHAIRPERSON                                                Mark Goodall                       **DATE        7/12/98   
  ISPACG WG:**                                                                                       REC'D:**                

  **7.                                               **RESPONSE                                                              
  CONSULTATION**                                     DUE BY                                                                  
                                                     DATE:**                                                                 

                   **Organisation**   **Name**                                  **Agree/Disagree**                           **Date**

                   **ISPACG/13**                                                                                             

  **8. ACTION                                                                                                                
  REQUIRED:**                                                                                                                
  ---------------- ------------------ ---------- --- ------------ ------------- -------------------- ------------- --------- -----------

  ------------------------- -- ------------------ ---------- ----------- -----------
  **9. CHAIRPERSON ATM                            **DATE                 
  WG:**                                           REC'D:**               

  **10 FEEDBACK PASSED                                       **DATE:**   
  TO:**                                                                  
  ------------------------- -- ------------------ ---------- ----------- -----------

**ATTACHMENT 3**

**Performance Data**

![](media/image2.jpeg){width="5.738888888888889in"
height="4.166666666666667in"}

![](media/image3.wmf)

![](media/image4.wmf)

![](media/image5.wmf)

![](media/image6.wmf)

![](media/image7.wmf)

![](media/image8.wmf)

**REPORT**

**of the**

**DARP WORKING GROUP**

# [DARP WORKGROUP REPORT]{.underline}

# 

# 1. INTRODUCTION

1.1 The group discussed DARP Phase 1, Phase 2 and Phase 3.

# 2. PARTICIPANTS

1.  The following participated in the DARP Working Group Meeting:

  ----------------------------- -----------------------------------------
  Mark Goodall                  Airways

  Steve Kelly                   ANZ

  Pat Thomas                    Airservices

  Carol Dryden                  FAA

  Jim Alley                     ARINC

  Rodney Bracefield             CAANZ

  Brian O'Keeffe                Honeywell

  Georges Claustre              DGAC

  Inia Tueli                    CAAF

  John McConway                 Airways

  Gene Cameron                  UAL
  ----------------------------- -----------------------------------------

# 3. Action item 20: DARP PHASE 1 

## DARP Phase 1 was divided into two parts, southbound DARP (Tracks W and X)

## and northbound DARP (Tracks 20 and 21). The airline operators stated that they were ready to implement DARP and would prefer to implement north and southbound tracks simultaneously. 

## 3.2 Southbound DARP:

### 3.2.1 Auckland, Brisbane, Fiji and Tahiti informed the group that they are ready to implement southbound DARPS. Oakland Center advised that due to the upgrade to MS-ODL a period of testing would be required prior to operational implementation. The group agreed to four consecutive days of testing in which all steps in the DARPS Phase 1 process would be exercised with the exception of the airborne reroute. The test period of January 19 through January 22, 1999 was accepted. The first two days of testing will involve Track W (KLAX to YSSY). The third day of the test will involve Track X (KLAX to NZAA). The last day of the test will include both Tracks W and X.  {#auckland-brisbane-fiji-and-tahiti-informed-the-group-that-they-are-ready-to-implement-southbound-darps.-oakland-center-advised-that-due-to-the-upgrade-to-ms-odl-a-period-of-testing-would-be-required-prior-to-operational-implementation.-the-group-agreed-to-four-consecutive-days-of-testing-in-which-all-steps-in-the-darps-phase-1-process-would-be-exercised-with-the-exception-of-the-airborne-reroute.-the-test-period-of-january-19-through-january-22-1999-was-accepted.-the-first-two-days-of-testing-will-involve-track-w-klax-to-yssy.-the-third-day-of-the-test-will-involve-track-x-klax-to-nzaa.-the-last-day-of-the-test-will-include-both-tracks-w-and-x. .unnumbered}

###  {#section-1 .unnumbered}

### 3.2.2 For each day in the test period the AOC's will be required to transmit a Change 15 message to their ICAO flight plan. The service providers will document receipt of the Change 15. The test scenario will be transmitted by Oakland Center in advance; upon completion of the test a telecon will be initiated to discuss test results and set the date of operational implementation. The group agreed to a targeted implementation date of February 1, 1999. Due to the transition to new hardware/software of the service providers in the region the operational implementation must commence between February 1 and April 30 or be subject to an approximate two to three month delay. {#for-each-day-in-the-test-period-the-aocs-will-be-required-to-transmit-a-change-15-message-to-their-icao-flight-plan.-the-service-providers-will-document-receipt-of-the-change-15.-the-test-scenario-will-be-transmitted-by-oakland-center-in-advance-upon-completion-of-the-test-a-telecon-will-be-initiated-to-discuss-test-results-and-set-the-date-of-operational-implementation.-the-group-agreed-to-a-targeted-implementation-date-of-february-1-1999.-due-to-the-transition-to-new-hardwaresoftware-of-the-service-providers-in-the-region-the-operational-implementation-must-commence-between-february-1-and-april-30-or-be-subject-to-an-approximate-two-to-three-month-delay. .unnumbered}

###   {#section-2 .unnumbered}

## 3.3 Northbound DARP:

### 3.3.1 All service providers with the exception of Auckland and Oakland expressed their readiness for northbound DARP. Auckland informed the group that they would be ready after OCS and a three-month controller consolidation period. Oakland advised they required enhancement to their DOTS Plus software prior to operational implementation on northbound routes. The required enhancements are being developed and are expected in the first quarter of 1999. Targeted implementation date is July 99. An update on readiness will be discussed at the FIT in May. {#all-service-providers-with-the-exception-of-auckland-and-oakland-expressed-their-readiness-for-northbound-darp.-auckland-informed-the-group-that-they-would-be-ready-after-ocs-and-a-three-month-controller-consolidation-period.-oakland-advised-they-required-enhancement-to-their-dots-plus-software-prior-to-operational-implementation-on-northbound-routes.-the-required-enhancements-are-being-developed-and-are-expected-in-the-first-quarter-of-1999.-targeted-implementation-date-is-july-99.-an-update-on-readiness-will-be-discussed-at-the-fit-in-may. .unnumbered}

# 4. Action Item 67: DARP PHASE 2 and 3

### 4.1 DARP Phase 2 has been divided into two steps. In Step 1 airline operators would provide their own flexible routes. It should be noted that all aircraft, FANS and non-FANS, will be permitted tofly airline defined routes. However, operational CPDLC is required for aircraft requesting airborne re-routes. In Step 2 airline operators would provide their own flexible route and one re-route.  {#darp-phase-2-has-been-divided-into-two-steps.-in-step-1-airline-operators-would-provide-their-own-flexible-routes.-it-should-be-noted-that-all-aircraft-fans-and-non-fans-will-be-permitted-tofly-airline-defined-routes.-however-operational-cpdlc-is-required-for-aircraft-requesting-airborne-re-routes.-in-step-2-airline-operators-would-provide-their-own-flexible-route-and-one-re-route. .unnumbered}

## 4.2 DARPS Phase 2 Step 1:

### 4.2.1 Brisbane and Nadi advised they are ready to implement DARP Phase 2 Step 1. Tahiti advised they require ADS and TDM message format. Auckland requires OCS and Oakland indicated that they must complete labor negotiations prior to implementation. Service provider requirements for DARPS Phase 2 and 3 are depicted in Figure 1.  {#brisbane-and-nadi-advised-they-are-ready-to-implement-darp-phase-2-step-1.-tahiti-advised-they-require-ads-and-tdm-message-format.-auckland-requires-ocs-and-oakland-indicated-that-they-must-complete-labor-negotiations-prior-to-implementation.-service-provider-requirements-for-darps-phase-2-and-3-are-depicted-in-figure-1. .unnumbered}

### 4.2.2 For DARPS Phase 2 the nominated city pairs will be between KSFO/KLAX and YSSY/NZAA. The targeted implementation date for DARPS Phase 2 Step 1 is July 1999. In discussion of DARPS Phase 2 Step 1 the following issues were identified: {#for-darps-phase-2-the-nominated-city-pairs-will-be-between-ksfoklax-and-yssynzaa.-the-targeted-implementation-date-for-darps-phase-2-step-1-is-july-1999.-in-discussion-of-darps-phase-2-step-1-the-following-issues-were-identified .unnumbered}

### 4.2.3 Application of RNP-10. Oakland informed the group that they do not intend to implement the longitudinal component of RNP-10 until ADS capability is available. They further advised that within the Oakland FIR the minimum longitudinal separation for aircraft on the same track is 15 minutes in trail. Unless the flights are on same or continuously diverging tracks 10 minutes longitudinal separation with mach technique can not be applied. This is contrary to adjacent FIRs. It was agreed that this would have a significant impact to the users and the FAA is strongly encouraged to review available documentation and coordinate with adjacent FIRs so that all ATSUs in the Pacific have the same application.  {#application-of-rnp-10.-oakland-informed-the-group-that-they-do-not-intend-to-implement-the-longitudinal-component-of-rnp-10-until-ads-capability-is-available.-they-further-advised-that-within-the-oakland-fir-the-minimum-longitudinal-separation-for-aircraft-on-the-same-track-is-15-minutes-in-trail.-unless-the-flights-are-on-same-or-continuously-diverging-tracks-10-minutes-longitudinal-separation-with-mach-technique-can-not-be-applied.-this-is-contrary-to-adjacent-firs.-it-was-agreed-that-this-would-have-a-significant-impact-to-the-users-and-the-faa-is-strongly-encouraged-to-review-available-documentation-and-coordinate-with-adjacent-firs-so-that-all-atsus-in-the-pacific-have-the-same-application. .unnumbered}

### 4.2.4 Flight Planning Information. The users requested information on flight planning through the FIRs. This includes information such as FIR boundary fix, route entry/exit requirements for domestic airspace and TDM requirements. It was agreed that FIR crossing points are necessary entering each FIR. The service providers indicated that this information would be included in their AIPs or equivalent documentation, and agreed to review and expand the information as necessary. ATSUs will coordinate changes and flight plan guidance material for users will be included in the SPOM if required. {#flight-planning-information.-the-users-requested-information-on-flight-planning-through-the-firs.-this-includes-information-such-as-fir-boundary-fix-route-entryexit-requirements-for-domestic-airspace-and-tdm-requirements.-it-was-agreed-that-fir-crossing-points-are-necessary-entering-each-fir.-the-service-providers-indicated-that-this-information-would-be-included-in-their-aips-or-equivalent-documentation-and-agreed-to-review-and-expand-the-information-as-necessary.-atsus-will-coordinate-changes-and-flight-plan-guidance-material-for-users-will-be-included-in-the-spom-if-required. .unnumbered}

### 4.2.5 Service Priority. The group agreed that in DARPS Phase 2 and 3 service priority would be based on first come first served basis.  {#service-priority.-the-group-agreed-that-in-darps-phase-2-and-3-service-priority-would-be-based-on-first-come-first-served-basis. .unnumbered}

## 4.3 DARPS Phase 2 Step 2:

### 4.3.1 DARPS Phase 2 Step 2 will expand the nominated city pairs identified in Step 1 by adding the routes between NFFN and KLAX/KSFO and NTAA and KLAX/KSFO. For this step all service providers will require AIDC, additional requirements are listed in Figure 1. AIDC must permit the transmission of route data. The route data transmitter must correspond with information in the aircraft FMC. It was also noted that reporting point identifiers that differ from ICAO designators would be rejected by ATC ground systems. {#darps-phase-2-step-2-will-expand-the-nominated-city-pairs-identified-in-step-1-by-adding-the-routes-between-nffn-and-klaxksfo-and-ntaa-and-klaxksfo.-for-this-step-all-service-providers-will-require-aidc-additional-requirements-are-listed-in-figure-1.-aidc-must-permit-the-transmission-of-route-data.-the-route-data-transmitter-must-correspond-with-information-in-the-aircraft-fmc.-it-was-also-noted-that-reporting-point-identifiers-that-differ-from-icao-designators-would-be-rejected-by-atc-ground-systems. .unnumbered}

### 4.3.2 The targeted implementation date for DARP Phase 2 Step 2 is last quarter 1999.  {#the-targeted-implementation-date-for-darp-phase-2-step-2-is-last-quarter-1999. .unnumbered}

## 4.4 DARPS Phase 3 and Beyond:

### 4.4.1 DARPS Phase 3 would expand on DARPS Phase 2 Step 2 by expanding the nominated city pairs to anywhere in the region and to add multiple re-routes. Service provider requirements listed in Figure 1. DARPS Phase 2 and 3 cater for non-FANS equipped aircraft by permitting random routes. In DARPS Phase 3 non-FANS equipped aircraft will also be permitted to file random routes anywhere in the region. The group felt that after DARPS Phase 3 is implemented the elimination of some ATS routes would be warranted. {#darps-phase-3-would-expand-on-darps-phase-2-step-2-by-expanding-the-nominated-city-pairs-to-anywhere-in-the-region-and-to-add-multiple-re-routes.-service-provider-requirements-listed-in-figure-1.-darps-phase-2-and-3-cater-for-non-fans-equipped-aircraft-by-permitting-random-routes.-in-darps-phase-3-non-fans-equipped-aircraft-will-also-be-permitted-to-file-random-routes-anywhere-in-the-region.-the-group-felt-that-after-darps-phase-3-is-implemented-the-elimination-of-some-ats-routes-would-be-warranted. .unnumbered}

###   {#section-3 .unnumbered}

### 4.4.2 Information regarding the DARP phases that require a change to the SPOM were documented on RFC 98/022 (see attached). The changes were agreed to by the group and will be incorporated into the SPOM. {#information-regarding-the-darp-phases-that-require-a-change-to-the-spom-were-documented-on-rfc-98022-see-attached.-the-changes-were-agreed-to-by-the-group-and-will-be-incorporated-into-the-spom. .unnumbered}

+--------+------------------------------+------------------------------+
| **     | **Requirements DARPS Phase 2 | **Requirement DARPS Phase 2  |
| ATSU** | Step 1**                     | Step 2 & DARPS Phase 3**     |
+--------+------------------------------+------------------------------+
| Au     | Aircraft Situation Display,  | Aircraft Situation Display,  |
| ckland | Conflict Probe (OCS)         | ADS, CPDLC, Conflict Probe,  |
|        |                              | AIDC (OCS)                   |
+--------+------------------------------+------------------------------+
| Br     | Nil                          | Aircraft Situation Display,  |
| isbane |                              | ADS, CPDLC, AIDC (TAAATS)    |
+--------+------------------------------+------------------------------+
| Nadi   | Nil                          | Aircraft Situation Display,  |
|        |                              | ADS, CPDLC, Conflict Probe,  |
|        |                              | AIDC (EASY)                  |
+--------+------------------------------+------------------------------+
| O      | Labor Agreement              | Aircraft Situation Display,  |
| akland |                              | CPDLC, Conflict Probe, AIDC  |
+--------+------------------------------+------------------------------+
| Tahiti | ADS                          | Aircraft Situation Display,  |
|        |                              | ADS, CPDLC, AIDC             |
|        | Airline generated TDM is     |                              |
|        | also required                | Airline generated TDM is     |
|        |                              | also required                |
+--------+------------------------------+------------------------------+

Figure 1

# 5. RNP-10 IMPLEMENTATION UPDATE

## 5.1 The group was asked to obtain RNP-10 implementation plans from the service providers. They are as follows:

5.1.1 Auckland has implemented RNP-10, 50 lateral within the FIR. They
intend to implement 50 NM longitudinal after OCS.

###  {#section-4 .unnumbered}

2.  Brisbane has implemented RNP-10, 50 NM lateral in the Tasman area;
    it will be

    expanded throughout the Brisbane FIR. They will introduce 50 NM
    longitudinal after TAAATS when ADS is available.

###  {#section-5 .unnumbered}

3.  Nadi expects to implement RNP-10, 50 NM lateral within the FIR in
    first quarter 1999.

    They will expand to 50 NM longitudinal after EASY.

###  {#section-6 .unnumbered}

4.  Oakland implemented RNP-10, 50 NM lateral in their FIR with the
    exception of the

    composite route structure between North America and the Hawaiian
    Islands. At the present time they do not plan to implement 50 NM
    longitudinal until ADS capability is available..

###  {#section-7 .unnumbered}

5.1.5 Tahiti is expected to implement RNP-10 on flex tracks and DARP
routes in the first quarter of 1999 after ADS is operational. After ADS
implementation procedures will be developed to apply 50nm lateral and
longitudinal separation.

# 6. WORK PLAN

+-------------+----------------------------------+----------+---------+
| **Action    | **Action**                       | **Target | *       |
| item**      |                                  | date**   | *Action |
|             |                                  |          | with**  |
+-------------+----------------------------------+----------+---------+
| 20 DARP     | Test DOTS upgrade                | 19-22    | Oakland |
| Phase 1     |                                  | Jan 99   |         |
|             | Implement South Bound tracks     |          | All     |
|             |                                  | Feb --   |         |
|             | Implement North bound tracks     | Apr 99   | Airways |
|             | subject to:                      |          |         |
|             |                                  | July 99  | Oakland |
|             | -   OCS consolidation            |          |         |
|             |                                  | March 99 |         |
|             | -   DOTS Software Enhancement    |          |         |
+-------------+----------------------------------+----------+---------+
| New Item    | Publish procedures in SPOM       | Feb 99   | Airways |
|             |                                  |          |         |
| Implement   | **Phase 2 Step 1:**              | March 99 | All     |
| DARP Phase  |                                  |          | ATSUs   |
| 2 & 3       | Review and co-ordinate flight    | May 99   |         |
|             | planning requirements            |          | FIT     |
|             |                                  | May 99   |         |
|             | Agree to common flight planning  |          | All     |
|             | requirements                     | July 99  | ATSU's  |
|             |                                  |          |         |
|             | Publish flight planning          | July 99  | Airways |
|             | requirements in SPOM and AIP's   |          |         |
|             | or equivalent as appropriate     | July 99  | Oakland |
|             |                                  |          |         |
|             | OCS consolidation                | August   | Airs    |
|             |                                  | 99       | ervices |
|             | Reach labour agreement           |          |         |
|             |                                  | Last qtr | CAAF    |
|             | **Phase 2 Step 2:**              | 99       |         |
|             |                                  |          | All     |
|             | TAAATS consolidation             | TBD      | ATSUs   |
|             |                                  |          |         |
|             | EASY consolidation               |          | ALL     |
|             |                                  |          |         |
|             | AIDC                             |          |         |
|             |                                  |          |         |
|             | **Phase 3**                      |          |         |
|             |                                  |          |         |
|             | Consolidation of Phase 2 Step 2  |          |         |
|             | procedures                       |          |         |
+-------------+----------------------------------+----------+---------+

# 7. ACCOMPLISHMENTS

-   Set target dates for DARP Phase 1 implementation.

-   Developed DARP Phase 2 and 3 procedures for publication in the SPOM.

-   Accommodated non-FANS aircraft in DARP Phase 2 and 3 by permitting
    these aircraft to fly random tracks.

-   Identified DARP Phase 2 and 3 requirements and established an
    implementation timetable.

  ----------------------------------------------------- -------- --------
  **REQUEST FOR CHANGE FORM**                           **RFC    98/022
                                                        Nr:**    

  ----------------------------------------------------- -------- --------

To be used whenever requesting a change to any part of SPOM. This form
may be photocopied as required.

  ------------------- ------ -- ----- --------- ----------- -------------------- --------------------------- ----------- -----------
  **1. SUBJECT:**     DARP 2                                                                                             
                      & 3                                                                                                

                                                                                                                         

  **2. REASON FOR                               Introduce                                                                
  CHANGE:**                                     DARP 2 & 3                                                               
                                                in SOPAC                                                                 

                                                                                                                         

  **3. DESCRIPTION OF                                                                                                    
  PROPOSAL: \[attach                                                                                                     
  additional pages if                                                                                                    
  necessary\]**                                                                                                          

  Insert SPOM Part 8                                                                                                     
  as attached                                                                                                            

  **4.                                                                                                                   
  REFERENCE(S):**                                                                                                        

  **5. PERSON                         Tommy E                                                                **DATE:**   8/12/98
  INITIATING:**                       Barclay                                                                            

  **ORGANISATION:**             ZOA                         **TEL/FAX/EMAIL:**   tommy.barclay@faa.dot.gov               
  ------------------- ------ -- ----- --------- ----------- -------------------- --------------------------- ----------- -----------

  ---------------- ------------------ ---------- --- ------------ ------------- -------------------- ------------- --------- -----------
  **6. CHAIRPERSON                                                M Goodall                          **DATE        8/12/98   
  ISPACG WG:**                                                                                       REC'D:**                

  **7.                                               **RESPONSE                                                              
  CONSULTATION**                                     DUE BY                                                                  
                                                     DATE:**                                                                 

                   **Organisation**   **Name**                                  **Agree/Disagree**                           **Date**

                   **ISPACG/13**                                                                                             

  **8. ACTION                                                                                                                
  REQUIRED:**                                                                                                                
  ---------------- ------------------ ---------- --- ------------ ------------- -------------------- ------------- --------- -----------

  ------------------------- -- ------------------ ---------- ----------- -----------
  **9. CHAIRPERSON ATM                            **DATE                 
  WG:**                                           REC'D:**               

  **10 FEEDBACK PASSED                                       **DATE:**   
  TO:**                                                                  
  ------------------------- -- ------------------ ---------- ----------- -----------

**South Pacific Operations Manual - Part 8**

**Dynamic Airborne Route Planning (DARP) Procedures**

**Phase 2 & 3 - User supplied original track and re-route/s**

1\. Definition DARP Phase 2 & 3 [62](#definition-darp-phase-2-3)

2\. Prerequisites / DARP Phase 2 Step 1 & 2
[62](#prerequisites-darp-phase-2-step-1-2)

3\. Prerequisites / DARP Phase 3 [63](#prerequisites-darp-phase-3)

4\. Coordination event sequence / DARP Phase 2 & 3
[63](#coordination-event-sequence-darp-phase-2-3)

4.1 Objectives & Assumptions [63](#objectives-assumptions)

4.2 DARP Phase 2 & 3 event sequence [63](#darp-phase-2-3-event-sequence)

5\. Procedures for DARP Phase 2 & 3 operations
[65](#procedures-for-darp-phase-2-3-operations)

6\. Contingencies DARP Phase 2 & 3 [65](#contingencies-darp-phase-2-3)

**Dynamic Airborne Route Planning (DARP) Procedures**

**Phase 2 & 3 - Airline defined track and re-route/s**

# 

# 1. Definition DARP Phase 2 & 3

**J DARP Phase 2**

**Step 1 - is defined as** - Individual airline defined track between
the city pairs of LAX/SFO-SYD/AKL-LAX/SFO (Note: NAN/PPT-LAX-NAN/PPT and
other tracks may be added).

**Step 2 - is defined as** - Individual airline defined track between
the above city pairs and a single re-route per flight.

**J DARP Phase 3 - is defined as** - Individual airline defined track
and multiple re-routes anywhere in the region.

# 2. Prerequisites / DARP Phase 2 Step 1 & 2

**J Airline ground system capabilities** - The airline shall have the
capability to generate routes and also a Track Definition Message (TDM)
for flights entering or exiting the NTTT FIR.

**J Aircraft capabilities**

**Step 1** - No additional capabilities are required

**Step 2** - CPDLC is required

**J ATS provider capabilities** - Each ATSU requires the following
capabilities

+--------+------------------------------+------------------------------+
| **     | **Requirements Step 1**      | **Requirement Step 2**       |
| ATSU** |                              |                              |
+--------+------------------------------+------------------------------+
| Au     | Aircraft Situation Display,  | Aircraft Situation Display,  |
| ckland | Conflict Probe (OCS)         | ADS, CPDLC, Conflict Probe,  |
|        |                              | AIDC\* (OCS)                 |
+--------+------------------------------+------------------------------+
| Br     | Nil                          | Aircraft Situation Display,  |
| isbane |                              | ADS, CPDLC, AIDC\* (TAAATS)  |
+--------+------------------------------+------------------------------+
| Nadi   | Nil                          | Aircraft Situation Display,  |
|        |                              | ADS, CPDLC, Conflict Probe,  |
|        |                              | AIDC\* (EASY)                |
+--------+------------------------------+------------------------------+
| O      | Labour Agreement             | Aircraft Situation Display,  |
| akland |                              | CPDLC, Conflict Probe,       |
|        |                              | AIDC\*                       |
+--------+------------------------------+------------------------------+
| Tahiti | ADS                          | Aircraft Situation Display,  |
|        |                              | ADS, CPDLC, AIDC\*           |
|        | Airline generated TDM is     |                              |
|        | also required                | Airline generated TDM is     |
|        |                              | also required                |
+--------+------------------------------+------------------------------+

\* Note: AIDC bilateral agreements must permit the processing and
transmission of route information and any subsequent changes to the
route.

**J Route data procedures** -

a)  ATSUs must ensure the route data transmitted via AIDC is exactly the
    same as the flight\'s cleared route.

b)  Reporting point identifiers that are different to the ICAO
    designators will be rejected by ATC ground systems.

**J DARP procedures** - DARP procedures and flight planning requirements
will be promulgated in AIPs or equivalent, and ATSU and airline manuals.

# 3. Prerequisites / DARP Phase 3

The requirements are the same as DARP Phase 2 Step 2. Oakland also
requires ADS.

# 4. Coordination event sequence / DARP Phase 2 & 3

## 4.1 Objectives & Assumptions

In DARPS Phase 2 and 3, Oakland Center TMU will discontinue producing
South Pacific PACOTS. Users will provide their own original random track
and subsequent re-route/s.

## 4.2 DARP Phase 2 & 3 event sequence

**J DARP Phase 2 Step 1 sequence -** The following sequence shall be
applied when DARP operating:

> **1) AOC and pilot**

a)  AOC generates original track that includes waypoints at the FIR
    boundary.

b)  Transmit a TDM for flights entering/exiting the NTTT FIR.

> **2) Sector controller**
>
> The controller works the flight like any other aircraft.

![](media/image9.wmf){width="6.233333333333333in"
height="4.019444444444445in"}

Figure 1: DARP Phase 2 Step 2 & Phase 3 sequence

**J DARP Phase 2 Step 2 & Phase 3 sequence -** The following sequence
shall be applied when DARP operating (see Figure 1):

> **1) AOC and pilot**

a)  AOC generates original track that includes waypoints at the FIR
    boundary.

b)  Transmit a TDM for flights entering/exiting the NTTT FIR.

c)  New weather forecast is loaded into the flight planning system.

d)  AOC generates and validates amended route and uplinks the ATS route
    to the aircraft. The amended ATS route defines waypoints at FIR
    boundaries. Note a TDM is also required for flights entering/exiting
    the NTTT FIR.

e)  Pilot downlinks request for re-route clearance.

f)  Pilot activates the amended route clearance into flight management
    computer and downlinks notification to AOC.

> **2) Sector controller**

a)  The controller receives clearance request, checks for conflicts and
    coordinates with adjacent ATSUs as required.

b)  The controller normally uplinks re-route clearance, using waypoints
    as received from the aircraft, to pilot.

c)  The controller works the remainder of the flight like any other
    re-routed aircraft.

d)  The route change is transmitted to subsequent ATSUs via AIDC.

# 5. Procedures for DARP Phase 2 & 3 operations

**J Re-route request and clearance delivery -** The pilot shall request
the re-route via CPDLC, using the downlink message 24 - **[Request route
clearance rte\[x\] or Request route clearance modified
rte\[x\]]{.smallcaps}**. The controller shall deliver the re-route
clearance via CPDLC, using message 80 - **[Cleared]{.smallcaps} \[route
clearance\]** or message 83 **[- At \[]{.smallcaps}position[\]
Cleared]{.smallcaps} \[route clearance\]** where
**[\[]{.smallcaps}position[\] ]{.smallcaps}**is a filed waypoint ahead
of the aircraft and before the start of the re-route.

  ---------------- -----------------------------------------------------------
  **Pilot**        **[Request]{.smallcaps} \[route clearance\]**

  **Controller**   **[Cleared]{.smallcaps} \[route clearance\]**
  ---------------- -----------------------------------------------------------

**OR**

+----------+-----------------------------------------------------------+
| *        | **[Request]{.smallcaps} \[route clearance\]**             |
| *Pilot** |                                                           |
+----------+-----------------------------------------------------------+
| **Cont   | **[At \[]{.smallcaps}position[\] Cleared]{.smallcaps}     |
| roller** | \[route clearance\]**                                     |
|          |                                                           |
|          | *(where **[\[]{.smallcaps}position[\] ]{.smallcaps}**is a |
|          | filed waypoint ahead of the aircraft and before the start |
|          | of the re-route)*                                         |
+----------+-----------------------------------------------------------+

# 6. Contingencies DARP Phase 2 & 3

**J Loss of aircraft CPDLC capability: -** No re-routes will be issued
to that aircraft.

**J Loss of ATC CPDLC capability** - If an ATS provider loses its CPDLC
capability the re-route clearance may be requested from the next FIR.

**REPORT**

**of the**

**SEPARATION WORKING GROUP**

## 

## 

**[SEPARATION WORKGROUP MEETING]{.underline}**

**1. INTRODUCTION**

1.1 The Separation Working Group considered working papers and
associated

documentation presented during the plenary session on the 7^th^ of
December, and working

papers presented during the working group meetings.

1.2 The working group considered a number of issues, including a review
of the

Asia/Pacific weather deviation procedures, issues relating to the use of
ADS in the

application of separation, and the implementation of RVSM. More detailed
descriptions of

the work of the group are contained in the following paragraphs.

**2. PARTICIPANTS**

2.1 The following participated in the separation working group meeting:

  ----------------------------------- -----------------------------------
  **Name**                            **Organisation**

  Adrian Dumsa                        Airservices Australia \[chair\]

  Gus Nezer                           FAA

  Roy Grimes                          FAA

  Leslie McCormick                    FAA \[chair RVSM discussion\]

  Chuck Reavis                        FAA

  Annie Coutin                        SEAC French Polynesia

  Roland Dugail                       SEAC French Polynesia

  Len Wicks                           CAA NZ

  Kevin Broome                        IFATCA

  Pat Thomas                          Airservices Australia

  Peter Foreman                       IFALPA

  Kim Joyce                           CSSI

  Mike Cuddy                          United Airlines

  Gene Cameron                        United Airlines

  Neil Jonasson                       IATA

  Owen Dell                           ICAO (Bangkok Office)

  Naomi Woodford                      Airservices Australia

  Jeff Spencer                        Airservices Australia

  Inia Sega                           CAA Fiji

  Gary Lawson-Smith                   IATA Observer

  Tom Barclay                         FAA

  Ian Varcoe                          Air New Zealand

  Ken Alexander                       USAF

  Murray Warfield                     Qantas

  Bryan Pawson                        Airways Corporation of NZ

  Hamish Gray                         Airways Corporation of NZ
  ----------------------------------- -----------------------------------

1.  A number of other people joined the WG for specific discussions
    including RVSM.

**3. REPORT ON OPEN ACTION ITEMS FROM LAST MEETING**

3.1 The open action items from the last meetings (ISPACG/10, 11 and 12)
were carried

forward into the work programme for this meeting, and updated as
follows:

+-----------------------+-----------------------+-----------------------+
| **ISPACG/10**         | ### Statu             | ### Sta               |
|                       | s/ Comments {#status- | tus/comments {#status |
| **Open Action Item    | comments .unnumbered} | comments .unnumbered} |
| Number**              |                       |                       |
|                       | **at ISPACG/ 11**     | **At ISPACG/13**      |
+-----------------------+-----------------------+-----------------------+
| **14.** Examine the   | **ON-GOING** - 60NM   | Implemented on the    |
| feasibility of        | lateral separation    | 23^rd^ of April 1998. |
| introducing RNP in    | was introduced in the |                       |
| the Tasman Sea        | Tasman Sea area on    | **Action Item         |
| airspace, in          | 14^th^ September      | CLOSED**.             |
| conjunction with the  | 1995. A review of the |                       |
| introduction of 60NM  | first year of         |                       |
| lateral separation    | operation was         |                       |
|                       | reported at           |                       |
|                       | ISPACG/11. The        |                       |
|                       | meeting considered    |                       |
|                       | the implementation of |                       |
|                       | RNP 10 within that    |                       |
|                       | airspace, and work is |                       |
|                       | on-going between CAA  |                       |
|                       | NZ, CASA and FAA to   |                       |
|                       | resolve the           |                       |
|                       | regulatory aspects    |                       |
|                       | associated with RNP   |                       |
|                       | 10, prior to wider    |                       |
|                       | consultation with     |                       |
|                       | service providers and |                       |
|                       | airspace users.       |                       |
+-----------------------+-----------------------+-----------------------+
| **32.** Introduction  | **ON-GOING** - Refer  | **ON-GOING**-lateral  |
| of 50NM RNAV          | checklist document    | implemented in some   |
| longitudinal/50NM     | referred to in        | areas - longitudinal  |
| lateral separation    | paragraph 4.          | approved, but subject |
|                       |                       | to on-going           |
|                       |                       | evaluation of         |
|                       |                       | procedures.           |
+-----------------------+-----------------------+-----------------------+
| **33.** Introduction  | **ON-GOING**          | **ON-GOING**          |
| of 30NM longitudinal  |                       |                       |
| & 30NM lateral        |                       |                       |
| separation between    |                       |                       |
| FANS 1 equipped       |                       |                       |
| aircraft              |                       |                       |
+-----------------------+-----------------------+-----------------------+
| **34.** In-trail      | **ON-GOING**          | **ON-GOING -** no     |
| climb using distance  |                       | further work at this  |
| based information     |                       | meeting               |
+-----------------------+-----------------------+-----------------------+
| **37.** Review        | **ON-GOING** - First  | Doc 7030 amendment    |
| weather deviation     | AIP SUP/NOTAM issued  | proposal has been     |
| procedures            | by States in February | promulgated.          |
|                       | 1996. Revised at this | Discussion at this    |
|                       | meeting to            | meeting centered on   |
|                       | incorporate the       | two issues -          |
|                       | changes in response   | controller            |
|                       | to concerns raised by | phraseology, and      |
|                       | IFALPA and US ALPA.   | route spacing versus  |
|                       | Agreement that FAA    | separation.           |
|                       | and ICAO Bangkok      |                       |
|                       | should co-operate in  | Controller            |
|                       | proposing a Doc 7030  | phraseology to be     |
|                       | amendment for target  | resolved between      |
|                       | implementation in     | IFATCA and IFALPA. NZ |
|                       | June 1997.            | to coordinate any     |
|                       |                       | change proposal.      |
+-----------------------+-----------------------+-----------------------+
| **38.** Use of        | **ON-GOING**          | Implemented in two    |
| distance based        | -discussed in detail  | States - Australia    |
| information to        | at this meeting.      | and New Zealand -     |
| determine lateral     | Table of lateral      | being evaluated in    |
| separation entry/exit | separation values to  | Oakland.              |
| points in OCA.        | be circulated and     |                       |
|                       | comments discussed at |                       |
|                       | next WG meeting.      |                       |
+-----------------------+-----------------------+-----------------------+
| **39.** Development   | **ON-GOING** - not    | **ON-GOING -** Agreed |
| of a plan for the     | discussed in detail   | an implementation     |
| conduct of a RVSM     | at this meeting       | plan for the South    |
| operational           |                       | Pacific area - refer  |
| demonstration.        |                       | summary of            |
|                       |                       | discussions           |
+-----------------------+-----------------------+-----------------------+
| **56.** Arrange       | **ON-GOING** - refer  | **Item Closed**       |
| promulgation and use  | item 37               |                       |
| of weather deviation  |                       |                       |
| procedures as the     |                       |                       |
| basis of a Doc 7030   |                       |                       |
| amendment proposal.   |                       |                       |
+-----------------------+-----------------------+-----------------------+
| **57.** Implement     | **WORK ON-GOING**     | **ON-GOING**          |
| data collection and   |                       |                       |
| analysis plan to      |                       |                       |
| support the 50/50NM   |                       |                       |
| verification trial,   |                       |                       |
| and to assist ICAO to |                       |                       |
| justify 30/30NM       |                       |                       |
| between RNP4 or       |                       |                       |
| better aircraft.      |                       |                       |
+-----------------------+-----------------------+-----------------------+
| **58.** Review        | **ON-GOING** - RNP10  | **Item Closed**       |
| implementation of     | not yet implemented - |                       |
| RNP10 in the Tasman   | refer item 14         |                       |
| at ISPACG/10          |                       |                       |
+-----------------------+-----------------------+-----------------------+

**4. Report of Meeting**

**4.1** **Weather Deviation**

> *Note: The report on item 4.1 is a summary report only. There was long
> debate over a number of days on the weather deviation issue, and it
> was not possible to capture all discussions verbatum.*

4.1.1 Roy Grimes presented an overview of the weather deviation issues
and discussion to

date. This included an overview of data collected in response to the
issue of controller

response times - at ISPACG 12 there had been discussion on a range of
values from 2 or 3

minutes requested by IFALPA, to 5 minutes suggested by FAA.

4.1.2 The principle issues were the need to mitigate pilot deviation
without clearance, and

definition of adequate response time from controllers.

4.1.3 The FAA presented proposed methodology and assumptions for
defining "adequate" controller response time when 50nm separation is
applied and guidance for controller and pilot action for "minor" track
deviations. Key points discussed were:

-   ATC must handle weather deviation requests with priority.

-   The Annex 2 paragraphs 3.6.2.1.1 and 3.6.2.1.3 require the pilot to
    fly centerline and notify ATC when he/she deviates.

-   A methodology was proposed to first define that portion of the 50nm
    separation standard that could be allocated to "navigation position
    uncertainty" and than to define the portion of the 50nm that could
    be considered as additional buffer in the 50nm lateral standard for
    communications system limitations and lack of surveillance.

-   The methodology led to a proposal that navigation uncertainty in an
    RNP-10 airspace was 15nm for a single aircraft and 30nm for two
    aircraft abeam. This left 20nm to be considered as additional buffer
    in the separation standard for the lack of surveillance and
    communications limitations. It was proposed that 10nm of the buffer
    could be assigned to a single aircraft.

-   It was proposed that the 10nm buffer be considered in determining
    adequate controller response time to a weather deviation request.

-   To define "adequate" controller response time, a weather deviation
    of 30nm was diagrammed to show the distance/time between a point
    70nm prior to cells at which the pilot could identify the magnitude
    and direction of the deviation, the point at which the aircraft
    deviated from track by 10nm and a point 30nm abeam the cell. This
    effort led to the proposal that adequate controller response time
    for 50nm minimum lateral separation should be approximately 4.3
    minutes.

-   To mitigate unnecessary pilot and controller response to minor (10nm
    or less) track deviations, it was proposed that guidance could be
    for pilots to notify ATC of such deviations IAW Annex 2, but action
    not be required to establish vertical or 50nm lateral separation
    until a deviation in excess of 10nm was made. The group did not
    believe that current ATC requirements for applying separation would
    allow such guidance to be promulgated.

-   It was proposed that action be taken to clarify the application of
    the term "emergency authority" to weather deviations made with ATC
    clearance not available.

4.1.4 Roy presented the results of a weather deviation survey - the data
was collected from

277 flights over a 6 month period from July 97. Tahiti also presented a
paper showing the results of a weather deviation survey over a 13 month
period from January 1997 with data collected from 1261 flights
connected; 452 weather deviations have been analysed.

4.1.5 There was general discussion on the wording in Annex 2 Chapter 3
paras 3.6.2 et al,

regarding adherence to flight plan or track. The argument was that the
paras could be

interpreted to mean that where a pilot deviates from track, but not from
flight plan, it may not

be an issue of captain's authority.

4.1.6 Neil Jonasson presented a view that actual aircraft performance
was better than the

design parameters used to determine the separation minima of 50NM, and
that the actual or

normal performance of aircraft should now be taken into account.

4.1.7 There was general discussion relating to RNP, actual nav
performance and core

performance, risk modelling and related matters. It was agreed to break
the discussions into

sessions over several days, in order to avoid overheating the debate.

4.1.8 There was discussion on whether or not a controller would be aware
that aircraft

deviations were occurring, and what action the controller would take if
he did become aware

of that fact. This would be more telling in an ADS environment, where
the deviation would

be displayed to the controller.

4.1.9 A fundamental discussion on separation and separation minima
ensued - however, it

was eventually agreed that there was indeed a difference between
separation minima and

aircraft spacing. It was noted that the Annex 11 amendment supporting
50NM route spacing

did make reference to the need to take into account factors such as
convective weather in

parallel track situations.

4.1.10 Roy Grimes addressed the issue of the need to collect further
data on controller

response times in South Pacific FIR's prior to expanding 50nm lateral
separation to areas

where convective weather presents a significant problem. He stated that
an agreed criteria

for adequate response times was needed. The IFALPA position remained
that controllers

should respond within approximately 2.5 minutes 95% of the time. The FAA
proposed a

criteria of 4.3 minutes 95% of the time be adopted based on the
methodology discussed in

paragraph 4.1.3. The group was not prepared to adopt either proposal

4.1.11 It was agreed that more work would need to be undertaken on this
matter. In

particular, it was agreed that some analysis work be done with a view to
recognising the low

density nature of the airspace in the South Pacific, and developing a
reduced separation

minima. This would probably allow maintenance of route spacings as
currently

planned. Some actions have been identified in the work plan shown at
Paragraph 5.

2.  **ADS Operating Context**

4.2.1 Adrian Dumsa presented three papers relating to the use of
displayed ADS

information, and in particular, a draft ICAO PANS-RAC amendment proposal
which has

reached a high level of maturity through the RGCSP and ADSP.

4.2.2 There was a deal of discussion on this issue, with Working Group
members agreeing

that the document would be very valuable in establishing a context for
the operation of ADS

systems.

4.2.3 A number of minor amendments were proposed. There was also some
discussion on

the addressing issue and identification, and in particular the need to
ensure, in an ADS

environment, that the services provided by ATS were in fact provided to
the correct aircraft.

4.2.4 It was agreed to forward these amendments and issues to the ADSP
WG meeting to

be held in Adelaide in February 1999.

**4.3 ADS Level Information**

4.3.1 Discussion was held on the use of ADS level information in the
application of

vertical separation. This stemmed from debate and discussions at both
RGCSP and ADSP on

whether or not the level occupancy values currently specified in
PANS-RAC for Mode C

could also be applied for ADS.

4.3.2 The WG supported the concept of the use of ADS level information
based on current

Mode C level occupancy procedures.

**4.4 RVSM Implementation**

4.4.1 Leslie McCormick, FAA, and Chairperson of the ICAO RVSM
Implementation Task

Force, led a discussion on the implementation of RVSM in the South
Pacific area. The

following tasks were accomplished during the discussion:

1.  Reviewed IP/4, *Reduced Vertical Separation Minima*, and WP/5,
    *Pacific Reduced Vertical Separation Minimum (RVSM) Implementation
    Strategy*

2.  Identified how the ATS Providers planned to apply RVSM within their
    airspace

3.  Identified where transitions would be required

4.  Developed a "straw-man" operational concept for presentation to the
    next meeting of the ICAO RVSM Implementation Task Force

5.  Identified "leads" for RVSM for each ATS Provider State for further
    coordination and communication

    2.  Owen Dell, ICAO Asia Pacific Regional Office, presented IP/4.
        This paper

detailed the outcome of the First Meeting of the ICAO RVSM Task Force
(RVSM/TF/1), held in Tokyo, Japan, on 18 November 1998. The presentation
highlighted the following areas:

1.  Plans for operational implementation in the Oakland and Tokyo Flight
    Information Regions (FIRs)

2.  The need to have a regional agreement by way of an amendment to the
    Regional Supplementary Procedures -- Doc 7030 prior to
    implementation

3.  Outstanding issues relating to airworthiness and approval of
    aircraft

4.  The need to establish an airspace monitoring program

5.  An overview of the work done in the area of collision risk modelling
    for RVSM

6.  Implementation management considerations, including the publication
    of the *Guidance Material on the Implementation of a 300 m (1000 ft)
    Vertical Separation Minimum (VSM) for Application in the Airspace of
    the Pacific*

7.  The project action plan presented to the RVSM/TF/1

    2.  It was emphasised that much work remained to be accomplished in
        the next 14

months in order to meet the target implementation date of 24 February
2000. The next meeting of the RVSM/TF is scheduled to be held in Los
Angeles, California, on 1-5 February 1999. All ISPACG members were
reminded of the importance of this forthcoming meeting and urged to
participate.

3.  Leslie McCormick presented WP/5, which provided a summary input from
    several

Pacific ATS Provider States on implementation plans within their
respective FIRs. In addition to the plans for implementation within the
Oakland FIR, the paper provided a copy of a draft Aeronautical
Information Circular (AIC) prepared by New Zealand, a summary of the
phased implementation planned by Fiji, and concerns raised by Tahiti in
their consideration of implementation of RVSM.

4.  While detailed presentations of working and information papers on
    the safety

analysis and collision risk modelling did not take place during the
session, all participants were strongly urged to review the following
papers and provide comments to the ICAO Asia Pacific Regional Office, or
to Leslie McCormick, not later than 31 December in order that issues and
concerns may be reviewed and addressed at the RVSM/TF/2 meeting.

1.  WP/7 -- *Proposed Vertical Collision Risk Model Associated with
    Formation Flights in PAC RVSM Airspace*

2.  WP/8 -- *Proposed Collision Risk Model for Two Aircraft in Vertical
    Alignment for their Entire PAC Oceanic Crossing*

3.  WP/9 -- *Estimating the Probability and Duration of Horizontal
    Overlaps Experienced by Airplanes Travelling on Intersecting Ocean
    Routes*

4.  WP/10 -- *Progress in the Development of a Model for Estimating the
    Risk of Collision at Intersections of Oceanic Air Routes*

5.  IP/5 -- *Assurance of Safe RVSM Implementation*

    2.  It was noted that the material in IP/5 was expected to serve as
        the

justification and safety analysis in support of the proposed amendment
to Doc 7030.

4.4.7 Roy Grimes, FAA, presented the North Atlantic Doc 7030, and
addressed the

changes required for the proposed Pacific Doc 7030, which include the
following areas:

1.  Minimum aviation system performance standards (MASPS) approval

2.  Monitoring requirements

3.  Area of applicability

4.  Approval status and aircraft registration

5.  Special procedures for in-flight contingencies

6.  Special procedures to mitigate wake turbulence encounters

4.4.8 In order to receive approval of an amendment to Doc 7030 prior to
implementation, it will be necessary for the proposed amendment to be
finalised at the RVSM/TF/2 meeting.

4.4.9 The group was informed of planned meetings that will further the
work toward

implementation of RVSM in the Region:

-   RVSM/TF/2 -- Los Angeles -- 1-5 Feb 1999

-   RVSM Seminar -- Singapore -- 16-17 Mar 1999

-   RVSM/TF/3 -- Anchorage -- April/May 1999

-   Report to ATS/AIS/SAR/SG/9 -- Bangkok -- 12-16 Jul 1999

-   RVSM/TF/4 -- location TBD -- Aug 1999

-   RVSM/TF/5 -- Tokyo -- Nov 1999 (Go/No-Go Decision)

4.4.10 Following a general discussion of RVSM by the working group, a
smaller group

made up of ATS Providers, regulatory authorities, ICAO, representatives
from international

organisations, and airspace users met to discuss the operational concept
for the

implementation of RVSM within the South Pacific.

4.4.11 The United States, Australia, New Zealand, Fiji and Tahiti agreed
a tentative

operational concept. All States with the exception of Tahiti support a
target date for initial

implementation of 24 February 2000. Due primarily to concerns about
controller training

and adaptation to a number of technological changes that will occur
within the next year,

Tahiti can not commit to meeting the 24 February date; however, they
support the RVSM

concept and will establish a later implementation date. There was a
preference expressed

that RVSM be implemented between flight levels 290 and 390, inclusive.
The use of the

single alternate flight level allocation scheme requires further
research. Only the Oakland

FIR is expected to be exclusionary airspace, with other ATS Providers
operating in a "mixed

environment" where priority will be given to RVSM-approved aircraft to
the extent

practicable. It is expected that all airspace will become exclusionary
as more aircraft equip

for RVSM.

4.4.12 States bordering with adjacent FIRs that will not be implementing
RVSM were

reminded of the need to urgently consider transition areas and
procedures. While it is

preferable to have radar coverage in the transition areas, some
transitions may be required to

take place in non-radar airspace.

4.4.13 Contacts for each ATS Provider State were designated:

> **United States:** Leslie McCormick
>
> **Australia:** Naomi Woodford (ASA) and TBD (CASA)
>
> **New Zealand:** Mark Goodall (ACNZ) and Rodney Bracefield (CAA)
>
> **Fiji:** Inia Sega
>
> **Tahiti:** Georges Claustre

**4.5 Review of Action Items from Previous Meeting**

4.5.1 The action items outstanding from ISPACG/10, 11 and 12 were
reviewed and

updated as per paragraph 3 above. In addition, actions arising from the
discussions of the last

Separation WG meeting were discussed and updated.

4.5.2 Of the 11 items identified, two action items remain to be
completed - one relates to

the decision to develop procedures for short term tactical use of 50NM
lateral separation -

further work will be done on this; however, it was felt that with the
imminent implementation

of ADS in a number of States, this may not be a high priority task.

4.5.3 The other outstanding item was related to the preparation of a
safety case for the

30/30 scenario. This will be actioned before the next meeting in
accordance with the action

plan at Paragraph 5.

4.5.4 Two IP's were presented by the FAA to address action items - one
gave a report on

progress with relation to "in-trail climb", and the other relating to 10
minute separation

without the use of Mach number.

**5. Future Work Programme**

5.5.1 The WG discussed plans for future work, structured on 5 key areas
-

-   Reduced Separation Minima (30/30 et al)

```{=html}
<!-- -->
```
-   RNP10/30NM Lateral in low density airspace

-   RNP4/30NM Lateral/Longitudinal in all density airspace

-   "Manoeuvring airspace" in Wx Deviation situations

```{=html}
<!-- -->
```
-   RVSM Implementation

```{=html}
<!-- -->
```
-   in accordance with report

```{=html}
<!-- -->
```
-   Weather Deviation Phraseology

```{=html}
<!-- -->
```
-   resolution by IFALPA/IFATCA

-   7030 amendment

```{=html}
<!-- -->
```
-   ACAS/TCAS Implementation

```{=html}
<!-- -->
```
-   States implementation programme

-   training and education

-   harmonisation of controller actions

-   information on regulatory changes etc

```{=html}
<!-- -->
```
-   ADS Procedures Alignment

```{=html}
<!-- -->
```
-   controller training and education

-   ATS procedures

5.2 This was used to establish the following work plan:

+-----+----------------------------------------+----------+----------+
| **  | **Action**                             | **       | **Action |
| Ite |                                        | Action** | by**     |
| m** |                                        |          |          |
+-----+----------------------------------------+----------+----------+
| 1   |                                        |          |          |
| .   |                                        |          |          |
| **R |                                        |          |          |
| edu |                                        |          |          |
| ced |                                        |          |          |
|     |                                        |          |          |
|     |                                        |          |          |
| Sep |                                        |          |          |
| ara |                                        |          |          |
| tio |                                        |          |          |
| n - |                                        |          |          |
|     |                                        |          |          |
|  30 |                                        |          |          |
| /30 |                                        |          |          |
|     |                                        |          |          |
|  et |                                        |          |          |
|     |                                        |          |          |
|   a |                                        |          |          |
| l** |                                        |          |          |
+-----+----------------------------------------+----------+----------+
| 1.1 | Research feasibility of reduced        | Adrian   | End      |
|     | separation minima of 30NM lateral      | Dumsa    | January  |
|     | separation in low density traffic      |          | 1999     |
|     | areas in the South Pacific areas using |          |          |
|     | RNP10 or RNP 4                         |          |          |
+-----+----------------------------------------+----------+----------+
| 1.2 | Develop amendment proposal using       | A        | End      |
|     | Safety Case methodology                | ustralia | March    |
|     |                                        |          | 1999     |
+-----+----------------------------------------+----------+----------+
| 1.3 | Develop Doc 7030 amendment proposal    | A        | End June |
|     |                                        | ustralia | 1999     |
+-----+----------------------------------------+----------+----------+
| 1.4 | Develop implementation plan            | All WG   | I        |
|     |                                        | Members  | SPACG/14 |
+-----+----------------------------------------+----------+----------+
|     |                                        |          |          |
+-----+----------------------------------------+----------+----------+
| 2   |                                        |          |          |
| .   |                                        |          |          |
| **R |                                        |          |          |
| VSM |                                        |          |          |
|     |                                        |          |          |
|   I |                                        |          |          |
| mpl |                                        |          |          |
| eme |                                        |          |          |
| nta |                                        |          |          |
| tio |                                        |          |          |
| n** |                                        |          |          |
+-----+----------------------------------------+----------+----------+
| 2.1 | Review safety analysis and collision   | All      | 31 Dec   |
|     | risk modelling papers and provide      |          | 1998     |
|     | comments to (ICAO Bangkok Office)      |          |          |
+-----+----------------------------------------+----------+----------+
| 2.2 | Further develop implementation         | All      | 1 Feb    |
|     | strategy                               |          | 1999     |
+-----+----------------------------------------+----------+----------+
| 2.3 | Participate in ICAO RVSM               | All      | On-going |
|     | Implementation Task Force              |          |          |
+-----+----------------------------------------+----------+----------+
| 2.4 | Begin operational demonstration        | US,      | 24 Feb   |
|     |                                        | Au       | 2000     |
|     |                                        | stralia, |          |
|     |                                        | New      |          |
|     |                                        | Zealand, |          |
|     |                                        | Fiji     |          |
+-----+----------------------------------------+----------+----------+
| 2.5 | Full implementation                    | All      | 24 Feb   |
|     |                                        |          | 2001     |
+-----+----------------------------------------+----------+----------+
|     |                                        |          |          |
+-----+----------------------------------------+----------+----------+
|     |                                        |          |          |
+-----+----------------------------------------+----------+----------+
| *   |                                        |          |          |
| *3. |                                        |          |          |
| Ph  |                                        |          |          |
| ras |                                        |          |          |
| eol |                                        |          |          |
| ogy |                                        |          |          |
| for |                                        |          |          |
| W   |                                        |          |          |
| eat |                                        |          |          |
| her |                                        |          |          |
| De  |                                        |          |          |
| via |                                        |          |          |
| tio |                                        |          |          |
| n** |                                        |          |          |
+-----+----------------------------------------+----------+----------+
| 3.1 | Resolve outstanding difficulties over  | Kevin    | End Feb  |
|     | current phraseology                    | Broo     | 1999     |
|     |                                        | me/Peter |          |
|     |                                        | Foreman  |          |
+-----+----------------------------------------+----------+----------+
| 3.2 | Distribute new phraseology proposal to | Peter    | End      |
|     | WG members                             | Foreman  | March    |
|     |                                        |          | 1999     |
+-----+----------------------------------------+----------+----------+
| 3.3 | Develop Doc 7030 amendment proposal    | Hamish   | End      |
|     |                                        | Gray     | April    |
|     |                                        |          | 1999     |
+-----+----------------------------------------+----------+----------+
|     |                                        |          |          |
+-----+----------------------------------------+----------+----------+
| *   |                                        |          |          |
| *4. |                                        |          |          |
| AC  |                                        |          |          |
| AS/ |                                        |          |          |
| TCA |                                        |          |          |
| S** |                                        |          |          |
+-----+----------------------------------------+----------+----------+
| 4.1 | Collate and distribute information     | All      | End      |
|     | from each State regarding TCAS/ACAS    | members  | March    |
|     | implementation programme, including    | through  | 1999     |
|     | pilot and controller training and      | Len      |          |
|     | procedures, regulatory requirements    | Wicks    |          |
|     | etc                                    | (CAA NZ) |          |
+-----+----------------------------------------+----------+----------+
| 4.2 | Examine ATS procedures and identify    | All WG   | End June |
|     | differences, deficiencies, etc         | members  | 1999     |
+-----+----------------------------------------+----------+----------+
| 4.3 | Develop harmonised ATS procedures, in  |          | TBD      |
|     | accordance with ICAO plans for ACAS    |          |          |
|     | implementation                         |          |          |
+-----+----------------------------------------+----------+----------+
| 4.4 | Develop implementation strategy for    |          | TBD      |
|     | harmonised procedures                  |          |          |
+-----+----------------------------------------+----------+----------+
|     |                                        |          |          |
+-----+----------------------------------------+----------+----------+
| *   |                                        |          |          |
| *5. |                                        |          |          |
| ADS |                                        |          |          |
| Pro |                                        |          |          |
| ced |                                        |          |          |
| ure |                                        |          |          |
| s** |                                        |          |          |
+-----+----------------------------------------+----------+----------+
| 5.1 | Distribute ADSP/RGCSP material on ADS  | Adrian   | End      |
|     | Operating Context                      | Dumsa    | March    |
|     |                                        |          | 1999     |
+-----+----------------------------------------+----------+----------+
| 5.2 | Review ADS operating procedures        | All WG   | End      |
|     |                                        | members  | April    |
|     |                                        |          | 1999     |
+-----+----------------------------------------+----------+----------+
| 5.3 | Align local ADS operating procedures   | All WG   | TBD      |
|     | with draft ADSP material, as required  | members  |          |
+-----+----------------------------------------+----------+----------+
| 5.4 | Develop harmonised ADS operating       |          | TBD      |
|     | procedures                             |          |          |
+-----+----------------------------------------+----------+----------+
|     |                                        |          |          |
+-----+----------------------------------------+----------+----------+
| *   |                                        |          |          |
| *6. |                                        |          |          |
| Act |                                        |          |          |
| ual |                                        |          |          |
| C,N |                                        |          |          |
| and |                                        |          |          |
| S   |                                        |          |          |
| P   |                                        |          |          |
| erf |                                        |          |          |
| orm |                                        |          |          |
| anc |                                        |          |          |
| e** |                                        |          |          |
+-----+----------------------------------------+----------+----------+
| 6.1 | Conduct research into the possibility  | All WG   | End      |
|     | of using the actual or certified       | members  | April    |
|     | performance of C, N or S capabilities  |          | 1999     |
|     | of aircraft in the determination of    |          |          |
|     | separation minima and air traffic      |          |          |
|     | service provision.                     |          |          |
+-----+----------------------------------------+----------+----------+
| 6.2 | Develop draft concept of operations    | All WG   | End June |
|     | for the potential use of this          | members  | 1999     |
|     | information                            |          |          |
+-----+----------------------------------------+----------+----------+
| 6.3 | Collate draft concepts                 | TBD      | End      |
|     |                                        |          | S        |
|     |                                        |          | eptember |
|     |                                        |          | 1999     |
+-----+----------------------------------------+----------+----------+
| 6.4 | Develop concept and set programme for  | All WG   | I        |
|     | associated minima                      | members  | SPACG/14 |
+-----+----------------------------------------+----------+----------+
|     |                                        |          |          |
+-----+----------------------------------------+----------+----------+

**Acronyms**

AAC Airline Administrative Communication

ABI Advanced Boundary Information

ACARS Aircraft Communications Addressing and Reporting System

ACAS Airborne Collision and Avoidance System (ICAO)

ACC Area Control Center

ACNZ Airways Corporation of New Zealand

ADIS ADS and Data Link Interim System (Datalink system for the Brisbane
FIR)

ADS Automatic Dependent Surveillance

ADS-B Automatic Dependent Surveillance Broadcast

AEEC Airline Electronic Engineering Committee

AFN ATS Facilities Notification

AFTN Aeronautical Fixed Telecommunication Network

AIDC ATC Inter-Facility Ground/Ground Data Communications

AIP Aeronautical Information Publication

AMSS Aeronautic Mobile Satellite System

ANZ Air New Zealand

AOC Airline Operational Communications

AOAS Advanced Oceanic Automation System (FAA system will supersede ODL,

among others)

APANPIRG Asia/Pacific Air Navigation Planning and Implementation
Regional Group

AQP Aircom Quality Performance

ASA Airservices Australia

ATC Air Traffic Control

ATM Air Traffic Management

ATN Aeronautical Telecommunication Network

ATS Air Traffic Services

ATSU ATS unit

AUSEP Australian RNAV

BEP Back End Processor

CAA Civil Aviation Authority

CAAF CAA of Fiji

CAA NZ CAA of New Zealand

CAA PNG CAA of Papua New Guinea

CAA SI CAA of Solomon Islands

CASA Civil Aviation Safety Authority (Australia)

CNS Communications, Navigation, Surveillance

CPDLC Controller Pilot Data Link Communications

CPL Current Plan

CPS Central Processing System

CRM Collision Risk Methodology

CVR Cockpit Voice Recorder

DARP(S) Dynamic Airborne Route Planning (System)

DCPC Direct Controller-Pilot Communications

DGAC Direction Générale de l'Aviation Civile (French CAA)

DL Downlink message

DLASD Data Link Application and System Document

DOTS Dynamic Ocean Tracking System

DSP Designated Service Provider

EASY Enhanced ADS and Datalink System

EUROCAE European Organisation for Civil Aviation Equipment

FAA Federal Aviation Administration

FANS Future Air Navigation System

FDR Flight Data Record

FHA Functional Hazard Analysis

FIR Flight Information Region

FIT FANS Interoperability Team

FMC Flight Management Computer

FMS Flight Management System

GES Ground Earth Station (satellite)

GLONASS Global Orbiting Navigation Satellite System (Russia)

GNSS Global Navigation Satellite System

GPS Global Positioning System (USA)

HF High Frequency (3-30 Mhz)

HMI Human Machine Interface

HMI Hazardously Misleading Information

IATA International Air Transport Association

IAM ISPACG Application Manual

ICAO International Civil Aviation Organisation

ICD Interface Control Document

IFATCA International Federation of Air Traffic Controllers Association

IFALPA International Federation of Airlines Pilots Association

INS Inertial Navigation System

IOCS Interim Oceanic Control System (Interim datalink system for the

Auckland FIR)

IPACG Informal Pacific ATS Coordinating Group

IRS Inertial Reference System

ISPACG Informal South Pacific ATS Coordinating Group

JAA Joint Aviation Authorities (Europe)

JAR Joint Airworthiness Requirement (Europe)

LAAS Local Area Augmentation System

LRNS Long Range Navigation System

MASPS Minimum Aviation Systems Performance Standards

MNPSA Minimum Navigation Performance Specification Airspace

MOPS Minimum Operation Performance Standards

MCDU Multipurpose Control Display Unit (ACARS & FMC)

MU Management Unit (ACARS)

NDA Next Data Authority

NOTAM NOtice To AirMen

OCS Oceanic Control System (Datalink system Auckland FIR, will supercede
IOCS)

ODL Oceanic Data Link (Datalink system for the Oakland FIR)

OED Operational Environment Definition

OSA Operational Safety Assessment

PACOTS Pacific Organised Track System

QFA QANTAS

QOS Quality Of Service

RA Resolution Advisory

RAIM Receiver Autonomous Integrity Monitoring

RAN Regional Air Navigation

RCP Required Communication Performance

RFC Request For Change

RGCSP Review of the General Concepts of Separation Panel (ICAO subgroup)

RNAV Area Navigation

RNP Required Navigation Performance

RSP Required Surveillance Performance

RTA Required Time of Arrival

RTCA Requirements and Technical Concepts for Aviation Inc

RTSP Required Total System Performance

RVSM Reduced Vertical Separation Minima

SARPs Standard And Recommended Practices

SATCOM Satellite Communication

SEAC Service d'Etat de l'Aviation Civile (French Polynesia)

SITA Société Internationale de Télécommunications Aéronautiques

SO&R System Objectives and Requirements (FANS-A document)

SPOM South Pacific Operations Manual

SR&O System Requirements and Objectives (FANS-1 document)

STNA Service Technique de la Navigation Aérienne (French technical
service)

TA Traffic Advisory

TAAATS The Australian Advanced ATS System (TAAATS will supersede ADIS)

TCAS Traffic Alert and Collision Avoidance System (USA)

TBC The Boeing Company

TDM Track Definition Message

TMU Traffic Management Unit

UAL United Airlines

UL Uplink message

VHF Very High Frequency (30-300 Mhz)

VIVO Visualisation des Vols Océaniques (Situation display & datalink
system for the Tahiti FIR)

WAAS Wide Area Augmentation System