# Summary of Discussions

Nineteenth Meeting of the

Informal Pacific Air Traffic Control Coordinating Group

Providers Only Meeting

(IPACG/19)

14-17 July 2003; Tokyo, Japan

1.  **Background**

1.1 The Nineteenth Meeting of the Informal Pacific Air Traffic Control
(ATC) Coordinating Group (IPACG/19) was held at the International
Conference Room in the Ministry of Land, Infrastructure and Transport in
Tokyo, Japan, from 14-17 July 2003. This meeting was for providers only.
The IPACG was established to provide a forum for air traffic service
(ATS) providers and users to informally meet and explore solutions to
near term 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. Akira Ono welcomed the participants to IPACG/19 and briefly
discussed the working hours, agenda and development of the final report,
which is to be coordinated by e-mail after the meeting has ended.

2.3 Mr. Shinta Ehara, Director of the Air Traffic Control Division,
JCAB, opened the meeting by welcoming everyone. He discussed IPACG's
accomplishments since its first meeting held in 1988, including RVSM
implementation in the Pacific, RNP10 for certain routes, and ATC
procedures improving operations. Mr. Ehara also noted that while there
were issues affecting the growing demands, JCAB believes that the
demands will recover in the future. The IPACG, therefore, plays an
important role to further improve operations in NOPAC and CENPAC in
introducing data link system.

2.4 Mr. Yoshiki Imawaka, JCAB FIT co-chair, and Mr. Reed Sladen, FAA FIT
co-chair, noted that due to this special providers-only meeting, the FIT
issues would be incorporated into IPACG/19 rather than holding a
separate meeting. The IPACG FIT/7 meeting will take place in October
2003.

## **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: FANS Interoperability Team (FIT) Issues

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/19 and can be made available upon request.

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

  WP/2        2           Implementation of Reduced         JCAB
                          Separation Minima in the NOPAC    
                          and CENPAC airspace using ADS     

  WP/3        2           Lateral Offsets                   JCAB

  WP/4        2           ATC Contingency Procedures During JCAB
                          the Failure of Satellite Datalink 

  WP/5        2           Additional altitudes on G344 and  FAA
                          R591                              

  WP/6        2           Strategic Lateral Offset          FAA

  WP/7        2           Lost Communication Procedures     FAA

  WP/8        2           Removal of Time Restriction for   FAA
                          PACOTS Track A                    

  WP/9        2           Removal of restriction on PACOTS  ATFMC
                          Tracks                            

  WP/10       3           Position Reporting Deficiencies   Oakland ARTCC

  WP/11       4           Distribution of Along Track ADS   JCAB
                          Prediction Errors                 

  WP/12       4           Airbus experience over the North  Airbus
                          Atlantic                          

  WP/13       4           DSP Failure                       ARINC

  WP/14       4           Use of HF datalink (HFDL) for ATC FAA CRA
                          communications                    

  WP/15       4           Proposed phraseology for          Airbus &
                          notifying an aircrew to check     Boeing
                          that the ADS system is armed      

  WP/16       7           Proposal for conduct of a         FAA
                          combined meeting of the Informal  
                          Pacific Air Traffic Coordinating  
                          Group (IPACG) and the Informal    
                          South Pacific Air Traffic         
                          Services Coordinating Group       
                          (ISPACG)                          

  WP/17       4           CRA activities since IPACG/18     CRA

  WP/18       4           Trend problem report              CRA

  WP/19       2           Report on study of bilateral      JCAB
                          contingency plans for             
                          North/Central Pacific airspace    

  WP/20       4           ATS Messaging via High Frequency  ARINC
                          Data Link (HFDL)                  

  WP/21       4           Request for Change (RFC)          FIT Co-chairs
                          proposals for Pacific Operations  
                          Manual (POM)                      
  ------------------------------------------------------------------------

##### **5.0 Agenda Items 2 & 3: ATM and CNS Issues**

1.  Mr. Ono introduced the co-chairs of the ATM Working Group, Ms. Carol
    Might, FAA, and Mr. Satoshi Yamaguchi, JCAB, who led the discussions
    on ATM and CNS issues.

###### Segregated Traffic Flow and Preferred Routes

2.  During IPACG/18, JCAB had proposed the establishment of segregated
    traffic flows in the NOPAC between equipped and non-equipped
    aircraft for 50NM longitudinal separation. The airlines expressed
    the opinion that any proposals should give benefits to equipped
    operators without financially penalized non-equipped operators.

3.  The meeting was presented with information from a survey conducted
    by JCAB in 2002 showing that flights departing from Asian cities and
    over-flying Japan occupied approximately half of the NOPAC and
    CENPAC flights, and that 30 to 50 percent of NOPAC and CENPAC
    flights, depending on the tracks were datalink capable aircraft.
    Another survey conducted by JCAB reported that some 35 percent of
    flights departing from Japan bound for North America were not able
    to obtain preferred levels from departure airports due to
    over-flying traffic from Asian cities. It was suggested that due to
    strong easterly winds in the NOPAC, the reduction of longitudinal
    separation from the current 15 minutes to 50NM and 30NM (equivalent
    to less than 5 minutes and 3 minutes respectively) would
    significantly improve eastbound operations in the NOPAC.

4.  JCAB reported on the status of the Multifunctional Transport
    Satellite (MTSAT). MTSAT-1R and MTSAT-2 have been scheduled for
    launch in early 2004 and early 2005, respectively. It is expected
    that each MTSAT will become operational approximately 9 months after
    the launch. Based on this information, JCAB would be prepared to
    reduce to 50NM longitudinal separation in late 2004; however, they
    do not intend to implement plans or procedures which are not
    accepted by the operators and neighboring centers.

5.  The FAA presented an update on the status of the Advanced
    Technologies and Operational Procedures (ATOP) program. Based on the
    remaining test activities, the FAA was optimistically projecting
    Initial Operational Capability (IOC) at Oakland Air Route Traffic
    Control Center (ARTCC) by the fourth quarter of calendar year 2003,
    with recognition that IOC may not occur until early 2004.

6.  Oakland ARTCC indicated that once the new oceanic automation system
    is operational, they would be able to accommodate either
    environment, and would be relying on airspace users to identify
    which would provide most benefits for them. It would be possible for
    a route to be designated as datalink capable-only. Anchorage ARTCC
    preferred not to implement segregated routes since ATOP will not be
    operational until 2005. Anchorage ARTCC offered to present an
    information paper on this subject at IPACG/20.

7.  Discussions were held on the IATA proposal to reduce separation from
    15 to 5 minutes from Southeast Asia, if FAA were to implement an
    eastbound FANS route. JCAB separation is currently time-based in the
    NOPAC; however, once ADS is operational, it will be necessary to
    review the letter of agreement. JCAB stated that 50 percent of the
    passenger aircraft are currently data-link equipped, so traffic
    would be evenly distributed. Since there was no clear opposition to
    this proposal from FAA, JCAB would propose it to users at IPACG/20.

###### Removal of Time Restrictions on Track A

8.  The FAA presented the results of a study which was conducted to
    evaluate traffic situations on PACOTS Track A, F and G, and to
    evaluate the possibility of removing or reducing the 2030 UTC time
    restriction. At the last meeting of the Oceanic Working Group (OWG),
    the airlines utilizing Track A confirmed that they realize a cost
    savings when time restrictions are not applied.

9.  The ATFMC similarly evaluated the data collected between 15 December
    2002 and 30 June 2003. While they have had no problems with the
    current procedure, they agreed to pursue this request by airspace
    users and Oakland ARTCC.

10. The meeting agreed that the test on Track A would continue until 13
    September 2003. Further discussions will take place at IPACG/20 as
    to whether this will become a permanent procedure. Tokyo ACC and
    Oakland ARTCC will present the results of the trials and consider
    ways to formalize the outcome.

###### Lateral Offsets

11. JCAB addressed a study done by the Electronic Navigation Research
    Institute (ENRI) to conduct a collision risk analysis for the 2NM
    right offset in the current NOPAC route structure. The study showed
    that the 2NM right offset in the NOPAC would meet the target level
    of safety of 5 x 10^-9^ fatal accidents per flight hour. The study
    was presented to the 3^rd^ Meeting of the Working Group of the Whole
    of the ICAO Separation and Airspace Safety Panel (SASP/WG/WHL/3) in
    May 2003. The meeting noted that JCAB did not intend to implement
    offset procedures that were different from the FAA, and that they
    wish to implement procedures that are mutually applied to the entire
    NOPAC and CENPAC.

12. The FAA advised that the SASP/WG/WHL/3 reached the conclusion that
    the ICAO State Letter regarding Guidance for Lateral Offsets would
    be revised to reflect further risk analysis studies done by the
    Mathematicians' Sub-Group of the WG. This revision would permit
    implementation of 2NM lateral offsets in an environment where 50NM
    lateral separation is applied, including the wake turbulence
    procedures, thereby establishing a standardized global procedure.

13. An implementation schedule for the Pacific Region will be further
    considered at IPACG/20.

###### Lost Communication Procedures

14. The FAA presented the meeting with a proposed change to the Regional
    Supplementary Procedures (ICAO Doc 7030) on lost communications.
    These procedures had already been discussed at IPACG/18 and
    ISPACG/17 before being presented to the APANPIRG ATS/AIS/SAR/SG/13
    for consideration.

15. After considerable discussion, it was agreed that this procedure
    should be limited to situations where there is a "total" loss of
    communications by an aircraft. Further editorial changes were made
    to the proposal, which would be coordinated with JCAB and then
    presented to the 14^th^ Meeting of the Asia Pacific Air Navigation
    Planning and Implementation Regional Group (APANPIRG/14) for
    consideration.

###### Overdue Position Reports

16. The FAA summarized deficiencies in the receipt of controller pilot
    data link communications (CPDLC) and high frequency (HF) position
    reports. During late 2002, Oakland ARTCC noticed an increase in the
    number of overdue position reports. Data was collected from 5 March
    to 26 May 2003 to evaluate this situation. During this period,
    Oakland ARTCC controllers had to solicit 2443 position reports that
    had not been received within 10 minutes after the reporting point,
    averaging 29.4 overdue reports per day. Of these, 50.6 percent were
    HF reports and 49.4 percent were CPDLC reports.

17. The FAA Central Reporting Agency (CRA) monitored the overdue CPDLC
    reports and found an error in the FANS software on the B777 that
    would account for some of the missing reports. However, no
    automation problems have been found on the B747 that might explain
    the higher rate for aircraft using CPDLC.

18. Tokyo ACC had observed a similar situation with CPDLC, but not with
    HF position reports. They solicit the report 5 minutes after it is
    overdue. In the past 2 months, 14 such cases were reported, and in
    almost all cases, once solicited, the report came immediately. The
    explanation provided by Tokyo ACC was that problems occurred with
    B777 downlinked information (which matched the explanation given to
    Oakland ARTCC). Pilots clearly know where the next position report
    is due when using HF, but with CPDLC they have to remember which are
    compulsory and which are non-compulsory, and are more likely to
    forget to make the reports. Tokyo ACC will continue to collect
    information and share it with Oakland ARTCC.

19. An amended working paper that reflects this issue as discussed here
    will be prepared for presentation to airspace users at IPACG/20.

###### ATC Contingency Procedures During the Failure of Satellite Data Link

20. JCAB requested that the meeting consider developing ATC contingency
    procedures to be mutually applied by Anchorage, Oakland and Tokyo
    ACCs when HF voice communications are available during the failure
    of satellite data link. According to a simulation conducted by ENRI,
    when a ground-Earth station (GES) fails, it may take several dozen
    minutes to re-establish logon with another GES.

21. ICAO procedures for the application of 50NM and 30NM longitudinal
    separation minima using ADS and CPDLC are detailed in the PANS-ATM,
    Doc 4444. These procedures detail action using an alternative means
    of communication when an ADS periodic or waypoint change event is
    not received within a certain time. The alternative means of
    communication is considered to be HF voice.

