text: AMC and GM to Part-ADR.AR Issue 1, Amendment 9

text: N o t e t o t h e re a d e r

text: In amended, and in particular in existing (that is, unchanged) text, ‘Agency’ is used interchangeably with ‘EASA’. The interchangeable use of these two terms is more apparent in the consolidated versions. Therefore, please note that both terms refer to the ‘European Union Aviation Safety Agency (EASA)’.

text: Annex V to ED Decision 2023/010/R Page 1 of 2

text: Annex V to ED Decision 2023/010/R Page 2 of 2

identifier: AMC & GM to Part-ADR.AR — Issue 1, Amendment 9

beslut: ED Decision 2023/010/R

text: Annex V to ED Decision 2023/010/R ‘AMC and GM to Part-ADR.AR — Issue 1, Amendment 9’

text: The text of the amendment is arranged to show deleted, new or amended text as follows:

text: — deleted text is struck through;

text: — new or amended text is highlighted in cyan;

text: — an ellipsis ‘[…]’ indicates that the rest of the text is unchanged.

text: The Annex to Decision 2014/012/R of 27 February 2014 of the Executive Director of the Agency is amended as follows:

text: AMC1 ADR.AR.A.030A Immediate reaction to an information security incident or vulnerability with an impact on aviation safety

text: (a) To appropriately collect and analyse information related to information security incidents and vulnerabilities with a potential impact on aviation safety, the competent authority should implement means that ensure the necessary confidentiality. (b) When disseminating information related to information security incidents and vulnerabilities with a potential impact on aviation safety, the competent authority should properly select the appropriate recipient(s) to prevent the content of a report from being exploited to the detriment of aviation safety, by revealing, for instance, uncorrected vulnerabilities.

text: GM1 ADR.AR.A.030A Immediate reaction to an information security incident or vulnerability with an impact on aviation safety

text: When deemed necessary, a two-step mechanism could be used: a report alerting about the information security event or incident and the availability of additional data that would require controlled and confidential distribution. This report should only alert recipients of the urgency and the necessity for organisations and competent authorities to establish further communication through secure means. Therefore, the report should consist of two parts: one limited to mostly public information and one containing the sensitive data that should be restricted to the recipients who need to know. Wherever possible, reports should be based on an agreed taxonomy.

text: AMC1 ADR.AR.B.010(a)(1) Allocation of tasks to qualified entities

text: GM1 ADR.AR.B.010 Allocation of tasks to qualified entities

type: vagledning

utgivare: easa


text: Annex VI to ED Decision 2020/008/R

text: AMC and GM to Part-AIS Issue 1, Amendment 1

text: Annex VI to ED Decision 2020/008/R Page 7 of 31

text: Annex VI to ED Decision 2020/008/R Page 8 of 31

text: Annex VI to ED Decision 2020/008/R Page 9 of 31

text: Annex VI to ED Decision 2020/008/R Page 10 of 31

text: Annex VI to ED Decision 2020/008/R Page 11 of 31

text: Annex VI to ED Decision 2020/008/R Page 12 of 31

text: Annex VI to ED Decision 2020/008/R Page 13 of 31

text: Annex VI to ED Decision 2020/008/R Page 14 of 31

text: Annex VI to ED Decision 2020/008/R Page 15 of 31

text: Annex VI to ED Decision 2020/008/R Page 16 of 31

text: Annex VI to ED Decision 2020/008/R Page 17 of 31

text: Annex VI to ED Decision 2020/008/R Page 18 of 31

text: Annex VI to ED Decision 2020/008/R Page 19 of 31

text: Annex VI to ED Decision 2020/008/R Page 20 of 31

text: Annex VI to ED Decision 2020/008/R Page 21 of 31

text: Annex VI to ED Decision 2020/008/R Page 22 of 31

text: Annex VI to ED Decision 2020/008/R Page 23 of 31

text: Annex VI to ED Decision 2020/008/R Page 24 of 31

text: Annex VI to ED Decision 2020/008/R Page 25 of 31

text: Annex VI to ED Decision 2020/008/R Page 26 of 31

text: Annex VI to ED Decision 2020/008/R Page 27 of 31

text: Annex VI to ED Decision 2020/008/R Page 28 of 31

text: Annex VI to ED Decision 2020/008/R Page 29 of 31

text: Annex VI to ED Decision 2020/008/R Page 30 of 31

text: Annex VI to ED Decision 2020/008/R Page 31 of 31

identifier: AMC & GM to Part-AIS — Issue 1, Amendment 1

beslut: ED Decision 2020/008/R

publisher: Europeiska unionens byrå för luftfartssäkerhet

sprak: en

title: AMC & GM to Part-AIS — Issue 1, Amendment 1

serie: amc-gm

text: ‘AMC and GM to Part-AIS — Issue 1, Amendment 1’

type: rubrik

text: Annex VI to Decision 2017/001/R is amended as follows: The text of the amendment is arranged to show deleted text, new or amended text as shown below: (a) deleted text is struck through; (b) new or amended text is highlighted in blue; (c) an ellipsis ‘[…]’ indicates that the rest of the text is unchanged.

type: stycke

text: AMC/GM TO PART-AIS SPECIFIC REQUIREMENTS FOR PROVIDERS OF AERONAUTICAL INFORMATION SERVICES

text: Reserved

text: SUBPART A — ADDITIONAL ORGANISATION REQUIREMENTS FOR PROVIDERS OF AERONAUTICAL INFORMATION SERVICES (AIS.OR)

text: Section 1 — General requirements

text: GM1 AIS.OR.100 Aeronautical information management

text: AERONAUTICAL INFORMATION

text: (a) The object of aeronautical information services is to ensure the flow of aeronautical data and aeronautical information necessary for global air traffic management (ATM) system safety, regularity, economy and efficiency in an environmentally sustainable manner. (b) The role and importance of aeronautical data and aeronautical information changed significantly with the implementation of area navigation (RNAV), performance-based navigation (PBN), airborne computer-based navigation systems, performance-based communication (PBC), performance-based surveillance (PBS), data link systems and satellite voice communications (SATVOICE). Corrupt, erroneous, late, or missing aeronautical data and aeronautical information can potentially affect the safety of air navigation. (c) Guidance material on the organisation and operation of aeronautical information services is contained in ICAO Doc 8126 ‘Aeronautical Information Services Manual’.

text: PERSONNEL INVOLVED IN FLIGHT OPERATIONS, INCLUDING FLIGHT CREWS, FLIGHT PLANNING, AND FLIGHT SIMULATORS

text: The data services (DAT) providers are considered as one of the entities or parties listed in AIS.OR.105(1). They also receive, assemble, translate, select, format, distribute and/or integrate aeronautical data and information that are released by an authoritative source for use in aeronautical databases on certified aircraft application/equipment.

text: SERVICES RESPONSIBLE FOR PRE-FLIGHT INFORMATION

text: An AIS provider obtains aeronautical data and aeronautical information to provide pre-flight information service and to meet the need for in-flight information from: (a) the aeronautical information services of other States; (b) other sources that may be available.

text: GM1 AIS.OR.105 Responsibilities of aeronautical information services providers

text: AVAILABILITY OF AERONAUTICAL DATA AND AERONAUTICAL INFORMATION

text: An AIS provider is not obliged to provide data or information requested by other AIS providers when they are not available.

text: Section 2 — Data quality management

text: GM1 AIS.OR.200(a) General

text: AERONAUTICAL DATA CATALOGUE

text: The aeronautical data catalogue presents the scope of data that can be collected and maintained by the AIS providers and provides a common terminology that can be used by data originators and service providers.

text: GM1 AIS.OR.200(b) General

text: DATA QUALITY

text: The quality of data is a degree or level of confidence that the data provided meets the requirements of the user. Minimum requirements for the processing of aeronautical data may be found in the EUROCAE Document ED-76A ‘Standards for Processing Aeronautical Data’ which aims to assist aeronautical data chain actors and authorities in meeting their responsibilities. It is intended to be used by organisations seeking approval of the method(s) they use to process or manipulate data.

text: AMC1 AIS.OR.200(c) General

text: AUTOMATED DATA PROCESSING

text: Where processes or parts of processes used in the origination, production, storage, handling, processing, transfer and distribution of aeronautical data and aeronautical information are subject to automation, they should be: (a) automated to a level commensurate with the context of the data process; (b) automated to optimise the allocation and interaction of human and machine to achieve a high degree of safety and quality benefits of the process; (c) automated to ensure traceability of the performed actions; (d) designed to avoid the introduction of data errors; and (e) designed to detect errors in received/input data.

text: AMC1 AIS.OR.205 Formal arrangements

text: MINIMUM CONTENT

text: Formal arrangements should include the following minimum content: (a) the aeronautical data to be provided; (b) the data quality requirements (DQRs) for each data item supplied according to the aeronautical data catalogue; (c) the method(s) for demonstrating that the data provided conforms with the specified requirements; (d) the action to be taken in the event of discovery of a data error or inconsistency in any data provided; (e) the following minimum criteria for notification of data changes: (1) criteria for determining the timeliness of data provision based on the operational or safety significance of the change; (2) any prior notice of expected changes; and (3) the means to be adopted for notification; (f) the party responsible for documenting data changes; (g) data exchange details such as format or format change processes; (h) any limitations on the use of data; (i) requirements for the production of data origination quality reports; (j) metadata requirements; and (k) contingency requirements concerning the continuity of data provision.

text: AMC1 AIS.OR.210(a) Exchange of aeronautical data and aeronautical information

text: EXCHANGE MODEL

text: An AIS provider should use the aeronautical information exchange model (AIXM) to enable the management and distribution of aeronautical information services data in digital format.

text: GM1 AIS.OR.210(a) Exchange of aeronautical data and aeronautical information

text: EXCHANGE MODEL

text: (a) AIXM 5.1 is considered as being the minimum baseline for the exchange of aeronautical data and aeronautical information. (b) More information on the AIXM may be found under http://www.aixm.aero.

text: GM2 AIS.OR.210(a) Exchange of aeronautical data and aeronautical information

text: DIGITAL TERRAIN DATA

text: (a) The existing formats for the exchange of electronic terrain datasets do not fully meet the requirements of the ISO 19100 series on geographic information, therefore the GeoTIFF format and Shape file with metadata is preferred. (b) The list of most used terrain formats can be found in Appendix D to the EUROCONTROL ‘Terrain and Obstacle Data (TOD) Manual’ (edition 2.2, dated 28 November 2019)

