APC | Prestwick (EGPK)¶
Airspace¶
Prestwick is located in Class D controlled airspace established as a CTR with adjacent CTAs. The Scottish TMA is located above the Prestwick CTR/CTA and is also established as Class D within the vicinity of Prestwick.
Prestwick APC is responsible for the Prestwick CTR/CTA and the “Prestwick Local Area” airspace delegated to them by Scottish Terminal Control at and below 6000 ft as depicted below.
Scottish TMA Local Areas
The Glasgow Local Area is established adjacent to the northern boundary of the Prestwick Local Area. A radar buffer is not established and neither unit shall vector within 2.5 NM of the common boundary without coordinating with the other unit.
Inbound Procedures¶
Inbound Releases¶
The table below summarises the agreed levels for inbounds transferred from Scottish Control to Prestwick APC. The subsequent sections add further specific conditions.
| Via | From | Agreement |
|---|---|---|
| BLACA 1P | Antrim | Agreed level (agreed between Antrim and Galloway) by GIRVA |
| APPLE 2P / RIBEL 2P | Galloway | MSL (See note) |
| TRN (no STAR) | Antrim / Galloway | Individually coordinated |
Note
MSL may be allocated to more than one aircraft provided a minimum of 5 NM between aircraft on parallel/diverging headings, or 10 NM (constant or increasing) between aircraft in trail is provided.
During low traffic levels, direct routings may be individually coordinated.
Where the conditions for a silent handover are not met, a reduced radar handover, in the following format, may be used:
Coordination
Callsign, descending to level, (heading), (speed).
Arrivals via BLACA 1P (Antrim)¶
Antrim shall coordinate a level with Galloway (Prestwick APC will not be involved in coordination), clearing the traffic to this level, level by GIRVA. Traffic shall then be transferred directly from Antrim to Prestwick INT by silent handover provided that the aircraft is routing to, or on a heading towards, the holding fix. Traffic is released subject to any outbound traffic.
Arrivals via APPLE 2P / RIBEL 2P¶
Galloway shall descend this traffic to the MSL, level 10 NM before TRN and transfer to Prestwick INT by silent handover provided that the aircraft is routing to, or on a heading towards, the holding fix.
If holding is required, Galloway will coordinate the use of the off-route hold at SUMIN with Prestwick APC as appropriate.
Arrivals from LOMON¶
ScAC South shall pass details of arrivals via LOMON to Glasgow APC, who may elect to work this traffic after radar handover. Should they choose not to work the traffic, it shall be coordinated with Galloway who is then responsible for coordinating the arrival with Prestwick INT.
Arrivals via P600 from the North¶
The default routing for traffic inbound to Prestwick shall be GRICE-FENIK-TRN. ScAC South shall coordinate a level at GRICE with Galloway.
Galloway shall then descend the traffic to MSL, ensuring it remains above the Glasgow Local Area before providing Prestwick INT with a radar handover when the traffic is clean. It is then Prestwick’s responsibility to coordinate with Glasgow APC, should they wish to descend it into Glasgow’s Local Area.
If the aircraft is low performance, it shall be routed to TRN by Galloway and identified to Glasgow APC if it is likely to conflict with Glasgow inbounds. If Glasgow chooses to work the traffic, they are then responsible for coordinating the inbound with Prestwick.
Alternative Routing via N864
In real life, when the P600 is in use by the Scottish Gliding Centre, inbounds are routed N864-PIPAR and then coordinated between Galloway and Talla accordingly. The preference is for aircraft to route via P600 on VATSIM, though some may file via N864.
Vectoring of Inbounds¶
All inbounds are released for turns in the same general direction whilst within the airspace of the transferring unit, until entering the Prestwick Local Area.
Descent of Inbounds¶
If Prestwick descend arriving aircraft below MSL, it is then their responsibility to ensure separation against departing aircraft already transferred to Scottish Control.
Holding Procedures¶
When holding is required inbounds via the APPLE 2P and RIBEL 2P STARs will be re-routed to hold at SUMIN. All other inbounds will hold at TRN.
Aircraft in the hold will typically be released to Prestwick INT at the MSL or below.
SUMIN Hold¶
The SUMIN Hold is an off-route RNAV hold.
| Name | Axis | Direction | Holding Levels | Leg Time | Speed |
|---|---|---|---|---|---|
| SUMIN | 269° | LEFT hand | 6000 feet - FL90 | 1 minute | Maximum 210 kts IAS |
Note
Although the maximum holding level is FL90, the SUMIN hold is separated from GOW, TRN, LANAK, TARTN, STIRA and FYNER at FL140 and below.
TRN Hold¶
| Name | Axis | Direction | Holding Levels | Leg Time | Speed |
|---|---|---|---|---|---|
| TRN | 028 | LEFT hand | 6000 feet - FL90 | 1 minute | Maximum 210 kts IAS |
Note
Although the maximum holding level is FL90, the SUMIN hold is separated from GOW, TRN, LANAK, TARTN, STIRA and FYNER at FL140 and below.
Outbound Procedures¶
Transfer of Departures¶
All standard outbounds (SID or standard omnidirectional departures) are free-flow and will be transferred on the SID/omnidirectional route directly to the appropriate Scottish Control sector.
Prestwick INT may request for departures to be transferred to them by AIR if they are likely to conflict with inbound traffic. During periods of heavy inbound demand, the INT controller should give significant consideration to either implementing a departure check or informing AIR they will be working all outbound traffic so as to avoid conflict with inbounds. In particular, Runway 30 departures to the south-east will conflict with all inbounds via TRN and can leave limited room to radar vector for an approach.
Silent Handover from INT to Scottish Control¶
If Prestwick INT elect to work a departure, it may be transferred by silent handover to Scottish Control provided it is climbing to the SID altitude, following the agreed route, and separated from all local area traffic.
Transfer of communications (coincident with transfer of control) must take place before the local area boundary.
Vectoring of Departures¶
By Prestwick APC
Prestwick INT is responsible for monitoring departures and ensuring separation against inbound traffic. Successive departures must be separated by at least 5 NM, constant or increasing, on transfer to Scottish.
Departures may be vectored by Prestwick INT within the local area to achieve separation without coordination with Scottish Control. This traffic must be resumed own navigation on the SID track by the local area boundary, else coordinated.
By Scottish Control
All vectoring, or deviation from the SID, below MSL is not permitted without coordination with Prestwick APC.