22. JCAB will permit the temporary use of one-half standard separation
    when the standard longitudinal separation cannot be immediately
    applied using HF voice, which could be one possible option.
    Anchorage ARTCC made the point that based on track loading, it may
    be easier to implement the standard separation rather than go to a
    contingency separation standard.

23. A task force made up of representatives from Oakland, Anchorage and
    Tokyo ACCs was established to work this issue by e-mail and report
    the progress to IPACG/20. Rapporteurs of the task force will be
    Yoshiki Imawaka, JCAB and Carol Might, FAA.

####### Report on Study of Bilateral Contingency Plans for North/Central Pacific Airspace

24. JCAB reported on a study conducted to prepare the concept of
    contingency plans and to develop contingency programs that are
    common to the North and Central Pacific airspace. The goal was to
    develop plans and programs that could accommodate a minimum flow and
    a level of safety for oceanic traffic when a catastrophe was
    experienced by an ATC facility. The study identified the basic
    requirements for contingency plans and recommended the categorizing
    of actions necessary immediately after the occurrence. An example of
    a contingency plan concept was presented to the meeting. JCAB will
    continue this study and report progress at future meetings.

25. The FAA reported that internal contingency plans are already in
    place. If so requested by JCAB, the FAA would further consider
    whether facilities could provide control services for portions of
    Tokyo FIR.

26. In order to ensure that an assessment of the impact on civil
    aircraft operating in international airspace would be made quickly
    should an event such as the tragedy on 11 September 2001 occur
    again, a proposal to amend the contingency checklist had been
    submitted to the FAA Crisis Response Working Group. The proposed
    checklist items read as follows:

```{=html}
<!-- -->
```
a.  *Should transit of U.S controlled international airspace outside the
    12 NM territorial limit be restricted?*

b.  *Assess the ability to continue to provide safe and orderly flow of
    international air traffic in the event of disruptions of air traffic
    services and related supporting services.*

c.  *Take into account the need to preserve the availability of major
    world air routes within the air transportation system.*

d.  *Ensure to the greatest extent possible the continuous access to
    airspace for international civil flights over the high seas.*

####### Additional Altitudes on G344 and R591

1.  Anchorage ARTCC proposed that the additional altitudes of FL350,
    FL370, FL390 and FL410 be available on G344 and R591, when
    designated at NOPAC tracks, without verbal coordination of
    inappropriate altitude for direction of flight. The additional
    altitudes would increase the capacity of the NOPAC without adding
    new routes. This was also seen as an incremental step toward an
    eventual restructuring of the NOPAC to accommodate ADS and reduced
    separation standards.

2.  Tokyo ACC concurred with the concept; however, Tokyo also wishes to
    use altitudes below FL350 without coordination. The Tokyo ACC
    proposal was that when G344 and R591 were designated as westward
    PACOTS routes, all flight levels above 350 would be used; conversely
    when they were eastbound routes, all flight levels below 350 would
    be used.

3.  The meeting encouraged the facilities to agree on a trial period.
    Anchorage ARTCC and Tokyo ACC will report the status to the next
    meeting.

*Elimination of Verbal Communication between Tokyo ACC & Oakland ARTCC*

4.  Oakland ARTCC advised the meeting that based on current
    capabilities, they are not able to discontinue verbal communication
    at this time. Because AIDC is not an integrated part of workstation,
    there is no way to accept/reject a message. Once ATOP is operational
    and there is complete AIDC functionality, they would be willing to
    re-address this issue. FAA recommended that this action item be
    closed until ATOP is implemented. The meeting agreed to this
    request.

###### Civil-Military ATC Coordination

5.  The United States Air Force highlighted the importance of the FAA
    ATC System Command Center (ATCSCC) and Air Traffic Services Cell to
    civil-military cooperation. The FAA management of the US National
    Airspace System with full consideration for Department of Defense
    needs, as well as the daily coordination, was noted.

**6.0 Agenda Item 4: The FANS Interoperability Team (FIT) Issues**

### 6.1 The FIT issues were addressed by the IPACG FANS Interoperability Team Working Group, which was co-chaired by Mr. Reed Sladen, FAA, and Mr. Yoshiki Imawaka, JCAB. 

### Requests for Change (RFCs) to the Pacific Operations Manual

6.2 The meeting was advised that the Informal South Pacific ATS
Coordinating Group FANS Interoperability Team (ISPACG/FIT) adopted at
its meeting held in March 2003, in whole or in part,

19 amendment proposals for various sections of the Pacific Operations
Manual (POM). All of the changes were adopted, with minor editorial
revisions in some cases. (Note that since the IPACG/19 meeting, Version
2.0 of the POM has been published including the revisions listed below.)

  -------- --------------------------------------------------------------
  **RFC    **Subject**
  Nr.**    

  02/008   ADS Emergency Mode

  02/009   ATS System Integrity

  02/010   Domestic CPDLC Implementation

  02/011   Report Level

  02/012   Transfer of Datalink for Shirt FIR Transit

  03/001   Downlink Messages

  03/002   Multi-element Uplink Messages

  03/003   System Integrity and Monitoring Introduction

  03/004   Changes to various sub-sections of POM Section4

  03/005   Proposed Amendments to POM Section 5

  03/006   Proposed Amendments to POM Section 5.8

  03/007   Proposed Amendments to POM Section 6

  03/008   Proposed Amendments to POM Section 7

  03/009   Aligning several Free Text Messages with the ICAO Message Set

  03/010   Responding to Downlink Request

  03/011   Proposed Amendments to POM Section 8

  03/012   Use of Contact/Monitor Uplink Messages

  03/013   Direct Tracking and UPR Aircraft

  03/014   Non-automatic Termination of the Connection
  -------- --------------------------------------------------------------

###### Datalink Position Reporting

### 6.3 Airbus briefed the meeting on ADS issues experienced with FANS-A in service in the North Atlantic (NAT) Region and listed the corrective actions launched by Airbus. Boeing advised that they have not had similar problems in their MD11, and that they tested all software and confirmed that the MD11 FANS-1 package was essentially the same as the one on the MD10 and B717.

###### ADS Phraseology

6.4 Airbus and Boeing jointly presented a proposed phraseology for
notifying an aircrew to check that the ADS system is armed. This was due
to instances where controllers were unable to initiate ADS contact with
aircraft under their control. This procedure would be intended to alert
aircrews to check their ADS system to ensure it is functioning as
required. Airbus and Boeing recommended to the meeting that an amendment
be made to the POM to reflect the proposed free text message "RECYCLE
ADS" which is consistent with other phraseology in the radar
environment. Since it is a free text uplink message, the only response
shown by the pilot is "ROGER." The meeting agreed to adopt the proposed
change. However, since a change to the POM requires endorsement by the
ISPACG, the amendment procedure will be studied. The FIT Co-chairs
agreed to notify the proposed change to the FIT members by e-mail.

###### New Problem Reports

6.5 The problem reports processed by the FAA and JCAB Central Reporting
Agency Support Agencies (CRASAs) since the IPACG FIT/6 meeting held in
October 2002 were presented. The JCAB CRASA received 39 problem reports,
while the FAA CRASA received 17 problem reports, of which 9 problem
reports (PRs) were transferred from the JCAB CRASA and 1 was forwarded
to the JCAB CRASA for analysis. The status of each PR was presented to
the meeting. The FIT Co-chairs advised the meeting that individual PRs
will not be presented to the next FIT meeting; however, since a list of
PRs will be attached to the meeting report, the FIT members would be
aware of them. The list of the PRs is in Appendix B.

6.6 Analysis of the specific reports was presented. A representative
from FAA Flight Standards voiced concerns about possible trends and
suggested that further analysis might help identify their presence. A
list of PRs to be closed was presented. Since not all the FIT members
attended this meeting, the PRs presented were not closed. The meeting
agreed to address this list at the FIT/7 meeting when all members were
present.

###### ADS Prediction Errors

6.7 The ENRI presented a paper analyzing ADS prediction errors observed
in the NOPAC. The paper recalled the recent paper chronicling this
analysis as presented at the SASP/WG/WHL/3. The ENRI had studied ADS
data collected on ATS route R220 in the NOPAC from April 2000 to October
2002. Extremely large along-track prediction errors, considered to be
caused by flight management system (FMS) software problems, were
excluded from the analysis. The analysis was summarized below.

  ---------------------- ----------------- ---------------- ---------------
                         **B747-400**      **B777-200**     **A340-300**

  **Sample size**        34507             7389             744

  **Mean (NM)**          \- 1.948          0.316            4.267

  **Standard deviation   2.403             1.792            5.067
  (NM)**                                                    

  **Range (NM)**         -27.43, +12.22    -7.512, +12.30   -5.897, +27.98
  ---------------------- ----------------- ---------------- ---------------

6.8 The meeting was advised that the ENRI planned to model along-track
ADS prediction errors and wished to study the algorithm of the onboard
ADS equipment and FMS. Airbus noted the potential impact of the
prediction of the wind and how this might be incorporated into the
analysis, and further suggested that this could be the reason for the
optimistic position-reporting observed in the study. Airbus and Boeing
agreed to supply data as needed to support further analysis.

###### Datalink Problem Reports

6.9 The JCAB CRASA presented the yearly trends of ATS data link problem
reports in 2001 and 2002. The JCAB CRASA concluded that a number of
problems were resolved by the efforts of FIT members and the number of
new problem reports tends to be decreasing gradually. However, new types
of reports, such as those involving high frequency data link (HFDL),
were received from the end users. The JCAB CRASA called for further
analysis as a variety of new air/ground systems are being introduced in
Pacific airspace.

###### HF Data Link

### 6.10 JCAB has not decided whether to use HFDL for ATS purposes yet, and further study was necessary. In order to assist the JCAB study, ARINC and Boeing gave presentations at the meeting.

6.11 ARINC presented a summary of its efforts to introduce worldwide
HFDL systems. The meeting was advised that ARINC has modified the
priority for data link connection on 8 July 2003 to be VHF, SATCOM then
HF in order. A representative from FAA Flight Standards noted that HFDL
is approved as a tertiary mode to SATCOM and trials in the NAT Region
should carefully be monitored so that it can be used in the Pacific
Region. Oakland ARTCC advised the meeting that if HFDL can be proven
reliable, then FAA would certify it as a backup for oceanic ATC
purposes. Airbus expressed support for the initiative. The United States
Air Force (USAF) representative referred to the ICAO *Manual on HF Data
Link* (Doc 9741) which states that HFDL can be used for ATC purposes,
although it is not meant to support separation standards reductions,
rather to support ADS and CNS/ATM in general.

6.12 The meeting considered that JCAB and FAA should determine if HFDL
could be used for ATC purposes in NOPAC and CENPAC and whether it is a
suitable means of communications to support the reduced horizontal
separation minima using ADS in a FANS-1/A data link environment. JCAB
noted that the NAT focus on using HFDL was improvement of waypoint
reports (WPR), however in the Pacific, JCAB and FAA were looking more at
separation reductions using ADS which requires a certain level of
performance. JCAB advised that while further study is required, their
initial study had indicated that HFDL could be used for WPR instead of
HF voice reporting, but did not appear appropriate for 50 and 30NM
longitudinal separation minima requiring ADS due to its performance.

6.13 Boeing presented the meeting with information on Boeing fleet HFDL
status, aircraft certification of HFDL for ATS communication, the Boeing
certification plan, and operational issues. A previous version of this
presentation was given to the ISPACG/17 meeting held in March 2003.
ARINC provided clarification that the HF voice and HFDL use one antenna,
known as common coupler, so if a transmission on voice is made, it would
interrupt an HFDL transmission. ARINC further advised that it would
require at least 60 seconds to come back after the interruption. FAA
noted that once pilots have been trained in proper procedural use, this
would mitigate dual use problems.