text: GM1 AIS.OR.210(b) Exchange of aeronautical data and information

text: ELECTRONIC MEANS

text: The exchange of aeronautical data and aeronautical information may be done by a number of electronic exchanges avoiding the need of manual interaction with the data itself.

text: GM1 AIS.OR.215 Tools and software

text: SOFTWARE

text: (a) A means by which AIS.OR.215 can be met, is through the verification of software applied to a known executable version of the software in its target operating environment. (b) The verification of software is a process for ensuring that the software meets the requirements for the specified application or intended use of the aeronautical data and aeronautical information. (c) The verification of software evaluates the output of an aeronautical data and/or aeronautical information software development process to ensure correctness and consistency with respect to the inputs and applicable software standards, rules and conventions used in that process.

text: GM2 AIS.OR.215 Tools and software

text: TOOLS

text: Tools can be qualified meeting point 2.4.5 Aeronautical Data Tool Qualification of EUROCAE ED- 76A/RTCA DO-200B ‘Standards for Processing Aeronautical Data’, dated June 2015.

text: GM1 AIS.OR.220 Validation and verification

text: GENERAL

text: (a) Validation Validation is the activity where a data element is checked as having a value that is fully applicable to the identity ascribed to the data element, or a set of data elements is checked as being acceptable for their intended use.

text: The application of validation techniques considers the entire aeronautical data chain. This includes the validation performed by prior data chain participants and any requirements levied on the data supplier. Providing data integrity has been assured, there is no need to repeat earlier validations as a matter of course. Examples of validation techniques include the following: (1) Validation by application validates by applying data under test conditions. In certain cases, this may not be practical. Validation by application is considered to be the most effective form of validation. For example, flight inspection of final approach segment data prior to publication can be used to ensure that the published data is acceptable. (2) Logical consistency validates by comparing two different data sets or elements and identifying inconsistencies between values based on operative rules (e.g. business rules). (3) Semantic consistency validates by comparing data to an expected value or range of values for the data characteristics. (4) Validation by sampling evaluates a representative sample of data and applies statistical analysis to determine the confidence in the data quality. (b) Verification Verification is a process for checking the integrity of a data element whereby the data element is compared to another source, either from a different process or from a different point in the same process. While verification cannot ensure that the data is correct, it can be effective to ensure that the data has not been corrupted by the data process. The application of verification techniques considers only the portion of the aeronautical data chain controlled by the organisation. Yet, verification techniques may be applied at multiple phases of the data processing chain. Examples of verification techniques include the following: (1) Feedback testing is the comparison of a data set between its output and input state. (2) Independent redundancy testing involves processing the same data through two or more independent processes and comparing the data output of each process. (3) Update comparison involves comparison of updated data with its previous version. This comparison can identify all data elements that have changed. The list of changed elements can then be compared to a similar list generated by the supplier. A problem can be detected if an element is identified as changed on one list and not on the other.

text: AMC1 AIS.OR.220 Validation and verification

text: DATA PROTECTION

text: (a) The processes implemented to carry out validation and verification should define the means used to: (1) verify received data and confirm that the data has been received without corruption; (2) preserve data quality and ensure that stored data is protected from corruption; and

text: (3) confirm that originated data has not been corrupted prior to being stored. (b) Those processes should define the: (1) actions to be taken when data fails a verification or validation check; and (2) tools required for the verification and validation process.

text: GM1 AIS.OR.225 Metadata

text: PERSONAL DATA

text: When collecting metadata, the protection of individuals with regard to the processing of personal data and with regard to the free movement of such data applies, in accordance with

text: Regulation (EU) 2016/679

text: of the European Parliament and of the Council of 27 April 2016 on the protection of natural persons with regard to the processing of personal data and on the free movement of such data, and repealing Directive

text: (General Data Protection Regulation).

text: GM1 AIS.OR.230 Data error detection and authentication

text: GENERAL

text: More explanation and guidance on data security, including data error detection and authentication, may be found in Section 2 of EUROCAE ED-76A.

text: DATA ERROR DETECTION

text: An example of a digital error detection technique is the use of cyclic redundancy checks (CRCs). Coding techniques can be effective regardless of the transmission media (e.g. computer disks, modem communication, or internet).

text: GM1 AIS.OR.230(a) Data error detection and authentication

text: ERROR

text: The term ‘error’ is understood as being defective, degraded, lost, misplaced or corrupted data elements, or data elements not meeting stated quality requirements.

text: GM1 AIS.OR.235 Error reporting, error measurement and corrective actions

text: ERROR MANAGEMENT

text: (a) An AIS provider should have a system for handling errors and anomalies identified both during data processing and after delivery of the data to the users. (b) All problems reported with the data should be analysed and any errors or anomalies documented and resolved or addressed. (c) All errors or anomalies detected in the data should be resolved or addressed prior to delivery. (d) Information concerning any errors in the data that have been delivered should be made available to all affected users.

text: AMC1 AIS.OR.250 Consistency requirement

text: DUPLICATED INFORMATION

text: The AIS provider should ensure that: (a) coordination and explicit agreement are established with the AIS providers responsible for the aeronautical information publications (AIPs) of the States concerned before introducing changes in published border or cross-border data and information; and (b) periodic reviews are performed to detect inconsistencies between the AIPs of the States concerned.

text: GM1 AIS.OR.250 Consistency requirement

text: DUPLICATED INFORMATION

text: (a) Coordination and alignment processes between AIS providers should whenever possible be expanded beyond the AIP content and include all duplicated aeronautical data and information. (b) The AIS provider may identify and maintain a list of the data items and information which should be subject to coordination, for reference and use by its operational staff. (c) When establishing periodic reviews, the AIS provider may reflect those in formal arrangements established with other AIS providers.

text: Section 3 — Aeronautical information products

text: GM1 AIS.OR.300 Aeronautical information products

text: AERONAUTICAL DATA AND INFORMATION PROVIDED IN MULTIPLE FORMATS

text: ‘Aeronautical data and information provided in multiple formats’ refers to aeronautical data and aeronautical information provided using different products, such as data sets, electronic or paper products.

text: Chapter 1 — Aeronautical information in a standardised presentation

text: AMC1 AIS.OR.325 Aeronautical charts

text: PRODUCTION

text: Aeronautical charts should be produced in accordance with the specifications contained in ICAO Annex 4, Amendment No 61.

text: GM1 AIS.OR.330(a) NOTAM

text: SHORT DURATION / SHORT NOTICE

text: (a) The term ‘short duration’ should, in general, be understood as being less than 3 months.

text: (b) The term ‘short notice’ should be understood as insufficient time for the AIS provider to distribute an AIP supplement or amendment.

text: GM1 AIS.OR.330(b) NOTAM

text: TIMELY KNOWLEDGE

text: It may be considered that the knowledge of the information is ‘timely’ if it reaches the personnel involved with flight operations in time to ensure the safety, regularity and efficiency of flight operations.

text: GM2 AIS.OR.330(b) NOTAM

text: EXCEPTIONAL SITUATIONS

text: (a) It is recognised that, in the cases of NOTAM or digital NOTAM that are crucial to ensure the safety of flight, it is not always possible to comply with all the relevant provisions of the Regulation. However, it is also not possible to determine a priori all cases where this consideration may apply; this is dependent on a case-by-case individual assessment made by competent AIS staff. (b) If it is determined that it is not possible to comply with all the relevant provisions of the Regulation, the NOTAM office ensures, at the minimum, that: (1) the party originating the aeronautical data is authorised and/or an eligible/reasonable source; (2) the content is plausible; and (3) the DQRs are validated post publication, as soon as practicable.

text: Chapter 2 — Digital data sets

text: GM1 AIS.OR.335(a) General — Digital data sets

text: DATA SETS

text: Data items may appear in multiple data sets.

text: GM1 AIS.OR.345 AIP data set

text: GENERAL

text: The purpose of the AIP data set is to support the initial transition of the ATM domain towards the use of digital data sets instead of paper products. Therefore, its scope is defined considering the likelihood that the data contained in this set is actually being used in digital format by service providers, air traffic control and instrument flight rules/visual flight rules airspace users.

text: GM1 AIS.OR.350 Terrain and obstacle data – General requirements

text: GENERAL

text: (a) Useful information for those organisations involved in the origination, processing and provision of digital terrain and obstacle data, from the point at which the need for origination is identified through to the point when the Member State makes it available in accordance with the requirements of ICAO Annex 15, can be found in the EUROCONTROL ‘Terrain and Obstacle Data (TOD) Manual’ (edition 2.2, dated 28 November 2019). (b) In addition, EUROCAE ED-98C ‘User Requirements For Terrain And Obstacle Data’ (October 2015) provides guidance for data gathering by data originators, for data processing by data integrators, for implementation by application integrators, and for end use by the aviation community (e.g. air carriers, air traffic services, procedure designers).

text: GM2 AIS.OR.350 Terrain and obstacle data – General requirements

text: NAVIGATION APPLICATIONS

text: (a) Terrain and obstacle data are intended to be used in air navigation applications such as: (1) ground proximity warning system with forward-looking terrain avoidance function and minimum safe altitude warning (MSAW) system; (2) determination of contingency procedures for use in the event of an emergency during a missed approach or take-off; (3) aircraft operating limitations analysis; (4) instrument procedure design (including circling procedure); (5) determination of en-route ‘drift-down’ procedure and en-route emergency landing location; (6) advanced surface movement guidance and control system (A-SMGCS); and (7) aeronautical chart production and on-board databases. Additional information on the use of terrain and obstacle data can be found in Appendix C to EUROCAE ED-98C. (b) The data may also be used in other applications such as flight simulator and synthetic vision systems, and may assist in determining the height restriction or removal of obstacles that pose a hazard to air navigation.

text: GM1 AIS.OR.355 Terrain data sets

text: ADDITIONAL TERRAIN DATA

text: Where additional terrain data is collected to meet other aeronautical requirements, the terrain data sets may be expanded to include this additional data.

text: GM1 AIS.OR.355(b)(3) Terrain data sets

text: TAKE-OFF FLIGHT PATH AREA

text: ‘Take-off flight path area’ is defined in 3.8.2 of ICAO Annex 4.

