# Summary of Discussions

Twenty-First Meeting of the

Informal Pacific Air Traffic Control Coordination Group

(IPACG/21)

7-11 June 2004; Tokyo, Japan

1.  **Background**

1.1 The Twenty-First Meeting of the Informal Pacific Air Traffic Control
(ATC) Coordinating Group (IPACG/21) was held at the Koku kaikan in
Tokyo, Japan, from 7-11 June 2004. The IPACG was established to provide
a forum for air traffic service (ATS) providers and airspace users to
informally meet and explore solutions to near term air traffic control
(ATC) problems that limit the capacity or efficiency within the
Anchorage, Oakland, and Tokyo Flight Information Regions (FIRs).

2.  **Welcome and Opening Remarks**

2.1 The meeting was co-chaired by Mr. Akira Ono for the Japan Civil
Aviation Bureau (JCAB) and Ms. Leslie McCormick for the Federal Aviation
Administration (FAA). The meeting attendees are shown in Appendix A.

2.2 Mr. Ono welcomed the participants to IPACG/21 and introduced Mr.
Shinta Ehara, Director of the Air Traffic Control Division, JCAB. Mr.
Ehara stated it was a great honor to welcome all participants to the
IPACG meeting. He noted that IPACG was established for collaboration
between FAA and JCAB. Mr. Ehara stated that during the last 20 meetings,
reduced vertical separation minimum (RVSM) and data link have enhanced
safety and efficiency across the Pacific. He hoped that the meeting
discussions would be active and fruitful and that everyone's stay in
Tokyo would be a pleasant one.

2.3 Ms. McCormick thanked Mr. Ono and the JCAB staff for hosting the
meeting. She stated that the airlines' representatives place great
importance on the work of this group and their support is appreciated.
She mentioned that the FAA delegation was quite small this time due to
the implementation of the new oceanic automation system. She noted that
although it is a small group, the delegation hopes to contribute to the
success of the meeting. Ms. McCormick then commented on the major
reorganization in the FAA with the addition of a new organization called
the Air Traffic Organization (ATO). She further stated that the new
Director of Air Traffic Operations Planning - International, Mr. Jack
Howell, is very supportive of international meetings and the work we do
with Japan and will continue to support this effort.

4.  Mr. Ono recognized the Air Traffic Management Working Group (ATM WG)
    co-chairs,

Mr. Gary Hancock of the FAA, and Mr. Hiroyuki Nakano of JCAB, and
thanked Mr. Yoshiki Imakawa for chairing the FANS Interoperability Team
(FIT) meeting.

2.5 The meeting was informed that the ICAO Asia Pacific Regional Office
was unable to send a representative to this meeting due to staffing and
funding shortages. IPACG assists the Regional Office in addressing
relevant air traffic management (ATM) matters for the major traffic
flows between Asia and North America (via Central and North Pacific),
and ICAO is strongly encouraged to make a representative available to
participate in future IPACG meetings.

## **Agenda Item 1: Review and Approve Agenda**

3.1 The following agenda was adopted by the meeting:

Agenda Item 1: Review and approve agenda

Agenda Item 2: Air Traffic Management (ATM) Issues

Agenda Item 3: Communications/Navigation/Surveillance (CNS) Issues

Agenda Item 4: Report on the outcome of the FANS Interoperability Team
(FIT) Meeting

Agenda Item 5: Review and update of CNS/ATM Planning Chart

Agenda Item 6: Evaluation of costs and benefits

Agenda Item 7: Other business

3.  **Submitted Papers**

4.1 The following working and information papers were presented to
IPACG/21 and can be made available upon request.

  -------------------------------------------------------------------------------
  **Paper    **Agenda   **Title**                               **Presented by**
  Number**   Item**                                             
  ---------- ---------- --------------------------------------- -----------------
  WP/1       1          Agenda and Proposed Timetable           Co-chairperson

                        Intentionally Blank                     

  WP/3       2          Oakland FIR Waypoints on PACOTS Tracks  Oakland ARTCC

  WP/4       2          Oceanic In-trail Climb and In-trail     FAA
                        Descent Using TCAS                      

  WP/5       2          Implementation of Reduced Separation    JCAB
                        Minima in the NOPAC and CENPAC Airspace 
                        Using ADS                               

  WP/6       2          ATC Contingency Procedures to be Used   JCAB
                        During Failure of Data Link in Oceanic  
                        Control Airspace                        

  WP/7       2          Traffic Movements within the Tokyo      JCAB
                        Oceanic Control Airspace                

  WP/8       2          Lateral Offsets in NOPAC and CENPAC     JCAB

  WP/9       2          Oakland ARTCC and Tokyo ACC Area (CTA)  Tokyo ACC
                        Airspace                                

  WP/10      2          Concept of Bilateral Contingency Plans  JCAB
                        for North/Central Pacific Airspace      

  WP/11      2          In-flight Contingencies                 FAA

  WP/12      2          Expansion of Reduced Vertical           FAA
                        Separation Minima (RVSM)-Exclusive      
                        Airspace in Oakland and Anchorage       
                        Oceanic Flight Regions (FIRs)           

  WP/13      3          Position Reporting Deficiencies         Oakland ARTCC

  WP/14      5          FAA Update to the CNS/ATM Planning      FAA
                        Chart                                   

  WP/15      7          Airspace Safety Monitoring in the       FAA
                        Pacific Region                          

  WP/16      2          ATS Interfacility Data Communications   FAA
                        (AIDC)                                  

  WP/17      2          Use of Non-Standard Altitude for        FAA
                        direction of flight on G344/R591 when   
                        designated as PACOTS Track(s).          

                                                                

  IP/1       2          Summary of the First Meeting of the     FAA
                        Informal South Pacific ATS Coordinating 
                        Group (ISPACG) 30NM                     
                        Lateral/Longitudinal Separation Working 
                        Group (30/30/WG)                        

  IP/2       6          North Pacific Airspace Cost             FAA Technical
                        Effectiveness (NPACE) Study-An Update   Center and
                                                                Rutgers
                                                                University

  IP/3       2          Required Navigation Performance 4       FAA
                        (RNP4) Oceanic and Remote Operational   
                        Approval                                

  IP/4       7          The Status of Air Traffic Flow          FAA
                        Management (ATFM) Communication Methods 
                        between Federal Aviation Administration 
                        (FAA)/Air Traffic Control System        
                        Command Center (ATCSCC) and Japanese    
                        Civil aviation Bureau (JCAB)/Air        
                        Traffic Flow Management Center (ATFMC)  

  IP/5       2          Removal of Restriction on PACOTS Tracks ATFMC / FAA

  IP/6       2          Automatic Dependent Surveillance -      FAA
                        Contract (ADS-C)                        

  IP/7       3          AIDC Performance Monitoring             JCAB CRA

  IP/8       3          SITA Enhanced Ground to Air Satellite   SITA
                        Voice Service                           

  IP/9       3          SATCOM Voice                            JCAB
  -------------------------------------------------------------------------------

**5.0 Agenda Item 2: ATM Issues**

5.1 Co-chairs of the ATM WG led the discussions on ATM issues.

####### Lateral Offsets in NOPAC and CENPAC

5.2 JCAB presented information regarding the status of ICAO guidelines
on the use of strategic lateral offsets and the effect on airspace
safety. The purpose of the guidelines is to reduce the likelihood of
pilots inadvertently applying procedures different from those specified
for the airspace in which they are operating, and to ensure that the
application of offsets to reduce the risk of collision as a result of
loss of vertical separation will not unduly increase the risk of loss of
lateral separation between aircraft on adjacent tracks.

5.3 JCAB noted that although the ICAO Separation and Airspace Safety
Panel (SASP) Working Group has completed its work on the guidance, the
0, 1, 2NM offset is not yet effective until such time as ICAO
distributes the guidance via a State letter.

5.4 The Northwest Airlines representative inquired if the global
positioning system (GPS) requirement still remained. The revised
guidance does not require that the aircraft be equipped with global
navigation satellite system (GNSS) equipment but does require that the
aircraft have auto-offset capability.

####### In-Flight Contingencies

5.5 The FAA proposed to open discussion on in-flight contingencies or
turnback procedures in Pacific FIRs. Currently the Pacific procedures
call for a 25 NM offset and a level change of 500 ft, while the North
Atlantic procedures call for a 30 NM offset and 500 ft level change.

5.6 The Northwest Airlines representative noted there should be
consistency between the Atlantic and Pacific procedures.

5.7 The United Airlines representative inquired if there was time to
influence the decision to change the turnback contingency procedures in
the North Atlantic. The FAA ATM WG co-chair will check with the
representative for the North Atlantic and provide advice on the status.

5.8 The International Air Transport Association (IATA) representative
stated there has been a difference in the North and South Pacific for
many years. In the South Pacific, half-track spacing, not exceeding 25
miles, is used. Using 300 ft vs 500 ft ensures that the separation is
not dependent on vertical or lateral distance alone. 300 ft is
appropriate in every case because it standardizes procedures for pilots
in all contingencies. He noted that procedures need to be harmonized
between North and South Pacific.

*Expansion of Reduced Vertical Separation Minima (RVSM)-Exclusive
Airspace in Oakland and Anchorage Oceanic Flight Information Regions
(FIRs)*

5.9 FAA announced that plans are underway to raise the upper limit of
RVSM-exclusive airspace from FL390 to FL410 in the Oakland Oceanic,
Anchorage Oceanic and Anchorage Arctic FIRs. This would result in
exclusive RVSM airspace in Oakland Oceanic FIR up to FL410 and will
harmonize with RVSM airspace in Tokyo, Naha, and US domestic FIRs. FAA
will discuss this issue with business aviation representatives and at
upcoming airspace user forums such as the Oceanic Work Group (OWG)
meeting in July. To document this change in RVSM exclusionary airspace,
FAA will update the Pacific and Alaska chart supplements, as
appropriate.

*Use of Non-Standard Altitude for Direction of Flight on G344/R591when
Designated as PACOTS Track(s)*

5.10 FAA recommended use of non-standard altitude for direction of
flight on G344/R591 when designated as PACOTS Tracks. Anchorage Air
Route Traffic Control Center (ARTCC) and Tokyo Area Control Center (ACC)
have been mutually involved in reviewing the use of non-standard
altitude for direction on G344/R591 when these routes are designated as
a portion of the PACOTS Tracks. The facilities have developed a draft
memorandum of understanding (MOU) outlining a 90-day test period to
validate use of these procedures within the PACOTS structure.

5.11 Anchorage ARTCC and Tokyo ACC are coordinating the MOU, which will
be effective as soon as possible.

####### Oceanic In-Trail Climb and In-Trail Descent Using TCAS

5.12 The FAA outlined recent discussions concerning the status of the
Oceanic In-Trail Climb and In-Trail Descent test procedures using
airborne collision avoidance systems (ACAS) and asked for input on both
experiences with and interest in continuing the procedure.

5.13 The IFATCA representative stated that Oakland ARTCC has not
recently used the procedure. The procedure can be cumbersome to the
controller workforce. In the time it takes to do one in-trail climb, 5
or 6 manual climbs may be completed.

5.14 The IFALPA representative stated that with the advent of RVSM in
the North Pacific (NOPAC), the need for the procedure has diminished.

5.15 The United States Air Force representative noted that this
procedure has been published in documents, ensuring crews are
knowledgeable of the procedure. It does not get used often but is a
valuable tool.

5.16 The IATA representative did not poll its members but recalled that
this procedure was suggested in pre-RVSM days. Its need has been
overtaken by ADS in the Pacific. It is still an individual choice of the
operator and should continue to be available.

5.17 The United Airlines representative stated that with multiple
operations across the Pacific, in different circumstances, the procedure
is still valuable. Republishing the procedure for United aircrews will
be completed in the near future. It is hoped that United pilots will
soon be ready to participate again. Additionally, there is another
airline interested in reestablishing this procedure. This procedure
could be replaced someday with ADS-C or even ADS-B.

5.18 JCAB stated the following concerns:

-   The application of this type of separation standard in Class A
    airspace (where visual flight rules (VFR) operation is not
    permitted) is not described in Annexes or Procedures for Air
    Navigation Services (PANS) documents; all aircraft shall be
    separated according to instrument flight rules (IFR) separation
    standards.

-   Use of ACAS for separation purposes. ACAS is a tool for collision
    avoidance and has not been designed for separation purposes. The
    accuracy of distance measurement by ACAS has not been proven.

-   Details of the safety analysis for the minimum separation of 15NM
    during in trail climb in terms of target level of safety.

-   The responsibility for the separation during climb and descent,
    pilot or ATC.

-   Identification process for aircraft concerned.

5.19 In response, the IATA representative provided the following
additional information regarding ACAS and aircraft separation:

-   Annex 11 and PANS-ATM refer to separation by ATC, not by the pilot.

-   ACAS is not an ATC separation tool, but it is a pilot collision
    avoidance tool approved by ICAO and used at distances closer than
    ATC separation minima.

-   ACAS and ATC separations are similar in that the prime function of
    each is the prevention of collision.

-   The accuracy of ACAS distance measurement is not in question. It
    uses the same information provided by the aircraft ATC-transponder
    as secondary surveillance radar (SSR). This standard is in Annex 10.

-   15NM separation is greater than any SSR separation used by ATC.

-   The responsibility for the use of ACAS separation is only with the
    pilots. This is endorsed by ICAO. ACAS overrules ATC in the event of
    a breakdown in ATC.

-   The identification of the two aircraft concerned in the use of ACAS
    is a pilot responsibility in all cases.

####### Traffic Data within the Tokyo Oceanic Control Airspace

5.20 JCAB presented information on traffic movements within the Tokyo
Oceanic Control Airspace and the population of aircraft with data link
and RNP4 capability. The JCAB and FAA have agreed to implement 50NM
longitudinal separation minimum in NOPAC and Central Pacific (CENPAC)
using ADS and controller pilot data link communication (CPDLC) and
intend to further reduce the longitudinal and lateral separation minima
to 30NM in the future. The 50NM longitudinal separation minimum could be
applied to aircraft certified for RNP10 or better, while the 30NM
longitudinal and lateral separation minima could only be applied to
aircraft certified for RNP4 (oceanic). The application of these reduced
separation minima requires satellite data link capability (ADS/CPDLC).

