Jump to content

2020-11-11 Farborough (EGLF) Provision of ATS


Jack Edwards

Recommended Posts

Effective 11 November 2020

 

The following Farnboroigh Airport (EGLF) positions may be staffed:

Logon Callsign

RTF Callsign

Frequency (MHz)

Log on conditions

EGLF_APP

Farnborough Radar

134.350

None

EGLF_L_APP

Farnborough LARS

125.250

LF APC must be online

EGLF_TWR

Farnborough Tower

122.775

None

EGLF_GND

Farnborough Ground

121.825

None

 

Farnborough Radar - APC 

APC has responsibility for the Farnborough CTR/CTA and top-down of the airfield in the absence of Tower/Ground. Further, the Heathrow runway-dependent RMA (which includes airspace delegated to Farnborough) is set out in the below procedure change post, as well as procedures for inbounds/outbounds. 

https://community.vatsim.uk/topic/37020-2020-02-26-farnborough-eglf-sids-stars-rma-and-procedures-for-inoutbounds/ 

Farnborough APC on 134.350 may additionally provide a LARS service for either the LARS West sector only, or all 3 real-world LARS sectors (West, North, and East). This shall be noted in the controller ATIS, as well as notified to surrounding APC units.

Note: The LARS position (EGLF_L_APP on 125.250) does not cover the APC position top-down and may not be opened without APC online (see below).

Note: Division policy does not permit bandboxing of two frequencies other than for short periods.

 

Farnborough Radar - LARS 

Farnborough LARS (EGLF_L_APP on 125.250) may only be opened when the Farnborough APC (EGLF_APP) position is staffed by a different controller on 134.350. If APC closes, the LARS controller has the option of switching to APC and covering the LARS sectors, or logging off. 

The coverage areas of the West, North and East LARS sectors on VATSIM shall be the same as they are in the real world, shown on Page 5 of this PDF. 

The reasons behind this policy are as follows: 

  1. To maximise top-down provision at Farnborough, therefore reducing the responsibilities of London positions. There is little operational sense in a radar-derived LARS position not also covering Farnborough APC, especially given the low traffic levels in/out of the airfield.
  2. To ensure that when any ‘EGLFxAPP’ position is online, responsibility for the CTR/CTA - and therefore transits of EGLF airspace - are clearly linked to the APC position. LARS on its own could not reasonably be responsible for the CTR/CTA at the same time as not giving a top-down service. 

Note: The opening of further LARS positions is posssible with prior approval from the Operations Department in the form of a Temporary Instruction. If it is envisaged that there will be an event or traffic load worthy of such a split, members are may reach out via the Helpdesk to discuss the available options.

 

 

Documentation Status

This clarification will be incorporated in the 2020/13 release of the London vMATS but not in Farnborough vMATS until a later date.

Edited by Jack Edwards
  • Like 2
Link to post
Share on other sites
Jack Edwards

This post has been updated to reflect changes to the logon convention for Farboroigh LARS effective 28th January 2020.

EGLF_R_APP -> EGLF_L_APP