text: GM1 AIS.OR.355(b)(4) Terrain data sets

text: AERODROME OBSTACLE LIMITATION SURFACES

text: ‘Aerodrome obstacle limitation surfaces’ are defined in Chapter H – Obstacle Limitation Surfaces of

text: Regulation (EU) No 139/2014

text: GM1 AIS.OR.360 Obstacle data sets

text: ADDITIONAL OBSTACLE DATA

text: Where additional obstacle data is collected to meet other aeronautical requirements, the obstacle data sets may be expanded to include this additional data.

text: Section 4 — Distribution and pre-flight information services

text: GM1 AIS.OR.400(a) Distribution services

text: DELIVERY METHOD

text: (a) The distribution of available aeronautical information products to the intended users differs in the delivery method applied which may either be: (1) physical distribution — the means by which aeronautical data and aeronautical information distribution is achieved through the delivery of a physical package, such as postal services; or (2) direct electronic distribution — the means by which aeronautical data and aeronautical information distribution is achieved automatically through the use of a direct electronic connection between the AIS provider and the intended user. (b) Different delivery methods and data media may require different procedures to ensure the required data quality. (c) Further guidance on digital dataset distribution can be found in ICAO Doc 10039 ‘Manual on System Wide Information Management (SWIM) Concept’. (d) Global communication networks and web services may be employed for the provision of aeronautical information products. (e) Guidance to assist the AIS providers in developing and adapting their systems for the distribution of the State AIP on the internet as an official and authoritative source of information may be found in the EUROCONTROL ‘Guidelines for Aeronautical Information Publication (AIP) distribution on the Internet’ (edition 1.0, dated October 2017).

text: GM1 AIS.OR.405(a) Pre-flight information services

text: COMMUNICATION

text: Pre-flight information may be provided as a verbal briefing or a self-briefing.

text: GM1 AIS.OR.405(b) Pre-flight information services

text: OPERATIONAL SIGNIFICANCE

text: (a) Geographic coverage for pre-flight information services should be determined and periodically reviewed. In general, the coverage zone should be limited to the flight information region (FIR) within which the aerodrome/heliport is located, the FIR(s) adjacent thereto, and all air route or portion of route flown without an intermediate landing, originating at the aerodrome/heliport and extending beyond the FIR(s) mentioned. (b) The elements of the aeronautical information products may be limited to national publications and when practicable, those of immediately adjacent States, provided that a complete library of aeronautical information is available at a central location and means of direct communications with that library are available. (c) A recapitulation of valid NOTAM of operational significance and other information of urgent character can be made available to flight crews in the form of plain-language pre-flight information bulletins (PIBs). (d) Guidance on the preparation of pre-flight information services and PIBs may be found in Chapter 8 of ICAO Doc 8126 ‘Aeronautical Information Services Manual’ and in Chapter 7 of the EUROCONTROL ‘Guidelines — Operating Procedures for AIS Dynamic Data (OPADD)’ (edition:4.0, dated 17 April 2015).

text: Section 5 — Aeronautical information products updates

text: GM1 AIS.OR.505 Aeronautical information regulation and control (AIRAC)

text: AIRAC SYSTEM

text: Further explanations with regard to the application of the AIRAC system can be found in the EUROCONTROL ‘Procedure for the Assessment of Information for Notification by AIRAC’ (SDP/8), (edition 2.0, dated 17 July 2009). Additional details can be found in SDP/9, 10 and 13 for specific products.

text: DISTRIBUTION

text: AIRAC information, distributed as a physical medium, should be sent at least 42 days in advance of the AIRAC effective dates with the objective of reaching recipients at least 28 days in advance of the effective date.

text: AMC1 AIS.OR.515 Data set updates

text: GENERAL

text: (a) When made available as a completely re-issued data set, the differences from the previously issued complete data set should be indicated. (b) When temporary changes of short duration are made available as digital data, they should use the same information model as the complete data set.

text: Section 6 — Personnel requirements

text: GM1 AIS.OR.600(b) General requirements

text: COMPETENCE

text: ‘Competence’ is understood as a situation where the personnel responsible for originating aeronautical data and aeronautical information possess the required level of knowledge, technical and behavioural skills and experience, and language proficiency when required, in order to be authorised to perform their duties.

text: AUTHORISATION

text: The authorisation of personnel is usually granted by the AIS provider, but it might be granted by another entity depending on the national arrangements for managing the competence and performance of AIS personnel.

text: SUBPART B — TECHNICAL REQUIREMENTS FOR PROVIDERS OF AERONAUTICAL INFORMATION SERVICES (AIS.TR)

text: Section 2 — Data quality management

text: GM1 AIS.TR.200(b) General

text: ACCURACY — RESOLUTION

text: (a) The resolution of the data contained in the database may be the same or finer than the publication resolution. (b) Stating that resolution needs to be commensurate with the accuracy means that digital data needs to have sufficient resolution to maintain accuracy. Typically, if an accuracy of .1 units is needed, then a resolution of 0.01 or .001 units would enable a data chain to preserve the accuracy without problems. A finer resolution could be misleading as one could assume that it supports a finer accuracy. This factor range of 10 to 100 between accuracy and resolution is applicable regardless of the units of measurements used.

text: AMC1 AIS.TR.200(d) General

text: TRACEABILITY

text: Aeronautical data and associated metadata should be kept for a minimum period of 5 years beyond the validity period of the associated aeronautical information.

text: AMC1 AIS.TR.210 Exchange of aeronautical data and aeronautical information

text: EXCHANGE MODELS

text: (a) The exchange model used should encompass the aeronautical data and aeronautical information to be exchanged. (b) The exchange model used should:

text: (1) use the unified modelling language (UML) to describe the aeronautical information features and their properties, associations and data types; (2) include data value constraints and data verification rules; (3) include provisions for metadata; (4) include a temporality model to enable capturing the evolution of the properties of an aeronautical information feature during its life cycle; (5) apply a commonly used data encoding format; (6) cover all the features, attributes, data types and associations of the aeronautical information model; and (7) provide an extension mechanism by which groups of users can extend the properties of existing features and add new features which do not adversely affect global standardisation.

text: GM1 to AMC1 AIS.TR.210 Exchange of aeronautical data and aeronautical information

text: ENABLING EXCHANGE

text: (a) The intent of using a commonly used data encoding format is to ensure interoperability of aeronautical data exchange between agencies and organisations involved in the data processing chain. (b) Examples of commonly used data encoding formats include extensible markup language (XML), geography markup language (GML), and JavaScript object notation (JSON).

text: AMC1 AIS.TR.225(a) Metadata

text: IDENTIFICATION

text: The metadata collected should clearly identify the organisation or entity originating the data, as well as any organisation or entity introducing amendments to the data.

text: AMC1 AIS.TR.225(b) Metadata

text: ACTION PERFORMED

text: The metadata reflecting each action performed involving origination or manipulation of the data should reflect any potential impact on the compliance with the applicable DQRs.

text: GM1 AIS.TR.225 Metadata

text: GENERAL

text: Further explanation on the schema required for describing geographic information and services by means of metadata may be found in the: (a) International Organization for Standardization, ISO 19115 — Geographic information — Metadata, Part I; and

text: (b) EUROCONTROL ‘Guidelines for the provision of Metadata to support the Exchange of Aeronautical Data’ (edition 1.0, dated 28 November 2019)

text: GM1 AIS.TR.240 Data limitations

text: ANNOTATION

text: (a) The objective of such an annotation is to notify the users of the AIS products including their aeronautical data that specific quality requirements are not met and may, therefore, compel limitations in the operational use of the relevant aeronautical data. (b) The following principles apply: (1) the solution applies for both the eAIP and paper AIP; (2) the use of the ‘asterisk’ is undesirable because it is already used for WGS-84 issues; (3) the non-compliance covers all parts of the AIP, i.e. textual aeronautical data and charts; and (4) non-compliant aeronautical data items shall be individually and explicitly identified and the use of any general statement with the intention of covering a range of data items shall be avoided. (c) The AIP section GEN 1.7 is used to identify non-compliant aeronautical data items. A new subheader should be introduced at the end of the current section named ‘Data non-compliant with European

text: Commission Regulation (EU) 2017/373

text: ’. (d) Within AIP GEN 1.7, the following two alternatives are proposed. The choice of which depends on national practicalities being based either on the amount of annotations to be published or on individual existing operational or technical constraints. (1) Annotation alternative 1 Alternative 1 is recommended if the number of identified non-compliances covers no more than two AIP pages. The relevant non-compliant data items shall be listed in a table, including as a minimum: — specific data item; — AIP section(s) concerned; — reason for non-compliance; — Notes/remarks. Proposed table format: Data Item AIP section Reason for non- Notes/remarks compliance

text: (2) Annotation alternative 2 Alternative 2 is recommended if the number of non-compliances extends more than two AIP pages. It should then contain a general (global) statement to indicate ‘Several data items are not compliant with the given regulation – details can be found online via <link>’. The link shall direct the user to a list on the website which must support compliance with minimum requirements: the list must be accessible online. Note: The indication of ‘available on request’, or similar, is clearly insufficient. The list must be kept up to date and fully synchronised (consistent) with the AIP update cycles, as relevant. This list should be in the form of a table as indicated under alternative 1 noting that it will be made available to users as an extra element outside the AIP.

text: GM1 AIS.TR.300(b) General — Aeronautical information products

text: PLACE NAMES

text: The phrase ‘when necessary’ means ‘for interoperability purposes’ e.g. in aeronautical information products that are intended to be processed by automated systems (NOTAM, data sets, etc.).

text: AMC1 AIS.TR.305(a) Aeronautical information publication (AIP)

text: ELECTRONIC FORM

text: The eAIP, eAIP amendments and eAIP supplements should be provided according to the EUROCONTROL ‘Specification for the Electronic Aeronautical Information Publication (eAIP)’ (edition 2.1, dated 6 October 2015).

text: AMC2 AIS.TR.305(a) Aeronautical information publication (AIP)

text: ELECTRONIC AIP

text: When provided, the eAIP should be available on a physical distribution medium (CD, DVD, etc.) and/or online on the internet.

text: GM1 AIS.TR.305(a) Aeronautical information publication (AIP)

text: PRINTED AIP

