OpenLegislation

Commission Regulation (EC) No 1032/2006 of 6 July 2006 laying down requirements for automatic systems for the exchange of flight data for the purpose of notification, coordination and transfer of flights between air traffic control units (Text with EEA relevance)

EU Regulation No 1032/2006 · Adopted 6 July 2006 · Extends to United Kingdom

Original text. legislation.gov.uk does not revise this item, so later amendments are not shown here. Changes made to it are listed under each provision when known.

Commission Regulation (EC) No 1032/2006

of 6 July 2006

laying down requirements for automatic systems for the exchange of flight data for the purpose of notification, coordination and transfer of flights between air traffic control units

(Text with EEA relevance)

THE COMMISSION OF THE EUROPEAN COMMUNITIES,

Having regard to the Treaty establishing the European Community,

Having regard to 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)f1, and in particular Article 3(1) thereof,

Having regard to 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)f2, and in particular Article 8(2) thereof,

Whereas:

(1)

Operation of air traffic management requires safe and efficient mechanisms for the notification, coordination and transfer of flights between air traffic control units. Provision of such mechanisms within the European Air Traffic Management Network requires the automatic exchange of flight data between flight data processing systems. Examination of the current situation within the Community has revealed that in some Member States those mechanisms have not yet reached a satisfactory level, and require further improvement. It is therefore necessary to lay down requirements for flight data processing systems with regard to interoperability, performance and quality of service of their flight data exchange functions.

(2)

The European Organisation for the Safety of Air Navigation (Eurocontrol) has been mandated in accordance with Article 8(1) of Regulation (EC) No 549/2004 to develop requirements for automatic systems for the exchange of flight data for the purpose of notification, coordination and transfer of flights. This Regulation is based on the resulting mandate report of 31 March 2005.

(3)

The Eurocontrol standard for on-line data exchange was annexed to Commission Regulation (EC) No 2082/2000 of 6 September 2000 adopting Eurocontrol standards and amending Directive 97/15/EC, adopting Eurocontrol standards and amending Council Directive 93/65/EECf3, making its use mandatory within the Community in the event of procurement of new flight data processing systems. As Regulation (EC) No 2082/2000 was repealed with effect from 20 October 2005, it is necessary to update Community legislation, so as to ensure the consistency of relevant regulatory provisions.

(4)

This Regulation should not cover military operation and training as referred in Article 1(2) of Regulation (EC) No 549/2004.

(5)

In a Statement by the Member States on military issues related to the single European skyf4, the Member States committed themselves to cooperate with each other, taking into account national military requirements, in order that the concept of flexible use of airspace is fully and uniformly applied in all Member States by all users of airspace.

(6)

The application of the concept of the flexible use of airspace, as defined in Article 2(22) of Regulation (EC) No 549/2004, requires the establishment of systems for the timely exchange of flight data between air traffic service units and controlling military units.

(7)

Automated processes related to notification and initial coordination should be implemented by area control centres to provide consistent flight information at both the transferring and receiving units and to support the coordination of the planned transfer of flights. They were part of the standards laid down by Regulation (EC) No 2082/2000 and should therefore be applied from the date of entry into force of this Regulation.

(8)

Flight information transmitted during the initial coordination process should be kept up to date. Automated processes should therefore be implemented progressively in order to allow revision of the information related to flights previously subject to an initial coordination process or abrogation of coordination when the accepting unit is no longer concerned by the flight.

(9)

Air traffic control units other than area control centres could draw benefit from the implementation of automated processes for notification, initial coordination, revision of coordination and abrogation of coordination of flights. If they choose to do so, the need for interoperability of the European Air Traffic Management Network (hereinafter EATMN) means that they must apply the same requirements as apply to area control centres.

(10)

Timely exchange of flight data between air traffic services units and controlling military units should rely on the progressive implementation of automated processes. A first step should be the introduction of transmission of basic flight data between such civil and military units, together with the possibility to update them as required.

(11)

Additional automated processes have been identified which would further strengthen the coordination between air traffic control units or between air traffic services units and controlling military units. If they choose to apply additional automated processes, the need for interoperability of the EATMN means that they must apply harmonised requirements to these processes.

(12)

The implementation of this Regulation should allow further developments for the achievement of higher levels of interoperability.

(13)

