Federal Aviation Administration - RTCA SC-186

RTCA SC-186 Working Group #4

ASA MASPS Development

Issue Papers

This page has been designed to support Working Group 4 of RTCA SC-186. This group is currently maintaing the Airborne Surveillance Applications (ASA) Minimum Aviation System Performance Standards (MASPS). This group is also chartered with developing the technical requirements for ADS-B applications that have had a detailed Concept of Operation developed within Working Group 1 and approved by the RTCA SC-186 Plenary. For more information on the group's activities contact the group co- chair, Don Walker of Honeywell <don.walker@honeywell.com >.

ASAS MOPS Meeting Calendar

Draft ASAS MOPS material

Meeting Location Travel Information
(Maps, Hotels, etc.)

Issue Papers:

File Name (*.PDF)	Size	Date	Status	Description
ASA-ASAS-Issue-Papers.zip	1.5m	11/23/2004	-	ZIP file containing all submitted issue papers (1-20)
Blank ASAS Issue Paper.zip	8k	-	-	Blank submission form
IP01 TCAS ASA MASPS Issue	14k	4/23/2003	Withdrawn	TCAS Platform Usage
IP02 Degraded Target Utility Indicator	16k	4/23/2003	Closed	Degraded Target Utility Indicator
IP03 ASSAP Ownship Data Processing	19k	4/23/2003	Closed	Specifications are needed for ASSAP processing of Ownship data and interfaces from ASSAP to the ADS-B transmitting subsystem.
IP04 Unknown SIL.	15k	4/23/2003	Open	Legacy GPS Systems are unable to provide values for SIL
IP05 Application Names and Acronyms	38k	4/23/2003	Deferred	Recommendations for changing the naming and acronym conventions for Airborne Surveillance Applications.
IP06 Minimum Data Quality Requirements	17k	4/23/2003	Closed	Cautions against placing minimum output requirements on ADS-B data.
IP07 Enhanced SIL Bit Definitions	21k	4/23/2003	Closed	Requests that SIL definitions be extended to include intermediate values than those specified in DO-242A.
IP08 CDTI - Ownship Directionality	59k	4/23/2003	Open	Proposal to address CDTI display requirements when ownship loses its directionality information.
IP09 CDTI - Display of Position Uncertainty	54k	4/23/2003	Open	Proposal for how CDTI symbology might represent position uncertainty.
IP10 CDTI - Altitude Usage	15k	6/18/2003	Open	Requests clarification on best choice of altitude source (i.e. baro vs. geo) for determining relative and absolute altitude of displayed CDTI traffic.
IP11ASA - Continuity in Tables 2-3 & 3-1	64k	1/13/2004	Pending	Identification of an inconsistency of continuity requirements between Tables 2-3 and 3-1 in ASA MASPS.
IP12 ASA - Air-Ground Determination	66k	1/13/2004	Pending	Problems with ASA MASPS air/Ground determination when A/V has no automatic detection means.
IP13 ASSAP - TIS-B Registration	58k	2/13/2004	Pending	Request to coordinate with WG2 that the TIS-B MASPS requires the appropriate registration functions between ADS-B and ground sensors such as SSR.
IP14 STP - Velocity Lag Indicator	64k	9/10/2004	Pending	Proposal for new ADS-B field to convey velocity tracker lag.
IP15 ASA - ADS-B OUT Power Switch	66k	9/10/2004	Pending	Question as to whether there needs to be a requirement for ADS-B Out systems to have an ON/OFF switch available to the pilot.
IP16 ASA - Surface Vehicles in Tunnels	58k	9/01/2004	Pending	Problem of Surface Vehicles which operate on in tunnels under runways and taxiways. How do Aircraft track these vehicles without placing them on the runways or taxiways?
IP17 CDTI - ADS-B TCAS Symbol Directionality	25k	11/03/2004	Open	Summation of issue of whether or not CDTI should introduce directionality indication onto TCAS targets.
IP18 CDTI - Velocity Vector Issues	718k	11/03/2004	Open	Summation of issues related to using velocity vectors for CDTI targets.
IP19 ASSAP - Received NUC means Integrity unknown	17k	11/02/2004	Pending	Since there is no means on the receive side to determine if transmitting DO-260 compliant systems are also TSO C166 compliant, integrity must be assumed to be ZERO for received data.
IP20 ASSAP - Limit of NIC & NAC to 8 or less	18k	11/02/2004	Pending	NIC & NAC values of 9 or greater are defined with vertical considerations. Since initial STP MOPS will not address these factors, ASSAP must not use values greater than 8 for these fields.
IP21 ASAS - Proposed Appendix on Symbol Determination	1.5m	4/2/2009	Pending	The proposed appendix provides information on how CDTI symbol requirements were determined through studies, expert opinion, and existing systems. It was prompted by the inability to locate such information on existing TCAS symbols. The appendix information should be helpful when re-examining display requirements for future versions or systems.
IP22 ASAS - Traffic Application - Selected/Coupled During TCAS RA/TA	25k	4/6/2009	Pending	Current Traffic Application descriptions do not consider what happens when a TCAS (ACAS) Traffic Alert (TA) or Resolution Advisory (RA) happens � the same holds for other ASAS alerts that may be generated by/for other applications. The ASAS MOPS does not specify what should happen when a TA/RA occurs when traffic is Selected or Coupled. This is currently left undefined in the ASAS MOPS (see appendix G., section G.6).

Links