-
Notifications
You must be signed in to change notification settings - Fork 2
Sectors
Last updated: 2026-06-02
Sources: myVATSIM FIR list, Discord AIRAC Updates, AeroNav GNG Register, AeroNav Download Page, GitHub (VATSIM-SSA), Control Center Positions Export, Control Center Areas Export, GitHub Issue Template (AIRAC 2412 #44)
These are two distinct things that are often confused:
VATSIM FIRs are the official airspace designators registered in myVATSIM. They represent real-world (or simulated) FIR boundaries. A controller logs on to a VATSIM FIR position.
Sector Files are the operational packages managed in GitHub. A sector file may cover exactly one FIR, bundle several adjacent FIRs together into one file, or span a large combined area (FSS/oceanic). The sector file code does not always equal a VATSIM FIR code.
- Official VATSIM FIRs (24)
- Sector Files (25 GitHub Repos) — Types A–D
- Control Center Areas
- Discord Sections (aligned to Control Center areas)
- Combined Download Packages (FAXX)
- Full Source Comparison Matrix
- Positions Count by Sector
- Discrepancies (D1–D14)
- Items Requiring Action
- AIRAC Cycle & Current Update Status
- Current Discord Message (Canonical)
- AIRAC Deployment Workflow (per-sector checklist)
- Deployment Access & Progress
- Reference Data (leadership, URL patterns, GitHub org)
- Staffing Website — Airport Coverage & Detection Gaps
From myVATSIM — these are the authoritative VATSSA FIRs. All under Division: Sub-Sahara Africa.
| Code | Name | Sector File | Notes |
|---|---|---|---|
| DGAC | Accra | sectorfile-dgac | 1:1 |
| DNKK | Kano | sectorfile-dnkk | 1:1 |
| FACA | Cape Town | sectorfile-fasa | Bundled into FASA sector file |
| FAJA | Johannesburg | sectorfile-fasa | Bundled into FASA sector file |
| FAJO | Johannesburg Oceanic | sectorfile-fajo | Combined oceanic sector file |
| FBGR | Gaborone | sectorfile-fbgr | 1:1 |
| FCCC | Brazzaville | sectorfile-fccc | 1:1 |
| FIMM | Mauritius | sectorfile-fimm | 1:1 |
| FLFI | Lusaka | sectorfile-flfi | 1:1 |
| FMMM | Antananarivo | sectorfile-fmmm | 1:1 |
| FNAN | Luanda | sectorfile-fnan | 1:1 |
| FQBE | Beira | sectorfile-fqbe | 1:1 |
| FSSS | Seychelles | sectorfile-fsss | 1:1 |
| FVHF | Harare | sectorfile-fvhf | 1:1 |
| FWLL | Lilongwe | sectorfile-fwll | 1:1 |
| FYWH | Windhoek | sectorfile-fywf |
1:1 (repo naming discrepancy) |
| FZZA | Kinshasa | sectorfile-fzza | 1:1 |
| GLRB | Roberts | sectorfile-gooo | Bundled into GOOO sector file |
| GOOO | Dakar | sectorfile-gooo | 1:1 (sector file also covers GLRB) |
| GVSC | Sal | sectorfile-gvsc | 1:1 |
| HBBA | Bujumbura | sectorfile-htdc | Bundled into HTDC sector file |
| HKNA | Nairobi | sectorfile-hkna | 1:1 |
| HRYR | Kigali | sectorfile-htdc | Bundled into HTDC sector file |
| HTDC | Dar es Salaam | sectorfile-htdc | 1:1 (sector file also covers HBBA, HRYR) |
| HUEC | Entebbe | sectorfile-huec | 1:1 |
Note: GVSC (Sal/Cape Verde) has a sector file and GNG entry but is absent from myVATSIM. Needs to be registered.
Sector files are the operational packages. There are four types.
| Sector File | FIR Code | FIR Name | GitHub Repo |
|---|---|---|---|
| DGAC | DGAC | Accra | sectorfile-dgac |
| DNKK | DNKK | Kano | sectorfile-dnkk |
| FBGR | FBGR | Gaborone | sectorfile-fbgr |
| FCCC | FCCC | Brazzaville | sectorfile-fccc |
| FIMM | FIMM | Mauritius | sectorfile-fimm |
| FLFI | FLFI | Lusaka | sectorfile-flfi |
| FMMM | FMMM | Antananarivo | sectorfile-fmmm |
| FNAN | FNAN | Luanda | sectorfile-fnan |
| FQBE | FQBE | Beira | sectorfile-fqbe |
| FSSS | FSSS | Seychelles | sectorfile-fsss |
| FVHF | FVHF | Harare | sectorfile-fvhf |
| FWLL | FWLL | Lilongwe | sectorfile-fwll |
| FYWH | FYWH | Windhoek |
sectorfile-fywf |
| FZZA | FZZA | Kinshasa | sectorfile-fzza |
| GOOO | GOOO | Dakar | sectorfile-gooo |
| GVSC | GVSC | Sal |
sectorfile-gvsc |
| HKNA | HKNA | Nairobi | sectorfile-hkna |
| HUEC | HUEC | Entebbe | sectorfile-huec |
These sector files package multiple adjacent VATSIM FIRs into one file for operational convenience.
| Sector File | Covers FIRs | GitHub Repo |
|---|---|---|
| FASA | FACA (Cape Town) + FAJA (Johannesburg) | sectorfile-fasa |
| HTDC | HTDC (Dar es Salaam) + HBBA (Bujumbura) + HRYR (Kigali) | sectorfile-htdc |
| GOOO | GOOO (Dakar) + GLRB (Roberts) | sectorfile-gooo |
Note: FASA is a sector file name only — there is no VATSIM FIR called FASA. The actual FIRs are FACA and FAJA.
Oceanic sector files covering large oceanic areas. FAJO is a registered VATSIM FIR; GOOOO is an operational construct only (not a VATSIM FIR). In release/Discord branding these are published under "Africa Oceanic" names — the display code differs from the file/repo code:
- AFOS (Africa Oceanic South) → file/repo FAJO
- AFOW (Africa Oceanic West) → file/repo GOOOO
| Sector File | Release Name | VATSIM FIR? | GitHub Repo | Download URL | Notes |
|---|---|---|---|---|---|
| FAJO | AFOS — Africa Oceanic South | ✓ Yes | sectorfile-fajo | files.aero-nav.com/FAJO | Combined oceanic sector |
| GOOOO | AFOW — Africa Oceanic West | ✗ No | sectorfile-goooo | files.aero-nav.com/GOOOO | Includes DGAO (Accra Radio) and GOOC (Dakar Radio) oceanic positions; positions assigned to GOOO in control center |
These sector files span large areas across multiple FIRs for upper-level/FSS operations. They are not VATSIM FIRs — they are purely operational constructs. Released under "Africa ... FSS" names.
| Sector File | Release Name | VATSIM FIR? | GitHub Repo | Download URL |
|---|---|---|---|---|
| AFRC | Africa Central FSS | ✗ No | sectorfile-afrc | files.aero-nav.com/AFRC |
| AFRS | Africa South FSS | ✗ No | sectorfile-afrs | files.aero-nav.com/AFRS |
| AFRW | Africa West FSS | ✗ No | sectorfile-afrw | files.aero-nav.com/AFRW |
From areas_export_2026-06-02_195624.csv. These are the training/operational areas within VATSSA's control center system.
| area_id | Name |
|---|---|
| 1 | Southern Africa |
| 2 | Eastern Africa |
| 3 | Western Africa |
| 4 | Central Africa |
| 5 | Vanilla |
Southern Africa (1) FACA, FAJA, FASA (sector file), FAJO, FBGR, AFRS, FQBE, FVHF, FYWH
Eastern Africa (2) HKNA, HTDC, HBBA, HRYR, HUEC, FWLL
Western Africa (3) DGAC, DNKK, GOOO, GLRB, GVSC, AFRW
Central Africa (4) AFRC, FCCC, FLFI, FNAN, FZZA
Vanilla (5) FIMM, FMMM, FSSS
The Discord post is now structured to mirror the Control Center's five areas (Southern, Eastern, Western, Central, Vanilla) plus a combined "Oceanic and FSS" section. See the canonical message in Section 11.
| Discord Section | Sectors | Source CC Area |
|---|---|---|
| Southern Africa | FASA, FBGR, FQBE, FVHF, FYWH | area_id 1 |
| Eastern Africa | HKNA, HTDC, HUEC, FWLL | area_id 2 |
| Western Africa | DGAC, DNKK, GOOO, GVSC | area_id 3 |
| Central Africa | FNAN, FCCC, FLFI, FZZA | area_id 4 |
| Vanilla | FIMM, FMMM, FSSS | area_id 5 |
| Oceanic and FSS | AFRC, AFRS, AFRW, AFOS (FAJO), AFOW (GOOOO) | cross-area |
The original post used three loose groups — Central / West / South — written with little context. They did not match the Control Center:
- "Central" lumped together Eastern Africa (HKNA, HTDC, HUEC, FWLL) + Central Africa (FNAN, FZZA, FLFI) + a Vanilla sector (FSSS).
- "South" mixed Southern Africa with Central Africa (FCCC) and Vanilla (FIMM, FMMM).
- There was no Vanilla section at all — its three sectors were scattered.
- Oceanic and FSS packages were omitted entirely.
This is now fixed (see D13).
These are AeroNav download page constructs that bundle multiple sector files. They are not VATSIM FIRs and not GitHub repos.
| Code | Bundles | Available On |
|---|---|---|
| FAXX | AeroNav download page, GNG register |
| Code | Type | myVATSIM | Discord | GNG | Download | Control | GitHub | Positions |
|---|---|---|---|---|---|---|---|---|
| DGAC | FIR + SF (1:1) | ✓ | ✓ | ✓ | ✓ | ✓ | ✓ | ✓ |
| DNKK | FIR + SF (1:1) | ✓ | ✓ | ✓ | ✓ | ✓ | ✓ | ✓ |
| FACA | FIR (in FASA SF) | ✓ | ✗ | ✓ | via FASA | ✓ | via FASA | 1 pos |
| FAJA | FIR (in FASA SF) | ✓ | ✗ | ✓ | via FASA | ✓ | via FASA | ✓ |
| FAJO | FIR + SF (oceanic) | ✓ | ✓ as AFOS | ✓ | ✓ (AFOS) | ✓ | ✓ | ✓ |
| FASA | SF only (not a FIR) | ✗ | ✓ | ✓ | ✓ standalone | ✓ | ✓ | ✓ |
| FBGR | FIR + SF (1:1) | ✓ | ✓ | ✓ | ✓ | ✓ | ✓ | ✓ |
| FCCC | FIR + SF (1:1) | ✓ | ✓ | ✓ | ✓ | ✓ | ✓ | ✓ |
| FIMM | FIR + SF (1:1) | ✓ | ✓ | ✓ | ✓ | ✓ | ✓ | ✓ |
| FLFI | FIR + SF (1:1) | ✓ | ✓ | ✓ | ✓ | ✓ | ✓ | ✓ |
| FMMM | FIR + SF (1:1) | ✓ | ✓ | ✓ | ✓ | ✓ | ✓ | ✓ |
| FNAN | FIR + SF (1:1) | ✓ | ✓ | ✓ | ✓ | ✓ | ✓ | ✓ |
| FQBE | FIR + SF (1:1) | ✓ | ✓ | ✓ | ✓ | ✓ | ✓ | ✓ |
| FSSS | FIR + SF (1:1) | ✓ | ✓ | ✓ | ✓ | ✓ | ✓ | ✓ |
| FVHF | FIR + SF (1:1) | ✓ | ✓ | ✓ | ✓ | ✓ | ✓ | ✓ |
| FWLL | FIR + SF (1:1) | ✓ | ✓ | ✓ | ✓ | ✓ | ✓ | ✓ |
| FYWH | FIR + SF (1:1) | ✓ | ✓ | ✓ | ✓ | |||
| FZZA | FIR + SF (1:1) | ✓ | ✓ | ✓ | ✓ | ✓ | ✓ | |
| GLRB | FIR (in GOOO SF) | ✓ | ★ parenthetical | ✓ | ✗ | ✓ | via GOOO | via GOOO |
| GOOO | FIR + SF (multi) | ✓ | ✓ | ✓ | ✓ | ✓ | ✓ | ✓ |
| GOOOO | SF only (not a FIR) | ✗ | ✓ as AFOW | ✓ | ✓ | ✓ | ✓ | ✗ |
| GVSC | FIR + SF (1:1) | ✓ | ✓ | ✓ | ✓ | ✓ | ✓ | |
| HBBA | FIR (in HTDC SF) | ✓ | ★ parenthetical | ✓ | ✗ | ✓ | via HTDC | via HTDC |
| HKNA | FIR + SF (1:1) | ✓ | ✓ | ✓ | ✓ | ✓ | ✓ | ✓ |
| HRYR | FIR (in HTDC SF) | ✓ | ★ parenthetical | ✓ | ✗ | ✓ | via HTDC | via HTDC |
| HTDC | FIR + SF (multi) | ✓ | ✓ | ✓ | ✓ | ✓ | ✓ | ✓ |
| HUEC | FIR + SF (1:1) | ✓ | ✓ | ✓ | ✓ | ✓ | ✓ | |
| AFRC | SF only (FSS) | ✗ | ✓ | ✓ | ✓ | ✓ | ✓ | ✓ |
| AFRS | SF only (FSS) | ✗ | ✓ | ✓ | via AFRC | ✓ | ✓ | ✓ |
| AFRW | SF only (FSS) | ✗ | ✓ | ✓ | via AFRC | ✓ | ✓ | ✓ |
From positions_export_2026-06-02_195639.csv. Positions are assigned to sector file FIR codes, not always to individual VATSIM FIR codes (e.g. HBBA, HRYR positions appear under HTDC; GLRB positions appear under GOOO).
| FIR / Sector | Positions | Control Center Area |
|---|---|---|
| FASA (covers FACA+FAJA) | 71 | Southern Africa |
| DNKK | 37 | Western Africa |
| GOOO (covers GLRB) | 33 | Western Africa |
| FZZA | 22 | Central Africa |
| HKNA | 23 | Eastern Africa |
| FNAN | 17 | Central Africa |
| FYWF (FYWH) | 14 | Southern Africa |
| FCCC | 16 | Central Africa |
| FBGR | 12 | Southern Africa |
| FVHF | 13 | Southern Africa |
| FQBE | 13 | Southern Africa |
| DGAC | 13 | Western Africa |
| FLFI | 12 | Central Africa |
| GVSC | 12 | Western Africa |
| FMMM | 9 | Vanilla |
| HTDC (covers HBBA+HRYR) | 10 | Eastern Africa |
| FIMM | 7 | Vanilla |
| HUEN (HUEC) | 6 | Eastern Africa |
| FSSS | 6 | Vanilla |
| FWLL | 6 | Eastern Africa |
| FAJO | 4 | Southern Africa |
| AFRC | 1 | Central Africa |
| AFRS | 1 | Southern Africa |
| AFRW | 2 | Western Africa |
| GOOOO | 0 | Western Africa (positions assigned to GOOO) |
| DIII (Abidjan) | 6 | Western Africa |
| FACA (Cape Town FIR) | 1 | Southern Africa |
The VATSIM FIR code (myVATSIM) and GNG register both use FYWH. However the GitHub repo is named sectorfile-fywf, the control center positions export uses FYWF as the FIR field, and older documents use FYWF. FYWH is correct — repo and positions need updating.
All sources use HUEC except the positions export which uses HUEN in the FIR field (even for the position callsign HUEC_CTR). HUEN is Entebbe airport code — it leaked into the FIR field by mistake. HUEC is correct — positions need fixing.
The Discord AIRAC post has FZAA — confirmed typo. All other sources use FZZA.
GVSC (Sal/Cape Verde) has a GitHub repo, GNG entry, 12 positions, and a download package but is not registered as a FIR in myVATSIM. This is a VATSIM-side registration error, not a VATSSA data problem.
➡️ Action: Follow up with VATSIM Staff to register GVSC as an official FIR in myVATSIM. Once added, the official FIR count becomes 25.
FIR code DIII (Abidjan, Côte d'Ivoire) has 6 positions in the control center assigned to Western Africa, but has no GitHub repo, no GNG entry, and is not in the myVATSIM list. Either a repo/GNG entry needs creating, or the positions should be reassigned (possibly to DGAC) or removed.
FACA is the real VATSIM FIR for Cape Town. In the positions export, however, almost all Cape Town positions are assigned to fir=FASA (the sector-file bundle code) — e.g. FACT_DEL, FACT_TWR, FACT_APP, FACA_CTR, FACA_E_CTR. Only FACT_GND (Cape Town Ground) uses fir=FACA, the actual FIR code.
This is a consistency issue, not a wrong entry — FACA is valid. A decision is needed on whether the control center should assign Cape Town positions to the real FIR code (FACA) or to the sector-file code (FASA), then apply it uniformly. Currently it is mixed.
Several ground positions in GOOO (Dakar) and DGAC (Accra) have area_id=2 (Eastern Africa) despite both FIRs being in Western Africa (area_id=3). All other position types (TWR, APP, CTR) in those FIRs correctly use area_id=3. Appears to be data entry errors.
Affected: GOBD_GND, GOOY_GND (GOOO); DGAA_GND (DGAC).
The earlier Discord post omitted FAJO, GOOOO, AFRC, AFRS, AFRW. The updated post now adds a combined "Oceanic and FSS" section covering all five, using release names: AFRC/AFRS/AFRW (FSS), AFOS (= FAJO), AFOW (= GOOOO). All currently AIRAC2602 🟡.
FASA is updated and released as its own standalone package (files.aero-nav.com/FASA) — this is the one actively maintained and used in the Discord post. The role of FAXX is therefore unclear: it may be a legacy/superseded combined package, an alias, or something else. The earlier assumption that "FASA is only available via FAXX" appears to be incorrect.
➡️ Follow-up (ties to D11): confirm whether FAXX is still live, deprecated, or a duplicate now that FASA is released standalone.
Expected behaviour: GOOOO (released as AFOW — Africa Oceanic West) is an operational oceanic construct. Its oceanic positions are assigned to fir=GOOO in the control center rather than to GOOOO. The AFOW package covers the western oceanic radio positions: DGAO (Accra Radio — DGAO_CTR, fir=DGAC) and GOOC (Dakar Radio — GOOC_FSS, GOOC_A_FSS, GOOC_B_FSS, fir=GOOO).
FAXX appears on the AeroNav download page and GNG register as a combined VATSSA package, but its exact contents are not confirmed. It was assumed to be FASA + FAJO (South Africa + Johannesburg Oceanic), but this is a guess.
Since FASA is released as its own standalone package (see D9), FAXX is likely not the live South Africa package. It may be legacy, a duplicate, or bundle something else entirely.
➡️ Action: Find out what FAXX actually is — whether it is still live, what it bundles, and how it relates to the standalone FASA and FAJO (AFOS) packages. Do not assume it equals FASA + FAJO.
The GNG register lists HRYR as "VATSSA Kigalo" — a typo for Kigali (confirmed by myVATSIM "KIGALI"). Cosmetic; worth fixing in GNG when convenient.
The original Discord post used ad-hoc Central / West / South groups with no Vanilla section, scattering the Vanilla sectors (FIMM, FMMM → "South"; FSSS → "Central") and merging Eastern + Central CC areas under "Central". The post is now restructured to mirror the five CC areas — Southern, Eastern, Western, Central, Vanilla — plus Oceanic and FSS. See Sections 4 and 11.
The staffing website builds each FIR's airport list by pulling from myVATSIM, matching on the first two letters of the FIR code. This silently misses any airport whose ICAO prefix differs from the FIR code — and several VATSSA FIRs staff airports across national/prefix boundaries. Those airports will never be auto-populated or flagged. See Section 15 for the mechanism and the full deviation list.
| # | Item | Priority |
|---|---|---|
| 1 | Rename GitHub repo sectorfile-fywf → sectorfile-fywh and update positions FYWF → FYWH
|
High |
| 2 | Fix positions export: HUEN → HUEC in fir column for all Entebbe positions |
High |
| 3 | Follow up with VATSIM Staff to register GVSC (Sal) in myVATSIM — VATSIM-side error | High |
| 4 | Find out what FAXX actually is — whether it's still live/legacy and what it bundles. FASA is released standalone, so FAXX ≠ FASA+FAJO as previously guessed; see D9 + D11 | High |
| 5 | Clarify DIII (Abidjan) — create repo + GNG entry, or reassign/remove positions | Medium |
| 6 | Decide canonical FIR code for Cape Town positions (FACA vs FASA) and apply uniformly; see D6 |
Medium |
| 7 | Fix positions export: GOBD_GND, GOOY_GND area_id=2 → 3
|
Medium |
| 8 | Fix positions export: DGAA_GND area_id=2 → 3
|
Medium |
| 9 | Staffing website: compile/document the source for its airport list (where the master airport list comes from); see §15 | Medium |
| 10 | Staffing website: cross-check Control Center positions/airports against the site + VATSpy data | Medium |
| 11 | Staffing website: manually add/flag the cross-border airports (DB, DX, FD, FX, FE, FG, FK, FO, FP, FJ, FH, GA, GB, GF, GG, GQ, GU) that prefix-matching won't detect; see §15 | Medium |
| ✅ |
FZAA → FZZA typo |
Resolved |
| ✅ |
|
Resolved |
| ✅ |
|
Resolved |
- Latest cycle: AIRAC2605 🟢
- Behind: AIRAC2602 🟡
- Legend: 🟢 green = updated to latest AIRAC · 🟡 orange = not yet updated to latest
| Status | Cycle | Sectors |
|---|---|---|
| 🟢 Updated | AIRAC2605 | FASA, HKNA, HTDC, HUEC |
| 🟡 Behind | AIRAC2602 | FNAN, FZZA, FWLL, FSSS, FLFI, GOOO, GVSC, DGAC, DNKK, FBGR, FCCC, FIMM, FMMM, FQBE, FVHF, FYWH, FAJO (AFOS), GOOOO (AFOW), AFRC, AFRS, AFRW |
This is the maintained "AIRAC Updates — Sector Updates" post. Each line is wrapped in inline-code backticks; the URL sits outside the backticks. Notes in parentheses indicate bundled sub-sectors.
Section structure now mirrors the Control Center areas (Southern / Eastern / Western / Central / Vanilla) plus a combined Oceanic and FSS section — see D13 for why the old Central/West/South grouping was dropped.
**AIRAC Updates** — Sector Updates
**Southern Africa**
`🟢 FASA | AIRAC2605 |` https://files.aero-nav.com/FASA (includes FACA and FAJA)
`🟡 FBGR | AIRAC2602 |` https://files.aero-nav.com/FBGR
`🟡 FQBE | AIRAC2602 |` https://files.aero-nav.com/FQBE
`🟡 FVHF | AIRAC2602 |` https://files.aero-nav.com/FVHF
`🟡 FYWH | AIRAC2602 |` https://files.aero-nav.com/FYWH
**Eastern Africa**
`🟢 HKNA | AIRAC2605 |` https://files.aero-nav.com/HKNA
`🟢 HTDC | AIRAC2605 |` https://files.aero-nav.com/HTDC (includes HBBA and HRYR)
`🟢 HUEC | AIRAC2605 |` https://files.aero-nav.com/HUEC
`🟡 FWLL | AIRAC2602 |` https://files.aero-nav.com/FWLL
**Western Africa**
`🟡 DGAC | AIRAC2602 |` https://files.aero-nav.com/DGAC
`🟡 DNKK | AIRAC2602 |` https://files.aero-nav.com/DNKK
`🟡 GOOO | AIRAC2602 |` https://files.aero-nav.com/GOOO (includes GLRB)
`🟡 GVSC | AIRAC2602 |` https://files.aero-nav.com/GVSC
**Central Africa**
`🟡 FNAN | AIRAC2602 |` https://files.aero-nav.com/FNAN
`🟡 FCCC | AIRAC2602 |` https://files.aero-nav.com/FCCC
`🟡 FLFI | AIRAC2602 |` https://files.aero-nav.com/FLFI
`🟡 FZZA | AIRAC2602 |` https://files.aero-nav.com/FZZA
**Vanilla**
`🟡 FIMM | AIRAC2602 |` https://files.aero-nav.com/FIMM
`🟡 FMMM | AIRAC2602 |` https://files.aero-nav.com/FMMM
`🟡 FSSS | AIRAC2602 |` https://files.aero-nav.com/FSSS
**Oceanic and FSS**
`🟡 AFRC Africa Central FSS | AIRAC2602 |` https://files.aero-nav.com/AFRC
`🟡 AFRS Africa South FSS | AIRAC2602 |` https://files.aero-nav.com/AFRS
`🟡 AFRW Africa West FSS | AIRAC2602 |` https://files.aero-nav.com/AFRW
`🟡 AFOS Africa Oceanic South | AIRAC2602 |` https://files.aero-nav.com/FAJO
`🟡 AFOW Africa Oceanic West | AIRAC2602 |` https://files.aero-nav.com/GOOOO (includes DGAO and GOOC)
Notes for the post:
-
FASAline is correct (FASA is released standalone).FAXXis a separate unresolved item (see D9/D11) and is not part of this post. - The FSS sectors (AFRC/AFRS/AFRW) belong to Central/Southern/Western CC areas respectively but are grouped under "Oceanic and FSS" for clarity, since they are wide-area FSS packages rather than single FIRs.
Each AIRAC cycle, a GitHub tracking issue is opened in sectorfile-overview (e.g. issue "AIRAC 2412 #44"). Every sector gets the following checklist:
### [<CODE> <Name>](https://github.com/VATSIM-SSA/sectorfile-<code>)
- [ ] Sector File Control Package
- [ ] Review Pending Pull Requests
- [ ] Make GitHub release (tag, release notes)
- [ ] Update GitHub milestone
- [ ] [Open GNG](https://gng.aero-nav.com/<CODE>/)
- [ ] Pull GitHub Main to GNG
- [ ] Ensure all files are checked
- [ ] Publish Install Package
- [ ] Create release notes from GitHub release notes
- [ ] Update discord messageThe full per-sector issue body (all 25 sectors, grouped Standard / Oceanic / FSS, with repo + GNG links filled in) was generated earlier this session and can be regenerated from the data in Sections 1–2.
Current progress: 4 / 25 sectors complete (16%).
GNG access is currently held for 12 sectors. Grouping for the active deployment:
| Group | Meaning | Sectors |
|---|---|---|
| Group 3 — Done | Updated to AIRAC2605 | FASA, HKNA, HTDC, HUEC |
| Group 1 — To Do (access available) | Have GNG access, not yet done | AFRC, AFRS, AFRW, DGAC, FZZA, GOOO, GOOOO, GVSC |
| Group 2 — Needs access | No GNG access yet | DNKK, FBGR, FCCC, FIMM, FLFI, FMMM, FNAN, FQBE, FSSS, FVHF, FWLL, FYWH, FAJO |
GNG access currently held (12): AFRC, AFRS, AFRW, DGAC, FASA, FZZA, GOOO, GOOOO, GVSC, HKNA, HTDC, HUEC.
All VATSSA vACCs/sectors are listed in the GNG register under leader Miguel Albano but its going to be transferred to our new division director, Wian Saptouw.
myVATSIM Division: Sub-Sahara Africa (all 24 FIRs).
| Resource | Pattern |
|---|---|
| GitHub sector repo |
https://github.com/VATSIM-SSA/sectorfile-<code> (lowercase) |
| GNG admin page | https://gng.aero-nav.com/<CODE>/ |
| AeroNav download/files | https://files.aero-nav.com/<CODE> |
There are two separate data sources in play, which is the root of the gap:
-
Positions — currently sourced from Control Center (CC) data (the
positions_exportanalysed in this doc). This is the authoritative list of what VATSSA actually staffs. -
Airports — pulled from myVATSIM, matched on the first two letters of the FIR code (the myVATSIM FIR codes). For example, FIR
FYWH→ allFY**airports (Namibia).
Because positions come from CC but airports come from a myVATSIM prefix-match, the two can diverge: a position can exist in CC for an airport whose prefix the myVATSIM match never pulls in.
This prefix-matching silently misses any airport whose ICAO prefix differs from its FIR code. Several VATSSA FIRs control airspace across national borders, so they staff airports with prefixes that don't match — and those airports will never be auto-populated, and any deviation won't be flagged by the system.
Because there is no master source feeding these in, they have to be added/checked manually.
Covered prefixes (from the 24 myVATSIM FIRs + GVSC): DG, DN, FA, FB, FC, FI, FL, FM, FN, FQ, FS, FV, FW, FY, FZ, GL, GO, GV, HB, HK, HR, HT, HU. Anything below falls outside that set:
| FIR (sector) | Missed prefix | Country / area | Example airports in positions |
|---|---|---|---|
| DGAC | DB | Benin | DBBB (Cotonou) |
| DGAC | DX | Togo | DXXX (Lomé), DXNG (Niamtougou) |
| FASA | FD | Eswatini | FDMS (Manzini), FDSK (Sikhuphe) |
| FASA | FX | Lesotho | FXMM (Maseru) |
| FCCC | FE | Central African Rep. | FEFF (Bangui) |
| FCCC | FG | Equatorial Guinea | FGSL (Malabo) |
| FCCC | FK | Cameroon | FKKD (Douala), FKYS (Yaoundé), FKKL/FKKN/FKKR |
| FCCC | FO | Gabon | FOOL (Libreville), FOOG (Port-Gentil), FOON |
| FCCC | FP | São Tomé | FPST (São Tomé) |
| FIMM | FJ | BIOT | FJDG (Diego Garcia) |
| FNAN | FH | St Helena | FHSH (St Helena) |
| GOOO | GA | Mali | GAAA (Bamako), GABS, GAKD, GAMB |
| GOOO | GB | Gambia | GBYD (Banjul) |
| GOOO | GF | Sierra Leone | GFLL (Freetown) |
| GOOO | GG | Guinea-Bissau | GGOV (Bissau) |
| GOOO | GQ | Mauritania | GQNO (Nouakchott), GQPP, GQQQ |
| GOOO | GU | Guinea | GUCY (Conakry), GUOK |
| DIII (unregistered) | DI | Côte d'Ivoire | DIAP (Abidjan), DIBK, DISP, DIYO (also see D5) |
FCCC and GOOO are the worst affected — each controls 5–6 foreign prefixes that the staffing site cannot see.
HB (Bujumbura), HR (Rwanda) and GL (Roberts) airports are staffed under HTDC / HKNA / GOOO in the Control Center, but myVATSIM has HBBA, HRYR, GLRB as separate FIRs. So the staffing site will associate those airports with the standalone FIR rather than the bundled sector. Detectable, but the FIR↔sector mapping is inconsistent (ties to the Type B bundling in Section 2).
- Compile/document the source the staffing site should use for airports (where the master airport list comes from).
- Cross-check Control Center positions/airports against the staffing site and VATSpy data.
- Manually flag and add the cross-border airports above, since prefix-matching won't surface them.