With a view to maintaining or enhancing existing safety levels of operations Member States should be required to ensure the conduct by the parties concerned of a safety assessment including hazard identification, risk assessment and mitigation processes. Harmonised implementation of these processes to the systems covered by this Regulation requires the identification of specific safety requirements for all mandatory interoperability, performance and quality of service requirements.

(14)

In accordance with Article 3(3)(d) of Regulation (EC) No 552/2004, implementing rules for interoperability should describe the specific conformity assessment procedures to be used to assess either the conformity or the suitability for use of constituents as well as the verification of systems.

(15)

In accordance with Article 10(1) and (2) of Regulation (EC) No 552/2004, the dates for the application of transitional arrangements may be specified by the relevant implementing rules for interoperability.

(16)

Manufacturers and air navigation service providers should be afforded a period of time to develop new constituents and systems in conformity with the new technical requirements.

(17)

The measures provided for in this Regulation are in accordance with the opinion of the Single Sky Committee established by Article 5 of Regulation (EC) No 549/2004,

HAS ADOPTED THIS REGULATION:

Annotations to the whole text

Footnotes

f1

OJ L 96, 31.3.2004, p. 26.

f2

OJ L 96, 31.3.2004, p. 1.

f3

OJ L 254, 9.10.2000, p. 1.

f4

OJ L 96, 31.3.2004, p. 9.

