Technical Provisions for Mode S Services and Extended Squitter

More documents

Recommendations

Info

A-12 Technical Provisions for Mode S Services and Extended Squitter second. DRAFT - Working Paper ASP TSGWP11-01 for review by the TSG during the meeting in June 2011 in Paris A.2.3.3.5 LATITUDE/LONGITUDE The latitude/longitude field in the surface message shall be a 34-bit field containing the latitude and longitude coding of the aircraft’s surface position. The latitude (Y) and longitude (X) shall each occupy 17 bits. The surface latitude and longitude encodings shall contain the low-order 17 bits of the 19-bit CPR-encoded values defined in §AC.2.6. Note 1.— The unambiguous range for local decoding of surface messages is 166.5 km (90 NM). The positional accuracy maintained by the surface CPR encoding is approximately 1.25 metres. The latitude/longitude encoding is also a function of the CPR format value (the “F” bit) described above. Note 2.— Although the positional accuracy of the surface CPR encoding is approximately 1.25 meters in most cases, the longitude position accuracy may only be approximately 3.0 meters when the latitude is either –87.0 ±1.0 degrees, or +87 ±1.0 degrees. A.2.3.3.5.1 Extrapolating position (when T = 1) This extrapolation shall conform to §A.2.3.2.3.1 (substitute “surface” for “airborne” where appropriate). A.2.3.3.5.2 Extrapolating position (when T = 0) This extrapolation shall conform to §A.2.3.2.3.2 (substitute “surface” for “airborne” where appropriate). A.2.3.3.5.3 Time-out when new position data are unavailable This time-out shall conform to §A.2.3.2.3.3 (substitute “surface” for “airborne” where appropriate). Draft A.2.3.4 IDENTIFICATION AND CATEGORY FORMAT The identification and category squitter shall be formatted as specified in the definition of transponder register 0816. A.2.3.5 AIRBORNE VELOCITY FORMAT The airborne velocity squitter shall be formatted as specified in the definition of transponder register number 0916 and in the following paragraphs. A.2.3.5.1 SUBTYPES 1 AND 2 Subtypes 1 and 2 of the airborne velocity format shall be used when the transmitting aircraft’s velocity over ground is known. Subtype 1 shall be used at subsonic velocities while subtype 2 shall be used when the velocity exceeds 1 022 kt. This message shall not be broadcast if the only valid data are the intent change flag and the IFR capability flag (see §A.2.3.5.3, §A.2.3.5.4). After initialization, the broadcast shall be suppressed by loading register 0916 with all zeros and then discontinuing the updating of the register until data input is available again. DRAFT - Working Paper ASP TSGWP11-01 for review by the TSG during the meeting in June 2011 in Paris
Appendix A A-13 The supersonic version of the velocity coding shall be used if either the east-west OR north-south velocities exceed 1 022 kt. A switch to the normal velocity coding shall be made if both the east-west AND north-south velocities drop below 1 000 kt. A.2.3.5.2 SUBTYPES 3 and 4 Subtypes 3 and 4 of the airborne velocity format shall be used when the transmitting aircraft’s velocity over ground is not known. These subtypes substitute airspeed and heading for the velocity over ground. Subtype 3 shall be used at subsonic velocities, while subtype 4 shall be used when the velocity exceeds 1 022 kt. This message shall not be broadcast if the only valid data are the intent change flag and the IFR capability flag (see §A.2.3.5.3, §A.2.3.5.4). After initialization, broadcast shall be suppressed by loading register 0916 with all zeros and then discontinuing the updating of the register until data input is available again. The supersonic version of the velocity coding shall be used if the airspeed exceeds 1 022 kt. A switch to the normal velocity coding shall be made if the airspeed drops below 1 000 kt. A.2.3.5.3 INTENT CHANGE FLAG IN AIRBORNE VELOCITY MESSAGES An intent change event shall be triggered 4 seconds after the detection of new information being inserted in registers 4016 to 4216. The code shall remain set for 18 ±1 second following an intent change. Intent change flag coding: 0 = no change in intent 1 = intent change Note 1.— Register 4316 is not included since it contains dynamic data which will be continuously changing. Note 2.— A four-second delay is required to provide for settling time for intent data derived from manually set devices. A.2.3.5.4 IFR CAPABILITY FLAG (IFR) IN AIRBORNE VELOCITY MESSAGES Draft The IFR capability flag shall be a 1-bit (bit 10) subfield in the subtypes 1, 2, 3 and 4 airborne velocity messages. IFR=1 shall signify that the transmitting aircraft has a capability for applications requiring ADS-B equipage class A1 or above. Otherwise, IFR shall be set to 0. A.2.3.5.5 RESERVED DRAFT - Working Paper ASP TSGWP11-01 for review by the TSG during the meeting in June 2011 in Paris A.2.3.5.6 MAGNETIC HEADING IN AIRBORNE VELOCITY MESSAGES A.2.3.5.6.1 Magnetic heading status This 1-bit field shall define the availability of the magnetic heading value. Coding for this field shall be: 0 = not available and 1 = available. 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 31 and 32: Appendix A A-7 TYPE Code Format Hor
Page 35: DRAFT - Working Paper ASP TSGWP11-0
Page 39 and 40: Appendix A A-15 The transponder sha
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 71 and 72: Appendix A A-47 MB FIELD 1 2 3 4 5
Page 79 and 80: Appendix A A-55 MB FIELD 1 BDS A,8
Page 87 and 88:
Appendix A A-63 MB FIELD DRAFT - Wo
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:
DRAFT - Working Paper ASP TSGWP11-0
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:
Page 173 and 174:
Page 175 and 176:
Page 177 and 178:
Appendix B B-41 CF value ICAO/Mode
Page 179 and 180:
Page 181 and 182:
Page 183 and 184:
Page 185 and 186:
Page 187 and 188:
Page 189 and 190:
Page 191 and 192:
Page 193 and 194:
Appendix C C-5 Table C-2. “TYPE
Page 195 and 196:
Page 197 and 198:
Page 199 and 200:
Appendix C C-11 C.2.3.2.2 Time Sync
Page 201 and 202:
Page 203 and 204:
Page 205 and 206:
Page 207 and 208:
Page 209 and 210:
Page 211 and 212:
Page 213 and 214:
Appendix C C-25 Notes.— DRAFT - W
Page 215 and 216:
Page 217 and 218:
Page 219 and 220:
Msg Bit # “ME” Bit # Appendix C
Page 221 and 222:
Appendix C C-33 Msg Bit # "ME” Bi
Page 223 and 224:
Page 225 and 226:
Page 227 and 228:
Page 229 and 230:
Page 231 and 232:
Appendix C C-43 Notes. — DRAFT -
Page 233 and 234:
Page 235 and 236:
Page 237 and 238:
Page 239 and 240:
Appendix C C-51 3. The decoded posi
Page 241 and 242:
Page 243 and 244:
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 249 and 250:
Page 251 and 252:
Page 253 and 254:
Appendix C C-65 Register 0A16 Figur
Page 255 and 256:
Page 257 and 258:
Page 259 and 260:
Appendix C C-71 Table C-37. CF Fiel
Page 261 and 262:
Page 263 and 264:
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?