Section 4, Chapter 2 - Approach Control Procedures

Question 1

What are the responsibilities of the Approach Coordinator (APC) in Approach Control Procedures?

Answer 1

Co-ordination of IFR traffic:
* Arriving, departing, and over-flying with PC, EGAC, and ADC.
* Includes range checks and radar handovers when delegated by APR.
* Inform APR/RAD2 of all such co-ordination.

Coordination of VFR/SVFR traffic:
* With adjacent ATSUs and ADC.

Runway declaration:
* In consultation with APR and ADC, based on weather and navigational aids serviceability.

Aircraft emergencies:
* Coordinate with ADC and adjacent ATSUs/Agencies.
* Provide necessary information for emergency procedures and updates as available.

Delegation to ADC:
* Certain IFR separations or block delegation of airspace, e.g., SVFR circuits.
* ADC ATCO uses reduced separations as per MATS 1, Section 1 Chapter 3.

Information APC must ensure is available to ADC/APR/RAD2 and adjacent ATSUs:

• Runway in use at EGAA and notification of changes to PC/EGAC.
• Runway in use/serviceability status at EGAC.
• Notification of EGAC runway to PC.
• Serviceability of radio and navigational aids.
• Essential Aerodrome Information.
• Weather warnings, including LVPs.
• Activity states of relevant Danger Areas.
• Airspace Restrictions.
• Minimum Stack Level in Belfast TMA and Transition level on radar display.
• Notification of any flow control restrictions to GMC/ADC and EGAC.
• Keep EFPS display updated in conjunction with INT.
• Inform DEO and WM/DWM of any radio/navigational aids malfunctions reported by aircraft.

When APC is opened by INT:

• APC assumes immediate responsibilities delegated by INT.

Question 2

What are the key responsibilities of the APC regarding coordination in Approach Control Procedures?

Answer 2

Notify APR:

• Inform APR of any VFR/SVFR traffic that may affect aircraft receiving a Radar Service.

Coordinate Outbound Clearances:

• Coordinate outbound clearances with APR.
• Impose any necessary restrictions regarding VFR/SVFR traffic.
• Notify APR of these restrictions.

Coordinate Non-Standard Routeings:

• ADC must coordinate with APC/PC any non-standard routeings or changes to flight plan information.
• Coordinate routeings that would be contrary to the Standing Agreement between units.

Pass Departure Clearances:

• Include radar headings.
• Coordinate with the APR ATCO regarding outbound, inbound, or transit aircraft.

Question 3

How should VFR transit aircraft intending to route through the Aldergrove CTR be controlled?

Answer 3

• Control as per Paragraph 3.1.3 VFR Arrivals: Follow the guidelines outlined in this section for managing VFR transit aircraft.
• Transfer to ADC: Any transit aircraft overflying the airfield should be transferred to ADC.

Question 4

What instructions and clearances are given to VFR traffic wishing to transit the Aldergrove Control Zone and overfly the airfield?

Answer 4

For transit through Aldergrove Control Zone:

• QNH
• CTR entry clearance
• Routing instructions
• Coordination with ADC should be effected.

For overflying the airfield:

• QNH
• CTR entry clearance
• Clearance limit

Additional Notes:

• Aircraft joining from the east or southeast will normally be notified via Belfast City ATC.
• Aldergrove may issue a CTR joining clearance to Belfast City for them to pass on to the pilot.
• Coordination with ADC should occur in sufficient time to enable transfer of control before the clearance limit.

Question 5

What are the procedures for VFR departures from the Aldergrove Control Zone?

Answer 5

Refer to Section 3, Ch 3.1.2 VFR Departures.
ADC Responsibilities:
* Pass pertinent airborne times on VFR departures to APR.

Coordination Requirements:
* VFR departures may require coordination if a conflict exists with other traffic.
* APC may apply restrictions to the departure.
* Any VFR departure wishing to fly above 2000ft must be coordinated with APC.

Frequency Management:
* Departing VFR traffic will remain on the Approach Control frequency until clear of the Control Zone.

Question 6

What is the procedure for issuing Special VFR departure clearances?

Answer 6

Issued by Approach Control:
* In response to pilot requests.

