¶ EGLF Farnborough Aerodrome Procedures
NOT FOR REAL WORLD USE
¶ General
¶ ATC Positions
| Position | IVAN CS | RT Callsign | Frequency |
|---|---|---|---|
| GMC | EGLF_GND | Farnborough Ground | 121.815 |
| AIR | EGLF_TWR | Farnborough Tower | 122.780 |
| INT | EGLF_APP | Farnborough Radar | 125.250 |
| LARS North | EGLF RSN APP | Farnborough Radar | 132.800 |
| LARS West | EGLF RSW APP | Farnborough Radar | 125.250 |
| LARS East | EGLF RSE APP | Farnborough Radar | 123.225 |
¶ Position opening and band boxing policy
¶ LARS
| Bandbox | EGLF ALL | ||
|---|---|---|---|
| Sector Split | LARS N | LARS W | LARS E |
Should EGLF-ALL be online in conjunction with any additional LARS sectors, EGLF-ALL is to relinquish control of the respective online sector.
¶ Aerodrome Control
Aerodrome Control responsibilities at Farnborough are split into:
- Ground Movement Control (GMC) “Farnborough Ground”
- Air Control (AIR) “Farnborough Tower”
¶ Runway Selection
- Runway 24 is the preferred runway when the tailwind component is 5 knots or less.
- AIR is responsible for Runway selection.
¶ Altimeter Setting
- Departing aircraft are to be given the Farnborough QNH prior to take-off.
- Arriving aircraft below the transition level are to be given the Farnborough QNH.
- Aircraft entering the aerodrome traffic circuit are to operate on the Farnbourough QFE.
Farnborough QFE = QNH - 8 hPa
¶ CAT II/III Operations
Farnborough is not equipped for Cat II/III operations, however Low Visibility Procedures are used to protect Cat I operations. Runway 24 and 06 are not suitable for Lower Than Category I operations.
¶ Low Visibility Procedures
ATC Low visibility procedures will commence when:
- Met visibility/IRVR is 1500 M or below
- and/or cloud ceiling is 200 FT or below
¶ Restrictions
- Pilots should be informed by ATIS Broadcast or by RTF when LVP’s commence.
- Conditional clearances are suspended.
- Departures in RVR Conditions less than 400M are not approved.
¶ Ground Movement Control (GMC)
¶ Responsibilities
- All ground movements on the manoeuvring area except for the active runway and its access points.
- Clearance Delivery and the issuing of ATC departure clearances.
- Requesting non standard clearances from INT/ LTC.
¶ Clearance Delivery
Departing aircraft should provide their:
- Aircraft type;
- stand/spot number and;
- ATIS Information code on first contact.
Any omitted information should be added to the clearance.
¶ Taxiway Restrictions
- Taxiway Y between South 1 Apron and South 2 Apron is not available to aircraft.
- Taxiway D is available to Helicopters for parking on the D Ramp only.
¶ Parking Allocation
- Parking locations referred to as Ramps by ATC delineate approximate location. Tower and Hangar Ramps are determined by the Hangar number the Ramp is outside/opposite and are referred to over the R/T as Tower x or Hangar x (where x is a number between 1 and 6 according to the aircraft parking/docking chart.
¶ Air Control (AIR)
¶ Responsibilities
- Absolute authority over all movements on the active runway and its access points.
- Aircraft within in, and in the vicinity of, the Farnborough ATZ and aerodrome traffic circuit.
- Requesting releases for non standard departures.
- Ground Movement Control responsibilities when GMC is closed.
¶ Departure Separation
¶ Wake Turbulence
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.
CAA Departure seperation minima must be applied between departing aircraft. Departure separation minima can also be found within the XU Quickview.
¶ Route separation
All departure SIDs from Farnborough are separated by 2 minutes.
¶ Transfer of Control
¶ Departures
All departures from Farnborough should be transferred to INT when airborne before passing altitude 2000ft.
- If INT is offline, departures should be transferred to:
- LARS_W (EGLF RSW APP)
- LARS_ALL (EGLF APP)
- TC_SW (EGTL SW CTR)
- TC_ALL (EGTL CTR)
- LAC_S (EGTT S CTR)
- LAC_ALL (EGTT CTR)
- If none of the above are online, departures should be released to UNICOM.
¶ Arrivals
INT will transfer control of arrivals up to 4 miles from touchdown. Transfer of communications can take place outside of 4 miles as soon as the aircraft reports established on the instrument approach.
INT may use speed control up to 4 miles from touchdown. If corrective speed control is required inside of 4 miles, AIR must coordinate with INT.
¶ Arrival Separation
¶ Wake Turbulence
The wake turbulence separation minima in the XU Quickview shall be applied to aircraft on final approach when:
(1) an aircraft is operating directly behind another aircraft at the same altitude or less than 1,000 ft below; or
(2) an aircraft is crossing behind another aircraft, at the same altitude or less than 1,000 ft below;
¶ Missed Approach
Missed approach procedures for Farnborough can be found in the UK AIP.
¶ Approach Control (INT)
¶ Area of Responsibility
- Farnborough INT is responsible for all aircraft within the Farnborough CTR and CTA’s.
- INT is also responsible for LARS_W and providing UK FIS outside of controlled airspace.
- Responsible for control of inbound aircraft from the release point until control is transferred to AIR.
- Responsible for the control of outbound aircraft until control is transferred to London Terminal Control (TC)
¶ Squawk Code Allocation (INT)
| Approach Radar (IFR/SVFR) | 0421 - 0427 |
| Farnborough Zone VFR | 0460 - 0466 |
| Farnborough Zone Conspicuity | 0467 |
| Farnborough Zone (IFR/SVFR) | 1750 - 1757 |
¶ Intermediate Approach
¶ Inbound Releases
The Standard release points from LTC to Farnborough are:
| Release point | Standing Agreement |
|---|---|
| VEXUB | 3000ft |
| PEPIS | FL80 |
TC will transfer Inbounds silently as long as the following conditions are met:
- The aircraft is inbound to a standard release point.
- The aircraft is descending to the standard agreed level.
TC will effect coordination with Farnborough INT if any of the above conditions are not met.
¶ Holding
| Hold | Inbound Course/ Direction | Min Altitude/ Level |
|---|---|---|
| VEXUB | 056/ Left | 3000ft |
| PEPIS | 003/ Right | FL70 / MSL |
¶ Radar Separation
A minimum radar seperation of 3nm must be applied within Farnbourough and LTMA Airspace.
¶ Final Approach
¶ Wake Turbulence Separation
The wake turbulence separation minima in the XU Quickview shall be applied to aircraft on final approach when:
(1) an aircraft is operating directly behind another aircraft at the same altitude or less than 1,000 ft below; or
(2) an aircraft is crossing behind another aircraft, at the same altitude or less than 1,000 ft below;
¶ Departures
Departures should be issued climb to the standard agreed levels.
| From | To | Via | Agreement |
|---|---|---|---|
| EGLF_INT | EGHI_INT | ALL Routes | ↑ 5000 ft |
In the absence of EGHI INT, Departures can be issued climb to MSL before transfer to TC SW.
¶ Low Level Procedures
¶ Airspace
The Farnborough CTR and CTA’s are Class D Controlled airspace with the exception of:
Farnborough CTA 8 and CTA 9 which are Class E Controlled Airspace. (VFR may transit class E airspace without am ATC clearance and may utilise a UK FIS.)
¶ VFR Circuit
Circuits are flown to the South:
- Runway 06: Right hand
- Runway 24: Left hand
Altitude/Height flown vary depending on the type of aircraft:
- Jet Aircraft: Altitude 1700ft QNH or Height 1500ft QFE.
- Light Aircraft: Altitude 1200ft QNH or Height 1000ft QFE
¶ VFR Inbounds/ Outbounds
VFR Fixed wing aircraft will be instructed to route via Visual Reference Point’s (VRP’s) not above altitude 3000ft QNH.
- VRP’s can be displayed within the Aurora sector file or;
- Referenced from the NATS UK AIP.
¶ VFR Transits
- VFR Transits must not enter the Farnborough ATZ without approval from AIR. If traffic permits, Transiting aircraft may cross directly overhead or via the threshold of the runway in use.
- VFR Transits may be requested to route west/ east of Farnborough as to not conflict with Farnborough departures/ arrivals.
¶ SVFR
- Special VFR (SVFR) clearances for flights within the Farnbourough CTA can be requested and may be given when traffic conditions permit. SVFR flights must be separated from other SVFR and IFR Flights.
¶ Helicopter Procedures
- Helicopter VFR arrival and departure Routes have been established for Farnborough.
- These routes and associated VRP’s can be found in the UK AIP.
- Helicopters should operate not above altitude 3000ft on the Farnborough QNH.
- Helicopters should arrive or depart from the Helicopter Landing Area’s (Heli Bravo, Heli Foxtrot, Heli Yankee) or via the Runway in use.
¶ Approach Control (LARS)
¶ Area of Responsibility
The lateral limits of the Farnborough Lower Airspace Radar Service are shown in the diagram below.
The figure above details the general areas of responsibility for the Farnborough LARS area. Each of the three sectors controls the airspace denoted above with the exception of the CTRs surrounding each aerodrome.
Additionally, LARS West is responsible for the intermediate approach function for Farnborough Airport (EGLF) as well as the respective CTAs and CTRs.
Despite being responsible for the provision of UK Flight Information Services across much of the South-East, Farnborough LARS is not responsible for and must not provide a Radar Control Service into any aerodrome with the exception of EGLF by LARS-W.
¶ Delegated Airspace
The airspace around Southampton and Southend is delegated to Solent Radar and Southend Approach respectively as shown in the colour cyan in the diagram above.
In the event of either of these ATSUs being closed the airspace will remain the responsibility of the relevant LARS sector.
¶ Service Provision by LARS
Farnborough LARS provides UK FIS’ (UK Flight Information Services) to anyone flying under or around the LTMA (London Terminal Manoeuvring Area) and within its sectors (see above).
Farnborough LARS may provide the following services to aircraft operating within its AoR:
- Basic Service
- Traffic Service
- Deconfliction Service (IFR Only)
- Radar Control Service (Inside CAS Only)
For further information on UK FIS, reference CAP 774.
¶ Service Reductions
When aircraft are provided with a traffic or deconfliction service, it may sometimes be necessary to provide a reduced service – the reason behind this must be stated to the aircraft. A reduced service may be provided for reasons such as but not limited to controller workload or radar suppression.
¶ Transponder Mandatory Zones
A TMZ is defined as a volume of airspace in which aircraft requiring to fly within the defined area, will be required to operate SSR (Secondary Surveillance Radar) equipment or be in contact with the controlling ATC authority i.e. Farnborough LARS.
There are four TMZs within the Farnborough LARS AoR as depicted in the below charts.
Aircraft wishing to enter a TMZ are required to enter according to certain conditions based on their aircraft equipment, this is summarised in the below table.
| XPDR Equipment | Conditions |
|---|---|
| Mode S and SSR Equipped | Do not need to ask permission but we do advise you still make two way contact with Farnborough Radar |
| Mode A or Mode A and C Only | Aircraft ARE REQUIRED to ask permission to access the TMZ and may continue through remaining outside CAS. |
| Not Equipped | Aircraft ARE REQUIRED to ask permission to access the TMZ and, once permission is granted, may continue through remaining outside CAS. |
There should never be a reason to refuse access to the TMZ’s but it is necessary to maintain a known traffic environment with commercial traffic operating at low level around the TMZ’s.
¶ Squawk Code Allocation (LARS)
| LARS West | 0430 - 0456 |
| LARS West Conspicuity | 0457 |
| LARS East | 1730 - 1746 |
| LARS East Conspicuity | 1747 |
| LARS West Listening Squawk | 4572 |
| LARS North | 5020 - 5036 |
| LARS North Conspicuity | 5037 |
¶ Separation Requirements
The deconfliction minima against unco-ordinated traffic are:
- 5NM Laterally
- 3000 ft Vertically
The deconfliction minima against aircraft that are being provided with an ATS by the same controller, or that have been subject to co-ordination, are:
- 3NM Laterally
- 1000 ft Vertically
CAP 774 Chapter 4: Deconfliction Service
¶ Separation Methods
Clearance Limits – Aircraft may be instructed not to climb above or descend below a certain altitude, or may be asked to proceed no further North/East/South/West of a certain position.
Routing – Aircraft may be asked to fly a prescribed route to maintain or create separation, particularly on the final approach.
¶ Overhead Transits
Aircraft may be asked on occasion to route East or West of the airfield during a zone transit to allow approaches and departures to take place from EGLF.