6.14 Oakland ARTCC expressed a concern that the controllers currently
have no indication of the type of data link and the automation system
would apply 50NM longitudinal standard automatically if using ADS and
CPDLC. If it were decided that HFDL could not be used for the
application of 50NM longitudinal separation minimum, the indication of
data link type would have to be displayed for controllers, and that
there is no real-time way to display this with ATOP. The FAA Flight
Standards representative informed the meeting that the operational
approval would stipulate the region where HFDL could be used. Mr. Sladen
advised that the data link service provider determines whether HFDL or
SATCOM is used. Coordination between data link service providers and ATS
providers must occur. The meeting agreed that in order to avoid possible
confusion for the operators, an operational approval for the use of HFDL
for ATC purposes in NOPAC and CENPAC should be harmonized between FAA
and JCAB. JCAB advised that modification was being made to ODP-3 so as
not to accept ADS/CPDLC messages from HFDL.

### Data Link Service Provider Failure Notification

6.15 ARINC informed the meeting of their efforts to remedy the problem
of ATS providers not receiving outage notification timely. At the
IPACG/18 meeting, ARINC was asked to research a quick notification
procedure. Based on information provided, ARINC made the following
decision:

1.  ARINC Operation Center could transmit Quick Notification via AFTN to
    Tokyo ACC, Anchorage ARTCC and Oakland ARTCC when it was determined
    that

-   ARINC Central Processing System was out of service

-   ARINC ATC Gateway was out of service

-   ARINC-SITA FANS internetworking link was completely non-operational.

2.  The AFTN message format will be "ARINC data link out of service as
    of (date & time) due to (one or more of the reasons stated above)."

6.16 The meeting was advised that ARINC sent out a test message to the
above three Centers (addressed to RJTGZQZX, PAZAZQZX, and KZOAZRZX) on 5
June 2003 and it was confirmed received. ARINC recommended that the
IPACG should determine if this is acceptable method for Quick
Notification to each Center concurred. All three Centers accepted this
recommendation.

6.17 SITA also gave a presentation regarding notifications of
planned/unplanned outages for the SITA system. SITA advised that SITA
Service Advisories, including notification of planned/unplanned outages
are sent to the SITA customers by SITATEX, fax or e-mails according to
the customer's preference. It was advised that SITA Service Advisories
for the onset of unplanned outages are sent within 5 minutes (Note:
ISPACG FIT in September 1998 requested 15 minutes.) JCAB advised that
the Radio Engineering Division of JCAB planned to coordinate with ARINC
and SITA for notifying outages. SITA asked that during August 2003 any
unplanned outages that are not notified, or unplanned outages whose
notifications do not arrive within 15 minutes of the start of the
outage, be advised to the JCAB CRASA.

### Draft Guidance for a Regional Monitoring Agency (RMA) Supporting Implementation and Continued Use of ATS Datalink Systems

6.18 The FAA and JCAB jointly presented the second draft of the handbook
on Guidance Material for the End-to-End Safety and Performance
Monitoring of Air Traffic Service Data Link Systems for the Asia/Pacific
Region, which had been developed by the ICAO Asia Pacific Airspace
Safety Monitoring (APASM) Task Force.

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

7.1 The **CNS/ATM Planning Chart** was presented and updated, and is at
Appendix C.

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

8.1 The FAA Technical Center and Rutgers University presented a brief
account of the progress to date associated with the Northern Pacific
Airspace Cost Effectiveness (NPACE) Study. The main purpose of the NPACE
study is to examine the relative value/benefit of potential future
changes to Northern Pacific airspace. This presentation provided an
overview of the flight event, flight planning and flight tracking
algorithms used in the simulation model. A comparison between simulated
flight plans and flight plans received from Cathay Pacific Airways Ltd.
was presented.

8.2 Appreciation was expressed to JCAB, Oakland ARTCC and the airlines
that provided data for this study. The modeling was based on more than
230,000 flights during 2002, which were studied to ensure that the model
was valid. The study confirmed that the Flight Events Program
statistically generated flight events that mimicked the current
characteristics of flights over the NOPAC and can incorporate changes to
represent changes in the Region.

8.3 Preliminary results for the high and low speed track scenario were
presented. Preliminary simulations show that the high and low speed
track scenario has the potential to provide the users with some fuel
savings over the current track system. Further simulations are required
to determine the influential factors (for example high and low speed
cutoff and route choices) and their effect on the system savings.

8.4 It was noted that there was still more work to be done on the high
speed -- low speed tracks. Future work will include the ADS and non-ADS
mixed environment. Oakland ARTCC asked that segregated routes be
simulated to determine the potential benefits and JCAB noted their
interest in seeing the results of this analysis. FAA responded that they
could conduct the simulation if provided with the necessary elements for
the study. The meeting was encouraged to provide suggestions and input
to the FAA Technical Center for future simulations.

**9.0 Agenda Item 7: Other Business**

*Proposal for Conduct of a Combined Meeting of the IPACG and the
Informal South Pacific Air Traffic Services*

*Coordinating Group (ISPACG)*

9.1 The FAA proposed to conduct a combined meeting of the IPACG and the
ISPACG for the purpose of harmonizing procedures within the Pacific
Region in a timely manner. The FAA has offered to host IPACG/20 in
Honolulu during the week of 6-10 October 2003, and asked the meeting to
consider inviting the ISPACG participants to that meeting. The paper
also asked the Group to consider a joint meeting of the IPACG/ISPACG FIT
Meetings at this venue.

9.2 JCAB commented that they felt it meaningful to harmonize procedures
and that they supported this idea of the joint meeting. JCAB added that
due to issues unique to JCAB and FAA, a joint meeting should be held on
an as-needed basis and that IPACG meetings should continue to be held at
least twice a year. It was agreed that, in order to avoid confusion, the
meeting would be named IPACG/20 and that an invitation would be extended
to the ISPACG ATS providers, regulatory authorities and airlines to
attend.

9.3 JCAB expressed their concern that a joint meeting could result in a
large meeting in excess of 100 participants and could be difficult. The
FAA responded that many people attend both meetings and the size of a
joint meeting would be manageable. The FAA FIT Co-Chair added that it
was helpful having the JCAB FIT Co-Chair at the previous ISPACG FIT
Meeting.

9.4 Anchorage ARTCC offered to host IPACG/21. A discussion ensued
regarding continuation of the past practice of JCAB hosting two
meetings, and then FAA hosting two meetings. JCAB proposed that the
meeting work towards alternating the meetings and decide on a future
schedule at IPACG/20.

####### Report on the Progress of the Asia Pacific Airspace Safety Monitoring Task Force

9.5 A brief update was presented on the progress of the ICAO Asia
Pacific Airspace Safety Monitoring (APASM) Task Force. The Task Force
has completed their work and will provide a recommendation to
APANPIRG/14 to establish a Sub-Group called the Regional Airspace Safety
Monitoring Advisory (RASMA) Sub-Group.

9.6 Handbooks detailing procedures for airspace safety monitoring and
CPDLC system performance monitoring have been prepared. Pacific Regional
monitoring of required navigation performance and reduced vertical
separation minimum will continue to be performed by the FAA Technical
Center, and Pacific data link monitoring will continue to be performed
by JCAB and FAA CRA's.

####### Update of Action Items

9.7 The meeting updated the action item list, which is at Appendix D.

*Closing*

9.8 The Co-chairs expressed their appreciation for the support of all
participants during the meeting. The FAA Co-Chair expressed her sincere
appreciation to JCAB for the excellent meeting facilities and their
flexibility in changing this meeting, which was previously planned to be
held in April 2002, on short notice.

9.9 The meeting was closed by the Co-chairs.

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

Akira Ono Leslie S. McCormick

Co-chair for JCAB Co-chair for FAA

Attachments:

Appendix A -- Meeting Attendees

Appendix B -- List of Problem Reports

Appendix C -- CNS/ATM Planning Chart

Appendix D -- Open Action Items

