APC | Leeds Bradford (EGNM)¶
Airspace¶
Leeds APC is responsible for the airspace contained within the Leeds CTR and CTA which has the maximum vertical extent of FL85. Leeds delegates a portion of its CTR/CTA below the Y70 between BATLI and POL to PC Northeast for use at FL80. PC Northeast shall not vector traffic at or below FL90 east of POL, between and above the Leeds CTR/CTA without prior coordination with Leeds APC.
The Leeds CTR/CTA is split by a line running POL - LBA into departure and arrival boxes dependent on the runway in use.
Additionally, Leeds has three ‘gates’ where arrivals will be positioned. One to the south, one to the northwest, and one to the southwest.
Leeds departure/arrival boxes and gates
Radar Split¶
The DIR position may be opened with the agreement of RAD. It shall be responsible for final sequencing of traffic received from RAD.
Inbound Procedures¶
Silent Handover Agreements¶
The following standard arrival routes exist for Leeds traffic. For routes inside controlled airspace, silent handover agreements exist between Area Control and Leeds Radar:
| From | Route | Agreed Level | From |
|---|---|---|---|
| South | TNT - DENBY | FL80 | PC Northeast |
| East | GOLES - BATLI | FL90 | PC Northeast |
| West | CALDA/BARTN - POL | FL80 | PC Northeast |
| North | GASKO (See Note 3) | FL80 | PC Northeast |
Notes
Note 1: All arrivals route to LBA after the initial route.
Note 2: Inbound traffic is released for descent on transfer to Leeds APC unless it is transiting the departure box. Traffic routing via the departure box is released for descent to FL80 (unless Leeds is controlling outbound traffic, or there are no departures).
Note 3: Inbounds via GASKO: If the aircraft and Leeds APC can accept/provide a Deconfliction Service then PC East shall arrange a GASKO DCT LBA routing descending FL130, released at GASKO. When this release is agreed, Leeds APC shall ensure that the aircraft descends to leave CAS. Once the aircraft subsequently enters the Leeds CTR/CTA, it must remain within.
Traffic from the south should be positioned through the south gate and is released for turns passing L975 (northern edge for Runway 14, southern edge for Runway 32).
Traffic from the east is transferred at FL90 and is released for turn 5 NM before GOLES, however, must not been turned east of the LBA 270° track for Runway 14.
Traffic from the west should be positioned via either of the west gates and is released for turns passing FL70 or when inside the arrival/departure box.
Traffic from the north is released for turn when inside the arrival/departure box.
Where PC is unable to vector traffic through the gates, APC can expect aircraft to be on own navigation to LBA.
Traffic will be transferred in accordance with the following conditions unless otherwise coordinated:
- PC will achieve a minimum radar spacing of 10 NM, constant or increasing, between successive inbounds from the same direction.
- PC will retain aircraft from different directions until the silent release level is vertically separated.
APC can suspend the silent handover agreement at any time, at which point arrivals must be individually coordinated. Additionally, any aircraft which will not meet the conditions of the silent handover agreement must be coordinated.
Coordination with AIR¶
IFR arrivals will be transferred to AIR established on the final approach track, in the landing order. Traffic performing a visual approach will be prenoted to AIR before establishing on the final approach track, ideally by 10 NM.
Holding Procedures¶
Leeds APC is responsible for the following holds:
| Fix | Course | Direction | Available Levels |
|---|---|---|---|
LBA (402.5 kHz) |
138° | LEFT Hand | 3000 ft - FL80 |
Notes
Note 1: Traffic may hold above FL80 within PC Northeast's airspace with coordination.
Note 2: When holding at LBA, RAD shall cancel all standard inbound agreements and coordinate each inbound individually. Additionally, all departures are subject to a release from RAD.
Note 3: Traffic holding below FL80 conflicts with outbound traffic and as such, RAD may need to coordinate a different initial climb.
Outbound Procedures¶
All departures require a release from RAD, unless otherwise agreed with AIR. Departures will normally be transferred directly to Scottish Control. However, RAD may elect to take initial control of departures to deconflict them from inbounds – for example, for LAMIX departures from Runway 32. Additionally, RAD may elect to stop departures at altitude 4000 ft following coordination with AIR if required due to holding/inbound traffic.
When the QNH is 977 hPa or less, FL70 is not separated from 5000 ft, and coordination will be required with PC Northeast to agree a course of action to separate outbounds at FL70 from inbounds that are at 5000 ft.
UK Flight Information Services¶
Although not a notified LARS provider, APC is encouraged, subject to controller workload, to provide a UK FIS to any traffic operating in the vicinity of Leeds. Responsibility for the provision of FIS is with RAD.