-
Notifications
You must be signed in to change notification settings - Fork 126
Sector Ownership
The Sector Ownership
folder is divided into the primary sector groupings used across all sectors in the UK. In addition, there is a folder for Alternate
and Non-UK
. Each folder for the primary sectors contains a number of files depending on how the airspace is defined (see below). The Alternate
folder contains definitions for the adjacent airports definitions. The Non-UK
folder contains sector definitions for our neighbours.
The UK follows two conventions for airspace definition:-
Here airspace is divided into the smallest openable sectors on VATSIM (e.g. AC Central is divided into AC Daventry and AC Clacton)
Here airspace is divided into the smallest sectors that exist, and then VATSIM combines these sectors (e.g. PX Rathlin East and PX Rathlin West combine on VATSIM to be PX Rathlin)
We are currently in transition towards the new system. As a result, the below shows the current status.
-
PX East (New)
- Hebrides
- Humber
- Montrose
- Moray
- Tyne
-
PX West (New)
-
Central (Hi)
-
Deancross
-
Rathlin
-
Terminal Control
- Antrim
- Central (Lo)
- Galloway
- Talla
- Tay
-
-
AC North (New)
-
Sector 3 (Lakes)
-
Sector 4 (Lakes)
-
Sector 7 (Lakes)
-
Sector 10 (North Sea)
-
Sector 11 (North Sea)
-
Manchester Prestwick Control (MPC)
- North
- East
- Sector 29
- STAFA
- Trent
- Wallasey
- Isle of Man
-
-
AC West (New)
- Sector 5
- Sector 6/36 combined
- Sector 8
- Sector 9
- Sector 23
- Sector 35
- UL18
-
AC Central (New)
-
Sector 27 (Daventry)
-
Sector 28 (Daventry)
-
Sector 32 (Daventry)
-
Sector 12 (Clacton)
-
Sector 13 (Clacton)
-
Sector 14 (Clacton)
-
Terminal Control (North and East)
- ABBOT
- TC LAM
- TC LOREL
- TC NE Deps
- TC NW
- TC DAGGA
- TC JACKO
- TC REFSO
- TC SABER
-
-
AC South (Old)
-
Worthing
-
Dover
-
Terminal Control (South & Capital)
- TC SE
- TC SW
- TC CPT (part of Worthing on VATSIM)
- TC VATON (part of Worthing on VATSIM)
-
SECTOR:Central 2 (DB-255):0:25000
OWNER:SC:SW:SWD:S
ALTOWNER:Observing Scottish FIR:O:SM:SC:SW:SWD:S
ALTOWNER:Observing Scottish FIR (excl. STC_CTR):O:SM:SC:SW:SWD:S
BORDER:Cen_DCS-N:Mon_Wes-Cen 1:Mon_Wes-Cen 2:Wes-Cen_Gal:Wes-Cen_Ant:DCS-S_RatW:Cen_DCS-S
- SECTOR: Any Name for that airspace, normally numbered according to documentation and the levels: Base of Airspace:Top of Airspace
- OWNER: The list of positions who owns this airspace, with the first in the list having priority over the second and so on.
- ALT OWNER: The list for observing this airspace
- BORDER:A closed border of lines separated by
:
with each line defined in the Sector Boundaries section
For Sector File Users:
For Developers:
- First Time Contributor's Guide
- WIP: The AIRAC Process on GitHub
- Contributing Guide
- More specifically, on submitting pull requests...
- Coordinates
- How to Create SMR Displays
- Using GitHub Labels
- Using Milestones
- Using Projects
Repository Folders:
- Root
- _data
- ARTCC
- ATS Routes
- Agreements
- Airports
- Area Positions
- Doc
- Misc Geo
- Misc Other
- Misc Regions
- Navaids (Fixes/NDBs/VORs)
- Radar Maps (Stars)
- Sector Boundaries
- Sector Ownership
File Contents: