Section 4, Chapter 2 - Area Control Procedures Flashcards
What are the principles of operation for an ACC sector team?
The principles of operation for an ACC sector team include:
- Each controller is responsible for efficiently performing specifically allocated tasks detailed in MATS Part 2.
- Controllers must monitor the actions of other sector team members as much as their primary duties allow.
- Sectors must have a defined prime flight data display for conflict detection, reflecting all clearance instructions and communications.
- Inter-sector coordination requires established criteria that allow the coordinator to use surveillance-derived information for traffic transfer between sectors without referring to the controller, when authorized by the CAA.
What are the requirements for coordination between Area Control Centres (ACC) before transferring control of an aircraft?
Coordination between ACCs or sectors must occur before an aircraft penetrates another’s airspace. The transferring controller is responsible for initiating coordination and complying with the accepting controller’s conditions. The process is complete when:
- Notification, negotiation, and agreement occur progressively, step-by-step.
- It is agreed that aircraft can proceed under specified conditions without individual coordination, as detailed in MATS Part 2.
- An estimate message is passed and no objections are raised by the accepting ATC unit. This procedure must be approved by the CAA.
What must be done if there are subsequent changes in flight level, routing, or revisions of 3 minutes or more before transferring communication between ACCs?
If there are subsequent changes in flight level, routing, or revisions of 3 minutes or more, the transferring controller must re-coordinate these changes and reach an agreement before the transfer of communication takes place.
What must be done if the first reporting point after take-off is in an adjoining area?
If the first reporting point after take-off is in an adjoining area, an approval request must be made to that ACC, and coordination must be achieved before giving clearance to the aircraft. The CAA may waive the requirement for approval requests.
Can an ACC provide service to aircraft outside its FIR, and how can transfer points be adjusted?
Normally, an ACC provides service only to aircraft within its own FIR. However, transfer points can be varied by prior arrangement between ACCs to suit traffic arrangements, either permanently or for a particular flight.
What data must Approach Control units promptly advise to Area Control regarding IFR flights, and what delegations and modifications can be made?
Approach Control units must promptly advise Area Control of the following data on IFR flights:
- Lowest level at the holding point available for use by Area Control.
- Average time interval between successive approaches.
- Revisions to expected approach times when variations of 5 minutes or more occur.
- Arrival times over the holding point if these vary by 3 minutes or more from the estimate.
- Missed approaches when re-routing is necessary, for coordinated subsequent action.
- Departure times of aircraft.
- All information on overdue aircraft.
This information passing can be delegated from Approach to Aerodrome Control, and any of these items can be removed from routine practice by agreement with Area Control.
What instructions can Area Control give regarding the take-off times for departing aircraft, and what must be communicated to aerodrome units?
Area Control may specify a specific time or a time slot during which an aircraft is authorized to take off. Units at aerodromes must be advised of any anticipated delays to departing aircraft along with the reason for the delay.
What are the requirements for Area Control when releasing inbound aircraft to Approach Control?
Estimates and Release Messages:
- Estimates on inbound aircraft must be passed to Approach Control at least 15 minutes before the aircraft arrives at the designated approach fix.
- Release messages must be passed in a timely manner and include:
1. Aircraft identity, type, and SSR code (if applicable).
2. Point of departure.
3. Release point.
4. Estimated time and level at the holding facility, or arrival time and level if after arrival.
5. Expected approach time.
6. Contact point.
Controlled Airspace:
- Aircraft released to Approach Control must be within controlled or advisory airspace when the release becomes effective.
- All other aircraft at lower levels must also be released or have procedural separation provided.
- Released aircraft should not be levelled off or climbed above the level at the holding facility without coordination with Area Control.
Release Point:
- Unless approved by the CAA, the release point for aircraft released to Approach Control should be below FL195. If approved, MATS Part 2 must include details of the area and conditions for these procedures.
Approach Sequencing:
- When approach sequencing is in force at aerodromes within Classes A to F airspace, Area Control clears all aircraft to the holding facility with holding instructions and an expected approach time if appropriate.
Class G Airspace:
- Aircraft proceeding to an aerodrome in Class G airspace are cleared to leave controlled or advisory airspace by descent or on an appropriate track, with the acceptance level advised in the release message.
Alternative Holding Facilities:
- Area Control may clear an arriving aircraft to an alternative holding facility or visual holding point after coordinating with Approach Control.
What is the “Release Subject Your Discretion” (RSYD) procedure and when is it used?
The RSYD procedure allows outbound clearances that do not provide required separation from inbound or overflying aircraft, under the following conditions:
- The outbound clearance must be qualified with “Release subject your discretion” and include details of the conflicting traffic.
- The release message for the inbound aircraft or full details of the overflying traffic must have already been passed.
RSYD is used to expedite traffic when Approach Control can provide a more efficient resolution of the conflict than Area Control. The approach controller is responsible for ensuring required separation for outbound aircraft and resolving all conflicts or coordinating before transferring the aircraft to Area Control.
What is the procedure for issuing departure clearances when two aircraft wish to depart in quick succession?
When two aircraft wish to depart in quick succession, Approach Control may issue departure clearances to Aerodrome Control with a condition, such as a time delay (e.g., “Release subject [callsign] departure plus two minutes”). The Aerodrome Controller is responsible for applying this separation or informing the Approach Controller if it is not possible.
An ACC may also issue two clearances to an Approach Control unit, requesting that aerodrome separation is applied between the aircraft (e.g., “…. release subject [callsign]”). The second aircraft must be separated from the first departure before transfer of control, with separation either constant or increasing. If Approach Control cannot ensure this, they must inform the centre immediately to agree on a new course of action.
What is a “radar release” and when might Area Control use it?
A “radar release” is a procedure where Area Control expedites traffic by transferring control of arriving aircraft to Approach Control. The details of this procedure are found in Section 1, Chapter 6.
What are the responsibilities of Area Control regarding separation and ATS surveillance services?
- Separation Responsibility: Area Control is responsible for providing separation between aircraft operating in controlled or advisory airspace, based on airspace classification, aircraft flight rules, and ATC clearances.
- ATS Surveillance Services: The area within which ATS surveillance services are provided is determined by equipment coverage and may be further limited to areas defined in MATS Part 2.
- Provision of ATS in Other Airspace: Where authorized, Area Control may provide ATS in airspace normally managed by another control unit, either permanently or on a limited basis, with specific arrangements published in MATS Part 2.
How should separation be applied between an aircraft under Radar Control and known traffic outside PSR/SSR cover?
Separation between an aircraft under Radar Control and known traffic outside PSR/SSR cover should be applied as follows:
- Opposite Direction Traffic: Vertical separation must be provided at least 10 NM before the conflicting traffic is expected to enter PSR/SSR cover.
- Same Direction Traffic:
1. Proceeding into PSR/SSR cover: Vertical separation must be provided until the identified aircraft is at least 10 NM within the point where the conflicting traffic is expected to enter coverage.
2. Proceeding out of PSR/SSR cover: Vertical or other procedural separation must be established at least 10 NM before the aircraft is expected to leave coverage.
What should controllers do if an aircraft reports “abeam” instead of “over” an en-route reporting point?
Controllers must ensure that the aircraft is aware of its correct routing and that separation is not adversely affected. Aircraft should report “over” en-route reporting points as close as possible to the actual time of the event, except when being vectored.
When should a pilot make a position report to reduce RTF communication, and when should controllers instruct pilots to make position reports?
Pilots should make a position report:
- On the first transfer of communication from another ACC or sector (containing aircraft identification and flight level only; subsequent reports include position and time).
- On reaching the limit of the ATC clearance.
- When instructed by ATC.
Controllers should instruct pilots to make position reports:
- When the aircraft is outside ATS surveillance system cover.
- Before identification has been achieved.
- As detailed in MATS Part 2.