Letter of Agreement (LOA) Between People's Republic of China Division (VATPRC) and Hong Kong vACC, Southeast Asia Division (VATSEA)

Revision 4

Date Issued: Nov 27, 2025

VATPRC Document Number: VATPRC-LOA-1-R4-EN

vACC Hong Kong Document Number: HKVACC-LOA-VATPRC-R4

1. Purpose

This Letter of Agreement (LOA) establishes standard procedures and coordination responsibilities of air traffic control between Guangzhou FIR (ZGZU), Shanghai FIR (ZSHA), Sanya FIR (ZJSA) of the People's Republic of China Division (VATPRC) and Hong Kong FIR (VHHK) of Hong Kong vACC, Southeast Asia Division (VATSEA).

2. Cancellation

This document supersedes any agreements previously established in verbal or written form between VATSEA and VATPRC.

3. Scope

3.1

The information contained herein is supplementary to the rules established under VATSIM regulations, Aeronautical Information Publication (AIP) of the Hong Kong Special Administrative Region published by the Hong Kong Civil Aviation Department, AIP (Publicações de Informações Aeronáuticas) of Macau Special Administrative Region published by the Civil Aviation Administration of Macau S.A.R. (Autoridade de Aviação Civil da RAEM) and the AIP of the People's Republic of China published by the Civil Aviation Administration of China (CAAC).

3.2

While such regulations shall generally be strictly followed on the VATSIM network, in some circumstances exemptions or modifications to the real-world regulations are necessary due to operational needs in an online environment. Such deviation shall be discussed in this document.

4. Disclosure

Both parties shall make this Letter of Agreement available for public access on their respective official websites. The information contained herein is for the exclusive use on the Virtual Air Traffic Simulation Network (VATSIM) only. Under no circumstances shall such information be used in the real world, including but not limited to, real-world air navigation or real-world air traffic control.

5. Language

This Letter of Agreement is officially and originally prepared and documented in the English language. Both parties are encouraged to translate this LOA into Traditional Chinese and/or Simplified Chinese for reference purposes, but this is optional. The English version of this LOA shall always prevail, and future revisions to this LOA shall be based upon the English version.

6. General Procedures

6.1

Unless otherwise stated or coordinated:

6.1.1

Enroute controllers (CTR) of both parties shall keep traffic away from the 5 nautical miles (nm) margin of the boundary between Hong Kong FIR (VHHK), Guangzhou FIR (ZGZU), Shanghai FIR (ZSHA) and Sanya FIR (ZJSA) under all circumstances. The margins on both sides constitute a buffer zone of a width of 10nm. Except during a standard handover procedure, the controller in charge of the corresponding airspace or sector must coordinate and point out such aircraft to the controller of the other party when it becomes necessary for traffic to enter or cross such margin.

6.1.2

Due to the proximity of the approach path of runway 07L at VHHH and runway 33/34 at ZGSZ, Controllers shall keep traffic away from the Hong Kong - Zhuhai Airspace Boundary Non-Transgression Zone, except when following a published procedure. Controllers should immediately vector the aircraft away from the Hong Kong - Zhuhai Airspace Boundary Non-Transgression Zone if a pilot deviates from a published procedure.

6.1.2.1

The Hong Kong - Zhuhai Airspace Boundary Non-Transgression Zone is defined as follows:

N021.37.33.223 E112.55.49.939

N021.31.58.768 E112.58.16.015

N021.38.09.770 E113.17.17.067

N021.39.01.179 E113.18.32.300

N021.49.52.182 E113.29.22.485

N021.50.03.922 E113.29.32.148

N021.59.57.924 E113.37.55.330

N021.59.57.539 E113.37.55.037

N022.04.35.539 E113.41.52.123

N022.08.04.418 E113.36.35.813

N022.03.26.419 E113.32.38.899

N022.03.26.034 E113.32.38.607

N021.53.32.036 E113.24.15.790

N021.53.43.781 E113.24.25.449

N021.43.31.152 E113.14.10.320

N021.37.33.223 E112.55.49.939

6.1.3

Controllers shall make every effort to follow the radar separation minima defined in ICAO Doc 4444. In addition, controllers shall also comply with the separation methods provided by the AIP of Hong Kong, the AIP of Macau, and the AIP of Mainland China.

6.1.3.1

As per ENR 2.2.2.3 Section 4.5 of AIP of Mainland China for IFR:

“For aircraft arriving at or departing from Macau at the same level and on the same route:

• Arrival: Minimum longitudinal separation shall be 5 minutes (or 30 NM) when the aircraft crosses the transfer of control point between Zhuhai Approach and Hong Kong.
• Departure: Minimum longitudinal separation shall be 5 minutes when aircraft crosses the transfer of control point between Macau and Zhuhai Approach.”

6.1.3.2

As per ENR 1.2 Section 4 of AIP of Mainland China for VFR:

“The separation between aircraft operating on the same track and at same altitude shall not be less than:

• 2000m①: when aircraft cruising indicated airspeed is less than 250km/h②; or
• 5000m①: when aircraft cruising indicated airspeed is 250km/h② or above.”

Remarks:

① 2000m = 1NM; 5000m = 3NM

② 250km/h = 135kt

6.1.4

Controllers of each side shall generally initiate each handover ten to thirty nautical miles (10-30 nm) before crossing the Transfer of Control Point (TCP). In the absence of identifiable operational conflicts, controllers are encouraged to initiate early transfer. Handoff must be completed at least ten nautical miles (10nm) for IFR or three nautical miles (3nm) for VFR from the TCP.