Details Provided:
* Specify departure route.
* Specify maximum altitude.

Communication with Aerodrome Control:
* Individual clearances are issued to Aerodrome Control.

Question 7

What should Aldergrove ATC do for flights leaving Northern Ireland at night intending to use the Scottish FIR?

Answer 7

• Advise the appropriate sector at PC of the intentions of any such aircraft.
• Example: PAZT leaving CTR S/VFR to EGNH.

Question 8

What procedures must be followed for VFR flights transiting between the EGPX FIR and EINN FIR?

Answer 8

EGPX FIR to EINN FIR (East of BAMLI):

Notify Dublin:
* Tel No: +353 184 44 564.
* Details to be Passed:
* Callsign.
* Type.
* Altitude.
* FIR boundary estimate destination.
* Point of departure.

EGPX FIR to EINN FIR (West of BAMLI):

• Notify Scotland Lower Support Sector (ANT ASST):
• Ensure information, including position and estimate for FIR boundary, is passed for onward transmission.

EINN FIR to EGPX FIR (East of BAMLI):

• ACC Dublin Notification:
• Notify Aldergrove verbally of VFR flights intending to land or transit the Scottish FIR at or below 4000ft.
• Transfer of communications to Aldergrove Approach.

EINN FIR to EGPX FIR (West of BAMLI):

• Scotland Lower Support Sector:
• Pass details of relevant VFR flights to Aldergrove Radar.

Question 9

What are the procedures and phraseology for Runway 07 when in use during daylight hours?

Answer 9

ATIS Broadcast:

• Phraseology: “There is an airfield with a similar runway near to the final approach track at DME 3NM. Runway 07 at Belfast international airport is lighted.”

If any of the following conditions apply:

• The message is not being broadcast.
• The ATM is Out of Service.
• The AFDA and/or Approach path Monitor are unserviceable.
• An arriving IFR flight is on a Visual or VOR approach.

APC Phraseology when transferring to ADC:

• “[Callsign], caution Langford Lodge, contact Tower on 118.3.”

ADC Instruction to Inbound Aircraft:

• “Report the Runway lights in sight.”

Question 10

What are the procedures for using a Non-Duty Runway (Non-Promulgated Duty Runway or Opposite End Approaches)?

Answer 10

Applicability:

• Only for Category A aircraft or aircraft carrying out ILS/AGL flight checks.
• Not applicable to cross runway operations.

For Arrival or Departure in Other Circumstances:

• Complete a full runway change as per unit checklist ATC/FORM/203.
• Radar Responsibilities:
• Hold arrivals at the BEL.
• Do not permit inbound aircraft to establish on the FAT until the last departure is airborne and 5NM or greater from the FAT.
• Provide vertical separation between the arrival and departure until the departure is:
• Airborne.
• Identified and radar can assure a minimum of 5NM lateral separation.

Note:
Sufficient notice must be given to enable the checklist to be completed when coordinating a runway change.

Question 11

What actions must APC take when a runway is reduced in length?

Answer 11

Receive Pilot Acknowledgement:

• Confirm receipt of the following message via RTF: “Confirm that you are aware that runway xx is operating at reduced distances.”

Traffic Display Update:

• Place a strip in the traffic display before the aircraft reaches 15NM from touchdown.
• The blank right-hand side of the strip is a text field where appropriate information can be displayed.

Question 12

What actions must APC take when a runway is returned to full length?

Answer 12

Advise all inbound aircraft:
* Inform them that runway [xx] is operating full length.

Update Traffic Display:
* Remove the strip from their display.

Question 13

What are the key points of the missed approach procedures?

Answer 13

Standard Procedures:

• Detailed on approach charts, including altitude.
• ATC may deviate from these as necessitated by the prevailing situation.

Wind Shear Considerations:

• Aircraft may use maximum thrust and risk exceeding the cleared level.

If missed approach is due to wind shear:
* ADC must immediately coordinate with INT/FIN to ensure separation.
* INT/FIN must ensure enhanced vertical separation against missed approach profiles where wind shear is known to exist.

Question 14

What actions must be taken during periods of runway closure?

Answer 14

• Place a “Runway xx Closed” strip in the center bay of the strip display.
• Deselect final approach track overlays.

