Annexes to COM(2013)410 - Implementation of the Single European Sky (recast) - Main contents
Please note
This page contains a limited version of this dossier in the EU Monitor.
| dossier | COM(2013)410 - Implementation of the Single European Sky (recast). |
|---|---|
| document | COM(2013)410  |
| date | June 11, 2013 |
è1 REQUIREMENTS FOR QUALIFIED ENTITIES ç
è2 The qualified entities must: ç
– be able to document extensive experience in assessing public and private entities in the air transport sectors, in particular air navigation service providers, and in other similar sectors in one or more of the fields covered by this Regulation,;
– have comprehensive rules and regulations for the periodic survey of the abovementioned entities, published and continually upgraded and improved through research and development programmes,;
ê 1070/2009 Art. 2.13(b)
– not be controlled by air navigation service providers, by airport management authorities or by others engaged commercially in the provision of air navigation services or in air transport services,
– be established with significant technical, managerial, support and research staff commensurate with the tasks to be carried out,.
ê 552/2004
- 6. The body must take out liability insurance unless its liability is assumed by the Member State in accordance with national law, or the Member State itself is directly responsible for the inspections.
7. The staff of the body must observe professional secrecy with regard to all information acquired in carrying out their tasks under this Regulation.
ê 552/2004 (adapted)
ð new
ANNEX V
NOTIFIED BODIES
1 The body ð qualified entity ï , its Director and the staff responsible for carrying out the checks may not become involved, either directly or as authorised representatives, in the design, manufacture, marketing or maintenance of the constituents or systems or in their use. This does not exclude the possibility of an exchange of technical information between the manufacturer or constructor and that body.
2. The body and the staff responsible for the checks ð The qualified entity ï must carry out the checks with the greatest possible professional integrity and the greatest possible technical competence and must be free of any pressure and incentive, in particular of a financial type, which could affect Ö its Õ their judgment or the results of Ö its Õ their inspection, in particular from persons or groups of persons affected by the results of the checks.
3. The body must employ staff and possess the means required to perform adequately the technical and administrative tasks linked with the checks; it should also have access to the equipment needed for exceptional checks.
ê 552/2004 (adapted)
ð new
4. The staff ð of the qualified entity ï responsible for inspection must have:
– sound technical and vocational training,
– satisfactory knowledge of the requirements of the inspections they carry out and adequate experience of such operations,
– the ability required to draw up the declarations, records and reports to demonstrate that the inspections have been carried out.
- 5. The ð guaranteed ï impartiality of the inspection staff must be guaranteed. Their Ö staff's Õ remuneration must not depend on the number of inspections carried out or on the results of such inspections.
ê 1070/2009 Art. 2.13(b)
ð new
– be managed and administered in such a way as to ensure the confidentiality of information required by the administration,;
– be prepared to provide relevant information to the national supervisory authority concerned,;
– have defined and documented its policy and objectives for and commitment to quality and have ensured that this policy is understood, implemented and maintained at all levels in the organisation,;
– have developed, implemented and maintained an effective internal quality system based on appropriate parts of internationally recognised quality standards and in compliance with EN 45004 (inspection bodies) and with EN 29001, as interpreted by the IACS Quality System Certification Scheme Requirements,;
– be subject to certification of its quality system by an independent body of auditors recognised by the authorities of the Member State in which it is located.;
ê 550/2004
ð new
ANNEX II
CONDITIONS TO BE ATTACHED TO CERTIFICATES
1. Certificates shall specify:
(a) the national supervisory authority issuing the certificate;
(b) the applicant (name and address);
(c) the services which are certified;
(d) a statement of the applicant's conformity with the common requirements, as defined in Article 6 ð 8b ï of this Regulation ð (EC) No 216/2008 ï ;
(e) the date of issue and the period of validity of the certificate.
2. Additional conditions attached to certificates may, as appropriate, be related to:
(a) non-discriminatory access to services for airspace users and the required level of performance of such services, including safety and interoperability levels;
(b) the operational specifications for the particular services;
(c) the time by which the services should be provided;
(d) the various operating equipment to be used within the particular services;
(e) ring-fencing or restriction of operations of services other than those related to the provision of air navigation services;
(f) contracts, agreements or other arrangements between the service provider and a third party and which concern the service(s);
(g) provision of information reasonably required for the verification of compliance of the services with the common requirements, including plans, financial and operational data, and major changes in the type and/or scope of air navigation services provided;
(h) any other legal conditions which are not specific to air navigation services, such as conditions relating to the suspension or revocation of the certificate.
ê 552/2004
ANNEX I
LIST OF SYSTEMS FOR AIR NAVIGATION SERVICES
For the purpose of this Regulation the EATMN is subdivided into eight systems.
1. Systems and procedures for airspace management.
2. Systems and procedures for air traffic flow management.
3. Systems and procedures for air traffic services, in particular flight data processing systems, surveillance data processing systems and human-machine interface systems.
4. Communications systems and procedures for ground-to-ground, air-to-ground and air-to-air communications.
5. Navigation systems and procedures.
6. Surveillance systems and procedures.
7. Systems and procedures for aeronautical information services.
8. Systems and procedures for the use of meteorological information.
ANNEX II
ESSENTIAL REQUIREMENTS
Part A: General requirements
These are network-wide requirements that are generally applicable to each one of the systems identified in Annex I.
1. Seamless operation
Air traffic management systems and their constituents shall be designed, built, maintained and operated using the appropriate and validated procedures, in such a way as to ensure the seamless operation of the EATMN at all times and for all phases of flight. Seamless operation can be expressed, in particular, in terms of information-sharing, including the relevant operational status information, common understanding of information, comparable processing performances and the associated procedures enabling common operational performances agreed for the whole or parts of the EATMN.
2. Support for new concepts of operation
ê 1070/2009 Art. 4.4(a)
The EATMN, its systems and their constituents shall support, on a coordinated basis, new agreed and validated concepts of operation that improve the quality, sustainability and effectiveness of air navigation services, in particular in terms of safety and capacity.
ê 552/2004
The potential of new concepts, such as collaborative decision-making, increasing automation and alternative methods of delegation of separation responsibility, shall be examined taking due account of technological developments and of their safe implementation, following validation.
3. Safety
Systems and operations of the EATMN shall achieve agreed high levels of safety. Agreed safety management and reporting methodologies shall be established to achieve this.
In respect of appropriate ground-based systems, or parts thereof, these high levels of safety shall be enhanced by safety nets which shall be subject to agreed common performance characteristics.
A harmonised set of safety requirements for the design, implementation, maintenance and operation of systems and their constituents, both for normal and degraded modes of operation, shall be defined with a view to achieving the agreed safety levels, for all phases of flight and for the entire EATMN.
Systems shall be designed, built, maintained and operated, using the appropriate and validated procedures, in such a way that the tasks assigned to the control staff are compatible with human capabilities, in both the normal and degraded modes of operation, and are consistent with required safety levels.
Systems shall be designed, built, maintained and operated using the appropriate and validated procedures, in such a way as to be free from harmful interference in their normal operational environment.
4. Civil-military coordination
The EATMN, its systems and their constituents shall support the progressive implementation of civil/military coordination, to the extent necessary for effective airspace and air traffic flow management, and the safe and efficient use of airspace by all users, through the application of the concept of the flexible use of airspace.
To achieve these objectives, the EATMN, its systems and their constituents shall support the timely sharing of correct and consistent information covering all phases of flight, between civil and military parties.
Account should be taken of national security requirements.
5. Environmental constraints
Systems and operations of the EATMN shall take into account the need to minimise environmental impact in accordance with Community legislation.
6. Principles governing the logical architecture of systems
Systems shall be designed and progressively integrated with the objective of achieving a coherent and increasingly harmonised, evolutionary and validated logical architecture within the EATMN.
7. Principles governing the construction of systems
Systems shall be designed, built and maintained on the grounds of sound engineering principles, in particular those relating to modularity, enabling interchangeability of constituents, high availability, and redundancy and fault tolerance of critical constituents.
Part B: Specific requirements
These are the requirements that are specific to each one of the systems and that complement or further refine the general requirements.
1. Systems and procedures for airspace management
1.1. Seamless operation
Information relating to pre-tactical and tactical aspects of airspace availability shall be provided to all interested parties in a correct and timely way so as to ensure an efficient allocation and use of airspace by all airspace users. This should take into account national security requirements.
2. Systems and procedures for air traffic flow management
2.1. Seamless operation
Systems and procedures for air traffic flow management shall support the sharing of correct, coherent and relevant strategic, pre-tactical and tactical, as applicable, flight information covering all phases of flight and offer dialogue capabilities with a view to achieving optimised use of airspace.
3. Systems and procedures for air traffic services
3.1. Flight data processing systems
3.1.1. Seamless operation
Flight data processing systems shall be interoperable in terms of the timely sharing of correct and consistent information, and a common operational understanding of that information, in order to ensure a coherent and consistent planning process and resource-efficient tactical coordination throughout the EATMN during all phases of flight.
In order to ensure safe, smooth and expeditious processing throughout the EATMN, flight data processing performances shall be equivalent and appropriate for a given environment (surface, terminal manoeuvring area (TMA), en-route), with known traffic characteristics and exploited under an agreed and validated operational concept, in particular in terms of accuracy and error tolerance of processing results.
3.1.2. Support for new concepts of operation
ê 1070/2009 Art. 4.4(b)
Flight data processing systems shall accommodate the progressive implementation of advanced, agreed and validated concepts of operation for all phases of flight, in particular as envisaged in the ATM Master Plan.
ê 552/2004
The characteristics of automation-intensive tools must be such as to enable coherent and efficient pre-tactical and tactical processing of flight information in parts of the EATMN.
Airborne and ground systems and their constituents supporting new, agreed and validated concepts of operation shall be designed, built, maintained and operated, using appropriate and validated procedures, in such a way as to be interoperable in terms of timely sharing of correct and consistent information and a common understanding of the current and predicted operational situation.
3.2. Surveillance data processing systems
3.2.1. Seamless operation
Surveillance data processing systems shall be designed, built, maintained and operated using the appropriate and validated procedures, in such a way as to provide the required performance and quality of service within a given environment (surface, TMA, en-route) with known traffic characteristics, in particular in terms of accuracy and reliability of computed results, correctness, integrity, availability, continuity and timeliness of information at the control position.
Surveillance data processing systems shall accommodate the timely sharing of relevant, accurate, consistent and coherent information between them to ensure optimised operations through different parts of the EATMN.
ê 1070/2009 Art. 4.4(b)
3.2.2. Support for new concepts of operation
Surveillance data processing systems shall accommodate the progressive availability of new sources of surveillance information in such a way as to improve the overall quality of service, in particular as envisaged in the ATM Master Plan.
ê 552/2004
3.3. Human-machine interface systems
3.3.1. Seamless operation
Human-machine interfaces of ground air traffic management systems shall be designed, built, maintained and operated using the appropriate and validated procedures, in such a way as to offer to all control staff a progressively harmonised working environment, including functions and ergonomics, meeting the required performance for a given environment (surface, TMA, en-route), with known traffic characteristics.
3.3.2. Support for new concepts of operation
Human-machine interface systems shall accommodate the progressive introduction of new, agreed and validated concepts of operation and increased automation, in such a way as to ensure that the tasks assigned to the control staff remain compatible with human capabilities, in both the normal and degraded modes of operation.
4. Communications systems and procedures for ground-to-ground, air-to-ground and air-to-air communications
4.1. Seamless operation
Communication systems shall be designed, built, maintained and operated using the appropriate and validated procedures, in such a way as to achieve the required performances within a given volume of airspace or for a specific application, in particular in terms of communication processing time, integrity, availability and continuity of function.
The communications network within the EATMN shall be such as to meet the requirements of quality of service, coverage and redundancy.
ê 1070/2009 Art. 4.4(b)
4.2. Support for new concepts of operation
Communication systems shall support the implementation of advanced, agreed and validated concepts of operation for all phases of flight, in particular as envisaged in the ATM Master Plan.
ê 552/2004
5. Navigation systems and procedures
5.1. Seamless operation
Navigation systems shall be designed, built, maintained and operated using appropriate and validated procedures in such a way as to achieve the required horizontal and vertical navigation performance, in particular in terms of accuracy and functional capability, for a given environment (surface, TMA, en-route), with known traffic characteristics and exploited under an agreed and validated operational concept.
6. Surveillance systems and procedures
6.1. Seamless operation
Surveillance systems shall be designed, built, maintained and operated using appropriate and validated procedures in such a way as to provide the required performance applicable in a given environment (surface, TMA, en-route) with known traffic characteristics and exploited under an agreed and validated operational concept, in particular in terms of accuracy, coverage, range and quality of service.
The surveillance network within the EATMN shall be such as to meet the requirements of accuracy, timeliness, coverage and redundancy. The surveillance network shall enable surveillance data to be shared in order to enhance operations throughout the EATMN.
7. Systems and procedures for aeronautical information services
7.1. Seamless operation
Accurate, timely and consistent aeronautical information shall be provided progressively in an electronic form, based on a commonly agreed and standardised data set.
Accurate and consistent aeronautical information, in particular concerning airborne and ground-based constituents or systems, shall be made available in a timely manner.
7.2. Support for new concepts of operation
Increasingly accurate, complete and up-to-date aeronautical information shall be made available and used in a timely manner in order to support continuous improvement of the efficiency of airspace and airport use.
8. Systems and procedures for the use of meteorological information
8.1. Seamless operation
Systems and procedures for the use of meteorological information shall improve the consistency and timeliness of its provision and the quality of its presentation, using an agreed data set.
8.2. Support for new concepts of operation
Systems and procedures for the use of meteorological information shall improve the promptness of its availability and the speed with which it may be used, in order to support continuous improvement of the efficiency of airspace and airport use.
ANNEX III
CONSTITUENTS
EC declaration
– of conformity
– of suitability for use
1. Constituents
The constituents will be identified in the implementing rules for interoperability in accordance with the provisions of Article 3 of this Regulation.
2. Scope
The EC declaration covers:
– either the assessment of the intrinsic conformity of a constituent, considered in isolation, with the Community specifications to be met, or
– the assessment/judgment of the suitability for use of a constituent, considered within its air traffic management environment.
The assessment procedures implemented by the notified bodies at the design and production stages will draw upon the modules defined in Decision 93/465/EEC, in accordance with the conditions set out in the relevant implementing rules for interoperability.
3. Contents of the EC declaration
The EC declaration of conformity or suitability for use and the accompanying documents must be dated and signed.
That declaration must be written in the same language as the instructions and must contain the following:
– the Regulation references,
– the name and address of the manufacturer or its authorised representative established within the Community (give trade name and full address and, in the case of the authorised representative, also give the trade name of the manufacturer),
– description of the constituent,
– description of the procedure followed in order to declare conformity or suitability for use (Article 5 of this Regulation),
– all of the relevant provisions met by the constituent and in particular its conditions of use,
– if applicable, name and address of notified body or bodies involved in the procedure followed in respect of conformity or suitability for use and date of examination certificate together, where appropriate, with the duration and conditions of validity of the certificate,
– where appropriate, reference to the Community specifications followed,
– identification of signatory empowered to enter into commitments on behalf of the manufacturer or of the manufacturer's authorised representative established in the Community.
ANNEX IV
SYSTEMS
EC declaration of verification of systems
Verification procedure for systems
1. Contents of EC declaration of verification of systems
The EC declaration of verification and the accompanying documents must be dated and signed. That declaration must be written in the same language as the technical file and must contain the following:
– the Regulation references,
– name and address of the air navigation service provider (trade name and full address),
– a brief description of the system,
– description of the procedure followed in order to declare conformity of the system (Article 6 of this Regulation),
– name and address of the notified body which carried out tasks pertaining to the verification procedure, if applicable,
– the references of the documents contained in the technical file,
– where appropriate, reference to the Community specifications,
– all the relevant temporary or definitive provisions to be complied with by the systems and in particular, where appropriate, any operating restrictions or conditions,
– if temporary: duration of validity of the EC declaration,
– identification of the signatory.
2. Verification procedure for systems
Verification of systems is the procedure whereby an air navigation service provider checks and certifies that a system complies with this Regulation and may be put into operation on the basis of this Regulation.
The system is checked for each of the following aspects:
– overall design,
– development and integration of the system, including in particular constituent assembly and overall adjustments,
– operational system integration,
– specific system maintenance provisions if applicable.
Where involvement of a notified body is required by the relevant implementing rule for interoperability, the notified body, after having carried out the tasks incumbent upon it in accordance with the rule, draws up a certificate of conformity in relation to the tasks it carried out. This certificate is intended for the air navigation service provider. This provider then draws up the EC declaration of verification intended for the national supervisory authority.
3. Technical file
The technical file accompanying the EC declaration of verification must contain all the necessary documents relating to the characteristics of the system, including conditions and limits of use, as well as the documents certifying conformity of constituents where appropriate.
The following documents shall be included as a minimum:
– indication of the relevant parts of the technical specifications used for procurement that ensure compliance with the applicable implementing rules for interoperability and, where appropriate, the Community specifications,
– list of constituents as referred to in Article 3 of this Regulation,
– copies of the EC declaration of conformity or suitability for use with which the above mentioned constituents must be provided in accordance with Article 5 of this Regulation accompanied, where appropriate, by a copy of the records of the tests and examinations carried out by the notified bodies,
– where a notified body has been involved in the verification of the system(s), a certificate countersigned by itself, stating that the system complies with this Regulation and mentioning any reservations recorded during performance of activities and not withdrawn,
– where there has not been involvement of a notified body, a record of the tests and installation configurations made with a view to ensuring compliance with essential requirements and any particular requirements contained in the relevant implementing rules for interoperability.
4. Submission
The technical file must be attached to the EC declaration of verification which the air navigation service provider submits to the national supervisory authority.
A copy of the technical file must be kept by the provider throughout the service life of the system. It must be sent to any other Member States which so request.
ANNEX III
CORRELATION TABLE
Regulation 549/2004 || Regulation 550/2004 || Regulation 551/2004 || Regulation 552/2004 || This Regulation
Article 1(1) to (3) || || || || Article 1(1) to (3)
|| || Article 1(3) || || Article 1(4)
Article 1(4) || || || || Article 1(5)
|| Article 1 || || || --------------
|| || Article 1(1), (2) and (4) || || --------------
|| || || Article 1 || --------------
Article 2 Nos (1) to (35) || || || || Article 2 Nos (1) to (35)
|| || || || Article 2 Nos (36) to (38)
Article 2 Nos 17, 18, 23, 24, 32, 35, 36 || || || || ---------------
Article 3 || || || || ---------------
Article 4(1) and (2) || || || || Article 3(1) and (2)
|| || || || Article 3(3) and (4)
Article 4(3) || || || || Article 3(5)
|| || || || Article 3(6)
Article 3(4) to (5) || || || || Article 3(7) and (8)
|| || || || Article 3(9)
|| Article 2(1) || || || Article 4(1a)
|| || || || Article 4(1b) to (1g)
|| Article 2(2) || || || Article 4(2)
|| || || || Article 5(1) and (2)
|| Article 2(3) to (6) || || || Article 5(3) to (6)
|| Article 3(1) and (2) || || || Article 6(1) and (2)
|| || || Article 8(1) and (3) || Article 6(3) and (4)
|| || || || Article 6(5)
|| || || Article 8(2) and (4) || -------------
|| Article 6 || || || ----------- -
Article 10(1) || || || || Article 7(1)
|| || || || Article 7(2)
|| Article 7(1) || || || Article 8(1)
|| || || || Article 8(2)
|| Article 7(4) and (6) || || || Article 8(3) and (4)
|| Article 7(2), (3), (5), (7) to (9) || || || -------------
|| Article 8 || || || Article 9
|| || || || Article 10
|| Article 9 || || || -------------
Article 11 || || || || Article 11
|| Article 14 || || || Article 12
|| Article 15 || || || Article 13
|| Article 16 || || || Article 14
|| Article 15a || || || Article 15
|| Article 9a(1) || || || Article 16(1) and (3)
|| || || || Article 16(2)
|| Article 9a(2) point (i) || || || ------------
|| Article 9a(2) || || || Article 16(4)
|| || || || Article 16(5)
|| Article 9a(3) to (9) || || || Article 16(6) to (12)
|| Article 9b || || || --------------
|| || Article 6(1) to (2b) || || Article 17(1) and (2b)
|| || || || Article 17(2c) to (2e)
|| || Article 6(3) –(4d) || || Article 17(3) to (4d)
|| || || || Article 17(4e)
|| || Article 6(4e) to (4f) || || Article 17(4f) and (4g)
|| || Article 6(5) and (7) || || Article 17(5) and (6)
|| || Article 6(8) and (9) || || -------------
|| Article 10 || || || Article 18
|| || || || Article 19
|| Article 11 || || || Article 20
|| Article 12 || || || Article 21
|| Article 13 || || || Article 22
|| || Article 3 || || ---------------
|| || Article 3a || || Article 23
|| || Article 4 || || ---------- ----
|| || Article 7 || || ---------- ----
|| || Article 8 || || ---------- ----
|| || || || Article 24(1) and (2)
|| || || Article 3(3) || ---------- ----
|| || || Article 2 to 3(2) || -------------
|| || || Article 3(4) to 7 || -------------
|| Article 17(1) || || || Article 25
|| || || || Article 26
Article 5(1) to (3) || || || || Article 27(1) to (3)
Article 5(4) and (5) || || || || -------------
Article 10(2) and (3) || || || || Article 28(1) and (2)
Article 6 || || || || Article 29
Article 7 || || || || Article 30
Article 8 || || || || Article 31
|| Article 4 || || || -------------
|| || || Article 9 || -------------
|| Article 18 || || || Article 32
Article 9 || || || || Article 33
Article 12(2) to (4) || || || || Article 34(1) to (3)
Article 12(1) || || || || -------------
|| Article 18a || || || ---- --------
|| || Article 10 || || ----- -------
Article 13 || || || || Article 35
Article 13a || || || || Article 36
|| || || Article 10 || -------------
|| || || Article 11 || Article 37
|| Article 19(1) || || || Article 38
|| Article 19(2) || || || -------------
|| Annex I || || Annex V || Annex I
|| || || Annex I || -----------
|| Annex II || || || Annex II
|| || || Annex II || ----------
|| || || || Annex III
|| || || Annex III || ----------
|| || || Annex IV || -----------
é
[1] The Framework Regulation ((EC) No 549/2004) - laying down the framework for the creation of the Single European Sky; The Service Provision Regulation ((EC) No 550/2004) - on the provision of air navigation services in the Single European Sky; The Airspace Regulation ((EC) No 551/2004) - on the organisation and use of airspace in the Single European Sky; The Interoperability Regulation ((EC) No 552/2004) - on the interoperability of the European Air Traffic Management network.
[2] An overview of SES legislation can be found in Annex III of the SES2+ Impact Assessment document.
[3] Regulation (EC) No 216/2008, as amended by Regulation (EC) No 1108/2009.
[4] Whereas the Commission Roadmap on implementation of the Joint Statement of the European Parliament, the Council of the EU and the European Commission on decentralised agencies, of July 2012, requires the standardisation of the names of all EU Agencies to conform to the same format, for reasons of clarity, this explanatory memorandum uses the currently existing name of the European Aviation Safety Agency (EASA) throughout the text. The text of the legislative proposal itself has been adapted in accordance with the new Joint Statement and Roadmap to use the standardised name "European Union Agency for Aviation (EAA)"
[5] Council Regulation (EC) No 219/2007; SESAR (the Single European Sky ATM Research Programme) is a technical pillar of SES - an ATM improvement programme involving all aviation.
[6] Regulation (EC) No 216/2008, (as amended by Regulation (EC) No 1108/2009) Art 65a.
[7] COM(2012) 573 final.
[8] Regulation (EC) No 216/2008.
[9] As mentioned above, the amendments to the EASA Basic Regulation will be of a technical nature and therefore will not be analysed in the IA context.
[10] http://ec.europa.eu/governance/impact/planned_ia/roadmaps_2013_en.htm#MOVE .
[11] OJ C 103 E, 30.4.2002, p. 1.
[12] OJ C 241, 7.10.2002, p. 24.
[13] OJ C 278, 14.11.2002, p. 13.
[14] OJ L 96, 31.3.2004, p. 1.
[15] OJ L 96, 31.3.2004, p. 10.
[16] OJ L 96, 31.3.2004, p. 20.
[17] OJ L 96, 31.3.2004, p. 26.
[18] See page 1 of this Official Journal.
[19] See page 1 of this Official Journal.
[20] See page 1 of this Official Journal.
[21] See page 9 of this Official Journal.
[22] See page 20 of this Official Journal.
[23] See page 10 of this Official Journal.
[24] See page 20 of this Official Journal.
[25] OJ C 136, 4.6.1985, p. 1.
[26] OJ L 225, 12.8.1998, p. 27.
[27] OJ L 225, 12.8.1998, p. 27.
[28] OJ L 95, 9.4.2009, p. 41
[29] OJ L 220, 30.8.1993, p. 23.
[30] OJ L 184, 17.7.1999, p. 23.
[31] OJ C 38, 6.2.2001, p. 3.
[32] OJ L 187, 29.7.1993, p. 52. Directive as last amended by Regulation (EC) No 1882/2003 of the European Parliament and of the Council (OJ L 284, 31.10.2003, p. 1).
[33] OJ L 95, 10.4.1997, p. 16. Directive as last amended by Regulation (EC) No 2082/2000 (OJ L 254, 9.10.2000, p. 1).
[34] OJ L 254, 9.10.2000, p. 1. Regulation as last amended by Regulation (EC) No 980/2002 (OJ L 150, 8.6.2002, p. 38).
[35] OJ L 79, 19.3.2008, p.1.
[36] OJ L 55, 28.2.2011, p.13.
[37] OJ L 134, 30.4.2004, p.114.
[38] OJ L 134, 30.4.2004, p. 1
[39] OJ C 179, 1.8.2006, p. 2.
[40] See page 10 of this Official Journal.
[41] OJ L 95, 9.4.2009, p. 41.
[42] OJ L 64, 2.3.2007, p. 1.
[43] See page 33 of this Official Journal.
[44] Convention modified by the protocol of 12 February 1981 and revised by the protocol of 27 June 1997.
[45] Ö Eurocontrol has been set up by the International Convention of 13 December 1960 relating to Cooperation for the Safety of Air Navigation, as modified by the protocol of 12 February 1981 and revised by the protocol of 27 June 1997. Õ
[46] See page 20 of this Official Journal.
[47] See page 10 of this Official Journal.
[48] See page 26 of this Official Journal.
[49] OJ L 243, 11.9.2002, p. 1.
[50] OJ L 204, 21.7.1998, p. 37. Directive as last amended by Directive 98/48/EC (OJ L 217, 5.8.1998, p. 18).
[51] OJ L 79, 19.3.2008, p. 1.
[52] OJ L 79, 19.3.2008, p. 1.