NOT FOR REAL WORLD USE
Last Updated - April 2023
Position | IVAN CS | RT Callsign | Frequency |
---|---|---|---|
GMC | EGVN GND | Brize Ground | 121.725 |
AIR | EGVN TWR | Brize Tower | 123.725 |
APP | EGVN APP | Brize Approach | 127.250 |
ATC Low Visibility Procedures come into effect when:
The following spacing should be used for arrivals during LVPs:
CPDLC Datalink clearances are not in use at Brize Norton.
Aerodrome Control responsibilities at Brize Norton are split between:
Brize Norton QFE = QNH - 10 hpa
“TARTAN41, After departure, CONKO SID, Climb FL80, Squawk 3701, When airborne, contact Brize Radar 127.250”
Brize Norton is not freeflow. AIR must request a release for all departures from Brize APC.
Note: Brize APC may amend the altitude/ after departure instructions if required due to the traffic situation.
Military ATC can clear an air system to land when another air system is on the runway.
”OMEN41, Surface Wind 250, 5, Runway 25, Cleared to land, one on, touch and go.”
Conditional clearances are used by Brize Norton ATC.
Wake turbulence separation minima on departure shall be applied by measuring airborne times between successive aircraft. Take-off clearance may be issued with an allowance for the anticipated take-off run on the runway; however, the airborne time interval shall reflect a difference of at least the required time separation. ATC does not have the discretion to reduce wake turbulence separation minima.
The following wake turbulence separation shall be applied between departing aircraft (in minutes):
Follower → ↓Leader
|
Super | Heavy | Medium | Small | Light |
---|---|---|---|---|---|
Super | # | 2 | 3 | 3 | 3 |
Heavy | # | 4nm | 2 | 2 | 2 |
Medium | # | # | # | 2 | 2 |
Small | # | # | # | # | # |
Light | # | # | # | # | # |
Aircraft departing from an intersection require an additional minute to the times stated above.
The following aircraft types are primarily based at Brize Norton:
In addition to turbulence and speed separations, Brize Norton operates a 2 minute route separation between departures. This time is counted from the moment the first aircraft begins its take-off roll. If the aircraft commences a full length take-off and the following aircraft departs from an intersection, the spacing should be increased to 3 minutes.
All aircraft should be transferred to Brize APC as soon as possible before passing altitude 2000ft.
if Brize APC is offline, Departures should be transferred to:
If all of the above are offline, Departures should be released to UNICOM.
The following wake turbulence separation (Nautical miles) shall be applied between arriving aircraft:
Follower → ↓Leader
|
Super | Heavy |
Upper Medium |
Lower Medium |
Small | Light |
---|---|---|---|---|---|---|
Super | # | 5 | 7 | 7 | 7 | 8 |
Heavy | # | 4 | 5 | 5 | 6 | 7 |
Upper Medium | # | # | 3 | 4 | 4 | 6 |
Lower Medium | # | # | # | # | 3 | 5 |
Small | # | # | # | # | 3 | 4 |
Light | # | # | # | # | # | # |
# Signifies that separation for wake turbulence reasons alone is not necessary
For details of missed approach procedures, refer to the UK MIL AIP.
Brize Norton Approach is responsible for aircraft within the Brize Norton CTR.
Use | Code |
---|---|
Approach | 3701 - 3736 |
Frequency Monitoring Code | 3727* |
Circuit | 7010 |
*This code may be used when flying in the vicinity of RAF Brize Norton, operating outside of Brize Norton CTR and monitoring Brize Norton LARS frequency.
Fix | Inbound course/ Direction | Minimum altitude |
---|---|---|
BZ | 098 / Right hand Turns | 3000ft |
Aircraft should be radar vectored to establish 2nm before the final approach fix or final approach point.
Speeds to be flown during approach are specified by the controller and will depend on the traffic situation at that time. If traffic conditions permit, a pilot may be requested to maintain a higher than normal speed or be advised that there is “no ATC speed restriction”.
There are standard speeds to be employed are as follows:
To assist pilots in the management of their descent, ranges from touchdown are to be passed as follows:
The following wake turbulence separation (miles) shall be applied between arriving aircraft:
Follower → ↓Leader
|
Super | Heavy |
Upper Medium |
Lower Medium |
Small | Light |
---|---|---|---|---|---|---|
Super | # | 5 | 7 | 7 | 7 | 8 |
Heavy | # | 4 | 5 | 5 | 6 | 7 |
Upper Medium | # | # | 3 | 4 | 4 | 6 |
Lower Medium | # | # | # | # | 3 | 5 |
Small | # | # | # | # | 3 | 4 |
Light | # | # | # | # | # | # |
# Signifies that separation for wake turbulence reasons alone is not necessary.
In the event of a missed approach, AIR will pass details of the missed approach to the APP controller. The APP controller shall issue a heading and frequency to which the subject aircraft will be transferred.
”TARTAN41, London Control clears you to Join controlled airspace, on track CONKO, Climb FL80”
VFR Circuits are flown to the North of Brize Norton. Runway 07 Left Hand and Runway 25 Right Hand.
On start up, departing aircraft have already been issued the following by the GMC controller:
VFR transits must not enter the ATZ without approval from AIR. Transits should cross the threshold of the runway in use. Transits not entering the ATZ can remain with APC.
All VFR inbounds/outbounds must route via a valid VRP not above altitude 1800ft QNH when inside the Brize CTR.
The following Visual Reference Point’s (VRP's) have been established for Brize Norton:
SVFR flights may be authorized to operate within the Brize Norton control zone, subject to ATC Clearance if flight visibility is not less than 1500m and the cloud ceiling is not less than 600ft.
Brize Norton APC provides a Lower Airspace Radar Service (LARS) up to a range of 40nm outside of controlled airspace subject to controller workload.