Question 15

What are the phases of radar failure and where can the checklists be found?

Answer 15

Phases of Radar Failure:

• Initial
• Intermediate
• Final
  ~~~~~
• Application: The same phases may apply to a planned outage but are more controlled.
• Checklists: Available in the ‘Checklists’ folders held in VCR and APC Room.

Question 16

What actions should controllers take during the initial phase of radar failure?

Answer 16

Inform Aircraft:

• Radar failure.
• Commencement of non-radar procedures (when practical).

Provide Non-Radar Separations:

• As soon as possible.
• Use emergency separation (500ft) with essential traffic information if standard separation cannot be immediately achieved (MATS Part 1, Section 1, Chapter 6).

Stop Departures:

• From EGAA and EGAC.
• Use EFPS ‘Stop All’ function or a phone call for EGAA.
• Use a phone call for EGAC.

Aircraft on Final Approach:

• May continue and land if already established (instrument or visual).

Subsequent Aircraft (Outside EGAC Hours):

• May continue approach visually as per MATS Part 1 with reduced separation in the vicinity of an aerodrome.

Aircraft Outside CAS with Surveillance Service:

• Amend service to Basic Service.
• Inform pilots, provide time check and expected CTR entry clearance if appropriate.

(S)VFR Aircraft Within the CTR:

• Inform them of the change of service to Approach Control.

(S)VFR Aircraft Cleared into the CTR (Not Inside CAS):

• Cancel the clearance.

Remember:

• Other units with radar may be able to offer assistance.

Question 17

What is the action list for APC during the initial phase of radar failure?

Answer 17

APC Responsibilities:

Inform ADC:

• Confirm all departures require start-up approval from APC, regardless of flight rules.

Inform:

• EGAC: Suspension of departures.
• PC: Notify radar failure, cancel the standing agreement.
• PC Antrim advises PC West Coast.
• PC stops transferring aircraft until APC declares readiness.
• PC Ops Supervisor: Instigate flow control measures.
• ADC: When flow control measures are complete.

Amend Strip Display:

• Reflect non-radar procedures (as per Para 2.8.2).
• Create ‘MAGEE’ and ‘BEL’ hold strips from Popup 885 “HOLD”.

ADC ATCO Responsibilities:

• Annotate the log book.
• Broadcast appropriate message on ATIS as soon as possible.

Inform:

• DEO
• BIAL
• Military operations & PSNI (regarding movement restrictions)
• General Manager

Publish a NOTAM:

• As soon as practicable.

Additional Note:
* If DEO is on call and call-out is outside the agreement, inform Manager Engineering first, who will handle engineer attendance.

Question 18

What actions should be taken during the intermediate phase of radar failure to re-establish a known traffic environment?

Answer 18

Inbound Traffic Management:

• Coordinate with PC: Transfer inbound traffic at the point of radar failure back to PC. PC retains aircraft until coordinated with EGAA.
• Route Traffic to Holding Fixes: Retained by EGAA to the most appropriate holding fix (BEL VOR or MAGEE).
• Inform Aircraft: Advise each inbound aircraft of the expected instrument approach procedure and provide an EAT when available.

Coordination with EGAC:

• EGAA coordinates inbound aircraft currently on frequency and transfers to Belfast Radar.

Traffic Outside CAS:

• Coordinate with PC West Coast and transfer if appropriate.

S/VFR Traffic Management:

• Within CAS: Provide a clearance limit and coordinate with ADC.
• Outside CAS: Instruct to remain outside until a clearance to enter CAS can be given.

Begin Calculation and Issue of EATs:

• Ensure all inbound aircraft receive their EATs.

Confirmation:

• EGAA APC confirms adequate separation exists and that all above measures have been completed.

Question 19

What are the actions and coordination required during the final phase of radar failure to operate a known traffic environment and start non-radar procedures?

Answer 19

EGAA APC Coordination:

• With ADC: Agree on start-up arrangements.
• With PC: Ascertain pending traffic and confirm minimum stack level.
• With EGAC: Confirm commencement of non-radar procedures and that EGAC may commence direct operating procedures with PC.

New Agreed Levels Between EGAA and PC:

