VATSIM-UK - Birmingham

Published with the kind permission of Denis Roschlau ©

Birmingham - EGBB

Welcome to the Birmingham International Airport - EGBB information pages. Please use the book mark links below to visit the relevant sections of this page.


General Information



Aerodrome Geographical Data



Aerodrome Reference Point522713.88N 0014452.9W
Location5.5 ESE of Birmingham
Elevation327ft

ATC Communication Facilities



Service DesignationCallsignFrequency
EGBB_APPBirmingham Radar118.05 MHz
EGBB_F_APPBirmingham Director131.00 MHz
EGBB_TWRBirmingham Tower118.30 MHz
EGBB_GNDBirmingham Ground121.80 Mhz
EGBB_DELBirmingham Delivery121.92 MHz
EGBB_ATISBirmingham ATIS126.27 MHz

Radio Navigation and Landing Aids



TypeIdentFrequencyRemarks
ILS 15I-BIR110.10 MHzCAT III 3° glideslope
ILS 33I-BM110.10 MHzCAT III 3° glideslope
NDBBHX406 Mhz20nm range

Runway Physical Characteristics



Runway NumberMagnetic BearingDimensionsSurface
15149°2599m x 46mAsphalt
33329°2599m x 46mAsphalt

Back to top

Departures

ON ALL BIRMINGHAM DEPARTURES MAINTAIN FL60 ON REACHING UNTIL CLEARED BY ATC.

The Transition Altitude in the Birmingham CTA is 4000ft. In low pressure, departing aircraft must ensure 1013mb is set as soon as practical to ensure they do not inadvertently climb higher than FL60.

Pilots are encouraged to attempt to fly the SIDs correctly from the charts. However, for pilots who do not have the charts, a simplified version is given which the controller can pass by text in the clearance. This version ignores the Noise Abatement Regulations and VOR radials but should produce approximately the same route. Use of an FMS is assumed for direct routings.

Charts are by far the best option and the latest charts for Birmingham can be found by using the Chart link at the top of this page.

Back to top

Arrivals



STARs should be used for flight planning purposes but routes may be varied by EGBB_APP to expedite arrivals or departures.
STARs via OLIVE are not used in VATSIM-UK since they are only for use when HON VOR is out of service.
Coventry Arrivals on airways should be routed on Birmingham STARs and positioned for Coventry by EGBB_APP
Aircraft inbound from the FIR (ie uncontrolled airspace) should be routed to GROVE or the BHX NDB.
Transition Level will be determined by ATC based on Transition Altitude of 4000ft and the Birmingham QNH. For the latest information on STAR procedures please refer to the charts that can be located via the Chart Link at the top of this page.



Click on the image to view the full size version or click here to download a copy

Back to top

Procedures



Birmingham Controller Positions



