--- title: "CAT.IDE.H.195 Data link recording — Part-CAT · Avioverse" description: "Helicopters first issued with an individual CofA on or after 8 April 2014 that have the capability to operate data link communications and are required…" url: "https://avioverse.aero/regulations/easa/air-ops/part-cat/subpart-d/cat-ide-h-195" --- # CAT.IDE.H.195 Data link recording ANNEX IV (Part-CAT) · Regulation (EU) No 965/2012 · EAR revision 27 Mar 2026 IR Implementing rule ## CAT.IDE.H.195 Data link recording (a) Helicopters first issued with an individual CofA on or after 8 April 2014 that have the capability to operate data link communications and are required to be equipped with a CVR, shall record on a recorder, where applicable: (1) data link communication messages related to ATS communications to and from the [helicopter](https://avioverse.aero/glossary/easa/helicopter), including messages applying to the following applications: (i) data link initiation; (ii) controller-pilot communication; (iii) addressed surveillance; (iv) flight information; (v) as far as is practicable, given the architecture of the system, [aircraft](https://avioverse.aero/glossary/easa/aircraft) broadcast surveillance; (vi) as far as is practicable, given the architecture of the system, aircraft [operational control](https://avioverse.aero/glossary/easa/operational-control) data; (vii) as far as is practicable, given the architecture of the system, graphics; (2) information that enables correlation to any associated records related to data link communications and stored separately from the helicopter; and (3) information on the time and priority of data link communications messages, taking into account the system’s architecture. (b) The recorder shall use a digital method of recording and storing data and information and a method of readily retrieving that data shall be available. The recording method shall allow the data to match the data recorded on the ground. (c) The recorder shall be capable of retaining data recorded for at least the same duration as set out for CVRs in CAT.IDE.H.185. (d) If the recorder is not deployable, it shall have a device to assist in locating it under water. By 1 January 2020 at the latest, this device shall have a minimum underwater transmission time of 90 days. If the recorder is deployable, it shall have an automatic emergency locator transmitter. (e) The requirements applicable to the start and stop logic of the recorder are the same as the requirements applicable to the start and stop logic of the CVR contained in CAT.IDE.H.185(d) and (e). IR · CAT.IDE.H.195 — Regulation (EU) No 965/2012 · Regulation (EU) 2015/2338 · Air OPS Easy Access Rules · EAR revision 27 Mar 2026 AMC Acceptable means of compliance ## AMC1 CAT.IDE.H.195 Data link recording GENERAL (a) The [helicopter](https://avioverse.aero/glossary/easa/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](https://avioverse.aero/glossary/easa/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](https://avioverse.aero/glossary/easa/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 | AMC · AMC1 CAT.IDE.H.195 — Regulation (EU) No 965/2012 · ED Decision 2014/015/R · Air OPS Easy Access Rules · EAR revision 27 Mar 2026 GM Guidance material ## GM1 CAT.IDE.H.195 Data link recording DEFINITIONS AND ACRONYMS (a) The letters and expressions in Table 1 of AMC1 CAT.IDE.H.195 have the following meaning: C: Complete contents recorded M: Information that enables correlation with any associated records stored separately from the [helicopter](https://avioverse.aero/glossary/easa/helicopter). \*: Applications that are to be recorded only as far as is practicable, given the architecture of the system. F1: Graphics applications may be considered as AOC data 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](https://avioverse.aero/glossary/easa/operational-control). 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 CAT.IDE.H.195 are described in Table 1 below. Table 1 Descriptions of the applications type | Item No | Application Type | Messages | Comments | | ------- | ---------------- | ------------------------------------------------------------------------------------- | ---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | | 1 | CM | | CM is an ATN service | | 2 | AFN | | AFN is a FANS 1/A service | | 3 | CPDLC | | All implemented up and downlink messages to be recorded | | 4 | ADS-C | ADS-C reports | All contract requests and reports recorded | | | | Position reports | Only used within FANS 1/A. Only used in oceanic and remote areas. | | 5 | ADS-B | Surveillance data | Information that enables correlation with any associated records stored separately from the helicopter. | | 6 | D-FIS | | D-FIS is an ATN service. All implemented up and downlink messages to be recorded | | 7 | TWIP | TWIP messages | Terminal weather information for pilots | | 8 | D-ATIS | ATIS messages | Refer to EUROCAE Document ED-89A dated December 2003. Data Link Application System Document (DLASD) for the ‘ATIS’ Data Link Service | | 9 | OCL | OCL messages | Refer to EUROCAE Document ED-106A dated March 2004. Data Link Application System Document (DLASD) for ‘Oceanic Clearance’ Data Link Service | | 10 | DCL | DCL messages | Refer to EUROCAE Document ED-85A dated December 2003. Data Link Application System Document (DLASD) for ‘Departure Clearance’ Data Link Service | | 11 | Graphics | Weather maps & other graphics | Graphics exchanged in the framework of procedures within the operational control, as specified in Part-ORO. Information that enables correlation with any associated records stored separately from the [aeroplane](https://avioverse.aero/glossary/easa/aeroplane). | | 12 | AOC | Aeronautical operational control messages | Messages exchanged in the framework of procedures within the operational control, as specified in Part-ORO. Information that enables correlation with any associated records stored separately from the helicopter. Definition in EUROCAE Document ED-112, dated March 2003. | | 13 | Surveillance | Downlinked [aircraft](https://avioverse.aero/glossary/easa/aircraft) parameters (DAP) | As defined in ICAO Annex 10 Volume IV (Surveillance systems and ACAS). | 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 data link ATIS D-FIS data link flight information service 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 GM · GM1 CAT.IDE.H.195 — Regulation (EU) No 965/2012 · ED Decision 2014/015/R · Air OPS Easy Access Rules · EAR revision 27 Mar 2026 GM Guidance material ## GM1 CAT.IDE.H.195(a) Data link recording APPLICABILITY OF THE DATA LINK RECORDING REQUIREMENT (a) If it is certain that the [helicopter](https://avioverse.aero/glossary/easa/helicopter) cannot use data link communication messages for ATS communications corresponding to any application designated by CAT.IDE.H.195(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. GM · GM1 CAT.IDE.H.195(a) — Regulation (EU) No 965/2012 · ED Decision 2014/015/R · Air OPS Easy Access Rules · EAR revision 27 Mar 2026 [All rules in SUBPART D: INSTRUMENTS, DATA, EQUIPMENT](https://avioverse.aero/regulations/easa/air-ops/part-cat/subpart-d) Consolidated from the EASA Easy Access Rules (revision 27 Mar 2026, extracted 13 Oct 2026) for convenience. Not the official publication — verify against the Official Journal of the European Union and the EASA publications before operational use.