• PC Antrim: Assumes responsibility for traffic at and above Minimum Stack Level (MSL).
• EGAA APC: Climbs outbound aircraft to altitude 6000ft (Aldergrove QNH).
• PC: Descends inbounds to Minimum Stack Level.
• PC: Coordinates all EGAC traffic directly with EGAC.

EGAC Radar Responsibilities:

• Use Mode S to identify EGAA traffic.
• Phone either EGAA or PC to determine the identity of unidentified aircraft (e.g., aircraft with incorrect Flight Identification set).
• Separate EGAC traffic from all EGAA arrivals and departures.

Additional Considerations:

• Continuation of (S)VFR Flights: May be permitted subject to controller workload.
• Emergency Scenario: All movements suspended until the scenario is resolved sufficiently to permit continuation of other aircraft movements.

Question 20

What assumption is made regarding radar serviceability in the context of non-radar procedures outlined in Para 2.8.6?

Answer 20

Assumption: Radar serviceability at Belfast City and Prestwick Centre until Para. 2.8.15.2.

Question 21

What are the key points for strip management during non-radar procedures at EGAA?

Answer 21

Report Requests:

• Initial Request: Noted in remarks (e.g., “BEL10” for “c/s report passing BEL10DME”).
• Confirmation: Appended with a ‘#’ (e.g., “BEL10#”).

Strip Management:

Pending Overflights (EGAC Arrivals/Departures):

• Appear in the top-left bay.
• EGAC may STEAL live estimate strips; EGAA retains strips for conflict management.
• EGAA removes EGAC inbound strips 10 minutes after transfer of control, unless a missed approach is suspected.
• EGAC retains outbound strips until transferred to PC unless coordinated otherwise.

Pending Departures:

• Appear in the bottom-left bay.
• Moved to the Outbound bay when appropriate.

Pending Arrivals:

• Appear in the top-right bay.
• Populate as normal, convert to HOLD strip format.
• Update with entry time when aircraft reports established in the hold (“IN” data field).
• Move under the BEL designator after completion.

Conflict Management:

• EGAA inbound strips not progressed below IFR outbound until conflict resolved.
• Ensure final level report received and recorded before transfer to ADC.

Retaining Strips:

• Retain IFR arrival strips in BEL bay until landing confirmation.
• EGAA to EGAC Strip

Coordination:

• Normally not shown unless coordinated/requested.

Transferred Aircraft:

• Place strips in ‘Transferred to’ bay (bottom right) and discard when appropriate.

Bay Assignments:

• MAGEE Bay (top-middle): For EGAC inbounds.
• BEL Bay (middle): For EGAA inbounds.
• Pink Strips: Placed based on relevance to movements (IFR/VFR).
• Dynamic 2: Used for UKFIS.

Question 22

What is the separation between the BEL and MAGEE holding patterns?

Answer 22

The BEL and MAGEE holding patterns are separated from each other up to FL140.

Question 23

What is the procedure for calculating and issuing Expected Approach Times (EATs)?

Answer 23

• Average Elapsed Time: Use 12 minutes as the average time for an aircraft to complete an approach from leaving the holding facility.
• Update EATs: Adjust the EAT as each aircraft leaves the holding fix.
• Notify Pilots: Inform pilots if the EAT changes by ± 3 minutes.
• Issuance of EATs:
• Allocate and issue EATs as soon as practicable.
• Coordinate through PC Antrim if necessary.

Question 24

What are the areas of responsibility during non-radar operations for Belfast Aldergrove APC and PC Antrim?

Answer 24

Belfast Aldergrove APC:

• Retains overall responsibility for the Belfast TMA and delegated airspace below MSL (Minimum Stack Level).
• May delegate responsibility for aircraft within this airspace to PC or EGAC on an individual basis.

PC Antrim:

• Assumes responsibility for MSL and above.
• Responsible for all overflights of the Belfast TMA at or above MSL.

Question 25

What is the declared runway in use at EGAA during non-radar operations?

Answer 25

The declared runway in use at EGAA during non-radar operations shall be the preferred arrival runway, normally Runway 25.

Question 26

What are the rules for cross runway operations during non-radar procedures?

Answer 26

General Rule: Cross runway operations are not normally permitted.