EGBB_DEL
(Only opened with prior permission)
Gives departure clearances for all departing aircraft. Airways clearances should include a SID. However, if the pilot does not have the SID chart then you MUST give vectors by text, ensuring they understand the routing. All EGBB SIDS climb to FL60. Inform the pilot of the departure frequency to expect - 118.05 if Approach is open otherwise see below. Once clearance has been given and readback correctly, instruct the pilot to contact Birmingham Ground and notify GND of the clearance given. Non-standard departures (Eg to the open FIR) will require a departure clearance which you must obtain from Approach and pass word for word to the pilot.
This position can only be opened when GND is manned and with the agreement of the controller on GND, when workload warrants it. Otherwise these duties will be carried out by GND in addition to those listed below.
EGBB_GND Provides for expeditious and safe movements of all aircraft on the ground except on active runways. Give Push (for aircraft on nose-in stands) and Start and then taxi instructions to the hold of the active runway. When the aircraft is at or approaching the hold pass to TWR and inform the tower of the aircraft's SID routing. TWR will pass arriving aircraft to you holding clear of the active runway. Give clearance to the aircraft to taxi to the appropriate terminal. If any aircraft needs to cross any runway then you must obtain clearance from TWR before clearing the aircraft to cross. Bear this in mind when issuing initial taxi clearances.
When GND is not open, TWR will carry out these duties in addition to those listed below.
EGBB_TWR Provides for the expeditious and safe arrival and departure of aircraft. APP will hand aircraft to you anywhere between 5 and 15 miles out! You have the call as to whether the aircraft may land. Once the aircraft has reported clear of the active instruct them to hold and pass to GND. Also ensure you know the correct missed approach procedures. Aircraft on a missed approach are handed back to EGBB_APP. Landing clearances are sometimes given as low as 200 feet (about 500ft QNH), you must decide. Departures should be passed to EGBB_APP as soon as possible. The SID charts actually require pilots to contact Birmingham Radar on their own initiative as soon as possible after passing 2000ft QNH so don't be surprised if they do! If Approach is not open, northbound departures should be passed to MAN_CTR, southbound to LON_N_CTR (or LON_CTR).
Low visibility procedures: When CatII/III is in operation, low visibility procedures should be introduced:- Hold at A2 for runway 15 instead of A1, twys G and K are closed.
When TWR is not open, APP will carry out these duties in addition to those listed below.
EGBB_APP Handles all traffic within the lateral boundaries of the CTA up to FL80 and will normally vector arrivals on to the ILS. Careful coordination is required with LON_N_CTR (or LON_CTR) for WCO, DTY COWLY and CPT departures and GROVE arrivals; and with MAN_CTR for TNT and WHI departures and CHASE arrivals. Traffic should be handed off as soon as possible to expedite the climb where possible. However, do not hand off until "clean" if there is a potential conflict with inbound traffic and ensure that the outbound maintains FL60 or vector them off the SID track if that helps to expedite the climb clearance. Departures on a TNT or WCO departure can be given further climb to FL80 if clear of conflict. Departures via the Birmingham-MOSUN procedure will be offered a Radar Advisory Service (RAS) or Radar Information Service (RIS) depending on workload by EGTT_W_CTR or EGTT_CTR if manned. If not, EGBB_APP can offer that service within a 40nm range and subject to workload. If there is no CTR position available, northbound departures should be contacted abeam TNT with a phrase such as "No ATC available in next sector, radar service terminates, frequency change approved", and southbound departures should be contacted abeam DTY with the same message.
Arrivals from the south and east should be handed off by LON_N_CTR abeam DTY at FL80 at the latest. This level will enable a direct interception of the ILS for runway 33 if traffic allows. Arrivals from the North and Northwest should be handed off by MAN_CTR abeam CREWE at FL90 at the latest to facilitate direct arrival to runway 15 if traffic allows.
EGBB_F_APPThis position must only be manned at the request and with the agreement of APP either during heavy traffic or to rehearse the procedures. It is known internally as Radar 2 and takes responsibility solely for final vectoring of arrivals. The stacks are managed by Radar 1 (EGBB_APP); when traffic commences an approach, they are given the descent and handed to Radar 2. See the diagram below for the division of responsibility.

Stacks

There are two main holding points for arrivals: CHASE for arrivals from the North and West and GROVE for arrivals from the South and East. (NB The OLIVE holding point is only for use in the real world when HON VOR is out of service and should never be needed on VATSIM.)

Of course, the normal level of traffic at Birmingham means that the stacks are rarely used (even in the real world). Even so, descent clearance below the minimum holding level should not be given until the approach path is assured. On runway 33 for example, traffic from DTY might be descended directly onto the ILS from the right to merge with traffic from the North via CHASE intercepting from the left. At busy times, the Director's task is to merge traffic from the South which will stay above FL70 over Honiley with a flow from the North via CHASE in the general area between Honiley and EBONY, the HON traffic probably turning left into the stream and descending before reaching EBONY. The CTR is not very big here and uncontrolled airspace is not far away! If in doubt, let them go to the hold and stick to the standard approach from there.

GROVE holding point

Max holding speed at GROVE and up to FL140 is 210kts
Max holding speed at GROVE and above FL140 is 240kts

CHASE holding point

ATC minimum FL80, max speed 210kts, inbound track 154° right turns



Pilots who wish to hold for training purposes should use GROVE as CHASE is not suitable for this purpose.

Max holding speed at CHASE and up to FL140 is 210kts
Max holding speed at CHASE and above FL140 is 240kts

Approach Patterns

Runway 33

