Summary of Discussions
Download 363.88 Kb.
|
- Navigate this page:
- 3.0 Agenda Item 1: Review and Approve Agenda
Summary of DiscussionsTwenty-Third Meeting of the Informal Pacific Air Traffic Control Coordination Group (IPACG/23) 11-15 July 2005; Tokyo, Japan
1.1 The Twenty-Third Meeting of the Informal Pacific Air Traffic Control (ATC) Coordinating Group (IPACG/23) was held at the Koku kaikan in Tokyo, Japan, from 11-15 July 2005. The IPACG was established to provide a forum for air traffic service (ATS) providers and airspace users to informally meet and explore solutions to near term ATC problems that limit the capacity or efficiency within the Anchorage, Oakland, and Tokyo Flight Information Regions (FIRs).
2.1 The meeting was co-chaired by Mr. Shigeru Kunitake 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. Kunitake welcomed the participants on behalf of the JCAB Director of ATC Division and thanked them for taking part in the IPACG discussions. He apologized for the delay in distributing the working and information papers. He noted that they will be posted on the IPACG website along with the final report. Mr. Kunitake further stated that although time is limited, he looks forward to intensive discussions during the week. 2.3 Ms. McCormick stated she was pleased to be back with friends and colleagues from IPACG. She thanked Mr. Kunitake and his staff, as well as all the others who helped prepare for this meeting. Ms. McCormick noted that this is a time of much change, both for JCAB and FAA. JCAB is transitioning to the new Air Traffic Management Center (ATMC) and preparing for new procedures based on the availability of Multi-Functional Transport Satellite (MTSAT), and FAA is similarly in the final stages of implementing the new oceanic automation system, Ocean21, and preparing to take advantage of automatic dependent surveillance (ADS) technology to provide reduced separation. The FAA Air Traffic Organization is also focusing on providing a safe and more efficient operating environment for all of our domestic and international customers, and we appreciate this opportunity for an exchange with our airspace users’ ideas on how we can best do this. We look forward to a productive meeting. 2.4 Mr. Kunitake recognized Mr. Reed Sladen of the FAA and Mr. Hideo Watanabe of the JCAB and thanked them for their leadership of the 10th Meeting of the FANS Interoperability Team (FIT/10). 3.0 Agenda Item 1: Review and Approve Agenda3.1 The following agenda was adopted by the meeting: Agenda Item 1 Review and approve agenda Agenda Item 2 Air Traffic Management (ATM) Issues Agenda Item 3 Communications/Navigation/Surveillance (CNS) Issues Agenda Item 4 Report on the outcome of the FANS Interoperability Team (FIT) Meeting Agenda Item 5 Review and update of CNS/ATM Planning Chart Agenda Item 6 Evaluation of costs and benefits Agenda Item 7 Other business 4.0 Submitted Papers 4.1 The following working and information papers were presented to IPACG/23 and are available on the IPACG website http://www.faa.gov/ats/ato/ipacg.htm.
5.0 Agenda Items 2 & 3: ATM and CNS Issues Status of Advanced Technologies and Oceanic Procedures (ATOP)/Ocean21 System Implementation 5.1 The FAA provided an overall status update on the deployment and implementation of the Ocean21 system. FAA is on schedule to meet 30NM lateral/30NM longitudinal separation (30/30) commitments at the end of 2005. Oakland Air Route Traffic Control Center (ARTCC) transition from the Oceanic Display and Planning System (ODAPS) to Ocean21 is now projected to begin 18 October 2005/0500UTC and will last 48 hours, during which two sectors will be transitioned at a time, approximately 4 hours apart. For 48 hours, the ODAPS control room will shadow Ocean21 to allow rapid reversion to the legacy system, if required. 5.2 Anchorage ARTCC is projected to declare Ocean21 Initial Operational Capability in March 2006. New York ARTCC transitioned to Ocean21 on 6 June 2005 and has experienced some anomalies but, through the efforts of New York ARTCC controllers and the FAA Technical Center, they have been able to remain operational on Ocean21 and not revert back to the legacy system. JCAB expressed their hopes for Oakland ARTCC’s successful transition to Ocean21. Interim ATS Inter-facility Data Communication (AIDC) Function between Tokyo Area Control Center (ACC) Oceanic Data Processing (ODP) System and Oakland ARTCC Ocean21 5.3 Oakland ARTCC presented information on the interim AIDC interface developed to support a legacy AIDC message service between the Oakland ARTCC Ocean21 system and the Tokyo ACC Oceanic Data Processing (ODP) system. The AIDC service between Oakland ARTCC and Tokyo ACC was initiated in 1998 based on Version 1 of the Asia/Pacific AIDC Interface Control Document (ICD). As a result of this cooperation, the first automated data interface between international flight information regions (FIRs) has run successfully for over 7 years. Ocean21 will replace all subsystems, including AIDC, but will not support the unique system that has been developed between Oakland ARTCC and Tokyo ACC. 5.4 Therefore, FAA has developed a “translator” that is in the Ocean21 – ODP system data path, and will deploy a system called AIDC – Tokyo (AIDC-T). The FAA has ported the current AIDC software to the new platform and modified the code so that it can maintain the currently deployed reduced message set and functionality. The functional requirement for AIDC-T is that it will present an interface to the Tokyo ODP that exactly matches the one that is in operation today. 5.5 The FAA has developed a transition plan to move the existing AIDC data streams from the current system to either the Ocean21 External Communications Server or the AIDC-T. This plan will not require non-FAA organizations to make any modifications to their systems coincident to the cutover of the interfaces. 5.6 JCAB has been requested to change the address that the Tokyo ODP uses to transmit AIDC messages to Oakland ARTCC at a time that is convenient to them. JCAB agreed to work on this change and expressed gratitude for making it possible to continue using AIDC operations after Ocean21 implementation. Common Air Traffic Flow Management (ATFM) Terminology 5.7 JCAB presented information describing the steps taken to establish a common ATFM terminology between the FAA and JCAB. FAA Air Traffic Control System Command Center (ATCSCC) and JCAB Air Traffic Flow Management Center (ATFMC) have agreed to study further means of using common terminology in order to avoid miscommunications. The meeting confirmed that the ATFM Task Force co-chairs would be Mr. Yoshinori Suzuki from JCAB and Mr. Richard Humphreys from FAA. The members of the Task Force include, but are not limited to, representatives from both ATCSCC and ATFMC. Each co-chair will select appropriate representatives from their organizations to serve on the Task Force. IPACG will select and change the members from organizations other than FAA and JCAB, such as US Department of Defense/US Forces Japan. The representative from the International Civil Aviation Organization (ICAO) Asia Pacific Regional Office offered to participate, to the extent possible, in the Task Force to ensure that the outcome of the Task Force is appropriately reflected in ICAO documents. The work of the Task Force will be done by electronic exchange to the greatest extent possible. It was emphasized that it is not the intent of the Task Force to duplicate work already in progress, but to initially consider and review that work. The meeting agreed that the Task Force would continue to address common terminology in view of existing terminology and ongoing ICAO work, and will report to IPACG/24. Future Improvement of JCAB ATFMC and FAA ATCSCC Information Exchange 5.8 Direct communication links between the JCAB ATFMC and the ATCSCC are of great importance and the two facilities established a hotline communication process in November 2002. Currently the facilities use the commercial telephone system to conduct verbal communication only. It is anticipated that there will be a necessity to communicate with each other while sharing documents and pictures in the future. 5.9 FAA ATCSCC introduced a Voice over Internet Protocol (VOIP) called Centra that is deployed at the ATCSCC and discussed the potential test use of the system between ATCSCC and ATFMC. Information is available on the Internet: (English language) http://www.centra.com/products/index.asp and (Japanese language) http://www.macnica.net/centra/ 5.10 It was agreed that the ATFMC would contact the ATCSCC to arrange the VOIP test. Test results and next steps will be reported to IPACG/24. Area Navigation (RNAV) Roadmap for Japan 5.11 The JCAB reported on the establishment of a Steering Committee and RNAV Study Group in 2004, composed of airspace users and related aviation communities, with the aim of developing an RNAV implementation plan for Japan. The group conducted extensive studies and visits to FAA, EUROCONTROL, and other aviation authorities, and exchanged views on RNAV operations. The study group developed the RNAV Roadmap for Japan and presented to it the Steering Committee. The Roadmap was approved by the committee and released in April 2005. A summary of the Roadmap was provided to the meeting. 5.12 The RNAV Roadmap divides the implementation schedules into three phases, taking into account user needs, traffic forecasts and future vision:
5.13 The airlines understood that there is not a clear plan for extending Narita Airport’s second runway due to landowner issues. It is hoped that there is focus and desire to come to resolution for Narita Airport at the earliest opportunity. JCAB has met with the International Air Transport Association (IATA) and is aware of this. JCAB expects Tokyo International Airport at Haneda and other major airports to implement RNAV to resolve some of the issues. 5.14 There was also a discussion about Japan’s amendment to aviation law concerning classification of domestic airspace. Visual flight rules (VFR) operations will not be permitted within Class A airspace (at or above FL290). Reduced vertical separation minimum (RVSM) will be applied between FL290-FL410 inclusive. Directory: about -> office org -> headquarters offices -> ato -> service units -> systemops -> ato intl -> documents -> IPACG IPACG -> The forty-first meeting of the informal pacific atc co-ordinating group IPACG -> The thirty-ninth meeting of the informal pacific atc co-ordinating group (ipacg/39) IPACG -> Ipacg/40 ip/09 8/9/14 the fortieth meeting of the informal pacific atc co-ordinating group IPACG -> Ipacg/40 fit/27 wp/xx 11 September 2014 IPACG -> Summary of Discussions service units -> Quarterly Status Report Download 363.88 Kb. Share with your friends:
|