Contents

  1. 1Subject-matter and scope
  2. 2Definitions
  3. 3Interoperability and performance requirements
  4. 4Quality of service requirements
  5. 5Associated procedures
  6. 6Safety requirements
  7. 7Conformity or suitability for use of constituents
  8. 8Verification of systems
  9. 9Compliance Repealed
  10. 10Transitional arrangements Repealed
  11. 11Entry into force Repealed
  12. Signature
  13. Annex I: Interoperability and performance requirements
  14. GENERAL REQUIREMENTS
  15. SYSTEM REQUIREMENTS
  16. 1.1Division 1.1
  17. 1.2Division 1.2
  18. 1.3Division 1.3
  19. 1.4Division 1.4
  20. 1.5Division 1.5
  21. 1.6Division 1.6
  22. RECORDING OF SYSTEM INFORMATION EXCHANGE DATA
  23. 2.1Division 2.1
  24. REQUIREMENTS FOR MANDATORY PROCESSES SUPPORTED BY SYSTEM INFORMATION EXCHANGES
  25. NOTIFICATION
  26. Flight information concerned
  27. 1.1.1The information subject to the Notification process shall include as a minimum:
  28. 1.1.2Division 1.1.2
  29. 1.1.3Division 1.1.3
  30. Rules of application
  31. 1.2.1Division 1.2.1
  32. 1.2.2Division 1.2.2
  33. 1.2.3Division 1.2.3
  34. 1.2.4Division 1.2.4
  35. 1.2.5The notification process shall take place again each time there is a change to any of the following data prior to the initial coordination process:
  36. 1.2.6Division 1.2.6
  37. Time criteria for the initiation of the notification process
  38. 1.3.1Division 1.3.1
  39. 1.3.2Division 1.3.2
  40. 1.3.3Division 1.3.3
  41. INITIAL COORDINATION
  42. Flight information concerned
  43. 2.1.1The information subject to the initial coordination process shall include as a minimum:
  44. 2.1.2Division 2.1.2
  45. 2.1.3Division 2.1.3
  46. Rules of application
  47. 2.2.1Division 2.2.1
  48. 2.2.2Division 2.2.2
  49. 2.2.3Unless already manually initiated, the initial coordination process shall be automatically initiated at:
  50. 2.2.4Division 2.2.4
  51. 2.2.5Division 2.2.5
  52. 2.2.6Division 2.2.6
  53. 2.2.7Division 2.2.7
  54. 2.2.8Division 2.2.8
  55. REVISION OF COORDINATION
  56. Flight information concerned
  57. 3.1.1Division 3.1.1
  58. 3.1.2Revision of coordination shall provide the following flight information if they have changed:
  59. 3.1.3If bilaterally agreed, the revision of coordination data shall provide the following if they have changed:
  60. Rules of application
  61. 3.2.1Division 3.2.1
  62. 3.2.2Revision of coordination process shall take place when:
  63. 3.2.3Where bilaterally agreed, revision of coordination process shall take place when there is any change in the following:
  64. 3.2.4Division 3.2.4
  65. 3.2.5Division 3.2.5
  66. 3.2.6Division 3.2.6
  67. 3.2.7Division 3.2.7
  68. 3.2.8Division 3.2.8
  69. THE ABROGATION OF COORDINATION
  70. Flight information concerned
  71. 4.1.1Division 4.1.1
  72. Rules of application
  73. 4.2.1The abrogation of coordination process shall take place with a unit for a coordinated flight when:
  74. 4.2.2The abrogation of coordination process may take place with a unit for a notified flight when:
  75. 4.2.3Division 4.2.3
  76. 4.2.4Division 4.2.4
  77. 4.2.5Division 4.2.5
  78. BASIC FLIGHT DATA
  79. Flight information concerned
  80. 5.1.1The information subject to the basic flight data process shall provide as a minimum:
  81. 5.1.2Division 5.1.2
  82. Rules of application
  83. 5.2.1Division 5.2.1
  84. 5.2.2Division 5.2.2
  85. 5.2.3Division 5.2.3
  86. 5.2.4Division 5.2.4
  87. CHANGE TO BASIC FLIGHT DATA
  88. Flight information concerned
  89. 6.1.1Division 6.1.1
  90. 6.1.2Division 6.1.2
  91. Rules of application
  92. 6.2.1Division 6.2.1
  93. 6.2.2Division 6.2.2
  94. 6.2.3Division 6.2.3
  95. 6.2.4Division 6.2.4
  96. 6.2.5Division 6.2.5
  97. REQUIREMENTS FOR OPTIONAL PROCESSES SUPPORTED BY SYSTEM INFORMATION EXCHANGES
  98. PRE-DEPARTURE NOTIFICATION AND COORDINATION
  99. Flight information concerned
  100. 1.1.1The information subject to the pre-departure notification and coordination process shall include as a minimum:
  101. 1.1.2The information subject to the pre-departure notification and coordination process from a terminal manoeuvring area (TMA) control unit or an ACC shall contain the following:
  102. 1.1.3Division 1.1.3
  103. 1.1.4Division 1.1.4
  104. Rules of Application
  105. 1.2.1Division 1.2.1
  106. 1.2.2Division 1.2.2
  107. 1.2.3Division 1.2.3
  108. 1.2.4Division 1.2.4
  109. 1.2.5Division 1.2.5
  110. 1.2.6Division 1.2.6
  111. CHANGE OF FREQUENCY
  112. Flight information concerned
  113. 2.1.1The information subject to the change of frequency process shall include as a minimum:
  114. 2.1.2The information subject to the change of frequency process shall include any of the following, if available:
  115. 2.1.3If bilaterally agreed, change of frequency data shall contain the following:
  116. Rules of application
  117. 2.2.1Division 2.2.1
  118. 2.2.2Division 2.2.2
  119. 2.2.3Division 2.2.3
  120. 2.2.4Division 2.2.4
  121. MANUAL ASSUMPTION OF COMMUNICATIONS
  122. Flight information concerned
  123. 3.1.1Division 3.1.1
  124. Rules of application
  125. 3.2.1Division 3.2.1
  126. 3.2.2Division 3.2.2
  127. 3.2.3Division 3.2.3
  128. 3.2.4Division 3.2.4
  129. CROSSING INTENTION NOTIFICATION
  130. Flight information concerned
  131. 4.1.1The information subject to the crossing intention notification process shall include as a minimum:
  132. Rules of application
  133. 4.2.1Division 4.2.1
  134. 4.2.2Division 4.2.2
  135. 4.2.3Division 4.2.3
  136. 4.2.4Division 4.2.4
  137. CROSSING CLEARANCE REQUEST
  138. Flight information concerned
  139. 5.1.1The information subject to the crossing clearance request process shall include as a minimum:
  140. 5.1.2Division 5.1.2
  141. 5.1.3Division 5.1.3
  142. 5.1.4Division 5.1.4
  143. Rules of application
  144. 5.2.1Division 5.2.1
  145. 5.2.2Division 5.2.2
  146. 5.2.3Division 5.2.3
  147. 5.2.4Division 5.2.4
  148. Operational reply
  149. 5.3.1A crossing clearance request process shall be replied to by:
  150. 5.3.2Division 5.3.2
  151. CROSSING COUNTER-PROPOSAL
  152. Flight information concerned
  153. 6.1.1Division 6.1.1
  154. 6.1.2The information subject to the crossing counter-proposal process shall include as a minimum:
  155. Rules of application
  156. 6.2.1Division 6.2.1
  157. 6.2.2Division 6.2.2
  158. 6.2.3Division 6.2.3
  159. 6.2.4Division 6.2.4
  160. Operational reply
  161. 6.3.1Division 6.3.1
  162. 6.3.2Division 6.3.2
  163. 6.3.3Division 6.3.3
  164. CROSSING CANCELLATION
  165. Flight information concerned
  166. 7.1.1Division 7.1.1
  167. Rules of application
  168. 7.2.1A crossing cancellation process shall be initiated by the unit responsible for the flight when one of the following occurs:
  169. 7.2.2Division 7.2.2
  170. 7.2.3Division 7.2.3
  171. 7.2.4Division 7.2.4
  172. 7.2.5Division 7.2.5
  173. REQUIREMENTS FOR PROCESSES SUPPORTING DATA LINK SERVICES
  174. 1Division 1
  175. 1.1Division 1.1
  176. 1.1.1Division 1.1.1
  177. 1.2Division 1.2
  178. 1.2.1Division 1.2.1
  179. 1.2.2Division 1.2.2
  180. 1.2.3Division 1.2.3
  181. 1.2.4Division 1.2.4
  182. 1.2.5Division 1.2.5
  183. 1.2.6Division 1.2.6
  184. 1.2.7Division 1.2.7
  185. 2Division 2
  186. 2.1Division 2.1
  187. 2.1.1Division 2.1.1
  188. 2.2Division 2.2
  189. 2.2.1Division 2.2.1
  190. 2.2.2Division 2.2.2
  191. 2.2.3Division 2.2.3
  192. 2.2.4Division 2.2.4
  193. 2.2.5Division 2.2.5
  194. 2.2.6Division 2.2.6
  195. Annex II: Requirements concerning quality of service
  196. Availability, reliability, data security and data integrity
  197. 1.1Division 1.1
  198. 1.2Division 1.2
  199. 1.3Division 1.3
  200. 1.4Division 1.4
  201. Process times
  202. 2.1Division 2.1
  203. 2.2Division 2.2
  204. 2.3Division 2.3
  205. Annex III: Safety requirements
  206. 1Division 1
  207. 2Division 2
  208. 3Division 3
  209. Annex IV
  210. Part A:: REQUIREMENTS FOR THE ASSESSMENT OF THE CONFORMITY OR SUITABILITY FOR USE OF CONSTITUENTS REFERRED TO IN ARTICLE 7
  211. 1Division 1
  212. 2The manufacturer shall manage the conformity assessment activities and shall in particular:
  213. 3Division 3
  214. 4Division 4
  215. Part B:: REQUIREMENTS FOR THE VERIFICATION OF SYSTEMS REFERRED TO IN ARTICLE 8(1)
  216. 1Division 1
  217. 2Division 2
  218. 3Division 3
  219. 4The verification of systems implementing information exchanges supporting the process of notification, coordination and transfer of flights and the process of civil-military coordination shall produce the elements of the technical file required by Annex IV(3) of the interoperability Regulation and the following elements:
  220. 5The air navigation service provider shall manage the verification activities and shall in particular:
  221. 6Division 6
  222. 7Division 7
  223. Part C:: REQUIREMENTS FOR THE VERIFICATION OF SYSTEMS REFERRED TO IN ARTICLE 8(2)
  224. 1Division 1
  225. 2Division 2
  226. 3Division 3
  227. 4The verification of systems implementing information exchanges supporting the process of notification, coordination and transfer of flights and the process of civil-military coordination shall produce the elements of the technical file required by Annex IV(3) of the interoperability Regulation and the following elements:
  228. 5Division 5
  229. 6The appointed body shall manage the verification activities and shall in particular:
  230. 7Division 7
  231. 8Division 8
  232. 9Division 9
  233. Annex V: Conditions referred to in Article 8
  234. 1Division 1
  235. 2Division 2
  236. 3Division 3
  237. 4Division 4
  238. 5Division 5