Language
RUEN
ES
FR
AR
CH
Login
RUEN
ES
FR
AR
CH
Annex 10. Vol 2. Edition 6
CORRIGENDUM NO. 2
Buy access
INFO
Text
Editions
Modifies
Links To
Links From
In Catalogs
search
Annex 10, Volume II Sixth Edition Corrigendum No. 2 English, Arabic, Chinese, French, Russian, Spanish 30/9/14 INTERNATIONAL STANDARDS, AND RECOMMENDED PRACTICES AND PROCEDURES FOR AIR NAVIGATION SERVICES AERONAUTICAL TELECOMMUNICATIONS ANNEX 10 TO THE CONVENTION ON INTERNATIONAL CIVIL AVIATION VOLUME II COMMUNICATION PROCEDURES including those with PANS status SIXTH EDITION JULY 2001 CORRIGENDUM NO. 2 1. Please replace existing pages 8-1, 8-8 and 8-9 by the attached new pages bearing the notation Corr. 2. 2. Record the entry of this corrigendum on page ii.
ANNEX 10 VOLUME II 8-1 1/11/01 13/11/14 No. 89 CHAPTER 8. AERONAUTICAL MOBILE SERVICE DATA LINK COMMUNICATIONS 8.1 GENERAL Note 1. While the provisions of Chapter 8 are based primarily on the use of controller-pilot data link communications CPDLC, the provisions of 8.1 would apply to other data link applications, where applicable, including automatic dependent surveillance contract ADS-C and data link-flight information services e.g. D-ATIS, D-VOLMET, etc.. Note 2. For the purposes of these provisions, the communication procedures applicable to the aeronautical mobile service, as appropriate, also apply to the aeronautical mobile satellite service. 8.1.1 Composition of data link messages 8.1.1.1 The text of messages shall be composed in standard message format e.g. CPDLC message set, in plain language or in abbreviations and codes, as prescribed in 3.7. Plain language shall be avoided when the length of the text can be reduced by using appropriate abbreviations and codes. Non-essential words and phrases, such as expressions of politeness, shall not be used. 8.1.1.2 The following characters are allowed in the composition of messages Letters ABCDEFGHIJKLMNOPQRSTUVWXYZ upper case only Figures 1 2 3 4 5 6 7 8 9 0 Other signs - hyphen question mark colon open bracket close bracket . full stop, period, or decimal point , comma apostrophe double hyphen or equal sign / oblique plus sign and the space character. Characters other than those listed above shall not be used in messages. 8.1.1.3 Roman numerals shall not be employed. If the originator of a message wishes the addressee to be informed that Roman figures are intended, the Arabic figure or figures shall be written and preceded by the word ROMAN. 30/9/14 Corr. 2
Annex 10 Aeronautical Telecommunications Volume II 1/11/01 8-2 13/11/14 No. 89 8.1.2 Display of data link messages 8.1.2.1 Ground and airborne systems shall allow for messages to be appropriately displayed, printed when required, and stored in a manner that permits timely and convenient retrieval should such action be necessary. 8.1.2.2 Whenever textual presentation is required, the English language shall be displayed as a minimum. 8.2 CPDLC PROCEDURES Note. The CPDLC message set referred to in this section can be found in the PANS-ATM, Appendix 5. 8.2.1 In all communications the highest standard of discipline shall be observed at all times. 8.2.1.1 Recommendation. Consequences of human performance, which could affect the accurate reception and comprehension of messages, should be taken into consideration when composing a message. Note. Guidance material on human performance can be found in the Human Factors Training Manual Doc 9683 and Human Factors Guidelines for Air Traffic Management ATM Systems Doc 9758. 8.2.2 Ground and airborne systems shall provide controllers and pilots with the capability to review and validate any operational messages they send. 8.2.3 Ground and airborne systems shall provide controllers and pilots with the capability to review, validate and when applicable, acknowledge any operational messages they receive. 8.2.4 The controller shall be provided with the capability to respond to messages, including emergencies, to issue clearances, instructions and advisories, and to request and provide information, as appropriate. 8.2.5 The pilot shall be provided with the capability to respond to messages, to request clearances and information, to report information, and to declare or cancel an emergency. 8.2.6 The pilot and the controller shall be provided with the capability to exchange messages which do not conform to defined formats i.e. free text messages. 8.2.7 Unless specified by the appropriate ATS authority, voice read-back of CPDLC messages shall not be required. 8.2.8 Establishment of CPDLC 8.2.8.1 The controller and the pilot shall be informed when CPDLC has been successfully established. 8.2.8.2 PANS. CPDLC shall be established in sufficient time to ensure that the aircraft is communicating with the appropriate ATC unit. 8.2.8.3 The controller and pilot shall be informed when CPDLC is available for operational use, at initial establishment, as well as on resumption of CPDLC after a failure. 8.2.8.4 The pilot shall be able to identify the air traffic control unit providing the air traffic control service at any time while the service is being provided.
EXAMPLE
To view full book Buy access
EXAMPLE
To view full book Buy access
EXAMPLE
To view full book Buy access
EXAMPLE
To view full book Buy access
Table Of Contents