5.21 The United Airlines representative informed the meeting that he
participates in the Informal South Pacific ATS Coordinating Group
(ISPACG) 30NM Lateral/30NM Longitudinal Separation (30/30) WG which is
looking at RNP4 approvals. He stated that the number of aircraft listed
in the paper may not accurately reflect the percentage of RNP4 capable
aircraft in the region.

####### Required Navigation Performance (RNP4) Oceanic and Remote Operational Approval

5.22 The FAA presented a draft FAA order for RNP4 oceanic and remote
operational approval. The order is expected to be finalized and
published in 2 to 6 months. United Airlines indicated that the ISPACG
30/30 WG is looking forward to the completion of the order in time for
use in the planned implementation on 25 November 2004 over the Tasman
Sea. Northwest Airlines stated that addressing RNP4 may not completely
address the requirements for 30/30. The navigation component is just one
element needed to achieve 30/30 capability. Without communication and
surveillance criteria and crew training, aircraft may not meet the
requirements for 30/30 separation. Northwest Airlines expressed a strong
desire to have all the requirements for 30/30 operational approval in
one document that would assist field inspectors in granting approvals.
Northwest Airlines will investigate the development of inspector
guidance with FAA Flight Standards.

####### Concept of Bilateral Contingency Plans for North/Central Pacific Airspace

5.23 JCAB presented a concept of bilateral contingency plans for
North/Central Pacific airspace. The airline representatives encouraged
the development of bilateral plans. FedEx commended JCAB for their
presentation and thought process. As has been pointed out, there would
still be many aircraft arriving and departing the airport despite ATC
facility failure. The FAA generally supported the idea and will develop
a position for the next meeting.

####### Position Reporting Deficiencies

5.24 Oakland ARTCC presented a summary of waypoint position reporting
deficiencies that have occurred in the Oakland FIR and corrective
actions that have been taken.

5.25 United Airlines noted that the aircraft sends actual position
reports, but they are not always processed at Oakland ARTCC because they
are coded incorrectly. Oakland ARTCC will continue to track the data and
provide more information to the next meeting.

5.26 JCAB stated that they have no major problem with overdue position
reporting within Tokyo FIR. Tokyo ACC will investigate the number of
overdue reports in their airspace.

5.27 Oakland ARTCC thanked the airlines for their patience and expressed
appreciation for continuing to work this issue.

####### 

####### Oakland FIR Waypoints on PACOTS Tracks

5.28 Oakland ARTCC presented a proposal to include an Oakland FIR
boundary waypoint when the eastbound PACOTS tracks are generated.
Further discussion will occur at OWG. From the operators' viewpoint,
this may be difficult to do because of waypoint database requirements.
This problem may be alleviated once ADS is operational.

5.29 Oakland ARTCC advised that the FIR crossing would be in the track
advisory message that goes out after routes are generated. United
Airlines said a similar situation exists in the South Pacific.

5.30 The Air Traffic Flow Management Center (ATFMC) advised that the
logic used can accommodate degrees and minutes. If a decision was made
to change the logic, it would take 2-3 months.

5.31 Tokyo ACC advised they are close to a resolution with Oakland
ARTCC.

####### Oakland ARTCC and Tokyo ACC CTA Airspace

5.32 Tokyo ACC presented draft procedures proposing the establishment of
fixes along the Control Area (CTA) boundary between Oakland ARTCC and
Tokyo ACC.

5.33 United Airlines agreed that the proposed additional fixes would be
very helpful to flight crews. Oakland ARTCC and Tokyo ACC will continue
to coordinate efforts.

*Removal of Restriction on PACOTS Tracks*

5.34 ATFMC and FAA presented an update on the removal of restriction on
PACOTS tracks. The trial to remove restrictions on PACOTS Tracks A, 2,
3, 14, and 15 has been successful and procedures have been incorporated
into an MOU. The MOU will become effective in July 2004.

*Automatic Dependent Surveillance -- Contract (ADS-C)*

5.35 The FAA presented a proposal to open discussion on ADS-C testing
within the Anchorage Oceanic FIR. The purpose of the test is to provide
an opportunity for controllers and pilots to gain experience with ADS-C
and to compare ADS-C data with data received in CPDLC position reports.

5.36 Gratitude was expressed toward the airlines for their ongoing
cooperation in aiding in early tests of new equipment and procedures. In
this case there would be costs involved for the operators in allowing
ADS contracts to be established with no immediate gain in service of
efficiency.

5.37 There were questions asked by the airlines that will need to be
directed to the appropriate authorities at Anchorage ARTCC, who were not
available at the meeting:

-   How long will the test last?

-   Why is the contract interval 15 minutes instead of 30 minutes?

    5.38 Anchorage ARTCC will be encouraged to participate in the OWG
    meeting either in person or by teleconference to answer these and
    other questions.

    5.39 The United Airlines representative advised that they are always
    happy to cooperate in such tests. He would encourage Anchorage ARTCC
    to move as soon as possible to use the experience gained in this
    test to implement distance based separation -- 50NM using the
    Micro-EARTS (MEARTS) platform since MEARTS is in place now and the
    Advanced Technologies and Oceanic Procedures (ATOP) system is at
    least a year and a half away.

    5.40 Procedures for this test would be conveyed to the operators by
    publication in the Alaska Supplement.

*Summary of the First Meeting of the Informal South Pacific ATS
Coordinating Group (ISPACG) 30nm Lateral/Longitudinal Separation Working
Group (30/30/WG)*

5.41 The 18th Meeting of the ISPACG held in Nadi, Fiji on 23-26 February
2004, agreed to establish a working group to manage the implementation
of 30/30 separation for trans-Tasman air traffic in the Brisbane and
Auckland FIRs. A summary of the discussions was provided to the meeting.

5.42 Terms of reference for the 30/30 WG were proposed, which were:

a)  To develop benefits-driven implementation plans for the
    implementation of 30NM lateral/30NM longitudinal (30/30) separation
    within selected areas and airspace in the South Pacific;

```{=html}
<!-- -->
```
a)  To consider the need for guidance material on the implementation of
    30/30, and if required, to develop such guidance material;

b)  To ensure the conduct of any required safety assessments based on an
    appropriate collision risk model (CRM); and

c)  To address any other matters as appropriate and relevant to the
    implementation of 30/30 within the South Pacific airspace.

d)  The Task Force will include participation from air traffic service
    providers, regulatory authorities and International Organizations
    represented at ISPACG.

5.43 The ISPACG/18 meeting agreed that assistance from ICAO was not yet
required, as the resources for this phase of implementation existed
within ISPACG. It was agreed that the first implementation would be over
the Tasman Sea, with a target date of 25 November 2004.

5.44 The FAA plans to implement 30/30 initially in a portion the South
Pacific airspace of the Oakland FIR during 2005.

*Implementation of Reduced Separation Minima in the NOPAC and CENPAC
airspace during ADS -- JCAB*

5.45 United Airlines observed that if ATOP is operational at Oakland
ARTCC and Anchorage ARTCC in 2005, Tokyo could possibly go to 50NM
longitudinal in early 2005. JCAB indicated that the Multifunctional
Transport Satellite (MTSAT) would need to be online for Tokyo to
implement 50NM longitudinal at cruise. ADS waypoint reporting and step
climb and descent with 50NM longitudinal separation may be implemented
prior to the commissioning of MTSAT.

**6.0 Agenda Item 3: CNS Issues**

6.1 Co-chairs of IPACG/22 led the discussions on communications,
navigation and surveillance (CNS) issues.

ATS Interfacility Data Communications (AIDC)

6.2 The FAA presented a paper proposing to validate and implement AIDC
between Anchorage ARTCC and Tokyo ACC for all aircraft transiting the
common boundaries between these facilities.

6.3 Anchorage ARTCC and Tokyo ACC were working together on a Memorandum
of Understanding (MOU) to establish AIDC procedures. A key issue in the
discussion was voice verification of AIDC information. An ODP program
fix will be required to eliminate voice notification. Tokyo ACC's
intention is to implement with Anchorage and use the same procedure as
is used with Oakland. The current MOU between Oakland ARTCC and Tokyo
ACC included voice verification.

####### ATC Contingency Procedures to be used during failure of data link in oceanic control airspace

6.4 JCAB presented an updated version of the draft ATC contingency
procedures to be used during failure of data link in the Pacific FIRs
and the proposed amendment to ICAO Doc. 7030.

6.5 The IFALPA representative questioned using the two-fold approach of
a 500 feet level change and a lateral offset. He noted that there are
different procedures for different environments and this adds another
layer of confusion to pilot.

[]{.mark}

*AIDC Performance Monitoring*

6.6 The JCAB Central Reporting Agency (CRA) presented information on one
of the possible methods of evaluating AIDC data and its sample findings.
JCAB CRA will continue this trial and provide further information in
this regard at future meetings. The meeting agreed that the information
should be discussed at an appropriate ICAO meeting to determine the
standardized analysis method of AIDC data and to set the criteria for
AIDC system performance.

*SITA Enhanced Ground to Air Satellite Voice Service*

6.7 SITA presented information on the Satellite AIRCOM voice service,
including recent enhancements to ground-to-air calling, to satisfy ATS
requirements.

6.8 HF voice communication is subject to interference, disruption and
delays due to its exposure to ionospheric conditions. Satellite voice
communication is considered reliable, easy to use, and of high quality
such that it may be an alternative to HF voice. Satellite air to ground
voice communications contribute to enhanced flight safety by providing
an alternate means of communications. Measures have been taken to ensure
the security of satellite voice communications.

6.9 At least one agency is evaluating the implementation of satellite
voice procedures, and has already proceeded with operational tests and
plans to present the results to the North Atlantic System Planning Group
in June 2004. SITA will follow the outcome of this meeting and provide
information to IPACG/22.

####### SATCOM Voice

6.10 JCAB intends to promulgate an aeronautical information publication
(AIP) (or aeronautical information circular (AIC)) on the use of SATCOM
voice for ATC with the commissioning of MTSAT. SATCOM voice could be
used for ATC communications, in principle, as an alternate means of
communication between the controller and the pilot with the following
guidelines:

-   When either CPDLC or HF voice is available, SATCOM voice should not
    be used for routine ATC communication;

-   If both HF voice and CPDLC are not available, SATCOM voice could be
    used for ATC communication; and

-   When an emergency or urgent call is received from the pilot or when
    ATC considers an aircraft is in an emergency or urgency, and if ATC
    considers that SATCOM voice is a more appropriate means of
    communication with the pilot, SATCOM voice could be used instead of
    CPDLC or HF voice.

6.11 United Airlines advised that the FAA had not certified SATCOM voice
as a long-range communications system. Work is ongoing to remove
restrictions to the use of SATCOM voice. Procedures need to be developed
so operators can talk to ATS providers if HF fails or if CPDLC is not
available.

6.12 Oakland ARTCC advised that their communications system provides
access to commercial phones at each control position, and that each
control position has an individual telephone number. It is believed that
these numbers can be used with SATCOM voice.

**7.0 Agenda Item 4: Report on the outcome of the FANS Interoperability
Team (FIT) Meeting**

7.1 The 8^th^ meeting of the IPACG FIT (FIT/8) was chaired by Mr.
Yoshiki Imawaka, JCAB FIT

Co-chair. Due to urgent commitments, Mr. Reed Sladen, FAA FIT Co-chair
was not able to attend, and Mr. Imawaka advised that regrets were
received from Mr. Sladen.

7.2 The following agenda was adopted by the IPACG FIT/8 meeting.

> Agenda Item 1: Review and approve agenda
>
> Agenda Item 2: FANS-1/A Operations Manual
>
> Agenda Item 3: Reports on the CRA and CRASA activities
>
> Agenda Item 4: Technical issues relating to use of MTSAT
>
> Agenda Item 5: Any Other Business

3.  The following working papers and information papers were presented
    to the FIT/8 meeting.

  ------------------------------------------------------------------------
  **Paper       **Agenda   **Title**                        **Presented
  Number**      Item**                                      by**
  ------------- ---------- -------------------------------- --------------
  WP/1          1          Proposed Agenda and Timetable    Chairpersons

  WP/2          2          FANS-1/A Operations Manual       Chairpersons

  WP/3          4          Status of MTSAT and its use      JCAB

  WP/4          5          Satellite Channel Data Format    Airbus

  WP/5                     Withdrawal                       

  WP/6          3          CRA Activities Since IPACG/20    IPACG FIT CRAs

  IP/1          3          Pattern of Factors Causing       JCAB CRA
                           Connection Failures              

  IP/2          5          A380 General Presentation        Airbus
  ------------------------------------------------------------------------

## *FANS-1/A Operations Manual*

7.4 Mr. Imawaka advised the meeting that 21 Request For Change forms
(RFCs) were presented to the ISPACG FIT/11 meeting held in February
2004, and of them, 19 RFCs were accepted. The RFCs accepted at the
ISPACG FIT/11 meeting included amendments developed following the ICAO
Guidance Material Review Task Force Meeting held in October 2003. The
ICAO Guidance Material Review Task Force Meeting had been held in order
to align the *ICAO Guidance Material on CNS/ATM Operations in the
Asia/Pacific Region* with the ICAO Standards and Recommended Practices
(SARPS) and PANS documents. The meeting was also advised that the
Pacific Operations Manual has been renamed the FANS-1/A Operations
Manual, a copy of which was distributed in March 2004 to the IPACG FIT
members by Mr. Reed Sladen, FANS-1/A Operations Manual Editor. The
meeting noted the amendments accepted at the ISPACG FIT/11 meeting as
well as the change of the title of the manual.

7.5 Concern was raised for the amendment process to the FANS-1/A
Operations Manual. The FANS-1/A Operations Manual has now been adopted
in many areas, namely South Pacific, NOPAC, CENPAC, Bay of Bengal, South
China Sea and Indian Oceans. Amendment to the FANS-1/A Operations Manual
may be made at each ATC coordinating group. Since ATC coordinating
groups for each area do not meet at the same time, it was not practical
for the whole group to discuss proposed amendments (RFCs). Further,
amendments accepted by an ATS coordinating group may not be accepted by
the other groups. The Co-chair advised the meeting that the amendments
accepted at the ISPACG FIT/11 were mainly developed following the ICAO
Guidance Material Review Task Force Meeting and considered not to affect
the operations. The procedures for amendments to the FANS-1/A Operations
Manual are detailed in its paragraph 1.4.

