Minimum Aviation System Performance Standards for Aircraft ...

94
© 20xx, RTCA, Inc.
ASSAP shall (R3.xxx) propagate all ASSAP required input interface elements to the
CDTI interfaces to support the minimum requirements for all installed applications as
indicated in §3.4.1.3, Table 3.4.1.3 by a dot (•), except those that are provided directly to
the CDTI from own-ship navigation sources.
Additionally, other information such as aircraft state information that is calculated or
estimated is required to be output to the CDTI for the display of own-ship, traffic, or
status to support the installed applications.
ASSAP shall (R3.xxx) provide all output interfaces to the CTDI to support the minimum
requirements for all installed applications as indicated in Table 3.4.1.5 by a dot (•).
The ASSAP function shall (R3.xxx) provide validation status information (e.g.,
valid/invalid flags) for each data element provided to the CDTI.
Note: No longer providing the data element (e.g., label or data word) may be another
method of inferring valid/invalid status.
Table 3.4.1.5: ASSAP to CDTI Information Elements
Category Contents EvAcq AIRB VSA ITP SURF
ID Track ID • • • • •
Horizontal Position • • • • •
Geometric Altitude 1 • • • • •
Pressure Altitude • • • • •
Traffic
State
Estimate
Status
Track Angle / Heading • • • • •
North Velocity • • • • •
East Velocity • • • • •
Vertical Rate / Vertical Senses 2 • • • • •
Ground Speed • • • •
ITP Distance •
ITP Traffic Ahead / Behind •
Traffic Air / Ground • • • • •
Traffic Application Capability • • •
Applications Status • • • • •
ASSAP Fault • • • • •
ITP Traffic Geometric Initialization
Pass / Fail
•
TCAS 3 Correlation Status • • • • •
Future
Alerts (TSAA)
Guidance (FIM-S)
Notes for Table 3.4.1.5:
1. Traffic Geometric Altitude is not needed for surface traffic.
2. When airborne.
3. The TCAS elements of the ASSAP to CDTI report are only required when the CDTI is
also the TCAS Traffic Display.