Page 829 - UK Air Operations Regulations 201121

~ Regulation SPO - ANNEX VIII - Specialised Operations
SPO.IDE.H.150 AMC1
20th November 2021
n trik
(c) The recorder shall be capable of retaining data recorded for at least the same duration as
set out for CVRs in SPO.IDE.H.140.
(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 SPO.IDE.H.140
(d) and (e).
Data link recording
GENERAL
(a) As a means of compliance with SPO.IDE.H.150, the recorder on which the data link
messages are recorded should be:
(1) the CVR;
(2) the FDR;
(3) a combination recorder when SPO.IDE.H.155 is applicable; or
(4) a dedicated flight recorder. In such 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.
(b) As a means of compliance with SPO.IDE.H.150 (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 SPO.IDE.H.150(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 SPO.IDE.H.150 (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
Item Application Application Description Req uired
No Type Record ing
Content
1 Data link Th is includes any application us ed t o log o n to, o r C
initiat ion initiate, a data link service. In future air navigation
system IFANS)-1/A and air traffic navigation (ATN),
these are ATS facilities notification (AFN) and context
ma nagement (CM), respectively.
2 Controller/pilot Th i.s, includes any app lication used t o exchange C
communication requests, clearances, inst ructions and reports.
between t he flight crew and controllers on the
ground. In FANS-1/ A an d ATN, t his includes t he
controller pilot data link communications (CPDLC)
application.
Item Application Application Description Requ ired
No Type Record ing
Content
It also includes applications used fo r the exchange of
oceanic clearances {OCL) and depart ure cleara nces
(DCL), as we ll as dat a link delivery of t axi clea rances.
3 Addressed Thi5 includes any surve illance appl icat ion in which t he C, F2
su rvei llance ground sets up contracts for delivery of survei llance
data.
In FANS-1/A and ATN, t his includes t he autom atic
dependent surve illance-contract (ADS-C) application.
4 Flight Thi5 includes any app licatio n used for delivery of C
829 of 856