- Latest available (Revised)
- Point in Time (31/12/2020)
- Original (As adopted by EU)
Commission Regulation (EC) No 633/2007 of 7 June 2007 laying down requirements for the application of a flight message transfer protocol used for the purpose of notification, coordination and transfer of flights between air traffic control units (Text with EEA relevance)
When the UK left the EU, legislation.gov.uk published EU legislation that had been published by the EU up to IP completion day (31 December 2020 11.00 p.m.). On legislation.gov.uk, these items of legislation are kept up-to-date with any amendments made by the UK since then.
Legislation.gov.uk publishes the UK version. EUR-Lex publishes the EU version. The EU Exit Web Archive holds a snapshot of EUR-Lex’s version from IP completion day (31 December 2020 11.00 p.m.).
Point in time view as at 31/12/2020.
There are currently no known outstanding effects by UK legislation for Commission Regulation (EC) No 633/2007, Introductory Text.
Revised legislation carried on this site may not be fully up to date. At the current time any known changes or effects made by subsequent legislation have been applied to the text of the legislation you are viewing by the editorial team. Please see ‘Frequently Asked Questions’ for details regarding the timescales for which new effects are identified and recorded on this site.
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)(1), and in particular Article 3(1) thereof,
Having regard to Regulation (EC) No 549/2004 of the European Parliament and the Council of 10 March 2004 laying down the framework for the creation of the single European sky (the framework Regulation)(2), and in particular Article 8(2) thereof,
Whereas:
(1) Information exchanges between flight data processing systems are established between air traffic control units for the purposes of notification, coordination and transfer of flights and for the purposes of civil-military coordination. These information exchanges should rely upon appropriate and harmonised communication protocols to secure their interoperability.
(2) The European Organisation for the Safety of Air Navigation (Eurocontrol) has been given a mandate in accordance with Article 8(1) of Regulation (EC) No 549/2004 to develop requirements for a flight message transfer protocol to be used 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 Flight 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/EEC(3), 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) It is becoming more and more difficult and costly to maintain Communication equipment and software complying with the Eurocontrol standard for Flight Data Exchange. An appropriate new standard to support the exchange of flight data should therefore be adopted.
(5) The Transmission Control Protocol together with the Internet Protocol (TCP/IP) is currently considered as the most appropriate basis to meet the communication requirements of flight data exchanges between air traffic control units.
(6) This Regulation should cover the application of a flight message transfer protocol used for the information exchanges in accordance with 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(4).
(7) This Regulation should not cover military operations and training as referred in Article 1(2) of Regulation (EC) No 549/2004.
(8) In a statement on military issues related to the Single European Sky(5), 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.
(9) The application of the concept of 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.
(10) 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.
(11) In accordance with Article 10(2) of Regulation (EC) No 552/2004, the date for the application of the essential requirements and transitional arrangements may be specified by the relevant implementing rules for interoperability.
(12) 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.
(13) 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:
OJ L 254, 9.10.2000, p. 1. Regulation as amended by Regulation (EC) No 980/2002 (OJ L 150, 8.6.2002, p. 38).
Latest Available (revised):The latest available updated version of the legislation incorporating changes made by subsequent legislation and applied by our editorial team. Changes we have not yet applied to the text, can be found in the ‘Changes to Legislation’ area.
Original (As adopted by EU): The original version of the legislation as it stood when it was first adopted in the EU. No changes have been applied to the text.
Point in Time: This becomes available after navigating to view revised legislation as it stood at a certain point in time via Advanced Features > Show Timeline of Changes or via a point in time advanced search.
Geographical Extent: Indicates the geographical area that this provision applies to. For further information see ‘Frequently Asked Questions’.
Show Timeline of Changes: See how this legislation has or could change over time. Turning this feature on will show extra navigation options to go to these specific points in time. Return to the latest available version by using the controls above in the What Version box.
Access essential accompanying documents and information for this legislation item from this tab. Dependent on the legislation item being viewed this may include:
This timeline shows the different versions taken from EUR-Lex before exit day and during the implementation period as well as any subsequent versions created after the implementation period as a result of changes made by UK legislation.
The dates for the EU versions are taken from the document dates on EUR-Lex and may not always coincide with when the changes came into force for the document.
For any versions created after the implementation period as a result of changes made by UK legislation the date will coincide with the earliest date on which the change (e.g an insertion, a repeal or a substitution) that was applied came into force. For further information see our guide to revised legislation on Understanding Legislation.
Use this menu to access essential accompanying documents and information for this legislation item. Dependent on the legislation item being viewed this may include:
Click 'View More' or select 'More Resources' tab for additional information including: