AMC 20-9 Acceptable Means of Compliance for the Approval of Departure Clearance via Data Communications over ACARS

• ED Decision 2006/012/R found in: AMC-20 Amdt 23 - Airworthiness of Products, Parts and Appliances (Jan 2022)

AMC 20-9 Acceptable Means of Compliance for the Approval of Departure Clearance via Data Communications over ACARS ED Decision 2006/012/R 1          PREAMBLE 1.1       This AMC is issued in response to the EUROCONTROL Convergence and Implementation Plan that recommends an interim deployment of air-to-ground and ground- to-air data link applications based on the existing airline ACARS technology. One such application is Departure Clearance (DCL) data link now operational at various airports in Europe (as indicated in AIPs). Aircraft operators, on a voluntary basis, may take advantage of DCL over ACARS where it is available, subject to any arrangements that may be required by their responsible operations authority. 1.2       The use of ACARS for data link purposes is a transitional step to data link applications that will use VDL Mode 2 and the Aeronautical Telecommunications Network (ATN), compliant with ICAO SARPS, as proposed in the EUROCONTROL LINK2000+ programme[[6]](#_ftn6). 1.3       Described in EUROCAE document ED-85A (hereafter “ED-85A”), Data Link Application System document (DLASD) for the “Departure Clearance” Data Link Service, DCL over ACARS is a control tower application providing direct communication between the flight crew and the air traffic controller. ED-85A addresses three domains: airborne, ground ATC, and communication service providers. It deals also with associated flight crew and controller procedures. ED-85A takes account of EUROCAE document ED-78 which describes the global processes including approval planning, co-ordinated requirements determination, development and qualification of a system element, entry into service, and operations. 2          PURPOSE 2.1       This AMC is intended for operators seeking to use Departure Clearance via data link over ACARS as described in ED-85A. It may assist also other stakeholders such as airspace planners, air traffic service providers, ATS system manufacturers, communication service providers, aircraft and equipment manufacturers, and ATS regulatory authorities to advise them of the airborne requirements and procedures, and the related assumptions. 2.2       This AMC provides a method for evaluating compliance of a data link system to the requirements of ED-85A, and the means by which an aircraft operator can satisfy an authority that operational considerations have been addressed. 3          SCOPE 3.1       This AMC addresses DCL over ACARS using the ARINC 623 protocol as elaborated in EUROCAE document ED-85A and promoted by the EUROCONTROL Convergence and Implementation Plan as an interim data link application pending maturity of the LINK2000+ programme. The AMC is not directly applicable to Pre-Departure Clearance (PDC) as used in the USA and some other states. For PDC approval, guidance may be found in FAA document Safety and Interoperability Requirements for Pre- Departure Clearance, issued by AIR-100 on April 21, 1998. A comparison of PDC with DCL may be found in Appendix 1. 3.2       This AMC is not applicable to the phased implementation of data link services within the EUROCONTROL LINK2000+ programme, in particular, DCL over the Aeronautical Telecommunications Network via VHF Digital Data Link (VDL) Mode 2. In this case, the Safety and Performance Requirements (EUROCAE ED-120) and the Interoperability Requirements (EUROCAE ED-110) are established using EUROCAE document ED-78A, Guidelines for Approval of the Provision and use of Air Traffic Services supported by Data Communications. Guidance for the implementation of DCL over ATN may be found in EASA document AMC 20-11. 3.3       The operational requirements for the DCL application are published in the EUROCONTROL document OPR/ET1/ST05/1000, Edition 2, October 15,1996, Transition guidelines for initial air ground data communication services. The EUROCONTROL document includes the re-issued clearance capability, however document ED-85A does not address this capability and it is not included in the scope of this AMC. 3.4       For the remainder of this document, the acronym DCL should be interpreted to mean DCL over ACARS using the ARINC 623 protocol unless stated otherwise. 4          REFERENCE DOCUMENTS 4.1       Related Requirements CS/FAR 25.1301, 25.1307, 25.1309, 25.1322, 25.1431, 25.1581, or equivalent requirementsof CS 23, 27 and 29 if applicable. 4.2       Related Standards and Guidance Material <table border="1" cellpadding="0" cellspacing="0" width="531"> <tr> <td rowspan="6" valign="top" width="101"> <p>ICAO</p> </td> <td valign="top" width="128"> <p>Doc 9694 AN/955</p> </td> <td valign="top" width="302"> <p>Manual of Air Traffic Services (ATS) DataLink Applications</p> </td> </tr> <tr> <td valign="top" width="128"> <p>Doc 4444</p> </td> <td valign="top" width="302"> <p>Rules of the Air and Air Traffic Services</p> </td> </tr> <tr> <td valign="top" width="128"> <p>Draft Proposal</p> </td> <td valign="top" width="302"> <p>PANS-Air Traffic Management</p> </td> </tr> <tr> <td valign="top" width="128"> <p>Annex 11</p> </td> <td valign="top" width="302"> <p>Air Traffic Services</p> </td> </tr> <tr> <td valign="top" width="128"> <p>Doc 8585</p> </td> <td valign="top" width="302"> <p>Designators for Aircraft Operating agencies,Aeronautical Authorities and Services</p> </td> </tr> <tr> <td valign="top" width="128"> <p>Doc 8643</p> </td> <td valign="top" width="302"> <p>Aircraft Type Designators</p> </td> </tr> <tr> <td valign="top" width="101"> <p>EASA</p> </td> <td valign="top" width="128"> <p>AMC 25-11</p> </td> <td valign="top" width="302"> <p>Electronic Display Systems</p> </td> </tr> <tr> <td rowspan="3" valign="top" width="101"> <p>EUROCONTROL</p> </td> <td valign="top" width="128"> <p>CIP:COM.</p> <p>ET2.SO4;2.1.5</p> </td> <td valign="top" width="302"> <p>Implement Air/Ground Communication</p> <p>Services- Interim step on non-ATN (ACARS)services.</p> </td> </tr> <tr> <td valign="top" width="128"> <p>OPR/ET1/ST05/1000</p> </td> <td valign="top" width="302"> <p>Transition guidelines for initial air ground data communication services</p> </td> </tr> <tr> <td valign="top" width="128"> <p>ESARR 4</p> </td> <td valign="top" width="302"> <p>Risk assessment and mitigation in ATM</p> </td> </tr> <tr> <td rowspan="4" valign="top" width="101"> <p>FAA</p> </td> <td valign="top" width="128"> <p>AC 25-11</p> </td> <td valign="top" width="302"> <p>Electronic Display Systems.</p> </td> </tr> <tr> <td valign="top" width="128"> <p>AC 120-COM</p> </td> <td valign="top" width="302"> <p>Initial Air Carrier Operational Approval for use of Digital Communication Systems</p> </td> </tr> <tr> <td valign="top" width="128"> <p>AC 20-140</p> </td> <td valign="top" width="302"> <p>Guidelines for design approval of aircraft data communications systems</p> </td> </tr> <tr> <td valign="top" width="128"> <p>98-Air-PDC</p> </td> <td valign="top" width="302"> <p>Safety and Interoperability requirement for Pre-Departure-Clearance (PDC). (Air-100, April 21,1998)</p> </td> </tr> <tr> <td rowspan="3" valign="top" width="101"> <p>EUROCAE</p> </td> <td valign="top" width="128"> <p>ED 78</p> </td> <td valign="top" width="302"> <p>Guidance material for the establishment of data link supported ATS Services</p> </td> </tr> <tr> <td valign="top" width="128"> <p>ED-85A</p> </td> <td valign="top" width="302"> <p>Data Link Application System document (DLASD) for the “ departureClearance ” data link service</p> </td> </tr> <tr> <td valign="top" width="128"> <p>ED-112</p> </td> <td valign="top" width="302"> <p>Minimum operational performance specification for Crash protected airborne recorder systems</p> </td> </tr> <tr> <td valign="top" width="101"> <p>RTCA</p> </td> <td valign="top" width="128"> <p>DO 224</p> </td> <td valign="top" width="302"> <p>Minimum Aviation System Performance Standards (MASPS) for Advanced VHF Digital Data Communications Including Compatibility with Digital Voice Techniques.</p> </td> </tr> <tr> <td valign="top" width="101"> <p>SAE</p> </td> <td valign="top" width="128"> <p>ARP 4791</p> </td> <td valign="top" width="302"> <p>Human Machine Interface on the flight deck</p> </td> </tr> </table> 5          ASSUMPTIONS Applicants should note that this AMC is based on the assumptions stated in Chapter 3 of ED-85A together with the following that concern the measures taken by the responsible airspace authorities to safeguard DCL operations. 5.1       ATS Provider 5.1.1   The data link service for DCL has been shown to satisfy applicable airspace safety regulations and the relevant ATS domain performance, safety and interoperability requirements of ED-85A. 5.1.2   Procedures for the use of DCL take account of the performance limitations of ACARS and the airborne implementation capabilities meeting at least the provisions of this AMC. Note: Some aircraft ACARS installations approved to earlier standards are classified as “Non Essential” without guarantees of performance or integrity. Consequently,procedures are necessary to compensate for any deficiency and to safeguard operations. ED-85A addresses this issue. 5.1.3   Appropriate procedures are established to minimise the possibility of failure to detect inconsistency in the case of a complex clearance. 5.1.4   Each ATS provider has published a list of communication service providers that may be used by aircraft operators for the DCL application. The list should take account of internetworking arrangements between service providers. 5.1.5   The procedures of the ATS provider state the actions that should be taken in the event of an inadequate communication service from the communications service provider (CSP). 5.2       Communications Service Provider The communications service provider does not modify the operational information (content and format) exchanged between the ATS provider and the airborne equipment. 5.3       Aeronautical Information Service Each State offering a DCL service by data link publishes in its AIP, or equivalent notification, availability of the service, relevant procedures, and confirmation of compliance with ED-85A. 5.4       Message Integrity The Cyclic Redundancy Check (CRC) is implemented as required by ED-85A and is providing integrity of the end-to-end data link transmission path. On this basis, Performance Technical Requirement PTR\_3 of ED-85A need not be demonstrated. 6          AIRWORTHINESS CONSIDERATIONS 6.1       General 6.1.1   The installation will need to be shown compliant with the airborne domain requirements allocated as per ED-85A (§7.1) covering the Interoperability Operational Requirements, the Interoperability Technical Requirements, the Performance Technical Requirements, the Safety Operational & Technical Requirements. 6.1.2   If multiple ATS data link applications are available to the aircraft, the crew interface and related crew procedures will need to be based on a common and compatible philosophy. 6.2       Required Functions An acceptable minimum airborne installation comprises the following functions: (a)       A means of data communication appropriate to the area of operation, e.g. plain old ACARS over AVLC (Aviation VHF Link Control) through VHF or SATCOM; Note: VDL Mode 2 equipment can be used provided that radio transceiver is compliant with ED-92A. (b)      A means to manage data communications and to control the data communications system; (c)       A means to easily check and modify the parameters of the DCL request; (d)      “Visual” alerting of an incoming message, visible to both pilots; (e)      Means to display the text message, e.g. a single display readable by both crewmembers or a dedicated display for each pilot. (f)       A means to accept the DCL delivered by the ATS. 6.3       Recommended Functions (a)       “Audible” alerting of an incoming message; (b)      A means to print the messages; (c)       Recording of DCL messages and flight crew responses on an accident flight recorder. Note: Data Link recording may be required in accordance with OPS rules. 7          ACCEPTABLE MEANS OF AIRWORTHINESS COMPLIANCE 7.1       Airworthiness 7.1.1   When demonstrating compliance with this AMC, the following specific points should be noted: (a)       Compliance with the airworthiness requirements for intended function and safety may be demonstrated by equipment qualification, safety analysis of the interface between the communications management system and data sources, structural analyses of new antenna installations, equipment cooling verification, and evidence of a suitable human to machine interface. The DCL function will need to be demonstrated by end-to-end ground testing that verifies system operation, either with an appropriate ATS unit, or by means of test equipment that has been shown to be representative of the actual ATS unit. Note: This limited testing assumes that the communication systems (VHF or SATCOM) have been shown to satisfactorily perform their intended functions in the flight environment in accordance with applicable requirements. (b)       The safety analysis of the interface between the communications management system and its data sources should show that, under normal or fault conditions, no unwanted interaction which adversely affects essential systems can occur. 7.1.2   To minimise the certification effort for follow-on installations credit may be granted for applicable certification and test data obtained from equivalent aircraft installations. 7.2       Performance The installation should be shown to meet the airborne domain performance requirements allocated by ED-85A (§7.1). Demonstration of Performance Technical Requirement PTR\_A1 may be difficult for some airborne installations. The applicant may choose an alternative acceptable means of compliance for PTR\_A1 consisting in an end-to-end demonstration of PTR\_5 & PTR-6 of ED-85A (§5.2) with an appropriate ATS unit and communication service provider. 7.3       Aircraft Flight Manual The Flight Manual should state the following limitation. Note: This limited entry assumes that a detailed description of the installed system and related operating instructions are available in other operating or training manuals and that operating procedures take account of ED-85A. Limitation: The Departure Clearance (DCL) over ACARS application has been demonstrated with data link services declared compliant with EUROCAE document ED- 85A. 7.4       Existing installations The applicant will need to submit a compliance statement that shows how the criteria of this AMC have been satisfied for existing installations. Compliance may be established by inspection of the installed system to confirm the availability of required features and functionality. Note: It is not intended that aircraft which have received airworthiness approval in compliance with ED-85 requirement should be reinvestigated where the installation is compliant with Section 6, 7 and 8 of this AMC. 8          OPERATIONAL CONSIDERATIONS 8.1       Flight Plan Information 8.1.1   The Aircraft Identification transmitted by data link will need to conform to the ICAO format and correspond with the flight identity as entered in the applicable flight plan. 8.1.2   Aircraft type designator includes both Aircraft Type and Sub-type and shall be coded in accordance with the format described in ICAO document 8643 at its latest edition. However, certain ACARS equipment can be pre-programmed only with Aircraft Type with the possibility of manual insertion of Sub-type via the system control panel. Absence of the Sub-type information may lead either to a rejected departure clearance request at some airports, or the issue of an inappropriate clearance where the aircraft performance capability is not taken into account. Where, to obtain the DCL service, Sub-type needs to be entered manually, the entry should be verified. 8.2       Operational Safety Aspects 8.2.1   Failure Conditions are presented in ED-85A (§6) together with the resulting safety requirements and operational means of mitigation. Failure Condition FC3 (undetected erroneous SID) is discussed further in the following paragraphs. 8.2.2   When a SID construct is simple and unambiguous (e.g. only one SID for one runway magnetic orientation (QFU) and one destination) so allowing the flight crew and the ATS controller to independently detect any inconsistency in the DCL, then additional means of mitigation are not required. 8.2.3   For other, more complex cases where the SID construction prevents the flight crew and the controller from readily detecting any inconsistency, a specific flight crew to controller procedure will need to be implemented to verify the clearance. This may be stated in the AIP or other notification issued by the State where aircraft will operate and use DCL service. Note (1): In some countries (e.g. United Kingdom, AIC 125/1999, France AIC A19/00), following the investigation of level violations, voice confirmation of cleared altitude or flight level and SID identification is already required even for voice delivered departure clearance on the first contact with the approach control/departure radar. In such cases, no additional confirmation procedure is required. Note (2): The ATS may agree that voice confirmation is not required where the data link function is certificated with an integrity level corresponding to the Essential category of CS25.1309. 8.2.4   In all cases, flight crews will need to comply with any mitigating procedures published by the States where aircraft will operate and use DCL service. 8.2.5   The assumptions of Section 5 need to be satisfied as a condition for operational use. 8.3       Operations Manual and Training 8.3.1   The Operations Manual shall reflect the Flight Manual statement of paragraph 7.3 and define operating procedures for use of the DCL. 8.3.2   Flight crew training should address: (a)       The different data link services available using the same airborne equipment (e.g. differences between DCL and PDC applications as described in Annex 1); (b)       ATS procedures for DCL; and (c)       The required format for the flight identification input. 8.3.3   Subject to any arrangements that may be required by the responsible operations authority in respect of amendments to the Operations Manual, and the approval of training programmes, the aircraft operator may implement operations using DCL over ACARS. 8.4       Incident reporting Significant incidents associated with a departure clearance transmitted by data link that affects or could affect the safe operation of the aircraft will need to be reported in accordance with applicable operational rules, and to the authority responsible for the airport where the DCL service was provided. AVAILABILITY OF DOCUMENTS EUROCAE documents may be purchased from EUROCAE, 17 rue Hamelin, 75783 Paris Cedex 16, France, (Fax: 33 1 45 05 72 30). Web site: [www.eurocae.org](http://www.eurocae.org/). JAA documents are available from the JAA publisher Information Handling Services (IHS). Information on prices, where and how to order is available on both the JAA web site [www.jaa.nl](http://www.jaa.nl/)and the IHS web site [www.avdataworks.com](http://www.avdataworks.com/). EUROCONTROL documents may be requested from EUROCONTROL, Documentation Centre, GS4, Rue de la Fusee, 96, B-1130 Brussels, Belgium; (Fax: 32 2 729 9109 or web site [www.eurocontrol.int](http://www.eurocontrol.int)). ICAO documents may be purchased from Document Sales Unit, International Civil Aviation Organisation, 999 University Street, Montreal, Quebec, Canada H3C 5H7, (Fax: 1 514 954 6769, e-mail: sales\_unit@icao.org) or through national agencies. FAA documents may be obtained from Department of Transportation, Subsequent Distribution Office SVC-121.23, Ardmore East Business Centre, 3341 Q 75th Avenue, Landover, MD 20785, USA. Web site [www.faa.gov/aviation.htm](http://www.faa.gov/aviation.htm) RTCA documents may be obtained from RTCA Inc, 1828 L Street, NW., Suite 805, Washington, DC 20036, USA., (Tel: 1 202 833 9339; Fax 1 202 833 9434). Web site:[www.rtca.org](http://www.rtca.org/). SAE documents may be obtained from SAE World Headquarters, 400 Commonwealth Drive, Warrendale, PA 15096-0001, USA. Telephone 1-877-606-7323 (U.S. and Canada only) or 724/776-4970 (elsewhere). Web site [www.sae.org](http://www.sae.org/). [Amdt 20/1] --- [[6]](#_ftnref6)     Information on LINK2000+ is available at web site [www.eurocontrol.int/link2000](http://www.eurocontrol.int/link2000) AMC 20-9 Acceptable Means of Compliance for the Approval of Departure Clearance via Data Communications over ACARS ED Decision 2006/012/R 1          PREAMBLE 1.1       This AMC is issued in response to the EUROCONTROL Convergence and Implementation Plan that recommends an interim deployment of air-to-ground and ground- to-air data link applications based on the existing airline ACARS technology. One such application is Departure Clearance (DCL) data link now operational at various airports in Europe (as indicated in AIPs). Aircraft operators, on a voluntary basis, may take advantage of DCL over ACARS where it is available, subject to any arrangements that may be required by their responsible operations authority. 1.2       The use of ACARS for data link purposes is a transitional step to data link applications that will use VDL Mode 2 and the Aeronautical Telecommunications Network (ATN), compliant with ICAO SARPS, as proposed in the EUROCONTROL LINK2000+ programme[[6]](#_ftn6). 1.3       Described in EUROCAE document ED-85A (hereafter “ED-85A”), Data Link Application System document (DLASD) for the “Departure Clearance” Data Link Service, DCL over ACARS is a control tower application providing direct communication between the flight crew and the air traffic controller. ED-85A addresses three domains: airborne, ground ATC, and communication service providers. It deals also with associated flight crew and controller procedures. ED-85A takes account of EUROCAE document ED-78 which describes the global processes including approval planning, co-ordinated requirements determination, development and qualification of a system element, entry into service, and operations. 2          PURPOSE 2.1       This AMC is intended for operators seeking to use Departure Clearance via data link over ACARS as described in ED-85A. It may assist also other stakeholders such as airspace planners, air traffic service providers, ATS system manufacturers, communication service providers, aircraft and equipment manufacturers, and ATS regulatory authorities to advise them of the airborne requirements and procedures, and the related assumptions. 2.2       This AMC provides a method for evaluating compliance of a data link system to the requirements of ED-85A, and the means by which an aircraft operator can satisfy an authority that operational considerations have been addressed. 3          SCOPE 3.1       This AMC addresses DCL over ACARS using the ARINC 623 protocol as elaborated in EUROCAE document ED-85A and promoted by the EUROCONTROL Convergence and Implementation Plan as an interim data link application pending maturity of the LINK2000+ programme. The AMC is not directly applicable to Pre-Departure Clearance (PDC) as used in the USA and some other states. For PDC approval, guidance may be found in FAA document Safety and Interoperability Requirements for Pre- Departure Clearance, issued by AIR-100 on April 21, 1998. A comparison of PDC with DCL may be found in Appendix 1. 3.2       This AMC is not applicable to the phased implementation of data link services within the EUROCONTROL LINK2000+ programme, in particular, DCL over the Aeronautical Telecommunications Network via VHF Digital Data Link (VDL) Mode 2. In this case, the Safety and Performance Requirements (EUROCAE ED-120) and the Interoperability Requirements (EUROCAE ED-110) are established using EUROCAE document ED-78A, Guidelines for Approval of the Provision and use of Air Traffic Services supported by Data Communications. Guidance for the implementation of DCL over ATN may be found in EASA document AMC 20-11. 3.3       The operational requirements for the DCL application are published in the EUROCONTROL document OPR/ET1/ST05/1000, Edition 2, October 15,1996, Transition guidelines for initial air ground data communication services. The EUROCONTROL document includes the re-issued clearance capability, however document ED-85A does not address this capability and it is not included in the scope of this AMC. 3.4       For the remainder of this document, the acronym DCL should be interpreted to mean DCL over ACARS using the ARINC 623 protocol unless stated otherwise. 4          REFERENCE DOCUMENTS 4.1       Related Requirements CS/FAR 25.1301, 25.1307, 25.1309, 25.1322, 25.1431, 25.1581, or equivalent requirementsof CS 23, 27 and 29 if applicable. 4.2       Related Standards and Guidance Material <table border="1" cellpadding="0" cellspacing="0" width="531"> <tr> <td rowspan="6" valign="top" width="101"> <p>ICAO</p> </td> <td valign="top" width="128"> <p>Doc 9694 AN/955</p> </td> <td valign="top" width="302"> <p>Manual of Air Traffic Services (ATS) DataLink Applications</p> </td> </tr> <tr> <td valign="top" width="128"> <p>Doc 4444</p> </td> <td valign="top" width="302"> <p>Rules of the Air and Air Traffic Services</p> </td> </tr> <tr> <td valign="top" width="128"> <p>Draft Proposal</p> </td> <td valign="top" width="302"> <p>PANS-Air Traffic Management</p> </td> </tr> <tr> <td valign="top" width="128"> <p>Annex 11</p> </td> <td valign="top" width="302"> <p>Air Traffic Services</p> </td> </tr> <tr> <td valign="top" width="128"> <p>Doc 8585</p> </td> <td valign="top" width="302"> <p>Designators for Aircraft Operating agencies,Aeronautical Authorities and Services</p> </td> </tr> <tr> <td valign="top" width="128"> <p>Doc 8643</p> </td> <td valign="top" width="302"> <p>Aircraft Type Designators</p> </td> </tr> <tr> <td valign="top" width="101"> <p>EASA</p> </td> <td valign="top" width="128"> <p>AMC 25-11</p> </td> <td valign="top" width="302"> <p>Electronic Display Systems</p> </td> </tr> <tr> <td rowspan="3" valign="top" width="101"> <p>EUROCONTROL</p> </td> <td valign="top" width="128"> <p>CIP:COM.</p> <p>ET2.SO4;2.1.5</p> </td> <td valign="top" width="302"> <p>Implement Air/Ground Communication</p> <p>Services- Interim step on non-ATN (ACARS)services.</p> </td> </tr> <tr> <td valign="top" width="128"> <p>OPR/ET1/ST05/1000</p> </td> <td valign="top" width="302"> <p>Transition guidelines for initial air ground data communication services</p> </td> </tr> <tr> <td valign="top" width="128"> <p>ESARR 4</p> </td> <td valign="top" width="302"> <p>Risk assessment and mitigation in ATM</p> </td> </tr> <tr> <td rowspan="4" valign="top" width="101"> <p>FAA</p> </td> <td valign="top" width="128"> <p>AC 25-11</p> </td> <td valign="top" width="302"> <p>Electronic Display Systems.</p> </td> </tr> <tr> <td valign="top" width="128"> <p>AC 120-COM</p> </td> <td valign="top" width="302"> <p>Initial Air Carrier Operational Approval for use of Digital Communication Systems</p> </td> </tr> <tr> <td valign="top" width="128"> <p>AC 20-140</p> </td> <td valign="top" width="302"> <p>Guidelines for design approval of aircraft data communications systems</p> </td> </tr> <tr> <td valign="top" width="128"> <p>98-Air-PDC</p> </td> <td valign="top" width="302"> <p>Safety and Interoperability requirement for Pre-Departure-Clearance (PDC). (Air-100, April 21,1998)</p> </td> </tr> <tr> <td rowspan="3" valign="top" width="101"> <p>EUROCAE</p> </td> <td valign="top" width="128"> <p>ED 78</p> </td> <td valign="top" width="302"> <p>Guidance material for the establishment of data link supported ATS Services</p> </td> </tr> <tr> <td valign="top" width="128"> <p>ED-85A</p> </td> <td valign="top" width="302"> <p>Data Link Application System document (DLASD) for the “ departureClearance ” data link service</p> </td> </tr> <tr> <td valign="top" width="128"> <p>ED-112</p> </td> <td valign="top" width="302"> <p>Minimum operational performance specification for Crash protected airborne recorder systems</p> </td> </tr> <tr> <td valign="top" width="101"> <p>RTCA</p> </td> <td valign="top" width="128"> <p>DO 224</p> </td> <td valign="top" width="302"> <p>Minimum Aviation System Performance Standards (MASPS) for Advanced VHF Digital Data Communications Including Compatibility with Digital Voice Techniques.</p> </td> </tr> <tr> <td valign="top" width="101"> <p>SAE</p> </td> <td valign="top" width="128"> <p>ARP 4791</p> </td> <td valign="top" width="302"> <p>Human Machine Interface on the flight deck</p> </td> </tr> </table> 5          ASSUMPTIONS Applicants should note that this AMC is based on the assumptions stated in Chapter 3 of ED-85A together with the following that concern the measures taken by the responsible airspace authorities to safeguard DCL operations. 5.1       ATS Provider 5.1.1   The data link service for DCL has been shown to satisfy applicable airspace safety regulations and the relevant ATS domain performance, safety and interoperability requirements of ED-85A. 5.1.2   Procedures for the use of DCL take account of the performance limitations of ACARS and the airborne implementation capabilities meeting at least the provisions of this AMC. Note: Some aircraft ACARS installations approved to earlier standards are classified as “Non Essential” without guarantees of performance or integrity. Consequently,procedures are necessary to compensate for any deficiency and to safeguard operations. ED-85A addresses this issue. 5.1.3   Appropriate procedures are established to minimise the possibility of failure to detect inconsistency in the case of a complex clearance. 5.1.4   Each ATS provider has published a list of communication service providers that may be used by aircraft operators for the DCL application. The list should take account of internetworking arrangements between service providers. 5.1.5   The procedures of the ATS provider state the actions that should be taken in the event of an inadequate communication service from the communications service provider (CSP). 5.2       Communications Service Provider The communications service provider does not modify the operational information (content and format) exchanged between the ATS provider and the airborne equipment. 5.3       Aeronautical Information Service Each State offering a DCL service by data link publishes in its AIP, or equivalent notification, availability of the service, relevant procedures, and confirmation of compliance with ED-85A. 5.4       Message Integrity The Cyclic Redundancy Check (CRC) is implemented as required by ED-85A and is providing integrity of the end-to-end data link transmission path. On this basis, Performance Technical Requirement PTR\_3 of ED-85A need not be demonstrated. 6          AIRWORTHINESS CONSIDERATIONS 6.1       General 6.1.1   The installation will need to be shown compliant with the airborne domain requirements allocated as per ED-85A (§7.1) covering the Interoperability Operational Requirements, the Interoperability Technical Requirements, the Performance Technical Requirements, the Safety Operational & Technical Requirements. 6.1.2   If multiple ATS data link applications are available to the aircraft, the crew interface and related crew procedures will need to be based on a common and compatible philosophy. 6.2       Required Functions An acceptable minimum airborne installation comprises the following functions: (a)       A means of data communication appropriate to the area of operation, e.g. plain old ACARS over AVLC (Aviation VHF Link Control) through VHF or SATCOM; Note: VDL Mode 2 equipment can be used provided that radio transceiver is compliant with ED-92A. (b)      A means to manage data communications and to control the data communications system; (c)       A means to easily check and modify the parameters of the DCL request; (d)      “Visual” alerting of an incoming message, visible to both pilots; (e)      Means to display the text message, e.g. a single display readable by both crewmembers or a dedicated display for each pilot. (f)       A means to accept the DCL delivered by the ATS. 6.3       Recommended Functions (a)       “Audible” alerting of an incoming message; (b)      A means to print the messages; (c)       Recording of DCL messages and flight crew responses on an accident flight recorder. Note: Data Link recording may be required in accordance with OPS rules. 7          ACCEPTABLE MEANS OF AIRWORTHINESS COMPLIANCE 7.1       Airworthiness 7.1.1   When demonstrating compliance with this AMC, the following specific points should be noted: (a)       Compliance with the airworthiness requirements for intended function and safety may be demonstrated by equipment qualification, safety analysis of the interface between the communications management system and data sources, structural analyses of new antenna installations, equipment cooling verification, and evidence of a suitable human to machine interface. The DCL function will need to be demonstrated by end-to-end ground testing that verifies system operation, either with an appropriate ATS unit, or by means of test equipment that has been shown to be representative of the actual ATS unit. Note: This limited testing assumes that the communication systems (VHF or SATCOM) have been shown to satisfactorily perform their intended functions in the flight environment in accordance with applicable requirements. (b)       The safety analysis of the interface between the communications management system and its data sources should show that, under normal or fault conditions, no unwanted interaction which adversely affects essential systems can occur. 7.1.2   To minimise the certification effort for follow-on installations credit may be granted for applicable certification and test data obtained from equivalent aircraft installations. 7.2       Performance The installation should be shown to meet the airborne domain performance requirements allocated by ED-85A (§7.1). Demonstration of Performance Technical Requirement PTR\_A1 may be difficult for some airborne installations. The applicant may choose an alternative acceptable means of compliance for PTR\_A1 consisting in an end-to-end demonstration of PTR\_5 & PTR-6 of ED-85A (§5.2) with an appropriate ATS unit and communication service provider. 7.3       Aircraft Flight Manual The Flight Manual should state the following limitation. Note: This limited entry assumes that a detailed description of the installed system and related operating instructions are available in other operating or training manuals and that operating procedures take account of ED-85A. Limitation: The Departure Clearance (DCL) over ACARS application has been demonstrated with data link services declared compliant with EUROCAE document ED- 85A. 7.4       Existing installations The applicant will need to submit a compliance statement that shows how the criteria of this AMC have been satisfied for existing installations. Compliance may be established by inspection of the installed system to confirm the availability of required features and functionality. Note: It is not intended that aircraft which have received airworthiness approval in compliance with ED-85 requirement should be reinvestigated where the installation is compliant with Section 6, 7 and 8 of this AMC. 8          OPERATIONAL CONSIDERATIONS 8.1       Flight Plan Information 8.1.1   The Aircraft Identification transmitted by data link will need to conform to the ICAO format and correspond with the flight identity as entered in the applicable flight plan. 8.1.2   Aircraft type designator includes both Aircraft Type and Sub-type and shall be coded in accordance with the format described in ICAO document 8643 at its latest edition. However, certain ACARS equipment can be pre-programmed only with Aircraft Type with the possibility of manual insertion of Sub-type via the system control panel. Absence of the Sub-type information may lead either to a rejected departure clearance request at some airports, or the issue of an inappropriate clearance where the aircraft performance capability is not taken into account. Where, to obtain the DCL service, Sub-type needs to be entered manually, the entry should be verified. 8.2       Operational Safety Aspects 8.2.1   Failure Conditions are presented in ED-85A (§6) together with the resulting safety requirements and operational means of mitigation. Failure Condition FC3 (undetected erroneous SID) is discussed further in the following paragraphs. 8.2.2   When a SID construct is simple and unambiguous (e.g. only one SID for one runway magnetic orientation (QFU) and one destination) so allowing the flight crew and the ATS controller to independently detect any inconsistency in the DCL, then additional means of mitigation are not required. 8.2.3   For other, more complex cases where the SID construction prevents the flight crew and the controller from readily detecting any inconsistency, a specific flight crew to controller procedure will need to be implemented to verify the clearance. This may be stated in the AIP or other notification issued by the State where aircraft will operate and use DCL service. Note (1): In some countries (e.g. United Kingdom, AIC 125/1999, France AIC A19/00), following the investigation of level violations, voice confirmation of cleared altitude or flight level and SID identification is already required even for voice delivered departure clearance on the first contact with the approach control/departure radar. In such cases, no additional confirmation procedure is required. Note (2): The ATS may agree that voice confirmation is not required where the data link function is certificated with an integrity level corresponding to the Essential category of CS25.1309. 8.2.4   In all cases, flight crews will need to comply with any mitigating procedures published by the States where aircraft will operate and use DCL service. 8.2.5   The assumptions of Section 5 need to be satisfied as a condition for operational use. 8.3       Operations Manual and Training 8.3.1   The Operations Manual shall reflect the Flight Manual statement of paragraph 7.3 and define operating procedures for use of the DCL. 8.3.2   Flight crew training should address: (a)       The different data link services available using the same airborne equipment (e.g. differences between DCL and PDC applications as described in Annex 1); (b)       ATS procedures for DCL; and (c)       The required format for the flight identification input. 8.3.3   Subject to any arrangements that may be required by the responsible operations authority in respect of amendments to the Operations Manual, and the approval of training programmes, the aircraft operator may implement operations using DCL over ACARS. 8.4       Incident reporting Significant incidents associated with a departure clearance transmitted by data link that affects or could affect the safe operation of the aircraft will need to be reported in accordance with applicable operational rules, and to the authority responsible for the airport where the DCL service was provided. AVAILABILITY OF DOCUMENTS EUROCAE documents may be purchased from EUROCAE, 17 rue Hamelin, 75783 Paris Cedex 16, France, (Fax: 33 1 45 05 72 30). Web site: [www.eurocae.org](http://www.eurocae.org/). JAA documents are available from the JAA publisher Information Handling Services (IHS). Information on prices, where and how to order is available on both the JAA web site [www.jaa.nl](http://www.jaa.nl/)and the IHS web site [www.avdataworks.com](http://www.avdataworks.com/). EUROCONTROL documents may be requested from EUROCONTROL, Documentation Centre, GS4, Rue de la Fusee, 96, B-1130 Brussels, Belgium; (Fax: 32 2 729 9109 or web site [www.eurocontrol.int](http://www.eurocontrol.int)). ICAO documents may be purchased from Document Sales Unit, International Civil Aviation Organisation, 999 University Street, Montreal, Quebec, Canada H3C 5H7, (Fax: 1 514 954 6769, e-mail: sales\_unit@icao.org) or through national agencies. FAA documents may be obtained from Department of Transportation, Subsequent Distribution Office SVC-121.23, Ardmore East Business Centre, 3341 Q 75th Avenue, Landover, MD 20785, USA. Web site [www.faa.gov/aviation.htm](http://www.faa.gov/aviation.htm) RTCA documents may be obtained from RTCA Inc, 1828 L Street, NW., Suite 805, Washington, DC 20036, USA., (Tel: 1 202 833 9339; Fax 1 202 833 9434). Web site:[www.rtca.org](http://www.rtca.org/). SAE documents may be obtained from SAE World Headquarters, 400 Commonwealth Drive, Warrendale, PA 15096-0001, USA. Telephone 1-877-606-7323 (U.S. and Canada only) or 724/776-4970 (elsewhere). Web site [www.sae.org](http://www.sae.org/). [Amdt 20/1] --- [[6]](#_ftnref6)     Information on LINK2000+ is available at web site [www.eurocontrol.int/link2000](http://www.eurocontrol.int/link2000) AMC 20-9 Acceptable Means of Compliance for the Approval of Departure Clearance via Data Communications over ACARS ED Decision 2006/012/R 1 PREAMBLE 1.1 This AMC is issued in response to the EUROCONTROL Convergence and Implementation Plan that recommends an interim deployment of air-to-ground and ground- to-air data link applications based on the existing airline ACARS technology. One such application is Departure Clearance (DCL) data link now operational at various airports in Europe (as indicated in AIPs). Aircraft operators, on a voluntary basis, may take advantage of DCL over ACARS where it is available, subject to any arrangements that may be required by their responsible operations authority. 1.2 The use of ACARS for data link purposes is a transitional step to data link applications that will use VDL Mode 2 and the Aeronautical Telecommunications Network (ATN), compliant with ICAO SARPS, as proposed in the EUROCONTROL LINK2000+ programme[[6]](#_ftn6). 1.3 Described in EUROCAE document ED-85A (hereafter “ED-85A”), Data Link Application System document (DLASD) for the “Departure Clearance” Data Link Service, DCL over ACARS is a control tower application providing direct communication between the flight crew and the air traffic controller. ED-85A addresses three domains: airborne, ground ATC, and communication service providers. It deals also with associated flight crew and controller procedures. ED-85A takes account of EUROCAE document ED-78 which describes the global processes including approval planning, co-ordinated requirements determination, development and qualification of a system element, entry into service, and operations. 2 PURPOSE 2.1 This AMC is intended for operators seeking to use Departure Clearance via data link over ACARS as described in ED-85A. It may assist also other stakeholders such as airspace planners, air traffic service providers, ATS system manufacturers, communication service providers, aircraft and equipment manufacturers, and ATS regulatory authorities to advise them of the airborne requirements and procedures, and the related assumptions. 2.2 This AMC provides a method for evaluating compliance of a data link system to the requirements of ED-85A, and the means by which an aircraft operator can satisfy an authority that operational considerations have been addressed. 3 SCOPE 3.1 This AMC addresses DCL over ACARS using the ARINC 623 protocol as elaborated in EUROCAE document ED-85A and promoted by the EUROCONTROL Convergence and Implementation Plan as an interim data link application pending maturity of the LINK2000+ programme. The AMC is not directly applicable to Pre-Departure Clearance (PDC) as used in the USA and some other states. For PDC approval, guidance may be found in FAA document Safety and Interoperability Requirements for Pre- Departure Clearance, issued by AIR-100 on April 21, 1998. A comparison of PDC with DCL may be found in Appendix 1. 3.2 This AMC is not applicable to the phased implementation of data link services within the EUROCONTROL LINK2000+ programme, in particular, DCL over the Aeronautical Telecommunications Network via VHF Digital Data Link (VDL) Mode 2. In this case, the Safety and Performance Requirements (EUROCAE ED-120) and the Interoperability Requirements (EUROCAE ED-110) are established using EUROCAE document ED-78A, Guidelines for Approval of the Provision and use of Air Traffic Services supported by Data Communications. Guidance for the implementation of DCL over ATN may be found in EASA document AMC 20-11. 3.3 The operational requirements for the DCL application are published in the EUROCONTROL document OPR/ET1/ST05/1000, Edition 2, October 15,1996, Transition guidelines for initial air ground data communication services. The EUROCONTROL document includes the re-issued clearance capability, however document ED-85A does not address this capability and it is not included in the scope of this AMC. 3.4 For the remainder of this document, the acronym DCL should be interpreted to mean DCL over ACARS using the ARINC 623 protocol unless stated otherwise. 4 REFERENCE DOCUMENTS 4.1 Related Requirements CS/FAR 25.1301, 25.1307, 25.1309, 25.1322, 25.1431, 25.1581, or equivalent requirementsof CS 23, 27 and 29 if applicable. 4.2 Related Standards and Guidance Material <table border="1" cellpadding="0" cellspacing="0" width="531"><tr><td rowspan="6" valign="top" width="101"><p>ICAO</p></td><td valign="top" width="128"><p>Doc 9694 AN/955</p></td><td valign="top" width="302"><p>Manual of Air Traffic Services (ATS) DataLink Applications</p></td></tr><tr><td valign="top" width="128"><p>Doc 4444</p></td><td valign="top" width="302"><p>Rules of the Air and Air Traffic Services</p></td></tr><tr><td valign="top" width="128"><p>Draft Proposal</p></td><td valign="top" width="302"><p>PANS-Air Traffic Management</p></td></tr><tr><td valign="top" width="128"><p>Annex 11</p></td><td valign="top" width="302"><p>Air Traffic Services</p></td></tr><tr><td valign="top" width="128"><p>Doc 8585</p></td><td valign="top" width="302"><p>Designators for Aircraft Operating agencies,Aeronautical Authorities and Services</p></td></tr><tr><td valign="top" width="128"><p>Doc 8643</p></td><td valign="top" width="302"><p>Aircraft Type Designators</p></td></tr><tr><td valign="top" width="101"><p>EASA</p></td><td valign="top" width="128"><p>AMC 25-11</p></td><td valign="top" width="302"><p>Electronic Display Systems</p></td></tr><tr><td rowspan="3" valign="top" width="101"><p>EUROCONTROL</p></td><td valign="top" width="128"><p>CIP:COM.</p><p>ET2.SO4;2.1.5</p></td><td valign="top" width="302"><p>Implement Air/Ground Communication</p><p>Services- Interim step on non-ATN (ACARS)services.</p></td></tr><tr><td valign="top" width="128"><p>OPR/ET1/ST05/1000</p></td><td valign="top" width="302"><p>Transition guidelines for initial air ground data communication services</p></td></tr><tr><td valign="top" width="128"><p>ESARR 4</p></td><td valign="top" width="302"><p>Risk assessment and mitigation in ATM</p></td></tr><tr><td rowspan="4" valign="top" width="101"><p>FAA</p></td><td valign="top" width="128"><p>AC 25-11</p></td><td valign="top" width="302"><p>Electronic Display Systems.</p></td></tr><tr><td valign="top" width="128"><p>AC 120-COM</p></td><td valign="top" width="302"><p>Initial Air Carrier Operational Approval for use of Digital Communication Systems</p></td></tr><tr><td valign="top" width="128"><p>AC 20-140</p></td><td valign="top" width="302"><p>Guidelines for design approval of aircraft data communications systems</p></td></tr><tr><td valign="top" width="128"><p>98-Air-PDC</p></td><td valign="top" width="302"><p>Safety and Interoperability requirement for Pre-Departure-Clearance (PDC). (Air-100, April 21,1998)</p></td></tr><tr><td rowspan="3" valign="top" width="101"><p>EUROCAE</p></td><td valign="top" width="128"><p>ED 78</p></td><td valign="top" width="302"><p>Guidance material for the establishment of data link supported ATS Services</p></td></tr><tr><td valign="top" width="128"><p>ED-85A</p></td><td valign="top" width="302"><p>Data Link Application System document (DLASD) for the “ departureClearance ” data link service</p></td></tr><tr><td valign="top" width="128"><p>ED-112</p></td><td valign="top" width="302"><p>Minimum operational performance specification for Crash protected airborne recorder systems</p></td></tr><tr><td valign="top" width="101"><p>RTCA</p></td><td valign="top" width="128"><p>DO 224</p></td><td valign="top" width="302"><p>Minimum Aviation System Performance Standards (MASPS) for Advanced VHF Digital Data Communications Including Compatibility with Digital Voice Techniques.</p></td></tr><tr><td valign="top" width="101"><p>SAE</p></td><td valign="top" width="128"><p>ARP 4791</p></td><td valign="top" width="302"><p>Human Machine Interface on the flight deck</p></td></tr></table> 5 ASSUMPTIONS Applicants should note that this AMC is based on the assumptions stated in Chapter 3 of ED-85A together with the following that concern the measures taken by the responsible airspace authorities to safeguard DCL operations. 5.1 ATS Provider 5.1.1 The data link service for DCL has been shown to satisfy applicable airspace safety regulations and the relevant ATS domain performance, safety and interoperability requirements of ED-85A. 5.1.2 Procedures for the use of DCL take account of the performance limitations of ACARS and the airborne implementation capabilities meeting at least the provisions of this AMC. Note: Some aircraft ACARS installations approved to earlier standards are classified as “Non Essential” without guarantees of performance or integrity. Consequently,procedures are necessary to compensate for any deficiency and to safeguard operations. ED-85A addresses this issue. 5.1.3 Appropriate procedures are established to minimise the possibility of failure to detect inconsistency in the case of a complex clearance. 5.1.4 Each ATS provider has published a list of communication service providers that may be used by aircraft operators for the DCL application. The list should take account of internetworking arrangements between service providers. 5.1.5 The procedures of the ATS provider state the actions that should be taken in the event of an inadequate communication service from the communications service provider (CSP). 5.2 Communications Service Provider The communications service provider does not modify the operational information (content and format) exchanged between the ATS provider and the airborne equipment. 5.3 Aeronautical Information Service Each State offering a DCL service by data link publishes in its AIP, or equivalent notification, availability of the service, relevant procedures, and confirmation of compliance with ED-85A. 5.4 Message Integrity The Cyclic Redundancy Check (CRC) is implemented as required by ED-85A and is providing integrity of the end-to-end data link transmission path. On this basis, Performance Technical Requirement PTR\_3 of ED-85A need not be demonstrated. 6 AIRWORTHINESS CONSIDERATIONS 6.1 General 6.1.1 The installation will need to be shown compliant with the airborne domain requirements allocated as per ED-85A (§7.1) covering the Interoperability Operational Requirements, the Interoperability Technical Requirements, the Performance Technical Requirements, the Safety Operational & Technical Requirements. 6.1.2 If multiple ATS data link applications are available to the aircraft, the crew interface and related crew procedures will need to be based on a common and compatible philosophy. 6.2 Required Functions An acceptable minimum airborne installation comprises the following functions: (a) A means of data communication appropriate to the area of operation, e.g. plain old ACARS over AVLC (Aviation VHF Link Control) through VHF or SATCOM; Note: VDL Mode 2 equipment can be used provided that radio transceiver is compliant with ED-92A. (b) A means to manage data communications and to control the data communications system; (c) A means to easily check and modify the parameters of the DCL request; (d) “Visual” alerting of an incoming message, visible to both pilots; (e) Means to display the text message, e.g. a single display readable by both crewmembers or a dedicated display for each pilot. (f) A means to accept the DCL delivered by the ATS. 6.3 Recommended Functions (a) “Audible” alerting of an incoming message; (b) A means to print the messages; (c) Recording of DCL messages and flight crew responses on an accident flight recorder. Note: Data Link recording may be required in accordance with OPS rules. 7 ACCEPTABLE MEANS OF AIRWORTHINESS COMPLIANCE 7.1 Airworthiness 7.1.1 When demonstrating compliance with this AMC, the following specific points should be noted: (a) Compliance with the airworthiness requirements for intended function and safety may be demonstrated by equipment qualification, safety analysis of the interface between the communications management system and data sources, structural analyses of new antenna installations, equipment cooling verification, and evidence of a suitable human to machine interface. The DCL function will need to be demonstrated by end-to-end ground testing that verifies system operation, either with an appropriate ATS unit, or by means of test equipment that has been shown to be representative of the actual ATS unit. Note: This limited testing assumes that the communication systems (VHF or SATCOM) have been shown to satisfactorily perform their intended functions in the flight environment in accordance with applicable requirements. (b) The safety analysis of the interface between the communications management system and its data sources should show that, under normal or fault conditions, no unwanted interaction which adversely affects essential systems can occur. 7.1.2 To minimise the certification effort for follow-on installations credit may be granted for applicable certification and test data obtained from equivalent aircraft installations. 7.2 Performance The installation should be shown to meet the airborne domain performance requirements allocated by ED-85A (§7.1). Demonstration of Performance Technical Requirement PTR\_A1 may be difficult for some airborne installations. The applicant may choose an alternative acceptable means of compliance for PTR\_A1 consisting in an end-to-end demonstration of PTR\_5 & PTR-6 of ED-85A (§5.2) with an appropriate ATS unit and communication service provider. 7.3 Aircraft Flight Manual The Flight Manual should state the following limitation. Note: This limited entry assumes that a detailed description of the installed system and related operating instructions are available in other operating or training manuals and that operating procedures take account of ED-85A. Limitation: The Departure Clearance (DCL) over ACARS application has been demonstrated with data link services declared compliant with EUROCAE document ED- 85A. 7.4 Existing installations The applicant will need to submit a compliance statement that shows how the criteria of this AMC have been satisfied for existing installations. Compliance may be established by inspection of the installed system to confirm the availability of required features and functionality. Note: It is not intended that aircraft which have received airworthiness approval in compliance with ED-85 requirement should be reinvestigated where the installation is compliant with Section 6, 7 and 8 of this AMC. 8 OPERATIONAL CONSIDERATIONS 8.1 Flight Plan Information 8.1.1 The Aircraft Identification transmitted by data link will need to conform to the ICAO format and correspond with the flight identity as entered in the applicable flight plan. 8.1.2 Aircraft type designator includes both Aircraft Type and Sub-type and shall be coded in accordance with the format described in ICAO document 8643 at its latest edition. However, certain ACARS equipment can be pre-programmed only with Aircraft Type with the possibility of manual insertion of Sub-type via the system control panel. Absence of the Sub-type information may lead either to a rejected departure clearance request at some airports, or the issue of an inappropriate clearance where the aircraft performance capability is not taken into account. Where, to obtain the DCL service, Sub-type needs to be entered manually, the entry should be verified. 8.2 Operational Safety Aspects 8.2.1 Failure Conditions are presented in ED-85A (§6) together with the resulting safety requirements and operational means of mitigation. Failure Condition FC3 (undetected erroneous SID) is discussed further in the following paragraphs. 8.2.2 When a SID construct is simple and unambiguous (e.g. only one SID for one runway magnetic orientation (QFU) and one destination) so allowing the flight crew and the ATS controller to independently detect any inconsistency in the DCL, then additional means of mitigation are not required. 8.2.3 For other, more complex cases where the SID construction prevents the flight crew and the controller from readily detecting any inconsistency, a specific flight crew to controller procedure will need to be implemented to verify the clearance. This may be stated in the AIP or other notification issued by the State where aircraft will operate and use DCL service. Note (1): In some countries (e.g. United Kingdom, AIC 125/1999, France AIC A19/00), following the investigation of level violations, voice confirmation of cleared altitude or flight level and SID identification is already required even for voice delivered departure clearance on the first contact with the approach control/departure radar. In such cases, no additional confirmation procedure is required. Note (2): The ATS may agree that voice confirmation is not required where the data link function is certificated with an integrity level corresponding to the Essential category of CS25.1309. 8.2.4 In all cases, flight crews will need to comply with any mitigating procedures published by the States where aircraft will operate and use DCL service. 8.2.5 The assumptions of Section 5 need to be satisfied as a condition for operational use. 8.3 Operations Manual and Training 8.3.1 The Operations Manual shall reflect the Flight Manual statement of paragraph 7.3 and define operating procedures for use of the DCL. 8.3.2 Flight crew training should address: (a) The different data link services available using the same airborne equipment (e.g. differences between DCL and PDC applications as described in Annex 1); (b) ATS procedures for DCL; and (c) The required format for the flight identification input. 8.3.3 Subject to any arrangements that may be required by the responsible operations authority in respect of amendments to the Operations Manual, and the approval of training programmes, the aircraft operator may implement operations using DCL over ACARS. 8.4 Incident reporting Significant incidents associated with a departure clearance transmitted by data link that affects or could affect the safe operation of the aircraft will need to be reported in accordance with applicable operational rules, and to the authority responsible for the airport where the DCL service was provided. AVAILABILITY OF DOCUMENTS EUROCAE documents may be purchased from EUROCAE, 17 rue Hamelin, 75783 Paris Cedex 16, France, (Fax: 33 1 45 05 72 30). Web site: [www.eurocae.org](http://www.eurocae.org/). JAA documents are available from the JAA publisher Information Handling Services (IHS). Information on prices, where and how to order is available on both the JAA web site [www.jaa.nl](http://www.jaa.nl/)and the IHS web site [www.avdataworks.com](http://www.avdataworks.com/). EUROCONTROL documents may be requested from EUROCONTROL, Documentation Centre, GS4, Rue de la Fusee, 96, B-1130 Brussels, Belgium; (Fax: 32 2 729 9109 or web site [www.eurocontrol.int](http://www.eurocontrol.int)). ICAO documents may be purchased from Document Sales Unit, International Civil Aviation Organisation, 999 University Street, Montreal, Quebec, Canada H3C 5H7, (Fax: 1 514 954 6769, e-mail: sales\_unit@icao.org) or through national agencies. FAA documents may be obtained from Department of Transportation, Subsequent Distribution Office SVC-121.23, Ardmore East Business Centre, 3341 Q 75th Avenue, Landover, MD 20785, USA. Web site [www.faa.gov/aviation.htm](http://www.faa.gov/aviation.htm) RTCA documents may be obtained from RTCA Inc, 1828 L Street, NW., Suite 805, Washington, DC 20036, USA., (Tel: 1 202 833 9339; Fax 1 202 833 9434). Web site:[www.rtca.org](http://www.rtca.org/). SAE documents may be obtained from SAE World Headquarters, 400 Commonwealth Drive, Warrendale, PA 15096-0001, USA. Telephone 1-877-606-7323 (U.S. and Canada only) or 724/776-4970 (elsewhere). Web site [www.sae.org](http://www.sae.org/). [Amdt 20/1] --- [[6]](#_ftnref6) Information on LINK2000+ is available at web site [www.eurocontrol.int/link2000](http://www.eurocontrol.int/link2000)