October 6, 2011 - RTCA

More documents

Recommendations

Info

1. Update Existing MOPS for TCAS II 2. Prepare MOPS for TCAS Hybrid Surveillance 3. Develop MOPS for Autoflight/TCAS Coupling 4. Develop guidance for traffic displays that support collision avoidance for aircraft not carrying TCAS II 5. Define proposals to support the development of future collision avoidance systems Ken noted that Working Group 75 had no plans to change the core TCAS II MOPS other than in unison with SC-147, and that MOPS for TCAS II and Hybrid Surveillance are expected to be identical to the RTCA MOPS. The primary focus of the initial work on developing MOPS for the Autoflight/TCAS Coupling will be in the areas of automatic guidance on RAs and altitude capture adaptation to reduce occurrence of RAs. It is expected that a new subgroup will be established to complete this work to ensure that appropriate expertise in autoflight systems is included in the work. Analyses have shown that the collision risk will be reduced by a factor of two and the RA rate reduced by over 50% in European airspace with the implementation of the autoflight/TCAS coupling. Ken expressed the desire from Working Group 75 to have the development of these MOPS be done in concert with RTCA. The SC-147 Co-Chairs outlined the process needed to have the efforts on MOPS development to become a joint effort. Bob Buley expressed his desire that the appropriate expertise from SC-147 be involved in any joint work, regardless of which RTCA Special Committee eventually is tasked with working with Working Group 75. Working Group 75 has also been working on the compatibility of TCAS with ground safety nets and the display of RA information to controllers. The Requirements Working Group (RWG) spent some time during their meeting this week discussing the display of RA information to controllers. Ken introduced two presentations on the topic display of RA information to controllers: � Yvonne Graner clarified DFS's motivation to perform significant research on this topic following the Überlingen accident and an associated safety recommendation. She outlined the DFS program for evaluating the use of this information, and the enabling technology. � Stan Drozdowski started by placing the display of RA information in the broader context of Compatibility of Safety Nets. He provided an overview of ATS facilities where Mode S RA downlink is already being used to display RA information to controllers although there are no ICAO provisions for the operation of RA downlink. He concluded by advocating a more holistic approach to further TCAS evolution. Agenda Item 3. TCAS Program Office Activities Neal Suchy provided an overview of the work being performed by the TCAS Program Office to define potential next generation collision avoidance system. Work is also underway to investigate the display of RA information to controllers. At the present time, the Program Office does not support the display of information to controllers. Agenda Item 3.a Monitoring Efforts/TRAMS/TOPA 2
Wes Olson provided an overview of data collected and analyzed as part of the TCAS Operational Assessment Program (TOPA). He noted that a majority of the data are being collected from Mode S radars across the United States. There are 21 sites now operational and there are currently over 150,000 RAs in the TOPA database. There has been little change in the findings from the data since his report at the last SC-147 meeting. Wes presented an overview of studies and analyses that have been completed on pilot response to RAs; TCAS performance in level off encounters (with both 500 and 1000 ft separation from the intruder); and RAs issued where an intruder could not be identified in the radar surveillance data. Agenda Item 3.b Future Collision Avoidance System (CAS) Development Efforts Neal Suchy provided an overview of the work being performed by the TCAS Program Office to define potential next generation collision avoidance system. The Program Office’s efforts are focused on three primary work packages. 1. Improve current surveillance performance to minimize TCAS utilization of the 1030/1090 MHz spectrum. 2. Develop threat logic that will be compatible with expected/planned changes in airspace structure and operations. This threat logic is focused for use on aircraft that currently use TCAS II systems. 3. Define surveillance requirements and concepts that will allow TCAS to use different surveillance sources and use improved tracking algorithms. Additional research is being conducted to evaluate requirements and concepts that could provide a collision avoidance capability for other classes of airspace users. Work is underway to conduct initial flight testing of the new threat logic in the 2013 time frame. Agenda Item 4 AVS and Other FAA Activities Agenda Item 4.a Certification and Flight Standard Activities Roger Sultan provided an update on the TCAS-related activities that Flight Standards have been working on since the last Plenary meeting. The Flight Standards’ Outreach efforts have resulted in meetings and discussions with NetJets and Boeing’s Training organization. The next efforts for the Outreach program are to conduct briefings at NBAA Regional Forums and with ALPA. A SAFO has been developed for Part 135 and Part 91k operators related to TCAS training and guidance. This is in final review and is expected to be released shortly. Flight Standards is also working on developing TCAS training material and has supported verification of the implementation of the autopilot and flight director automated response systems on the A350. Roger introduced Wayne Gallo to the Committee. Wayne is a new member of the Flight Standards Organization and will be representing Flight Standards in future SC-147 meetings. 3
Page 1: Special Committee 147 1 RTCA Paper
Page 5 and 6: The SWG also sought the Committee
Page 7: Name Organization E-mail Thomas Tro

October 6, 2011 - RTCA

Create successful ePaper yourself

Delete template?

Save as template?