Technical Provisions for Mode S Services and Extended Squitter

More documents

Recommendations

Info

DRAFT - Working Paper ASP TSGWP11-01 for review by the TSG during the meeting in June 2011 in Paris C-36 Technical Provisions for Mode S Services and Extended Squitter Table C-30. A/V Length and Width Code A/V - L/W Length Code Width Upper-Bound Length and Width Code Code for Each Length/Width Code (Decimal) “ME” “ME” “ME” “ME” Length Width Bit 49 Bit 50 Bit 51 Bit 52 (meters) (meters) 0 0 0 0 0 No Data or Unknown 1 0 0 0 1 15 23 2 3 0 0 1 0 1 25 28.5 34 4 5 0 1 0 0 1 35 33 38 6 7 0 1 1 0 1 45 39.5 45 8 9 1 0 0 0 1 55 45 52 10 11 1 0 1 0 1 65 59.5 67 12 13 1 1 0 0 1 75 72.5 80 14 15 1 1 1 0 1 85 80 90 If the Aircraft or Vehicle is longer than 85 meters, or wider than 90 meters, then decimal Aircraft/Vehicle Length/Width Code 15 shall be used. Note.— For example, consider a powered glider with overall length of 24 meters and wingspan of 50 meters. Normally, an aircraft of that length would be in length category 1 (that is, have a length code of 1). But since the wingspan exceeds 34 meters, it does not qualify for even the “wide” subcategory (width code = 1) of length category 1. Such an aircraft would be assigned length code = 4 and width code = 1, meaning “length less than 55 meters and width less than 52 meters.” C.2.3.10.12 Track Angle/Heading The Track Angle/Heading is a 1-bit (“ME” bit 53, Message bit 85) subfield of the ADS-B Aircraft Operational Status Message (Subtype=1, for Surface Participants) that allows correct interpretation of the data contained in the Heading/Ground Track subfield of the ADS-B Surface Position Message when the Air/Ground status is determined to be in the “On-Ground” state as indicated in §3.1.2.6.10.1.2 of Annex 10, Vol. IV. Draft C.2.3.10.13 Horizontal Reference Direction (HRD) This 1-bit (“ME” bit 54, Message bit 86) subfield will be used to indicate the reference direction (true north or magnetic north) for horizontal directions such as Heading, Track Angle. The Horizontal Reference Direction subfield will be encoded as specified in Table C-31. Table C-31. Horizontal Reference Direction (HRD) Encoding HRD Value Meaning 0 True North 1 Magnetic North C.2.3.10.14 System Design Assurance (SDA) The position transmission chain includes the ADS-B transmission equipment, ADS-B processing equipment, position source, and any other equipment that processes the position data and position quality metrics that shall be transmitted. DRAFT - Working Paper ASP TSGWP11-01 for review by the TSG during the meeting in June 2011 in Paris
DRAFT - Working Paper ASP TSGWP11-01 for review by the TSG during the meeting in June 2011 in Paris Appendix C C-37 The “System Design Assurance” (SDA) subfield is a 2-bit (“ME” bits 31 – 32, Message bits 63 – 64) field that shall define the failure condition that the position transmission chain is designed to support as defined in Table C-32. The supported failure condition shall indicate the probability of a position transmission chain fault causing false or misleading information to be transmitted. The definitions and probabilities associated with the supported failure effect are defined in AC 25.1309-1A, AC 23-1309-1C, and AC 29-2C. All relevant systems attributes should be considered including software and complex hardware in accordance with RTCA DO- 178B (EUROCAE ED-12B) or RTCA DO-254 (EUROCAE ED-80). Table A-32. “System Design Assurance” OM Subfield in Aircraft Operational Status Messages SDA Value Supported Probability of Undetected Fault Software & Hardware (decimal ) (binary) Failure Note 2 Condition causing transmission of False or Note 3,4 Misleading Information Design Assurance Note 1,3 Level 0 00 Unknown/ No safety effect > 1x10 -3 per flight hour or Unknown N/A 1 01 Minor ≤ 1x10 -3 per flight hour D 2 10 Major ≤ 1x10 -5 per flight hour C 3 11 Hazardous ≤ 1x10 -7 per flight hour B Notes.— 1. Software Design Assurance per RTCA DO-178B (EUROCAE ED-12B). Airborne Electronic Hardware Design Assurance per RTCA DO-254 (EUROCAE ED-80). 2. Supported Failure Classification defined in AC-23.1309-1D, AC-25.1309-1A, AC-27-1B and AC 29-2C. 3. Because the broadcast position can be used by any other ADS-B equipped aircraft or by ATC, the provisions in AC 23-1309-1D that allow reduction in failure probabilities and design assurance level for aircraft under 6000 pounds do not apply. 4. Includes probability of transmitting false or misleading latitude, longitude, or associated accuracy and integrity metrics. C.2.3.10.15 SIL Supplement The “SIL Supplement” (Source Integrity Level Supplement) subfield is a 1-bit (“ME” bit 8, Message bit 40) field that shall define whether the reported SIL probability is based on a “per hour” probability or a “per sample” probability as defined in §C.2.3.9.2 and Table C-6. Draft C.2.3.10.16 TCAS/ACAS Operational The “TCAS/ACAS Operational” subfield (“ME” bit 11, Message bit 43) of the CC Codes subfield in ADS-B Aircraft Operational Status Messages (TYPE=31, SUBTYPE=0, for airborne participants) is used to indicate whether the TCAS/ACAS System is Operational or not, and remains as defined for use in the Target State and Status Message (§C.2.3.9.18), with the encoding as specified in Table C-21. C.2.3.10.17 1090ES IN The CC Code subfield for “1090ES IN” in Aircraft Operational Status Messages (TYPE=31, Subtype=0 or 1) is a 1-bit field (“ME” bit 12, Message bit 44) that is set to ONE (1) if the transmitting aircraft has the capability to receive ADS-B 1090ES Messages. Otherwise, this CC code subfield is set to ZERO (0). DRAFT - Working Paper ASP TSGWP11-01 for review by the TSG during the meeting in June 2011 in Paris
Page 1 and 2:
DRAFT - Working Paper ASP TSGWP11-0
Page 3 and 4:
Page 5 and 6:
Page 7 and 8:
Page 9 and 10:
Page 11 and 12:
Page 13 and 14:
Page 15 and 16:
Page 17 and 18:
Page 19 and 20:
Page 21 and 22:
Page 23 and 24:
Page 25 and 26:
Page 27 and 28:
Page 29 and 30:
Page 31 and 32:
Appendix A A-7 TYPE Code Format Hor
Page 33 and 34:
Page 35 and 36:
Page 37 and 38:
Appendix A A-13 The supersonic vers
Page 39 and 40:
Appendix A A-15 The transponder sha
Page 41 and 42:
Page 43 and 44:
Page 45 and 46:
Page 47 and 48:
Page 49 and 50:
Page 51 and 52:
Page 53 and 54:
Page 55 and 56:
Page 57 and 58:
Page 59 and 60:
Page 61 and 62:
Page 63 and 64:
Page 65 and 66:
Appendix A A-41 MB FIELD DRAFT - Wo
Page 67 and 68:
Appendix A A-43 MB FIELD 1 MSB TRAN
Page 69 and 70:
Page 71 and 72:
Appendix A A-47 MB FIELD 1 2 3 4 5
Page 73 and 74:
Page 75 and 76:
Page 77 and 78:
Page 79 and 80:
Appendix A A-55 MB FIELD 1 BDS A,8
Page 81 and 82:
Page 83 and 84:
Page 85 and 86:
Page 87 and 88:
Page 89 and 90:
Page 91 and 92:
Page 93 and 94:
Page 95 and 96:
Page 97 and 98:
Page 99 and 100:
Page 101 and 102:
Page 103 and 104:
Page 105 and 106:
Page 107 and 108:
Page 109 and 110:
Page 111 and 112:
Page 113 and 114:
Page 115 and 116:
Page 117 and 118:
Page 119 and 120:
Page 121 and 122:
Appendix A A-97 a) the PI sends a T
Page 123 and 124:
Appendix A A-99 This subfield shall
Page 125 and 126:
Appendix A A-101 These channels hav
Page 127 and 128:
Page 129 and 130:
Page 131 and 132:
Page 133 and 134:
Appendix A A-109 A.4. MODE S BROADC
Page 135 and 136:
Appendix A A-111 Note 1.— This st
Page 137 and 138:
Page 139 and 140:
Appendix B B-3 TYPE code Subtype co
Page 141 and 142:
Page 143 and 144:
Page 145 and 146:
Page 147 and 148:
Page 149 and 150:
Page 151 and 152:
Page 153 and 154:
Appendix B B-17 Coding (Binary) (De
Page 155 and 156:
Appendix B B-19 a) ACAS operational
Page 157 and 158:
Appendix B B-21 Subfield Coding: DR
Page 159 and 160:
Appendix B B-23 Coding (Binary) (De
Page 161 and 162:
Page 163 and 164:
Page 165 and 166:
Page 167 and 168:
Page 169 and 170:
Appendix B B-33 MB FIELD DRAFT - Wo
Page 171 and 172:
Appendix B B-35 MB FIELD DRAFT - Wo
Page 173 and 174: Appendix B B-37 MB FIELD DRAFT - Wo
Page 177 and 178: Appendix B B-41 CF value ICAO/Mode
Page 179 and 180: DRAFT - Working Paper ASP TSGWP11-0
Page 193 and 194: Appendix C C-5 Table C-2. “TYPE
Page 199 and 200: Appendix C C-11 C.2.3.2.2 Time Sync
Page 213 and 214: Appendix C C-25 Notes.— DRAFT - W
Page 219 and 220: Msg Bit # “ME” Bit # Appendix C
Page 221 and 222: Appendix C C-33 Msg Bit # "ME” Bi
Page 223: DRAFT - Working Paper ASP TSGWP11-0
Page 231 and 232: Appendix C C-43 Notes. — DRAFT -
Page 239 and 240: Appendix C C-51 3. The decoded posi
Page 245 and 246: Appendix C C-57 B Reports to have k
Page 247 and 248: Appendix C C-59 Register 0516 DRAFT
Page 253 and 254: Appendix C C-65 Register 0A16 Figur
Page 259 and 260: Appendix C C-71 Table C-37. CF Fiel
Page 275 and 276:
Page 277 and 278:
Page 279 and 280:
Page 281 and 282:
Page 283 and 284:
Page 285 and 286:
Page 287 and 288:
Appendix CD CD-3 ACTIONS EVENTS DRA
Page 289 and 290:
Page 291 and 292:
Appendix CD CD-7 too many broadcast
Page 293 and 294:
Page 295 and 296:
Page 297 and 298:
Appendix CD CD-13 CD.2.4.4.1.2 Poss
Page 299 and 300:
Appendix CD CD-15 D.2.4.4.2.1.2 A32
Page 301 and 302:
Appendix CD CD-17 AP/FD mode V/S-FP
Page 303 and 304:
Page 305 and 306:
Page 307 and 308:
Appendix CD CD-23 CD.2.4.7.5 BINARY
Page 309 and 310:
Page 311 and 312:
Appendix CD CD-27 Zone no. DRAFT -
Page 313 and 314:
Page 315 and 316:
Appendix CD CD-31 CD.4 IMPLEMENTATI
Page 317 and 318:
Page 319 and 320:
Page 321 and 322:
Page 323 and 324:
Page 325 and 326:
Appendix DE DE-7 c. for GNSS, the p
Page 327 and 328:
Appendix DE DE-9 MB FIELD DRAFT - W
Page 329 and 330:
Appendix DE DE-11 MB FIELD DRAFT -
show all

Technical Provisions for Mode S Services and Extended Squitter

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

Delete template?

Save as template?