6.1.5

Conversion of altitude measurement units shall be performed according to Section 8 and Section 9 of this document prior to handoff.

6.1.6

No controller shall clear an aircraft directly to a waypoint outside of the FIR at which the controller controls unless prior coordination is made, and proper permission of such clearance is obtained. This also applies when there is no en-route/ terminal ATC available at the adjacent FIR through which a flight will transit.

6.1.7

Proper liaison between FIRs shall be established for handover. Controllers shall advise any cruising level changes (i.e., the altitude at which the aircraft will be flying during the handover) of a particular aircraft prior to entering neighboring FIR. As per ICAO Doc 4444 Section 5.3.3.1, aircraft may not be cleared to change altitude during a handoff unless prior clearance has been obtained from the accepting controller. Controllers may request an altitude different from the ones specified in Section 7 of this LOA document from the receiving controller with prior coordination.

6.1.8

Controllers shall ensure that all aircraft are flying under real-time speed (1x rate) prior to the initiation of a handover and during a handover. Crossing FIR boundary while under acceleration mode is strictly prohibited.

6.1.9

Enroute or Terminal controllers should advise controllers of the other FIR when a sector is combined or separated and provide corresponding information.

6.1.10

If the route of the filed flight plan of a flight flying between FIRs does not include a valid TCP or does not include an airway that contains the valid TCP, a controller shall amend the route of such flight plan following standard procedures as per ICAO Doc 4444 so that the amended route will include a valid TCP. If the pilot is unable to amend their route, proper coordination shall be made to accommodate such situations.

6.1.11

Controllers should refer to the Sector Ownership Priority table in Appendix B to determine which position to handoff to. If sectorization deviates from this standard (e.g., due to extra sectorization during events), controllers must explicitly coordinate this through ATC channels or otherwise.

7. Sector Definitions

7.1 Mainland China ATC

7.1.1 Zhuhai TMA

• Position: ZGJD_APP; Callsign: Zhuhai Approach
• In the absence of ZGJD_APP, the Guangzhou ACC controller shall be responsible for this sector.
• The horizontal boundary of Zhuhai TMA is shown in Figure 7.1
• The vertical boundary of Zhuhai TMA is GND-S0450 (F148)
• Handoffs to Zhuhai TMA shall be made in the following order: ZGJD_APP -> ZGGG_CTR -> ZGZU_CTR

Figure 7.1: Zhuhai TMA Sector

7.1.2 Shantou TMA

• Position: ZGOW_APP; Callsign: Shantou Approach
• In the absence of ZGOW_APP, the Guangzhou ACC controller shall be responsible for this sector.
• The Xiamen ACC controller shall be responsible for Shantou TMA when none of the Shantou TMA or Guangzhou ACC controllers are online.
• The horizontal boundary of Shantou TMA is shown in Figure 7.2
• The vertical boundary of Shantou TMA is GND-S0450 (F148)
• Handoffs to Shantou TMA shall be made in the following order: ZGOW_APP -> ZGGG_CTR -> ZGZU_CTR -> ZSAM_CTR -> ZSHA_CTR

Figure 7.2: Shantou TMA Sector

7.1.3 Zhanjiang TMA

• Position: ZGZJ_APP; Callsign Zhanjiang Approach
• In the absence of ZGZJ_APP, the Nanning ACC controller will take responsibility.
• The horizontal boundary of Zhanjiang TMA is shown in Figure 7.3
• The vertical boundary of Zhanjiang TMA is GND-S0600 (F197)
• Handoffs to Zhanjiang TMA shall be made in the following order: ZGZJ_APP -> ZGNN_CTR -> ZGZU_CTR

Figure 7.3: Zhanjiang TMA Sector

7.1.4 Guangzhou ACC

• Position: ZGGG_CTR; Callsign: Guangzhou Control
• In the absence of ZGGG_CTR, the Guangzhou FIR controller (ZGZU_CTR) shall be responsible for this sector.
• PRC_FSS (Callsign: Beijing Control) shall be responsible for Guangzhou ACC above S0780 (F256) (not incl.) when none of the Guangzhou ACC controllers are online.
• PRC_FSS can accept the handover on coordination, but only if their cruising level is higher than S0780 (F256).
• The horizontal boundary of Guangzhou ACC is shown in Figure 7.4
• Handoffs to Guangzhou ACC shall be made in the following order: ZGGG_CTR -> ZGZU_CTR -> PRC_FSS (Above S0780/F256)

Figure 7.4: Guangzhou ACC Sector

7.1.5 Sanya ACC

• Position: ZJSA_CTR; Callsign: Sanya Control
• There are 2 split sectors in Sanya ACC. Sanya ACC Land sector (ZJSY_L_CTR) and Sanya ACC Oceanic sector (ZJSY_O_CTR).
• The Sanya ACC Land sector covers the whole of Hainan Island and the upper airspace (S0780/F256 and above) of Zhanjiang TMA. This sector uses fully metric operations.
• The Sanya ACC Oceanic sector covers the oceanic area and uses fully imperial operations from F140 up to F410. The airspace below F140 is uncontrolled.
• PRC_FSS (Callsign: Beijing Control) shall be responsible for Sanya ACC above S0780 (F256) (not incl.) when none of the Sanya ACC controllers are online.
• PRC_FSS can accept the handover on coordination, but only if their cruising level is higher than S0780 (F256).
• The horizontal boundary of Sanya ACC is shown in Figure 7.5
• Handoffs to Sanya ACC shall be made in the following order: ZJSY_L_CTR/ZJSY_O_CTR -> ZJSA_CTR -> PRC_FSS (Above S0780/F256)

