Minimum Aviation System Performance Standards for Aircraft ...

C3 Flight
Following
Surveillance
Supports private user
operations planning and
flight following
Does not require ATS interface.
Certification requirements
determined by user application.
3.1.1.3.3 Ground Receive-Only Subsystems (Class C)
© 20xx, RTCA, Inc.
47
Coverage determined by
application.
Surveillance state vector reports, mode-status reports, and on-condition reports are
available from ADS-B system participants within the coverage domain of ground ADS-B
receive-only, or Class C subsystems. The following Class C subsystems are defined
(Table 3.1.1.3.2a):
Class C1: Ground ATS Receive-Only ADS-B Subsystems for En Route and Terminal
area applications. Class C1 subsystems should meet continuity and availability
requirements determined by the ATS provider.
Class C2: Ground ATS Receive-Only ADS-B Subsystems for approach monitoring and
surface surveillance applications. Class C2 subsystems have more stringent accuracy
and latency requirements than Class C1 systems. Class C2 systems may be required,
depending upon the ADS-B System design, to recognize and process additional
ADS-B message formats not processed by Class C1 subsystems.
Class C3: Ground ATS Receive-Only ADS-B Subsystems for flight following
surveillance is available from this equipage class for use by private operations
planning groups or for provision of flight following and SAR.
3.1.2 ASSAP Subsystem Description (Dave Elliott)
The Airborne Surveillance and Separation Assurance Processing (ASSAP) subsystem
represents the surveillance and application-specific processing functions of ASA.
ASSAP surveillance processing consists of correlation, possible data fusion, and track
processing of ADS-B, ADS-R, TIS-B, and TCAS traffic reports. ASSAP application
processing provides the application-specific processing for all ASA applications. The
extent of ASSAP application processing is dependent upon the aircraft’s capabilities, as
determined by each application’s minimum performance requirements. ASSAP
application processing may be minimal for airborne situational awareness applications
(e.g., EvAcq or AIRB), or may require more significant processing for surface situational
awareness applications (e.g., SURF) or future guidance applications (e.g., FIM-S). The
ASSAP subsystem also monitors and processes flight crew inputs via the interface from
the Cockpit Display of Traffic Information (CDTI) subsystem, and provides all traffic
surveillance data and ASA application-specific data for visual and /or aural display to the
CDTI for the flight crew.
3.1.2.1 ASSAP/CDTI System Boundaries
Figure 3.1.2.1 illustrate the ASSAP/CDTI system boundaries as two subsystems of the
ASA System, and is based on Figure x.y in §x.y. The dashed line represents the system
boundaries for the ASSAP and CDTI subsystems. The allocated requirements for
ASSAP and the CDTI are found in §3.4.1 and §3.4.2, respectively.