18.11.2012 Views

Minimum Aviation System Performance Standards for Aircraft ...

Minimum Aviation System Performance Standards for Aircraft ...

Minimum Aviation System Performance Standards for Aircraft ...

SHOW MORE
SHOW LESS

You also want an ePaper? Increase the reach of your titles

YUMPU automatically turns print PDFs into web optimized ePapers that Google loves.

92<br />

© 20xx, RTCA, Inc.<br />

5. Required if TCAS is present in the configuration and an integrated TCAS/ASA traffic<br />

display is used. These outputs are expected to be supplied by current TCAS<br />

installation.<br />

6. Each future application will add columns <strong>for</strong> minimum requirement.<br />

7. When used to display the Emergency/Priority Status.<br />

8. When used to display the physical extent of the aircraft.<br />

3.4.1.4 ASSAP Functional Requirements<br />

ASSAP functional requirements are broken into surveillance processing requirements<br />

(§3.4.1.4.1) and applications processing requirements (§3.4.1.4.2).<br />

3.4.1.4.1 ASSAP Surveillance Processing Requirements<br />

ASSAP surveillance processing function receives in<strong>for</strong>mation <strong>for</strong> traffic A/V’s from<br />

various surveillance sources, correlates the data, registers the data, and outputs a track file<br />

consisting of state and other in<strong>for</strong>mation about each A/V under track. Requirements <strong>for</strong><br />

the surveillance sub-function follow. Note that the tracking and correlation functions<br />

make extensive use of the data that is provided in state data (Table 3.4.1.3).<br />

ASSAP shall (R3.xxx) acquire all state data necessary to generate tracks <strong>for</strong> A/Vs and<br />

own-ship.<br />

ASSAP may receive A/V data from different surveillance sources.<br />

ASSAP shall (R3.xxx) per<strong>for</strong>m a tracking function on each traffic A/V.<br />

ASSAP shall (R3.xxx) extrapolate the target horizontal position (i.e., latitude and<br />

longitude), <strong>for</strong> tracks <strong>for</strong> which a position update has not been received, to a common<br />

time reference prior to providing in<strong>for</strong>mation to the CDTI.<br />

Note: A linear extrapolation is expected to be used to compensate <strong>for</strong> any delays<br />

incurred leading up to the time of transmission. Extrapolation is only per<strong>for</strong>med<br />

on targets determined to be airborne. The pressure altitude should not be<br />

extrapolated since the altitude rate accuracy may induce larger altitude errors<br />

than the provided in the original data.<br />

ASSAP shall (R3.xxx) not introduce any additional position error to that which might<br />

otherwise be introduced by a linear extrapolation using the instantaneous velocity<br />

reported <strong>for</strong> the target by other surveillance sources.<br />

ASSAP shall (R3.xxx) maintain tracks <strong>for</strong> multiple A/Vs.<br />

ASSAP may receive A/V data <strong>for</strong> the same A/V from different surveillance sources.<br />

The ASSAP tracking function shall (R3.xxx) include a correlation function that<br />

associates traffic data from any surveillance sources that relate to the same A/V’s track to<br />

minimize the probability of processing and displaying duplicate A/Vs.

Hooray! Your file is uploaded and ready to be published.

Saved successfully!

Ooh no, something went wrong!