From CHASE: Leave CHASE heading 180°, then left heading 150° downwind.
From GROVE: Leave GROVE heading 150° downwind.
Aircraft on a GROVE arrival can normally be given a crosswind heading after HON, before heading 150° downwind, if traffic permits.
From downwind: Left heading 060° base leg, descending to 2000ft minimum, 360° to intercept from the left.



Runway 15

Minimum descent clearance is 2500ft due to the Sutton Coldfield TV mast at 1358ft and the Tamworth mast at 1501ft.
Taxiway Charlie is not yet in any scenery file, so all aircraft requiring the terminals will have to vacate at the end. For this reason, aircraft on approach should be spaced at least 5nm apart for runway 15.
From CHASE: Leave CHASE heading 180°, then right heading 330° downwind.
From GROVE: Leave GROVE heading 330° downwind.
Aircraft on a GROVE arrival can normally be given a heading around 290° after HON, before right heading 330° downwind, if traffic permits.
From downwind: Right 060° base leg, descending to 2500ft minimum, then right heading 120° to intercept from the right.



Radar Positions - Division of Responsibility

The diagram below shows the dividing lines for each runway. Radar 1 handles all traffic FL80 and above and at lower levels prior to crossing the line. Radar 2 handles all traffic in the approach area beyond the line FL70 and below.



Radar Manoeuvring Area - RMA





Speed Control

Departures should be relieved of the 250kt speed restriction as soon as possible with the phrase "no ATC speed restriction".

Remember the following speed limits:-

No speed control can be imposed inside 4 miles from touchdown.

High speed, ie: greater than 250 knots can be approved by Birmingham Radar when an aircraft is clearly number 1 and traffic conditions are very light. Use the phrase "high speed approved" rather than giving a specific minimum speed and ensure the pilot is clear that speed is at his or her discretion.

Wake Vortex Seperation

Aircraft produce vortices from their wingtips, caused by the pressure differential between the top of the wing and the bottom of the wing meeting at the wingtips. What happens is large circular vortices form and trail behind the aircraft, a little like this:



For more information on this subject see our Wake Vortex page

Missed Approach Procedures

In the absence of ATC, aircraft should proceed as follows:-

Rwy 33 Climb straight ahead to 2500ft or I-BM DME 2 whichever is later and turn left to NDB BHX to hold at 2500ft

Rwy 15 Climb straight ahead to 1000ft QNH then turn right on track 170 to 2500ft or I-BIR DME 4 whichever is later then turn left to BHX and hold at 2500ft.

Contact LON_N_CTR or LON_CTR for further instructions at or before reaching BHX. When EGBB_APP is manned, vectors should be given for a further approach preferably using a righthand circuit for rwy 15 or a lefthand circuit for rwy 33 or diversion as required.

Back to top

Stand Allocation


Terminal 1Terminal 2
Adria AirwaysAir France/Cityjet/Britair
Aer ArannBritish Airways
Aer LingusEastern Airways
Air BerlinFlybe
Air IndiaKLM/KLM Cityhopper
Air MaltaSN Brussels Airlines
Air SlovakiaSwiss
Air Transat
Austrian
BH Air
BMI/BMI Baby
Centralwings
City Airline
Continental Airlines
Cyprus Airways
Easyjet
Emirates
Eurocypria Airlines
First Choice
Freebird
KTHY
LTE
Lufthansa/Lufthansa Cityline/Eurowings
Monarch
Norwegian
Onurair
Pakistan
Ryanair
SAS/Atlantic Airways
SKY Europe
Thomas Cook/MyTravel
Thomsonfly
Titan
Turkmenistan
XL


VFR Procedures

VFR flights are welcomed at Birmingham but should file a flight plan mainly to show departure point, aircraft type and intentions (Eg "Depart the circuit to the NW"). VFR Arrivals should be at or above 1000ft QFE at the final approach fix. Circuit height is 1000ft QFE (1325ft QNH) and a/c flying visual circuits will be controlled by EGBB_TWR.

Pilots arriving from the FIR should call EGBB_APP at least 5 mins before reaching the CTA boundary for clearance to enter controlled airspace and will normally be cleared to BHX NDB for a standard join to the circuit for the notified runway and circuit direction. Circuit height is 1000ft (1325ft QNH)

Back to top


[Page last modified 02/07/2009]


©2006, 2007, 2008, 2009 VATSIM-UK - No information contained in this site should be use for real world flights or navigation.