Jump to content
  • 0

Visiting airports


Filippo Genoni

Question

Filippo Genoni

Hi everyone, 

I’m interested in visiting here in Vatuk. I took a look to the visiting groups and at the airports but I don’t know any of those... which group do you suggest? Thank you 🙂

Link to post
Share on other sites

1 answer to this question

Recommended Posts

  • 3
Matthew Wilson

Hi Filippo

In answer to your question, it really depends on where you want to control. Most of the groups have at least a couple of airports from the bigger towns in the UK. It's just a case of choosing the ones you fancy.

Regards

Link to post
Share on other sites
  • Similar Content

    • Brooklyn Grantham
      By Brooklyn Grantham
      As with many members within the Vatsim UK discord. I'm sure we are all in agreement that we should have a separate channel on the discord for just talking about Vatsim ATC and Vatsim itself. I also feel we should have a real world chat on the Vatsim uk where members can discuss real things atc related etc.
       
      Would like to hear other members opinions on this!
    • Harry Sugden
      By Harry Sugden
      This post brings together links to all London (EGTT) - and Scottish (MPC) - documentation and additionally summarises the available positions, including under what conditions they may be opened.
       
      Documentation
      London (EGTT) Area vMATS Part 2 - spot a mistake, or have some feedback? Post in THIS thread. London Agreed Levels Diagrams - spot a mistake, or have some feedback? Post in THIS thread. London Sector Diagrams Current Supplementary Instructions (SIs)
      None Procedure Changes
      [Active] 2021-04-22 - London (South, Central & West) - Changes to South Sectorisation & Agreements Letters of Agreement (LoAs)
      Whilst the Operations Department aims to ensure the information in the vMATS is up to date, where there are conflicts, the LoA will override any procedures detailed in the vMATS Part 2, except where instructions are otherwise promulgated to the ATC Procedure Changes Forum.
      VATéir (Shannon & Dublin ACCs) & VATSIM UK (London ACC) LoA Dutch vACC (Amsterdam ACC & Maastricht UAC Delta) & VATSIM UK (London ACC) LoA Belux vACC (Brussels ACC & Maastricht UAC Koksy) & VATSIM UK (London ACC) LoA French vACC (Reims, Paris & Brest ACCs) & VATSIM UK (London ACC) LoA  
      Sectorisation
      Controller Bookings and Logging On
      In line with Division Policy and guidance on the VATSIM UK website: "Members may open either a single Primary or Secondary sector, or a valid combination of Primary or Secondary sectors."
      London Primary Sectors
      LON_S_CTR LON_C_CTR LON_N_CTR LON_W_CTR London (MPC) Secondary Sectors
      LON_M_CTR LON_E_CTR LON_D_CTR LTC_N_CTR LTC_S_CTR MAN_CTR To open any further splits of a Primary or Secondary sector, the remaining portion of that sector must be staffed too. For example, to open PC East (MAN_E_CTR) requires PC West (MAN_W_CTR) to be open, or covered by another controller. Or to open TC South East (LTC_SE_CTR), TC South West must be open or covered by another London controller.
      Controllers who booked a primary or secondary sector shall have first preference over the airspace they wish to control if a split of that primary/secondary sector wishes to log on (Div Pol 3.8 k). This applies too if LON_S_CTR is booked before someone else then books LTC_S_CTR; the controller who made the first booking for LON_S_CTR has the right to swap with a booking made at a later point for LTC_S_CTR. However, booking a bandbox such as LON_SC_CTR or LTC_CTR gives the controller no right to pick which airspace they control with precedence over subsequent bookings.
       
      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 - which are collected in a Local Area Group (LAG):
      South LAG: Worthing, Dover, TC South West, TC South East Central LAG: Daventry, Clacton, TC East, TC North West, TC North East North LAG: AC North, PC West, PC East West LAG: AC West  
      Controller Positions & Coordination Names
      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 LON_SC_CTR and LTC_S_CTR were logged on, LON_SC_CTR would be controlling the Daventry, Clacton, TC East, TC NW, TC NE, Worthing and Dover sectors, whilst LTC_S_CTR would be controlling the TC SW and TC SE sectors. If LTC_E_CTR then logged on, LON_SC_CTR would now be controlling the Daventry, Clacton, TC NW, Worthing and Dover sectors. The names of the positions (i.e. the callsign you use for coordination) sometimes change in London.
      LON_CTR (127.825) - always "(AC) Bandbox" LON_SC_CTR (132.600) - "AC South Central" - if the controller is left with just South/Central group sectors, as either South/Central South LAG
      LON_S_CTR - "AC South" - if Dover is opened, then the position becomes known as "(AC) Worthing" LON_D_CTR - always "(AC) Dover" LTC_S_CTR - "TC South" - if TC South West/TC South East is subsequently opened then the position becomes known as the remainder of the two LTC_SW_CTR - always "TC South West" LTC_SE_CTR -  always "TC South East" Central LAG
      LON_C_CTR - "AC Central" - if Daventry/Clacton is subsequently opened then the position becomes known as the remainder of the two LON_M_CTR - always "(AC) Daventry" LON_E_CTR - always "(AC) Clacton" LTC_E_CTR - always "TC East" LTC_N_CTR - "TC North" - if TC North West/TC North East is subsequently opened then the position becomes known as the remainder of the two LTC_NW_CTR - always "TC North West" LTC_NE_CTR -  always "TC North East" North LAG
      LON_N_CTR - always "AC North" MAN_CTR - "PC Bandbox" - if PC East/PC West is subsequently opened then the position becomes known as the remainder of the two MAN_E_CTR - always "PC East" MAN_W_CTR - always "PC West" West LAC
      LON_W_CTR (126.075) - always "(AC) West"
    • Harry Sugden
      By Harry Sugden
      This post brings together links to all Scottish (EGPX) documentation and additionally summarises the available positions, including under what conditions they may be opened.
       
      Documentation
      Scottish (EGPX) Area vMATS Part 2 - spot a mistake, or have some feedback? Post in THIS thread. Scottish Agreed Levels Diagrams - spot a mistake, or have some feedback? Post in THIS thread. Scottish Sector Diagrams Current Supplementary Instructions (SIs)
      None Procedure Changes
      [Active] 2021-03-07 - London & Scottish - Removal of Eurocontrol Islands Letters of Agreement (LoAs)
      Whilst the Operations Department aims to ensure the information in the vMATS is up to date, where there are conflicts, the LoA will override any procedures detailed in the vMATS Part 2, except where instructions are otherwise promulgated to the ATC Procedure Changes Forum.
      VATéir (Shannon & Dublin ACCs) & VATSIM UK (Scottish ACC) LoA VATSIM Scandinavia (Reykjavík ACC) & VATSIM UK (Scottish ACC) LoA VATSIM Scandinavia (Polaris ACC - Stavanger) & VATSIM UK (Scottish ACC) LoA VATSIM Scandinavia (Copenhagen ACC) & VATSIM UK (Scottish ACC) LoA Dutch vACC (Amsterdam ACC & Maastricht UAC Delta) & VATSIM UK (Scottish ACC) LoA  
      Sectorisation
      Controller Bookings and Logging On
      In line with Division Policy and guidance on the VATSIM UK website: "Members may open either a single Primary or Secondary sector, or a valid combination of Primary or Secondary sectors."
      Scottish Primary Sectors
      SCO_CTR (Scottish AC Bandbox) Scottish Secondary Sectors
      STC_CTR (Scottish TMA Bandbox) STC_A_CTR (Antrim) To open any further splits of a Primary or Secondary sector, the remaining portion of that sector must be staffed too. For example, to open SCO_W_CTR requires the remainder of the Scottish FIR to be staffed by another controller. Or to open Talla (STC_E_CTR), Galloway must be open or covered by another Scottish controller.
      Controllers who booked a primary or secondary sector shall have first preference over the airspace they wish to control if a split wishes to log on (Div Pol 3.8 k). This applies too if SCO_CTR is booked first, then that controller reserves the right to swap with a booking made at a later point for STC_CTR.
       
      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, with names in bold - some of which are collected in a Local Area Group (LAG):
      ScAC East LAG: North, South ScAC West LAG: West, Rathlin Deancross Scottish TMA: Galloway, Talla Antrim  
      Controller Positions & Coordination Names
      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 North, South, 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) very rarely change in Scottish.
      SCO_CTR (135.525) - always "Scottish Bandbox" SCO_WD_CTR (133.875) - "West-Deancross" - if West/Deancross is subsequently opened then the position becomes known as the remainder of the two SCO_D_CTR (135.850) - always "Deancross" ScAC East LAG
      SCO_E_CTR (121.325) - always "Scottish East" SCO_N_CTR (129.225) - always "Scottish North" SCO_S_CTR (134.775) - always "Scottish South" ScAC West LAG
      SCO_W_CTR (132.725) - always "Scottish West" SCO_R_CTR (129.1) - always "Rathlin" Low Level / TMA
      STC_CTR (126.3) - "Scottish TMA" - if Talla/Galloway is subsequently opened, then the position becomes known as the remainder of the two STC_E_CTR  (130.975) - always "Talla" STC_W_CTR (124.825) - always "Galloway" STC_A_CTR (123.775) - always "Antrim"
    • Henry Cleaver
      By Henry Cleaver
      /
    • Robin Meads
      By Robin Meads
      The new aircraft symbol on the Euroscope smr now looks like a fuzzy X shape and it is not possible to tell which way the a/c is facing unless it is moving. As a/c have a habit of pushing back the wrong way this can cause problems for giving taxi directions. I much prefer the previous symbol that looked like an a/c and showed its facing direction.

×
×
  • Create New...