[1]     The published date represents the date when the consolidated version of the document was generated.

[2]     Euro-Lex, Important Legal Notice: http://eur-lex.europa.eu/content/legal-notice/legal-notice.html.

[3]     This is the date of application (i.e. the date from which an act or a provision in an act produces its full legal effects) as defined in the relevant cover regulation article. Some provisions of the regulations though may be applicable at a later date (deferred applicability). Besides, there may be some opt-outs (derogations from certain provisions) notified by the Member States.

[4]        Regulation (EU) 2017/373 shall apply from 2 January 2020. However:

- in respect of the Agency, Article 4(1), (2), (5), (6) and (8) and Article 5 shall apply from the date of entry into force of this Regulation;
- in respect of data services providers, Article 6 shall apply in any case from 1 January 2019 and, where such a provider applies for and is granted a certificate in accordance with Article 6, from the date of entry into force of this Regulation.

[5]     OJ L 79, 19.3.2008, p. 1.

[6]     OJ L 96, 31.3.2004, p. 10.

[7]     OJ L 96, 31.3.2004, p. 20.

[8]     Commission Implementing Regulation (EU) No 1034/2011 of 17 October 2011 on safety oversight in air traffic management and air navigation services and amending Regulation (EU) No 691/2010 (OJ L 271, 18.10.2011, p. 15).

[9]     Commission Implementing Regulation (EU) No 1035/2011 of 17 October 2011 laying down common requirements for the provision of air navigation services and amending Regulations (EC) No 482/2008 and (EU) No 691/2010 (OJ L 271, 18.10.2011, p. 23).

[10]    Regulation (EC) No 549/2004 of the European Parliament and of the Council of 10 March 2004 laying down the framework for the creation of the single European Sky (OJ L 96, 31.3.2004, p. 1).

[11]    Commission Regulation (EU) No 965/2012 of 5 October 2012 laying down technical requirements and administrative procedures related to air operations pursuant to Regulation (EC) No 216/2008 of the European Parliament and of the Council (OJ L 296, 25.10.2012, p. 1).

[12]    Commission Regulation (EU) No 1178/2011 of 3 November 2011 laying down technical requirements and administrative procedures related to civil aviation aircrew pursuant to Regulation (EC) No 216/2008 of the European Parliament and of the Council (OJ L 311, 25.11.2011, p. 1).

[13]    Commission Regulation (EU) No 139/2014 of 12 February 2014 laying down requirements and administrative procedures related to aerodromes pursuant to Regulation (EC) No 216/2008 of the European Parliament and of the Council (OJ L 44, 14.2.2014, p. 1).

[14]    Commission Regulation (EU) 2015/340 of 20 February 2015 laying down technical requirements and administrative procedures relating to air traffic controllers' licences and certificates pursuant to Regulation (EC) No 216/2008 of the European Parliament and of the Council, amending Commission Implementing Regulation (EU) No 923/2012 and repealing Commission Regulation (EU) No 805/2011 (OJ L 63, 6.3.2015, p. 1).

[15]    Commission Implementing Regulation (EU) No 923/2012 of 26 September 2012 laying down the common rules of the air and operational provisions regarding services and procedures in air navigation and amending Implementing Regulation (EU) No 1035/2011 and Regulations (EC) No 1265/2007, (EC) No 1794/2006, (EC) No 730/2006, (EC) No 1033/2006 and (EU) No 255/2010 (OJ L 281, 13.10.2012, p. 1).

[16]    Commission Regulation (EC) No 482/2008 of 30 May 2008 establishing a software safety assurance system to be implemented by air navigation service providers and amending Annex II to Regulation (EC) No 2096/2005 (OJ L 141, 31.5.2008, p. 5).

[17]    Commission Regulation (EU) No 677/2011 of 7 July 2011 laying down detailed rules for the implementation of air traffic management (ATM) network functions and amending Regulation (EU) No 691/2010 (OJ L 185, 15.7.2011, p. 1).

[18]    Commission Implementing Regulation (EU) 2016/1377 of 4 August 2016 laying down common requirements for service providers and the oversight in air traffic management/air navigation services and other air traffic management network functions, repealing Regulation (EC) No 482/2008, Implementing Regulations (EU) No 1034/2011 and (EU) No 1035/2011 and amending Regulation (EU) No 677/2011 (OJ L 226, 19.8.2016, p. 1).

[19]    Regulation (EC) No 216/2008 of the European Parliament and the Council of 20 February 2008 on common rules in the field of civil aviation and establishing a European Aviation Safety Agency, and repealing Council Directive 91/670/EEC, Regulation (EC) No 1592/2002 and Directive 2004/36/EC (OJ L 79, 19.3.2008, p. 1).

[20]    Regulation (EC) No 549/2004 of the European Parliament and of the Council of 10 March 2004 laying down the framework for the creation of the single European sky (the framework Regulation) - Statement by the Member States on military issues related to the single European sky (OJ L 96, 31.3.2004, p. 1).

[21]    Regulation (EC) No 550/2004 of the European Parliament and of the Council of 10 March 2004 on the provision of air navigation services in the single European sky (the service provision Regulation) (OJ L 96, 31.3.2004, p. 10).

[22]    Regulation (EC) No 551/2004 of the European Parliament and of the Council of 10 March 2004 on the organisation and use of the airspace in the single European sky (the airspace Regulation) - Commission statement (OJ L 96, 31.3.2004, p. 20).

[23]    Regulation (EC) No 552/2004 of the European Parliament and of the Council of 10 March 2004 on the interoperability of the European Air Traffic Management network (the interoperability Regulation) (OJ L 96, 31.3.2004, p. 26).

[24]    As prescribed by the competent authority.

[25]    ATS covers alerting service.

[26]    Where necessary.

[27]    If the competent authority considers it necessary to establish additional requirements.

[28]    As prescribed by the competent authority.

[29]    Where necessary.

[30]    As prescribed by the competent authority.

[31]    Where necessary.

3       Design, documentation and validation of flight procedures includes maintenance and periodic review activities.

[32]    Commission Regulation (EU) No 677/2011 of 7 July 2011 laying down detailed rules for the implementation of air traffic management (ATM) network functions and amending Commission Regulation (EU) No 691/2010 (OJ L 185, 15.7.2011, p. 1).

[33]    Commission Implementing Regulation (EU) No 390/2013 of 3 May 2013 laying down a performance scheme for air navigation services and network functions (OJ L 128, 9.5.2013, p. 1).

[34]    For example, http://www.nlr.nl/downloads/safety-methods-database.pdf or http://www.scsc.org.uk/

[35]    Directive 95/46/EC of the European Parliament and of the Council of 24 October 1995 on the protection of individuals with regard to the processing of personal data and on the free movement of such data (OJ L 281, 23.11.1995, p. 31).

[36] When a meteorological element is temporarily missing, or its value is considered temporarily as incorrect, it is replaced by a solidus (‘/’)

[37] When a meteorological element is temporarily missing, or its value is considered temporarily as incorrect, it is replaced by a solidus (‘/’)

[38] When a meteorological element is temporarily missing, or its value is considered temporarily as incorrect, it is replaced by a solidus (‘/’)

[39] To be included if the visibility or the runway visual range is < 1 500 m for up to a maximum of four runways.

[40] When a meteorological element is temporarily missing, or its value is considered temporarily as incorrect, it is replaced by a solidus (‘/’)

[41] For automated reports only.

[42] ‘Heavy’ is used to indicate ‘tornado’ or ‘waterspout’; ‘moderate’ (no qualifier) to indicate ‘funnel cloud not reaching the ground’.

[43] For automated reports only.

[44] For automated reports only.

[45] For automated reports only.

[46] When a meteorological element is temporarily missing, or its value is considered temporarily as incorrect, it is replaced by a solidus (‘/’)

[47] When a meteorological element is temporarily missing, or its value is considered temporarily as incorrect, it is replaced by a solidus (‘/’)

[48] When a meteorological element is temporarily missing, or its value is considered temporarily as incorrect, it is replaced by a solidus (‘/’)

[49] When a meteorological element is temporarily missing, or its value is considered temporarily as incorrect, it is replaced by a solidus (‘/’)

[50] When a meteorological element is temporarily missing, or its value is considered temporarily as incorrect, it is replaced by a solidus (‘/’)

[51] When a meteorological element is temporarily missing, or its value is considered temporarily as incorrect, it is replaced by a solidus (‘/’)

[52] When a meteorological element is temporarily missing, or its value is considered temporarily as incorrect, it is replaced by a solidus (‘/’)

[53] When a meteorological element is temporarily missing, or its value is considered temporarily as incorrect, it is replaced by a solidus (‘/’)

[54] For automated reports only.

[55] When a meteorological element is temporarily missing, or its value is considered temporarily as incorrect, it is replaced by a solidus (‘/’)

[56] In the case of automated reports, solidi (‘///’) may replace the relevant cloud type, as appropriate, dependent on the capability of the automatic observing system. Furthermore, solidi may replace cloud amount and/or cloud height of reported CB or TCU layer.

[57] When a meteorological element is temporarily missing, or its value is considered temporarily as incorrect, it is replaced by a solidus (‘/’)

[58] When a meteorological element is temporarily missing, or its value is considered temporarily as incorrect, it is replaced by a solidus (‘/’)

[59] When a meteorological element is temporarily missing, or its value is considered temporarily as incorrect, it is replaced by a solidus (‘/’)

[60] When a meteorological element is temporarily missing, or its value is considered temporarily as incorrect, it is replaced by a solidus (‘/’)

[61] For automated reports only.

[62] For automated reports only.

[63] For automated reports only.

[64] For automated reports only.

[65] When a meteorological element is temporarily missing, or its value is considered temporarily as incorrect, it is replaced by a solidus (‘/’)

[66] When a meteorological element is temporarily missing, or its value is considered temporarily as incorrect, it is replaced by a solidus (‘/’)

[67] When a meteorological element is temporarily missing, or its value is considered temporarily as incorrect, it is replaced by a solidus (‘/’)

[68] When a meteorological element is temporarily missing, or its value is considered temporarily as incorrect, it is replaced by a solidus (‘/’)

[69] When a meteorological element is temporarily missing, or its value is considered temporarily as incorrect, it is replaced by a solidus (‘/’)

[70] Replacing visibility, runway visual range, present weather, and cloud elements, when applicable.

[71] To be included whenever applicable. No qualifier for moderate intensity.

[72] Up to four cloud layers.

[73] Consisting of up to a maximum of four temperatures (two maximum temperatures and two minimum temperatures).

[74] Replacing visibility, runway visual range, forecast weather and cloud elements, when applicable.

[75] Used only when SIGMET/AIRMET is issued to indicate that a test or an exercise is taking place. When the word ‘TEST’ or the abbreviation ‘EXER’ is included, the message may contain information that should not be used operationally or will otherwise end immediately after the word ‘TEST’.

[76] Used for unnamed tropical cyclones.

[77] In the case of volcanic ash cloud covering more than one area within the FIR, these elements can be repeated, as necessary. Each location and forecast position are to be preceded by an observed or forecast time.

[78] In the case of cumulonimbus clouds associated with a tropical cyclone covering more than one area within the FIR, these elements can be repeated as necessary. Each location and forecast position must be preceded by an observed or forecast time.

[79] In the case of volcanic ash cloud covering more than one area within the FIR, these elements can be repeated, as necessary. Each location and forecast position are to be preceded by an observed or forecast time.

[80] In the case of cumulonimbus clouds associated with a tropical cyclone covering more than one area within the FIR, these elements can be repeated as necessary. Each location and forecast position must be preceded by an observed or forecast time.

[81] For SIGMET for radioactive cloud, only within (WI) is to be used for theelements ‘location’ and ‘forecast position’.

[82] The number of coordinates are to be kept to a minimum and should not normally exceed seven.

[83] Only for SIGMET for tropical cyclones.

[84] Only for SIGMET for radioactive cloud. A radius of up to 30 kilometres (or 16 nautical miles) from the source and a vertical extent from surface (SFC) to the upper limit of the flight information region/upper flight information region (FIR/UIR) or control area (CTA) is to be applied.

[85] Only for SIGMET for tropical cyclones.

[86] In the case of volcanic ash cloud covering more than one area within the FIR, these elements can be repeated, as necessary. Each location and forecast position are to be preceded by an observed or forecast time.

[87] The elements ‘forecast time’ and ‘forecast position’ are not to be used in conjunction with the element ‘movement or expected movement’.

[88] For SIGMET for radioactive cloud, only stationary (STNR) is to be used for the element ‘movement or expected movement’.

[89] In the case of volcanic ash cloud covering more than one area within the FIR, these elements can be repeated, as necessary. Each location and forecast position are to be preceded by an observed or forecast time.

[90] In the case of volcanic ash cloud covering more than one area within the FIR, these elements can be repeated, as necessary. Each location and forecast position are to be preceded by an observed or forecast time.

[91] In the case of cumulonimbus clouds associated with a tropical cyclone covering more than one area within the FIR, these elements can be repeated as necessary. Each location and forecast position must be preceded by an observed or forecast time.

[92] The elements ‘forecast time’ and ‘forecast position’ are not to be used in conjunction with the element ‘movement or expected movement’.

[93] Only for SIGMET for tropical cyclones.

[94] The term ‘CB’ is to be used when the forecast position for the cumulonimbus cloud is included.

[95] In the case of volcanic ash cloud covering more than one area within the FIR, these elements can be repeated, as necessary. Each location and forecast position are to be preceded by an observed or forecast time.

[96] In the case of cumulonimbus clouds associated with a tropical cyclone covering more than one area within the FIR, these elements can be repeated as necessary. Each location and forecast position must be preceded by an observed or forecast time.

[97] For SIGMET for radioactive cloud, only within (WI) is to be used for theelements ‘location’ and ‘forecast position’.

[98] The elements ‘forecast time’ and ‘forecast position’ are not to be used in conjunction with the element ‘movement or expected movement’.

[99] The forecast position for cumulonimbus (CB) cloud occurring in connection with tropical cyclones relates to the forecast time of the tropical cyclone centre position, not to the end of the validity period of the SIGMET.

[100] The number of coordinates are to be kept to a minimum and should not normally exceed seven.

[101] Only for SIGMET for volcanic ash.

[102] Only for SIGMET for radioactive cloud. A radius of up to 30 kilometres (or 16 nautical miles) from the source and a vertical extent from surface (SFC) to the upper limit of the flight information region/upper flight information region (FIR/UIR) or control area (CTA) is to be applied.

[103] Only for SIGMET for tropical cyclones.

[104] To be used for more than one volcanic ash clouds or cumulonimbus clouds associated with a tropical cyclone simultaneously affecting the FIR concerned.’

[105] To be used for more than one volcanic ash clouds or cumulonimbus clouds associated with a tropical cyclone simultaneously affecting the FIR concerned.’

[106] Only for SIGMET for volcanic ash.

[107] Used only when the message is issued to indicate that a test or an exercise is taking place. When the word ‘TEST’ or the abbreviation ‘EXER’ is included, the message may contain information that should not be used operationally or will otherwise end immediately after the word ‘TEST’.

[108] The term ‘resuspended’ to be used for volcanic ash deposits raised by the wind.

[109] If a volcanic ash cloud is reported (e.g. AIREP) but not identifiable from the satellite data.

[110] A straight line between two points drawn on a map in the Mercator projection or a straight line between two points which crosses lines of longitude at a constant angle.

[111] Up to four selected layers.

[112] A straight line between two points drawn on a map in the Mercator projection or a straight line between two points which crosses lines of longitude at a constant angle.

[113] Up to four selected layers.

[114] A straight line between two points drawn on a map in the Mercator projection or a straight line between two points which crosses lines of longitude at a constant angle.

[115] Up to four selected layers.

[116] The term ‘resuspended’ to be used for volcanic ash deposits raised by the wind.

[117] To be included (as free text)

[118] To be included (as free text) where space in the Remarks section allows.

[119] Used only when the message is issued to indicate that a test or an exercise is taking place. When the word ‘TEST’ or the abbreviation ‘EXER’ is included, the message may contain information that should not be used operationally or will otherwise end immediately after the word ‘TEST’.

[120] In the case of CB clouds associated with a tropical cyclone covering more than one area within the area of responsibility, this element can be repeated, as necessary.

[121] The number of coordinates should be kept to a minimum and should not normally exceed seven.

[122]  Commission Regulation (EU) No 255/2010 of 25 March 2010 laying down common rules on air traffic flow management (OJ L 80, 26.3.2010, p. 10).

[123]  Commission Regulation (EC) No 2150/2005 of 23 December 2005 laying down common rules for the flexible use of airspace (OJ L 342, 24.12.2005, p. 20).