Figure 7.5: Sanya ACC Sector

7.1.6 Nanning ACC

• Position: ZGNN_CTR; Callsign: Nanning Control
• In the absence of ZGZJ_APP, the Nanning ACC controller shall be responsible for this sector.
• In the absence of ZGNN_CTR, the Guangzhou FIR controller (ZGZU_CTR) shall be responsible for this sector.
• The vertical airspace constraints of Nanning ACC in the area of SIKOU and above Zhanjiang TMA are S0600(F197)-S0780(F256).
• Controllers shall use caution when transferring aircraft to Nanning ACC to avoid transferring aircraft to the wrong controller.
• The horizontal boundary of Nanning ACC is shown in Figure 7.6
• Handoffs to Nanning ACC shall be made in the following order: ZGNN_CTR -> ZGZU_CTR

Figure 7.6: Nanning ACC Sector

7.1.7 Xiamen ACC

• Position: ZSAM_CTR; Callsign: Xiamen Control
• ZSAM_CTR shall be responsible for Shantou TMA when none of the Shantou TMA or Guangzhou ACC controllers are online.
• In the absence of ZSAM_CTR, the Shanghai FIR controller (ZSHA_CTR) shall be responsible for this sector.
• The vertical airspace constraints of Xiamen ACC in the area of DOTMI/LELIM and above Shantou TMA are S0450(F148)-S0780(F256).
• Controllers shall use caution when transferring aircraft to Xiamen ACC to avoid transferring aircraft to the wrong controller.
• The horizontal boundary of Xiamen ACC is shown in Figure 7.7
• Handoffs to Xiamen ACC shall be made in the following order: ZSAM_CTR -> ZSHA_CTR

Figure 7.7: Xiamen ACC Sector

7.1.8 Shanghai ACC

• Position: ZSSS_CTR; Callsign: Shanghai Control
• When Shanghai ACC South sector (ZSSS_S_CTR) is online, aircraft shall be handed off to this sector instead.
• In the absence of ZSSS_CTR and ZSSS_S_CTR, the Shanghai FIR controller (ZSHA_CTR) shall be responsible for this sector.
• PRC_FSS (Callsign: Beijing Control) shall be responsible for Shanghai ACC above S0780(F256) (not incl.) when none of the Shanghai ACC controllers are online.
• PRC_FSS can accept the handover on coordination, but only if their cruising level is higher than S0780 (F256).
• The horizontal boundary of Shanghai ACC is shown in Figure 7.8
• Handoffs to Shanghai ACC shall be made in the following order: ZSSS_S_CTR -> ZSSS_CTR -> ZSHA_CTR -> PRC_FSS (Above S0780/F256)

Figure 7.8: Shanghai ACC Sector

7.2 Hong Kong ATC

7.2.1 Hong Kong Departure South

• Position: VHHH_S_DEP; Callsign: Hong Kong Departure
• This sector covers ZGSZ/VMMC departures via LUKBU and VHHH RWY 07R / 25L departures.
• Hong Kong Departure South covers the airspace around LUKBU between SFC - FL130.
• Handoffs to Hong Kong Departure South shall be made in the following order:
  VHHH_S_DEP -> VHHH_N_DEP -> VHHH_APP -> HKG_W_CTR

Figure 7.9: Hong Kong Departure South Sector when runway 07s are in use

Figure 7.10: Hong Kong Departure South Sector when runway 25s are in use

7.2.2 Hong Kong Departure North

• Position: VHHH_N_DEP; Callsign: Hong Kong Departure
• This sector covers VHHH RWY 07L / 25R and RWY 07C / 25C departures. In the absence of VHHH_H_DEP, its responsibilities are assumed by this sector. The same applies to VHHH_S_DEP.
• Hong Kong Departure North covers the airspace around BEKOL between SFC - FL160.
• Handoffs to Hong Kong Departure North shall be made in the following order:
  VHHH_N_DEP -> VHHH_APP -> HKG_W_CTR

Figure 7.11: Hong Kong Departure North Sector when runway 07s are in use

Figure 7.12: Hong Kong Departure North Sector when runway 25s are in use

7.2.3 Hong Kong Departure (High)

• Position: VHHH_H_DEP; Callsign: Hong Kong Departure
• This sector covers ZGGG arrivals via TAMOT and VHHH/VHHX departures via BEKOL.
• Hong Kong Departure (High) covers the airspace around TAMOT between FL130 - FL250, and the airspace around BEKOL between FL160 - FL250.
• Handoffs to Hong Kong Departure shall be made in the following order:
  VHHH_H_DEP -> VHHH_DEP -> VHHH_APP -> HKG_W_CTR

Figure 7.13: Hong Kong Departure (High) Sector when runway 07s are in use

Figure 7.14: Hong Kong Departure (High) Sector when runway 25s is in use

7.2.4 Hong Kong Approach

• Position: VHHH_APP; Callsign: Hong Kong Approach
• This sector is the primary APP sector within Hong Kong vACC. While it does not cover any airspace at any boundary between VATPRC and HKvACC, it has been included here for completeness.

