Section 4, Chapter 2 - Approach Control Procedures Flashcards
What are the responsibilities of the Approach Coordinator (APC) in Approach Control Procedures?
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.
What are the key responsibilities of the APC regarding coordination in Approach Control Procedures?
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.
How should VFR transit aircraft intending to route through the Aldergrove CTR be controlled?
- 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.
What instructions and clearances are given to VFR traffic wishing to transit the Aldergrove Control Zone and overfly the airfield?
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.
What are the procedures for VFR departures from the Aldergrove Control Zone?
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.
What is the procedure for issuing Special VFR departure clearances?
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.
What should Aldergrove ATC do for flights leaving Northern Ireland at night intending to use the Scottish FIR?
- Advise the appropriate sector at PC of the intentions of any such aircraft.
- Example: PAZT leaving CTR S/VFR to EGNH.
What procedures must be followed for VFR flights transiting between the EGPX FIR and EINN FIR?
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.
What are the procedures and phraseology for Runway 07 when in use during daylight hours?
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.”
What are the procedures for using a Non-Duty Runway (Non-Promulgated Duty Runway or Opposite End Approaches)?
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.
What actions must APC take when a runway is reduced in length?
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.
What actions must APC take when a runway is returned to full length?
Advise all inbound aircraft:
* Inform them that runway [xx] is operating full length.
Update Traffic Display:
* Remove the strip from their display.
What are the key points of the missed approach procedures?
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.
What actions must be taken during periods of runway closure?
- Place a “Runway xx Closed” strip in the center bay of the strip display.
- Deselect final approach track overlays.
What are the phases of radar failure and where can the checklists be found?
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.
What actions should controllers take during the initial phase of radar failure?
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.
What is the action list for APC during the initial phase of radar failure?
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.
What actions should be taken during the intermediate phase of radar failure to re-establish a known traffic environment?
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.
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?
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.
What assumption is made regarding radar serviceability in the context of non-radar procedures outlined in Para 2.8.6?
Assumption: Radar serviceability at Belfast City and Prestwick Centre until Para. 2.8.15.2.
What are the key points for strip management during non-radar procedures at EGAA?
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.
What is the separation between the BEL and MAGEE holding patterns?
The BEL and MAGEE holding patterns are separated from each other up to FL140.
What is the procedure for calculating and issuing Expected Approach Times (EATs)?
- 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.
What are the areas of responsibility during non-radar operations for Belfast Aldergrove APC and PC Antrim?
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.