+---------+------------+-----------+----------------+-----------------+
| *       | ## **      | #         | ## **Mai       | ## **Ph         |
| *Name** | Position** | # **Organ | ling Address** | one/Fax/Email** |
|         |            | ization** |                |                 |
+=========+============+===========+================+=================+
| Burton, | Program    | CSSI,     | 400 Virginia   | PH:             |
| Ross    | Manager    | Inc.      | Avenue, SW     | +1-202-863-7439 |
|         | Oceanic    |           |                |                 |
|         | Airspace   |           | Suite 210      | Fax:            |
|         |            |           |                | +1-202-863-2398 |
|         |            |           | Washington, DC |                 |
|         |            |           | 20024 USA      | Email:          |
|         |            |           |                | rbur            |
|         |            |           |                | ton@cssiinc.com |
+---------+------------+-----------+----------------+-----------------+
| C       | Datalink   | AIRBUS    | 1, Rond Point  | PH:             |
| assiau- | System     |           | Maurice        | +33-5-6211-0525 |
| Haurie, | Engineer   |           | Bellonte       |                 |
| chr     |            |           |                | Fax:            |
| istophe |            |           | 31707 Blacnac  | +33-5-6193-4425 |
|         |            |           | Cedex France   |                 |
|         |            |           |                | Email:Christ    |
|         |            |           |                | ophe.cassiau-ha |
|         |            |           |                | urie@airbus.com |
+---------+------------+-----------+----------------+-----------------+
| E       | Professor  | Rutgers   | Dept. of       | PH:             |
| lsayed, |            | U         | Industrial     | +1-732-445-3859 |
| Elsayed |            | niversity | Engineering    |                 |
|         |            |           |                | Fax:            |
|         |            |           | 96             | +1-732-445-5467 |
|         |            |           | Frelinghuysen  |                 |
|         |            |           | Road           | Email:          |
|         |            |           |                | elsayed@        |
|         |            |           | Piscataway, NJ | rci.rutgers.edu |
|         |            |           | 08854-8018 USA |                 |
+---------+------------+-----------+----------------+-----------------+
| F       | CRA        | The       | PO Box 3707 MC | PH:             |
| ischer, |            | Boeing Co | 7x-70          | +1-425-373-2683 |
| Bill    |            |           |                |                 |
|         |            |           | Seattle, WA    | Fax:            |
|         |            |           | 98124-2207 USA | +1-425-373-2623 |
|         |            |           |                |                 |
|         |            |           |                | Email:          |
|         |            |           |                | William.m.fis   |
|         |            |           |                | cher@boeing.com |
+---------+------------+-----------+----------------+-----------------+
| Fujita, | ATCA       | Air       | K-1 Building   | PH:             |
| Hiroshi | Associa    | Traffic   | 1-6-6          | +81-3-3747-1231 |
|         | te/CNS/ATM | Control   | Han            |                 |
|         | Specialist | As        | edakuko,Ota-ku | Fax:            |
|         |            | sociation |                | +81-3-3747-1231 |
|         |            | -- Japan  | Tokyo,         |                 |
|         |            |           | 144-0041 Japan | Email:          |
|         |            |           |                | cras            |
|         |            |           |                | a@cra-japan.org |
+---------+------------+-----------+----------------+-----------------+
| Fu      | Chief,     | JCAB      | 2-1-3          | PH:             |
| nayama, | Flight     |           | Kasumigaseki   | +81-3-5253-8750 |
| To      | Procedures |           | Chiyoda-ku     |                 |
| shihide | and        |           |                | Fax:            |
|         | Airspace   |           | Tokyo,         | +81-3-5253-1663 |
|         | Program    |           | 100-8918,      |                 |
|         | Office,    |           | Japan          | Email:          |
|         | ATC        |           |                | funayama-       |
|         | Division   |           |                | t2qp@mlit.go.jp |
+---------+------------+-----------+----------------+-----------------+
| Hata    | Manager    | Air       | K-1 Building   | PH:             |
| kenaka, |            | Traffic   | 1-6-6          | +81-3-3747-1231 |
| Masami  |            | Control   | Han            |                 |
|         |            | Asso      | edakuko,Ota-ku | Fax:            |
|         |            | ciation - |                | +81-3-3747-1231 |
|         |            | Japan     | Tokyo,         |                 |
|         |            |           | 144-0041 Japan | Email:          |
|         |            |           |                | hatakenaka@a    |
|         |            |           |                | tc.mt.nec.co.jp |
+---------+------------+-----------+----------------+-----------------+
| H       | ATC        | Tokyo     | 1-12 Namiki    | PH:             |
| ayashi, | Oceanic    | Area      |                | +81-42-992-1317 |
| Atsushi | Specialist | Control   | T              |                 |
|         |            | Center    | okorozawa-city | Fax:            |
|         |            |           |                | +81-42-992-1195 |
|         |            |           | SAITAMA Pref   |                 |
|         |            |           |                | Email:          |
|         |            |           | 359-0042 Japan |                 |
+---------+------------+-----------+----------------+-----------------+
| Harris, | Int        | CSSI,     | 400 Virginia   | PH:             |
| J       | ernational | Inc.      | Avenue, SW     | +1-202-484-3358 |
| ennifer | Air        |           |                |                 |
|         | Traffic    |           | Suite 210      | Fax:            |
|         | Specialist |           |                | +1-202-863-2398 |
|         |            |           | Washington, DC |                 |
|         |            |           | 20024 USA      | Email:          |
|         |            |           |                | jhar            |
|         |            |           |                | ris@cssiinc.com |
+---------+------------+-----------+----------------+-----------------+
| Hong,   |            | JCAB      | 2-1-3          | PH:             |
| Robert  |            |           | Kasumigaseki   | +81-3-5253-8749 |
|         |            |           | Chiyoda-ku     |                 |
|         |            |           |                | Fax:            |
|         |            |           | Tokyo,         | +81-3-5253-1663 |
|         |            |           | 100-8918,      |                 |
|         |            |           | Japan          | Email:          |
+---------+------------+-----------+----------------+-----------------+
| I       | Special    | JCAB      | 2-1-3          | PH:             |
| mawaka, | Assistant  |           | Kasumigaseki   | +81-3-5253-8743 |
| Yoshiki | to the     |           | Chiyoda-ku     |                 |
|         | Director   |           |                | Fax:            |
|         |            |           | Tokyo,         | +81-3-5253-1663 |
|         |            |           | 100-8918,      |                 |
|         |            |           | Japan          | Email:          |
|         |            |           |                | imawaka-        |
|         |            |           |                | y2ys@mlit.go.jp |
+---------+------------+-----------+----------------+-----------------+
| Iw      | Chief of   | JCAB      | 2-1-3          | PH:             |
| ahashi, | ATS radio  |           | Kasumigaseki   | +81-3-5253-8749 |
| Kouji   | com        |           | Chiyoda-ku     |                 |
|         | munication |           |                | Fax:            |
|         |            |           | Tokyo,         | +81-3-5253-1663 |
|         |            |           | 100-8918,      |                 |
|         |            |           | Japan          | Email:          |
|         |            |           |                | iwahashi-       |
|         |            |           |                | k2b2@mlit.go.jp |
+---------+------------+-----------+----------------+-----------------+
| Izuka,  |            | JCAB      | 2-1-3          | PH:             |
| Naoto   |            |           | Kasumigaseki   | +81-3-5253-8749 |
|         |            |           | Chiyoda-ku     |                 |
|         |            |           |                | Fax:            |
|         |            |           | Tokyo,         | +81-3-5253-1663 |
|         |            |           | 100-8918,      |                 |
|         |            |           | Japan          |                 |
+---------+------------+-----------+----------------+-----------------+
| Kodo,   | Internship | E         | 689-42         | PH:             |
| T       | Student    | lectronic | Tsuboi-cho     | +81-422-41-3171 |
| akahiro |            | N         | Funabashi      |                 |
|         |            | avigation | Chiba,         | Fax:            |
|         |            | Research  | 274-0062,      | +81-422-41-3176 |
|         |            | Institute | Japan          |                 |
|         |            |           |                | Email:          |
|         |            |           |                | Kodo@enri.go.jp |
+---------+------------+-----------+----------------+-----------------+
| Kudo,   | Director   | JCAB      | 2-1-3          | PH:             |
| M       | of         |           | Kasumigaseki   | +81-3-5253-8743 |
| asahiro | Int        |           | Chiyoda-ku     |                 |
|         | ernational |           |                | Fax:            |
|         | Policy     |           | Tokyo,         | +81-3-5253-1663 |
|         | Co         |           | 100-8918,      |                 |
|         | ordination |           | Japan          | Email:          |
|         |            |           |                | kudou-          |
|         |            |           |                | m2ct@mlit.go.jp |
+---------+------------+-----------+----------------+-----------------+
| Kearns, | Manager,   | SITA      | PMB210, 8094   | PH:             |
| K       | AIRCOM     |           | Rolling Road   | +1-703-339-8965 |
| athleen | Service    |           | Springfield,   |                 |
|         | D          |           | Virginia,      | Fax:            |
|         | evelopment |           | 22153, USA     | +1-703-339-8966 |
|         |            |           |                |                 |
|         |            |           |                | Email:          |
|         |            |           |                | Kathleen.k      |
|         |            |           |                | earns@sita.aero |
+---------+------------+-----------+----------------+-----------------+
| Kosugi, | Air        | Air       | 1302-17        | PH:             |
| Shoichi | Traffic    | Traffic   | Kosenuki,      | +81-92-608-6114 |
|         | Flow       | Flow      | Nata,          |                 |
|         | Management | M         | Higashi-ku     | Fax:            |
|         | Officer    | anagement |                | +81-92-608-6129 |
|         |            | Center,   | Fukuoka-city,  |                 |
|         |            | Japan     | Fukuoka,       | Email:          |
|         |            |           |                | kosugi-s07vf@   |
|         |            |           | 811-0204,      | atfm.mlit.go.jp |
|         |            |           | Japan          |                 |
+---------+------------+-----------+----------------+-----------------+
| Lavi    | Customer   | SITA      | 770 Sherbrooke | PH:             |
| olette, | Support    |           | West, Suite    | +1-514-982-3524 |
| Sylvain | Account    |           | 1500 Montreal, |                 |
|         | Manager    |           | Quebec,        | Fax:            |
|         |            |           | H3A1G1, Canada | +1-514-982-3597 |
|         |            |           |                |                 |
|         |            |           |                | Email:          |
|         |            |           |                | sylvain.lavio   |
|         |            |           |                | lette@sita.aero |
+---------+------------+-----------+----------------+-----------------+
| M       | Support    | FAA       | Oakland ARTCC  | PH:             |
| aynard, | Manager,   |           |                | +510-745-3543   |
| David   | Int        |           | 5125 Central   |                 |
|         | ernational |           | Avenue         | Fax:            |
|         | Procedures |           |                | +510-745-3482   |
|         |            |           | Fremont, CA    |                 |
|         |            |           | 94536 USA      | Email:          |
|         |            |           |                | david.          |
|         |            |           |                | maynard@faa.gov |
+---------+------------+-----------+----------------+-----------------+
| Martin, | Operations | FAA       | Wi             | PH:             |
| Lauren  | Research   |           | lliam.J.Hughes | +1-609-485-7941 |
|         | Analist    |           | Technical      |                 |
|         |            |           | Center         | Fax:            |
|         |            |           |                | +1-609-485-5117 |
|         |            |           | ACB-310        |                 |
|         |            |           | Atlantic city, | Email:          |
|         |            |           | NJ, 08405, USA | Lauren          |
|         |            |           |                | .martin@faa.gov |
+---------+------------+-----------+----------------+-----------------+
| McC     | Deputy     | FAA       | Air Traffic    | PH:             |
| ormick, | Manager,   |           | S              | +1-202-267-7646 |
| Leslie  | ATS        |           | ervices/AAT-30 |                 |
|         | Int        |           |                | Fax:            |
|         | ernational |           | 800            | +1-208-246-6014 |
|         | Staff      |           | Independence   |                 |
|         |            |           | Ave SW         | Email:          |
|         | FAA        |           |                | leslie.mc       |
|         | Co-Chair   |           | Washington DC  | cormick@faa.gov |
|         |            |           | 20591 USA      |                 |
+---------+------------+-----------+----------------+-----------------+
| Might,  | Air        | FAA       | Oceanic        | PH:             |
| Carol   | Traffic    |           | Proc           | +1-202-267-7940 |
|         | Control    |           | edures/ATP-130 |                 |
|         | S          |           |                | Fax:            |
|         | pecialist, |           | 800            | +1-202-267-5110 |
|         | Oceanic    |           | Independence   |                 |
|         | Procedures |           | Ave SW         | Email:          |
|         |            |           |                | caro            |
|         |            |           | Washington DC  | l.might@faa.gov |
|         |            |           | 20591 USA      |                 |
+---------+------------+-----------+----------------+-----------------+
| Momii,  | Air        | Tokyo     | 1-12 Namiki    | PH:             |
| Yasuko  | Traffic    | Area      |                | +81-42-992-1317 |
|         | Controller | Control   | To             |                 |
|         |            | Center    | korozawa-city, | Fax:            |
|         |            |           | SAITAMA Pref   | +81-42-992-1195 |
|         |            |           |                |                 |
|         |            |           | 359-0042 Japan | Email:          |
+---------+------------+-----------+----------------+-----------------+
| Nakano, | Chief of   | JCAB      | 2-1-3          | PH:             |
| H       | operation  |           | Kasumigaseki   | +81-3-5253-8749 |
| iroyuki | section    |           | Chiyoda-ku     |                 |
|         |            |           |                | Fax:            |
|         |            |           | Tokyo,         | +81-3-5253-1663 |
|         |            |           | 100-8918,      |                 |
|         |            |           | Japan          | Email:          |
|         |            |           |                | nakano-         |
|         |            |           |                | h2rn@mlit.go.jp |
+---------+------------+-----------+----------------+-----------------+
| Nak     | Manager,   | Air       | K-1 Building   | PH:             |
| atsuji, | Planning   | Traffic   | 1-6-6          | +81-3-3747-1231 |
| Yoshiro |            | Control   | Han            |                 |
|         |            | Asso      | edakuko,Ota-ku | Fax:            |
|         |            | ciation - |                | +81-3-3747-0856 |
|         |            | Japan     | Tokyo,         |                 |
|         |            |           | 144-0041 Japan | Email:          |
|         |            |           |                | n               |
|         |            |           |                | aka@atcaj.or.jp |
+---------+------------+-----------+----------------+-----------------+
| Palmer, | Operations | Anchorage | 700 North      | PH:             |
| David   | Support    | ARTCC     | Boniface       | +1-907-269-1331 |
|         | Manager    |           | Parkway        |                 |
|         |            |           | Anchorage, AK, | Fax:            |
|         |            |           | 99645, USA     | +1-907-269-2580 |
|         |            |           |                |                 |
|         |            |           |                | Email:          |
|         |            |           |                | dave            |
|         |            |           |                | .palmer@faa.gov |
+---------+------------+-----------+----------------+-----------------+
| Ono,    | Special    | JCAB      | 2-1-3          | PH:             |
| Akira   | Assistant  |           | Kasumigaseki   | +81-3-5253-8749 |
|         | to the     |           | Chiyoda-ku     |                 |
|         | Director,  |           |                | Fax:            |
|         | ATC        |           | Tokyo,         | +81-3-5253-1663 |
|         | Division\  |           | 100-8918,      |                 |
|         | JCAB       |           | Japan          | Email:          |
|         | Co-Chair   |           |                | ono-            |
|         |            |           |                | a25d@mlit.go.jp |
+---------+------------+-----------+----------------+-----------------+
| Oseto,  |            | JCAB      | 2-1-3          | PH:             |
| Hideki  |            |           | Kasumigaseki   | +81-3-5253-8749 |
|         |            |           | Chiyoda-ku     |                 |
|         |            |           |                | Fax:            |
|         |            |           | Tokyo,         | +81-3-5253-1663 |
|         |            |           | 100-8918,      |                 |
|         |            |           | Japan          |                 |
+---------+------------+-----------+----------------+-----------------+
| Saji,   | Senior     | SITA      | SHIBA 1-choume | PH:             |
| Yasuo   | C          |           | Bldg. 8FL      | +81-3-3456-8188 |
|         | onsultant, |           |                |                 |
|         | Japan      |           | 1-12-7 Shiba,  | Fax:            |
|         | Aircraft   |           | Minato-ku,     | +81-3-3456-8190 |
|         | Comm       |           | Tokyo,         |                 |
|         | unications |           | 105-0014,      | Email:          |
|         |            |           | Japan          | yasuo           |
|         |            |           |                | .saji@sita.aero |
+---------+------------+-----------+----------------+-----------------+
| S       | CRA        | Boeing    | P.O. Box 3707, | PH:             |
| andell, |            |           | MC 02-98       | +1-425-294-0349 |
| Gordon  |            |           |                |                 |
|         |            |           | Seattle, WA    | Fax:            |
|         |            |           | 98124-2207 USA |                 |
|         |            |           |                | Email:          |
|         |            |           |                | Gordon.r.san    |
|         |            |           |                | dell@boeing.com |
+---------+------------+-----------+----------------+-----------------+
| Sladen, | Special    | FAA       | Oceanic        | PH:             |
| Reed    | Assistant  |           | IPT/AUA-600    | +1-510-745-3328 |
|         | -- Pacific |           |                |                 |
|         |            |           | Oakland ARTCC  | Fax:            |
|         |            |           |                | +1-510-745-3826 |
|         |            |           | 5125 Central   |                 |
|         |            |           | Avenue         | Email:          |
|         |            |           |                | reed.b          |
|         |            |           | Fremont, CA    | .sladen@faa.gov |
|         |            |           | 94536 USA      |                 |
+---------+------------+-----------+----------------+-----------------+
| Step    | Business   | SITA      | Level11,       | PH:             |
| henson, | Manager,   |           | Underwood      | +61-2-9240-1427 |
| Karen   | Air        |           | House, 37 Pitt |                 |
|         | Traffic    |           | Street,        | Fax:            |
|         | Services   |           | Sydney, NSW,   | +61-2-9247-9330 |
|         |            |           | 2000,          |                 |
|         |            |           | Australia      | Email:          |
|         |            |           |                | Karen.Steph     |
|         |            |           |                | enson@sita.aero |
+---------+------------+-----------+----------------+-----------------+
| Storm,  | Civi       | USAF      | Flight         | PH:             |
| Allan   | l/Military |           | Standards      | +1-240-857-2146 |
|         | Aviation   |           | Agency         |                 |
|         | Issues     |           |                | Fax:            |
|         |            |           | 1535 Command   | +1-240-857-3194 |
|         |            |           | Drive          |                 |
|         |            |           |                | Email:          |
|         |            |           | Suite D309     | Allan.storm     |
|         |            |           |                | @andrews.af.mil |
|         |            |           | Andrews Air    |                 |
|         |            |           | Force Base, MD |                 |
|         |            |           | 20762 USA      |                 |
+---------+------------+-----------+----------------+-----------------+
| Suzuki, | ATCA       | Air       | K-1 Building   | PH:             |
| Hiromi  | Associa    | Traffic   | 1-6-6          | +81-3-3747-1231 |
|         | te/CNS/ATM | Control   | Han            |                 |
|         | Specialist | As        | edakuko,Ota-ku | Fax:            |
|         |            | sociation |                | +81-3-3747-1231 |
|         |            | -- Japan  | Tokyo,         |                 |
|         |            |           | 144-0041 Japan | Email:          |
|         |            |           |                | cras            |
|         |            |           |                | a@cra-japan.org |
+---------+------------+-----------+----------------+-----------------+
| Suzuki, | Special    | JCAB      | 2-1-3          | PH:             |
| Yo      | Assistant  |           | Kasumigaseki   | +81-3-5253-8739 |
| shinori | to the     |           | Chiyoda-ku     |                 |
|         | Director,  |           |                | Fax:            |
|         | ATS        |           | Tokyo,         | +81-3-5253-1663 |
|         | Planning   |           | 100-8918,      |                 |
|         | Division   |           | Japan          | Email:          |
|         |            |           |                | suzuki-         |
|         |            |           |                | n2dr@mlit.go.jp |
+---------+------------+-----------+----------------+-----------------+
| Tak     | Special    | JCAB      | 2-1-3          | PH:             |
| ahashi, | Assistant  |           | Kasumigaseki   | +81-3-5253-8755 |
| Syuji   | to the     |           | Chiyoda-ku     |                 |
|         | Director,  |           |                | Fax:            |
|         | Radio      |           | Tokyo,         | +81-3-5253-1663 |
|         | E          |           | 100-8918,      |                 |
|         | ngineering |           | Japan          | Email:          |
|         | Division   |           |                | takahashi-      |
|         |            |           |                | s28g@mlit.go.jp |
+---------+------------+-----------+----------------+-----------------+
| Takan   | Repre      | ARINC     | Atago Green    | PH:             |
| ohashi, | sentative, |           | Hills Mori     | +81-3-5408-5423 |
| Seiichi | ARINC      |           | BLDG 25F,      |                 |
|         | Tokyo      |           | 2-5-1, Atago,  | Fax:            |
|         |            |           | Minato-ku,     |                 |
|         |            |           | Tokyo          | Email:          |
|         |            |           |                | takanoha        |
|         |            |           |                | shi@arinc.co.jp |
+---------+------------+-----------+----------------+-----------------+
| T       | Aviation   | FAA AFS   | 800            | PH:             |
| egeder, | Safety     | 400       | Independence   | +1-202-385-4581 |
| Robert  | Inspector  |           | Ave. SW        |                 |
|         |            |           |                | Fax:            |
|         |            |           | Flight         | +1-202-385-4653 |
|         |            |           | Technology     |                 |
|         |            |           | requirements   | Email:          |
|         |            |           |                | Robert.m.       |
|         |            |           | Branch,        | Tegeder@faa.gov |
|         |            |           | AFS-430        |                 |
|         |            |           |                |                 |
|         |            |           | Washington, DC |                 |
|         |            |           | 20591 USA      |                 |
+---------+------------+-----------+----------------+-----------------+
| Wada,   | ATC        | Tokyo     | 1-12 Namiki    | PH:             |
| H       | Oceanic    | Area      |                | +81-42-992-1317 |
| iroyuki | Specialist | Control   | To             |                 |
|         |            | Center    | korozawa-city, | Fax:            |
|         |            |           | SAITAMA Pref   | +81-42-992-1195 |
|         |            |           |                |                 |
|         |            |           | 359-0042 Japan | Email:          |
|         |            |           |                | h-              |
|         |            |           |                | wada@tacc.go.jp |
+---------+------------+-----------+----------------+-----------------+
| Wa      | Operating  | Tokyo     | 1-12 Namiki    | PH:             |
| tanabe, | Manager    | Area      |                | +81-42-992-1317 |
| Hideo   |            | Control   | To             |                 |
|         |            | Center    | korozawa-city, | Fax:            |
|         |            |           | SAITAMA Pref   | +81-42-992-1195 |
|         |            |           |                |                 |
|         |            |           | 359-0042 Japan | Email:          |
|         |            |           |                | hideo           |
|         |            |           |                | -wsj@tacc.go.jp |
+---------+------------+-----------+----------------+-----------------+
| Wiles,  | Manager,   | ARINC     | 6o11           | PH:             |
| Jerome  | Quality    |           | Industrial Way | +1-925-294-8400 |
|         | and        |           | Livermore, CA, |                 |
|         | Service    |           | 94551, USA     | Fax:            |
|         |            |           |                | +1-925-294-9597 |
|         |            |           |                |                 |
|         |            |           |                | Email:          |
|         |            |           |                | j               |
|         |            |           |                | wiles@arinc.com |
+---------+------------+-----------+----------------+-----------------+
| Yam     | Special    | JCAB      | 1-8-7          | PH:             |
| aguchi, | Assistant  |           | Haneda-kuko,   | +81-3-3747-0558 |
| Hideo   | to the     |           | Ohota-ku       |                 |
|         | Director   |           |                | Fax:            |
|         |            |           | Tokyo,         | 81-3-3747-0568  |
|         |            |           | 144-0041,      |                 |
|         |            |           | Japan          | Email:          |
|         |            |           |                | hideo@          |
|         |            |           |                | pop01.odn.ne.jp |
+---------+------------+-----------+----------------+-----------------+
| Yam     | Air        | JCAB      | 2-1-3          | PH:             |
| aguchi, | Traffic    |           | Kasumigaseki   | +81-3-5253-8111 |
| Satoshi | Controller |           | Chiyoda-ku     | ext. 51228      |
|         |            |           |                |                 |
|         |            |           | Tokyo,         | Fax:            |
|         |            |           | 100-8918,      | +81-3-5253-1663 |
|         |            |           | Japan          |                 |
|         |            |           |                | Email:          |
|         |            |           |                | yamaguchi-      |
|         |            |           |                | s2cp@mlit.go.jp |
+---------+------------+-----------+----------------+-----------------+

