AMC1 ACNS.B.DLS.B1.010 Flight deck interface

• ED Decision 2022/008/R found in: GM Remote Aerodrome Air Traffic Services (ED 2019/004/R) Issue 2 (Jul 2020)

AMC1 ACNS.B.DLS.B1.010 Flight deck interface ED Decision 2022/008/R Flight crew control and display of data link related information (connectivity status, outstanding messages, etc.) should be consistent with the overall crew flight deck design philosophy. Flight crew control and display of data link messages should satisfy integrity and interface design criteria appropriate for the intended purpose. Reference to the applicable CS xx.1309 requirements should be observed. If a direct interface exists between the data link application and other on board systems, (e.g. flight planning and navigation), a means may be provided for the flight crew to initiate the use of the data contained in the message by the other on board system. The means provided should be separate from that used to respond to a message. Flight deck annunciations should be compatible with the overall alerting scheme of the aircraft. Audible and visual indications should be given by the data link system for each uplinked ATS message, including those messages not displayed immediately because of lack of crew response to an earlier ATS message. Visual alerts alone may be used for non-ATS messages. Annunciation of the receipt of a message during critical flight phases should be inhibited until after the critical flight phase. The criteria that define critical flight phases should be consistent with the particular flight deck philosophy and the particular data link services supported. Means should be provided for the flight crew to list, select, and retrieve the most recent ATS messages received and sent by the flight crew during the flight segment. The status of each message, the time it was received or sent, should be accessible. When CPDLC messages are displayed: (a) such location should be in the maximum field of view. (b) messages should be provided in a dedicated display (or in a dedicated window of a display). Shared use of CPDLC and other applications in a common display (or in the same window of a display) should be avoided. Note 1: (a) and (b) are intended for future extension of CPDLC use beyond en-route flight phase. Installations not in accordance with these recommendations are liable to be limited for CPDLC operations in the en-route or prior departure flight phase. Note 2: Where data link messages are displayed on a shared display or on a shared display area, selection of another display format or function should not result in the loss of uplinked messages which are waiting for a response. In case the pilot is working on another task and a message is uplinked, the uplinked message should not interrupt the current work, nor result in the loss of any uplinked message and/or data entered while accomplishing the other task. (c) messages from the ATS should remain displayed until responded, cleared or the flight crew selects another message. (d) means should be provided for the flight crew to clear uplinked messages from the display. However, this capability should be protected against inadvertent deletion. Means should be provided for the flight crew to create, store, retrieve, edit, delete, and send data link messages. The data link system should indicate when message storage and/or printing is not available. A flight deck printer could be used as a means of storing data communications messages received or sent during flight. If a message intended for visual display is greater than the available display area and only part of the message is displayed, a visual indication shall be provided to the pilot to indicate the presence of remaining message. Data link messages from the ATS should be displayed and remain displayed until responded, cleared or the flight crew selects another message. The status of each message (i.e. source, time sent, open/closed) should be displayed together with the message. [Issue: CS-ACNS/4]