- Latest available (Revised)
- Original (As adopted by EU)
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)
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.).
There are currently no known outstanding effects for the Commission Regulation (EC) No 1032/2006.
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.
Interoperability and performance requirements
1.1. The system shall provide all the information required for the...
1.2. The system shall be able to automatically receive, store, process,...
1.3. The system shall issue a warning when information exchange facility...
1.4. The system shall be able to provide warnings related to...
1.6. The system shall be capable of providing the ATC staff...
PART B: REQUIREMENTS FOR MANDATORY PROCESSES SUPPORTED BY SYSTEM INFORMATION EXCHANGES
1.2.1. The notification process shall be performed at least once for...
1.2.2. The eligibility criteria for cross boundary notification of flights shall...
1.2.3. When the notification process cannot be performed by a bilateral...
1.2.4. When performed, the notification process shall precede the initial coordination...
1.2.5. The notification process shall take place again each time there...
1.2.6. If a discrepancy is identified between the transmitted data and...
1.3. Time criteria for the initiation of the notification process
2.2.1. The initial coordination process shall be performed for all eligible...
2.2.2. Eligibility criteria for cross boundary initial coordination of flights shall...
2.2.3. Unless already manually initiated, the initial coordination process shall be...
2.2.4. The initial coordination process for a flight shall only be...
2.2.5. Following an abrogation of coordination process, the initial coordination process...
2.2.6. Completion of the initial coordination process including confirmation from the...
2.2.7. Failure of the initial coordination process to confirm completion, within...
2.2.8. The initial coordination information shall be made available at the...
3.2.1. The revision of coordination process may take place one or...
3.2.2. Revision of coordination process shall take place when:
3.2.3. Where bilaterally agreed, revision of coordination process shall take place...
3.2.4. Completion of the revision of coordination process including confirmation from...
3.2.5. Failure of the revision of coordination process to confirm completion,...
3.2.6. The revision of coordination process shall take place immediately following...
3.2.7. The revision of coordination process shall be inhibited after the...
3.2.8. The Revision of coordination information shall be made available at...
4. THE ABROGATION OF COORDINATION
4.2.1. The abrogation of coordination process shall take place with a...
4.2.2. The abrogation of coordination process may take place with a...
4.2.3. Completion of the abrogation of coordination process including confirmation from...
4.2.4. Failure of the abrogation of coordination process to confirm completion,...
4.2.5. The abrogation of coordination information shall be made available at...
6. CHANGE TO BASIC FLIGHT DATA
6.2.1. A change to basic flight data process shall only take...
6.2.2. A change to basic flight data process shall be initiated...
6.2.3. Completion of the change to basic flight data process including...
6.2.4. Failure of the change to basic flight data process to...
6.2.5. The change to basic flight data information shall be made...
PART C: REQUIREMENTS FOR OPTIONAL PROCESSES SUPPORTED BY SYSTEM INFORMATION EXCHANGES
1. PRE-DEPARTURE NOTIFICATION AND COORDINATION
1.1. Flight information concerned
1.1.1. The information subject to the pre-departure notification and coordination process...
1.1.2. The information subject to the pre-departure notification and coordination process...
1.1.3. The content of the ‘equipment capability and status’ information shall...
1.1.4. The ‘equipment capability and status’ information may contain other items...
1.2.1. Pre-departure notification and coordination process shall take place one or...
1.2.2. Eligibility criteria for cross boundary pre-departure notification and coordination of...
1.2.3. The pre-departure notification and coordination process shall take place again...
1.2.5. Failure of the pre-departure notification and coordination process to confirm...
1.2.6. The pre-departure notification and coordination information shall be made available...
2.2.1. The change of frequency process shall be manually initiated by...
2.2.2. Completion of the change of frequency process including confirmation from...
2.2.3. Failure of the change of frequency process to confirm completion,...
2.2.4. The change of frequency information shall be made available to...
3. MANUAL ASSUMPTION OF COMMUNICATIONS
3.2.1. The manual assumption of communications process shall be initiated by...
3.2.2. Completion of the manual assumption of communications process including confirmation...
3.2.3. Failure of the manual assumption of communication process to confirm...
3.2.4. The manual assumption of communications information shall be presented immediately...
4. CROSSING INTENTION NOTIFICATION
4.2.1. The crossing intention notification process shall be initiated manually by...
4.2.2. Completion of the crossing intention notification process including confirmation from...
4.2.3. Failure of the crossing intention notification process to confirm completion,...
4.2.4. The crossing intention notification information shall be made available at...
5.1. Flight information concerned
5.1.1. The information subject to the crossing clearance request process shall...
5.1.2. If bilaterally agreed, a crossing clearance request shall contain the...
5.1.3. The content of the ‘equipment capability and status’ information shall...
5.1.4. The ‘equipment capability and status’ information may contain other items...
5.2.1. The crossing clearance request shall be initiated at the controller's...
5.2.2. Completion of the crossing clearance request process including confirmation from...
5.2.3. Failure of the crossing clearance request process to confirm completion,...
5.2.4. The crossing clearance request information shall be made available at...
6.2.1. The counter-proposal shall include a proposed new flight level and/or...
6.2.2. Completion of the crossing counter-proposal process including confirmation from the...
6.2.3. Failure of the crossing counter-proposal process to confirm completion, within...
6.2.4. The crossing counter-proposal information shall be made available at the...
7.2.1. A crossing cancellation process shall be initiated by the unit...
7.2.2. A crossing cancellation process shall be triggered automatically or manually...
7.2.3. Completion of the crossing cancellation process including confirmation from the...
7.2.4. Failure of the crossing cancellation process to confirm completion, within...
7.2.5. The crossing cancellation information shall be made available at the...
PART D: REQUIREMENTS FOR PROCESSES SUPPORTING DATA LINK SERVICES
1.2.1. One logon forward process shall be performed for each data-link...
1.2.2. The logon forward process shall be initiated at or as...
1.2.3. Eligibility criteria for the logon forward process shall be in...
1.2.4. The logon forward information shall be included with the corresponding...
1.2.5. The logged-on status of the flight may be displayed at...
1.2.6. Completion of the logon forward process, including confirmation from the...
1.2.7. Failure of the logon forward process to confirm completion, within...
2.2.1. One next authority notified process shall be performed for each...
2.2.2. The next authority notified process shall be initiated after the...
2.2.3. Following the successful processing of the next authority notified information...
2.2.4. If the next authority notified information has not been received...
2.2.5. Completion of the next authority notified process, including confirmation from...
2.2.6. Failure of the next authority notified process to confirm completion,...
Requirements concerning quality of service
1. Availability, reliability, data security and data integrity
1.1. The system information exchange facilities shall be available during the...
1.2. Any scheduled down-time periods shall be bilaterally agreed between the...
1.3. The reliability for a system information exchange link shall be...
1.4. The integrity and security of information exchanged using system information...
1. The verification activities shall demonstrate the conformity of constituents with...
2. The manufacturer shall manage the conformity assessment activities and shall...
3. The manufacturer shall ensure that the constituents implementing information exchanges...
4. Upon satisfying completion of verification of conformity or suitability for...
PART B: REQUIREMENTS FOR THE VERIFICATION OF SYSTEMS REFERRED TO IN ARTICLE 8(1)
1. The verification of systems shall demonstrate the conformity of these...
2. The verification of systems implementing information exchanges supporting the process...
3. Test tools used for the verification of systems implementing information...
4. The verification of systems implementing information exchanges supporting the process...
5. The air navigation service provider shall manage the verification activities...
6. The air navigation service provider shall ensure that the implementation...
7. Upon satisfying completion of verification of compliance, air navigation service...
PART C: REQUIREMENTS FOR THE VERIFICATION OF SYSTEMS REFERRED TO IN ARTICLE 8(2)
1. The verification of systems shall demonstrate the conformity of these...
2. The verification of systems implementing information exchanges supporting the process...
3. Test tools used for the verification of systems implementing information...
4. The verification of systems implementing information exchanges supporting the process...
5. The air navigation service provider shall determine the appropriate simulated...
6. The appointed body shall manage the verification activities and shall...
7. The appointed body shall ensure that the implementation of information...
8. Upon satisfying completion of verification tasks, the appointed body shall...
9. Then, the air navigation service provider shall draw up the...
Conditions referred to in Article 8
1. The air navigation service provider must have in place reporting...
2. The air navigation service provider must ensure that the personnel...
3. The air navigation service provider must ensure that the personnel...
4. The air navigation service provider must ensure that the personnel...
5. The air navigation service provider must ensure that the personnel...
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.
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: