Jump to content
Sign in to follow this  
Chris Pawley

active 2017-10-12 London/Heathrow (EGLL) 3.2' RNAV approach trial (RNAV Y)

Recommended Posts

Chris Pawley

Effective 12 October 2017

 

Until 10 October 2018, a trial exists for the use of steeper (compared to the published procedure) RNAV approaches to all four runways at London/Heathrow. These procedures are known as "RNAV (GNSS) Y Runway xx L/R" and contain a VPA (Verticle Path Angle) of 3.2 degrees.

 

Crews requesting to take part in the trail should state "Request RNAV Yankee" on first contact with Heathrow Director.

 

These trial is designed to establish is a steeper approach angle is manageable for flight crews and ATC while reducing noise for the surrounding communities.

 

Note that:

  • PAPI lights for all runways remain at 3.0' crews should take care in the final stages of landing and using the PAPI in combination with the RNAV Y procedures.
  • RNAV Y approaches may only be conducted in  CAT I conditions or better
  • Missed approaches are designed around pre-existing approach procedures and thus require the relevant ILS DME to be functional as well as the LON DME.

 

These procedures will be documented only here (not in any ATC documentation) as they remain a trial; if and when they are permanently Incorporated, we will revise our documentation.

Edited by Chris Pawley

Share this post


Link to post
Share on other sites
Chris Pawley

This trial recommences on 10th October 2019 (AIRAC 2019/11) for a period of  one year (until AIRAC 2020/11)

Share this post


Link to post
Share on other sites
Sign in to follow this  

  • Similar Content

    • Chris Pawley
      By Chris Pawley
      Effective 21 May 2020
       
      The Heathrow RMA is revised in the vicinity of the OCK area, now the outer boundary of the RMA is on a track OCK-BIG (rather than OCK-EPM-BIG) and traffic may be descended below MSL by Heathrow when North of the DET SID track.

       
      Documentation revisions to reflect this change will follow, the 2020/06 version of the sector file has these changes already applied.
       
      Thanks to @Sebastian Rekdal for the graphics
    • Chris Pawley
      By Chris Pawley
      Effective 2020-05-21
       
      Agreements between Antrim and Scottish TMA are amended as follows:
       
      Traffic inbound to EGPK:- Descend to FL80 and coordinate with EGPK_APP
      Traffic inbound to EGPF:- Descend to FL150 level GIRVA and transfer to Scottish TMA
      Traffic inbound to EGPH:- Descend to FL170 level TUNSO and transfer to Scottish TMA
       
      The Agreed levels diagrams will be updated in the next cycle and published in 2020/07, the Sector File has these changes from 2020/06 onwards.
    • Chris Pawley
      By Chris Pawley
      Effective 21 May 2020
       
      The runway at London/Luton is redesignated 07/25 with magnetic headings of 075/255 - with all SIDs being redesignated to reflect the change of departure runway.
       
      No fundemental change of procedures is required, simply references to runway 08/26 should be transcribed.
       
      These changes are added to the Sector File from 2020/06
    • Chris Pawley
      By Chris Pawley
      Effective 6th April 2020
       
      As of 6th April, Heathrow has adjusted the noise alleviation scheme for local residents in light of the significantly reduced demand on the aerodrome. This scheme affords many local residents a respite from the noise and disruption from living near to the airport.
       
      The new arrangements see the airport utilising one runway for a week at time.
       
      Already in the last two days we have seen conflicts and complications applying these procedures. We see the opportunity to do something different as interesting, but this comes with some caveats and guidance. The VATSIM situation could not be any more different to the real situation - we're busier than ever - therefore :-
       
      It is the sole discretion of the Tower controller to determine whether to use single or dual runway(s). The choice of runway should be informed by the alternation plan for the respective option. Traffic levels are the primary consideration for a choice of mode - for example, there is no need for inbound to hold or departing traffic to recieve unnecessary delay while one totally servicable and usable runway is available. Runways should not be opened and closed excessively. Ideally controllers will decide a mode to operate in for the duration of their session. During training, members should be especially considerate to ensure the training process is not impacted and that students are supported as much as possible.  
      If the inter-member conflicts continue and operations continue to be impacted, we will revert to the dual runway alternation programme as published in December 2019.
       
       
×
×
  • Create New...