> "Whenever a user identifies a need for a change to this document, a
> Request for Change Form (RFC) (see Section 1.6 below) should be
> completed and submitted to the FOM Editor. The RFC may also be given
> to any or all of the IPACG, ISPACG, or IIOCG, or FITBOB chairs listed
> in Document Management above.
>
> When an RFC has been approved by all of the owners then a new version
> of the FOM will be published, with the changes marked by an "\|" in
> the margins, and an endnote indicating the relevant RFC, in case the
> reader wants to actually see the origin of the change. If the change
> is in a table cell, the outside edges of the table will be
> highlighted:

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

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

> In those few cases where a change is initiated by the editor and has
> to do with document format rather than functional content, the change
> may not have an associated RFC, but the change will be marked and
> annotated in the same way."

7.6 The Co-chair advised that there was no RFC submitted to the FANS-1A
Operations Manual Editor before the IPACG FIT/8 meeting.

7.7 The meeting then discussed similar documents regarding FANS-1/A data
link operations issued by other bodies. The ICAO Asia/Pacific Office has
published the *ICAO Guidance Material on CNS/ATM Operations in the
Asia/Pacific Region*, while the ICAO Europe office has issued three
documents, namely *Guidance Material for ATS Data Link Services in NAT
Airspace*, *Guidance Material for ATS Data Link Services in NAT
Airspace*, and *Guidance Material for FMC WPR Services in NAT Airspace*.
It was advised that ICAO would not be the position to publish an
operational manual, but would issue guidance material. The meeting noted
that the FANS-1/A Operations Manual contains information which would not
be appropriate to an ICAO guidance material but valuable and
indispensable for the FANS-1/A data link operation. The operators wished
to have a single document mutually applicable to all areas.

*Reports on the CRA and CRA Supporting Agency (CRASA) activities\
*

7.8 The FAA CRA and JCAB CRA jointly presented the report of CRA and
CRASA activities. It was advised that since the IPACG FIT/7 meeting in
October 2003, the FAA CRA, responsible for processing reports
originating in or relating occurrences in the Oakland and Anchorage
Oceanic FIRs, received 9 new problem reports (PRs) from operators. The
FAA CRA proposed closure of 5 PRs, which had all been closed by ISPACG
FIT/11 in February 2004. 4 PRs were due to release of a new avionics
software version. The IPACG FIT/8 agreed to close 5 PRs proposed by the
FAA CRA.

7.9 The JCAB CRA is responsible for processing PRs originating in or
relating to occurrences in the Tokyo FIR, and received 37 PRs since the
IPACG FIT/7 meeting. The JCAB CRA proposed 14 PRs to be closed. During
the review of the PRs to be closed, concern was raised for PR 10186
regarding different CPDLC messages displayed on two Control Display
Units (CDU) (left and right seats in cockpit). While Boeing has issued
an operations manual bulletin instructing flight crews to use the left
CDU when the different CPDLC messages were displayed on the left and
right CDUs, it was considered that a software change may be required to
resolve this problem. The meeting therefore did not close PR 10186 and
kept it open. The FAA CRA agreed to study this problem and report back
to the next FIT meeting.

7.10 Mr. Gordon Sandell, the FAA CRA discussed following specific
reports.

-   B747-400 FMC ignores uplinks for one function (PR 377)

-   B777 position report estimate incorrect after waypoint sequence (PR
    446)

-   KAKES black hole investigation (PR 447)

-   B777 flight number synchronization problem (PR 449)

-   Multiple reports from B777 (PR450)

-   Ground system used wrong format for B777 (PR 451)

-   Airplane transfers OK, but ATSU does not recognize transfer (PR 452)

-   Unusual free text with vertical clearance request (PR 454)

7.11 Mr. Sandell advised that problems should be reported to the CRAs,
and that problems will not be fixed if they are not reported. A problem
reporting mechanism was discussed at the JCAB FANS Data Link Seminar in
October 2002. Mr. Sandell also advised that a new software version, once
it was released, should be obtained from Boeing and installed into
airframes.

12. Mr. Hiroshi Fujita reported on the JCAB CRA activities since the
    IPACG FIT/7 meeting.

Mr. Fujita discussed the following PRs.

-   Unreasonable message sent from DSP (PR10191)

-   ADS report error (PR10193)

-   Data delay (PR10198, PR10201, PR10203, PR10207, PR10217)

-   Inappropriate logon and CPDLC position report (PR10205)

-   Abnormal display of flight path on ATC screen (PR10212, PR10215)

-   Illegible CPDLC freetext (PR10216)

-   Multiple reception of same CPDLC downlink messages (PR10222)

7.13 The Co-chair asked if specific problems, which are considered to
affect the application of distance-based separation minima using
ADS/CPDLC, have been received or identified. The meeting felt that there
were no such problems at this stage; however, the JCAB CRA agreed to
study this and report to the next meeting.

7.14 A list of the PRs closed at the IPACG FIT/8 meeting is in Appendix
B

## *Technical issues relating to use of MTSAT*

7.15 Mr. Imawaka advised the meeting that MTSAT-1R was delivered to the
Tanegashima Space Center in Japan in March 2004 and is waiting for the
launch, while MTSAT-2 is currently being manufactured by the Mitsubishi
Electric Co. and will be delivered by the end of 2004. Due to the
failure of the launch of the H2A rocket in November 2003, a launch
recovery plan for the H2A has not been announced. It was advised that
JCAB expects the MTSAT-1R launch in early 2005, and it will become
operational 7 to 9 months after the launch.

7.16 At the ISPACG/18 meeting, information on the status of MTSAT was
provided and stakeholders raised concerns regarding technical issues
relating to use of MTSAT. A JCAB coordinated message replying to the
queries had been forwarded to the ISPACG members through the ISPACG
Co-chair. The JCAB message was reproduced for the meeting and is in
Appendix C.

7.17 Mr. Shigehiko Yamaguchi, Office of Aeronautical Satellite Systems,
JCAB presented information on the MTSAT system and discussed the
following.

-   Handover between MTSAT and Inmarsats during flight

-   GES and satellite redundancy

-   SATCOM ORT Editor

-   Distribution of SATCOM message to each end-user

7.18 The meeting noted that JCAB does not intend to change, with the
commissioning of MTSAT, the current air navigation charge for
international flights operating within the Japanese FIRs; therefore, the
air navigation charge for aircraft connecting with MTSAT will be the
same as aircraft using HF voice and aircraft connecting with Inmarsat.

7.19 The meeting also noted that connection to MTSAT within the Japanese
FIRs will not be mandatory, and selection of satellite service will be
the decision of the operators. It was advised that JCAB is willing to
participate in airline meetings to provide them with information on
MTSAT.

## *Satellite Channel Data Format*

7.20 Mr. Jean-Francois Bousquie, Airbus presented information regarding
satellite channel data format. The recent CPDLC testing of FANS-A +
avionics, developed in accordance with RTCA DO-219 (ED100), in the North
Atlantic had revealed a mismatch between uplinked satellite phone
numbers and information displayed in the cockpit. Mr. Bousquie asked the
meeting if IPACG plans to use CPDLC messages which refer to satellite
channel coding. If so, Mr. Bousquie suggested a test for uplinking the
messages 117 and 120 be conducted. The meeting agreed that Tokyo ACC
would conduct a test for sending these messages to an Airbus test bed
from the Oceanic Data Processing (ODP) system, and that the outcome will
be reported at the next meeting.

## *Airbus presentation regarding A380*

7.21 Mr. Jean-Francois Bousquie presented information on the new A380.
The IPACG FIT/7 meeting had requested Airbus to make this presentation
on the A380. Mr. Bousquie highlighted that the A380 is not as large as
it is said, comparing it with the current B747. The size of A380 is
79.80 meters in length, less than 80 meters in width and 80 foot in
height. The "80 x 80 box" was a design requirement for minimizing
infrastructure impact. Some 10 airports in the world have indicated that
they would be capable of accommodating the A380. The inauguration flight
for the A380 will be conducted in early 2005 and it will come online in
mid 2006.

7.22 IFALPA stated that the A380 might reduce the operational efficiency
on the ground at certain airports where taxiway and runway
configurations would not accommodate the A380.

## *Possible factors causing data link connection failure*

7.23 The JCAB CRA presented an analysis of the causes of data link
connection failures. One month's data in January 2003 were analyzed.
During the period, 3405 flights performed AFN logon to Tokyo ODP system.
Of them, 2459 flights established connection at the first attempt, 875
flights established after the second attempt, and 71 flights were not
able to establish connection. The following table depicts the causes of
those 71 flights' failures:

  ------------------------------------------------------------- ---------
  Reception of DR1 (disconnect request) after CR1 (connection   45.1 %
  request) was uplinked                                         

  Related to FN_AK (Reason Code = 4)                            31.6 %

  MAF (message assurance failure) was received after CR1        17.3 %

  Time out after FN_AK or CR1                                   5.9 %
  ------------------------------------------------------------- ---------

7.24 The JCAB CRA advised that they would continue monitoring data link
connections and report to future meetings.

*ICAO Southeast Asia ATS Coordinating Group FANS Interoperability Team
(SEACG FIT)*

7.25 Mr. Keizo Udaka, JCAB advised the meeting that the 11^th^ meeting
of the ICAO South-East Asia ATS Coordination Group (SEACG/11) and the
1^st^ meeting of the SEACG FANS Implementation Team (FIT-SEA/1) were
held in Bangkok, Thailand on 24 - 28 May 2004, and discussed ATS related
issues and FANS-1/A data link operations over the South China Sea area.

7.26 It was advised that there were significant operational and safety
issues in the South China Sea area related to not using common operating
procedures, and that the SEACG/11 and FIT-SEA/1 meetings emphasized the
importance for States to review their operational procedures and revise
the procedures in line with the FANS-1/A Operations Manual.

7.27 Mr. Udaka advised that JCAB presented to the FIT-SEA/1 meeting
information detailing the roles and activities being undertaken by the
JCAB CRA for the Tokyo FIR oceanic controlled airspace, and offered to
undertake the role of CRA for the South China Sea area.

**8.0 Agenda Item 5: Review and update of CNS/ATM Planning Chart**

8.1 The CNS/ATM Planning Chart was presented and updated and is at
Appendix D.

**9.0 Agenda Item 6: Evaluation of Costs and Benefits**

9.1 The FAA presented an update of the status of the North Pacific
Airspace Cost Effectiveness (NPACE) study. The first NPACE Study
Advisory Group (NSAG) meeting was held in January 2004. This smaller
advisory group was formed to provide technical and operational guidance
to the NPACE Study team. At that meeting, three specific simulation
scenarios were established for the NPACE study. Additional information
was provided by the NSAG regarding air traffic control procedures to be
incorporated into the simulation model. A summary of the modifications
made to the flight events program was provided.

9.2 The first simulation scenario would involve the current airspace
traffic volume and separation standards with the additional objective of
assessing effectiveness of the track advisory algorithm. The second and
third simulation scenarios would involve forecasted airspace traffic
volume for years 2005 and 2010 and RNP10 separation standards for
various proportions of ADS equipped aircraft.

9.3 The initial testing and validation of the programs indicated that
Scenarios I through III will be fully investigated. The flight tracking
program will be updated to include an in-flight conflict resolution
algorithm. This part of the program will ensure that the longitudinal
separation standards are maintained for all flights during their entire
travel over the NOPAC and PACOTS tracks. It will also ensure the
standards are upheld when step climb requests and track crossings occur.
In addition, a procedure will be incorporated to apply the appropriate
separation standards.

9.4 Once the flight tracking program is complete, Scenario I will be
examined more completely and Scenarios II and III will be thoroughly
investigated. Results will be presented at future IPACG meetings.

**10.0 Agenda Item 7: Other Business**

####### Airspace Safety Monitoring in the Pacific Region

10.1 The FAA reported on the first meeting of the Regional Airspace
Monitoring Advisory Group (RASMAG/1) held in Bangkok from 26-30 April
2004. The report of RASMAG/1 related to the IPACG and associated FIT and
CRA and requested that these meetings provide reports of their
activities to RASMAG for review.

10.2 JCAB suggested that reports should be from CRA or FIT, not both.
FAA noted there is a difference between how IPACG and ISPACG FITs
operate, and agreed that the CRA should report to RASMAG.

####### Status of ATFM Communication Methods between FAA, ATCSCC, and JCAB ATFMC

10.3 The FAA presented the status of Air Traffic Flow Management (ATFM)
communication methods between the FAA Air Traffic Control System Command
Center (ATCSCC) and the JCAB ATFMC.

10.4 The FAA ATCSCC and the JCAB ATFMC are in the process of finalizing
a Letter of Agreement outlining hotline communication procedures. The
FAA ATCSCC recommended the following future topics for exploration:

-   Terminology and Phraseology - Development of the common terms of
    reference for definitive, clear, and concise communication between
    FAA ATCSCC and JCAB ATFMC:

```{=html}
<!-- -->
```
-   Contingency Plan Development -- In the event of a major catastrophe
    such as a natural disaster or terrorist attack, we support ICAO's
    recommendation for the development of contingency plans to
    accommodate the malfunctioning of ATC facilities.

-   Internet Technology -- Over the past 5 years, developments in
    Internet technology have begun to make available the use of that
    medium for the exchange of data through the use of secure
    communications. We recommend discussions between the JCAB and FAA to
    evaluate the feasibility and capability of utilizing this medium for
    communication between the states at some future date.

-   Traffic Flow Management Tools -- Traffic Flow Management
    Modernization (TFM-M) is the FAA multi-year plan to replace portions
    of the existing TFM automation systems with a modernized automation
    environment that supports both legacy and new functional
    capabilities. We recommend continued discussion between JCAB and
    FAA, as traffic flow management tools are enhanced and developed, to
    facilitate the exchange of ideas and data to solve flow management
    problems in both states.