text: (a) A system of page numbering adaptable to the addition or deletion of sheets should be adopted. The page number should include: (1) an identification of the part of the AIP; (2) the section; and (3) subsection, as applicable, thus creating a separate set of numbers for each subject (e.g. GEN 2.1-3, ENR 4.1-1 or AD 2.2- 3).

text: (b) If it is necessary by reason of bulk or for convenience, to publish an AIP in two or more parts or volumes, each of them will indicate that the remainder of the information is to be found in the other part(s) or volume(s). (c) When the AIP is provided in more than one volume, each volume should include: (1) a preface; (2) a record of AIP amendments; (3) a record of AIP supplements; (4) a checklist of AIP pages; and (5) a list of current hand amendments. (d) When the AIP is published as one volume, the above-mentioned subsections should appear only in Part 1 — GEN and the annotation ‘not applicable’ should be entered against each of these subsections in Parts 2 and 3. (e) The AIP should be published in loose-leaf form unless the complete publication is reissued at frequent intervals. (f) Further guidelines for a harmonised AIP publication may be found in the EUROCONTROL ‘Guidelines for harmonised AIP publication and data set provision’ (edition 2.0, dated 23 May 2019).

text: GM1 AIS.TR.305(c) Aeronautical information publication (AIP)

text: INFORMATION RELATED TO LOCATIONS

text: When listing locations, the city or town should be given in capital letters followed, where the facility is an aerodrome/heliport or is located at an aerodrome/heliport, by an oblique stroke and the name of the aerodrome/heliport in smaller capital letters or lower-case letters. Unless otherwise indicated, the list should be in alphabetical order.

text: GM2 AIS.TR.305(c) Aeronautical information publication (AIP)

text: INFORMATION RELATED TO CHARTS, MAPS OR DIAGRAMS

text: (a) Charts, maps or diagrams should be used, when appropriate, to complement the AIP or serve as a substitute for the tabulations or text of the AIP. (b) Where appropriate, charts produced in conformity with AIS.OR.325 may be used to fulfil this requirement.

text: GM3 AIS.TR.305(c) Aeronautical information publication (AIP)

text: INFORMATION RELATED TO THE AIP DATA SET

text: When the AIP data set is provided, the following sections of the AIP may be left blank and a reference to the data set availability should be provided:

text: (a) ENR 2.1 FIR, UIR, TMA; (b) ENR 3.1 Lower ATS routes; (c) ENR 3.2 Upper ATS routes; (d) ENR 3.3 Area navigation (RNAV) routes; (e) ENR 3.4 Helicopter routes; (f) ENR 3.5 Other routes; (g) ENR 3.6 En route holding; (h) ENR 4.1 Radio navigation aids — en route; (i) ENR 4.4 Name-code designators for significant points; (j) ENR 4.5 Aeronautical ground lights — en route; (k) ENR 5.1 Prohibited, restricted and danger areas; (l) ENR 5.2 Military exercise and training areas and air defence identification zone (ADIZ); (m) ENR 5.3.1 Other activities of a dangerous nature; (n) ENR 5.5 Aerial sporting and recreational activities; (o) AD 2.17 Air traffic services airspace; (p) AD 2.19 Radio navigation and landing aids; (q) AD 3.16 Air traffic services airspace; and (r) AD 3.18 Radio navigation and landing aids.

text: GM4 AIS.TR.305(c) Aeronautical information publication (AIP)

text: INFORMATION RELATED TO THE OBSTACLE DATA SET

text: When the obstacle data set is provided, the following sections of the AIP may be left blank and a reference to the data set availability should be provided: (a) ENR 5.4 Air navigation obstacles; (b) AD 2.10 Aerodrome obstacles; and (c) AD 3.10 Heliport obstacles.

text: AMC1 AIS.TR.310(g) AIP amendments

text: ANNOTATION

text: (a) The annotation in the margin should be done by a thick black vertical line or, where the change incorporated covers one line only or a part of a line, a thick black horizontal arrow. (b) For aeronautical charts, the annotation should be made as a marginal note.

text: GM1 AIS.TR.310(h) AIP amendments

text: EFFECTIVE TIME

text: When an effective time other than 00.00 UTC is used, the effective time should also be indicated.

text: GM1 AIS.TR.315 AIP supplements

text: ISSUE OF NOTAM

text: When there is not sufficient time for the distribution of an AIP supplement, a NOTAM may be issued.

text: AMC1 AIS.TR.320(a) Aeronautical information circular (AIC)

text: ELECTRONIC FORM

text: When AICs are provided as part of the ‘electronic AIP’, they should comply with the EUROCONTROL ‘Specification for the Electronic Aeronautical Information Publication (eAIP)’ (edition 2.1, dated 6 October 2015).

text: GM1 AIS.TR.320(a) Aeronautical information circular (AIC)

text: PRINTED FORM

text: Differentiation and identification of AIC topics according to subjects using colour coding should be practised where the numbers of AICs in force are sufficient to make identification in this form necessary. For example: (a) white — administrative; (b) yellow — ATC; (c) pink — safety; (d) mauve — danger area map; and (e) green — maps/charts.

text: GM1 AIS.TR.320(c) Aeronautical information circular (AIC)

text: GENERAL

text: (a) AICs are not used to promulgate aeronautical data and aeronautical information that qualify for inclusion in AIP (including amendments and supplements) or in NOTAM. Nevertheless, AICs can be used to provide detailed information and/or interpretation about data contained in those aeronautical information products. (b) Consequently: (1) an AIC is not used to promulgate aeronautical data that is part of the data catalogue; and (2) the content of an AIC is not subject to the application of the DQRs. (c) AICs can be made available with the electronic AIP for distribution purpose, as long as it is understood that they remain separate aeronautical information products.

text: GM1 AIS.TR.320(d) Aeronautical information circular (AIC)

text: SNOW PLAN INFORMATION

text: The seasonal AIC on the snow plan may contain information such as that listed below: (a) a list of aerodromes/heliports where during the coming winter the following are expected to be performed: (1) snow clearance in accordance with the runway and taxiway systems; or (2) planned snow clearing, deviating from the runway system (length, width and number of runways, affected taxiways and aprons or portions thereof); (b) information concerning any centre designated to coordinate information on the current state of progress of clearance and on the current state of runways, taxiways and aprons; (c) a division of the aerodromes/heliports into SNOWTAM distribution lists in order to avoid excessive NOTAM distribution; (d) an indication, as necessary, of minor changes to the standing snow plan; (e) a descriptive list of clearance equipment; and (f) a listing of what will be considered as the minimum critical snow bank to be reported at each aerodrome/heliport at which reporting will commence.

text: AMC1 AIS.TR.330 NOTAM

text: USE OF OPADD

text: The origination and issuing of NOTAM should be in accordance with the EUROCONTROL ‘Guidelines — Operating Procedures for AIS Dynamic Data (OPADD)’ (edition 4.0, dated 17 April 2015).

text: GM1 AIS.TR.330(d) NOTAM

text: NOTAM CODE

text: The ICAO NOTAM Code together with significations/uniform abbreviated phraseology, and ICAO Abbreviations are those contained in ICAO Doc 8400 ‘Procedures for Air Navigation Services — ICAO Abbreviations and Codes (PANS-ABC)’.

text: GM1 AIS.TR.330(u) NOTAM

text: CHECKLIST

text: The checklist NOTAM may include the checklist of AIP Supplement (SUP) .

text: Chapter 2 — Digital data sets

text: GM1 AIS.TR.335(a) General — Digital data sets

text: STANDARD FOR GEOGRAPHIC INFORMATION

text: The ISO 19100 series of standards for geographic information may be used as a reference framework.

text: GM1 AIS.TR.335(b) General — Digital data sets

text: DATA PRODUCT SPECIFICATION

text: (a) ISO Standard 19131 specifies the requirements and outline of data product specifications for geographic information. This is intended to facilitate and support the use and exchange of digital data sets between data providers and data users. (b) The data product specification enables air navigation users to evaluate the products and determine whether they fulfil the requirements for their intended use (application). (c) This may include an overview, specification scope, data product identification, data content and structure, reference system, data quality, data capture, data maintenance, data portrayal, data product delivery, additional information, and metadata.

text: GM1 AIS.TR.345(b) AIP data set

text: PROPERTY

text: There may also be other reasons why a property is not provided, e.g. missing, unknown, withheld, etc.

text: GM1 AIS.TR.350(d) Terrain and obstacle data — General requirements

text: AREA 4

text: Where the terrain at a distance greater than 900 m (3 000 ft) from the runway threshold is mountainous or otherwise significant, the length of Area 4 should be extended to a distance not exceeding 2 000 m (6 500 ft) from the runway threshold.

text: GM1 AIS.TR.355(e) Terrain data sets

text: ATTRIBUTES

text: The following additional terrain feature attributes may be recorded in the terrain data set: (a) surface type; (b) penetration level; and (c) known variations.

text: GM1 AIS.TR.360(b) Obstacle data sets

text: ATTRIBUTES

text: The following additional obstacle feature attributes may be recorded in the obstacle data set: (a) height; (b) operations; and (c) effectiveness.

text: GM1 AIS.TR.365 Aerodrome mapping data sets

text: ADDITIONAL GUIDANCE

text: Further information concerning minimum requirements and reference material applicable to the content, origination, publication, and updating of aerodrome mapping information may be found in EUROCAE ED-99D ‘User Requirement for Aerodrome Mapping Information’, October 2015, and EUROCAE ED-119C ‘Interchange Standards for Terrain, Obstacle and Aerodrome Mapping Data’, October 2015.

text: GM1 AIS.TR.365(a) Aerodrome mapping data sets

text: AERODROME FEATURES

text: Aerodrome features consist of attributes and geometries, which are characterised as points, lines or polygons. Examples include runway thresholds, taxiway guidance lines and parking stand areas.

text: GM2 AIS.TR.365(a) Aerodrome mapping data sets

text: ADDITIONAL DATA

text: Aerodrome mapping data may be supported by electronic terrain and obstacle data for Area 3 in order to ensure consistency and quality of all geographical data related to the aerodrome.

text: GM3 AIS.TR.365(a) Aerodrome mapping data sets

text: COMMON ACQUISITION TECHNIQUES

text: Electronic terrain and obstacle data pertaining to Area 3 as well as aerodrome mapping data may be originated using common acquisition techniques and managed within a single geographic information system (GIS).

