Jump to content
Sign in to follow this  
Harry Sugden

atc-discussion New Scottish Controller Positions 2016/02

Recommended Posts

Harry Sugden

In a similar style to the London post, with regard to the new EGPX FIR area sectors:

Sector Names

A sector name (i.e. what we publish in documentation) will always be the most-split version - i.e. the blocks of airspace and arranged into Local Area Groups (LAGs):

ScAC East: East

ScAC West: West, Deancross, Rathlin, TMA, Antrim

Controller Positions

A position is different from a sector, in that a controller may log on to a position and be covering different sectors depending upon what other positions are open. For example:

If SCO_W_CTR and SCO_CTR were logged on, SCO_W_CTR would be controlling the West, Rathlin and Antrim sectors whilst SCO_CTR would be controlling the East, Deancross and TMA sectors.

If STC_A_CTR then logged on, SCO_W_CTR would now just be controlling the West and Rathlin sectors.

The names of the positions (i.e. the callsign you use for coordination) don't change for SCO/STC, meaning commuting the nomenclature to memory is a little easier!

Bandbox (SCO_CTR) will always be known as "(Scottish) Bandbox"

Low Level / TMA

The names of these positions never change:

  • STC_CTR - "(Scottish) TMA"
  • STC_A_CTR - "Antrim"

ScAC East LAG

  • SCO_E_CTR - always "(Scottish) East"

ScAC West LAG

  • SCO_WD_CTR - "West (and) Deancross", regardless of whether Rathlin is split
  • SCO_W_CTR - always "(Scottish) West"
  • SCO_R_CTR - always "Rathlin"
  • SCO_D_CTR - always "Deancross"

When SCO_WD_CTR is online and SCO_W_CTR or SCO_D_CTR subsequently logs on, the controller on SCO_WD_CTR should, where possible, switch to the remaining sector callsign if a suitable moment in the traffic arises. It is however possible to have SCO_WD_CTR and SCO_R_CTR online without the need to change callsigns.

Edited by Harry Sugden

Share this post


Link to post
Share on other sites
Guest
This topic is now closed to further replies.
Sign in to follow this  

  • Similar Content

    • Sebastian Wheeler
      By Sebastian Wheeler
      Just a slight query related to the above:
      I was fortunate enough to partake in a weeks worth of work experience with NATS recently, and while at whitely on the ADC sims, I heard the following phraseology being used "G-ABCD, Cleared to enter controlled airspace via Route A, at or below altitude 2000 feet, QNH 1014."
      Upon asking one of the pseudo-pilots about the change, I was told it is "new phraseology" can anyone else confirm whether this is the case? Apparently, it was put in place after some confusion from pilots after receiving a "not above" clearance.
    • Chris Pawley
      By Chris Pawley
      Effective 26 April 2019
       
      Traffic inbound to Dublin is subject to the following revised agreement:-
      From Deancross  Rathlin to Antrim descending FL260 level TRN NELBO.
       
      The UK Sector File version 2019/05 is updated, in future, the agreed level diagrams will be updated to reflect this change.
       
    • Steve Riley
      By Steve Riley
      Just reading the new sid charts , am I right in saying hand offs are going to LONDON or SCOTTISH  and not radar as no mention of Radar on the charts.
      2. After departure, aircraft shall remain on the Tower frequency until instructed. 3. En-route cruising levels will be issued after take-off by 'London Control'. 4. Report callsign, SID designator, current altitude and cleared level on first contact with 'London Control'.
      I have not got the old charts to confirm this as I take them straight from NATS web site. 
      Also frequencies have changed are we changing them within ES ?
        123.980, 131.005  BIRMINGHAM APPROACH/RADAR
        118.305  BIRMINGHAM TOWER
      121.805  BIRMINGHAM GROUND 
       

       
       
    • Thomas Wowk
      By Thomas Wowk
      As above, how do you guys assess the runway surface condition on VATSIM? Do you make a visual assessment from the visual control room in correlation to the current/prevailing weather conditions or do you assess this purely off the METAR/TAF?
       
      The only reason i ask it that the surface condition of a runway really affects our landing performance (each operators SOP's may be different for the same aircraft type) Specifically if the runway is declared as DRY full length our crosswind limitations may be increased, whereas if the runway is declared WET full length, crosswind limitations are decreased. If i also needed to return after departure due to an emergency and perform an overweight landing, a DRY/WET surface also makes quite a difference for our overall LDA requirements. 
       
      Cheers
    • Thomas Wowk
      By Thomas Wowk
      Hi all,
       
      For the ones who enjoy carrying out IFR circuits in large aircraft, Doncaster Sheffield (EGCN) accepts visual circuits for aircraft above 5,700kg - B737/B757/B767/B747 etc. 
       
      The circuit profile & procedure can be found in the textual data in the AIP for EGCN. Primarily speaking only one aircraft can be in the circuit at a time. Be nice to get TWR on at EGCN from time to time to accept more training traffic within the network.
       
      The circuit profile briefly summarised as below:
       
      Visual circuits by aircraft above 5700 kg must comply with the following noise abatement procedures.
       
      i. Runway 02 After departure turn right crosswind at no greater than 2.5 DME, fly downwind at 2000 FT QNH, report final south of Bawtry (3 DME) and not below 1500 FT QNH.
      ii. Runway 20 After departure climb on track 190°, at 1.5 DME turn left crosswind, fly downwind at 2000 FT QNH and report final not below 1500 FT QNH
       
      Cheers.
       
       
×
×
  • Create New...