Figure 7.15: Hong Kong Approach Sector when runway 07s are in use

Figure 7.16: Hong Kong Approach Sector when runway 25s are in use

7.2.5 Hong Kong Terminal Radar West

• Position: VHHH_W_APP; Callsign: Hong Kong Radar
• This sector covers ZGSZ/ZGGG departures and VHHH arrivals via SIERA, as well as Hong Kong Terminal Radar Low and Macau Approach Radar sector in their absence.
• Hong Kong Terminal Radar West covers the airspace around SIERA between FL190 - FL250.
• Handoffs to Hong Kong Terminal Radar West shall be made in the following order:
  VHHH_W_APP -> HKG_W_CTR -> VHHH_APP

Figure 7.17: Hong Kong Terminal Radar West Sector

7.2.6 Hong Kong Terminal Radar Low

• Position: VHHH_L_APP; Callsign: Hong Kong Radar
• This sector is responsible for SIERA arrivals that have been handed off from Hong Kong Terminal Radar West and Macau Approach Radar sector in its absence. When this sector is open, FL190 is not available at SIERA.
• Hong Kong Terminal Radar Low covers the airspace around SIERA between FL120 and FL190.
• Handoffs to Hong Kong Terminal Radar Low shall be made in the following order: VHHH_L_APP -> VHHH_W_APP -> HKG_W_CTR -> VHHH_APP

7.2.7 Macau Approach Radar

• Position: VMMC_APP; Callsign: Hong Kong Radar
• This sector covers ZGSZ arrivals via LANDA and ZGSZ departures via SIERA. When Runway 16 is in use, this sector also covers VMMC arrivals entering Zhuhai airspace via INDUS as well as VMMC arrivals via UJ and MCU and oil rig support helicopters via Track D.
• Macau Approach Radar covers the airspace around LANDA and SIERA between SFC - FL120.
• Handoffs to Macau Approach Radar shall be made in the following order: VMMC_APP -> VHHH_L_APP -> VHHH_W_APP -> HKG_W_CTR -> VHHH_APP

Figure 7.18: Macau Approach Radar Sector

7.2.8 Hong Kong Area Radar East Arrivals

• Position: HKG_K_CTR; Callsign: Hong Kong Radar
• This sector covers traffic via DOTMI and LELIM.
• Hong Kong Area Radar East Arrivals covers the airspace around DOTMI and LELIM between SFC - UNL. (SFC - FL365 when Hong Kong Area Radar Upper is online)
• Handoffs to Hong Kong Area Radar East Arrivals shall be made in the following order:
  HKG_K_CTR -> HKG_E_CTR -> HKG_S_CTR -> HKG_W_CTR

Figure 7.19: Hong Kong Area Radar East Arrivals Sector

7.2.9 Hong Kong Area Radar West (TRD)

• Position: HKG_D_CTR; Callsign: Hong Kong Radar
• This sector covers traffic via EPKAL and DOSUT.
• Hong Kong Area Radar West (TRD) covers the airspace around EPKAL and DOSUT between SFC - UNL. (SFC - FL365 when Hong Kong Area Radar Upper is online)
• Handoffs to Hong Kong Area Radar West (TRD) shall be made in the following order:
  HKG_D_CTR -> HKG_V_CTR -> HKG_W_CTR

Figure 7.20: Hong Kong Area Radar West (TRD) Sector

7.2.10 Hong Kong Area Radar West (TRV)

• Position: HKG_V_CTR; Callsign: Hong Kong Radar
• This sector covers traffic via IKELA.
• Hong Kong Area Radar West (TRV) covers the airspace around IKELA between SFC - UNL. (SFC - FL365 when Hong Kong Area Radar Upper is online)
• Handoffs to Hong Kong Area Radar West (TRV) shall be made in the following order:
  HKG_V_CTR -> HKG_W_CTR

Figure 7.21: Hong Kong Area Radar West (TRV) Sector

7.2.11 Hong Kong Area Radar West

• Position: HKG_W_CTR; Callsign: Hong Kong Radar
• This is the primary Area Radar sector. When fully split, this sector covers traffic via SIKOU, high-level overflights and VHHX arrivals via TAMOT.
• Hong Kong Area Radar West covers the airspace around SIKOU and TAMOT between SFC - UNL. (SFC - FL365 when Hong Kong Area Radar Upper is online)

Figure 7.22: Hong Kong Area Radar West Sector

7.2.12 Hong Kong Area Radar Upper

• Position: HKG_U_CTR; Callsign: Hong Kong Radar
• This sector covers high-level traffic within Hong Kong FIR.
• Hong Kong Area Radar Upper covers the airspace within Hong Kong FIR between FL365 - UNL.
• When Hong Kong Area Radar Upper is online, the upper limit for all other Area Radar sectors becomes FL365.

Figure 7.23: Hong Kong Area Radar Upper Sector

7.2.13 Hong Kong Air Movements Control (North)

• Position: VHHH_N_TWR; Callsign: Hong Kong Tower
• This sector covers the northern half of the Hong Kong ATZ. In the absence of VHHH_S_TWR and VHHH_C_TWR, it shall cover the entire Hong Kong ATZ.
• Hong Kong Air Movements Control (North) covers SFC - 2000ft AAL.
• Handoffs to Hong Kong Air Movements Control (North) shall be made in the following order:
  VHHH_N_TWR -> VHHH_C_TWR -> VHHH_S_TWR -> VHHH_APP -> HKG_W_CTR

