Skip to content

Conversation

@AnTruongTV
Copy link
Contributor

Description of changes

Added Sector 1 to 7 for VVHM
Modify airport data within Viet Nam.
Modify FIR along the border between Viet Nam and Cambodia
Fixed overlap between VVHN/VVHN-1/VLVT.

Reason and motivation

Improve displacement for each sector within VVHM CTR, instead of display a whole bandbox causing aircraft calling when they not actually in that sector airspace.

New sectorization:
image

This has been configured to comply with VCLvACC enroute sectors assume control:
image

Modified intersection between VLVT/VDPF/VVHM/VVHN:
image

According to real life, these 4 FIR merged at D02, all FIR already modified to match with real life:
image

Modified FIR border between VVHM and VDPF with more precision :
image

Small overlap between VVHN/VVHN-1/VLVT has been fixed.

Slight modified sector name as follow:

  • All sector remove "Control" at last
  • Re-added "Control" from "Vietnam|VV| " to "Vietnam|VV|Control"
  • "VVCL" previous display "Mekong Control" because it have prefix "VV", now modified to "VCL" instead, borrow prefix "VC" because prefix "VC" belongs to Sri Lanka and call "Radar" which will make "VCL" to showing on map as "Mekong Radar" which is the correct callsign we looking for.

Modified airport data:

  • Removed VVNT which is not existed anymore.
  • Modified name for some airport.
  • Added airport data for some airport.

Approved contributior?

  • I am on the approved contributers list
  • I have sent an request by email to get approved
  • Someone on the approved contributer list will review this request

Added sector 1 to 7 for VVHM
Modified data for airport within VCL, removed non existed airport, added data for some airport within Viet Nam.
@github-actions
Copy link

github-actions bot commented Nov 2, 2025

@github-actions
Copy link

github-actions bot commented Nov 2, 2025

Contributor data:

  • CID: 1634146
  • Name: Nguyen An Truong
  • Region: VATSEA / Vietnam-Cambodia-Laos
  • Role: N/A
  • Approving CID: 1357854
  • Approving staff: Amos Ng

Error in callsign has been fixed
@amosngSP
Copy link
Contributor

@AnTruongTV As spoken, VCL FIR Code will make it show up as part of Sri Lanka. You can revise it and use a FIR code not used by other countries.

@AnTruongTV
Copy link
Contributor Author

Removed all military airport is needed, we have real life frequency attach to those airport, I dont want to explain with national defense about those, so better just remove them all together, on the list now should be only civil airport/civil mixed military airport, all military airport has been removed from database

@Adrian2k
Copy link
Collaborator

What is the reason for VVCL now being XVCL, yet both are still specified under the county Vietnam?
Wouldnt it be more logical to keep it as VVCL and add VCL as secondary (basically the way you have done it with XVCL now)

@amosngSP
Copy link
Contributor

What is the reason for VVCL now being XVCL, yet both are still specified under the county Vietnam?
Wouldnt it be more logical to keep it as VVCL and add VCL as secondary (basically the way you have done it with XVCL now)

VCL doesn't cover just Vietnam. It covers the airspace of 4 countries. We wanted a better way to reflect its callsign and country neutrality.

VCL by itself wasn't an option as this would show it under Sri Lanka.

@AnTruongTV
Copy link
Contributor Author

As Amos said, VCL covered 4 FIRs to be exact, its 3 country, using VCL only was my plan from the beginning but it conflict with VC from Sri Lanka, if there was any special rules to show just VCL - Mekong RADAR it will be great. VVCL before work but the callsign shown is Mekong CONTROL instead.

@Adrian2k Adrian2k merged commit 8fa858b into vatsimnetwork:master Nov 26, 2025
3 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

4 participants