Minimum Aviation System Performance Standards for Aircraft ...

More documents

Recommendations

Info

3.5.1.3.12 Heading While on the Surface Field © 20xx, RTCA, Inc. Heading (§3.3.7) indicates the orientation of an A/V, that is, the direction in which the nose of an aircraft is pointing. ADS-B Participants are not required to broadcast heading if their length/width code (part of the aircraft size code, Table 3.3.4.1a) is Zero (0). However, each ADS B participant that reports a length code of 2 or greater shall (242AR3.76) transmit messages to support the heading element of the SV report when that participant is on the surface and has a source of heading available to its ADS-B transmitting subsystem. Heading shall (242AR3.77-A) be reported for the full range of possible headings (the full circle, from 0° to nearly 360°). The heading of surface participants shall (242AR3.77-B) be communicated and reported with a resolution of 6 degrees of arc or finer. Notes: 1. If heading is encoded as a binary fraction of a circle, a resolution of 6° of arc or finer would require at least 6 binary bits. 2. The reference direction for heading (true north or magnetic north) is communicated in the True/Magnetic Heading Flag (§3.2.7) of the Mode Status report. 3. For operations at some airports, heading may be required to enable proper orientation and depiction of an A/V by applications supporting those surface operations. 3.5.1.3.13 Heading Valid Field The “heading valid” field in the SV report shall (242AR3.78-A) be ONE if a valid heading is provided in the “heading while on the surface” field of the SV report; otherwise, it shall (242AR3.78-B) be ZERO. 3.5.1.3.14 Pressure Altitude Field Barometric pressure altitude shall (242AR3.79) be reported referenced to standard temperature and pressure (1013.25 hPa or mB, or 29.92 in Hg). Barometric pressure altitude shall (242AR3.80) be reported over the range of -1,000 feet to +100,000 feet. If a pressure altitude source with 25 foot or better resolution is available to the ADS-B transmitting subsystem, then pressure altitude from that source shall (242AR3.81-A) be communicated and reported with 25 foot or finer resolution. Otherwise, if a pressure altitude source with 100 foot or better resolution is available, pressure altitude from that source shall (242AR3.81-B) be communicated and reported with 100 foot or finer resolution.
3.5.1.3.15 Pressure Altitude Valid Field The “pressure altitude valid” field in the SV report is a one-bit field which shall (242AR3.82-A) be ONE if valid information is provided in the “pressure altitude” field; otherwise, the “pressure altitude valid” field shall (242AR3.82-B) be ZERO. 3.5.1.3.16 Vertical Rate Field The “vertical rate” field in the SV report contains the altitude rate of an airborne ADS-B participant. This shall (242AR3.83) be either the rate of change of pressure altitude or of geometric altitude, as specified by the “vertical rate type” element in the MS report. The range of reported vertical rate shall (242AR3.84) accommodate up to ±32000 ft/min for airborne participants. Geometric vertical rate shall (242AR3.85) be communicated and reported with a resolution sufficiently fine that it does not compromise the accuracy reported in the NACV field of the Mode Status report. Moreover, vertical rate shall (242AR3.86) be communicated and reported with a resolution sufficiently fine that it does not compromise the one-sigma maximum ADS-B contribution to vertical rate error, σvv, listed in Table 3.4.3.3.1.1a, that is, 1.0 ft/s for airborne participants. 3.5.1.3.17 Vertical Rate Valid Field The “vertical rate valid” field in the SV report is a one-bit field which shall (242AR3.87- A) be ONE if valid information is provided in the “vertical rate” field; otherwise, the “vertical rate valid” field shall (242AR3.87-B) be ZERO. 3.5.1.3.18 Navigation Integrity Category (NIC) Field The NIC field in the SV report is a 4-bit field that shall (242AR3.88) report the Navigation Integrity Category described in Table 3.3.10a (§3.3.10). 3.5.1.3.19 Report Mode Field The “Report Mode” provides a positive indication when SV and MS acquisition is complete and all applicable data sets and modal capabilities have been determined for the participant or that a default condition is determined by the Report Assembly function. The information for this SV element is not transmitted over the ADS-B data link, but is provided by the report assembly function at the receiving ADS-B participant. Table 3.5.1.3.19 lists the possible values for the SV Report Mode. Table 3.5.1.3.19: SV Report Mode Values. Value Meaning 0 Acquisition 1 Track 2 Default © 20xx, RTCA, Inc.
Page 1 and 2:
1150 18 th Street, NW, Suite 910 Wa
Page 3 and 4:
FOREWORD This document was prepared
Page 5 and 6:
TABLE OF CONTENTS 1 PURPOSE AND SCO
Page 7 and 8:
3.3.23 Selected Heading Sign Field.
Page 9 and 10:
LIST OF TABLES Table 2-5: High Leve
Page 11:
This Page Intentionally Left Blank.
Page 14 and 15:
2 © 20xx, RTCA, Inc. C: Derivation
Page 16 and 17:
4 1.2.3 ASA Architecture © 20xx, R
Page 18 and 19:
6 © 20xx, RTCA, Inc. The TCAS traf
Page 20 and 21:
8 © 20xx, RTCA, Inc. DO-3xx ADS-B
Page 22 and 23:
10 1.3.1.4 Basic Surface Situationa
Page 24 and 25:
12 2 Operational Requirements 2.1 G
Page 26 and 27:
14 © 20xx, RTCA, Inc. timeliness,
Page 28 and 29:
16 © 20xx, RTCA, Inc. Table 2-6: R
Page 30 and 31:
18 2. FAA TSO-C195 states applicati
Page 32 and 33:
20 © 20xx, RTCA, Inc. Notes for Ta
Page 34 and 35:
22 © 20xx, RTCA, Inc. • Optimiza
Page 36 and 37:
24 © 20xx, RTCA, Inc. same approac
Page 38 and 39:
26 © 20xx, RTCA, Inc. may allow de
Page 40 and 41:
28 © 20xx, RTCA, Inc. An aircraft
Page 42 and 43:
30 Information ↓ Initial Acquisit
Page 44 and 45:
32 © 20xx, RTCA, Inc. NRA - 3 NM E
Page 46 and 47:
34 © 20xx, RTCA, Inc. Aircraft typ
Page 48 and 49:
36 © 20xx, RTCA, Inc. This Page In
Page 50 and 51:
38 © 20xx, RTCA, Inc. In Figure 3.
Page 52 and 53:
40 © 20xx, RTCA, Inc. Figure 3.1.1
Page 54 and 55:
42 3.1.1.1.3 Functional Level © 20
Page 56 and 57:
Page 58 and 59:
46 © 20xx, RTCA, Inc. Table 3.1.1.
Page 60 and 61:
Page 62 and 63:
50 © 20xx, RTCA, Inc. Figure 3-8 i
Page 64 and 65:
52 USER AIR INTERFACE © 20xx, RTCA
Page 66 and 67:
54 3.1.4.2.1.4 ADS-R in Enroute and
Page 68 and 69:
56 TIS‐B Non‐Equipped © 20xx,
Page 70 and 71:
58 © 20xx, RTCA, Inc. available fo
Page 72 and 73:
60 3.2.2 Identification 3.2.2.1 Cal
Page 74 and 75:
62 © 20xx, RTCA, Inc. i. Lighter-t
Page 76 and 77:
64 © 20xx, RTCA, Inc. The ADS-B po
Page 78 and 79:
66 3.2.4.2 Altitude © 20xx, RTCA,
Page 80 and 81:
68 3.2.7 Heading © 20xx, RTCA, Inc
Page 82 and 83:
70 3.2.8.7 Other Capability Codes
Page 84 and 85:
72 SDA Value (decimal) (binary) 0 0
Page 86 and 87: 74 © 20xx, RTCA, Inc. Table 3.2.9.
Page 88 and 89: 76 © 20xx, RTCA, Inc. 5. RC < 0.3
Page 90 and 91: 78 © 20xx, RTCA, Inc. Table 3.2.12
Page 92 and 93: 80 3.2.16 Geometric Vertical Accura
Page 94 and 95: 82 © 20xx, RTCA, Inc. Note: Users
Page 96 and 97: 84 3.2.24 Selected Heading Field ©
Page 98 and 99: 86 © 20xx, RTCA, Inc. a. The ADS-B
Page 100 and 101: 88 3.4.1.1 Definitions © 20xx, RTC
Page 102 and 103: 90 Source Info Category Information
Page 104 and 105: 92 © 20xx, RTCA, Inc. 5. Required
Page 106 and 107: 94 © 20xx, RTCA, Inc. ASSAP shall
Page 108 and 109: 96 3.4.2.2 Latency 3.4.2.3 Integrit
Page 110 and 111: 98 3.4.2.11 Suitability of Traffic
Page 112 and 113: 100 3.4.3.1 ADS-B Surveillance Cove
Page 114 and 115: 102 © 20xx, RTCA, Inc. required to
Page 116 and 117: 104 Equipage Class ↓ B0 Aircraft
Page 118 and 119: © 20xx, RTCA, Inc. Table 3.4.3.3.1
Page 120 and 121: © 20xx, RTCA, Inc. Notes for Table
Page 122 and 123: Operational Domain → © 20xx, RTC
Page 124 and 125: © 20xx, RTCA, Inc. 2. Future versi
Page 126 and 127: © 20xx, RTCA, Inc. • Report time
Page 128 and 129: 3.5.1.2 ADS-B Message Exchange Tech
Page 130 and 131: Notes: © 20xx, RTCA, Inc. 1. It is
Page 132 and 133: © 20xx, RTCA, Inc. • Ground Spee
Page 134 and 135: © 20xx, RTCA, Inc. Note: The recom
Page 138 and 139: 3.5.1.4 Mode Status Report © 20xx,
Page 140 and 141: © 20xx, RTCA, Inc. 3. These elemen
Page 142 and 143: 3.5.1.4.9 Capability Class (CC) Cod
Page 144 and 145: 3.5.1.4.15 Geometric Vertical Accur
Page 146 and 147: 3.5.1.6.2 ARV Report Update Require
Page 148 and 149: © 20xx, RTCA, Inc. The higher “s
Page 150 and 151: © 20xx, RTCA, Inc. Whereas ADS-B r
Page 152 and 153: 4 ADS-B IN System Applications Requ
Page 154 and 155: © 20xx, RTCA, Inc. Broadcast (ADS-
Page 156 and 157: © 20xx, RTCA, Inc. This Page Inten
Page 158 and 159: This page intentionally left blank.
Page 160 and 161: Appendix A Page A-2 ©20xx, RTCA, I
Page 166 and 167: Appendix A Page A-8 A.2 Definitions
Page 168 and 169: Appendix A Page A-10 Air/Ground Sta
Page 170 and 171: Appendix A Page A-12 Collision Avoi
Page 172 and 173: Appendix A Page A-14 Extended Displ
Page 174 and 175: Appendix A Page A-16 Latency Compen
Page 176 and 177: Appendix A Page A-18 Regime - Divis
Page 178 and 179: Appendix A Page A-20 TCAS Potential
Page 180 and 181: Appendix B Bibliography
Page 182 and 183: B Bibliography Appendix B Page B-1
Page 184 and 185: Appendix B Page B-3 Name Reference
Page 186 and 187:
Appendix B Page B-5 Name Reference
Page 188 and 189:
Page 190 and 191:
Page 192 and 193:
show all

Minimum Aviation System Performance Standards for Aircraft ...

Create successful ePaper yourself

Delete template?

Save as template?