NCC.IDE.H.170 Data link recording

GENERAL

(a)As a means of compliance with NCC.IDE.H.170, the recorder on which the data link messages are recorded should be:

(1)the CVR;

(2)the FDR;

(3)a combination recorder when NCC.IDE.H.175 is applicable; or

(4)a dedicated flight recorder. In such a 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 n°1 and n°2, or any later equivalent standard produced by EUROCAE.

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

(c)The timing information associated with the data link communications messages required to be recorded by NCC.IDE.H.170(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 flight crew;

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

(4)the time of each status change.

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

(e)The expression ‘taking into account the system’s architecture’, in NCC.IDE.H.170(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.

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

(g)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: Data link recording

GENERAL

(a)The letters and expressions in Table 1 of AMC1 NCC.IDE.H.170 have the following meaning:

(1)C: complete contents recorded.

(2)M: information that enables correlation with any associated records stored separately from the helicopter.

(3)*: applications that are to be recorded only as far as is practicable, given the architecture of the system.

(4)F1: graphics applications may be considered as AOC messages when they are part of a data link communications application service run on an individual basis by the operator itself in the framework of the operational control.

(5)F2: where parametric data sent by the helicopter, such as Mode S, is reported within the message, it should be recorded unless data from the same source is recorded on the FDR.

(b)The definitions of the applications type in Table 1 of AMC1 NCC.IDE.H.170 are described in Table 1 below.

Table 1: Definitions of the applications type

AAC aeronautical administrative communications ADS-B automatic dependent surveillance - broadcast ADS-C automatic dependent surveillance – contract AFN aircraft flight notification AOC aeronautical operational control ATIS automatic terminal information service ATSC air traffic service communication CAP controller access parameters CPDLC controller pilot data link communications CM configuration/context management D-ATIS digital ATIS D-FIS data link flight information service D-METAR data link meteorological airport report DCL departure clearance FANS Future Air Navigation System FLIPCY flight plan consistency OCL oceanic clearance SAP system access parameters TWIP terminal weather information for pilots

APPLICABILITY OF THE DATA LINK RECORDING REQUIREMENT

(a)If it is certain that the helicopter cannot use data link communication messages for ATS communications corresponding to any application designated by NCC.IDE.H.170(a)(1), then the data link recording requirement does not apply.

(b)Examples where the helicopter cannot use data link communication messages for ATS communications include but are not limited to the cases where:

(1)the helicopter data link communication capability is disabled permanently and in a way that it cannot be enabled again during the flight;

(2)data link communications are not used to support air traffic service (ATS) in the area of operation of the helicopter; and

(3)the helicopter data link communication equipment cannot communicate with the equipment used by ATS in the area of operation of the helicopter.