曝光臺(tái) 注意防騙 網(wǎng)曝天貓店富美金盛家居專(zhuān)營(yíng)店坑蒙拐騙欺詐消費(fèi)者

lists the message elements and their respective message
intents/use.
14.1.2.1 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.
14.1.2.2 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.
14.1.2.3 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).
14.1.3 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.
14.1.4 Whenever textual presentation is required, the
English language shall be displayed as a minimum.
14.1.5 Where applicable, the communication procedures
for the provision of CPDLC shall be in accordance with Annex
10, Volume III, Part I, Chapter 3. Message element intent and
text and associated procedures are, in general, consistent with
Chapter 12 — Phraseologies. It is, however, recognized that
the CPDLC message set and the associated procedures differ
somewhat from the voice equivalent used because of the
differences between the two media; one being direct-speech
and the other an exchange of data, the latter of which can be
displayed and/or printed.
14.2 ESTABLISHMENT OF CPDLC
14.2.1 CPDLC shall be established in sufficient time to
ensure that the aircraft is communicating with the appropriate
ATC unit. Information concerning when and, where
applicable, where, the air or ground systems should establish
CPDLC, shall be published in Aeronautical Information
Publications.
14.2.2 Airborne-initiated CPDLC
14.2.2.1 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.
14.2.2.2 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.
14.2.3 ATC unit-initiated CPDLC
14.2.3.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.
14.2.3.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.
14.3 EXCHANGE OF OPERATIONAL
CPDLC MESSAGES
14.3.1 The controller or pilot shall construct CPDLC
messages using the defined message set, a free text message or
a combination of both.
14-2 Air Traffic Management (PANS-ATM)
1/11/01
Note.— See Appendix 5 for the CPDLC message set
including message intent/use and the respective message
elements.
14.3.1.1 The use of long messages or messages with
multiple clearance 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).
14.3.1.2 When CPDLC is being used, and the intent of
the message is included in the CPDLC message set contained
in Appendix 5, the associated message shall be used.
14.3.1.3 Except as provided by 14.3.5.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.
14.3.1.4 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.
14.3.2 Message attributes dictate certain message handling
requirements for the CPDLC user receiving a message.
Each CPDLC message has three attributes: Urgency, Alert and
Response.
14.3.2.1 URGENCY
The urgency attribute delineates the queuing requirements for
received messages that are displayed to the end-user. Urgency
　
中國(guó)航空網(wǎng) m.k6050.com
航空翻譯 www.aviation.cn
本文鏈接地址：Air Traffic Management 下(20)