Page 806 - UK Air Operations Regulations 201121

~ Regulation SPO - ANNEX VIII - Specialised Operations n trik

(b) As a means of compliance with SPO.IDE.A.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.A.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.A.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 below 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 l: Data link recording
Item Application Type Application Description Required
No Recording
Content
Data link init iation This includes any application used to log C
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 not ification (AFN) and
context management (CM),
respectively.

Controller/pilot This includes any application used to C
communication exchange request s, clearances,
instructions and reports between the
flight crew and controllers on the
ground. In FANS-1/A and ATN, this
includes the controller pilot data link
communications (CPDLC) application.
It also includes applications used for the
exchange of oceanic clearances (OCL)
and departure clearances (DCL), as well
as data link delivery of taxi clearances.
3 Addressed This includes any surveillance C, F2
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) applicat ion.

4 Flight information This includes any application used for C
delivery of flight information data to
specific aeroplanes. This includes for
example digital automatic terminal
information service (D ATIS), data link
operational terminal information
service (D OTIS), digital weather
information services (data link-
meteorological aerodrome or
aeronautical report (D-METAR) or
terminal weather information for pilots
(TWIP)), data link flight information
service (D-FIS), and Not ice to Airmen
(electronic NOTAM) delivery.

5 Broadcast This includes elementary and enhanced M*
surveillance systems, as well as
surveillance automatic dependent surveillance- F2
broadcast (ADS-B) output data.
6 Aeronautical This includes any application M'
20th November 2021 806 of 856