10.5 FAA and JCAB continue to review the draft MOU which will enable and
promote the cooperation between FAA ATCSCC and JCAB ATFMC to exchange
air traffic flow management information between the United States and
Japan.

10.6 JCAB indicated full support of the activities recommended by the
FAA and agreed that participation in future meetings by ATFMC and ATCSCC
technical experts is essential.

10.7 Mr. Ono reported that JCAB is developing a data exchange system for
ATFM information and has requested that this be included in the budget.
Further information will be provided to the next meeting.

####### Update of Action Items

10.8 The meeting updated the action item list which is at Appendix E.

*Closing*

9.  FAA will host IPACG/22 during the week of 24-28 January 2005, at the
    Portofino Hotel,

Los Angeles, California. The FIT will meet during the first 2 days in
advance of IPACG/22. FAA will provide further details prior to the
meeting.

10.10 The Co-chairs expressed their appreciation for the support of all
participants during the meeting. Several items were noted in closing,
particularly the importance of contingency procedures for the future,
the success in finalizing the MOU on hotline communications between the
ATFMC and ATCSCC, and the planned implementation of ADS control
procedures in 2005.

10.11 The meeting was closed by the Co-chairs.

*/s/ Akira Ono /s/ Leslie S. McCormick*

\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_
\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_

Akira Ono Leslie S. McCormick

Co-chair for JCAB Co-chair for FAA

Attachments:

Appendix A -- Meeting Attendees

Appendix B -- List of Problem Reports Closed

Appendix C -- JCAB Response to ISPACG FIT

Appendix D -- CNS/ATM Planning Chart

Appendix E -- Open Action Items

