Minimum Aviation System Performance Standards for Aircraft ...

More documents

Recommendations

Info

58 © 20xx, RTCA, Inc. available for a Mode S track (typically only in the surface service volumes), then this address is provided in the TIS-B messages. The SBS – Ground System has multiple trackers, deployed regionally such that there is an airborne tracker dedicated to the airspace of each FAA Enroute Center/Terminal Area. There is no correlation of track IDs between trackers, so as a TIS-B Target transitions across Service Volume boundaries between Enroute Centers, its Track ID will change, which may cause duplicate symbols to overlap while the old track ID times out on a CDTI. The avionics may need to be aware of the potential for track ID changes and perform correlation and association processing to associate aircraft across the track ID change in order to minimize duplicate symbols and perception of dropped tracks. When ADS-R services are not offered in an airspace, the TIS-B service provides Client ADS-B equipped aircraft with proximity targets that are ADS-B equipped on the opposite link technology. 3.1.4.2.2.4 TIS-B in Enroute and Terminal Airspace Domains The SBS – Ground System examines each potential TIS-B target to determine if it is within proximity of one or more TIS-B clients. In order to become a TIS-B target, a potential target must be contained in a cylinder defined by lateral and vertical distance from Client aircraft. The size of this cylinder depends on the airspace domain of the Client aircraft. TIS-B Service is provided to aircraft operating in the En Route and Terminal Service Volumes. There is a Service Ceiling of 24,000 feet, above which TIS- B clients will not be provided TIS-B service. In the En Route and Terminal domains, proximity aircraft include all aircraft within a 15 NM radius and ±3500 feet of altitude. Aircraft or vehicles determined to be operating on the surface will not be considered valid TIS-B targets for aircraft operating in En Route and Terminal Service Volumes. 3.1.4.2.2.5 TIS-B in Surface Domains Figure 3-13: TIS-B Client Proximity Determination In a surface domain SV, a client is provided all applicable TIS-B targets in SV domain. This includes all targets in the ground state within the movement area as well as airborne
targets within 5 NM and 2000 feet AGL of the airport reference point (ARP). Additionally, TIS-B in surface domains covers expanding volumes along the approach and departure corridors. 3.1.4.2.2.6 Transmission of TIS-B Target Messages The SBS – Ground System transmits TIS-B reports for every TIS-B Target that is in proximity of one or more Clients. An individual Target may be in proximity of multiple Clients, with the potential for the Clients to be in separate airspace domains, with differing update rates. The SBS – Ground System will transmit TIS-B reports for a Target aircraft at the highest rate required by any of the clients of that aircraft. For example, if a Target aircraft has clients in both terminal and en route domains, TIS-B reports for that Target aircraft will be transmitted at the rate required for the terminal domain. The cumulative number of messages transmitted by all SBS – Ground System radio stations within reception range of any aircraft in the NAS will not exceed 1000 1090ES messages per second with received signal strength greater than -78 dBm. This limit applies to both the ADS-R and TIS-B Service combined. The cumulative maximum number of UAT messages received by an aircraft will not exceed 400 messages per second with received signal strength greater than -82 dBm. 3.1.4.3 TIS-B and ADS-R Subsystem Requirements (Mike Garcia) 3.1.5 Surface Vehicles (UNASSIGNED) 3.2 Broadcast Information Elements Requirements The ADS-B system shall (242AR2.3) be capable of transmitting messages and issuing reports containing the information specified in the following subsections. These MASPS do not specify a particular message structure or encoding technique. The information specified in the following subparagraphs can be sent in one or more messages in order to meet the report update requirements specified in Section §3.4.3.3. 3.2.1 Time of Applicability (TOA) The time of applicability (TOA) of ADS-B reports indicates the time at which the reported values were valid. Time of applicability shall (242AR2.4) be provided in all reports. Requirements on the accuracy of the time of applicability are addressed in Section §3.4.3.3.2.2 and paraphrased in §3.5.1.3.3. © 20xx, RTCA, Inc. 59
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 58 and 59: 46 © 20xx, RTCA, Inc. Table 3.1.1.
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 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 136 and 137:
3.5.1.3.12 Heading While on the Sur
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 162 and 163:
Page 164 and 165:
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:
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?