# Problem Reports received by CRASA-Japan

+----+------------------+------+------+--------------------+-----+----+
| PR | Problem Report   | #    | Air  | Comments           | Sta | D  |
| \# | Title            | # Re | or   | /Notes/Description | tus | is |
|    |                  | gion | Gr   |                    |     | cu |
|    |                  |      | ound |                    |     | ss |
|    |                  |      |      |                    |     | at |
|    |                  |      |      |                    |     | FI |
|    |                  |      |      |                    |     | T? |
+====+==================+======+======+====================+=====+====+
| 1  | Uplink to a      | N    | Ai   | Although DWLK      | W   | No |
| 01 | particular       | OPAC | r/Gr | arrived to ATSU,   | ait |    |
| 35 | aircraft failed  |      | ound | UPLK did not reach | ing |    |
|    | repeatedly       |      |      | an airplane.       |     |    |
+----+------------------+------+------+--------------------+-----+----+
| 1  | Uplink to a      | N    | Ai   | Although DWLK      | W   | No |
| 01 | particular       | OPAC | r/Gr | arrived to ATSU,   | ait |    |
| 36 | aircraft failed  |      | ound | UPLK did not reach | ing |    |
|    | repeatedly       |      |      | an airplane.       |     |    |
+----+------------------+------+------+--------------------+-----+----+
| 1  | CPDLC Message    | N    | Air  | A problem in the   | O   | No |
| 01 | Decode Error     | OPAC |      | avionics.          | pen |    |
| 37 |                  |      |      |                    |     |    |
+----+------------------+------+------+--------------------+-----+----+
| 1  | CPDLC Message    | N    | Air  | A problem in the   | O   | No |
| 01 | Decode Error     | OPAC |      | avionics.          | pen |    |
| 38 |                  |      |      |                    |     |    |
+----+------------------+------+------+--------------------+-----+----+
| 1  | Q5 RJCT from     | CE   | Air  | A problem in the   | W   | No |
| 01 | B747-400         | NPAC |      | avionics (ACARS    | ait |    |
| 39 |                  |      |      | MU-FMC Interface). | ing |    |
+----+------------------+------+------+--------------------+-----+----+
| 1  | Inappropriate    | N    | Air  | It is deemed       | O   | No |
| 01 | use of CPDLC     | OPAC |      | desirable to       | pen |    |
| 40 | DWLK free text   |      |      | review appropriate |     |    |
|    | message          | CE   |      | use of free text   |     |    |
|    |                  | NPAC |      | message.           |     |    |
+----+------------------+------+------+--------------------+-----+----+
| 1  | Inappropriate    | N    | Air  | It is deemed       | O   | No |
| 01 | use of CPDLC     | OPAC |      | desirable to       | pen |    |
| 41 | DWLK free text   |      |      | review appropriate |     |    |
|    | message          | CE   |      | use of free text   |     |    |
|    |                  | NPAC |      | message.           |     |    |
+----+------------------+------+------+--------------------+-----+----+
| 1  | Transfer Failure | N    | Gr   | DR1 was received   | W   | Y  |
| 01 |                  | OPAC | ound | after connection   | ait | es |
| 42 |                  |      |      | establishment at   | ing |    |
|    |                  |      |      | NEXT ATSU.         |     |    |
+----+------------------+------+------+--------------------+-----+----+
| 1  | DWLK Delay /     | N    | Gr   | DSP system failure | Re  | Y  |
| 01 | UPLK Failure     | OPAC | ound |                    | ady | es |
| 43 |                  |      |      |                    |     |    |
|    |                  | CE   |      |                    |     |    |
|    |                  | NPAC |      |                    |     |    |
+----+------------------+------+------+--------------------+-----+----+
| 1  | Inappropriate    | N    | Air  | It is deemed       | O   | No |
| 01 | use of CPDLC     | OPAC |      | desirable to       | pen |    |
| 44 | DWLK free text   |      |      | review appropriate |     |    |
|    | message          | CE   |      | use of free text   |     |    |
|    |                  | NPAC |      | message.           |     |    |
+----+------------------+------+------+--------------------+-----+----+
| 1  | Datalink failure | N    | Air  | A problem in the   | W   | Y  |
| 01 | with a           | OPAC |      | avionics (ACARS MU | ait | es |
| 45 | particular       |      |      | of BFE: Buyer      | ing |    |
|    | aircraft         | CE   |      | Furnished          |     |    |
|    |                  | NPAC |      | Equipment).        |     |    |
+----+------------------+------+------+--------------------+-----+----+
| 1  | Transfer Failure | CE   | Gr   | Since Media        | O   | Y  |
| 01 |                  | NPAC | ound | Advisory was not   | pen | es |
| 46 |                  |      |      | notified between   |     |    |
|    |                  |      |      | DSP                |     |    |
+----+------------------+------+------+--------------------+-----+----+
| 1  | UPLK Failure     | CE   | Ai   | Flying on the      | O   | Y  |
| 01 |                  | NPAC | r/Gr | fringe area of VHF | pen | es |
| 47 |                  |      | ound | coverage           |     |    |
+----+------------------+------+------+--------------------+-----+----+
| 1  | DWLK Delay /     | N    | Gr   | DSP system failure | Re  | Y  |
| 01 | UPLK Failure     | OPAC | ound |                    | ady | es |
| 48 |                  |      |      |                    |     |    |
|    |                  | CE   |      |                    |     |    |
|    |                  | NPAC |      |                    |     |    |
+----+------------------+------+------+--------------------+-----+----+
| 1  | Datalink failure | CE   | Air  | A problem in the   | W   | Y  |
| 01 | with a           | NPAC |      | avionics (ACARS MU | ait | es |
| 49 | particular       |      |      | of BFE).           | ing |    |
|    | aircraft         |      |      |                    |     |    |
+----+------------------+------+------+--------------------+-----+----+
| 1  | DWLK Delay /     | N    | Gr   | DSP system failure | Re  | Y  |
| 01 | UPLK Failure     | OPAC | ound |                    | ady | es |
| 50 |                  |      |      |                    |     |    |
|    |                  | CE   |      |                    |     |    |
|    |                  | NPAC |      |                    |     |    |
+----+------------------+------+------+--------------------+-----+----+
| 1  | DWLK Delay /     | N    | Gr   | DSP system failure | Re  | Y  |
| 01 | UPLK Failure     | OPAC | ound |                    | ady | es |
| 51 |                  |      |      |                    |     |    |
|    |                  | CE   |      |                    |     |    |
|    |                  | NPAC |      |                    |     |    |
+----+------------------+------+------+--------------------+-----+----+
| 1  | Datalink failure | N    | Air  | A problem in the   | W   | Y  |
| 01 | with a           | OPAC |      | avionics (ACARS MU | ait | es |
| 52 | particular       |      |      | of BFE).           | ing |    |
|    | aircraft         |      |      |                    |     |    |
+----+------------------+------+------+--------------------+-----+----+
| 1  | Transfer Failure | N    | Ai   | Human              | O   | Y  |
| 01 |                  | OPAC | r/Gr | /Machine/Procedure | pen | es |
| 53 |                  |      | ound | interface issue    |     |    |
+----+------------------+------+------+--------------------+-----+----+
| 1  | DWLK Delay /     | N    | Gr   | DSP system failure | Re  | Y  |
| 01 | UPLK Failure     | OPAC | ound |                    | ady | es |
| 54 |                  |      |      |                    |     |    |
|    |                  | CE   |      |                    |     |    |
|    |                  | NPAC |      |                    |     |    |
+----+------------------+------+------+--------------------+-----+----+
| 1  | DWLK Delay /     | N    | Gr   | DSP system failure | Re  | Y  |
| 01 | UPLK Failure     | OPAC | ound |                    | ady | es |
| 55 |                  |      |      |                    |     |    |
|    |                  | CE   |      |                    |     |    |
|    |                  | NPAC |      |                    |     |    |
+----+------------------+------+------+--------------------+-----+----+
| 1  | CPDLC Message    | N    | Air  | A problem in the   | O   | No |
| 01 | Decode Error     | OPAC |      | avionics.          | pen |    |
| 56 |                  |      |      |                    |     |    |
+----+------------------+------+------+--------------------+-----+----+
| 1  | > ATC Received   | N    | Ai   | Flying on the      | O   | No |
| 01 | > DSP\'s MAF in  | OPAC | r/Gr | fringe area of VHF | pen |    |
| 57 | > spite of       |      | ound | coverage           |     |    |
|    | > Reception of   |      |      |                    |     |    |
|    | > Aircraft       |      |      |                    |     |    |
|    | > Response       |      |      |                    |     |    |
+----+------------------+------+------+--------------------+-----+----+
| 1  | DWLK Delay /     | N    | Gr   | DSP system failure | O   | No |
| 01 | UPLK Failure     | OPAC | ound |                    | pen |    |
| 58 |                  |      |      |                    |     |    |
|    |                  | CE   |      |                    |     |    |
|    |                  | NPAC |      |                    |     |    |
+----+------------------+------+------+--------------------+-----+----+
| 1  | Incorrect        | CE   | Ai   | Response-DWLK via  | O   | Y  |
| 01 | message sequence | NPAC | r/Gr | SATCOM arrived to  | pen | es |
| 59 | via HFDL         |      | ound | ATSU earlier than  |     |    |
|    |                  |      |      | MAS of UPLK via    |     |    |
|    |                  |      |      | HFDL.              |     |    |
+----+------------------+------+------+--------------------+-----+----+
| 1  | ADS report       | CE   | Gr   | With character     | In  | No |
| 01 | received after a | NPAC | ound | strings of         | pr  |    |
| 60 | DIS reception    |      |      | "QTBQTBQTB" being  | ogr |    |
|    |                  |      |      | added to the last  | ess |    |
|    |                  |      |      | part of the        |     |    |
|    |                  |      |      | report.            |     |    |
+----+------------------+------+------+--------------------+-----+----+
| 1  | Datalink failure | N    | Air  | A problem in the   | W   | Y  |
| 01 | with a           | OPAC |      | avionics (ACARS MU | ait | es |
| 61 | particular       |      |      | of BFE).           | ing |    |
|    | aircraft         | CE   |      |                    |     |    |
|    |                  | NPAC |      |                    |     |    |
+----+------------------+------+------+--------------------+-----+----+
| 1  | DWLK Delay /     | N    | Gr   | DSP system failure | Re  | Y  |
| 01 | UPLK Failure     | OPAC | ound |                    | ady | es |
| 62 |                  |      |      |                    |     |    |
|    |                  | CE   |      |                    |     |    |
|    |                  | NPAC |      |                    |     |    |
+----+------------------+------+------+--------------------+-----+----+
| 1  | Same content     | CE   | Air  | A problem in the   | W   | No |
| 01 | CPDLC message    | NPAC |      | avionics.          | ait |    |
| 63 | was received     |      |      |                    | ing |    |
|    | repeatedly down  |      |      |                    |     |    |
|    | linked           |      |      |                    |     |    |
+----+------------------+------+------+--------------------+-----+----+
| 1  | DWLK Delay /     | N    | Gr   | DSP system failure | Re  | Y  |
| 01 | UPLK Failure     | OPAC | ound |                    | ady | es |
| 64 |                  |      |      |                    |     |    |
|    |                  | CE   |      |                    |     |    |
|    |                  | NPAC |      |                    |     |    |
+----+------------------+------+------+--------------------+-----+----+
| 1  | DWLK Delay /     | N    | Gr   | DSP system failure | Re  | Y  |
| 01 | UPLK Failure     | OPAC | ound |                    | ady | es |
| 65 |                  |      |      |                    |     |    |
|    |                  | CE   |      |                    |     |    |
|    |                  | NPAC |      |                    |     |    |
+----+------------------+------+------+--------------------+-----+----+
| 1  | Transfer Failure | N    | Ai   | Human              | O   | Y  |
| 01 |                  | OPAC | r/Gr | /Machine/Procedure | pen | es |
| 66 |                  |      | ound | interface issue    |     |    |
+----+------------------+------+------+--------------------+-----+----+
| 1  | Incorrect        | CE   | Ai   | Response-DWLK via  | O   | Y  |
| 01 | message sequence | NPAC | r/Gr | SATCOM arrived to  | pen | es |
| 67 | via HFDL         |      | ound | ATSU earlier than  |     |    |
|    |                  |      |      | MAS of UPLK via    |     |    |
|    |                  |      |      | HFDL.              |     |    |
+----+------------------+------+------+--------------------+-----+----+
| 1  | ADS Periodic     | N    | Ai   |                    | In  | No |
| 01 | Report down      | OPAC | r/Gr |                    | pr  |    |
| 68 | linked one hour  |      | ound |                    | ogr |    |
|    | late.            |      |      |                    | ess |    |
+----+------------------+------+------+--------------------+-----+----+
| 1  | Duplicated       | N    | Gr   | Incorrect          | O   | Y  |
| 01 | reception of ACK | OPAC | ound | interface message  | pen | es |
| 69 | and NAK in       |      |      | from DSP-X to      |     |    |
|    | response to an   |      |      | DSP-Y              |     |    |
|    | ADS request      |      |      |                    |     |    |
+----+------------------+------+------+--------------------+-----+----+
| 1  | DWLK Delay /     | N    | Gr   | DSP system failure | Re  | Y  |
| 01 | UPLK Failure     | OPAC | ound |                    | ady | es |
| 70 |                  |      |      |                    |     |    |
|    |                  | CE   |      |                    |     |    |
|    |                  | NPAC |      |                    |     |    |
+----+------------------+------+------+--------------------+-----+----+
| 1  | Connection       | CE   | Air  | This event was     | Re  | Y  |
| 01 | Failure          | NPAC |      | caused by an       | ady | es |
| 71 |                  |      |      | incorrect REG down |     |    |
|    |                  |      |      | linked based upon  |     |    |
|    |                  |      |      | an erroneous crew  |     |    |
|    |                  |      |      | entry.             |     |    |
+----+------------------+------+------+--------------------+-----+----+
| 1  | Downlink Failure | N    | Ai   |                    | In  | No |
| 01 |                  | OPAC | r/Gr |                    | pr  |    |
| 72 |                  |      | ound |                    | ogr |    |
|    |                  |      |      |                    | ess |    |
+----+------------------+------+------+--------------------+-----+----+
| 1  | Same content     | N    | Air  | A problem in the   | In  | Y  |
| 01 | CPDLC message    | OPAC |      | avionics.          | pr  | es |
| 73 | was received     |      |      |                    | ogr |    |
|    | repeatedly down  |      |      |                    | ess |    |
|    | linked           |      |      |                    |     |    |
+----+------------------+------+------+--------------------+-----+----+

