ANNEX I U.K. Interoperability and performance requirements(referred to in Article 3)

PART C: U.K. REQUIREMENTS FOR OPTIONAL PROCESSES SUPPORTED BY SYSTEM INFORMATION EXCHANGES

7. CROSSING CANCELLATION U.K.

7.1. Flight information concerned U.K.

7.1.1. The crossing cancellation process shall ensure association with the previous notification or coordination process that is canceled. U.K.

7.2. Rules of application U.K.

7.2.1. A crossing cancellation process shall be initiated by the unit responsible for the flight when one of the following occurs: U.K.

• the flight previously notified by a basic flight data process will now not enter the airspace of the notified unit or is no longer of interest to the notified unit,

• the crossing will not be executed on the route expressed in the crossing notification information,

• the crossing will not be executed according to the conditions under negotiation or according to the conditions agreed after an airspace crossing dialogue.

7.2.2. A crossing cancellation process shall be triggered automatically or manually by a controller input in accordance with the letters of agreement. U.K.

7.2.3. Completion of the crossing cancellation process including confirmation from the notified/requested unit shall be provided at the cancelling unit. U.K.

7.2.4. Failure of the crossing cancellation process to confirm completion, within the applicable quality of service requirements, shall result in a warning at the appropriate working position within the cancelling unit. U.K.

7.2.5. The crossing cancellation information shall be made available at the appropriate working position in the notified/requested unit. U.K.