-
Notifications
You must be signed in to change notification settings - Fork 168
Add sectorization for VVHM FIR, modified airport data #1072
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Conversation
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.
|
Validate data: https://vatsim-radar.com/data/vatspy/1072/compare For controllers data testing visit https://docs.vatsim-radar.com/contributing/debug.html |
|
Contributor data:
|
Error in callsign has been fixed
|
@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. |
|
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 |
|
What is the reason for VVCL now being XVCL, yet both are still specified under the county Vietnam? |
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. |
|
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. |
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:

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

Modified intersection between VLVT/VDPF/VVHM/VVHN:

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

Modified FIR border between VVHM and VDPF with more precision :

Small overlap between VVHN/VVHN-1/VLVT has been fixed.
Slight modified sector name as follow:
Modified airport data:
Approved contributior?