# 

# Problem Reports received by FAA CRASA

+---+------------------+------+------+---------------------+----+----+
| P | Problem Report   | #    | Air  | Comment             | St | D  |
| R | Title            | # Re | or   | s/Notes/Description | at | is |
| \ |                  | gion | Gr   |                     | us | cu |
| # |                  |      | ound |                     |    | ss |
|   |                  |      |      |                     |    | at |
|   |                  |      |      |                     |    | FI |
|   |                  |      |      |                     |    | T? |
+===+==================+======+======+=====================+====+====+
| 4 | Messages stay in | N    | Airp | The following       | R  | Y  |
| 3 | SENDING and      | OPAC | lane | report was received | ea | es |
| 2 | appear not to be |      |      | from an operator:   | dy |    |
|   | sent             |      |      |                     | f  |    |
|   |                  |      |      | When sending, the   | or |    |
|   |                  |      |      | acceptance of a     | F  |    |
|   |                  |      |      | CPDLC message the   | IT |    |
|   |                  |      |      | CDU (L and R) seems |    |    |
|   |                  |      |      | to get stuck on the |    |    |
|   |                  |      |      | \"SENDING\" phase   |    |    |
|   |                  |      |      | and then fails to   |    |    |
|   |                  |      |      | send at all,        |    |    |
|   |                  |      |      | resulting in        |    |    |
|   |                  |      |      | \"OPEN\" messages.  |    |    |
|   |                  |      |      |                     |    |    |
|   |                  |      |      | This also occurred  |    |    |
|   |                  |      |      | in the previous     |    |    |
|   |                  |      |      | FIR.                |    |    |
+---+------------------+------+------+---------------------+----+----+
| 4 | Connect Request  | N    | Airp | A report was        | In | \- |
| 3 | After HX Reject  | OPAC | lane | received indicating | pr |    |
| 3 | Gets Connect     |      |      | that on 3 November  | og |    |
|   | Confirm But No   |      |      | 2002, a 747-400 had | re |    |
|   | Connection       |      |      | experienced a       | ss |    |
|   |                  |      |      | problem in logging  |    |    |
|   |                  |      |      | on to one ATSU      |    |    |
|   |                  |      |      | after disconnecting |    |    |
|   |                  |      |      | from the previous   |    |    |
|   |                  |      |      | one.                |    |    |
|   |                  |      |      |                     |    |    |
|   |                  |      |      | The Logon showed    |    |    |
|   |                  |      |      | SENT and then       |    |    |
|   |                  |      |      | nothing until a     |    |    |
|   |                  |      |      | RE-LOGON TO ATC     |    |    |
|   |                  |      |      | COMM scratchpad     |    |    |
|   |                  |      |      | message. They tried |    |    |
|   |                  |      |      | several logons with |    |    |
|   |                  |      |      | other centers, all  |    |    |
|   |                  |      |      | failed.             |    |    |
+---+------------------+------+------+---------------------+----+----+
| 4 | AOC Position     | N    | Airp | On 747-400, if the  | R  | Y  |
| 3 | Report Sent      | OPAC | lane | operator has set    | ea | es |
| 6 | Before ADS       |      |      | the FMS up to       | dy |    |
|   | Waypoint Change  |      |      | transmit company    | f  |    |
|   | Event Report     |      |      | (AOC) position      | or |    |
|   |                  |      |      | reports             | F  |    |
|   |                  |      |      | automatically on    | IT |    |
|   |                  |      |      | sequencing          |    |    |
|   |                  |      |      | specified           |    |    |
|   |                  |      |      | waypoints, they     |    |    |
|   |                  |      |      | will be triggered   |    |    |
|   |                  |      |      | before the ADS      |    |    |
|   |                  |      |      | waypoint change     |    |    |
|   |                  |      |      | event report for    |    |    |
|   |                  |      |      | the same waypoint.  |    |    |
|   |                  |      |      |                     |    |    |
|   |                  |      |      | As an example, for  |    |    |
|   |                  |      |      | ZK-NBW on 3         |    |    |
|   |                  |      |      | November 2002, the  |    |    |
|   |                  |      |      | AOC position report |    |    |
|   |                  |      |      | at 00:42:40 was     |    |    |
|   |                  |      |      | initiated before    |    |    |
|   |                  |      |      | the corresponding   |    |    |
|   |                  |      |      | ADS waypoint change |    |    |
|   |                  |      |      | event report. The   |    |    |
|   |                  |      |      | AOC report was      |    |    |
|   |                  |      |      | itself delayed by 8 |    |    |
|   |                  |      |      | seconds (compared   |    |    |
|   |                  |      |      | to its time stamp)  |    |    |
|   |                  |      |      | for some unknown    |    |    |
|   |                  |      |      | reason, so the ADS  |    |    |
|   |                  |      |      | report was 15       |    |    |
|   |                  |      |      | seconds old before  |    |    |
|   |                  |      |      | it was received on  |    |    |
|   |                  |      |      | the ground.         |    |    |
+---+------------------+------+------+---------------------+----+----+
| 4 | Airplane lost    | NO   | Airp | Two reports have    | Op | Y  |
| 3 | CPDLC and ADS    | PAC\ | lane | been received of    | en | es |
| 7 | when             | S    |      | 747-400 airplanes   |    |    |
|   | transitioning to | OPAC |      | belonging to one    |    |    |
|   | SATCOM           |      |      | airline losing      |    |    |
|   |                  |      |      | CPDLC and ADS when  |    |    |
|   |                  |      |      | transitioning to    |    |    |
|   |                  |      |      | SATCOM. Uplinks     |    |    |
|   |                  |      |      | appear to be        |    |    |
|   |                  |      |      | accepted (message   |    |    |
|   |                  |      |      | assurance           |    |    |
|   |                  |      |      | received), and the  |    |    |
|   |                  |      |      | airplane is able to |    |    |
|   |                  |      |      | send company        |    |    |
|   |                  |      |      | messages via        |    |    |
|   |                  |      |      | SATCOM. On          |    |    |
|   |                  |      |      | returning to VHF    |    |    |
|   |                  |      |      | coverage, datalink  |    |    |
|   |                  |      |      | operation is        |    |    |
|   |                  |      |      | resumed, beginning  |    |    |
|   |                  |      |      | with an old message |    |    |
|   |                  |      |      | (the first that     |    |    |
|   |                  |      |      | should have been    |    |    |
|   |                  |      |      | sent after the VHF  |    |    |
|   |                  |      |      | to SATCOM           |    |    |
|   |                  |      |      | transition)         |    |    |
+---+------------------+------+------+---------------------+----+----+
| 4 | Legitimate but   | C    | Air  | A 777 operator has  | Op | Y  |
| 4 | wrong next + one | EPAC |      | reported several    | en | es |
| 1 | positions        |      |      | occurrences of      |    |    |
|   |                  | S    |      | CPDLC Position      |    |    |
|   |                  | OPAC |      | Reports being sent  |    |    |
|   |                  |      |      | that contained      |    |    |
|   |                  |      |      | wrong idents in the |    |    |
|   |                  |      |      | fix next plus one   |    |    |
|   |                  |      |      | field. In all       |    |    |
|   |                  |      |      | cases, the fix was  |    |    |
|   |                  |      |      | a legitimate fix,   |    |    |
|   |                  |      |      | but not in the      |    |    |
|   |                  |      |      | aircraft\'s route.  |    |    |
+---+------------------+------+------+---------------------+----+----+

