Technical Provisions for Mode S Services and Extended Squitter

More documents

Recommendations

Info

CD-12 Technical Provisions for Mode S Services and Extended Squitter General example for the loading of data in register 40 16 DRAFT - Working Paper ASP TSGWP11-01 for review by the TSG during the meeting in June 2011 in Paris Hypothesis on information available to transponder The FMS selected altitude (calculated by the FMS) and the target altitude source information are available on aircraft buses (this is not necessarily the case today) as well as the MCP/FCU mode bits. Bits 48 and 54 are set to 1 all the time with this hypothesis. The reverse hypothesis would require bits 48–51 and bits 54–56 to be all set to 0 and the FMS selected altitude field to be all zeroed. Pilot selects ALT HOLD mode The autopilot holds the current aircraft altitude MCP/FCU selected altitude captured (ALT CAP) VNAV mode automatically disengaged ALT HOLD mode automatically selected New cleared flight level entered in MCP/FCU Selection of VNAV or equivalent mode where flight is controlled by FMS Pilot disengages autopilot and flights manual Intermediate FMS selected altitude capture and hold Draft Autopilot/flight director engaged Cleared flight level 1 (FL100) entered in MCP/FCU Holding last MCP/FCU selected altitude New FMS selected altitude FL 350 FL 300 Selected altitude calculated by the FMS in order to fulfil flight plan and best vertical profile FL 250 MCP/FCU Selected altitude = Cleared flight level FL 100 Aircraft flight path MCP/FCU selected altitude 100 300 300 300 300 300 300 FMS selected altitude 250 250 250 350 350 350 350 MCP/FCU mode bits Provided 1 1 1 1 1 1 1 VNAV 0 1 1 1 0 0 0 Alt hold 1 0 0 0 1 0 1 Approach 0 0 0 0 0 0 0 Figure D-2. General example for the loading of data in register 4016 Register 4016 content DRAFT - Working Paper ASP TSGWP11-01 for review by the TSG during the meeting in June 2011 in Paris FCU/MCP FMS FMS FCU/MCP FCU/MCP Unknown Altitude Target altitude (Unknown, Altitude, FCU/MCP, FMS) 1 2 3 4 5 6 7 Step
Appendix CD CD-13 CD.2.4.4.1.2 Possible uses of selected altitude and target altitude 1. MCP/FCU selected altitude will be downlinked as an additional read-back in order to check that the cleared flight level has been correctly understood and entered in the airborne system by the pilot. 2. Target altitude and associated mode of flight may be of interest to reduce the Short Term Conflict Alert false alarm rate. CD.2.4.4.1.3 Target altitude implementation difficulties It is recognized that all information to determine which altitude is the target altitude or which mode of flight is currently used may not always be available to the transponder in the current airborne implementation. In addition it may be very dependent on the platform. It is therefore preferable to set to 0 the corresponding bits of register 4016 rather than sending wrong information. CD.2.4.4.2 TRANSPONDER REGISTER NUMBER 4016 ON AIRBUS AIRCRAFT CD.2.4.4.2.1 Target altitude In order to clarify how aircraft intention information is reported in transponder register 4016 a mapping (Table CD-2) has been prepared to illustrate, for a number of conditions: a) how the altitude data are derived that are loaded into transponder register 4016, and b) how the corresponding source bits are set. CD.2.4.4.2.1.1 A330/A340 family Auto pilot or flight director status (AP on and FD on/off) or (AP off and FD on) DRAFT - Working Paper ASP TSGWP11-01 for review by the TSG during the meeting in June 2011 in Paris Table CD-2. Transponder register number 4016 on Airbus A330/340 aircraft Auto pilot or flight director vertical mode Conditions: vertical status/altitude (FCU, FMS or aircraft) Target altitude used Bit 55 Bit 56 Draft Vertical speed (V/S) V/S > ( ( () A/C ALT / 0 0 V/S = 0 A/C ALT 0 1 FPA > ( ( () A/C ALT / 0 0 FPA = 0 A/C ALT 0 1 Aircraft operating with FCU altitude FCU ALT 1 0 Aircraft capturing a constrained altitude imposed by the FMS FMS ALT 1 1 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:
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 253 and 254: Appendix C C-65 Register 0A16 Figur
Page 255 and 256: DRAFT - Working Paper ASP TSGWP11-0
Page 259 and 260: Appendix C C-71 Table C-37. CF Fiel
Page 287 and 288: Appendix CD CD-3 ACTIONS EVENTS DRA
Page 291 and 292: Appendix CD CD-7 too many broadcast
Page 295: DRAFT - Working Paper ASP TSGWP11-0
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 307 and 308: Appendix CD CD-23 CD.2.4.7.5 BINARY
Page 311 and 312: Appendix CD CD-27 Zone no. DRAFT -
Page 315 and 316: Appendix CD CD-31 CD.4 IMPLEMENTATI
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?