Extreme Circumstances:

• Aircraft may depart from a cross runway if no aircraft is allowed to commence an approach until APC ensures separation with the BEL hold (coordinate with PC Antrim if necessary).

Arrivals to a Non-Declared Runway:

• Allowed to commence an approach only once the previous arriving aircraft has landed.

Question 27

What are the procedures for start-ups and ATC route clearances for departures from EGAA during non-radar operations?

Answer 27

Start-Up Approval:

• All departures require start-up approval by Aldergrove APC, regardless of flight rules.

Standard Enroute Clearances:

• Issued by ADC to altitude 5000ft Aldergrove QNH prior to pushback.

Initial Routing:

• From Rwys 17 or 25: BEL VOR 185°
• From Rwys 07 or 35: BEL VOR 053°
• This routing is relayed to the pilot on start-up for full pre-departure briefing.

Strip Management:

• ADC controller types ‘R185’ or ‘R053’ into the HDG box of the strip.
• Populate the level box when an ATC clearance is issued.

Question 28

What are the conditions for deemed separation between inbound and outbound aircraft during non-radar operations at EGAA?

Answer 28

Inbound Aircraft:

• Established on the outbound radial from the holding fix.
• Reported at BEL DME 5NM.
• Separated from a departure on the same runway onto BEL VOR 185°/053° radials (as appropriate).

Outbound Aircraft:

• On the BEL VOR 053°/185° radials are separated from the BEL VOR holding pattern at 10 DME.

Controllers’ Awareness:

• Ascertain distance from touchdown information to assist situational awareness.
• Ensure outbound aircraft have commenced take-off roll by the time the inbound reports at 6 DME.
• Subsequent departures shall be separated vertically or as per MATS Part 1.

Question 29

What are the procedures for handling EGAA outbound aircraft during non-radar operations?

Answer 29

Requesting Departure Release:

• EGAA ADC requests a departure release from APC using standard EFPS methodology.
• Standard IFR clearances will be on the pre-populated radial and 5A level.
• If APC wants to amend the release to non-standard, they will coordinate the amendment with ADC before amending the strip.

Strip Marking:

