AMC1 CAT.IDE.H.195 Data link recording    

CAA ORS9 Decision No. 1

GENERAL

(a) The helicopter should be capable of recording the messages as specified in this AMC.

(b) As a means of compliance with CAT.IDE.H.195(a), the recorder on which the data link messages are recorded may be:

    (1) the CVR;

    (2) the FDR;

    (3) a combination recorder when CAT.IDE.H.200 is applicable; or

    (4) a dedicated flight recorder. In that case, the operational performance requirements for this recorder should be those laid down in EUROCAE Document ED-112 (Minimum Operational Performance Specification for Crash Protected Airborne Recorder Systems) dated March 2003, including amendments No 1 and No 2, or any later equivalent standard produced by EUROCAE.

(c) As a means of compliance with CAT.IDE.H.195(a)(2), the operator should enable correlation by providing information that allows an accident investigator to understand what data were provided to the helicopter and, when the provider identification is contained in the message, by which provider.

(d) The timing information associated with the data link communications messages required to be recorded by CAT.IDE.H.195(a)(3) should be capable of being determined from the airborne- based recordings. This timing information should include at least the following:

    (1) the time each message was generated;

    (2) the time any message was available to be displayed by the crew;

    (3) the time each message was actually displayed or recalled from a queue; and

    (4) the time of each status change.

(e) The message priority should be recorded when it is defined by the protocol of the data link communication message being recorded.

(f) The expression ‘taking into account the system architecture’, in CAT.IDE.H.195(a)(3) means that the recording of the specified information may be omitted if the existing source systems involved would require a major upgrade. The following should be considered:

    (1) the extent of the modification required;

    (2) the down-time period; and

    (3) equipment software development.

(g) The intention is that new designs of source systems should include this functionality and support the full recording of the required information.

(h) Data link communications messages that support the applications in Table 1 below should be recorded.

(i) Further details on the recording requirements can be found in the recording requirement matrix in Appendix D.2 of EUROCAE Document ED-93 (Minimum Aviation System Performance Specification for CNS/ATM Recorder Systems, dated November 1998).

Table 1

Applications

Item No

Application Type

 

Application Description

Required Recording

Content

1

Data link initiation

This includes any application used to log on to, or initiate, a data link service. In future air navigation system (FANS)-1/A and air traffic navigation (ATN), these are ATS facilities notification (AFN) and context management (CM), respectively.

C

2

Controller/pilot communication

This includes any application used to exchange requests, clearances, instructions and reports between the flight crew and air traffic controllers. In FANS-1/A and ATN, this includes the controller pilot data link communications (CPDLC) application.

CPDLC includes the exchange of oceanic clearances (OCLs) and departure clearances (DCLs).

C

3

Addressed surveillance

This includes any surveillance application in which the ground sets up contracts for delivery of surveillance data.

In FANS-1/A and ATN, this includes the automatic dependent surveillance-contract (ADS-C) application.

C, F2

4

Flight information

This includes any application used for delivery of flight information data to specific aeroplanes. This includes for example, data link- automatic terminal information service (D-ATIS), data link- operational terminal information service (D-OTIS), digital weather information services (D-METAR or TWIP), data link flight information service (D-FIS) and Notice to Airmen (D-NOTAM) delivery.

C

5

Aircraft broadcast surveillance

This includes elementary and enhanced surveillance systems, as well as automatic dependent surveillance-broadcast (ADS-B) output data.

M*, F2

6

Airlines operations centre (AOC) data

This includes any application transmitting or receiving data used for AOC purposes (in accordance with the ICAO definition of AOC). Such systems may also process AAC messages, but there is no requirement to record AAC messages

M*

7

Graphics

This includes any application receiving graphical data to be used for operational purposes (i.e. excluding applications that are receiving such things as updates to manuals).

M* F1