Edited by Jack Edwards
Link to post
Share on other sites
  • Similar Content

    • Chad Byworth
      By Chad Byworth
      Effective 20 May 2021
      As part of the UK programme to remove dependency on conventional navigation aids and to align with ICAO naming conventions for STARs the following changes have been made to Southend STARs:
      STARs Introduced
      Designator
      Terminal Hold
      Replaces
      Notes
      FINMA 1S
      SPEAR
      -
      -
      LISTO 1S
      SPEAR 2L
      -
      STARs Removed
      Designator
      Originating Fix
      Notes
      SPEAR 2L
      LISTO
      Replaced with LISTO 1S
      SPEAR 1M
      MCT
      Traffic to no longer route CALDA DCT MCT, new routing is CALDA L612 LISTO LISTO 1S
      SPEAR 2H
      HON
      Traffic to route HON L15 FINMA FINMA 1S
      Documentation Status
      The Southend vMATS Part 2 will be amended at it’s next revision.
    • Chad Byworth
      By Chad Byworth
      Effective 20 May 2021
      As part of the UK programme to remove dependency on conventional navigation aids and to align with ICAO naming conventions for STARs the following changes have been made to London City and Biggin Hill STARs:
      STARs Introduced
      Designator
      Terminal Hold
      Replaces
      Notes
      LISTO 1C
      JACKO
      JACKO 2L
      -
      STARs Re-designated
      JACKO 1H → HON 1C (no change to route).
      STARs Removed
      Designator
      Originating Fix
      Notes
      JACKO 2L
      LISTO
      Replaced with LISTO 1C
      JACKO 1M
      MCT
      Traffic to no longer route CALDA DCT MCT, new routing is CALDA L612 LISTO LISTO 1C
      Documentation Status
      The London City/TC Thames and Biggin Hill vMATS Part 2(s) will be amended at their next revision.
    • Chad Byworth
      By Chad Byworth
      2021-05-20 - Essex Group (EGSS/GW/SC) - STARs Amended
      Effective 20 May 2021
      As part of the UK programme to remove dependency on conventional navigation aids and to align with ICAO naming conventions for STARs the following changes have been made to Essex Group STARs:
      STARs Introduced
      Designator
      Terminal Hold
      Replaces
      Notes
      LISTO 1L
      LOREL
      LOREL 5F
      -
      RINIS 1A
      ABBOT
      IDESI 1A
      IDESI star extended outward to FIR boundary fixes - otherwise routing is per IDESI 1A
      TOSVA 1A
      XAMAN 1A
      Stack Swap STARs
      BKY 1X
      ABBOT
      ABBOT 1A
      -
      BPK 1X
      ABBOT 1F
      STARs Re-designated
      BARMI 1A → BARMI 2A - no change to route over the ground, re-designated as the ABBOT hold is now defined as RNAV (previously conventional).
      STARs Removed
      Designator
      Originating Fix
      Notes
      LOREL 2H
      HON
      Traffic to route HON L15 FINMA FINMA 1L
      LOREL 3G
      MCT
      Traffic to no longer route CALDA DCT MCT, new routing is CALDA L612 LISTO LISTO 1L
      LOREL 5F
      LISTO
      Replaced with LISTO 1L
      Additionally, all STARs via ASKEY/CASEY have been removed, these were STARs used during periods of VOR unserviceability and were never applicable to VATSIM. With the introduction of RNAV defined holds at ABBOT and LOREL they are now no longer required in reality either.
      Documentation Status
      The Stansted/Luton/Cambridge vMATS Part 2(s) will be amended at their next revision.
    • Chad Byworth
      By Chad Byworth
      Effective 20 May 2021
      The 9th Edition of MATS Part 1 becomes effective on the above date. It includes changes in the following areas, incorporating some recent supplemental instructions to MATS 1:
      Vectoring to Final Approach RNP Approaches Wake Turbulence VMC Criteria in Class D Airspace These changes will become effective on VATSIM on the above date and are summarised below, however controllers are encouraged to review the relevant sections of MATS Part 1 (9th Edition). Comments in [square brackets] highlight the differences against the 8th Edition.
      Vectoring to Final Approach
      There are minor changes to vectoring restrictions for ILS/VOR/NDB/surveillance radar approaches (see below for RNP) however, the day-to-day impact for most units is nil. 
      When vectoring to final approach controllers shall apply the following restrictions:
      Except when requested by the pilot, or authorised by a vMATS Part 2, aircraft shall be vectored to establish the final approach track no closer than 2NM before the FAF for an ILS/VOR/NDB/surveillance radar approach (see below for RNP) - [this changes from the previous restriction of no closer than 5NM from touchdown] At units where CDA procedures are not used controllers shall position aircraft to facilitate a period of level flight at either the published FAF procedure altitude or, where approved in the vMATS Part 2 and ATCSMAC allows, a level below the FAF procedure altitude - [no previous restriction specified] Allocate closing headings of not greater than 45° offset from the final approach track (not greater than 30° for independent parallel approaches) - [this changes from a previous recommendation to use less than 40°] Note: All UK aerodromes shall be considered notified for vectoring to establish closer than 2NM from the FAF or, where the ATCSMAC allows, below the published FAF procedure altitude unless documented otherwise in a vMATS Part 2 or ACB.
      RNP Approaches
      These changes are notified as changes to ‘Vectoring to Final Approach’ within the MATS Part 1 Revision History however, unlike the above changes these are more significant and will impact on how controllers vector to RNP approaches from 20 May 2021 onwards.
      When vectoring for an RNP approach controllers shall apply the following restrictions:
      When traffic permits controllers should permit aircraft to route on own-navigation via the appropriate IAF not below the published procedure altitude When necessary, controllers may vector onto the final approach track but must: Allocate closing headings of not greater than 45° offset from the final approach track (not greater than 30° for independent parallel approaches) Position aircraft to establish on the final approach track no later than the IF Controllers should not position aircraft on to the final approach track inside the IF as this may prevent aircraft RNP equipment from correctly flying the approach [Previously controllers were permitted to vector aircraft onto the final approach track of an RNP approach so long as the aircraft was established prior to the FAF. For some aircraft this may prevent the approach from correctly sequencing within the avionics equipment, preventing the pilot from flying the approach, hence the above restrictions]
      Note: Due to restrictions relating to controlled airspace containment, controllers at the following aerodromes may continue to vector aircraft to establish inside the IF so long as the pilot is informed and the aircraft establishes the final approach track prior to 2NM from the FAF:
      Stansted - EGSS Liverpool - EGGP Bristol - EGGD - for Runway 09 approach only Wake Turbulence Separation
      The following changes are made to the wake turbulence separation criteria:
      Guidance on application of wake turbulence separation criteria for tilt rotor types A380 category replaced with SUPER category - A380/AN124/AN225 types SUPER leading - HEAVY following separation now 5NM [reduced from 6NM] Opposite direction departures: SUPER leading - LIGHT/SMALL/MEDIUM following separation now 4 min [increased from 3 min] SUPER leading - HEAVY following new separation standard 3 min [no previous separation requirement] Note: There is change to wake turbulence separation for same direction departures.
      VMC Criteria in Class D Airspace
      Following the UK’s exit from the EU the historical Class D VMC criteria have been reintroduced. These considerably simplify VFR operations in Class D airspace and will reduce the need for SVFR clearances when the cloud ceiling is below 1500ft AGL.
      The following conditions, during the day, are now considered VMC thus permitting VFR flight:
      For aircraft other than helicopters, flying at or below 3000ft AMSL or 1000ft AGL (whichever is the higher) at 140 kts IAS or less - clear of cloud and with the surface in sight, and with a visibility of 5 km  For helicopters, flying at or below 3000ft AMSL or 1000ft AGL (whichever is the higher) at 140 kts IAS or less - clear of cloud and with the surface in sight, and with a visibility of 1500m For VFR traffic departing/arriving at an aerodrome or transiting the ATZ the more stringent criteria of remaining clear of cloud by 1000ft vertically/1.5 km horizontally with a visibility of 5 km (8 km above FL100) remains. When conditions are such that the cloud ceiling is less than 1500ft AGL, controllers should advise the pilot and ask them to report their intentions. The pilot may then proceed either by means of a SVFR clearance or, if their simulator is set to VMC, by VFR clearance. In the event of a pilot simulating VMC when IMC prevails the controller may either ensure standard separation against other flights (effectively treating the flight as SVFR for controlling purposes) or obtain positive confirmation from the pilot that they have conflicting traffic in sight when any instruction would require visual manoeuvring (for example a turn to final behind an IFR inbound).
      Note: For traffic operating at or above 3000 ft AMSL/1000 ft AGL/140 kts IAS the previous Class D VMC criteria of remaining clear of cloud by 1000ft vertically/1.5 km horizontally with a visibility of 5 km (8 km above FL100) remains.
      Documentation Status
      Except where stated above, these changes override any conflicting vMATS Part 2 procedures published prior to 20 May 2021. For vMATS Part 2 procedures published on or after 20 May 2021 which deviate from MATS Part 1 (9th Edition) controllers should use the documented vMATS Part 2 procedures which will have been developed with these MATS Part 1 changes in mind.
    • Chad Byworth
      By Chad Byworth
      Effective 25 February 2021
      To correct an omission from the Gatwick vMATS Part 2 controllers should note the following information regarding the Gatwick visual circuit.
      To deconflict against Gatwick outbounds routing north of the field and the Redhill Local Flying Area, all Gatwick visual circuits operate to the south of the airfield (ie. Runway 26L/R left-hand, Runway 08R/L right-hand).
      The visual circuit operates to a maximum of altitude 1500ft on the Gatwick QNH.
      AIR shall notify FIN when the visual circuit is active and coordinate when they wish to extend the downwind leg beyond 4 NM.
      Documentation Status
      The Gatwick vMATS Part 2 will be updated to reflect this change at the next revision.
×
×
  • Create New...