• Demonstrate aircraft has established on the appropriate radial (e.g., ‘E#’).
• Mark aircraft report of reaching BEL DME 10NM (e.g., ‘10D#’).

Agreed Outbound Level:

• Altitude 6000ft (Aldergrove QNH).

Transfer to PC:

• Traffic may be transferred before BEL DME 10NM with confirmation from PC that the outbound aircraft is clear of the BEL Hold.
• PC shall not turn an aircraft off the outbound radial until it is at or above 6000ft (Aldergrove QNH).
• All EGAA outbounds are transferred to PC Antrim unless otherwise coordinated.

Coordination for Climb:

• If PC cannot see traffic at 6000ft (Aldergrove QNH), EGAA will coordinate the climb.
• EGAA may only climb to the coordinated level once the aircraft reports 10 DME from BEL.

Question 30

What are the procedures for handling EGAC outbound aircraft during non-radar operations?

Answer 30

Coordination:

• Coordinate individual departures with PC Antrim/West Coast as appropriate.
• Maintain 5NM and/or 1000ft+ separation from all traffic not under their control.

Notification:

• Inform EGAA ATC when such aircraft are airborne.

Question 31

What are the procedures for handling Belfast TMA inbounds during non-radar operations?

Answer 31

Approach Procedures:

• Published approach procedures are detailed in UK AIP AD2 EGAA 8-1 to 8-13.
• RNP is not available during non-radar operations.

MSL Coordination:

• EGAA informs PC when MSL is available.
• PC Antrim/West Coast Sectors descend EGAA inbound aircraft to MSL at BEL VOR.

EGAC Inbounds:

• Inbound traffic to EGAC is individually coordinated with EGAC Radar.

Conflict Resolution:

• PC sectors coordinate to resolve any inbound TMA conflicts before transferring to either APC Unit.

Question 32

What are the detailed procedures for handling EGAA inbounds during non-radar operations?

Answer 32

MSL Coordination:

• EGAA APC must keep PC Antrim updated with the Minimum Stack Level (MSL).
• Inform PC promptly of any changes in MSL, especially due to significant QNH changes.
• Do not pass new QNH to aircraft until coordination with PC is confirmed.

Vertical Order and EATs:

• PC advises EGAA of the vertical order of inbound aircraft entering the hold.
• EGAA advises Estimated Approach Times (EATs) for each inbound when available.

Release of Traffic:

• PC Antrim releases EGAA traffic to EGAA APC once established in the BEL hold or entry procedure, descending to, or level at, MSL unless otherwise coordinated.
• EGAC radar informed of the type of approach and assumes all aircraft are on the same type unless otherwise notified.

EFPS Notifications:

• APC gives ADC a ‘Beacon Outbound’ (BO#) check when the inbound aircraft leaves the BEL hold.
• Provide a 10nm range check (10#) or base turn complete check (BTC#) for situational awareness.
• ADC advises APC when inbound aircraft have landed.

Subsequent Inbounds:

• Cleared for approach, descending not below 4000ft until:
• The preceding aircraft has landed.
• Any conflict with departing aircraft is resolved.

Coordination with PC:

• If PC cannot retain radar contact with traffic to MSL, they may coordinate a release of traffic at a higher level (not greater than FL100).

Additional Requests:

• ADC may request inbound aircraft to report at 6 DME (IAG or BEL equivalent), annotated on the strip (e.g., 6D#).

Question 33

What are the procedures for handling EGAC inbounds during non-radar operations?

Answer 33

Transfer of Aircraft:

• PC transfers the aircraft directly to EGAC Radar following coordination.

Separation Responsibility:

• PC is responsible for all separation against inbound traffic prior to the point of transfer.
• EGAC Radar assumes responsibility for maintaining 5NM+/1000ft+ separation between any aircraft under their control and all EGAA traffic.

Question 34

What is the inbound flow control rate for EGAA inbound traffic during non-radar operations?

Answer 34

Inbound flow control is initiated for EGAA inbound traffic at a maximum rate of 5 per hour.

Question 35

What procedures should be followed if EGAC Radar is out of service (O.O.S.) during non-radar operations?

Answer 35

Routing and Approaches:

• EGAC arrivals routed to MAGEE hold.
• Simultaneous approaches to EGAA & EGAC are not permitted.
• EGAA issues EATs to aircraft in MAGEE and BEL holds, via PC if appropriate.

Releases and Departures:

• EGAA APC issues releases to EGAC APC by phone call.
• Only one aircraft at a time allowed to depart from either airfield; transfer level is 6000ft.
• EGAC departures route via the BEL 135° radial, regardless of flight planned route.

PC Responsibilities:

• Retain all traffic in BEL & MAGEE holds above MSL.
• Issue standard release messages on aircraft descending to MSL to EGAA APC for EGAC inbound aircraft.

Deemers:

• No deemers between outbounds except departures established on the BEL 135° radial are separated from BEL & MAGEE holds.

Approaches to EGAC:

• Details found in UK AIP AD2 EGAC 8-1 to 8-6.

Flow Control:

• Inbound flow control initiated for TMA inbound traffic with a recommended rate of 5 per hour.
• EGAC ATC, in conjunction with EGAA WM/DWM, determines the flow rate they can accept, considering forecast traffic, weather conditions, and loss of EGAA radar.

Question 36

What are the steps for returning to service after radar becomes serviceable at EGAA?

Answer 36

Initial Actions by APC:

• Inform PC Antrim and EGAC ATC that interim arrangements are terminated.
• Coordinate individual EGAC traffic with EGAA APC.
• EGAC waits for handovers via EFPS, no longer “STEAL” live EGAC estimate strips.
• Set radar defaults as per MATS 2.
• Identify traffic on frequency and traffic under control of other agencies with caution to avoid misidentification.
• Inform traffic of alteration of service.
• Advise ADC of cessation of start-up requests.
• Inform GS Scotland Lower.

Subsequent Actions by APC:

• Open FIN position if required.
• Inform PC that the standing agreement is re-instated and agree on coordination requirements regarding airborne traffic.

Actions by ADC:

• Inform:
• BIAL
• Military operations
• PSNI
• General Manager
• Update ATIS.
• Cancel the NOTAM.
• Annotate the log book.