text: GM1 AIS.TR.365(b) Aerodrome mapping data sets

text: GENERAL

text: ISO Standard 19100 series on geographic information can be used as a reference framework.

text: GM1 AIS.TR.365(c) Aerodrome mapping data sets

text: GENERAL

text: ISO Standard 19131 contains standards for data product specification.

text: GM1 AIS.TR.365(d) Aerodrome mapping data sets

text: GENERAL

text: ISO Standard 19109 contains standards for application schemas, while ISO Standard 19110 describes the feature cataloguing methodology for geographic information.

text: GM1 AIS.TR.370 Instrument flight procedure data sets

text: GENERAL

text: Guidance on the instrument flight procedure data sets can be found in PANS-OPS, ICAO Doc 8168, Volume II – Part III, Section 2, Chapter 5.

text: GM1 AIS.TR.400(a) Distribution services

text: NOTAM

text: (a) The predetermined distribution system provides for incoming NOTAM (including SNOWTAM and ASHTAM) to be channelled through the aeronautical fixed service (AFS) directly to designated addressees predetermined by the receiving country concerned while concurrently being routed to the international NOTAM office for checking and control purposes. (b) The addressee indicators for those designated addressees are constituted as follows: (1) First and second letters The first two letters of the location indicator for the AFS communication centre associated with the relevant international NOTAM office of the receiving country. (2) Third and fourth letters The letters ‘ZZ’ indicating a requirement for special distribution. (3) Fifth letter The fifth letter differentiating between NOTAM (letter ‘N’), SNOWTAM (letter ‘S’), and ASHTAM (letter ‘V’). (4) Sixth and seventh letters The sixth and seventh letters, each taken from the series A to Z, denoting the national and/or international distribution list(s) to be used by the receiving AFS centre. The fifth, sixth and seventh letters replace the three-letter designator YNY which, in the normal distribution system, denotes an international NOTAM office. (5) Eighth letter The eighth position letter shall be the filler letter ‘X’ to complete the eight-letter addressee indicator. (c) Member States are to inform the States from which they receive NOTAM of the sixth and seventh letters to be used under different circumstances to ensure proper routing.

text: GM1 AIS.TR.405(a) Pre-flight information services

text: AUTOMATION

text: (a) Automated pre-flight information systems that provide a harmonised, common point of access by operations personnel, including flight crew members and other aeronautical personnel concerned, to aeronautical information and meteorological information should be established by an agreement between the AIS provider and the meteorological services provider.

text: (b) Where automated pre-flight information systems are used to provide the harmonised, common point of access by operations personnel, including flight crew members and other aeronautical personnel concerned, to aeronautical data, aeronautical information and meteorological information, the AIS provider remains responsible for the quality and timeliness of the aeronautical data and aeronautical information provided by means of such a system. (c) The meteorological services provider concerned remains responsible for the quality of the meteorological information provided by means of such a system in accordance with Annex V to

text: Regulation (EU) 2017/373

text: GM1 AIS.TR.405(e) Pre-flight information services

text: NOTAM

text: Although NOTAM with purpose ‘M’ are regarded not subject for a briefing but available on request, all NOTAM are to be provided for briefing by default, and content reduction should be at user’s discretion.

text: GM1 AIS.TR.505(a) AIRAC

text: OTHER CIRCUMSTANCES WHERE USE OF THE AIRAC SYSTEM MAY BE CONSIDERED

text: The AIRAC system may also be considered for the provision of information relating to the establishment and withdrawal of, and planned significant changes in, the circumstances listed below: (a) position, height and lighting of air navigation obstacles; (b) hours of service of aerodromes, facilities and services; (c) customs, immigration and health services; (d) temporary danger, prohibited and restricted areas and navigational hazards, military exercises and mass movements of aircraft; and (e) temporary areas or routes or portions thereof where the possibility of interception exists.

text: AMC1 AIS.TR.505(b) AIRAC

text: MAJOR CHANGES

text: Whenever major changes are planned and where advance notice is desirable and possible, information should be distributed and/or made available by the AIS provider, whenever practicable, so as to reach recipients at least 56 days in advance of the AIRAC effective date. This should apply to the establishment of, and premeditated major changes in the circumstances listed below, as well as to other major changes if deemed necessary: (a) new aerodromes for international instrument flight rules operations; (b) new runways for instrument flight rules (IFR) operations at international aerodromes; (c) design and structure of the ATS route network;

text: (d) design and structure of a set of terminal procedures (including change of procedure bearings due to magnetic variation change); and (e) circumstances listed in AIS.TR.505(a) if the entire State or any significant portion thereof is affected or if cross-border coordination is required.

text: GM1 AIS.TR.510(a) NOTAM

text: ADVANCE NOTICE

text: (a) Whenever possible, an at least 24 hours’ advance notice is desirable, to permit timely completion of the notification process and to facilitate airspace utilisation planning. (b) Notice of any subsequent cancellation of the activities or any reduction of the hours of activity or the dimensions of the airspace should be given as soon as possible.


text: AMC and GM to Part-AIS Issue 1, Amendment 2

identifier: AMC & GM to Part-AIS — Issue 1, Amendment 2

beslut: ED Decision 2022/015/R

text: The text of the amendment is arranged to show deleted, new or amended text as shown below: — deleted text is struck through; — new or amended text is highlighted in blue; — an ellipsis ‘[…]’ indicates that the rest of the text is unchanged.

text: Annex VI to Decision 2017/001/R is amended as follows:

text: AMC1 AIS.TR.305(c) Aeronautical information publication (AIP)

text: INFORMATION PUBLISHED UNDER ‘AD 1.2.2 RUNWAY SURFACE CONDITION ASSESSMENT AND REPORTING, AND SNOW PLAN’ The following information, originated by the competent authority, should be published under AD 1.2.2 for all aerodromes open to public use in the State:

text: 1. Organisation of the runway surface condition reporting and the winter service An indication of the: — organisation responsible for snow clearance and for assessing, improving and reporting runway surface conditions; — general policy concerning operational priorities established for the clearance of movement areas; — general policy concerning trend monitoring of surface friction characteristics, and what constitutes a complete survey.

text: 2. Surveillance of movement areas Indication of how surveillance of the movement areas is organised.

text: 3. Surface condition assessment methods used; operations on specially prepared winter runways Assessment methods and measurements taken. Reference should be made to the use of the runway condition assessment matrix, including the case of specially prepared winter runways, in the case the use of such runways has been approved.

text: 4. Actions taken to maintain the usability of movement areas A brief description of the methods used for clearing snow, slush, ice and standing water, e.g. plowing, sweeping or blowing, and details of any chemical methods employed for clearing movement areas. Information concerning when and how surface friction characteristics will be improved. General policy concerning coordination between aerodrome operators, air traffic services providers and the competent authorities to ensure compatibility between efficient snow clearance procedures and maximum utilisation of the aerodrome.

text: 5. System and means of reporting Reference should be made to the runway condition report.

text: 6. The cases of runway closure Indication of the general policy on closure of a runway.

text: 7. Distribution of information about runway surface conditions A short description of the system for distribution of information (NOTAM) for runways reaching the minimum friction value (slippery wet runways). Reference should be made to when NOTAMs for slippery wet runways are issued and updated. A short description of the system for distribution of information about runway surface conditions (SNOWTAM, automatic terminal information service (ATIS) updating). Reference should be made to when SNOWTAMs are issued and updated. Furthermore, a description should be provided of how the upgraded/downgraded information is included in the SNOWTAM. In addition, a statement should be included when the information is disseminated with ATIS only.

text: AMC2 AIS.TR.305(c) Aeronautical information publication (AIP)

text: INFORMATION PUBLISHED UNDER ‘AD 2.7 RUNWAY SURFACE CONDITION ASSESSMENT AND REPORTING AND SNOW PLAN’ The following information, originated by the respective aerodrome operator, should be published under AD 2.7. (a) A reference to the content of AD.1.2.2 should be made for the runway surface condition assessment and reporting. Additional, aerodrome-specific information on runway surface condition assessment and reporting, complementing the information contained in AD 1.2.2 should be included. (b) A detailed description of the equipment and operational priorities established for the clearance of aerodrome movement areas should be given, including: 1. Type(s) of clearing equipment Indication as to whether the aerodrome is serviceable during all seasons of the year and, if not, the periods (months of the year) during which it may be unserviceable or must be used with caution, indicating the likely cause of unserviceability and the precautions to be taken. Information relating to snow removal should include: (i) where no snow removal equipment is required, ‘Not applicable’ should be indicated; (ii) where snow conditions exist, the types of equipment used should be indicated.

text: 2. Clearance priorities Indication of the priorities with regard to clearing of runway(s), taxiway(s) and apron(s). 3. Use of material for movement area surface treatment Indication of the type of material used for movement area surface treatment, using the abbreviation/text or the material. Where no material is used, ‘Not applicable’ should be indicated. 4. Specially prepared winter runways Indication if specially prepared winter runways have been approved, including runway designators. Where the use of specially prepared winter runways has not been approved, ‘Not applicable’ should be indicated. 5. Remarks Any other relevant information not covered under this subsection.

text: AMC3 AIS.TR.305(c) Aeronautical information publication (AIP)

text: INFORMATION FOR LED LIGHTS PUBLISHED UNDER ‘AD 2.14 APPROACH AND RUWNAY LIGHTING’ If the aerodrome operator provides information that light emitting diode (LED) lights are used as part of the approach and runway lighting system of the aerodrome, such information should be published in the ‘Remarks’. In such case, the information published should make clear, for each part of the lighting system, whether: — LED lights are exclusively used for that part of the lighting system; or — LED lights are used in combination with incandescent lights.

text: AMC4 AIS.TR.305(c) Aeronautical information publication (AIP)

text: INFORMATION FOR VISUAL SEGMENT SURFACE (VSS) PENETRATION, PUBLISHED UNDER ‘AD 2.25’ If the VSS is penetrated, the information to be published under this section should clearly indicate the name of the affected procedure and the procedure minima affected. The published information should be grouped per runway end. In the case of no penetration, ‘Not applicable’ should be indicated.

text: GM3 AIS.TR.305(c) Aeronautical information publication (AIP)