7.2.14 Hong Kong Air Movements Control (South)

• Position: VHHH_S_TWR; Callsign: Hong Kong Tower
• This sector covers the southern half of the Hong Kong ATZ. In the absence of VHHH_N_TWR and VHHH_C_TWR, it shall cover the entire Hong Kong ATZ.
• Hong Kong Air Movements Control (South) covers SFC - 2000ft AAL.
• Handoffs to Hong Kong Air Movements Control (South) shall be made in the following order:
  VHHH_S_TWR -> VHHH_C_TWR -> VHHH_N_TWR -> VHHH_APP -> HKG_W_CTR

7.2.15 Hong Kong Air Movements Control (Midfield)

• Position: VHHH_C_TWR; Callsign: Hong Kong Tower
• This sector covers the centre runway at VHHH. In the absence of VHHH_N_TWR and VHHH_S_TWR, it shall cover the entire Hong Kong ATZ.
• Handoffs to Hong Kong Air Movements Control (Midfield) shall be made in the following order: VHHH_C_TWR -> VHHH_S/N_TWR (depending on RWY in use) -> VHHH_APP -> HKG_W_CTR

Figure 7.24: Hong Kong Air Movements Control Sector

7.2.16 Macau Tower

• Position: VMMC_TWR; Callsign: Macau Tower
• This sector covers the Macau ATZ.
• Macau Tower covers SFC - 3000ft AAL.
• Handoffs to Macau Tower shall be made in the following order:
  VMMC_TWR -> VMMC_APP -> VHHH_L_APP -> VHHH_W_APP -> HKG_W_CTR -> VHHH_APP

Figure 7.25: Control airspace of Macau Tower

7.2.17 Hong Kong Flight Information Service

• Position: VHHH_F_TWR; Callsign: Hong Kong Information
• This sector is responsible for providing Flight Information Service within Class G airspace in Hong Kong FIR.
• Handoffs to Hong Kong Flight Information Service shall be made in the following order: VHHH_F_TWR -> VHHH_Z_TWR -> VHHH_S/C/N_TWR (by coordination) -> VHHH_APP -> HKG_W_CTR

7.2.18 Hong Kong Zone Control

• Position: VHHH_Z_TWR; Callsign: Hong Kong Zone
• This sector is responsible for VFR traffic operating within the Hong Kong CTR at or below 2000ft. While this sector will not normally accept handoffs from Mainland China ATC positions, it is responsible for covering Hong Kong Flight Information Service in its absence, hence it has been included in this document.
• Handoffs to Hong Kong Zone Control shall be made in the following order: VHHH_Z_TWR -> VHHH_S/C/N_TWR (by coordination) -> VHHH_APP -> HKG_W_CTR

7.2.19 Southeast Asia Control

• Position: ASEA_FSS; Callsign: Southeast Asia Control
• This sector covers all CTR sectors within each VATSEA vACC in the absence of local ATC.
• Southeast Asia Control covers FL245 - UNL.

8. Routing Requirements

8.1

Both Mainland China and Hong Kong have strict flight planning requirements. On VATSIM, VATPRC and vACC Hong Kong have agreed to comply with requirements on some routes.

8.2

Hong Kong ATC is responsible for checking parts of routes and cruising altitude in the direction of Mainland China:

• BEKOL northbound traffic via W56 or eastbound via G471 shall use Metric Odd Levels.
• BEKOL westbound traffic via B330 shall use Metric Even Levels.
• BEKOL westbound traffic shall NOT route via A599, flights shall route via SIKOU R339 BSE, then join A599.
• BEKOL eastbound traffic shall NOT route via R200, flights shall route via DOTMI, then join A470.
• LELIM northbound traffic shall only be flown by aircraft with destinations ZSPD/ZSQD/ZSYT/ZYTL.
• Flights departing from VMMC:
  • NLG SIDs shall only be used for flights landing ZGSZ with cruising level S0150.
  • IDUMA SIDs shall be used for flights landing ZGGG with cruising level S0450.
  • Eastbound traffic via A470 shall route via DOTMI.
  • All other northbound and eastbound traffic shall route via MIPAG or IDUMA.
  • Westbound traffic shall route via BIGRO.
• Routes within Mainland China airspace shall not contain DCTs. Unless coordinated, all flight segments shall be connected via valid airways.

8.3

Mainland China ATC is responsible for checking parts of routes and cruising altitude in the direction of Hong Kong:

• Flights departing from ZGGG or ZGSZ and transiting Hong Kong airspace shall use one of the routes specified in AIP Hong Kong ENR 1.10-8.2 (Figure 8.1).
• Traffic routing via LUKBU may be subject to delay due to congestion in the vicinity of Hong Kong and Macao airports.

8.4 Special Routes for Helicopter or General Aviation Aircraft

8.4.1

The following routes are generally for helicopter use ONLY. However, due to the nature of VATSIM, other non-helicopter aircraft - but limited to general aviation aircraft - can be used with the permission of ATC.

8.4.2

Unless otherwise stated or coordinated, the helicopter or general aviation aircraft shall use the following routes. Referring to ENR 3.4 Section 2.2 of AIP of Hong Kong and ENR 2.2.2.4 of AIP of Mainland China, the routes are:

8.4.2.1 VFR - Shenzhen ⟷ Hong Kong:

• KEVAR – URBOR – LAXUS – LUKBU (TCP)
  • 300m/1000ft or below

