Compare and highlight differences

Compare / EASA/ Incorporated Amendments/ Compare & Highlight Differences

AMC1 CAT.IDE.H.195 Data link recording

Available versions for ERULES-1963177438-12631

ED Decision 2014/015/R found in: Air Operations (965/2012) Part-ARO Part-ORO Part-CAT Part-SPA Part-NCC Part-NCO Part-SPO (Sep 2023)

From

Show details Hide details

AMC1 CAT.IDE.H.195 Data link recording

ED Decision 2014/015/R

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)](#_DxCrossRefBm318086787), 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](#_DxCrossRefBm318086789) 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)](#_DxCrossRefBm318086787), 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)](#_DxCrossRefBm318086787) 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)](#_DxCrossRefBm318086787) 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

<table border="1" cellpadding="0" cellspacing="0" width="607"><tr><td width="41">Item No</td><td width="100">Application Type</td><td width="393">Application Description</td><td width="73">Required Recording Content</td></tr><tr><td valign="top" width="41">1</td><td valign="top" width="100">Data link initiation</td><td valign="top" width="393">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.</td><td valign="top" width="73">C</td></tr><tr><td valign="top" width="41">2</td><td valign="top" width="100">Controller/pilot communication</td><td valign="top" width="393">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).</td><td valign="top" width="73">C</td></tr><tr><td valign="top" width="41">3</td><td valign="top" width="100">Addressed surveillance</td><td valign="top" width="393">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.</td><td valign="top" width="73">C, F2</td></tr><tr><td valign="top" width="41">4</td><td valign="top" width="100">Flight information</td><td valign="top" width="393">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.</td><td valign="top" width="73">C</td></tr><tr><td valign="top" width="41">5</td><td valign="top" width="100">Aircraft broadcast surveillance </td><td valign="top" width="393">This includes elementary and enhanced surveillance systems, as well as automatic dependent surveillance-broadcast (ADS-B) output data.</td><td valign="top" width="73">M*,F2</td></tr><tr><td valign="top" width="41">6</td><td valign="top" width="100">Airlines operations centre (AOC) data</td><td valign="top" width="393">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</td><td valign="top" width="73">M*</td></tr><tr><td valign="top" width="41">7</td><td valign="top" width="100">Graphics </td><td valign="top" width="393">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).</td><td valign="top" width="73">M*F1</td></tr></table>

AMC1 CAT.IDE.H.195 Data link recording

ED Decision 2014/015/R

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)](#_DxCrossRefBm927679167), 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](#_DxCrossRefBm927679169) is applicable; or

(c) As a means of compliance with [CAT.IDE.H.195(a)(2)](#_DxCrossRefBm927679167), 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)](#_DxCrossRefBm927679167) 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)](#_DxCrossRefBm927679167) 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.

Table 1

Applications

##### AMC1 CAT.IDE.H.195 Data link recording

*ED Decision 2014/015/R*

**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)](#_DxCrossRefBm523088728),
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](#_DxCrossRefBm523088730)
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)](#_DxCrossRefBm523088728),
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)](#_DxCrossRefBm523088728)
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)](#_DxCrossRefBm523088728)
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

<table bgcolor="#d9d9d9" cellpadding="7" cellspacing="0">
<col/>
<col/>
<col/>
<col/>
<tr>
<td bgcolor="#808080">
Item
			No
</td>
<td bgcolor="#808080">
Application
			Type
</td>
<td bgcolor="#808080">
Application
			Description
</td>
<td bgcolor="#808080">
Required
			Recording Content
</td>
</tr>
<tr valign="top">
<td bgcolor="#d9d9d9">
1
</td>
<td bgcolor="#d9d9d9">
Data
			link initiation
</td>
<td bgcolor="#d9d9d9">
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.
</td>
<td bgcolor="#d9d9d9">
C
</td>
</tr>
<tr valign="top">
<td bgcolor="#d9d9d9">
2
</td>
<td bgcolor="#d9d9d9">
Controller/pilot
			communication
</td>
<td bgcolor="#d9d9d9">
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).
</td>
<td bgcolor="#d9d9d9">
C
</td>
</tr>
<tr valign="top">
<td bgcolor="#d9d9d9">
3
</td>
<td bgcolor="#d9d9d9">
Addressed
			surveillance
</td>
<td bgcolor="#d9d9d9">
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.
</td>
<td bgcolor="#d9d9d9">
C,
			F2
</td>
</tr>
<tr valign="top">
<td bgcolor="#d9d9d9">
4
</td>
<td bgcolor="#d9d9d9">
Flight
			information
</td>
<td bgcolor="#d9d9d9">
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.
</td>
<td bgcolor="#d9d9d9">
C
</td>
</tr>
<tr valign="top">
<td bgcolor="#d9d9d9">
5
</td>
<td bgcolor="#d9d9d9">
Aircraft
			broadcast surveillance 

</td>
<td bgcolor="#d9d9d9">
This
			includes elementary and enhanced surveillance systems, as well as
			automatic dependent surveillance-broadcast (ADS-B) output data.
</td>
<td bgcolor="#d9d9d9">
M*,
F2
</td>
</tr>
<tr valign="top">
<td bgcolor="#d9d9d9">
6
</td>
<td bgcolor="#d9d9d9">
Airlines
			operations centre (AOC) data
</td>
<td bgcolor="#d9d9d9">
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
</td>
<td bgcolor="#d9d9d9">
M*
</td>
</tr>
<tr valign="top">
<td bgcolor="#d9d9d9">
7
</td>
<td bgcolor="#d9d9d9">
Graphics
			

</td>
<td bgcolor="#d9d9d9">
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).
</td>
<td bgcolor="#d9d9d9">
M*
F1
</td>
</tr>
</table>

Compare / EASA/ Incorporated Amendments/ Compare & Highlight Differences

AMC1 CAT.IDE.H.195 Data link recording

View