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-26 Technical Provisions for Mode S Services and Extended Squitter 3. The use of Gilham type altimeters is strongly discouraged because of the potential for undetected altitude errors. C.2.3.9.11 Source Integrity Level (SIL) This 2-bit (“ME” bits 45 – 46, Message bits 77 – 78) subfield shall be used to define the probability of the reported horizontal position exceeding the radius of containment defined by the NIC, without alerting, assuming no avionics faults. Although the SIL assumes there are no unannunciated faults in the avionics system, the SIL must consider the effects of a faulted Signal-in-Space, if a Signal-in-Space is used by the position source. The probability of an avionics fault causing the reported horizontal position to exceed the radius of containment defined by the NIC, without alerting, is covered by the System Design Assurance (SDA) parameter (§C.2.3.10.14). The SIL probability can be defined as either “per sample” or “per hour” as defined in the SIL Supplement (SILSUPP) in §C.2.3.9.2. Notes. — 1. For GNSS position sources the HIL or HPL is provided with a probability of 1x10 -7 per hour, which should be used to set the SIL to 3. 2. The GPS defined HPL probability rate of 10 -7 per hour is based on the GPS constellation fault rate of 10 -4 per hour and a 10 -3 probability of missed detection, given that the fault occurs. Different containment radii indicated by the HPL are all defined at the missed detection probability of 10 -3 . 3. Fault detection is an essential consideration in determining the SIL parameter. Fault detection assures, at a specified probability of missed detection, that the error is no greater than a specified limit without an alert. 4. For alternate ADS-B position sources to report integrity, they will need to be certified for their fault detection characteristics. The “SIL” subfield is encoded in accordance with Table C-15. For installations where the SIL value is being dynamically updated, if an update has not been received from an on-board data source for SIL within the past 2 seconds, then the SIL subfield shall be encoded as a value of ZERO (0), indicating “Unknown.” Table C-15. Source Integrity Level (SIL) Encoding SIL Coding (Binary) (Decimal) 00 0 01 1 Probability of Exceeding the NIC Containment Radius (RC) Unknown or > 1 x 10 -3 per flight hour or per sample ≤ 1 × 10 -3 per flight hour or per sample ≤ 1 × 10 -5 per flight hour or per sample ≤ 1 × 10 -7 per flight hour or per sample Draft 10 2 11 3 C.2.3.9.12 Status of MCP/FCU Mode Bits The “Status of MCP / FCU Mode Bits” subfield is a 1-bit (“ME” bit 47, Message bit 79) field that shall be used to indicate whether the mode bits (“ME” bits 48, 49, 50, and 52 and 54, Message bits 80, 81, 82, and 84, and 86) are actively being populated (e.g., set) in the Target State and Status Message in accordance with Table C-16. If information is provided to the ADS-B Transmitting Subsystem to set either “ME” bit 48, 49, 50, or 52 or 54 (Message bit 80, 81, 82, or 84 or 86) to either “0” or “1,” then bit 47 shall be set to ONE (1). Otherwise, bit 47 shall be set to ZERO (0). 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-27 Table C-16. “Status of MCP/FCU Mode Bits” Subfield Encoding Coding (“ME” Bit 47) 0 1 Meaning No Mode Information is being provided in “ME” bits 48, 49, 50, or 52 or 54 (Message bits 80, 81, 82, or 84 or 86) Mode Information is deliberately being provided in “ME” bits 48, 49, 50, or 52, or 54 (Message bits 80, 81, 82, or 84, or 86) C.2.3.9.13 Autopilot Engaged The “Autopilot Engaged” subfield is a 1-bit (“ME” bit 48, Message bit 80) field that shall be used to indicate whether the autopilot system is engaged or not. a. The ADS-B Transmitting Subsystem shall accept information from an appropriate interface that indicates whether or not the Autopilot is engaged. b. The ADS-B Transmitting Subsystem shall set “ME” bit 48 (Message bit 80) in accordance with Table C-17. Coding (“ME” Bit 48) Table C-17. “Autopilot Engaged” Subfield Encoding Meaning 0 Autopilot is NOT Engaged (e.g., not actively coupled and flying the aircraft) 1 Autopilot is Engaged (e.g., actively coupled and flying the aircraft) C.2.3.9.14 VNAV Mode Engaged The “VNAV Mode Engaged” subfield is a 1-bit (“ME” bit 49, Message bit 81) field that shall be used to indicate whether the Vertical Navigation Mode is active or not. a. The ADS-B Transmitting Subsystem shall accept information from an appropriate interface that indicates whether or not the Vertical Navigation Mode is active. Draft b. The ADS-B Transmitting Subsystem shall set “ME” bit 49 (Message bit 81) in accordance with Table C-18. Coding (“ME” Bit 49) Table C-18. “VNAV Engaged” Subfield Encoding 0 VNAV Mode is NOT Active 1 VNAV Mode is Active Meaning C.2.3.9.15 Altitude Hold Mode The “Altitude Hold Mode” subfield is a 1-bit (“ME” bit 50, Message bit 82) field that shall be used to indicate whether the Altitude Hold Mode is active or not. a. The ADS-B Transmitting Subsystem shall accept information from an appropriate interface that indicates whether or not the Altitude Hold Mode is active. b. The ADS-B Transmitting Subsystem shall set “ME” bit 50 (Message bit 82) in accordance with Table C-19. 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: DRAFT - Working Paper ASP TSGWP11-0
Page 169 and 170: Appendix B B-33 MB FIELD DRAFT - Wo
Page 177 and 178: Appendix B B-41 CF value ICAO/Mode
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: 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 227 and 228: Appendix C C-39 Notes.— DRAFT - W
Page 229 and 230: Appendix C C-41 Notes.— DRAFT - W
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 265 and 266:
Page 267 and 268:
Page 269 and 270:
Page 271 and 272:
Page 273 and 274:
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

Create successful ePaper yourself

Delete template?

Save as template?