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 CD-10 Technical Provisions for Mode S Services and Extended Squitter • Unknown. — MCP/FCU mode bits: • VNAV indicates when a VNAV or equivalent mode in which the A/P is controlled by FMS is selected. • ALT HOLD indicates when A/P Alt Hold mode is selected. It does not correspond to a general altitude capture and does not cover VNAV hold situation. • Approach indicates that a mode to capture ILS localizer and glide slope is engaged. — Priority of MCP/FCU selected altitude on FMS selected altitude The MCP/FCU selected altitude is the altitude that the aircraft shall not violate and therefore it has always priority on FMS selected altitude. Explanation of the different steps in Figure CD-2: Generally, Figure CD-2 shows a theoretical sequence of cases which should not be considered as a real operational sequence. For example, some steps may be more realistic when the aircraft is in descent. Step 1: The MCP/FCU selected altitude has been set to first cleared flight level (FL100). The Autopilot/Flight Director is engaged and the aircraft is holding the latest MCP/FCU selected altitude which has been reached before step 1. The target altitude is the MCP/FCU selected altitude. VNAV mode is not engaged. The FMS selected altitude is not the target altitude. Step 2: A new clear flight level has been allocated to the aircraft by ATC. The pilot has entered this value into the MCP/FCU resulting in a new MCP/FCU selected altitude. The pilot has engaged the VNAV mode. The aircraft speed/path is determined by the FMS. The FMS contains a flight path with an altitude restriction at a given waypoint (FL250). The FMS selected altitude corresponds to the associated altitude restriction. This FMS selected altitude is less than the MCP/FCU selected altitude and therefore becomes the target altitude to which the aircraft is climbing. Step 3: There is an altitude restriction associated with a waypoint. The aircraft has captured and is maintaining the FMS selected altitude until crossing the waypoint. The VNAV mode remains active. In an operational environment, aircrew should also set the MCP/FCU altitude to the intermediate levels on a stepped climb SID if workload permits. Draft Step 4: The waypoint with restricted altitude is passed. A new FMS selected altitude is now valid. The aircraft resumes its climbing to try to reach this new FMS selected altitude. VNAV mode is still engaged. Although the aircraft is trying to reach the FMS selected altitude (FL350) it will level off at the MCP/FCU selected altitude, which is lower than the FMS selected altitude, therefore the selected altitude is the MCP/FCU selected altitude. Step 5: The MCP/FCU selected altitude is lower than the FMS selected altitude. The aircraft therefore first approaches this MCP/FCU selected altitude which is a limit to not violate. This MCP/FCU altitude is captured and held by the aircraft. This automatically disengages the VNAV mode. Step 6: The flight crew has disengaged the autopilot and is flying the aircraft manually. The target altitude is not known. However on an operational point of view it must be noted that such mode would not be allowed in regulated airspace unless the aircrew had declared an emergency or had obtained a new ATC clearance. In the latter case the ATC clearance should be entered in the MCP/FCU. It is more probable that this case may happen on a “descent when ready” profile. In all cases, the MCP/FCU selected altitude may still be useful because it should be the value used in the altitude alerter. Step 7: The pilot selects altitude hold (Alt Hold or equivalent mode) making the current altitude equivalent to the target altitude. Note that although MCP/FCU selected altitude could become the same (pilot entering the new flight level in the MCP/FCU) this is not mandatory and, therefore, only altitude represents with full confidence the level the aircraft is maintaining. 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 CD CD-11 CD.2.4.4.1.1 Target Altitude Summary If MCP/FCU altitude is between your current altitude and FMS Selected Altitude, then the target altitude is MCP/FCU. If VNAV is engaged and the previous case is not in effect, then FMS is the target altitude. If Alt Hold is selected and the current altitude is not equal to either of the selected altitudes, then target altitude is altitude. Draft 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: DRAFT - Working Paper ASP TSGWP11-0
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 287 and 288: Appendix CD CD-3 ACTIONS EVENTS DRA
Page 291 and 292: Appendix CD CD-7 too many broadcast
Page 293: DRAFT - Working Paper ASP TSGWP11-0
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 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?