Commission Regulation (EC) No 1032/2006Show full title

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

1. PRE-DEPARTURE NOTIFICATION AND COORDINATION U.K.

1.1. Flight information concerned U.K.

1.1.1. The information subject to the pre-departure notification and coordination process shall include as a minimum: U.K.

• aircraft identification,

• SSR mode and code (if available),

• departure aerodrome,

• estimated take-off time or estimate data, as bilaterally agreed,

• destination aerodrome,

• number and type of aircraft.

1.1.2. The 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: U.K.

• type of flight,

• equipment capability and status.

1.1.3. The content of the ‘equipment capability and status’ information shall include RVSM and 8.33 KHz capability as a minimum. U.K.

1.1.4. The ‘equipment capability and status’ information may contain other items as bilaterally agreed by the letters of agreement. U.K.

1.2. Rules of Application U.K.

1.2.1. Pre-departure notification and coordination process shall take place one or more times for each eligible flight planned to cross the boundaries where the flight time from departure to the coordination point would not allow sufficient time for the initial coordination or notification processes to be executed. U.K.

1.2.2. Eligibility criteria for cross boundary pre-departure notification and coordination of flights shall be in accordance with the letters of agreement. U.K.

1.2.3. The pre-departure notification and coordination process shall take place again each time there is a change to any item of the data subject to the previous pre-departure notification and coordination process before departure. U.K.

1.2.4. Completion of the pre-departure notification and coordination process including confirmation from the receiving unit shall be provided at the transferring unit. U.K.

1.2.5. Failure of the pre-departure notification and coordination process to confirm completion, within the applicable quality of service requirements, shall result in a warning at the working position responsible for the notification/coordination of the flight within the transferring unit. U.K.

1.2.6. The pre-departure notification and coordination information shall be made available at the appropriate working position in the notified unit. U.K.

2. CHANGE OF FREQUENCY U.K.

2.1. Flight information concerned U.K.

2.1.1. The information subject to the change of frequency process shall include as a minimum: U.K.

• aircraft identification.

2.1.2. The information subject to the change of frequency process shall include any of the following, if available: U.K.

• release indication,

• cleared flight level,

• assigned heading/track or direct clearance,

• assigned speed,

• assigned rate of climb/descent.

2.1.3. If bilaterally agreed, change of frequency data shall contain the following: U.K.

• current track position,

• instructed frequency.

2.2. Rules of application U.K.

2.2.1. The change of frequency process shall be manually initiated by the transferring controller. U.K.

2.2.2. Completion of the change of frequency process including confirmation from the receiving unit shall be provided at the transferring ATC unit. U.K.

2.2.3. Failure of the change of frequency process to confirm completion, within the applicable quality of service requirements, shall result in a warning at the appropriate working position within the transferring ATC unit. U.K.

2.2.4. The change of frequency information shall be made available to the accepting controller without delay. U.K.

3. MANUAL ASSUMPTION OF COMMUNICATIONS U.K.

3.1. Flight information concerned U.K.

3.1.1. The information subject to the manual assumption of communications process shall include as a minimum the aircraft identification. U.K.

3.2. Rules of application U.K.

3.2.1. The manual assumption of communications process shall be initiated by the accepting unit when communication is established. U.K.

3.2.2. Completion of the manual assumption of communications process including confirmation from the transferring unit shall be provided at the accepting ATC unit. U.K.

3.2.3. Failure of the manual assumption of communication process to confirm completion, within the applicable quality of service requirements, shall result in a warning at the appropriate working position within the accepting ATC unit. U.K.

3.2.4. The manual assumption of communications information shall be presented immediately to the controller in the transferring unit. U.K.

4. CROSSING INTENTION NOTIFICATION U.K.

4.1. Flight information concerned U.K.

4.1.1. The information subject to the crossing intention notification process shall include as a minimum: U.K.

• aircraft identification,

• SSR mode and code,

• number and type of aircraft,

• sector in charge identifier,

• crossing route including estimated times and flight levels for each point on the route.

4.2. Rules of application U.K.

4.2.1. The crossing intention notification process shall be initiated manually by the controller, or automatically as described in the letters of agreement. U.K.

4.2.2. Completion of the crossing intention notification process including confirmation from the notified unit shall be provided to the notifying unit. U.K.

4.2.3. Failure of the crossing intention notification process to confirm completion, within the applicable quality of service requirements, shall result in a warning at the notifying unit. U.K.

4.2.4. The crossing intention notification information shall be made available at the appropriate working position in the notified unit. U.K.

5. CROSSING CLEARANCE REQUEST U.K.

5.1. Flight information concerned U.K.

5.1.1. The information subject to the crossing clearance request process shall include as a minimum: U.K.

• aircraft identification,

• SSR mode and code,

• number and type of aircraft,

• sector in charge identifier,

• crossing route including estimated times and flight levels for each point on the route.

5.1.2. If bilaterally agreed, a crossing clearance request shall contain the equipment capability and status. U.K.

5.1.3. The content of the ‘equipment capability and status’ information shall include RVSM capability as a minimum. U.K.

5.1.4. The ‘equipment capability and status’ information may contain other items as bilaterally agreed. U.K.

5.2. Rules of application U.K.

5.2.1. The crossing clearance request shall be initiated at the controller's discretion, in accordance with the conditions specified in the letters of agreement. U.K.

5.2.2. Completion of the crossing clearance request process including confirmation from the unit receiving the request shall be provided to the requesting unit. U.K.

5.2.3. Failure of the crossing clearance request process to confirm completion, within the applicable quality of service requirements, shall result in a warning at the appropriate working position within the requesting unit. U.K.

5.2.4. The crossing clearance request information shall be made available at the appropriate working position in the unit receiving the request. U.K.

5.3. Operational reply U.K.

5.3.1. A crossing clearance request process shall be replied to by: U.K.

• an acceptance of the proposed route/airspace crossing details, or,

• a counter-proposal including different route/airspace crossing details as specified in section 6 below, or

• a rejection of the proposed route/airspace crossing details.

5.3.2. If an operational reply is not received within a bilaterally agreed time interval a warning shall be issued at the appropriate working position within the requesting unit. U.K.

6. CROSSING COUNTER-PROPOSAL U.K.

6.1. Flight information concerned U.K.

6.1.1. The crossing counter-proposal process shall ensure association with the flight previously subject to coordination. U.K.

6.1.2. The information subject to the crossing counter-proposal process shall include as a minimum: U.K.

• aircraft identification,

• crossing route including estimated times and flight levels for each point on the route.

6.2. Rules of application U.K.

6.2.1. The counter-proposal shall include a proposed new flight level and/or route. U.K.

6.2.2. Completion of the crossing counter-proposal process including confirmation from the original requesting unit shall be provided to the counter proposing unit. U.K.

6.2.3. Failure of the crossing counter-proposal process to confirm completion, within the applicable quality of service requirements, shall result in a warning at the appropriate working position within the counter proposing unit. U.K.

6.2.4. The crossing counter-proposal information shall be made available at the appropriate working position in the original requesting unit. U.K.

6.3. Operational reply U.K.

6.3.1. The confirmation of the successful processing of the crossing counter-proposal information in the original requesting unit shall be followed by an operational reply from the original requesting unit. U.K.

6.3.2. The operational reply to a crossing counter-proposal shall be an acceptance or rejection as appropriate. U.K.

6.3.3. If an operational reply is not received within a bilaterally agreed time interval a warning shall be issued at the appropriate working position within the counter proposing unit. U.K.

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.