8.4.2.2 VFR - Shenzhen ⟷ Macau:

• KEVAR – URBOR – PEXEL – ZAO (TCP)
  • 300m/1000ft or below

8.4.2.3 VFR track H - Guangzhou FIR ⟷ Hong Kong FIR:

• HG – PS – AT – SS (TCP) – H
  • 600m/2000ft or below

8.4.2.4 VFR track HT - Guangzhou FIR ⟷ Hong Kong FIR:

• HG – PS – AT – HMS - QZ (TCP)
  • 600m/2000ft or below

8.4.2.5 VFR track VH - Guangzhou FIR ⟷ Hong Kong FIR:

• HG – PS – DP (TCP)
  • 600m/2000ft or below

8.4.2.6 VFR track VW - Guangzhou FIR ⟷ Hong Kong FIR:

• ZAO (TCP) – U – VW
  • ZAO – U
    • 150m/500ft or below when VHHH RWY 07s in use
    • 250m/800ft or below when VHHH RWY 25s in use
  • U – VW
    • 300m/1000ft or below

8.4.2.7 IFR track H - Guangzhou FIR ⟷ Hong Kong FIR:

• HG – PS – AT – SS (TCP) – H
  • To Hong Kong FIR
    • 1500m/5000ft
  • To Guangzhou FIR
    • 1200m/4000ft

8.4.2.8 IFR track HT - Guangzhou FIR ⟷ Hong Kong FIR:

• HG – PS – AT – HMS - QZ (TCP)
  • To Hong Kong FIR
    • 1500m/5000ft
  • To Guangzhou FIR
    • 1200m/4000ft

8.4.2.9 IFR track D - Guangzhou FIR ⟷ Hong Kong FIR:

• ZUH – R (TCP) – D
  • To Hong Kong FIR
    • 1200m/4000ft
  • To Guangzhou FIR
    • 1500m/5000ft

8.4.3 VFR waypoint and coordinates

8.4.4

Track H shall be used as the primary IFR route.

8.4.5

Track H and Track VW shall be used as the primary VFR routes.

8.4.6

Track HT shall be used in the event of unavailability of Track H. Coordination required.

8.4.7

Handoff from/to Hong Kong Zone (VHHH_Z_TWR) or any online controllers who are responsible for this area may be established. Refer to Appendix B.

8.4.8

For VFR route Shenzhen ⟷ VHHH, to avoid unnecessary change of frequencies, handoff from/to Hong Kong Air Movements Control North (VHHH_N_TWR) if online or Hong Kong Air Movements Control Midfield (VHHH_C_TWR) / Hong Kong Air Movements Control South (VHHH_S_TWR) if offline may be established.

Figure 8.1: Departures from Guangzhou or Shenzhen Airports transiting Hong Kong FIR (Source: Hong Kong AIP ENR1.10-8.2)

Figure 8.2: Oil Rig Support Helicopter Routes in Hong Kong FIR (Source: Hong Kong AIP ENR3.4-Heli-1)

Figure 8.3: Area chart-Guangzhou and Zhuhai (Source: China AIP ENR2.2.2.4)

9. Handoff Altitudes at Transfer of Control Points (TCP) for IFR flights

9.1 Zhuhai TMA – Hong Kong TMA

Remarks:

① This TCP is for Helicopter or General Aviation aircraft ONLY. Hong Kong airspace at this altitude is Class G (uncontrolled), so aircraft may be handed directly to Advisory Frequency. Under coordination, the aircraft may be handed to Hong Kong Radar/Approach for traffic information purposes (see Appendix B).

② This TCP is for Helicopter or General Aviation aircraft ONLY.

Remarks:

① Traffic arriving at ZGSZ from other airports should route via LANDA.

② When Hong Kong airspace is congested, traffic should route via SIERA. See section 7.2.

9.2 Shantou TMA ① – Hong Kong ACC (K)

Remarks:

① Traffic departing ZGMX to VHHK should route via ZGZU and SIERA. Traffic arriving at ZGMX from VHHK should route via ZGZU and BEKOL.

9.3 Zhanjiang TMA ① – Hong Kong ACC (W)

Remarks:

① Aircraft departing ZGBH to VHHK should route via ZGZU and SIERA.

9.4 Guangzhou ACC – Hong Kong ACC (W/U)/TMC*

Remarks:

① This TCP shall NOT be used for aircraft landing ZGGG transit via VHHK FIR. Such aircraft need to be rerouted to TAMOT.

② Aircraft can be handed off when climbing but must be above 4800m (F157).

③ Lower altitudes may be used with coordination to allow direct handoff with VHHH_APP.

9.5 Sanya ACC – Hong Kong ACC (W/V/D/U)

9.6 Nanning ACC ① – Hong Kong ACC (W)

Remarks:

① Aircraft departing ZGNN to VHHK should route via ZGZU and SIERA.

9.7 Xiamen ACC - Hong Kong ACC (K)

9.8 Shanghai ACC - Hong Kong ACC (K/U)

10. Handoff Altitudes at Transfer of Control Points (TCP) for VFR flights

10.1 TCP: Jiuzhou VOR (ZAO)

10.1.1 From Guangzhou FIR to Hong Kong FIR

• 150m/500ft or below when Hong Kong runway 07s in use
• 250m/800ft or below when Hong Kong runway 25s in use

10.1.2 From Hong Kong FIR to Guangzhou FIR

• 300m/1000ft or below

10.2 TCP: LUKBU

