For which data link applications are all implemented up and downlink messages required to be recorded?

All implemented up and downlink messages are to be recorded for CPDLC and D-FIS applications, as stated in Table 1 of GM1 NCC.IDE.H.170.

Which applications in Table 1 of GM1 NCC.IDE.H.170 are marked with an asterisk (*) and what does that mean?

The asterisk (*) applies to applications that are to be recorded only as far as is practicable, given the architecture of the system. The specific applications marked with * are not explicitly listed in the text, but the meaning is defined in GM1 NCC.IDE.H.170(a)(3).

What is the definition of the 'Surveillance' application type in Table 1 of GM1 NCC.IDE.H.170?

The 'Surveillance' application type is defined as 'Downlinked Aircraft Parameters (DAP)' as defined in ICAO Annex 10 Volume IV (Surveillance systems and ACAS), according to Table 1 of GM1 NCC.IDE.H.170.

Which EUROCAE document is referenced for the D-ATIS data link service and what is its date?

For D-ATIS, the reference is EUROCAE ED-89A, dated December 2003: Data Link Application System Document (DLASD) for the 'ATIS' data link service, as per Table 1 of GM1 NCC.IDE.H.170.

What is the recording requirement for ADS-C position reports?

ADS-C position reports are only used within FANS 1/A, mainly in oceanic and remote areas, and all contract requests and reports are recorded, as per Table 1 of GM1 NCC.IDE.H.170.

What does the abbreviation 'TWIP' stand for and what messages are associated with it?

TWIP stands for 'terminal weather information for pilots', and the associated messages are TWIP messages, as per Table 1 of GM1 NCC.IDE.H.170.

What is the meaning of 'C' in the context of data link recording?

In the context of GM1 NCC.IDE.H.170, 'C' means 'complete contents recorded'.

Which applications are defined as ATN services in Table 1 of GM1 NCC.IDE.H.170?

CM (Configuration/Context Management) and D-FIS (Data Link Flight Information Service) are defined as ATN services, as per Table 1 of GM1 NCC.IDE.H.170.

What is the definition of 'AOC' messages in Table 1 of GM1 NCC.IDE.H.170?

AOC messages are 'Aeronautical operational control messages' exchanged in the framework of procedures within the operational control, as specified in Part-ORO, with information that enables correlation with any associated records stored separately from the helicopter, as per Table 1 of GM1 NCC.IDE.H.170.

Which EUROCAE document is referenced for the OCL data link service and what is its date?

For OCL, the reference is EUROCAE ED-106A, dated March 2004: Data Link Application System Document (DLASD) for 'Oceanic Clearance' (OCL) data link service, as per Table 1 of GM1 NCC.IDE.H.170.

What is the definition of 'Graphics' application type in Table 1 of GM1 NCC.IDE.H.170?

Graphics are 'Weather maps & other graphics' exchanged in the framework of procedures within the operational control, as specified in Part-ORO, with information that enables correlation with any associated records stored separately from the helicopter, as per Table 1 of GM1 NCC.IDE.H.170.

What is the definition of 'DCL' messages in Table 1 of GM1 NCC.IDE.H.170?

DCL messages are 'Departure Clearance' messages, and the reference is EUROCAE ED-85A, dated March 2003: Data Link Application System Document (DLASD) for 'Departure Clearance' data link service, as per Table 1 of GM1 NCC.IDE.H.170.

What is the definition of 'AFN' in Table 1 of GM1 NCC.IDE.H.170?

AFN is defined as 'Aircraft Flight Notification' and is a FANS 1/A service, as per Table 1 of GM1 NCC.IDE.H.170.

What is the definition of 'CPDLC' in Table 1 of GM1 NCC.IDE.H.170?

CPDLC is defined as 'Controller Pilot Data Link Communications' and all implemented up and downlink messages are to be recorded, as per Table 1 of GM1 NCC.IDE.H.170.

GM1 NCC.IDE.H.170 Data link recording

Q: What does the letter 'M' signify in the context of the data link recording requirements for non-commercial helicopter operations?

According to GM1 NCC.IDE.H.170, the letter 'M' means 'information that enables correlation with any associated records stored separately from the helicopter'.

Q: How should graphics applications be treated for recording purposes when they are part of a data link communications application service run by the operator for operational control?

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 operational control, as per GM1 NCC.IDE.H.170(a)(4).

Q: What is the recording requirement for parametric data sent by the helicopter, such as Mode S, when reported within a message?

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, as per GM1 NCC.IDE.H.170(a)(5).

Navigate / EASA

Ask question Discover more Add to collection

GM1 NCC.IDE.H.170 Data link recording

ED Decision 2013/021/R

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

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
4	ADS-C	Position reports	Only used within FANS 1/A. Mainly 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 ED-89A, dated December 2003: Data Link Application System Document (DLASD) for the ‘ATIS’ data link service
9	OCL	OCL messages	Refer to EUROCAE ED-106A, dated March 2004: Data Link Application System Document (DLASD) for ‘Oceanic Clearance’ (OCL) data link service
10	DCL	DCL messages	Refer to EUROCAE ED-85A, dated March 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 helicopter.
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 ED-112, dated March 2003.
13	Surveillance	Downlinked 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 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

Details

Source-Title: GM1 NCC.IDE.H.170 Data link recording View latest amendments

Erulesid: ERULES-1963177438-13329 Compare versions

Domain: Air operations

Applicabilitydate: 23 August, 2013

Entryintoforcedate: 23 August, 2013

Regulatorysource: ED Decision 2013/021/R Navigate

Regulatorysubject: Part-NCC

Typeofcontent: GM to IR (Guidance material to implementing rule)

Parentir: NCC.IDE.H.170 Data link recording

Origin: EASA

Category: EAR