text: INFORMATION RELATED TO THE AIP DATA SET When the AIP data set is provided, the following sections of the AIP may be left blank and a reference to the data set availability should be provided: (a) ENR 2.1 FIR, UIR, TMA and CTA; (b) ENR 3.1 Lower ATS Conventional navigation routes; (c) ENR 3.2 Upper ATS routes; (d c) ENR 3.32 Area navigation (RNAV) routes; (e) ENR 3.4 Helicopter routes; (f d) ENR 3.53 Other routes; (g e) ENR 3.64 En route holding; (h f) ENR 4.1 Radio navigation aids — en route; (i g) ENR 4.4 Name-code designators for significant points; (j h) ENR 4.5 Aeronautical ground lights — en route; (k i) ENR 5.1 Prohibited, restricted and danger areas; (l j) ENR 5.2 Military exercise and training areas and air defence identification zone (ADIZ); (mk) ENR 5.3.1 Other activities of a dangerous nature; (n l) ENR 5.5 Aerial sporting and recreational activities; (o m) AD 2.17 Air traffic services airspace; (p n) AD 2.19 Radio navigation and landing aids; (q o) AD 3.16 Air traffic services airspace; and (r p) AD 3.18 Radio navigation and landing aids.

text: GM5 AIS.TR.305(c) Aeronautical information publication (AIP)

text: INFORMATION PUBLISHED REGARDING USE OF MATERIAL FOR MOVEMENT AREA SURFACE TREATMENT UNDER ‘AD 2.7 RUNWAY SURFACE CONDITION ASSESSMENT AND REPORTING AND SNOW PLAN’ The following list contains the abbreviations/words that may be published in the relevant section of the AIP regarding the use of material for movement area surface treatment, according to the information originated by the aerodrome operator: (a) KAC, for potassium acetate fluids; (b) KFOR, for potassium formate fluids; (c) GAC, for glycerine acetate fluids;

text: (d) NAFO, for sodium formate solids; (e) NAAC, for sodium acetate solids; (f) EG, for ethylene glycol fluids; (g) PG, for propylene glycol fluids; (h) UREA; and (i) SAND.

text: GM6 AIS.TR.305(c) Aeronautical information publication (AIP)

text: INFORMATION FOR LED LIGHTS PUBLISHED UNDER ‘AD 2.14 APPROACH AND RUWNAY LIGHTING’ Examples of information published in the ‘Remarks’ indicating that light emitting diode (LED) lights are used as part of the approach and runway lighting system of the aerodrome, are shown below: — ‘RWY 05, LED and incandescent lights used as part of the RWY edge lights on both sides of RWY’; — ‘RWY 05, LED lights used for the centreline lighting system in the first 600 m; remaining length incandescent lights are used’; — ‘RWY 05, LED lights used in the full length of the approach lighting system’.

text: GM7 AIS.TR.305(c) Aeronautical information publication (AIP)

text: INFORMATION FOR VISUAL SEGMENT SURFACE (VSS) PENETRATION, PUBLISHED UNDER ‘AD 2.25’ In case of VSS penetration, the information published under AD 2.25 is limited to the name of the affected procedure and procedure minima affected; information about the obstacles themselves penetrating the VSS is not published under ‘AD 2.25’, as such information is meant to be published under ‘AD 2.10 Aerodrome obstacles’.


text: AMC & GM to Annex VI (Part-AIS) to Commission Implementing

text: Regulation (EU) 2017/373

text: Issue 1, Amendment 3

text: N o t e t o t h e r e a d e r

text: In amended, and in particular in existing (that is, unchanged) text, ‘Agency’ is used interchangeably with ‘EASA’. The interchangeable use of these two terms is more apparent in the consolidated versions. Therefore, please note that both terms refer to the ‘European Union Aviation Safety Agency (EASA)’.

text: Annex II to ED Decision 2024/006/R Page 1 of 3

text: RMZ TMZ RMZ/TMZ

text: FL60 FL60 FL60 3500FT 3500FT 3500FT

text: Annex II to ED Decision 2024/006/R Page 2 of 3

text: Annex II to ED Decision 2024/006/R Page 3 of 3

identifier: AMC & GM to Part-AIS — Issue 1, Amendment 3

beslut: ED Decision 2024/006/R

text: Acceptable Means of Compliance and Guidance Material to Annex VI (Part-AIS) to Commission Implementing

text: Regulation (EU) 2017/373

text: Issue 1, Amendment 3

text: Annex II to ED Decision 2024/006/R ‘AMC and GM to Part-AIS — Issue 1, Amendment 3’

text: This Annex shows deleted, new or amended text as follows:

text: — deleted text is struck through;

text: — new or amended text is highlighted in blue;

text: — an ellipsis ‘[…]’ indicates that the rest of the text is unchanged.

text: Annex VI (AMC and GM to Part-AIS) to ED Decision 2017/001/R of the Executive Director of the Agency of 8 March 2017 is amended as follows:

text: Annex VI

text: AMC1 AIS.OR.325 Aeronautical charts

text: PRODUCTION

text: Aeronautical charts should be produced in accordance with the specifications contained in ICAO Annex 4, Amendment No 61, except that any radio mandatory zones (RMZs) and transponder mandatory zones (TMZs) should be depicted on the ‘En-route chart – ICAO’, the ‘Visual approach chart – ICAO’ and the ‘Area chart – ICAO’, as follows: (a) the radio mandatory zones and the transponder mandatory zones should be displayed with an RMZ tag and a TMZ tag respectively, and, if both zones are defined for a specific area, with an RMZ/TMZ tag. The vertical limits of the zone should be indicated under the tag. A thick, dark, grey-dashed and dotted line should be used to show the boundaries of the zones in all cases.

text: GM1 AIS.OR.325 Aeronautical charts

text: PRODUCTION

text: The radio mandatory zones (RMZs) and transponder mandatory zones (TMZs) on the ‘En-route chart – ICAO’, the ‘Visual approach chart – ICAO’ and the ‘Area chart – ICAO’ may be depicted as in the following examples:

text: GM8 AIS.TR.305(c) Aeronautical information publication (AIP)

text: PUBLICATION OF RADIO MANDATORY ZONES (RMZs) AND TRANSPONDER MANDATORY ZONES (TMZs)

text: (a) The requirement to include a detailed description of RMZs and TMZs in the AIP, including in the relevant charts, should be met in a clear and unambiguous manner. (b) The following illustrates the appropriate AIP sections where RMZ and TMZ information should be included:

text: (1) Section GEN 1.5 should contain any relevant information regarding aircraft equipment required for operations in RMZs and TMZs. (2) Section ENR 2 should contain the information on RMZs and TMZs in the air traffic services airspace and other regulated airspace. (3) Section ENR 6 should contain an en-route chart illustrating the RMZs and TMZs. (4) Section AD 2 should contain the aerodrome-specific information, including the visual approach and area charts with the information on RMZs and TMZs.


text: For the date of entry into force of this issue, kindly refer to Decision 2017/001/R in the Official Publication of the Agency. Page 1 of 3

identifier: AMC & GM to Part-AIS

beslut: ED Decision 2017/001/R

nummer: part-ais

title: AMC & GM to Part-AIS

text: European Aviation Safety Agency

text: Acceptable Means of Compliance (AMC) and Guidance Material (GM) to Part-AIS Specific requirements for providers of aeronautical information services

text: Initial Issue 8 March 2017

text: Annex VI to ED Decision 2017/001/R

text: Table of contents

text: Annex VI to ED Decision 2017/001/R

text: AMC/GM TO PART-AIS SPECIFIC REQUIREMENTS FOR PROVIDERS OF AERONAUTICAL INFORMATION SERVICES

text: Reserved


identifier: AMC & GM to Part-ARA — Amendment 1

amnesord: Part-ARA - Authority Requirements for Aircrew

beslut: ED Decision 2013/006/R

title: AMC & GM to Part-ARA — Amendment 1

text: Annex to Decision 2013/006/R

text: Annex to Decision 2012/006/R of the Executive Director of the Agency of 19 April 2012, on ‘Acceptable means of compliance and guidance material to

text: Commission Regulation (EU) No 1178/2012 of 3 November 2011

text: laying down technical requirements and administrative procedures related to civil aviation aircrew pursuant to

text: Regulation (EC) No 216/2008

text: of the European Parliament and of the Council’, is amended as follows: The text of the amendment is arranged to show deleted text, new or amended text as shown below:

text: 1. deleted text is marked with strike through;

text: 2. new or amended text is highlighted in grey;

text: 3. an ellipsis (…) indicates that the remaining text is unchanged in front of or following the reflected amendment. Annex to ED Decision 2013/006/R 16/04/2013 A new AMC1 ARA.GEN.300(a);(b);(c) is added as follows: AMC1 ARA.GEN.300(a);(b);(c) Oversight EVALUATION OF APPROVED TRAINING ORGANISATIONS’ OPERATIONAL SAFETY RISK ASSESSMENT As part of the initial certification or the continuing oversight of an ATO, the competent authority should normally evaluate its safety risk assessment processes related to hazards identified by the ATO as having an interface with its operations. These safety risk assessments should be identifiable processes of the ATO’s management system. As part of its continuing oversight, the competent authority should also remain satisfied as to the effectiveness of these safety risk assessments. (a) General methodology for operational hazards The competent authority should establish a methodology for evaluating the safety risk assessment processes of the ATO’s management system. When related to operational hazards, the competent authority’s evaluation under its normal oversight process should be considered satisfactory if the ATO demonstrates its competence and capability to: (1) understand the hazards identified and their consequences on its operations; (2) be clear on where these hazards may exceed acceptable safety risk limits; (3) identify and implement mitigations including suspension of operations where mitigation cannot reduce the risk to within safety risk limits; (4) develop and execute effectively, robust procedures for the preparation and the safe operation of the flights subject to the hazards identified; (5) assess the competence and currency of its staff in relation to the duties for the intended operations and implement any necessary training; and (6) ensure sufficient numbers of qualified and competent staff for such duties. The competent authority should take into account: (1) the ATO’s recorded mitigations for each unacceptable risk identified are in place; (2) the operational procedures specified by the ATO with the most significance to safety appear to be robust; and (3) that the staff on which the ATO depends in respect of those duties necessary for the intended operations are trained and assessed as competent in the relevant procedures. EVALUATION OF APPROVED TRAINING ORGANISATIONS’ VOLCANIC ASH SAFETY RISK ASSESSMENT In addition to the general methodology for operational hazards, the competent authority’s evaluation under its normal oversight process should also assess the ATO’s competence and capability to: (1) choose the correct information sources to use to interpret the information related to volcanic ash contamination forecast and to resolve correctly any conflicts among such sources; and (2) take account of all information from its type certificate holders (TCHs) concerning volcanic ash-related airworthiness aspects of the aircraft it operates, and the related pre-flight, in-flight and post flight precautions to be observed; Annex to ED Decision 2013/006/R 16/04/2013 A new GM1 ARA.GEN.300(a);(b)(c) is added as follows: GM1 ARA.GEN.300(a);(b);(c) Oversight VOLCANIC ASH SAFETY RISK ASSESSMENT - ADDITIONAL GUIDANCE Further guidance on the assessment of an ATO volcanic ash safety risk assessment is given in ICAO Doc. 9974 (Flight safety and volcanic ash – Risk management of flight operations with known or forecast volcanic ash contamination).


