Publication: Magyar Közlöny
Issue: MK-2009-104 (Year: 2009, Number: 104)
Era: 2004-2010
Section: 
Paragraph Index: 1752

b) when an expected communication from an aircraft has not been received within a time period such that the occurrence of a communication failure is suspected. Note.— A specific time period may be prescribed by the appropriate ATS Authority. 5.2.2.7.2.3 Recommendation.— If the attempts specified in 5.2.2.7.2.1 fail, the aeronautical station should transmit messages addressed to the aircraft, other than messages containing air traffic control clearances, by blind transmission on the frequency(ies) on which the aircraft is believed to be listening. 5.2.2.7.2.4 Blind transmission of air traffic control clearances shall not be made to aircraft, except at the specific request of the originator. 5.2.2.7.3 Notification of communications failure. The air-ground control radio station shall notify the appropriate air traffic services unit and the aircraft operating agency, as soon as possible, of any failure in air-ground communication. 5.2.3 HF message handling 5.2.3.1 General 5.2.3.1.1 PANS.— When operating within a network, an aircraft station should, in principle, whenever communications conditions so permit, transmit its messages to the stations of the network from which they can be most readily delivered to their ultimate destinations. In particular, aircraft reports required by air traffic services should be transmitted to the network station serving the flight information centre or area control centre in whose area the aircraft is flying. Conversely, messages to aircraft in flight should, whenever possible, be transmitted directly to the aircraft by the network station serving the location of the originator. Note.— Exceptionally, an aircraft may need to communicate with an aeronautical station outside the network appropriate to its particular route segment. This is permissible, provided it can be done without interrupting the continuous watch with the communication network appropriate to the route segment, when such watch is required by the appropriate ATS Authority, and provided it does not cause undue interference with the operation of other aeronautical stations. 5.2.3.1.2 PANS.— Messages passed from an aircraft to a network station should, whenever possible, be intercepted and acknowledged by other stations of the network, which serve locations where the information is also required. Note 1.— Determination of the arrangements for dissemination of air-ground messages without address will be a matter for multilateral or local agreement. Note 2.— In principle, the number of stations required to intercept are to be kept to a minimum consistent with the operational requirement. 5.2.3.1.2.1 PANS.— Acknowledgement of intercept should be made immediately after the acknowledgement of receipt by the station to which the message was passed. 5.2.3.1.2.2 PANS.— Acknowledgement of an intercept message should be made by transmitting the radio call sign of the station having intercepted the message, followed by the word ROGER, if desired, and the call sign of the station having transmitted the message. 5.2.3.1.2.3 PANS.— In the absence of acknowledgement of intercept within one minute, the station accepting the message from the aircraft should forward it, normally over the aeronautical fixed service, to the station(s) which have failed to acknowledge intercept. 5.2.3.1.2.3.1 PANS.— If, in abnormal circumstances, forwarding is necessary using the air-ground channels, the provisions of 5.2.2.3.4 should be observed. 5.2.3.1.2.4 PANS.— When such forwarding is done over the aeronautical fixed telecommunication network, the messages should be addressed to the network station(s) concerned. 5.2.3.1.2.5 PANS.— The station(s) to which the messages have been forwarded should carry out local distribution of them in the same way as if they had been received directly from the aircraft over the air-ground channel. 5.2.3.1.2.6 The aeronautical station receiving an airreport or a message containing meteorological information transmitted by an aircraft in flight shall forward the message without delay: 1) to the air traffic services unit and meteorological offices associated with the station; 2) to the aircraft operating agency concerned or its representative when that agency has made a specific request to receive such messages. 5.2.3.1.3 PANS.— The provisions of 5.2.3.1.2 should also be applied, if practicable, in non-network operation. 24/11/05 No. 80 ANNEX 10 — VOLUME II 8-1 1/11/01 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 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. Nonessential 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. 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. Annex 10 — Aeronautical Telecommunications Volume II 1/11/01 8-2 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. 8.2.8.5 When the airborne system detects that CPDLC is available for operational use, it shall send the CPDLC downlink message element CURRENT DATA AUTHORITY. 8.2.8.6 Airborne-initiated CPDLC 8.2.8.6.1 PANS.— When an ATC unit receives an unexpected request for CPDLC from an aircraft, the circumstances leading to the request shall be obtained from the aircraft to determine further action. 8.2.8.6.2 PANS.— When the ATC unit rejects a request for CPDLC, it shall provide the pilot with the reason for the rejection using an appropriate CPDLC message. 8.2.8.7 ATC unit-initiated CPDLC 8.2.8.7.1 An ATC unit shall only establish CPDLC with an aircraft if the aircraft has no CPDLC link established, or when authorized by the ATC unit currently having CPDLC established with the aircraft. 8.2.8.7.2 When a request for CPDLC is rejected by an aircraft, the reason for the rejection shall be provided using CPDLC downlink message element NOT CURRENT DATA AUTHORITY or message element NOT AUTHORIZED NEXT DATA AUTHORITY, as appropriate. Local procedures shall dictate whether the reason for rejection is presented to the controller. No other reasons for airborne rejection of ATC unitinitiation of CPDLC shall be permitted. 8.2.9 Exchange of operational CPDLC messages 8.2.9.1 Controllers and pilots shall construct CPDLC messages using the defined message set, a free text message or a combination of both. 8.2.9.1.1 PANS.— When CPDLC is being used, and the intent of the message is included in the CPDLC message set contained in the PANS-ATM, Appendix 5, the associated message shall be used. 8.2.9.1.2 PANS.— Except as provided by 8.2.12.1, when a controller or pilot communicates via CPDLC, the response should be via CPDLC. When a controller or pilot communicates via voice, the response should be via voice. 8.2.9.1.3 PANS.— Whenever a correction to a message sent via CPDLC is deemed necessary or the contents of a message needs to be clarified, the controller or pilot shall use the most appropriate means available for issuing the correct details or for providing clarification. Note.— The following procedures may be applied by the controller, in terms of correcting clearances, instructions or information, or by a pilot, in terms of correcting a reply to an uplink message or correcting previously advised requests or information. 8.2.9.1.3.1 PANS.— When voice communications are used to correct a CPDLC message for which no operational response has yet been received, the controller’s or pilot’s transmission shall be prefaced by the phrase: “DISREGARD CPDLC (message type) MESSAGE, BREAK” — followed by the correct clearance, instruction, information or request. Note.— It is possible that, at the time the voice communicated clarification is transmitted, the CPDLC message being referred to has not yet reached the recipient, or has reached the recipient but has not been acted upon, or has reached the recipient and has been acted upon. 8.2.9.1.3.2 PANS.— When referring to and identifying the CPDLC message to be disregarded, caution should be exercised in its phrasing so as to avoid any ambiguity with the issuance of the accompanying corrected clearance, instruction, information or request. Note.— For example, if SAS445, maintaining FL290, had been instructed via CPDLC to climb to FL350, and the controller needs to correct the clearance utilizing voice communications, the following phrase might be used: SAS445 DISREGARD CPDLC CLIMB CLEARANCE MESSAGE, BREAK, CLIMB TO FL310. 22/11/07 No. 82 Chapter 8 Annex 10 — Aeronautical Telecommunications 8-3 1/11/01 8.2.9.1.3.3 PANS.— If a CPDLC message that requires an operational response is subsequently negotiated via voice, an appropriate CPDLC message closure response shall be sent to ensure proper synchronization of the CPDLC dialogue. This could be achieved either by explicitly instructing the recipient of the message via voice to close the dialogue or by allowing the system to automatically close the dialogue. 8.2.9.2 The composition of a CPDLC message shall not exceed five message elements, only two of which may contain the route clearance variable. 8.2.9.2.1 PANS.— The use of long messages or messages with multiple clearance elements, multiple clearance request elements or messages with a combination of clearances and information should be avoided where possible. Note.— Guidance material on the development of local operating procedures and CPDLC good operating technique can be found in the Human Factors Guidelines for Air Traffic Management (ATM) Systems (Doc 9758). 8.2.9.3 CPDLC ground systems and airborne systems shall be capable of using the CPDLC message urgency and alert attributes to alter presentations in order to draw attention to higher priority messages. Note.— Message attributes dictate certain message handling requirements for the CPDLC user receiving a message. Each CPDLC message has three attributes: urgency, alert and response attributes. When a message contains multiple message elements, the highest precedence message element attribute type becomes the attribute type for the entire message. 8.2.9.3.1 The urgency attribute shall delineate the queuing requirements for received messages that are displayed to the end-user. Urgency types are presented in Table 8-1. 8.2.9.3.2 The alert attribute shall delineate the type of alerting required upon message receipt. Alert types are presented in Table 8-2. 8.2.9.3.3 The response attribute shall delineate valid responses for a given message element. Response types are presented in Table 8-3 for uplink messages and Table 8-4 for downlink messages. 8.2.9.3.3.1 PANS.— When a multi-element message requires a response, and the response is in the form of a single message element, the response shall apply to all message elements. Note.— For example, a multi-element message containing CLIMB TO FL310 MAINTAIN MACH.84, a WILCO response applies to, and indicates compliance with, both elements of the message. 8.2.9.3.3.2 PANS.— When a single message element clearance or any part of a multi-element clearance message cannot be complied with, the pilot shall send an UNABLE response for the whole message. 8.2.9.3.3.3 PANS.— The controller shall respond with an UNABLE message that applies to all elements of the request when no element(s) of a single or multi-element clearance request can be approved. The current clearance(s) shall not be restated. 8.2.9.3.3.4 PANS.— When a multi-element clearance request can only be partially accommodated, the controller shall respond with an UNABLE message applying to all the message elements of the request and, if appropriate, include a reason and/or information on when a clearance may be expected. Table 8-1. Urgency Attribute (Uplink and Downlink) Table 8-2. Alert Attribute (Uplink and Downlink) Type Description Precedence D Distress U Urgent N Normal L Low Type Description Precedence H High M Medium L Low N No alerting required 22/11/07 No. 82 Annex 10 — Aeronautical Telecommunications Volume II 1/11/01 8-4 Table 8-3. Response Attribute (Uplink) Table 8-4. Response Attribute (Downlink) Type Response required Valid responses Precedence W/U Yes WILCO, UNABLE, STANDBY, NOT CURRENT DATA AUTHORITY, NOT AUTHORIZED NEXT DATA AUTHORITY, LOGICAL ACKNOWLEDGEMENT (only if required), ERROR A/N Yes AFFIRM, NEGATIVE, STANDBY, NOT CURRENT DATA AUTHORITY, NOT AUTHORIZED NEXT DATA AUTHORITY, LOGICAL ACKNOWLEDGEMENT (only if required), ERROR R Yes ROGER, UNABLE, STANDBY, NOT CURRENT DATA AUTHORITY, NOT AUTHORIZED NEXT DATA AUTHORITY, LOGICAL ACKNOWLEDGEMENT (only if required), ERROR Y Yes Any CPDLC downlink message, LOGICAL ACKNOWLEDGEMENT (only if required) N No, unless logical acknowledgement required LOGICAL ACKNOWLEDGEMENT (only if required), NOT CURRENT DATA AUTHORITY, NOT AUTHORIZED NEXT DATA AUTHORITY, ERROR Type Response required Valid responses Precedence Y Yes Any CPDLC uplink message, LOGICAL ACKNOWLEDGEMENT (only if required) N No, unless logical acknowledgement required LOGICAL ACKNOWLEDGEMENT (only if required), SERVICE UNAVAILABLE, FLIGHT PLAN NOT HELD, ERROR Chapter 8 Annex 10 — Aeronautical Telecommunications 8-5 1/11/01 Note.— A separate CPDLC message (or messages) may subsequently be transmitted to respond to those elements that can be accommodated. 8.2.9.3.3.5 PANS.— When all elements of a single or multi-element clearance request can be accommodated, the controller shall respond with clearances corresponding to each element of the request. This response should be a single uplink message. Note.— For example, while messages containing multielement clearance requests are to be avoided, a multi-element downlink message containing the indicated message elements: REQUEST CLEARANCE YQM YYG YYT YQX TRACK X EINN EDDF REQUEST CLIMB TO FL350 REQUEST MACH 0.84 could be responded to with CLEARED YQM YYG YYT YQX TRACK X EINN EDDF CLIMB TO FL350 REPORT MAINTAINING CROSS YYG AT OR AFTER 1150 NO SPEED RESTRICTION. 8.2.9.3.3.6 PANS.— When a CPDLC message contains more than one message element and the response attribute for the message is Y, when utilized, the single response message shall contain the corresponding number of replies in the same order. Note.— For example, a multi-element uplink message containing CONFIRM SQUAWK WHEN CAN YOU ACCEPT FL410 could be responded to with SQUAWKING 5525 WE CAN ACCEPT FL410 AT 1636Z 8.2.9.4 When a ground or airborne system generates the CPDLC message ERROR, the reason for the error shall be included in the message. 8.2.9.5 The appropriate ATS authority shall select those message elements contained in PANS-ATM, Appendix 5 that support operations in their airspace. Should an ATS authority choose to select a subset of the message elements, and a received message does not belong to this subset, the ATC unit shall respond by uplinking the message element SERVICE UNAVAILABLE. Note.— Further processing of the received message is not required. 8.2.9.5.1 Recommendation.— Only the uplink messages appropriate to a particular control sector’s operations should be provided to the controller. Note.— The CPDLC message set contained in PANS-ATM, Appendix 5 was developed to encompass different air traffic management environments. 8.2.9.5.2 When considered necessary by the appropriate ATS authority, additional pre-formatted free text messages shall be made available to the controller for those occasions where the CPDLC message set contained in the PANS-ATM does not provide for specific requirements. In such cases, a list of pre-formatted free text messages shall be established by the appropriate ATS authority, in consultation with operators and other ATS authorities that may be concerned. 8.2.9.5.3 Information concerning CPDLC message element subsets utilized and, if applicable, any additional preformatted free text messages, shall be published in aeronautical information publications. 8.2.9.6 Transfer of CPDLC Note.— Details on CPDLC transfer can be found in the Manual of Air Traffic Services Data Link Applications (Doc 9694). 8.2.9.6.1 PANS.— When CPDLC is transferred, the transfer of voice communications and CPDLC shall commence concurrently. 8.2.9.6.2 PANS.— When an aircraft is transferred from an ATC unit where CPDLC is available to an ATC unit where CPDLC is not available, CPDLC termination shall commence concurrent with the transfer of voice communications. 8.2.9.6.3 When a transfer of CPDLC results in a change of data authority, and there are still messages for which the closure response has not been received (i.e. messages outstanding), the controller transferring the CPDLC shall be informed. 8.2.9.6.3.1 If the controller needs to transfer the aircraft without replying to any downlink message(s) outstanding, the system shall have the capability to automatically send the appropriate closure response message(s). In such cases, the contents of any automatically sent closure response message(s) shall be promulgated in local instructions. 8.2.9.6.3.2 When the controller decides to transfer the aircraft without receiving pilot responses to any uplink message(s) outstanding, the ground system shall have the capability to automatically end the dialogue for each message prior to the transfer. 8.2.9.6.3.2.1 PANS.— The controller should revert to voice communications to clarify any ambiguity associated with the message(s) outstanding. 22/11/07 No. 82 Annex 10 — Aeronautical Telecommunications Volume II 1/11/01 8-6 8.2.9.6.4 When a transfer of CPDLC does not result in a change of data authority, and there are still messages outstanding, these messages shall either be forwarded to the appropriate controller or shall be closed in accordance with local instructions and, if necessary, letters of agreement. 8.2.10 Display of CPDLC messages Recommendation.— ATC units utilizing a CPDLC message contained in the PANS-ATM should display the associated text pertaining to that message as presented in the PANS-ATM, Appendix 5. 8.2.11 Free text messages PANS.— The use of free text messages by controllers or pilots, other than pre-formatted free text messages referred to in paragraph 8.2.9.5.2, should be avoided. Note.— Whilst it is recognized that non-routine and emergency situations may necessitate the use of free text, particularly when voice communication has failed, the avoidance of utilizing free text messages is intended to reduce the possibility of misinterpretation and ambiguity. 8.2.12 Emergencies, hazards and equipment failure procedures 8.2.12.1 PANS.— When a CPDLC emergency message is received, the controller shall acknowledge receipt of the message by the most efficient means available. 8.2.12.2 PANS.— When responding via CPDLC to a report indicating unlawful interference, uplink message ROGER 7500 shall be used. 8.2.12.3 PANS.— When responding via CPDLC to all other emergency or urgency messages, uplink message ROGER shall be used. 8.2.12.4 When a CPDLC message requires a logical acknowledgement and/or an operational response, and such a response is not received, the pilot or controller, as appropriate, shall be alerted. 8.2.12.5 Failure of CPDLC Note.— Action to be taken in the event of the failure of a single CPDLC message is covered in 8.2.12.7. 8.2.12.5.1 Recommendation.— A CPDLC failure should be detected in a timely manner. 8.2.12.5.2 The controller and pilot shall be alerted to a failure of CPDLC as soon as a failure has been detected. 8.2.12.5.3 PANS.— When a controller or pilot is alerted that CPDLC has failed, and the controller or pilot needs to communicate prior to CPDLC being restored, the controller or pilot should revert to voice, if possible, and preface the information with the phrase: CPDLC FAILURE. 8.2.12.5.4 PANS.— Controllers having a requirement to transmit information concerning a complete CPDLC ground system failure to all stations likely to intercept should preface such a transmission by the general call ALL STATIONS CPDLC FAILURE, followed by the identification of the calling station. Note.— No reply is expected to such general calls unless individual stations are subsequently called to acknowledge receipt. 8.2.12.5.5 PANS.— When CPDLC fails and communications revert to voice, all CPDLC messages outstanding should be considered not delivered and the entire dialogue involving the messages outstanding should be recommenced by voice. 8.2.12.5.6 PANS.— When CPDLC fails but is restored prior to a need to revert to voice communications, all messages outstanding should be considered not delivered and the entire dialogue involving the messages outstanding should be recommenced via CPDLC. 8.2.12.6 Intentional shutdown of CPDLC 8.2.12.6.1 When a system shutdown of the communications network or the CPDLC ground system is planned, a NOTAM shall be published to inform all affected parties of the shutdown period and if necessary, the details of the voice communication frequencies to be used. 8.2.12.6.2 Aircraft currently in communication with the ATC unit shall be informed by voice or CPDLC of any imminent loss of CPDLC service. 8.2.12.6.3 The controller and pilot shall be provided with the capability to abort CPDLC. 8.2.12.7 Failure of a single CPDLC message PANS.— When a controller or pilot is alerted that a single CPDLC message has failed, the controller or pilot shall take one of the following actions, as appropriate:

Source: https://magyarkozlony.hu/hivatalos-lapok/1f7c6b0e16b4b71a92e5ad24416008bbe2e26aab/dokumentumok/710811d1f7f958a2990684d0cbf918e84f5497e5/letoltes