Section 4, Chapter 4 - Interface Agreements Flashcards
What controlled airspace is delegated to Aldergrove at FL90 and below, and what UK Flight Information Services (UKFIS) responsibilities does Aldergrove have?
Delegated Airspace to Aldergrove at FL90 and Below:
- The Belfast TMA
- P600 between ROTEV and BLACA
- N34 between NEVRI and BELZU
- Below P620 between BLACA and NIMAT
- Controlled airspace below P620 between BLACA and NIMAT
UKFIS Responsibilities:
- Aldergrove shall provide UKFIS to traffic operating below N34 and P600 when Aldergrove Radar is serviceable.
- Aldergrove will not provide UKFIS to aircraft below P620.
What are the agreed levels for the transfer of traffic using the ATS route system between Scottish Control (PC) and Aldergrove?
Belfast TMA Arrivals:
- Agreed level is FL100.
Belfast TMA Departures:
- Agreed level is FL90.
Traffic Cruising Below FL100:
- When Aldergrove accepts an estimate for traffic cruising below FL100, this level becomes the agreed arrival level.
Departures Filed Below FL90:
- When Belfast TMA departures have filed cruising levels below FL90, this level becomes the agreed departure level.
ATS Route L10 Traffic:
- All traffic cruising on ATS Route L10 at FL90 or below shall be transferred to PC.
Transfer Restrictions:
- Traffic shall not be transferred directly to EGNS Radar if requested by PC, as EGNS does not have the appropriate level of RTF or Radar cover.
What are the agreed routes for traffic inbound to or outbound from Aldergrove and Belfast City airports, and how are they determined?
Agreed Routes:
* Traffic shall be routed according to tables related to aircraft navigation equipment.
RNP 1 Routes:
* Aircraft equipped to use RNP 1 related M and Q routes will flight plan accordingly.
Flight Plan Rejection:
* If an aircraft flight plans to use a route for which they are not equipped, the plan will be rejected.
What are the agreed routes for arrivals to Aldergrove and Belfast City airports based on their approach direction and aircraft navigation equipment?
Approach from NE:
- Via: P600
- Route: BLACA - BELZU / MAGEE
Approach from E FIR:
- Via: BLACA/TMA Boundary
- Route: BELZU / MAGEE
Approach from SE (RNP 5):
- Via: L10 (FL75+)
- Route: IOM - NELBO - BELZU / MAGEE
- Via: L10 (Below FL75)
- Route: IOM - RINGA - BELZU / MAGEE
- Via: UP6/L46 (RNP 5)
- Route: REMSI - MASOP - NELBO - BELZU / MAGEE
Approach from SE (RNP 1):
- Via: M146 (EGAA arr. - FL255, EGAC arr. FL195-)
- Route: PEPEG - ROBOP - IPSET - BELZU / MAGEE
- Via: M147 (EGAA arr. FL255+)
- Route: NOPKI - MATUT - ROBOP - IPSET - BELZU
- Via: M148 (EGAC arr. +FL195)
- Route: MASOP - IDGAS - IBTES - LIMKA - MAGEE
Approach from S:
- Via: N34
- Route: NEVRI - ABSUN - BELZU / MAGEE
Approach from SW, W, NW, N FIR:
- Via: TMA Boundary
- Route: Direct to BELZU / MAGEE
What are the agreed routes for departures from Aldergrove and Belfast City airports based on direction and aircraft navigation equipment?
Departing to SE (RNP 5):
- Via: L603 / L15 (RNP 5 FL150+)
- Route: LISBO / DUFFY - PEPOD - MAKUX
- Via: L603 / L15 (FL90 - FL140)
- Route: LISBO / DUFFY - PEPOD - IOM
- Via: L10 (FL80-)
- Route: LISBO / DUFFY - RINGA - SLYDA - IOM
Departing to SE (RNP 1):
- Via: Q38 (Belfast TMA RNP1 departures RFL285-)
- Route: LISBO / DUFFY - PEPOD - VAKPO - MAKUX - SOSIM
- Via: Q39 (Belfast TMA RNP1 departures RFL285+)
- Route: LISBO / DUFFY - RINGA - BABGU - ETIGA - TIMIS - INKOB
Departing to S:
- Via: P620
- Route: LISBO / DUFFY - NUMPI - NIMAT - DUB
Departing to N:
- Via: P600
- Route: LISBO / DUFFY - BLACA - TRN
Special Requirements for Departures via UL15/Q39 with a Requested Level of FL290 or Above:
Crossing Requirement:
- Aircraft must cross SOSIM/INKOB at FL290 or above.
Speed Restrictions:
Jet Traffic with MTOW > 35,000 kg:
* Max 250kt IAS until FL100, then Max 290kt IAS until FL250.
Jet Traffic with MTOW < 35,000 kg and all non-jet traffic:
* Max 250kt IAS until above FL250.
Unable to Reach FL290 by SOSIM/INKOB:
- Aircraft must advise EGAA/EGAC as appropriate prior to pushback, giving the anticipated flight level at SOSIM/INKOB.
- Once the departure strip is moved into the pushback bay, the Antrim Sector controller must be informed of the aircraft’s anticipated flight level at SOSIM/INKOB.
What are the conditions for silent handovers between the Antrim sector and Aldergrove?
Agreed Route and Level:
- Traffic is following the agreed route and is at or climbing/descending to the agreed level.
Distance and Altitude:
- Traffic inside CAS is within 60NM of the ARP and below FL195 (frequency 133.125 available).
- Traffic outside CAS is within 40NM of the ARP.
Spacing of Successive Arrivals and Departures:
- 10NM: Constant or increasing, between aircraft in trail.
- 5NM: Constant or increasing, between aircraft on parallel or diverging headings, following the general direction of the appropriate arrival or departure route.
- Deemed Separated Parallel Routes: Aircraft on these routes are deemed separated.
Previously Transferred Traffic:
- The transferring unit must consider previously transferred traffic.
Hazard Management:
- If the Antrim Controller considers that aircraft inbound via BLACA may constitute a hazard to aircraft routing inbound via NELBO, ROBOP, or LIMKA, they shall apply vertical separation and provide a reduced handover to Aldergrove.
Notes:
Aircraft established on M147/148 or M146/Q39 are deemed separated.
Traffic routing via Q38/39 is not deemed separated until both aircraft are established on those routes.
Coordination is required if the spacing conditions (a or b) cannot be complied with.
What are the procedures for the transfer of control for arriving and departing traffic between Aldergrove and PC?
Transfer of Arriving Traffic:
- Must be completed by BLACA, NELBO, ABSUN, ROBOP, or LIMKA as appropriate.
Transfer of Departing Traffic:
- Must be completed by BLACA or before crossing a line between NEVRI and RINGA as appropriate.
Conditions for Transfer of Control:
- Transfer of control is coincident with the transfer of communications, provided:
- The receiving unit continues the flight in the same general direction and does not alter altitude while still in the airspace of the offering unit.
- Any potential traffic conflicts within the offering sector’s airspace are resolved before the transfer of communications.
Longitudinal Separation:
If 10NM constant or increasing:
* EGAA Radar should route departures on their own navigation according to their flight plan.
* Such traffic may be turned by Antrim by no more than 20° on transfer of communications.
If less than 10NM:
* EGAA Radar shall position departures on a tactical heading to remain south of the radar buffer, ensuring PC can keep the aircraft within CAS after transfer.
Restrictions on Changing Radar Heading by PC:
- PC shall not change the radar heading, unless verbal coordination occurs, until the aircraft:
- Is FL100 or above, or
- Has passed BLACA or crossed a line between NEVRI and RINGA.
- Aldergrove may not turn arrivals via NELBO, ROBOP, or LIMKA to route above the Radar Buffer Zone.
PSNI Operations:
- PC controllers may not alter the assigned route/heading of outbound traffic, without coordination, until the aircraft is above FL110.
Responsibility for Separation:
- If Aldergrove descends arrivals below the agreed level, it is their responsibility to provide separation against departures already transferred to PC.
- If PC climbs departures above the agreed level, it is their responsibility to provide separation against arrivals already transferred to Aldergrove.
- When an aircraft has been transferred to PC, APR must not assume that the aircraft will be given continuous climb by PC on first contact.
What are the conditions for the transfer of communication from an ACC to a civil Approach or military ATC terminal unit?
Transfer of Control:
- Shall not take place at or above FL195 unless specifically authorized by the CAA.
Transfer of Communications:
- May take place above FL195.
Frequency Unavailability:
- When Aldergrove frequency 133.125MHz is not available, traffic shall not be transferred before BEL D.M.E. 40NM.
What are the procedures for traffic positioning in relation to the Radar Buffer Zone?
Radar Buffer Zone:
* Established following the L10 centerline, 6NM long, 5NM wide, from BABGU to 2.5NM NW of SLYDA, at FL90 and FL100.
* Antrim and Aldergrove controllers shall not allow traffic to penetrate the Buffer Zone without prior coordination.
Antrim Responsibilities:
- Position inbound traffic according to the flight-planned routing unless requested otherwise by Aldergrove.
- When the EGAA/EGAC runway combination is 25/04, position EGAC arrivals south of EGAA arrivals.
Aldergrove Responsibilities:
- Endeavor to position outbound traffic according to the flight-planned routing.
- If conflictions arise due to limited TMA airspace, Aldergrove controllers may transfer outbound traffic on headings to remain south of the radar buffer.
- It is then incumbent on Antrim to position the traffic according to the planned route.
What phraseology is used for a reduced handover when the conditions for a silent handover cannot be met?
Phraseology:
* “[Callsign] descending to level”.
What are the procedures for handling overflying traffic southbound from BLACA at FL80 or below?
Routing Instructions:
- APR, following coordination with Antrim Sector, will instruct the aircraft to route BLACA - RINGA - NIMAT.
Passing Details:
- Details of all overflying traffic at or below FL100 must be passed to Aldergrove.
- The estimate message should be for BELZU (or abeam that position), BLACA, or ROTEV as appropriate.
- Provide APR at least 15 minutes notice whenever possible.
Radar Handover:
- Subject to a radar handover with Aldergrove at or before the lateral boundary of the delegated area.
- APR will not change the level or squawk of this traffic.
Transfer Back to Antrim:
- Traffic will be transferred back to Antrim sector at or before the lateral boundary of the delegated area.
What are the procedures for handling military traffic requesting entry to Aldergrove and outbound military OAT traffic?
Inbound Military Traffic as GAT:
- Route via IOM VOR.
- The London (Military) controller will request ATS Route L10 joining clearance from Antrim Sector.
Outbound Military OAT Traffic:
- Must remain clear of PC airspace and contact London Military.
- If aircraft wish to transit through PC airspace, they must file a full flight plan.
What are the coordination procedures for IFR departures from Aldergrove to the FIR?
VFR Arrivals and Departures:
Subject to individual coordination.
IFR Departures:
Departures via Antrim Sector:
- East of the western edges of the Strangford CTA and the Belfast TMA above FL55, and if cruising level is below FL090.
Departures into the West Coast Sector:
- West of the western edges of the Strangford CTA and the Belfast TMA.
- Aldergrove shall allocate a maximum of FL90 to FIR departures from Belfast TMA airfields.
- If Aldergrove requests climb coordination from West Coast Sector, any climb instruction above FL90 before the TMA boundary must be coordinated directly with Antrim Sector (unless the two sectors are bandboxed).
- Aldergrove will provide a departure warning and airborne time for such traffic to be transferred to West Coast.
Departures into PC FISO Sector:
- East of the western edges of P600 and east of the Belfast TMA, FL55 and below.
What are the coordination procedures for IFR arrivals from the FIR to Aldergrove?
General Coordination:
* PC shall coordinate FIR arrivals, giving at least 15 minutes notice whenever possible.
From the FIR into Antrim Sector:
Arrivals at FL100 or Above:
- Subject to the agreed level and routing procedures as detailed in section 4.1.2.
- Shall be transferred in accordance with silent handover procedures, descending to FL100.
- Antrim shall clear such arrivals to join CAS.
Arrivals Below FL100:
- Antrim shall coordinate a joining clearance with Aldergrove and issue it to the aircraft.
From the West Coast Sector:
Level Coordination:
* West Coast shall coordinate a level with Aldergrove for Belfast TMA arrivals.
* West Coast shall transfer traffic when clear of confliction and within 40nm of EGAA to enable Aldergrove to issue a CAS joining clearance in a timely manner.
* Aldergrove will ensure that such traffic crosses the Belfast TMA boundary at or below FL90, unless coordinated with Antrim.
From PC FISO Sector:
Estimate and Clearance:
* The FISO (A) will normally pass an estimate on known traffic to Aldergrove.
* Aldergrove Radar may issue a joining clearance which the FISO (A) should relay, or may request that the aircraft contacts Aldergrove Radar directly for a joining clearance.
What are the procedures for handling police aircraft operating at FL100 in the Belfast TMA and P600?
Identification and Validation:
- APR shall identify, validate, and verify the Mode A and C of the police aircraft and confirm the type of service being provided.
Request Clearance:
- APR shall advise PC Antrim Sector of the requirement for use of FL100 and request clearance for the flight at that level.
- Provide details of the callsign, aircraft type, and squawk.
Coordination Procedures:
Belfast TMA Arrivals:
* Descended to FL110 by Antrim Sector.
Belfast TMA Departures:
* Climbed to FL90 by APR and transferred clean of the police aircraft (lateral separation of 5NM constant or increasing).
Higher Climb for Departures:
* May be coordinated on an individual basis as required, still ensuring the traffic is transferred clean of the police aircraft (vertical separation of 1000ft or lateral separation of 5NM constant or increasing).
Cruising Levels Coordination:
- Traffic arriving and departing the Belfast TMA at or below FL90 shall continue to be coordinated at their cruising levels as per the Standing Agreement.
Completion of Police Aircraft Detail:
- When the police aircraft has completed the detail and descended below FL90, APR shall advise PC Antrim Sector, and all parties will revert to the Standing Agreement.
What are the procedures for traffic operating outside the Belfast TMA within the West Coast Sector?
Identification and Validation:
- Traffic in the FIR within West Coast Sector wearing an Aldergrove Radar squawk (7031-7047, excluding 7045 Listening) may be deemed identified, validated, and verified by PC.
- Assumed to be operating not above FL85 VFR unless otherwise advised by Aldergrove.
- West Coast shall coordinate as required against such aircraft.
Observation and Reporting:
- Aldergrove shall advise West Coast if an aircraft is observed using a local code but not in contact with them.
IFR Departures:
- IFR departures from Aldergrove will be transferred to PC sectors with 5nm and 1,000ft separation from these squawks.
What are the coordination procedures for traffic affecting EGAE instrument approach areas?
Traffic Routing:
- All traffic operating at or below 3000ft intending to route North or North West of the Belfast TMA that is likely to affect EGAE instrument approach areas should be coordinated with and/or transferred to EGAE in a timely manner.
Operating Hours:
- EGAE operating hours are NOTAMed and can be found on the daily nav warnings.
- EGAE will telephone EGAA RAD to advise when opening and closing.
EFPS Display:
- The “EGAE OPEN” info strip shall be placed into the INT EFPS display when EGAE advises they are open and removed when they advise they are closed.
What are the departure routings for IFR aircraft entering the West Coast Sector?
- DEGOS: VF073
- ERNAN: VF108
- NIPIT: VF053
- MOLAK: VF041
- NIBOG: VF148
- LUTOV: VF034
- KUGUR: VF147
- APSOV: VF024
- MIMKU: VF146
- AMLAD: VF105
- IBROD: VF137
- GOMUP: VF059
- ERAKA: VF060
- BALIX: VF061
- ATSIX: VF062
- STN: VF063
- LUSEN: VF260
- ORTAV: VF267
- ADODO: VF279
- ETILO: VF289
What is the delegated airspace to Belfast City Airport and its coordination requirements with Aldergrove?
Delegated Airspace:
- The airspace between 2,000ft and 3,000ft above Belfast City’s Control Zone and CTAs 1 and 2 is delegated to EGAC during the airport’s hours of opening.
Coordination with Aldergrove:
- Due to the proximity to the let down area for Runway 25 at Aldergrove, Belfast City must ensure all aircraft operating NW of the runway centerline above 2000ft are identified to Aldergrove, which can be achieved via EFPS.
- Belfast City must coordinate any traffic they intend to position west of their CTR/CTA above 3,000’.
What are the conditions for EGAC to clear aircraft into the delegated portion of the Aldergrove CTR, and what are the coordination requirements?
Delegated Portion:
- The segment of the Aldergrove CTR between 544000N 055720W and 543210N 0060350W is delegated to EGAC up to 2000ft during EGAC hours of opening.
- A map overlay is available at AERON>AC_CORD and shall be displayed during EGAC hours of opening.
Conditions for Clearing Aircraft:
- The aircraft must be VFR.
- The maximum altitude allowed is 2000ft.
Coordination Requirements:
- EGAC can clear aircraft into the delegated portion without prior coordination with Aldergrove.
- EGAC shall show the EFPS of traffic in the delegated airspace to EGAA and annotate “DA” in the remarks box.
What are the conditions and procedures for EGAA vectoring EGAC aircraft to final approach for an ILS approach?
Service Limitation:
- An ATCO providing a RiT service may not use this procedure.
Recording:
- Instances of EGAA Radar vectoring EGAC inbounds for an ILS approach must be recorded on ATC/FORM/221.
Coordination:
- The EGAA WM and EGAC Supervisor must coordinate an agreed transition point or time for EGAA to commence vectoring EGAC inbounds for an instrument approach.
Range Checks:
- Necessary only if EGAC Radar or ATM is unserviceable. In such cases, EGAA must pass two checks for each inbound, with the final check passed between 10-15nm from touchdown.
Visual Approaches:
- EGAA ATCOs are not permitted to authorize visual approaches to EGAC.
Traffic Priority:
- Priority order: EGAA traffic, the DF as a whole, then additional sequencing for EGAC. If unmanageable, EGAC traffic should be held, and a non-radar service provided by EGAC approach, with handover at 4A in the MAGEE / HB hold. EGAC is responsible for issuing EATs.
Manageable Workload:
- If workload is within manageable limits, ATCOs should consider opening a dedicated position using a dedicated frequency (120.905).
Vectoring Conditions:
- Aircraft must intercept the procedure at not less than 10nm from touchdown and at not less than 3000ft.
- DOC for 04 and 22 ILS: Glidepath 10 DME, Localiser 25 DME.
- Instruct aircraft: “when inside 10 DME descend on the glidepath.”
- Caution: Minimum terrain safe level is 4000’ (Runway 22) and 3500’ (Runway 04).
Spacing:
- Aircraft must be presented to EGAC with not less than 10nm spacing, unless previously coordinated for increased spacing.
Speed Control:
- Essential to maintain separation, as traffic will be lost below radar cover at approximately 1500ft.
Weather and Aeronautical Information:
ATIS and QNH:
* EGAC will pass the current ATIS letter and QNH to EGAA, who may record the details if required.
* EGAA will ensure inbound aircraft are in receipt of the latest ATIS information before approach.
* EGAA will inform the pilot of the type of approach.
Operational Considerations:
Aircraft Movements:
- EGAC must not permit movements above 2,000ft Belfast QNH within the Belfast City CTR and CTA without prior coordination with EGAA Radar, except for missed approaches.
Missed Approach Notification:
- EGAC must inform EGAA Radar of a missed approach at the earliest opportunity.
S/VFR Aircraft:
- EGAC must advise EGAA Radar of all S/VFR aircraft operating in the EGAC CTR/CTAs.
- EGAC must minimize and exercise caution when clearing S/VFR aircraft to enter the CTR/CTAs. They must not cross the approach extended centerline without prior coordination with EGAA Radar.
Non-Duty Runway:
- The non-duty runway is not to be used when EGAA is vectoring EGAC inbound traffic. A runway change procedure must be implemented for non-duty runway use, with an agreed transition point.
Flow Control:
- The EGAC supervisor must contact the EGAA WM to coordinate Flow Control requirements and implement it accordingly.