+---+-----------------------------+-----------+--------------+---------+
|   | ***Capacity                 | ***Action | ***Action    | ***Date |
|   | Enhancement/Action          | with***   | Due***       | Compl   |
|   | Required***                 |           |              | eted*** |
+===+=============================+===========+==============+=========+
|   | **[Implement Reduced        |           |              |         |
|   | Vertical                    |           |              |         |
|   | Separation]{.smallcaps}**   |           |              |         |
+---+-----------------------------+-----------+--------------+---------+
|   | Implement RVSM FL290-390    | FAA/JCAB  |              | 24 Feb  |
|   |                             |           |              | 2000    |
+---+-----------------------------+-----------+--------------+---------+
|   | Expand RVSM FL390-410       | FAA/JCAB  |              | 5 Oct   |
|   |                             |           |              | 2000    |
+---+-----------------------------+-----------+--------------+---------+
|   | # [Implement 50NM Late      |           |              |         |
|   | ral Separation]{.smallcaps} |           |              |         |
+---+-----------------------------+-----------+--------------+---------+
|   | #                           | FAA/JCAB  |              | Apr     |
|   |   Implement on NOPAC routes |           |              | 1998    |
+---+-----------------------------+-----------+--------------+---------+
|   | #  Imp                      | Anchorage |              | 3 Dec   |
|   | lement on NOPAC transitions | ARTCC     |              | 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     |              |         |
+---+-----------------------------+-----------+--------------+---------+
|   | #                           | Tokyo     |              | 21 Feb  |
|   |   Complete software changes | ACC/ JCAB |              | 2002    |
+---+-----------------------------+-----------+--------------+---------+
|   | #  Complete weather devi    | FAA       |              | 6 Feb   |
|   | ation analysis south of 30N |           |              | 2002    |
+---+-----------------------------+-----------+--------------+---------+
|   | # Sufficie                  | Airlines  |              | 6 Feb   |
|   | nt aircraft RNP-10 approved |           |              | 2002    |
+---+-----------------------------+-----------+--------------+---------+
|   | #                           |           |              |         |
|   |   [Implement 50NM Longitudi |           |              |         |
|   | nal Separation]{.smallcaps} |           |              |         |
+---+-----------------------------+-----------+--------------+---------+
|   | #  Amend Doc 7030 to p      | JCAB/FAA  | 2004         |         |
|   | ermit application in Tokyo/ |           |              |         |
|   | Naha/Oakland/Anchorage FIRs |           |              |         |
+---+-----------------------------+-----------+--------------+---------+
|   | Replace CPDLC waypoint      | JCAB      | Late 2003    |         |
|   | reporting with ADS waypoint |           |              |         |
|   | reporting within Tokyo FIR  |           |              |         |
+---+-----------------------------+-----------+--------------+---------+
|   | Replace CPDLC waypoint      | # FAA     | Oct 2004     |         |
|   | reporting with ADS waypoint |           |              |         |
|   | reporting within Anchorage  |           |              |         |
|   | FIR                         |           |              |         |
+---+-----------------------------+-----------+--------------+---------+
|   | #  Implement for            | JCAB      | Late 2003    |         |
|   |  climb/descent in Tokyo FIR |           |              |         |
+---+-----------------------------+-----------+--------------+---------+
|   | #  Implement for c          | FAA       | TBD          |         |
|   | limb/descent in Oakland FIR |           |              |         |
+---+-----------------------------+-----------+--------------+---------+
|   | #  Implement for cruise     | FAA/JCAB  | ## TBD       |         |
+---+-----------------------------+-----------+--------------+---------+
|   | #  Complete/eval            | Tokyo     | 2004         |         |
|   | uate ODP-3 software changes | ACC/ JCAB |              |         |
+---+-----------------------------+-----------+--------------+---------+
|   | # [Implement 30NM Late      |           | On hold      |         |
|   | ral Separation]{.smallcaps} |           |              |         |
+---+-----------------------------+-----------+--------------+---------+
|   | # [Implement 30NM Longitudi |           | On hold      |         |
|   | nal Separation]{.smallcaps} |           |              |         |
+---+-----------------------------+-----------+--------------+---------+
|   | **[Implement Tracks 14/15   |           |              |         |
|   | HKG/TPE to/from             |           |              |         |
|   | LAX/SFO]{.smallcaps}**      |           |              |         |
+---+-----------------------------+-----------+--------------+---------+
|   | #  Conduct trials           | ATFMC     |              | 7 Sep   |
|   |                             |           |              | 2001    |
+---+-----------------------------+-----------+--------------+---------+
|   | #  Provide                  | Airlines  |              | 7 Sep   |
|   | data on use of Tracks 14/15 |           |              | 2001    |
|   |  and impact to Tracks 11/12 |           |              |         |
+---+-----------------------------+-----------+--------------+---------+
|   | **[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          |         |
+---+-----------------------------+-----------+--------------+---------+

+------+----------------+----------+---------------------------------+
| Ac   | *              | **Res    | **Status and Action to be       |
| tion | *Description** | ponsible | taken**                         |
| Item |                | Office** |                                 |
+======+================+==========+=================================+
| IP/  | Application of | ICAO     | ICAO submitted questions to the |
| 11-2 | a 10- minute   |          | FAA regarding the proposed      |
|      | longitudinal   |          | amendment to Doc 7030. Those    |
|      | separation     |          | questions have been answered.   |
|      | minimum        |          | Awaiting approval by ICAO.      |
|      | without the    |          |                                 |
|      | mandatory      |          |                                 |
|      | application of |          |                                 |
|      | Mach Number.   |          |                                 |
+------+----------------+----------+---------------------------------+
| IP/  | International  | FAA      | JCAB ATFMC and FAA ATCSCC are   |
| 11-3 | Air Traffic    |          | checking the "hotline" circuit  |
|      | Flow           | JCAB     | monthly to ensure it will be    |
|      | Management.    |          | available if required. FAA and  |
|      |                |          | JCAB are also working to        |
|      |                |          | establish an agreement to       |
|      |                |          | exchange Enhanced Traffic       |
|      |                |          | Management System (ETMS) data.  |
|      |                |          | The meeting will be kept        |
|      |                |          | informed of developments in the |
|      |                |          | area of ATFM.                   |
+------+----------------+----------+---------------------------------+
| IP/  | Elimination of | FAA      | Oakland ARTCC requested that    |
| 12-2 | verbal         |          | this be put on hold until the   |
|      | coordination   | JCAB     | implementation of ATOP. Will    |
|      | that is        |          | consider re-opening at that     |
|      | currently      |          | time. **CLOSED**.               |
|      | required in    |          |                                 |
|      | addition to    |          |                                 |
|      | AIDC           |          |                                 |
|      | coordination   |          |                                 |
|      | between        |          |                                 |
|      | Oakland ARTCC  |          |                                 |
|      | and Tokyo ACC  |          |                                 |
+------+----------------+----------+---------------------------------+
| IP/  | Expansion of   | ICAO     | An AIC was published with       |
| 13-3 | Russian Routes |          | details for a demonstration on  |
|      |                | FAA      | Polar Route 4 between 7 Aug and |
|      |                |          | 27 Nov 2003. Polar Route 4 has  |
|      |                | JCAB     | been given an ICAO ATS route    |
|      |                |          | designator and operation will   |
|      |                |          | begin 27 Nov 03. It will be     |
|      |                |          | linked to the A204 route. The   |
|      |                |          | meeting will be kept informed   |
|      |                |          | of developments in this area.   |
+------+----------------+----------+---------------------------------+
| IP/  | Explore the    | JCAB     | JCAB intends to implement 50NM  |
| 13-4 | implementation |          | longitudinal separation with    |
|      | of 50NM ADS    | FAA      | the commissioning of MTSAT-1R.  |
|      | longitudinal   |          | JCAB will report on the status  |
|      | separation     |          | to IPACG/20.                    |
|      | minimum in the |          |                                 |
|      | North Pacific  |          |                                 |
|      | area           |          |                                 |
+------+----------------+----------+---------------------------------+
| IP/  | Consider the   | FAA      | JCAB reported on the outcome of |
| 14-1 | need for       |          | their study in FY2002 to        |
|      | contingency    | JCAB     | clarify the need for            |
|      | plans          |          | establishing a contingency plan |
|      |                |          | for ATC activities and provided |
|      |                |          | information on the fundamental  |
|      |                |          | elements of a bilateral oceanic |
|      |                |          | contingency plan. JCAB will     |
|      |                |          | continue studies and seek input |
|      |                |          | from IPACG as required.         |
+------+----------------+----------+---------------------------------+
| IP/  | Remove         | FAA      | The trial was successful and    |
| 17-1 | city-pair      |          | JCAB ATFMC and FAA would like   |
|      | restriction on | JCAB     | to consider the possibility of  |
|      | Tracks 2/3 and |          | formalizing this before         |
|      | 14/15          |          | IPACG/20.                       |
+------+----------------+----------+---------------------------------+
| IP/  | Examine ways   | JCAB     | IATA raised this issue at the   |
| 17-2 | to enhance     |          | ATS/AIS/SAR/SG. Further         |
|      | airspace       |          | information will be reported at |
|      | capacity for   |          | IPACG/20.                       |
|      | aircraft       |          |                                 |
|      | departing      |          |                                 |
|      | HKG/TPE and    |          |                                 |
|      | entering       |          |                                 |
|      | Tokyo/Naha     |          |                                 |
|      | FIRs bound for |          |                                 |
|      | North America  |          |                                 |
+------+----------------+----------+---------------------------------+
| IP/  | Consider       | FAA      | Preliminary work has been       |
| 17-3 | whether the    |          | completed on this scenario      |
|      | application of | JCAB     | under the NPACE Study and was   |
|      | a "high        |          | presented to the meeting. Early |
|      | speed/low      |          | simulations indicate that there |
|      | speed" route   |          | are potential fuel savings by   |
|      | philosophy     |          | establishing high speed/low     |
|      | would be of    |          | speed tracks. Further           |
|      | benefit to     |          | refinement of the modeling to   |
|      | users.         |          | continue. Update to be provided |
|      |                |          | to IPACG/20.                    |
+------+----------------+----------+---------------------------------+
| IP/  | Implement      | ICAO     | FAA reported that the SASP WG   |
| 17-4 | lateral offset |          | had agreed to revise the State  |
|      | procedures in  | FAA      | Letter to include use of a 2NM  |
|      | the North and  |          | offset in a 50NM lateral        |
|      | Central        |          | environment and to evaluate use |
|      | Pacific.       |          | of the 2NM lateral offset in a  |
|      |                |          | 30NM lateral environment with   |
|      |                |          | GNSS-equipped aircraft. Once    |
|      |                |          | the revised State letter is     |
|      |                |          | published, FAA will propose     |
|      |                |          | application of the 2NM offset   |
|      |                |          | for the Pacific Region. If the  |
|      |                |          | safety analysis on crossing     |
|      |                |          | tracks proves acceptable and    |
|      |                |          | ICAO guidelines are amended,    |
|      |                |          | JCAB would accept the 2NM       |
|      |                |          | lateral offset to harmonize     |
|      |                |          | procedures across the Pacific   |
|      |                |          | Region. Further discussions to  |
|      |                |          | be held with South Pacific      |
|      |                |          | States during IPACG/20.         |
+------+----------------+----------+---------------------------------+
| IP/  | Evaluate       | FAA      | FAA presented an updated        |
| 17-5 | current lost   |          | amendment to Doc 7030 lost      |
|      | communications | ICAO     | communications procedures based |
|      | procedures     |          | on discussions at ISPACG and    |
|      |                |          | ATS/AIS/SAR/SG. A further       |
|      |                |          | change to state that this       |
|      |                |          | procedure is for a *total loss  |
|      |                |          | of communications* and a        |
|      |                |          | re-sequencing of actions to be  |
|      |                |          | taken by the pilot were agreed  |
|      |                |          | and will be presented to        |
|      |                |          | APANPIRG/14. Any comments       |
|      |                |          | proposed by APANPIRG/14 will be |
|      |                |          | considered and the FAA will     |
|      |                |          | submit the proposed amendment   |
|      |                |          | to ICAO. Status to be reported  |
|      |                |          | to IPACG/20. Once the Doc 7030  |
|      |                |          | amendment is approved,          |
|      |                |          | consideration will be given to  |
|      |                |          | proposing a corresponding       |
|      |                |          | change to Annex 11 in order to  |
|      |                |          | provide for global              |
|      |                |          | harmonization of lost           |
|      |                |          | communications procedures.      |
+------+----------------+----------+---------------------------------+
| IP/  | Monitor the    | FAA      | FAA and JCAB have been          |
| 18-1 | work of the    |          | represented at the Task Force   |
|      | Asia Pacific   | JCAB     | meetings. JCAB provided an      |
|      | Airspace       |          | update to this meeting. The     |
|      | Safety         |          | work of the APASM/TF is         |
|      | Monitoring     |          | complete and recommendations    |
|      | Task Force to  |          | will be presented to            |
|      | establish a    |          | APANPIRG/14. **CLOSED**.        |
|      | regional       |          |                                 |
|      | airspace       |          |                                 |
|      | safety         |          |                                 |
|      | monitoring     |          |                                 |
|      | agency.        |          |                                 |
+------+----------------+----------+---------------------------------+
| IP/  | Implement      | JCAB     | No update was available.        |
| 18-2 | flight         |          | Progress to be reported at      |
|      | re-routing     | FAA      | IPACG/20.                       |
|      | between Japan  |          |                                 |
|      | and Hawaii     |          |                                 |
|      | tracks.        |          |                                 |
+------+----------------+----------+---------------------------------+
| IP/  | Remove of time | FAA      | JCAB and FAA agreed that the    |
| 18-3 | restrictions   |          | trial has been successful thus  |
|      | for PACOTS     | JCAB     | far and will be completed on 13 |
|      | Track A.       |          | Sept. FAA will present the      |
|      |                |          | outcome of the trial and        |
|      |                |          | recommend permanent procedures  |
|      |                |          | to IPACG/20. JCAB will consider |
|      |                |          | whether further reductions are  |
|      |                |          | possible and present            |
|      |                |          | recommendations to IPACG/20     |
+------+----------------+----------+---------------------------------+
| IP/  | Consider       | FAA      | Although the idea of a          |
| 18-4 | whether the    |          | segregated route had been       |
|      | application of | JCAB     | rejected in the past, it was    |
|      | a "segregated" |          | agreed that there would be      |
|      | route          |          | value in developing a scenario  |
|      | philosophy     |          | involving a mixed environment   |
|      | would be of    |          | for evaluation using the NPACE  |
|      | benefit to     |          | model. Relevant parties are to  |
|      | users.         |          | provide information for the     |
|      |                |          | simulation to the FAA Technical |
|      |                |          | Center. Preliminary results     |
|      |                |          | will be made available to       |
|      |                |          | IPACG/20. A "preferred route"   |
|      |                |          | philosophy for eastbound routes |
|      |                |          | will be discussed at IPACG/20.  |
+------+----------------+----------+---------------------------------+
| IP/  | Develop ATC    |          | JCAB identified a need to       |
| 19-1 | contingency    |          | develop contingency procedures  |
|      | procedures to  |          | in the event of a loss of data  |
|      | be used during |          | link communication prior to     |
|      | a failure of   |          | implementing 50NM longitudinal  |
|      | satellite      |          | separation. A task force led by |
|      | datalink       |          | Yoshiki Imawaka and Carol Might |
|      |                |          | will draft procedures to be     |
|      |                |          | presented at IPACG/20.          |
+------+----------------+----------+---------------------------------+
| IP/  | Add altitudes  |          | FAA proposed that the           |
| 19-2 | on G344 and    |          | additional altitudes of FL350,  |
|      | R591           |          | FL370, FL390, and FL410 be      |
|      |                |          | available on G344 and R591,     |
|      |                |          | when designated as PACOTS       |
|      |                |          | track(s), without verbal        |
|      |                |          | coordination of inappropriate   |
|      |                |          | altitude for direction of       |
|      |                |          | flight. JCAB further requested  |
|      |                |          | the use of flight levels lower  |
|      |                |          | than FL340 without              |
|      |                |          | coordination. Anchorage ARTCC   |
|      |                |          | and Tokyo ACC will make         |
|      |                |          | arrangements for a trial and    |
|      |                |          | report to IPACG/20.             |
+------+----------------+----------+---------------------------------+
| IP/  | Develop a      | FAA      | Oakland ARTCC presented         |
| 19-3 | means to       |          | information on the frequency of |
|      | reduce         | JCAB     | missed waypoint position        |
|      | position       |          | reports by pilots. Tokyo ACC    |
|      | reporting      |          | reported on a study that        |
|      | deficiencies   |          | confirmed this to be a problem. |
|      |                |          | FAA agreed to take action to    |
|      |                |          | make airlines aware of this     |
|      |                |          | problem. Further analysis will  |
|      |                |          | be done by both facilities and  |
|      |                |          | an updated report will be       |
|      |                |          | presented at IPACG/20.          |
+------+----------------+----------+---------------------------------+