text: ED Decision 2012/006/R of 19 April 2012 on acceptable means of compliance and guidance material to

text: Commission Regulation (EU) No 1178/2011 of 3 November 2011

text: 1 laying down technical requirements and administrative procedures related to civil aviation aircrew pursuant to

text: regulation (EC) No 216/2008

text: of the European Parliament and of the Council. Decision as last amended by ED Decision 2013/006/R of 16 April 2013.

text: MED.A.020 Decrease in medical fitness

text: (a) Licence holders shall not exercise the privileges of their licence and related ratings or certificates at any time when they: (1) are aware of any decrease in their medical fitness that might render them unable to safely exercise those privileges; (2) take or use any prescribed or non-prescribed medication that is likely to interfere with the safe exercise of the privileges of the applicable licence; or (3) receive any medical, surgical or other treatment that is likely to interfere with flight safety. (b) In addition, licence holders shall, without undue delay, seek aeromedical advice when they: (1) have undergone a surgical operation or invasive procedure; (2) have commenced the regular use of any medication; (3) have suffered any significant personal injury involving incapacity to function as a member of the flight crew; (4) have been suffering from any significant illness involving incapacity to function as a member of the flight crew; (5) are pregnant; (6) have been admitted to hospital or medical clinic; or (7) first require correcting lenses.

identifier: AMC & GM to Part-ARA — Amendment 2

beslut: ED Decision 2014/020/R

title: AMC & GM to Part-ARA — Amendment 2

text: Annex to ED Decision 2014/020/R

text: Annex to ED Decision 2014/020/R

text: Annex to Decision 2012/006/R is hereby amended as follows: The text of the amendment is arranged to show deleted text, new or amended text as shown below: (a) deleted text is marked with strike through; (b) new or amended text is highlighted in grey; (c) an ellipsis (…) indicates that the remaining text is unchanged in front of or following the reflected amendment.

text: 1. AMC1 ARA.FCL.300(b) is amended as follows:

text: AMC1 ARA.FCL.300(b) Examination procedures

text: THEORETICAL KNOWLEDGE EXAMINATIONS FOR PROFESSIONAL LICENCES AND INSTRUMENT RATINGS With regard to the IR(A), this table applies to theoretical knowledge examinations for applicants who have completed a modular training course for the IR(A) according to Appendix 6 section A.

text: 2. A new AMC2 ARA.FCL.300(b) is added:

text: AMC2 ARA.FCL.300(b) Examination procedures

text: THEORETICAL KNOWLEGDE EXAMINATIONS FOR THE EN-ROUTE INSTRUMENT RATING (EIR) AND THE INSTRUMENT RATING (IR) OBTAINED THROUGH THE COMPETENCY-BASED MODULAR TRAINING COURSE The following tables contain the number of questions, the distribution of questions related to the different syllabus topics and the time allowed for the theoretical knowledge examination. Subject: 010 — AIR LAW Theoretical knowledge examination Exam length and total questions EIR FCL.825 & IR(A) Appendix 6 Aa Time allowed 0:30 Distribution of questions with regard to the topics of the syllabus 010 04 01 010 05 05 010 06 06 010 07 03 010 08 01 010 09 02 Total questions 18

text: Subject: 022 — AIRCRAFT GENERAL KNOWLEDGE — INSTRUMENTATION Theoretical knowledge examination Exam length and total questions EIR FCL.825 & IR(A) Appendix 6 Aa Time allowed 0:20 Distribution of questions with regard to the topics of the syllabus 022 02 05

text: 022 04 04 022 13 03 Total questions 12

text: Subject: 033 — FLIGHT PERFORMANCE AND PLANNING — FLIGHT PLANNING AND MONITORING Theoretical knowledge examination Exam length and total questions EIR FCL.825 & IR(A) Appendix 6 Aa Time allowed 0:40 Distribution of questions with regard to the topics of the syllabus 033 02 10 033 03 4 033 04 7 033 05 5 Total questions 26

text: Subject: 040 — HUMAN PERFORMANCE Theoretical knowledge examination Exam length and total questions EIR FCL.825 & IR(A) Appendix 6 Aa Time allowed 0:20 Distribution of questions with regard to the topics of the syllabus 040 01 01 040 02 07 040 03 04 Total questions 12

text: Subject: 050 — METEOROLOGY Theoretical knowledge examination Exam length and total questions EIR FCL.825 & IR(A) Appendix 6 Aa Time allowed 0:50 Distribution of questions with regard to the topics of the syllabus 050 01 05 050 02 03 050 03 01 050 04 05 050 05 03 050 06 05 050 08 01 050 09 07 050 10 05

text: Total questions 35

text: Subject: 062 — RADIO NAVIGATION Theoretical knowledge examination Exam length and total questions EIR FCL.825 & IR(A) Appendix 6 Aa Time allowed 0:40 Distribution of questions with regard to the topics of the syllabus 062 02 15 062 03 03 062 05 05 062 06 01 Total questions 24

text: Subject: 092 — IFR COMMUNICATION Theoretical knowledge examination Exam length and total questions EIR FCL.825 & IR(A) Appendix 6 Aa Time allowed 0:30 Distribution of questions with regard to the topics of the syllabus 092 01 05 092 02 10 092 03 02 092 04 02 092 05 02 092 06 02 Total questions 23

text: 3. A new AMC1 ARA.MED.130 is added:

text: AMC1 ARA.MED.130 Medical certificate format

text: STANDARD EASA MEDICAL CERTIFICATE FORMAT

text: The format of the medical certificate should be as shown below.

text: Competent authority name and logo Requirements (English and any language(s) determined by the competent authority)

text: EUROPEAN UNION "European Union” to be deleted (English only) for non-EU Member States

text: Class 1/2/LAPL

text: Size of each page shall be one

text: MEDICAL CERTIFICATE

text: eighth A4

text: pertaining to a Part-FCL licence (English and any language(s) determined by the competent authority) Issued in accordance with Part-MED This medical certificate complies with ICAO standards, except for the LAPL medical certificate (English and any language(s) determined by the competent authority) .

text: I National language(s)/ Authority that issued or is to issue

text: the pilot licence

text: III National language(s):/Certificate number IV National language(s):/ Last and first name of holder: XIV National language(s):/Date of birth: (dd/mm/yyyy) VI National language(s)/Nationality: VII National language(s)/ Signature of holder:

text: XIII National language(s)/Limitations: Code. Description :