+---------+------------+-----------+----------------+-----------------+
| Name    | ## **      | #         | ## **Mai       | ## **Ph         |
|         | Position** | # **Organ | ling Address** | one/Fax/Email** |
|         |            | ization** |                |                 |
+---------+------------+-----------+----------------+-----------------+
| Anton,  | Senior     | ARINC     | 2551 Riva Road | Ph:             |
| Terri   | Director   |           |                | +1-410-266-4027 |
|         |            |           | Annapolis, MD  |                 |
|         |            |           | 21401-7465 USA | Fax:            |
|         |            |           |                | +1-410-573-3026 |
|         |            |           |                |                 |
|         |            |           |                | Email:          |
|         |            |           |                | txa@arinc.com   |
+---------+------------+-----------+----------------+-----------------+
| Arima,  | Special    | FAA\`     | U.S.           | Ph:             |
| Takashi | Assistant  |           | Embassy/Tokyo  | +81-3-3224-5515 |
|         | to the     |           |                |                 |
|         | Senior FAA |           | 1-10-5         | Fax:            |
|         | Rep        |           | Akasaka,       | +81-3-3582-5974 |
|         |            |           | minato-ku      |                 |
|         |            |           |                | Email:          |
|         |            |           | Tokyo, Japan   | larr            |
|         |            |           | 107-8420       | y.arima@faa.gov |
+---------+------------+-----------+----------------+-----------------+
| B       | System     | CMC       | 600 Dr.        | Ph:             |
| oucher, | Engineer   | Ele       | Fr             | +1-514-748-3000 |
| Martin  |            | ctronics, | edrik-Philipps | x4134           |
|         |            | Inc       |                |                 |
|         |            |           | St-Laurent,    | Fax:            |
|         |            |           | Quebec, H8R3S4 | +1-514-748-3136 |
|         |            |           | Canada         |                 |
|         |            |           |                | Email:          |
|         |            |           |                | ma              |
|         |            |           |                | rtin.boucher@cm |
|         |            |           |                | celectronics.ca |
+---------+------------+-----------+----------------+-----------------+
| Bo      | Flight     | AIRBUS    | 1, Rond Point  | Ph:             |
| usquie, | Test       |           | Maurice        | +33-561-93-9704 |
| Jean-F  | Engineer   |           | Bellonte       |                 |
| rancois |            |           |                | Fax:            |
|         |            |           | 31707 Blagnac  | +33-561-93-2934 |
|         |            |           | Cedex France   |                 |
|         |            |           |                | Email:          |
|         |            |           |                | jea             |
|         |            |           |                | n-francois.bous |
|         |            |           |                | quie@airbus.com |
+---------+------------+-----------+----------------+-----------------+
| C       | Manager,   | United    | P.O. Box 576   | Ph:             |
| ameron, | Global     | Airlines  |                | +1-530-878-8791 |
| Gene    | Support -- |           | Applegate, CA  |                 |
|         | Flight     |           | 95703 USA      | Fax:            |
|         | Dispatch   |           |                | 1-530-878-8791  |
|         |            |           |                |                 |
|         |            |           |                | Email:          |
|         |            |           |                | Gene.           |
|         |            |           |                | cameron@ual.com |
+---------+------------+-----------+----------------+-----------------+
| Dale,   | Manager,   | Co        | 1600 Smith     | Ph:             |
| Greg    | Int        | ntinental | St-HQSSC       | +1-713-324-5095 |
|         | ernational | Airlines  |                |                 |
|         | Operations |           | Houston, TX    | Fax:            |
|         | Planning   |           | 77002 USA      | +1-713-324-2138 |
|         |            |           |                |                 |
|         |            |           |                | Email:          |
|         |            |           |                | gdale@coair.com |
+---------+------------+-----------+----------------+-----------------+
| Dell,   | Manager of | Cathay    | CPA,           | Ph:             |
| Owen    | Int        | Pacific   | International  | +852-2747-8829  |
|         | ernational | Airways   | Affairs &      |                 |
|         | Operations | ltd       | Alliance       | Fax:            |
|         |            |           | Dept., 91F     | +852-2141-8822  |
|         |            |           | Central Tower, |                 |
|         |            |           | Cathay City,   | Email:          |
|         |            |           | Lantan, Hong   | owen_dell@ca    |
|         |            |           | Kong           | thaypacific.com |
+---------+------------+-----------+----------------+-----------------+
| F       | Operations | Boeing    | P.O. Box 3707  | Ph:             |
| ischer, | Concept    | Phantom   |                | +1-425-373-2683 |
| William | Analyst    | Works     | M/S 02-98      |                 |
|         |            |           |                | Fax:            |
|         |            |           | Seattle, WA    | +1-425-373-2623 |
|         |            |           | 98124 USA      |                 |
|         |            |           |                | Email:          |
|         |            |           |                | William.m.fis   |
|         |            |           |                | cher@boeing.com |
+---------+------------+-----------+----------------+-----------------+
| Fujii,  | Director,  | Japan     | 300            | Ph:             |
| Frank   | Flight     | Airlines  | Continental    | +1-310-606-6557 |
|         | Operations |           | Boulevard      |                 |
|         | -- The     |           |                | Fax:            |
|         | Americas   |           | Suite 620      | +1-310-606-6550 |
|         |            |           |                |                 |
|         |            |           | El Segundo, CA | Email:          |
|         |            |           | 90245 USA      | fran            |
|         |            |           |                | k.fujii@jal.com |
+---------+------------+-----------+----------------+-----------------+
| Fu      | Special    | JCAB      | 2-1-3          | Ph:             |
| jimoto, | Assistant  |           | Kasumigaseki,  | +81-3-5253-8111 |
| Hi      | to the     |           | Chiyodaku      | x51247          |
| roshige | Director,  |           |                |                 |
|         | ATMC       |           | Tokyo,         | Fax:            |
|         | Project    |           | 100-8918,      | +81-3-5253-1663 |
|         |            |           | Japan          |                 |
|         |            |           |                | Email:          |
|         |            |           |                | fujimoto-       |
|         |            |           |                | h2k8@mlit.go.jp |
+---------+------------+-----------+----------------+-----------------+
| Fujita, | ATCA       | ATCA --   | K-1 Building,  | Ph:             |
| Hiroshi | Associate  | Japan     | 1-6-6 Haneda   | +81-3-3747-1231 |
|         | CNS/ATM    |           | Airport,       |                 |
|         | Specialist |           | Ota-ku         | Fax:            |
|         |            |           |                | +81-3-3747-1231 |
|         |            |           | Tokyo,         |                 |
|         |            |           | 144-0041 Japan | Email:          |
|         |            |           |                | cras            |
|         |            |           |                | a@cra-japan.org |
+---------+------------+-----------+----------------+-----------------+
| F       | Air        | IFA       | Oakland ARTCC  | Ph:             |
| ullmer, | Traffic    | TCA/NATCA |                | +1-510-745-3342 |
| Ian     | Controller |           | 5125 Central   |                 |
|         |            |           | Avenue         | Fax:            |
|         |            |           |                | +1-510-745-3411 |
|         |            |           | Fremont, CA    |                 |
|         |            |           | 94536 USA      | Email:          |
|         |            |           |                | ian.fullm       |
|         |            |           |                | er@zoanatca.com |
+---------+------------+-----------+----------------+-----------------+
| H       | Oceanic    | FAA       | 800            | Ph:             |
| ancock, | Procedures |           | Independence   | +1-202-267-7698 |
| Gary    | Specialist |           | Ave SW         |                 |
|         |            |           |                | Fax:            |
|         |            |           | Washington DC  | +1-202-267-5110 |
|         |            |           | 20591 USA      |                 |
|         |            |           |                | Email:          |
|         |            |           |                | gary.           |
|         |            |           |                | hancock@faa.gov |
+---------+------------+-----------+----------------+-----------------+
| Hata    | ATCA       | ATCA --   | K-1 Building,  | Ph:             |
| kenaka, | Associate  | Japan     | 1-6-6 Haneda   | +81-3-3747-1231 |
| Masami  | CNS/ATM    |           | Airport,       |                 |
|         | Specialist |           | Ota-ku         | Fax:            |
|         |            |           |                | +81-3-3747-1231 |
|         |            |           | Tokyo,         |                 |
|         |            |           | 144-0041 Japan | Email:          |
|         |            |           |                | cras            |
|         |            |           |                | a@cra-japan.org |
+---------+------------+-----------+----------------+-----------------+
| Name    | ## **      | #         | ## **Mai       | ## **Ph         |
|         | Position** | # **Organ | ling Address** | one/Fax/Email** |
|         |            | ization** |                |                 |
+---------+------------+-----------+----------------+-----------------+
| Hirata, | Senior     | Nippon    | Narita         | Ph:             |
| To      | Manager,   | Cargo     | International  | +81-476-34-7724 |
| shiyuki | Flight     | Airlines  | Airport        |                 |
|         | Operations |           |                | Fax:            |
|         |            |           | Narita         | +81-476-34-7771 |
|         |            |           | 282-8691 Japan |                 |
|         |            |           |                | Email:          |
|         |            |           |                | toshiyuki.      |
|         |            |           |                | hirata@nca.aero |
+---------+------------+-----------+----------------+-----------------+
| I       | Special    | JCAB      | 2-1-3          | Ph:             |
| mawaka, | Assistant  |           | Kasumigaseki,  | +1              |
| Yoshiki | to the     |           | Chiyodaku      | -81-3-5253-8111 |
|         | Director,  |           |                | x51152          |
|         | Office of  |           | Tokyo,         |                 |
|         | Ae         |           | 100-8918,      | Fax:            |
|         | ronautical |           | Japan          | +1              |
|         | Satellite  |           |                | -81-3-5253-1663 |
|         | Systems    |           |                |                 |
|         |            |           |                | Email:          |
|         |            |           |                | imawaka-        |
|         |            |           |                | y2ys@mlit.go.jp |
+---------+------------+-----------+----------------+-----------------+
| In      | Special    | JCAB      | 2-1-3          | Ph:             |
| amitsu, | Assistant  |           | Kasumigaseki,  | +1              |
| Hiroshi | to         |           | Chiyodaku      | -81-3-5253-8111 |
|         | Director,  |           |                | x51236          |
|         | Flight     |           | Tokyo,         |                 |
|         | Procedure  |           | 100-8918,      | Fax:            |
|         | and        |           | Japan          | +1              |
|         | Airspace   |           |                | -81-3-5253-1663 |
|         | Program    |           |                |                 |
|         | Office     |           |                | Email:          |
|         |            |           |                | Inamitsu-       |
|         |            |           |                | h2db@mlit.go.jp |
+---------+------------+-----------+----------------+-----------------+
| Is      | Chief,     | JCAB      | 2-1-3          | Ph:             |
| hikawa, | Flight     |           | Kasumigaseki,  | +1              |
| Makoto  | Procedure  |           | Chiyodaku      | -81-3-5253-8111 |
|         | and        |           |                | x51235          |
|         | Airspace   |           | Tokyo,         |                 |
|         | Program    |           | 100-8918,      | Fax:            |
|         | Office     |           | Japan          | +1              |
|         |            |           |                | -81-3-5253-1663 |
|         |            |           |                |                 |
|         |            |           |                | Email:          |
|         |            |           |                | ishikawa-       |
|         |            |           |                | m2af@mlit.go.jp |
+---------+------------+-----------+----------------+-----------------+
| Jo      | Assistant  | IATA      | 77 Robinson    | Ph:             |
| nasson, | Director,  |           | Road           | +65-6239-7262   |
| Neil    | Safety     |           |                |                 |
|         | Operations |           | #05-00 SIA     | Fax:            |
|         | &          |           | Building       | +65-6536-6267   |
|         | Infr       |           |                |                 |
|         | astructure |           | Singapore      | Email:          |
|         | --         |           | 068896         | jon             |
|         | As         |           |                | assonn@iata.org |
|         | ia/Pacific |           |                |                 |
+---------+------------+-----------+----------------+-----------------+
| Kato,   | IFATCA     | IFATCA    | 3-4-12         | Ph:             |
| Koji    | Repr       |           | Fujimi-cho,    | +               |
|         | esentative |           |                | 81-80-5496-3538 |
|         |            |           | Higash         |                 |
|         |            |           | imurayama-shi, | Fax:            |
|         |            |           | Tokyo,         | +81-42-396-7506 |
|         |            |           | 189-0024,      |                 |
|         |            |           | Japan          | Email:          |
|         |            |           |                | koji            |
|         |            |           |                | 358@naver.co.jp |
+---------+------------+-----------+----------------+-----------------+
| Kearns, | Manager,   | SITA      | PMB 210        | Ph:             |
| K       | AIRCOM     |           |                | +1-703-339-8965 |
| athleen | Service    |           | 8094 Rolling   |                 |
|         | De         |           | Road           | Fax:            |
|         | velopment, |           |                | +1-703-339-8966 |
|         | North      |           | Springfield,   |                 |
|         | America    |           | VA 22153 USA   | Email:          |
|         |            |           |                | Kathleen.k      |
|         |            |           |                | earns@sita.aero |
+---------+------------+-----------+----------------+-----------------+
| Kimura, | Special    | JCAB      | 2-1-3          | Ph:             |
| Akira   | Assistant  |           | Kasumigaseki,  | +1              |
|         | to         |           | Chiyodaku      | -81-3-5253-8111 |
|         | Director,  |           |                | x51247          |
|         | ATMC       |           | Tokyo,         |                 |
|         | Project    |           | 100-8918,      | Fax:            |
|         |            |           | Japan          | +1              |
|         |            |           |                | -81-3-5253-1663 |
|         |            |           |                |                 |
|         |            |           |                | Email:          |
|         |            |           |                | kimura-         |
|         |            |           |                | a225@mlit.go.jp |
+---------+------------+-----------+----------------+-----------------+
| Kob     | Senior     | All       | 3-3-2, Haneda  | Ph:             |
| ayashi, | Manager,   | Nippon    | Airport Ota-ku | +81-3-5757-5311 |
| Ma      | Flight     | Airways   |                |                 |
| satoshi | Standards  |           | Tokyo,         | Fax:            |
|         |            |           | 144-0041,      | +81-3-5757-5404 |
|         |            |           | Japan          |                 |
|         |            |           |                | Email:          |
|         |            |           |                | masat.koba      |
|         |            |           |                | yashi@ana.co.jp |
+---------+------------+-----------+----------------+-----------------+
| Ko      | Staff      | Japan     | West Passenger | Ph:             |
| metani, | Director,  | Airlines  | Terminal 3-3-2 | +81-3-5756-3139 |
| Shinji  | Avionics   |           |                |                 |
|         | Section    |           | Haneda Airport | Fax:            |
|         |            |           | Ota-ku,        | +81-3-5756-3529 |
|         |            |           |                |                 |
|         |            |           | Tokyo 144-0041 | Email:          |
|         |            |           | Japan          | shinji.k        |
|         |            |           |                | ometani@jal.com |
+---------+------------+-----------+----------------+-----------------+
| Koshi,  | Assistant  | All       | 3-3-2, Haneda  | Ph:             |
| Makoto  | Manager    | Nippon    | Airport Ota-ku | +81-3-5757-5374 |
|         |            | Airwa     |                |                 |
|         |            | ys/Flight | Tokyo,         | Fax:            |
|         |            | Oper      | 144-0041,      | +81-3-5757-5406 |
|         |            | ations-En | Japan          |                 |
|         |            | gineering |                | Email:          |
|         |            |           |                | m.              |
|         |            |           |                | koshi@ana.co.jp |
+---------+------------+-----------+----------------+-----------------+
| Kosugi, | Air        | ATFMC,    | 1302-17        | Ph:             |
| Shoichi | Traffic    | JCAB      | Kosenumi,      | +81-92-608-6115 |
|         | Flow       |           | Nata,          |                 |
|         | Management |           | Higashi-ku     | Fax:            |
|         | Officer    |           |                | +81-92-608-6130 |
|         |            |           | Fukuoka-shi,   |                 |
|         |            |           | Fukuoka, Pre   | Email:          |
|         |            |           |                | kosugi-s07vf@   |
|         |            |           | 811-0204,      | atfm.mlit.go.jp |
|         |            |           | Japan          |                 |
+---------+------------+-----------+----------------+-----------------+
| Ku      | Air        | JCAB      | 2-1-3          | Ph:             |
| nitake, | Traffic    |           | Kasumigaseki,  | +1              |
| Shigeru | Controller |           | Chiyodaku      | -81-3-5253-8111 |
|         |            |           |                | x51228          |
|         |            |           | Tokyo,         |                 |
|         |            |           | 100-8918,      | Fax:            |
|         |            |           | Japan          | +1              |
|         |            |           |                | -81-3-5253-1663 |
|         |            |           |                |                 |
|         |            |           |                | Email:          |
|         |            |           |                | kunitake-       |
|         |            |           |                | s2kj@mlit.go.jp |
+---------+------------+-----------+----------------+-----------------+
| Lavi    | Customer   | SITA      | 770 Sherbrooke | Ph:             |
| olette, | Support    |           | St. W.         | +1-514-982-3524 |
| Sylvain | Account    |           |                |                 |
|         | Manager    |           | Suite 2400     | Fax:            |
|         |            |           |                | +1-514-982-3597 |
|         |            |           | Montreal,      |                 |
|         |            |           | Quebec, H3A    | Email:          |
|         |            |           | 1G1 Canada     | sylvain.lavio   |
|         |            |           |                | lette@sita.aero |
+---------+------------+-----------+----------------+-----------------+
| Name    | ## **      | #         | ## **Mai       | ## **Ph         |
|         | Position** | # **Organ | ling Address** | one/Fax/Email** |
|         |            | ization** |                |                 |
+---------+------------+-----------+----------------+-----------------+
| Maeda,  | Manager    | Nippon    | Narita         | Ph:             |
| Masato  |            | Cargo     | International  | +81-476-34-7731 |
|         |            | Airlines  | Airport        |                 |
|         |            |           |                | Fax:            |
|         |            |           | Narita         | +               |
|         |            |           | 282-8691 Japan | 81-510-745-3443 |
|         |            |           |                |                 |
|         |            |           |                | Email:          |
|         |            |           |                | masato          |
|         |            |           |                | .maeda@nca.aero |
+---------+------------+-----------+----------------+-----------------+
| Mar     | Manager,   | Air       | Air Canada     | Ph:             |
| cinkow, | Airspace   | Canada    | Centre 1019    | +1-514-422-4655 |
| Robert  | --         |           |                |                 |
|         | As         |           | P.O. Box 9000  | Fax:            |
|         | ia/Pacific |           | Station        | +1-514-422-6896 |
|         |            |           | Airport        |                 |
|         |            |           |                | Email:          |
|         |            |           | Dorval,        | Robert.marcink  |
|         |            |           | Quebec, Canada | ow@aircanada.ca |
|         |            |           | H4Y 1C2        |                 |
+---------+------------+-----------+----------------+-----------------+
| McC     | Senior     | FAA/ Air  | 800            | Ph:             |
| ormick, | Int        | Traffic   | Independence   | +1-202-385-8082 |
| Leslie  | ernational | O         | Ave SW         |                 |
|         | Program    | perations |                | Fax:            |
|         | Officer    | Planning  | Washington DC  | +1-208-246-6014 |
|         |            | Inte      | 20591 USA      |                 |
|         | FAA        | rnational |                | Email:          |
|         | Co-chair   |           |                | leslie.mc       |
|         |            |           |                | cormick@faa.gov |
+---------+------------+-----------+----------------+-----------------+
| Metts,  | Senior FAA | FAA       | U.S.           | Ph:             |
| Chri    | Repr       |           | Embassy/Tokyo  | +81-3-3224-5511 |
| stopher | esentative |           |                |                 |
|         |            |           | 1-10-5         | Fax:            |
|         |            |           | Akasaka,       | +81-3-3582-5974 |
|         |            |           | minato-ku      |                 |
|         |            |           |                | Email:          |
|         |            |           | Tokyo, Japan   | chri            |
|         |            |           | 107-8420       | s.metts@faa.gov |
+---------+------------+-----------+----------------+-----------------+
| Miller, | Director,  | CSSI,     | 400 Virginia   | Ph:             |
| Robert  | Airspace   | Inc.      | Avenue, SW     | +1-202-484-3359 |
|         | Analysis   |           |                |                 |
|         | and        |           | Suite 210      | Fax:            |
|         | Modeling   |           |                | +1-202-863-2398 |
|         |            |           | Washington, DC |                 |
|         |            |           | 20024 USA      | Email:          |
|         |            |           |                | rmil            |
|         |            |           |                | ler@cssiinc.com |
+---------+------------+-----------+----------------+-----------------+
| Mi      | Chief of   | KSS       | 1-4-28, Mita,  | Ph:             |
| namiru, | Technical  |           | Minato-ku,     | +81-3-3452-6830 |
| Osamu   | Fellow     |           | Tokyo, 108-073 |                 |
|         |            |           | Japan          | Fax:            |
|         |            |           |                | +81-3-3452-5629 |
|         |            |           |                |                 |
|         |            |           |                | Email:          |
|         |            |           |                | o.minam         |
|         |            |           |                | iru@atcss.co.jp |
+---------+------------+-----------+----------------+-----------------+
| Momii,  | Air        | Tokyo     | 1-12 Namiki,   | Ph:             |
| Yasuko  | Traffic    | ACC, JCAB | Tokorozawa     | +81-42-992-1181 |
|         | Controller |           | City, Saitama  |                 |
|         |            |           | Prefecture,    | Fax:            |
|         |            |           | 359-0042 Japan | +81-42-992-1195 |
|         |            |           |                |                 |
|         |            |           |                | Email:          |
|         |            |           |                |                 |
|         |            |           |                | momii-y03h9@    |
|         |            |           |                | tacc.mlit.go.jp |
+---------+------------+-----------+----------------+-----------------+
| Nakano, | Chief,     | JCAB      | 2-1-3          | Ph:             |
| H       | Operations |           | Kasumigaseki,  | +81-3-5253-8111 |
| iroyuki | Section,   |           | Chiyodaku      | x51219          |
|         | ATC        |           |                |                 |
|         | Division   |           | Tokyo,         | Fax:            |
|         |            |           | 100-8918,      | +81-3-5253-1663 |
|         |            |           | Japan          |                 |
|         |            |           |                | Email:          |
|         |            |           |                | nakano-         |
|         |            |           |                | h2rn@mlit.go.jp |
+---------+------------+-----------+----------------+-----------------+
| Nak     | Manager    | Japan     | West Passenger | Ph:             |
| ashima, |            | Airlines  | Terminal 3-3-2 | +81-3-5756-3134 |
| Tatsuo  |            |           |                |                 |
|         |            |           | Haneda Airport | Fax:            |
|         |            |           | Ota-ku,        | +81-3-5756-3527 |
|         |            |           |                |                 |
|         |            |           | Tokyo 144-0041 | Email:          |
|         |            |           | Japan          | tatsuo.na       |
|         |            |           |                | kashima@jal.com |
+---------+------------+-----------+----------------+-----------------+
| Nakata, | Manager    | Northwest | 650-35 Nanae,  | Ph:             |
| Kazuo   | Flight     | Airlines  | Tomisato,      | +81-476-91-3923 |
|         | Dispatch   |           | Chiba,         |                 |
|         | Pacific    |           | 286-0221 Japan | Fax:            |
|         | Division   |           |                | +81-476-91-3904 |
|         |            |           |                |                 |
|         |            |           |                | Email:          |
|         |            |           |                | kazuo           |
|         |            |           |                | .nakata@nwa.com |
+---------+------------+-----------+----------------+-----------------+
| Nak     | Manager    | ATCA --   | K-1 Building,  | Ph:             |
| atsuji, |            | Japan     | 1-6-6 Haneda   | +81-3-3747-1234 |
| Yoshiro |            |           | Airport,       |                 |
|         |            |           | Ota-ku, Tokyo, | Fax:            |
|         |            |           |                | +81-3-3747-1231 |
|         |            |           | 144-0041 Japan |                 |
|         |            |           |                | Email:          |
|         |            |           |                | cras            |
|         |            |           |                | a@cra-japan.org |
+---------+------------+-----------+----------------+-----------------+
| Oh,     | Deputy     | Singapore | SIA Training   | Ph:             |
| Aric    | Chief      | Airlines  | Centre, 720    | +65-6540-3694   |
|         | Pilot      |           | Changi Road    |                 |
|         | Technical  |           | East,          | Fax:            |
|         |            |           | Singapore      | +65-6542-9564   |
|         |            |           |                |                 |
|         |            |           |                | Email:          |
|         |            |           |                | aric_oh@s       |
|         |            |           |                | ingaporeair.com |
+---------+------------+-----------+----------------+-----------------+
| Ono,    | Special    | JCAB      | 2-1-3          | Ph:             |
| Akira   | Assistant  |           | Kasumigaseki,  | +1              |
|         | to the     |           | Chiyodaku      | -81-3-5253-8111 |
|         | Director,  |           |                | x51226          |
|         | ATC Div.   |           | Tokyo,         |                 |
|         |            |           | 100-8918,      | Fax:            |
|         | IPACG      |           | Japan          | +1              |
|         | Co-chair   |           |                | -81-3-5253-1663 |
|         |            |           |                |                 |
|         |            |           |                | Email:          |
|         |            |           |                | ono-            |
|         |            |           |                | a25d@mlit.go.jp |
+---------+------------+-----------+----------------+-----------------+
| Ryan,   | Int        | FAA/ Air  | 800            | Ph:             |
| Carolyn | ernational | Traffic   | Independence   | +1-202-385-8084 |
|         | Program    | O         | Ave SW         |                 |
|         | Officer    | perations |                | Fax:            |
|         |            | Planning  | Washington DC  | +1-202-267-5120 |
|         |            | Inte      | 20591 USA      |                 |
|         |            | rnational |                | Email:          |
|         |            |           |                | Car             |
|         |            |           |                | ol.Ryan@faa.gov |
+---------+------------+-----------+----------------+-----------------+
| Saji,   | Senior     | SITA      | Shiba 1-chome  | Ph:             |
| Yasuo   | C          |           | Building, 8FL, | +81-3-3456-8188 |
|         | onsultant, |           | 1-12-7 Shiba,  |                 |
|         | Japan      |           | Minato-ku,     | Fax:            |
|         |            |           | Tokyo          | +81-3-3456-8190 |
|         |            |           | 105-0014,      |                 |
|         |            |           | Japan          | Email:          |
|         |            |           |                | yasuo           |
|         |            |           |                | .saji@sita.aero |
+---------+------------+-----------+----------------+-----------------+
| *       | ## **      | #         | ## **Mai       | ## **Ph         |
| *Name** | Position** | # **Organ | ling Address** | one/Fax/Email** |
|         |            | ization** |                |                 |
+---------+------------+-----------+----------------+-----------------+
| S       | Associate  | Boeing    | P.O. Box 3707, | Ph:             |
| andell, | Technical  | C         | M/S 02-98      | +1-425-294-0349 |
| Gordon  | Fellow     | ommercial |                |                 |
|         |            |           | Seattle, WA    | Email:          |
|         |            |           | 98124 USA      | Gordon.r.san    |
|         |            |           |                | dell@boeing.com |
+---------+------------+-----------+----------------+-----------------+
| Sayler, | HQ PACAF   | USAF      | 25 E Street    | Ph:             |
| Kenneth | Command    |           |                | +1-808-449-4889 |
|         | Airspace   |           | Suite I-232    |                 |
|         | Manager    |           |                | Fax:            |
|         |            |           | Hickam AFB, HI | +1-808-449-4013 |
|         |            |           | 96853-5426 USA |                 |
|         |            |           |                | Email:          |
|         |            |           |                | Ken.sayle       |
|         |            |           |                | r@hickam.af.mil |
+---------+------------+-----------+----------------+-----------------+
| Shindo, | Deputy     | ATCA --   | K-1 Building,  | Ph:             |
| Tatsumi | Manager    | Japan     | 1-6-6 Haneda   | +81-3-3747-1685 |
|         | Planning   |           | Airport,       |                 |
|         |            |           | Ota-ku, Tokyo, | Fax:            |
|         |            |           |                | +81-3-3747-0856 |
|         |            |           | 144-0041 Japan |                 |
|         |            |           |                | Email:          |
|         |            |           |                | shi             |
|         |            |           |                | ndo@atcaj.or.jp |
+---------+------------+-----------+----------------+-----------------+
| Storm,  | Civi       | USAF      | 1535 Command   | Ph:             |
| Allan   | l/Military | Flight    | Drive          | +1-240-857-2146 |
|         | Aviation   | Standards |                |                 |
|         | Issues     | Agency    | Suite D/E      | Fax:            |
|         |            |           |                | +1-240-857-3194 |
|         |            |           | Andrews Air    |                 |
|         |            |           | Force Base, MD | Email:          |
|         |            |           | 20762 USA      | Allan.storm     |
|         |            |           |                | @andrews.af.mil |
+---------+------------+-----------+----------------+-----------------+
| Suzuki, | ATCA       | ATCA --   | K-1 Building,  | Ph:             |
| Hiromi  | Associate  | Japan     | 1-6-6 Haneda   | +81-3-3747-1231 |
|         | CNS/ATM    |           | Airport,       |                 |
|         | Specialist |           | Ota-ku,        | Fax:            |
|         |            |           |                | +81-3-3747-1231 |
|         |            |           | Tokyo,         |                 |
|         |            |           | 144-0041 Japan | Email:          |
|         |            |           |                | cras            |
|         |            |           |                | a@cra-japan.org |
+---------+------------+-----------+----------------+-----------------+
| Suzuki, | Special    | JCAB      | 2-1-3          | Ph:             |
| Yo      | Assistant  |           | Kasumigaseki   | +81-3-5253-8111 |
| shinori | Director,  |           | Chiyoda-ku     | x51245          |
|         | ATMC       |           |                |                 |
|         | Project    |           | Tokyo,         | Fax:            |
|         |            |           | 100-8918,      | +81-3-5253-1663 |
|         |            |           | Japan          |                 |
|         |            |           |                | Email:          |
|         |            |           |                | syzyki-         |
|         |            |           |                | n2dr@mlit.go.jp |
+---------+------------+-----------+----------------+-----------------+
| Taylor, | Manager,   | Northwest | 7200 34^th^    | Ph:             |
| Curtis  | ATC        | Airlines  | Avenue South   | +1-612-727-7775 |
|         | Operations |           |                |                 |
|         |            |           | Department     | Fax:            |
|         |            |           | F7010          | +1-612-726-0916 |
|         |            |           |                |                 |
|         |            |           | Minneapolis,   | Email:          |
|         |            |           | MN 55450 USA   | curtis          |
|         |            |           |                | .taylor@nwa.com |
+---------+------------+-----------+----------------+-----------------+
| Udaka,  | Special    | JCAB      | 2-1-3          | Ph:             |
| Keizo   | Assistant  |           | Kasumigaseki   | +81-3-5253-8111 |
|         | to the     |           | Chiyoda-ku     | x51128          |
|         | Director,  |           |                |                 |
|         | ATS System |           | Tokyo,         | Fax:            |
|         | Planning   |           | 100-8918,      | +81-3-5253-1663 |
|         | Div.       |           | Japan          |                 |
|         |            |           |                | Email:          |
|         |            |           |                | udaka-          |
|         |            |           |                | k2s5@mlit.go.jp |
+---------+------------+-----------+----------------+-----------------+
| Wada,   | Air        | JCAB      | 1-12 Namiki    | Ph:             |
| H       | Traffic    |           |                | +81-42-992-1181 |
| iroyuki | Controller |           | Tokorozawa-shi |                 |
|         |            |           | Saitama-Pre    | Fax:            |
|         |            |           |                | +81-42-992-1195 |
|         |            |           | 359-0042 Japan |                 |
|         |            |           |                | Email:          |
|         |            |           |                | wada-h033q@     |
|         |            |           |                | tacc.mlit.go.jp |
+---------+------------+-----------+----------------+-----------------+
| Wall,   | Manager,   | FedEx     | 5927 West      | Ph:             |
| Roger   | Air        |           | Imperial       | +1-310-378-5527 |
|         | Traffic    |           | Highway        |                 |
|         | Projects   |           |                | Fax:            |
|         |            |           | Room 248 LAX   | +1-310-646-0639 |
|         |            |           |                |                 |
|         |            |           | Los Angeles,   | Email:          |
|         |            |           | CA 90045-0000  | c               |
|         |            |           | USA            | rwall@fedex.com |
+---------+------------+-----------+----------------+-----------------+
| Wa      | Air        | Tokyo     | 1-12 Namiki    | Ph:             |
| tanabe, | Traffic    | ACC, JCAB |                | +81-42-992-1181 |
| Hideo   | Controller |           | Tokorozawa-shi |                 |
|         |            |           | Saitama-Pre    | Fax:            |
|         |            |           |                | +81-42-992-1195 |
|         |            |           | 359-0042 Japan |                 |
|         |            |           |                | Email:          |
|         |            |           |                | watanabe-h03cf@ |
|         |            |           |                | tacc.mlit.go.jp |
+---------+------------+-----------+----------------+-----------------+
| Wojcik, | Oceanic    | FAA       | Oakland ARTCC  | Ph:             |
| John    | Operations |           |                | +1-510-745-3859 |
|         | Manager    |           | 5125 Central   |                 |
|         |            |           | Avenue         | Fax:            |
|         |            |           |                | +1-510-745-3411 |
|         |            |           | Fremont, CA    |                 |
|         |            |           | 94536 USA      | Email:          |
|         |            |           |                | john.a          |
|         |            |           |                | .wojcik@faa.gov |
+---------+------------+-----------+----------------+-----------------+
| Wolfs   | Regional   | IFALPA    | 12402 98^th^   | Ph:             |
| heimer, | Vice       |           | Ave CT NW      | +1-253-858-3799 |
| Greg    | President, |           |                |                 |
|         | CEP        |           | Gig Harbor, WA | Fax:            |
|         |            |           | 98329 USA      | +1-253-858-7774 |
|         |            |           |                |                 |
|         |            |           |                | Email:          |
|         |            |           |                | cap             |
|         |            |           |                | tintlops@cs.com |
+---------+------------+-----------+----------------+-----------------+
| Yama,   | Assistant  | Japan     | West Passenger | Ph:             |
| Y       | Vice       | Airlines  | Terminal 3-3-2 | +81-3-5756-3135 |
| asuhiro | President  |           |                |                 |
|         |            |           | Haneda Airport | Fax:            |
|         |            |           | Ota-ku,        | +81-3-5756-3527 |
|         |            |           |                |                 |
|         |            |           | Tokyo 144-0041 | Email:          |
|         |            |           | Japan          | yasuhi          |
|         |            |           |                | ro.yama@jal.com |
+---------+------------+-----------+----------------+-----------------+
| Yam     | Flight     | JCAB      | 2-1-3          | Ph:             |
| aguchi, | Inspector  |           | Kasumigaseki   | +81-3-5253-8111 |
| Hideo   |            |           | Chiyoda-ku     | x51346          |
|         |            |           |                |                 |
|         |            |           | Tokyo,         | Fax:            |
|         |            |           | 100-8918,      | +81-3-5253-1663 |
|         |            |           | Japan          |                 |
|         |            |           |                | Email:          |
|         |            |           |                | yamaguchi-      |
|         |            |           |                | h2zb@mlit.go.jp |
+---------+------------+-----------+----------------+-----------------+
| *       | ## **      | #         | ## **Mai       | ## **Ph         |
| *Name** | Position** | # **Organ | ling Address** | one/Fax/Email** |
|         |            | ization** |                |                 |
+---------+------------+-----------+----------------+-----------------+
| Yam     | Captain    | Japan     | West Passenger | Ph:             |
| aguchi, |            | Airlines  | Terminal 3-3-2 | +81-3-5756-3113 |
| M       |            |           |                |                 |
| asahiko |            |           | Haneda Airport | Fax:            |
|         |            |           | Ota-ku,        | +81-3-5756-3527 |
|         |            |           |                |                 |
|         |            |           | Tokyo 144-0041 | Email:          |
|         |            |           | Japan          | masahiko.ya     |
|         |            |           |                | maguchi@jal.com |
+---------+------------+-----------+----------------+-----------------+
| Ya      | Flight     | JCAB      | 2-1-3          | Ph:             |
| mamiya, | Inspector  |           | Kasumigaseki   | +81-3-5253-8111 |
| S       |            |           | Chiyoda-ku     |                 |
| hinichi |            |           |                | Fax:            |
|         |            |           | Tokyo,         | +81-3-5253-1663 |
|         |            |           | 100-8918,      |                 |
|         |            |           | Japan          |                 |
+---------+------------+-----------+----------------+-----------------+

List of Problem Reports closed at the IPACG FIT/8 meeting

+-------------+----------------------+-----------------------+--------+
| **C         | # Title              | **Rationale**         | **PR\  |
| onsultation |                      |                       | Nu     |
| with**      |                      |                       | mber** |
+-------------+----------------------+-----------------------+--------+
| Aircraft    | CPDLC connection     | Design policy of ATS  | 10,019 |
| operator    | timing               | end system            |        |
+-------------+----------------------+-----------------------+--------+
|             | Unable to perform    | Reported event was    | 10,190 |
|             | CPDLC Auto Transfer  | not recognized.       |        |
+-------------+----------------------+-----------------------+--------+
| Aircraft    | Incorrect AFN        | Avionics software     | 10,060 |
| m           | message              | updated               |        |
| anufacturer |                      |                       |        |
+-------------+----------------------+-----------------------+--------+
| DSP         | A data link message  | Data link system      | 10,012 |
|             | consisting of ADS    | modified              |        |
|             | and CPDLC messages   |                       |        |
+-------------+----------------------+-----------------------+--------+
|             |                      |                       | 10,091 |
+-------------+----------------------+-----------------------+--------+
|             |                      |                       | 10,094 |
+-------------+----------------------+-----------------------+--------+
| DSP/GES     | DWLK delay / UPLK    | DSP/GES systems       | 10,188 |
|             | failure              | backed on             |        |
+-------------+----------------------+-----------------------+--------+
|             |                      |                       | 10,192 |
+-------------+----------------------+-----------------------+--------+
|             |                      |                       | 10,194 |
+-------------+----------------------+-----------------------+--------+
|             |                      |                       | 10,195 |
+-------------+----------------------+-----------------------+--------+
|             |                      |                       | 10,197 |
+-------------+----------------------+-----------------------+--------+
|             |                      |                       | 10,200 |
+-------------+----------------------+-----------------------+--------+
|             |                      |                       | 10,202 |
+-------------+----------------------+-----------------------+--------+

+----+----------------------------------+-----------------------------+
| ** | **Title**                        | **Rationale**               |
| PR |                                  |                             |
| ** |                                  |                             |
+====+==================================+=============================+
| 2  | Difficulties establishing CPDLC  | Fixed in BP03.              |
| 87 | connection with B777             |                             |
|    |                                  | Closed in SOPAC.            |
+----+----------------------------------+-----------------------------+
| 2  | B777 sent ADS report after       | Fixed in BP03.              |
| 97 | disconnect                       |                             |
|    |                                  | Closed in SOPAC.            |
+----+----------------------------------+-----------------------------+
| 4  | Legitimate but wrong next + one  | Fixed in BP03.              |
| 41 | positions                        |                             |
|    |                                  | Closed in SOPAC.            |
+----+----------------------------------+-----------------------------+
| 4  | Current ATC Log Replaced By Old  | Fixed in Pegasus 03.        |
| 45 | Log In-Flight                    |                             |
|    |                                  | Closed in SOPAC.            |
+----+----------------------------------+-----------------------------+
| 4  | 777 - Pos Report EST Incorrect   | Fixed in BP03.              |
| 46 | After Waypoint Sequence          |                             |
|    |                                  | Closed in SOPAC.            |
+----+----------------------------------+-----------------------------+

Notes:

1.  BP03 is the Block Point 2003 software release for B777, certified
    for new deliveries in 9/03 and for retrofit 5/04.

2.  Pegasus 03 is the 2003 FMC software release for the B767, certified
    1/04.

JCAB coordinated reply to the ISPACG Co-chair

When an airplane logs onto a particular satellite/Ground Earth Station
(GES), then all SATCOM traffic will be routed via that satellite/GES.
This includes not only ATS messages, but also company data link traffic
(AOC and AAC messages), the flight deck voice channel and the passenger
voice channels. The Owner Requirements Table (ORT) in the airplane\'s
SATCOM system will not provide the flexibility to logon to MTSAT only in
Tokyo FIR. Therefore, airplanes that logon in Tokyo FIR will also do so
in other areas of the Pacific.

Q1: What arrangements will need to be made to allow proper delivery of
company data link messages (and ATS messages to other ATS providers),
including internetworking to ARINC and SITA, as well as forwarding of
messages necessary to support data link (such as media advisories)?

A1: JCAB will deliver ATS messages to/from aircraft connecting with
MTSAT and operating within the Tokyo FIR. These ATS messages will be
directly delivered to Tokyo ACC via MTSAT dedicated network without
routing via a third party. AOC and AAC messages (both data and voice),
passenger communications (APC) for aircraft connecting with MTSAT, and
ATS messages for aircraft connecting with MTSAT and operating in the
foreign FIRs will be delivered by a service provider. JCAB has
officially selected SITA for delivering these messages. Contract with
SITA is underway and will be concluded in the very near future. It is
our understanding that ARINC and SITA have agreed to internetworking
between them for ATS message delivery. We believe that ATS messages
to/from aircraft operating in the foreign FIRs and connecting with MTSAT
will also be exchanged between ARINC and SITA, and will be delivered to
each destination (ATC center) as the same way as currently being done
for ATS messages via Inmarsat. MTSAT DLCS (Data Link Center System) will
route each message to proper destination to be delivered (Tokyo ACC or
SITA). MTSAT DLCS has capability for forwarding media advisories.

Q2: Will operators have to make special arrangements for telephone calls
(flight deck and passenger, both ground to air and air to ground)?

A2: We are working with avionics manufacturers for making arrangements
so that operators will be able to call without modifications to their
equipment, excepting inserting MTSAT data into the ORT, in order to call
to/from aircraft via MTSAT as the same as they do via Inmarsat. As
dialing scheme for telephone call from ground to aircraft varies in
communication carriers (telecom company) and dialing for calls to
aircraft varies in four Inmarsats, dialing for calls to aircraft
connecting with MTSAT may also be different from the dialing for calls
to aircraft connecting with Inmarsat. Regarding calls from aircraft to
ground via MTSAT, JCAB is coordinating with avionics manufacturers in
order that the current arrangements in SATVOICE system in aircraft can
be used without modification.

Q3: How will operators be charged for the AAC and AOC data link messages
(and ATS messages to other centers), as well as the flight deck and
passenger voice channels?

A3: As stated above, any messages via MTSAT, excepting ATS messages
(voice and data) with Tokyo ACC, will be delivered via SITA to each
destination. ATS messages to foreign ATS providers will be delivered via
a DSP who contracts with the foreign ATS provider, after internetworking
between SITA and ARINC. We consider that SITA will charge to users for
the AOC and AAC messages (both data and voice), and passenger
communications (APC), and ATS messages (to foreign ATS providers) as the
same way as they do for their current services.

Q4: Will operators need to establish individual contracts with the MTSAT
GES?

A4: JCAB has implemented two MTSAT GESs in Kobe and Hitachi-ohta. Since
the MTSAT GESs have been designed/configured to be recognized by
operators as a single GES, it is not necessary for operators to
establish individual contracts with the two MTSAT GESs. MTSAT System
will automatically allocate an MTSAT satellite/GES to be connected.
Since a single GES ID is allocated to MTSAT GES, switching-over between
two satellites will automatically be made within seconds when one of
satellites or MTSAT GESs is malfunctioned. Therefore, the operator will
not be aware of the outage nor the switch over. It should be noted that
the Owner Requirements Table (ORT) should include and recognize MTSAT
data. We will inform operators how to add MTSAT data in the ORT upon
completing work with avionics manufacturers.

Q5: Will costs for these other messages be comparable to costs via
INMARSAT satellites?

A5: We consider that the fees for non-ATS messages and the fees for ATS
messages with foreign ATS providers will be determined by SITA according
to their charging policy and considering the costs via Inmarsat. As
stated previously, JCAB, itself will provide Air Traffic Services to
aircraft operating within the Japanese FIRs, while SITA will deliver
non-ATS messages to aircraft connecting with MTSAT and ATS messages to
aircraft connecting with MTSAT and operating outside of the Japanese
FIRs. JCAB will charge to operators for the fees for ATS messages (data
and voice) with Tokyo ACC and collect it as air navigation charge. It
should be noted, however that JCAB does not intend to change, with the
commissioning of MTSAT, the current air navigation charge. Therefore,
the air navigation charge for aircraft connecting with MTSAT will be the
same as aircraft using HF voice.

+---+-----------------------------+-----------+--------------+---------+
|   | ***Capacity                 | ***Action | ***Action    | ***Date |
|   | Enhancement/Action          | with***   | Due***       | Compl   |
|   | Required***                 |           |              | eted*** |
+===+=============================+===========+==============+=========+
|   | **[Implement Reduced        |           |              |         |
|   | Vertical                    |           |              |         |
|   | Separation]{.smallcaps}**   |           |              |         |
+---+-----------------------------+-----------+--------------+---------+
|   | Implement RVSM FL290-410    | FAA/JCAB  |              | 5 Oct   |
|   |                             |           |              | 2000    |
+---+-----------------------------+-----------+--------------+---------+
|   | # [Implement 50NM Late      |           |              |         |
|   | ral Separation]{.smallcaps} |           |              |         |
+---+-----------------------------+-----------+--------------+---------+
|   | #  Implement                | FAA/JCAB  |              | 3 Dec   |
|   | on NOPAC routes/transitions |           |              | 1998    |
+---+-----------------------------+-----------+--------------+---------+
|   | #                           | FAA/JCAB  |              | 3 Dec   |
|   |  Implement on CENPAC PACOTS |           |              | 1998    |
+---+-----------------------------+-----------+--------------+---------+
|   | #  Implement on CEP Tracks  | FAA       |              | 24 Feb  |
|   |                             |           |              | 2000    |
+---+-----------------------------+-----------+--------------+---------+
|   | #  Implement on Ja          | Oakland   |              | 3 Oct   |
|   | pan/Hawaii PACOTS (Generate | ARTCC     |              | 2002    |
|   |  tracks at 50NM separation) |           |              |         |
|   |                             | ATFMC     |              |         |
|   |                             | Japan     |              |         |
+---+-----------------------------+-----------+--------------+---------+
|   | # [I                        |           |              |         |
|   | mplement 50NM Longitudinal  |           |              |         |
|   | Separation]{.smallcaps}[^1] |           |              |         |
+---+-----------------------------+-----------+--------------+---------+
|   | #  Amend Doc 7030 to p      | JCAB/FAA  |              | 20      |
|   | ermit application in Tokyo/ |           |              | April   |
|   | Naha/Oakland/Anchorage FIRs |           |              | 2004    |
+---+-----------------------------+-----------+--------------+---------+
|   | Replace CPDLC waypoint      | JCAB      | Early 2005   |         |
|   | reporting with ADS waypoint |           |              |         |
|   | reporting within Tokyo FIR  |           |              |         |
+---+-----------------------------+-----------+--------------+---------+
|   | Replace CPDLC waypoint      | # FAA     | Oct 2004     |         |
|   | reporting with ADS          |           |              |         |
|   | surveillance within         |           |              |         |
|   | Anchorage FIR               |           |              |         |
+---+-----------------------------+-----------+--------------+---------+
|   | Replace CPDLC waypoint      | # FAA     | June 2005    |         |
|   | reporting with ADS          |           |              |         |
|   | surveillance within Oakland |           |              |         |
|   | FIR                         |           |              |         |
+---+-----------------------------+-----------+--------------+---------+
|   | #  Implement for step       | JCAB      | 2005         |         |
|   |  climb/descent in Tokyo FIR |           |              |         |
+---+-----------------------------+-----------+--------------+---------+
|   | #  Implement for cli        | FAA       | 2005         |         |
|   | mb/descent in Anchorage FIR |           |              |         |
+---+-----------------------------+-----------+--------------+---------+
|   | #  Implement for c          | FAA       | 2005         |         |
|   | limb/descent in Oakland FIR |           |              |         |
+---+-----------------------------+-----------+--------------+---------+
|   | #  Implem                   | JCAB      | 2005         |         |
|   | ent for cruise in Tokyo FIR |           |              |         |
+---+-----------------------------+-----------+--------------+---------+
|   | #  Implement                | FAA       | 2005         |         |
|   | for cruise in Anchorage FIR |           |              |         |
+---+-----------------------------+-----------+--------------+---------+
|   | #  Implemen                 | FAA       | 2005         |         |
|   | t for cruise in Oakland FIR |           |              |         |
+---+-----------------------------+-----------+--------------+---------+
|   | # [Implement 30NM Late      |           |              |         |
|   | ral Separation]{.smallcaps} |           |              |         |
+---+-----------------------------+-----------+--------------+---------+
|   | #  Amend Doc 7030 to p      | JCAB/FAA  |              | 20      |
|   | ermit application in Tokyo/ |           |              | April   |
|   | Naha/Oakland/Anchorage FIRs |           |              | 2004    |
+---+-----------------------------+-----------+--------------+---------+
|   | #  Apply[^2] in li          | FAA/JCAB  | TBD          |         |
|   | mited NOPAC/CENPAC airspace |           |              |         |
+---+-----------------------------+-----------+--------------+---------+
|   | #  Apply i                  | FAA/JCAB  | TBD          |         |
|   | n all NOPAC/CENPAC airspace |           |              |         |
+---+-----------------------------+-----------+--------------+---------+
|   | # [Implement 30NM Longitudi |           |              |         |
|   | nal Separation]{.smallcaps} |           |              |         |
+---+-----------------------------+-----------+--------------+---------+
|   | #  Amend Doc 7030 to p      | JCAB/FAA  |              | 20      |
|   | ermit application in Tokyo/ |           |              | April   |
|   | Naha/Oakland/Anchorage FIRs |           |              | 2004    |
+---+-----------------------------+-----------+--------------+---------+
|   | #  Apply in li              | FAA/JCAB  | TBD          |         |
|   | mited NOPAC/CENPAC airspace |           |              |         |
+---+-----------------------------+-----------+--------------+---------+
|   | #  Apply i                  | FAA/JCAB  | TBD          |         |
|   | n all NOPAC/CENPAC airspace |           |              |         |
+---+-----------------------------+-----------+--------------+---------+
|   | **[Implement Tracks 14/15   |           |              | 7 Sep   |
|   | HKG/TPE to/from             |           |              | 2001    |
|   | LAX/SFO]{.smallcaps}**      |           |              |         |
+---+-----------------------------+-----------+--------------+---------+
|   | **[Implement]{.smallcaps}   |           |              |         |
|   | DARPS**                     |           |              |         |
+---+-----------------------------+-----------+--------------+---------+
|   | #  Limited imp              | Oakland   | TBD          |         |
|   | lementation on Tracks 14/15 | ARTCC     |              |         |
+---+-----------------------------+-----------+--------------+---------+
|   | #  Conduct trials           | Oakland   | TBD          |         |
|   |                             | ARTCC     |              |         |
+---+-----------------------------+-----------+--------------+---------+
|   | #  Impl                     | FAA/JCAB  | TBD          |         |
|   | ementation in North Pacific |           |              |         |
+---+-----------------------------+-----------+--------------+---------+
|   | #  Complete study           | JCAB      |              | 19 Apr  |
|   |                             |           |              | 2002    |
+---+-----------------------------+-----------+--------------+---------+
|   | #  Implementation in CENPAC | JCAB      | TBD          |         |
+---+-----------------------------+-----------+--------------+---------+

OPEN ACTION ITEMS[^3]

+--------+------------------+-----------+------------------------------+
| Action | **Description**  | **Re      | **Status and Action to be    |
| Item   |                  | sponsible | taken**                      |
|        |                  | Office**  |                              |
+========+==================+===========+==============================+
| I      | Application of a | ICAO      | Awaiting approval by ICAO.   |
| P/11-2 | 10- minute       |           | (*Note: information has been |
|        | longitudinal     |           | received informally from     |
|        | separation       |           | ICAO HQ that the proposed    |
|        | minimum without  |           | amendment is being returned  |
|        | the mandatory    |           | to the ICAO Asia/Pacific     |
|        | application of   |           | Office for further           |
|        | Mach Number.     |           | justification*.)             |
+--------+------------------+-----------+------------------------------+
| I      | International    | FAA       | Both FAA and JCAB reported   |
| P/11-3 | Air Traffic Flow |           | that they are working toward |
|        | Management       | JCAB      | a conclusion on the          |
|        |                  |           | agreement to exchange        |
|        |                  |           | Enhanced Traffic Management  |
|        |                  |           | System (ETMS) data.          |
|        |                  |           | FAA/ATCSCC and JCAB/ATFMC    |
|        |                  |           | are in the process of        |
|        |                  |           | finalizing a Letter of       |
|        |                  |           | Agreement outlining hotline  |
|        |                  |           | communication procedures.    |
|        |                  |           | The meeting will be kept     |
|        |                  |           | informed of developments in  |
|        |                  |           | this area.                   |
+--------+------------------+-----------+------------------------------+
| I      | Expansion of     | ICAO      | The meeting will be kept     |
| P/13-3 | Russian Routes   |           | informed of developments in  |
|        |                  | FAA       | this area.                   |
|        |                  |           |                              |
|        |                  | JCAB      |                              |
+--------+------------------+-----------+------------------------------+
| I      | Implement 50NM   | JCAB      | JCAB offered a plan on ADS   |
| P/13-4 | ADS longitudinal |           | waypoint position reporting, |
|        | separation       | FAA       | step climbs and 50NM at      |
|        | minimum in the   |           | cruise. FAA expects to be    |
|        | North Pacific    |           | ready to implement 50NM      |
|        | area             |           | longitudinal separation in   |
|        |                  |           | 2005. Status will be         |
|        |                  |           | reported to IPACG/22.        |
+--------+------------------+-----------+------------------------------+
| I      | Consider the     | JCAB      | JCAB presented a report on   |
| P/14-1 | need for         |           | their concept of bilateral   |
|        | contingency      | FAA       | contingency planning for     |
|        | plans            |           | North/Central Pacific        |
|        |                  |           | airspace in the event that   |
|        |                  |           | an ATC unit experienced      |
|        |                  |           | total failure. The basic     |
|        |                  |           | concept of this plan would   |
|        |                  |           | be that other ATC units      |
|        |                  |           | would be prepared to assume  |
|        |                  |           | responsibility for the       |
|        |                  |           | airspace, facilitated by a   |
|        |                  |           | Coordination Center. FAA     |
|        |                  |           | will respond to JCAB's       |
|        |                  |           | report at IPACG/22.          |
+--------+------------------+-----------+------------------------------+
| I      | Remove city-pair | FAA       | JCAB and FAA have agreed on  |
| P/17-1 | restriction on   |           | the removal of restrictions  |
|        | Tracks 2/3 and   | JCAB      | on PACOTS tracks. MOU        |
|        | 14/15            |           | between all parties will be  |
|        |                  |           | effective July 2004.         |
|        |                  |           | **CLOSED**.                  |
+--------+------------------+-----------+------------------------------+
| I      | Implement        | FAA       | JCAB reported on the revised |
| P/17-4 | lateral offset   |           | guidelines developed by the  |
|        | procedures in    | JCAB      | ICAO SASP/WGWHL/5 meeting,   |
|        | the North and    |           | held in May 2004, which are  |
|        | Central Pacific. |           | expected to be distributed   |
|        |                  |           | as a State Letter. When      |
|        |                  |           | these procedures are         |
|        |                  |           | implemented by ICAO, FAA     |
|        |                  |           | will coordinate with ISPACG  |
|        |                  |           | ATS providers to implement   |
|        |                  |           | lateral offset procedures by |
|        |                  |           | AIP amendment according to   |
|        |                  |           | the revised ICAO guidelines  |
|        |                  |           | on a common date. JCAB and   |
|        |                  |           | FAA will promulgate AIP on   |
|        |                  |           | the lateral offset           |
|        |                  |           | procedures according to the  |
|        |                  |           | revised ICAO guidelines when |
|        |                  |           | they are issued.             |
+--------+------------------+-----------+------------------------------+
| I      | Evaluate current | ICAO      | Awaiting ICAO approval.      |
| P/17-5 | lost             |           |                              |
|        | communications   |           |                              |
|        | procedures       |           |                              |
+--------+------------------+-----------+------------------------------+
| I      | Implement flight | JCAB      | Deferred to IPACG/22.        |
| P/18-2 | re-routing       |           |                              |
|        | between Japan    | FAA       |                              |
|        | and Hawaii       |           |                              |
|        | tracks.          |           |                              |
+--------+------------------+-----------+------------------------------+
| I      | Removal of time  |           | JCAB and FAA have agreed on  |
| P/18-3 | restrictions for |           | the removal of TIME          |
|        | PACOTS Track A.  |           | restrictions on PACOTS Track |
|        |                  |           | A. MOU between all parties   |
|        |                  |           | will be effective soon July  |
|        |                  |           | 2004. **CLOSED**.            |
+--------+------------------+-----------+------------------------------+
| I      | Consider whether | FAA       | Based on discussions at      |
| P/18-4 | the application  |           | IPACG/20, it was agreed that |
|        | of a             | JCAB      | separate tracks should not   |
|        | "segregated"     |           | be considered further by the |
|        | route philosophy |           | NPACE Study and instead the  |
|        | would be of      |           | NPACE model should be        |
|        | benefit to       |           | modified. See new action     |
|        | users.           |           | item IP/21-2. **CLOSED**.    |
+--------+------------------+-----------+------------------------------+
| I      | Develop ATC      | JCAB      | JCAB presented a proposed    |
| P/19-1 | contingency      |           | amendment to the ICAO Doc    |
|        | procedures to be |           | 7030 with contingency        |
|        | used during a    |           | procedures in the event of a |
|        | failure of       |           | loss of data link            |
|        | satellite data   |           | communication.               |
|        | link             |           |                              |
+--------+------------------+-----------+------------------------------+
| I      | Add altitudes on | FAA       | FAA presented a draft MOU    |
| P/19-2 | G344 and R591    |           | outlining a 90-day trial to  |
|        |                  | JCAB      | validate use of non-standard |
|        |                  |           | altitude for direction on    |
|        |                  |           | G344 and R591 when these     |
|        |                  |           | routes are designated as     |
|        |                  |           | part of the PACOTS tracks.   |
|        |                  |           | Anchorage ARTCC and Tokyo    |
|        |                  |           | ACC to finalize the draft    |
|        |                  |           | MOU and establish an         |
|        |                  |           | implementation date. Update  |
|        |                  |           | to be provided to IPACG/22.  |
+--------+------------------+-----------+------------------------------+
| I      | Develop a means  | FAA       | FAA summarized position      |
| P/19-3 | to reduce        |           | report deficiencies that     |
|        | position         | JCAB      | have occurred in Oakland     |
|        | reporting        |           | FIR, which continue to be a  |
|        | deficiencies     | Airlines  | problem. The number of       |
|        |                  |           | overdue reports has declined |
|        |                  |           | only slightly since 2003.    |
|        |                  |           | Aircraft operators were      |
|        |                  |           | encouraged to explain the    |
|        |                  |           | importance of this problem   |
|        |                  |           | to crews, remind flight      |
|        |                  |           | crews of the requirements    |
|        |                  |           | for position reporting, and  |
|        |                  |           | to communicate technical     |
|        |                  |           | problem to the FIT. Tokyo    |
|        |                  |           | ACC and Oakland ARTCC will   |
|        |                  |           | further investigate overdue  |
|        |                  |           | reports and report to        |
|        |                  |           | IPACG/22.                    |
+--------+------------------+-----------+------------------------------+
| I      | Implement        | JCAB      | JCAB advised the meeting     |
| P/20-1 | International    |           | that a survey of airlines    |
|        | Route            |           | has been initiated. Update   |
|        | Reservation      |           | to be provided to IPACG/22.  |
|        | Service (IRRES)  |           |                              |
|        | Program          |           |                              |
+--------+------------------+-----------+------------------------------+
| I      | In-trail         | FAA       | FAA proposed to resume       |
| P/20-2 | climb/in-trail   |           | discussions with airlines    |
|        | descent          |           | regarding their experience   |
|        | (ITC/ITD)        |           | and interest in renewing     |
|        | procedure using  |           | this test procedure. Oakland |
|        | TCAS             |           | ARTCC reported only minimal  |
|        |                  |           | use during recent months by  |
|        |                  |           | airlines of this controller  |
|        |                  |           | workload-intensive           |
|        |                  |           | procedure. IATA and airlines |
|        |                  |           | represented agreed that the  |
|        |                  |           | need for this procedure will |
|        |                  |           | probably be overtaken by ADS |
|        |                  |           | in the Pacific, but it       |
|        |                  |           | should remain available as a |
|        |                  |           | tool for operators who wish  |
|        |                  |           | to use it. UAL is finalizing |
|        |                  |           | pilot procedures to be used, |
|        |                  |           | and expects increased use in |
|        |                  |           | the future. JCAB expressed   |
|        |                  |           | concerns about its           |
|        |                  |           | application, as well as the  |
|        |                  |           | concerns of Japanese         |
|        |                  |           | airspace users. FAA will     |
|        |                  |           | develop a proposed amendment |
|        |                  |           | to ICAO Doc 7030 for         |
|        |                  |           | application in the           |
|        |                  |           | Oakland/Anchorage FIRs.      |
+--------+------------------+-----------+------------------------------+
| I      | Tokyo/Oakland    | FAA       | Oakland ARTCC proposed to    |
| P/20-3 | 165E FIR/CTA     |           | include Oakland FIR/CTA      |
|        | boundary fixes   | JCAB      | boundary waypoints when      |
|        |                  |           | eastbound PACOTS tracks are  |
|        |                  |           | generated. Airlines          |
|        |                  |           | requested that Oakland ARTCC |
|        |                  |           | and Tokyo ACC do a brief     |
|        |                  |           | (10-days or so) survey to    |
|        |                  |           | identify what the 165E       |
|        |                  |           | crossing points would be and |
|        |                  |           | report this information to   |
|        |                  |           | IPACG/22.                    |
+--------+------------------+-----------+------------------------------+
| I      | Implementation   | FAA       | FAA presented a draft MOU to |
| P/21-1 | of AIDC between  |           | validate and implement AIDC  |
|        | Anchorage ARTCC  | JCAB      | for all aircraft transiting  |
|        | and Tokyo ACC    |           | common boundaries between    |
|        |                  |           | these facilities. Tokyo ACC  |
|        |                  |           | advised that they cannot     |
|        |                  |           | agree with the procedures    |
|        |                  |           | unless they are the same as  |
|        |                  |           | those used with Oakland      |
|        |                  |           | ARTCC. Tokyo ACC and         |
|        |                  |           | Anchorage ARTCC to continue  |
|        |                  |           | discussions to finalize the  |
|        |                  |           | MOU. Update to be provided   |
|        |                  |           | to IPACG/22.                 |
+--------+------------------+-----------+------------------------------+
| I      | Determine at     | JCAB      | FAA presented information on |
| P/21-2 | what point       |           | the activities of the NPACE  |
|        | implementing ADS | FAA       | Study Advisory Group (NSAG)  |
|        | technology will  |           | regarding three simulation   |
|        | be necessary for | IATA      | scenarios established.       |
|        | all airlines     |           | Flight tracking program will |
|        |                  |           | be updated to include an     |
|        |                  |           | in-flight conflict           |
|        |                  |           | resolution algorithm and a   |
|        |                  |           | procedures will be           |
|        |                  |           | incorporated to apply        |
|        |                  |           | reduced separation           |
|        |                  |           | standards. NSAG will report  |
|        |                  |           | progress to IPACG/22.        |
+--------+------------------+-----------+------------------------------+
| I      | Consider         | FAA       | FAA presented information on |
| P/21-3 | revising PAC     |           | inconsistencies between NAT  |
|        | turnback         |           | and PAC turnback procedures. |
|        | procedures to    |           | FAA will present information |
|        | harmonize with   |           | from the IPACG discussion    |
|        | changes being    |           | for further discussion at    |
|        | proposed to NAT  |           | Oceanic Work Group. FAA will |
|        | procedures       |           | report status of NAT         |
|        |                  |           | procedure and progress to    |
|        |                  |           | IPACG/22.                    |
+--------+------------------+-----------+------------------------------+
| I      | Expansion of     | FAA       | FAA reported on the plan to  |
| P/21-4 | RVSM-Exclusive   |           | raise the ceiling of         |
|        | Airspace to      |           | RVSM-exclusive airspace in   |
|        | FL410            |           | the Oakland Oceanic,         |
|        |                  |           | Anchorage Oceanic and        |
|        |                  |           | Anchorage Arctic FIRs from   |
|        |                  |           | FL390 to FL410 to correspond |
|        |                  |           | with implementation of US    |
|        |                  |           | domestic RVSM from FL290 --  |
|        |                  |           | FL410 on 20 Jan 2005. Update |
|        |                  |           | to be provided to IPACG/22.  |
+--------+------------------+-----------+------------------------------+
| I      | Implement 30NM   | FAA       | FAA presented the draft      |
| P/21-5 | lateral/30NM     |           | order on RNP4 approval. FAA  |
|        | longitudinal     |           | expects to be ready to       |
|        | (30/30)          |           | implement 30/30 separation   |
|        | separation       |           | in limited South Pacific     |
|        |                  |           | airspace in 2005.            |
|        |                  |           | Information was provided on  |
|        |                  |           | the progress of Australia    |
|        |                  |           | and New Zealand to implement |
|        |                  |           | across the Tasman Sea on 25  |
|        |                  |           | Nov 04. Airlines expressed   |
|        |                  |           | the wish that a coordinated  |
|        |                  |           | 30/30 approval process be    |
|        |                  |           | finalized very soon in order |
|        |                  |           | that the South Pacific       |
|        |                  |           | implementation is not        |
|        |                  |           | jeopardized. FAA will        |
|        |                  |           | provide update to IPACG/22.  |
+--------+------------------+-----------+------------------------------+
| I      | Tokyo/Oakland    | FAA       | Tokyo ACC proposed to add    |
| P/21-6 | 25N and 160E CTA |           | fixes on CTA boundary at the |
|        | boundary fixes   | JCAB      | crossing point of the CTA    |
|        |                  |           | boundary and 25N, and the    |
|        |                  |           | crossing point of the CTA    |
|        |                  |           | boundary and 160E. FAA to    |
|        |                  |           | coordinate with JCAB prior   |
|        |                  |           | to discussions at next OWG   |
|        |                  |           | meeting.                     |
+--------+------------------+-----------+------------------------------+
| I      | Develop common   | FAA       | FAA ATCSCC recommended       |
| P/21-7 | traffic          | ATCSCC    | development of common terms  |
|        | management       |           | of reference for ATFM        |
|        | terminology      |           | communications. FAA ATCSCC   |
|        |                  |           | to provide an update to      |
|        |                  |           | IPACG/22.                    |
+--------+------------------+-----------+------------------------------+
| I      | Evaluate the     | FAA       | FAA ATCSCC recommended       |
| P/21-8 | feasibility and  | ATCSCC    | discussions between the JCAB |
|        | capability of    |           | and FAA to evaluate the      |
|        | utilizing the    |           | feasibility and capability   |
|        | Internet as a    |           | of utilizing secure          |
|        | medium for ATFM  |           | communications technology    |
|        | communication    |           | (Virtual Private Networks)   |
|        |                  |           | over the Internet as a       |
|        |                  |           | medium for communication.    |
|        |                  |           | FAA ATCSCC to provide an     |
|        |                  |           | update to IPACG/22.          |
+--------+------------------+-----------+------------------------------+

[^1]: Implementation of 50NM longitudinal separation will not be
    exclusionary

[^2]: "Apply" means that the air traffic controller may apply this
    separation standard on one or more tracks, or between two or more
    aircraft that are suitably equipped.

[^3]: ^\*^ Action Items for the FANS Interoperability Team (FIT) will be
    tracked separately by the FIT co-chairs.