ADC | Oxford (EGTK)¶
Taxiway Restrictions¶
| Taxiway | Restriction |
|---|---|
| Beyond holding point K | Single and twin piston aircraft only |
| Beyond holding point J | Code A & Code B aircraft only |
Parking Stands¶
All maintenance areas are considered non-manoeuvring and taxi clearance can be expected from holding points M, K or J.
IFR Departure Clearances¶
Oxford is located outside of controlled airspace and therefore there are no SIDs established. IFR flights joining controlled airspace are expected to file via (and will be cleared via) the following initial routes:
| To | Joining Fix | Route | ATS Route Network Joining Sector |
|---|---|---|---|
| North | SAPCO | IXURA - DTY - SAPCO | TC Midlands |
| East | DTY | IXURA - DTY | TC Midlands |
| South (RFL < FL 195) |
KENET | BUGUP - KENET | TC South West |
| South (RFL > FL 195) |
CPT | IXURA - NANUM - BUGUP - EVSEM - CPT | TC Midlands |
| West (RFL < FL 105) |
BADIM | BADIM | Bristol APC |
| West (RFL > FL 105) |
CONKO | CONKO | AC West |
| London TMA | SILVA | SILVA | TC North West |
| EGLL / EGWU | WCO | WCO | TC North West |
When the aircraft requests start-up clearance, GMC shall coordinate with RAD, who shall then prenote (via text coordination) the appropriate Area Control sector and generate an SSR code. RAD will confirm the SSR code and after departure instructions to GMC, to be passed to the aircraft. During radar operation, aircraft will typically fly a tactical heading with a level outside of controlled airspace to initially deconflict from local traffic before continuing according to their flight plan.
Radiotelephony
OXF12, after departure runway 19, turn left heading 090 degrees, climb to altitude 4000 feet, squawk 1234
When the aircraft is airborne, RAD shall coordinate with the appropriate Area Control sector for a clearance to join controlled airspace. This will then be passed to the aircraft. If Area Control is unable to pass a joining clearance immediately, RAD may need to issue delay vectors, or allow the aircraft to enter the hold at OX.
IFR departures intending to remain outside of controlled airspace only require after departure instructions from RAD and shall be allocated an Oxford local SSR code. These will be requested upon engine start.
Departure Releases¶
All IFR departures require a release from RAD. Amended after departure instructions may be given with the release, which must be passed to the aircraft before take-off clearance is given.
Additionally, all IFR departures and turboprop/jet VFR departures from Runway 19 must be released by Brize. This is obtained by RAD from Brize APP prior to issuing a release to ADC.
IFR flights joining controlled airspace at KENET require release from TC SW, and via SILVA or WCO from TC NW. RAD shall obtain this release from TC prior to issuing a release.
It is the responsibility of RAD to provide releases for IFR traffic that ensure separation between departing aircraft (see Approach Control – Outbound Procedures).
Departure Separation without APC¶
In the absence of a controller providing radar services, aircraft may depart with a 2-minute departure interval, reduced to 1-minute when the initial route diverges by 45° or greater.
ADC shall apply departure separation in accordance with the UK Harmonised Speed Table, when APC (or top-down) is offline.
| Group 4 | Group 3 | Group 2 | Group 1 |
|---|---|---|---|
| All jet aircraft except: - Those in Group 3 - Concorde - Military fast jets |
BAE146/Avro RJ CL35/CL60 CRJ1/2/7/9/X B328/J328 D8D E135/145 E50P/55P P180 SB20 Citations except: C56X/680/68A/700/750 |
ATR variants DH8A/B/C F50 JS31/32/41 King Air variants PC12 SF34 SW3/4 TBM7/8/9 |
BN2P/T C208 DA62 DHC6 E110 |
Speed Separation Notes
- The basic separation interval (2 minutes) is applied between types in the same group (or where the following aircraft is one group slower)
- An additional 1 minute is added for each successive group when the following aircraft is faster (where the resulting timed interval is excessive, the controller may coordinate an early release)
- The basic interval may be reduced by 1 minute when the following aircraft is two or more groups slower (however, the controller must account for wake turbulence separation)
- Types not in the speed table (and the subsequent aircraft) are subject to release from the appropriate radar controller.
Departure Hand-off Order¶
All departures are to be transferred to RAD once aerodrome conflictions are resolved, unless otherwise notified by APC.
In the absence of RAD, or when departing aircraft request surveillance-based services outside of radar operation, departures are to be transferred in accordance with the following sequence:
| Callsign | Position Logon | Controller Identifier | Frequency |
|---|---|---|---|
| Brize Radar | EGVN_L_APP | VNL | 124.280 |
| Brize Approach | EGNV_APP | VNA | 127.255 |
| TC Midlands | LTC_M_CTR | TCM | 121.030 |
| AC Daventry | LON_M_CTR | LM | 120.025 |
| AC Central | LON_C_CTR | LC | 127.105 |
| AC South-Central | LON_SC_CTR | LSC | 132.605 |
| AC Bandbox | LON_CTR | L | 127.830 |
Note
The radiotelephony callsign is “London Control” for all the above Area Control positions.
The radiotelephony callsign is “Brize Radar” for Brize Norton LARS and “Brize Approach” for APP.
In the absence of any of the above positions, aircraft should be instructed to “remain outside controlled airspace” and free-call the sector responsible for the ATS Route Network join as listed in the table above.