text: X National language(s)/* Date of issue: (dd/mm/yyyy) Signature of issuing AME/medical assessor /(GMP): XI National language(s)/Stamp:

text: IX Nat. Class 1 single pilot commercial lang(s)/ operations carrying passengers Expiry (dd/mm/yyyy)

text: date of this

text: certificate Class 1 (dd/mm/yyyy)

text: Class 2 (dd/mm/yyyy)

text: LAPL (dd/mm/yyyy)

text: Nat. lang(s)./Examination date: (dd/mm/yyyy)

text: * Date of issue is the date the certificate is issued and signed


identifier: AMC & GM to Part-ARA — Amendment 3

beslut: ED Decision 2016/008/R

title: AMC & GM to Part-ARA — Amendment 3

text: Annex I to ED Decision 2016/008/R

text: Acceptable Means of Compliance and Guidance Material to Part-FCL (PBN) and Part-ARA (PBN, ARA.MED)

text: A. Amendments to AMC/GM to Part-FCL

text: 1. A new GM2 FCL.010 is inserted as follows: ‘GM2 FCL.010 Definitions — lateral and vertical navigation Lateral and vertical navigation guidance refers to the guidance provided either by: (a) a ground-based radio navigation aid; or (b) computer-generated navigation data from ground-based, space-based, self-contained navigation aids or a combination of these.’

text: 2. Point AMC7 FCL.615(b) is amended as follows:

text: AMC7 FCL.615(b) IR — Theoretical knowledge and flight instruction

text: Delete ‘062 05 01’, ‘062 05 02’, ‘062 05 03’, and insert ‘062 07 00 00’ below when applicable:

text: Aeroplane Helicopter IR ATPL CPL ATPL/IR ATPL CPL ‘062 07 00 00 PBN 062 07 01 00 PBN concept (as described in ICAO Doc 9613) 062 07 01 01 PBN principles LO List the factors used to define RNAV or RNP system x x x performance requirements (accuracy, integrity, continuity and functionality). LO Explain the concept of continuity. x x x

text: LO Explain the concept of integrity. x x x LO State that, unlike conventional navigation, performance- x x x based navigation is not sensor-specific. LO Explain the difference between raw data and computed data. 062 07 01 02 PBN components LO List the components of PBN as NAVAID infrastructure, x x x navigation specification and navigation application. LO Identify the components from an example. x x x 062 07 01 03 PBN scope LO State that in oceanic/remote, en route and terminal x x x phases of flight PBN is limited to operations with linear lateral performance requirements and time constraints.

text: Annex I to ED Decision 2016/008/R

text: LO State that in the approach phases of flight PBN x x x accommodates both linear and angular laterally guided operations. 062 07 02 00 Navigation specifications 062 07 02 01 RNAV and RNP LO State the difference between RNAV and RNP in terms of x x x the requirement for on-board performance monitoring and alerting. 062 07 02 02 Navigation functional requirements LO List the basic functional requirements of RNAV and RNP x x x specifications (continuous indication of lateral deviation, distance/bearing to active waypoint, g/s or time to active waypoint, navigation data storage and failure indication). 062 07 02 03 Designation of RNP and RNAV specifications

text: LO Interpret “X” in RNAV X or RNP X as the lateral x x x navigation accuracy (total system error) in nautical miles, which is expected to be achieved at least 95 per cent of the flight time by the population of aircraft operating within the airspace, route or procedure. LO State that aircraft approved to the more stringent x x x accuracy requirements may not necessarily meet some of the functional requirements of the navigation specification having a less stringent accuracy requirement. LO State that RNAV10 and RNP4 are used in the x x x oceanic/remote phase of flight.

text: LO State that RNAV5 is used in the en route and arrival x x x phase of flight.

text: LO State that RNAV2 and RNP2 are also used as navigation x x x specifications.

text: LO State that RNP2 is used in the en route and x x x oceanic/remote phases of flight.

text: LO State that RNAV1 and RNP1 are used in the arrival and x x x departure phases of flight.

text: LO State that RNP APCH is used in the approach phase of x x x flight.

text: LO State that RNP AR APCH is used in the approach phase of x x x flight.

text: LO State that RNP 0.3 navigation specification is used in all x x x phases of flight, except for oceanic/remote and final approach, primarily for helicopters. 062 07 03 00 Use of PBN 062 07 03 01 Airspace planning

text: Annex I to ED Decision 2016/008/R

text: LO State that navigation performance is one factor used to x x x determine minimum route spacing. 062 07 03 02 Approval LO State that the airworthiness approval process assures x x x that each item of the area navigation equipment installed is of a type and design appropriate to its intended function and that the installation functions properly under foreseeable operating conditions. LO State that some PBN specifications require operational x x x approval. 062 07 03 03 Specific RNAV and RNP system functions

text: LO Recognise the definition of an RF leg. x x x

text: LO Recognise the definition of a fixed radius transition. x x x

text: LO Recognise the definition of a fly-by-turn and a fly-over. x x x

text: LO Recognise the definition of a holding pattern. x x x

text: LO Recognise the definition of an “ARINC 424 path x x x terminator”. LO Recognise the definition of the following path x x x terminators: IF, TF, CF, DF, FA, CA. LO Recognise the definition of an offset flight path. x x x 062 07 03 04 Data processes

text: LO State that the safety of the application is contingent x x x upon the accuracy, resolution and integrity of the data. LO State that the accuracy of the data depends upon the x x x processes applied during data origination. 062 07 04 00 PBN operations 062 07 04 01 PBN principles LO Recognise the definition of path definition error. x x x LO Recognise the definition of flight technical error. x x x LO Recognise the definition of navigation system error. x x x LO Recognise the definition of total system error. x x x 062 07 04 02 On-board performance monitoring and alerting LO State that on-board performance monitoring and x x x alerting of flight technical error is managed by on-board systems or crew procedures. LO State that on-board performance monitoring and x x x alerting of navigation system error is a requirement of on-board equipment for RNP. LO State that on-board performance monitoring and x x x alerting of path definition error are managed by gross reasonableness checks of navigation data. 062 07 04 03 Abnormal situations

text: Annex I to ED Decision 2016/008/R

text: LO State that abnormal and contingency procedures are to x x x be used in case of loss of the PBN capability. 062 07 04 04 Database management

text: LO State that, unless otherwise specified in operations x x x documentation or AMC, the navigational database must be valid for the current AIRAC cycle. 062 07 05 00 Requirements of specific RNAV and RNP specifications

text: 062 07 05 01 RNAV10

text: LO State that RNAV10 requires that aircraft operating in x x x oceanic and remote areas be equipped with at least two independent and serviceable LRNSs comprising an INS, an IRS FMS or a GNSS. LO State that aircraft incorporating dual inertial navigation x x x systems (INS) or inertial reference units (IRU) have a standard time limitation. LO State that operators may extend their RNAV10 x x x navigation capability time by updating. 062 07 05 02 RNAV5 LO State that manual data entry is acceptable for RNAV5. x x x 062 07 05 03 RNAV/RNP1/2

text: LO State that pilots must not fly an RNAV/RNP1/2 SID or x x x STAR unless it is retrievable by route name from the onboard navigation database and conforms to the charted route. LO State that the route may subsequently be modified x x x through the insertion (from the database) or deletion of specific waypoints in response to ATC clearances. LO State that the manual entry, or creation of new x x x waypoints by manual entry, of latitude and longitude or place/bearing/ distance values is not permitted. 062 07 05 04 RNP4

text: LO State that at least two LRNSs, capable of navigating to x x x RNP4 and listed in the flight manual, must be operational at the entry point of the RNP airspace. 062 07 05 05 RNP APCH

text: LO State that pilots must not fly an RNP APCH unless it is x x x retrievable by procedure name from the on-board navigation database and conforms to the charted procedure. LO State that an RNP APCH to LNAV minima is a non- x x x precision instrument approach procedure designed for 2D approach operations. LO State that an RNP APCH to LNAV/VNAV minima has x x x lateral guidance based on GNSS and vertical guidance based on either SBAS or BaroVNAV.

text: Annex I to ED Decision 2016/008/R

text: LO State that an RNP APCH to LNAV/VNAV minima may only x x x be conducted with vertical guidance certified for the purpose. LO Explain why an RNP APCH to LNAV/VNAV minima based x x x on BaroVNAV may only be conducted when the aerodrome temperature is within a promulgated range. LO State that the correct altimeter setting is critical for the x x x safe conduct of an RNP APCH using BaroVNAV. LO State that an RNP APCH to LNAV/VNAV minima is a 3D x x x operation. LO State that an RNP APCH to LPV minima is a 3D x x x operation. LO State that RNP APCH to LPV minima requires an FAS x x x data-block. 062 07 05 06 RNP AR APCH

text: LO State that RNP AR APCH requires authorisation. x x x 062 07 05 07 A-RNP

text: LO State that Advanced RNP incorporates the navigation x x x specifications RNAV5, RNAV2, RNAV1, RNP2, RNP1 and RNP APCH. LO State that Advanced RNP may be associated with other x x x functional elements. 062 07 05 08 PBN Point in Space (PinS) departure LO State that a PinS departure is a departure procedure x x designed for helicopters only. LO State that a PinS departure procedure includes either a x x “proceed VFR” or a “proceed visually” instruction from landing location to IDF. LO Recognise the differences between “proceed VFR” and x x “proceed visually” instruction. 062 07 05 09 PBN Point in Space (PinS) approach LO State that a PinS approach is an instrument RNP APCH x x procedure designed for helicopters only, and that may be published with LNAV minima or LPV minima. LO State that a PinS approach procedure includes either a x x “proceed VFR” or a “proceed visually” instruction from the MAPt to a landing location. LO Recognise the differences between “proceed VFR” and x x “proceed visually” instruction.

text: 3. Point AMC2 ARA.FCL.300(b) is amended as follows:

text: AMC2 ARA.FCL.300(b) Examination procedures

text: Replace the table for ‘Subject 062 — RADIO NAVIGATION’ with the table below when applicable:

text: Annex I to ED Decision 2016/008/R

text: ‘Subject: 062 — RADIO NAVIGATION Theoretical knowledge examination Exam length, total questions and distribution of questions ATPL(A) CPL(A) ATPL(H)/IR ATPL(H) CPL(H) IR(A) & (H) Time allowed 1:30 0:30 1:30 1:00 0:30 1:00 (hours) Distribution of questions with regard to the topics of the syllabus 062 01 07 04 07 05 04 02 062 02 21 12 21 15 12 23 062 03 12 02 12 08 02 05 062 04 XX XX XX XX XX XX 062 05 10 XX 10 XX XX 05 062 06 11 04 11 06 04 04 062 07 05 XX 05 XX XX 05 Total 66 22 66 34 22 44’ questions

text: Annex I to ED Decision 2016/008/R

text: B. Amendments to Part-ARA

text: 1. Point AMC5 ARA.FSTD.100(a)(1) is amended as follows:

text: AMC5 ARA.FSTD.100(a)(1) Initial evaluation procedure

text: On the form FSTD EVALUATION REPORT FOR INITIAL AND RECURRENT EVALUATION delete the line ‘GPS’ and insert instead between the lines ‘ETOPS capability’ and ‘Other’ the following lines: ‘RNP APCH LNAV RNP APCH LNAV/VNAV RNP APCH LPV RNP AR APCH’

text: 2. A new AMC1 ARA.MED.330 is inserted as follows:

text: ‘AMC1 ARA.MED.330 Special medical circumstances GENERAL The protocol should: (a) assess the incapacitation risk; (b) assess the risk of subtle impairment of performance; (c) undertake a risk–benefit analysis; (d) include a review of the regulations in use in other major aviation States and ICAO; (e) determine which class of medical certificate is included in the scope; (f) estimate the number of pilots likely to be included; (g) list all anticipated risks to the protocol and provide a risk management strategy including appropriate limitations for every anticipated risk; where the risk of subtle impairment of performance is identified, the protocol should include requirements for minimum simulator testing or minimum line-flying under supervision or both; (h) nominate medical research experts, if necessary, to provide advice on research methods.’

text: 3. A new AMC1 ARA.MED.330(b)(c) is inserted as follows:

text: ‘AMC1 ARA.MED.330(b)(c) Special medical circumstances GENERAL Initial medical certificates issued on the basis of a protocol should only be issued by the competent authority. Thereafter, the competent authority should decide whether the AeMC or AME may issue the medical certificate.’

text: Annex I to ED Decision 2016/008/R

text: 4. A new GM1 ARA.MED.330 is inserted as follows:

text: ‘GM1 ARA.MED.330 Special medical circumstances GENERAL (a) When the terms ‘medical assessment protocol’, ‘research protocol’ and ‘protocol’ (as mentioned in ARA.MED.330 and its associated AMC) are used, they all refer to a ‘medical assessment protocol’. (b) The protocol is to enable experience to be gained in special medical circumstances in a controlled manner. This is to facilitate a better understanding of the treatment or condition, so that an evidence-based decision concerning its implementation may be considered. (c) The protocol and its implementation should comply with the principles described in the following publication of the World Medical Association (WMA): “WMA Declaration of Helsinki - Ethical Principles for Medical Research Involving Human Subjects”, as last amended.’