10.2.1 From Guangzhou FIR landing Hong Kong airport

• 300m/1000ft or below

10.2.2 From Hong Kong airport to Guangzhou FIR

• 300m/1000ft or below

10.3 TCP: SESAN (Xing Shan/星山)

10.3.1 From Guangzhou FIR to Hong Kong FIR

• 600m/2000ft or below

10.3.2 From Hong Kong FIR to Guangzhou FIR

• 600m/2000ft or below

10.4 TCP: DAPENG (Da Peng/大鹏)

10.4.1 From Guangzhou FIR to Hong Kong FIR

• 600m/2000ft or below

10.4.2 From Hong Kong FIR to Guangzhou FIR

• 600m/2000ft or below

10.5 TCP: QZ (Qing Zhou/青州)

10.5.1 From Guangzhou FIR to Hong Kong FIR

• 600m/2000ft or below

10.5.2 From Hong Kong FIR to Guangzhou FIR

• 600m/2000ft or below

11. Coordination Procedures for Macau International Airport (VMMC)

11.1

This section defines the ATC coordination procedures for departing and arriving traffic at Macau International Airport (VMMC) on VATSIM.

11.2 General

11.2.1

Aerodrome control of Macau International Airport (Delivery (DEL), Ground (GND), and Tower (TWR)) shall be under the jurisdiction of Hong Kong vACC of the Southeast Asia Division (VATSEA). The ATC service of such positions shall be provided by Hong Kong vACC controllers.

11.2.2

Responsibility for Terminal ATC service at Macau International Airport (VMMC) shall be shared between Hong Kong ATC and Mainland China ATC depending on the SID, STAR, and IAP of the specific flight.

11.2.3

Hong Kong ATC is responsible for ensuring all activities within ATZ Macau (SFC - 3000ft AMSL) do not deviate into Zhuhai TMA unless prior coordination with Mainland China ATC is performed.

11.2.4

Mainland China ATC shall be responsible for all segments of SID/STAR within Mainland China airspace.

11.2.5

Hong Kong ATC shall be responsible for all segments of SID/STAR within Hong Kong airspace.

11.2.6

All handoff procedures shall follow the AIP of Macau ENR1.5-2 (Figure 11.1) and the AIP of China ENR 2.2.2.3-3 (Figure 11.2).

11.2.7

Controllers shall assign the RNAV procedure for departure and arrival for flights from/to Mainland China airspace. Where a pilot is not able to accept a RNAV procedure, radar vectors shall be used.

11.2.8

As per AIP of Mainland China, ENR 2.2 Section 2.3.2, the altimeter setting procedure for aircraft departing and arriving at VMMC in Zhuhai TMA shall be as follows:

• When the aircraft is at VMMC prior to departure, the altimeter setting shall be set to the QNH of VMMC.

• After departure, when the aircraft enters Zhuhai TMA, the altimeter shall be set to Zhuhai TMA QNH on instruction of Mainland China ATC.

• Altimeter shall be set to 1013.2 hPa upon passing the transition altitude of Zhuhai TMA (2700m on QNH).

• While operating as local flight within Zhuhai TMA, Zhuhai Approach may instruct the aircraft to set altimeter to either the Zhuhai Terminal QNH or VMMC QNH.

11.2.9

Controllers should refer to Appendix B for details on sectorization. Any non-standard sectorization must be coordinated through the ATC channel or via private messages.

11.2.10

Controllers covering Macau Airport should advise neighbouring controllers when a change of runway has occurred via the ATC channel or private message if necessary.

Figure 11.1: Transfer of Control Points for VMMC Airport (Source: Macau AIP ENR1.5-2)

Figure 11.2: Transfer of control points for VMMC Airport (Source: China AIP ENR2.2.2.3-3)

11.3 Special Procedures for Departing Flights from Macau International Airport (VMMC)

11.3.1

Per the AIP of Macau S.A.R., flights departing from runway 34 of Macau International Airport (VMMC) shall not overshoot Jiuzhou VOR (ZAO) due to noise abatement for Zhuhai.

11.3.2

If runway 34 is in use and the aircraft is non-RNAV, Hong Kong ATC shall notify Mainland China ATC and instruct the aircraft to fly a heading as coordinated with Mainland China ATC (usually 040) after departure. If the pilot insists on flying conventional procedures, coordination must take place.

11.3.3

When runway 34 is in use at Macau International Airport (VMMC), Macau Tower shall obtain a release from Zhuhai Approach(if online) for departing IFR aircraft prior to issuing takeoff clearance. Once this release has been obtained, only then is Macau Tower allowed to issue takeoff clearance to an aircraft.

11.4 Initial Altitude for Departing Flights from Macau International Airport (VMMC)

11.4.1 Runway 34 departure

• All directions – S0120

11.4.2 Runway 16 departure

• To Hong Kong direction – 4000ft
• To other Guangzhou directions - S0120

11.5 Procedure in the Absence of Mainland China ATC

11.5.1

This section defines the procedures when all Mainland China ATC are offline. This deviates from the AIP of Macau as the absence only takes place on an online network.

11.5.2

RWY 34 Departure towards LUKBU and missed approach towards MC411 – After takeoff/missed approach, Macau Tower shall instruct aircraft with the following phraseology: “<callsign>, leaving controlled airspace, monitor Advisory Frequency 122.8, report passing LUKBU/MC411 on <next controller frequency>.”

11.5.3

RWY 16 arrival via INDUS – Upon reaching INDUS, Hong Kong ATC shall instruct aircraft with the following phraseology: “<callsign>, leaving controlled airspace, monitor Advisory Frequency 122.8, report established on the localiser runway 16 on <next controller frequency>.”

11.5.4

Hong Kong ATC is responsible for all VMMC departing and arriving traffic except runway 34 departures to Guangzhou FIR.

11.6 Procedure in the Absence of Hong Kong ATC

11.6.1

This section shall define the procedures when all Hong Kong ATC are offline. This deviates from the AIP of Macau as the absence only takes place on an online network.

11.6.2

RWY 34 arrival – Mainland China ATC shall instruct aircraft to monitor Advisory Frequency (122.800) upon reaching waypoint ROMEO or MCU VOR.

11.6.3

RWY 34 missed approach – Macau Tower (if online) shall instruct traffic on the missed approach to tune to Mainland China ATC after the initial right turn. After passing LUKBU or MC411, Mainland China ATC shall instruct the aircraft to monitor Advisory Frequency (122.800).

11.6.4

RWY 16 arrival via INDUS – Traffic shall contact Mainland China ATC upon crossing INDUS. After establishing on MCS LOC (LOC/DME approach) or reaching MC510 (RNAV-GNSS) Mainland China ATC may instruct the aircraft to:

• Monitor Advisory Frequency (122.800) if Macau Tower is offline; or,
• Contact Macau Tower if it is online.

11.6.5

RWY 16 departure – for SIDs entering Zhuhai TMA, Macau Tower shall directly hand traffic off to Mainland China ATC after departure.

11.6.6

RWY 16 missed approach – Traffic shall contact Mainland China ATC upon passing INDUS.

12. Special Agreement on FIR Boundary

12.1

There are differences between the depiction of the boundary line in the AIP of Hong Kong (shown in Figure 12.1) and that in the AIP of Mainland China (shown in Figure 12.2). To follow real-world operations, and to avoid unnecessary handoffs, on VATSIM, Hong Kong vACC and VATPRC use actual controlling boundaries as the FIR boundary. (shown in Figure 12.3).

12.1.1

To comply with the real-world operation, Mainland China ATC will transfer aircraft as per Section 6.1.4,. while Hong Kong ATC will transfer aircraft prior to them reaching the line specified by the following coordinates:

N022.47.09.363 E116.05.41.000

N022.43.05.999 E116.10.05.999

N022.56.21.001 E117.18.42.001

N023.00.00.000 E117.30.00.000

Figure 12.1: Hong Kong FIR boundary as shown in Hong Kong AIP ENR6.1 (AMD 12/23).

Figure 12.2: Mainland China FIR boundaries as shown in Mainland China AIP ENR6 ERC (2024 No. 4).

Figure 12.3: Coordinated Hong Kong FIR-Mainland China FIRs Boundary in AeroNav

12.2

To follow the real-world operation, the Hong Kong Area of ​​Responsibility (AoR)(shown in Figure 12.4) is established in Guangzhou FIR (ZGZU). GND-S0390 (FL130) and below are under the jurisdiction of Hong Kong ATC. Above S0390 (FL130) are under the jurisdiction of Mainland China ATC.

Figure 12.4: Hong Kong AoR, as shown in Mainland China AIP ENR6 ERC

12.3

Since the coordinates of MAGOG published within the Mainland China AIP and Hong Kong AIP are different, both sides agree that the coordinates of MAGOG shall be based on the coordinates published within the Hong Kong AIP. The routing to be flown after the handover point DOTMI shall be based on the content published within the Hong Kong AIP. The routing for the segment within the Mainland China FIRs shall end at DOTMI, e.g. A470 DOTMI.

13. Validity, Review, and Amendment

13.1

This Letter of Agreement becomes valid and takes immediate effect upon the approval of the Division Director (VATPRC1) of the People's Republic of China Division (VATPRC), the Division Director (VATSEA1) of the Southeast Asia Division (VATSEA), and the Director of Hong Kong Virtual Area Control Centre (HK vACC).

13.2

Should there be any changes to real-world procedures made by the local authorities, both parties shall decide whether an amendment to this LOA is necessary.

13.3

A content review of this LOA shall take at most six (6) months after this LOA takes effect. During the review, both parties shall convene to discuss the implementation of this LOA and make proper amendments to it if necessary. Subsequent content review shall take place at most every six (6) months henceforth.

13.4

Any parties wishing to amend this LOA (by adding, omitting or changing any clauses) shall contact the other party to call for an immediate review of the LOA. Both parties must reach a consensus on any amendments before they take effect. Subsequent content review shall take place at most every six (6) months henceforth.

This Letter of Agreement is approved on 27 Nov, year 2025:

VATPRC Division Director - Hongye Rudi Zhang

VATSEA Acting Division Director - Hoo Jiong Sheng

Hong Kong vACC Director - Mark Hui

Appendix A: References

Aeronautical Information Publication of Hong Kong Special Administrative Region, published by the Hong Kong Civil Aviation Department.

Aeronautical Information Publication of the People's Republic of China, published by the Civil Aviation Administration of China.

Aeronautical Information Publication (Publicações de Informações Aeronáuticas) of Macau Special Administrative Region published by the Civil Aviation Administration of Macau S.A.R. (Autoridade de Aviação Civil da RAEM)

ICAO Doc 4444

Appendix B: Quick Reference Table