1 Requirement for the Submission of a Flight Plan
1.1 All aircraft intending to conduct an IFR flight within the Hong Kong FIR shall file a flight plan, except that authorised operators may submit a CAD approved flight notification form for local VFR flights.
2 Procedures for the Submission of a Flight Plan and Subsequent Changes for Flights Departing HKIA
2.1 There are three means of filing flight plans for flights departing HKIA
- by Private Communication Network;
- by AFTN (for scheduled flight operations only);
- by Flight Plan Form.
2.2 FILING OF FLIGHT PLAN BY PRIVATE COMMUNICATION NETWORK
2.2.1 Airline operators can use the Private Communication Network service to submit flight plans to the AIMC.
2.2.2 Private Communication Network is the most effective means above all and is widely in use.
2.2.3 A customized flight plan form is provided by the system on-line for users to complete and submit to the AIMC.
2.2.4 The flight plan form mimics the present ICAO flight plan format with the following customization:
- all flight plans are addressed to VHHHZPZA which is the default address on the flight plan form;
- for the purpose of flight plan message distribution by VHHHZPZA, an “AD/” field is provided on the flight plan form for airline operators to insert up to a maximum of 40 individual or collective AFTN addresses of the flight plan recipients. Please note that VHHHZPZA is not permissible under the “AD/” field; and
- flight plan Field 19 can be activated for the input of supplementary information but Field 19 will not be transmitted as part of the normal flight plan message. The supplementary information stored can be transmitted as a Supplementary Flight Plan (SPL) upon request from ATC units.
2.2.5 Prior to the submission of flight plan, the system will perform validity checks on the flight plan fields as follows:
- syntactic check for fields allowing alpha characters only or digits only;
- syntactic check on time format;
- semantic check on aircraft type and location indicators for destination/alternate aerodrome;
- syntactic check on route as required by ICAO Doc 4444, Appendix 2 but no semantic check is provided;
- checking of AFTN addresses in the “AD/” field against the global address book; and
- checking of all entries in Field 18 and sorting them according to the sequence prescribed in ICAO Doc 4444, Appendix 2.
2.2.6 For details of Private Communication Network service, refer to GEN 3.4 para
3.6.
2.3 FILING OF FLIGHT PLAN BY AFTN
2.3.1 This facility is only applicable to scheduled flight operations.
- Flight plans are to be addressed to VHHHZPZA;
- Addressees of flight plan recipients are to be inserted in the “AD” field positioned at the beginning of the flight plan message, before the open bracket symbol; each line of “AD” field shall be prefixed by the characters “AD”. “AD” and each addressee shall be separated by a space; and a maximum of 7 addressees may be inserted to each line of “AD” field.
- Supplementary Information in Field Type 19 is not required but it should be made readily available at the airline operator’s office / handling agent in Hong Kong and provide to ATC units when requested.
2.3.2 Filing of flight plan from an overseas AFTN address is not accepted unless the address has been registered with the AIMC. Registration requests should be sent to the Briefing Officer of the AIMC by email at
bo@cad.gov.hk
. The registration shall not be considered successful until a notice of confirmation is received from the AIMC.
2.3.3 In addition to the requirements stated in para
2.3.1 above, airline operators, filing a flight plan from an overseas AFTN address, shall adhere to the following submission requirements:
- ensure the overseas AFTN address used for sending FPL is the same as the one registered with the AIMC. Prior approval shall be sought from the Briefing Officer of the AIMC for any change in the registered overseas AFTN address;
- should the inclusion of the Hong Kong office/handling agent address is required, insert the addressee in the AD field as per para 2.3.1 b) above;
- ensure the Hong Kong office/handling agent can be contacted by the AIMC in case of queries.
2.4 FILING OF FLIGHT PLAN BY FLIGHT PLAN FORM
2.4.1 The flight plan shall be completed on Flight Plan Form DCA6a. Flight plan forms other than DCA6a will not be accepted.
2.4.2 Flight Plan Form DCA6a is downloadable from the following CAD website:
http://www.cad.gov.hk/application/DCA6a.pdf
2.4.3 The addressees of all recipients shall be inserted into the addressee boxes provided in the beginning of the flight plan form.
2.4.4 To ensure legibility, flight plan data shall be printed onto the flight plan form. Only fair copies of flight plan will be accepted. A flight plan form with manuscript entries or amendments will be rejected and not processed.
2.4.5 Completed Flight Plan Form DCA6a shall be submitted to AIMC by the following means:
- by hand to the staff in the AIMC; or
- by facsimile to the AIMC, fax number 2910 1180.
2.4.6 The ultimate responsibility for compiling an accurate flight plan rests with pilots and/or airline operators. In order to avoid undue delay in flight plan processing, operators are advised to refer to the guidance notes appended to the Flight Plan Form DCA6a and other pertinent documents to ensure the information entered into the form is compliant with all relevant requirements.
2.5 CHANGES TO THE FILED FLIGHT PLAN
2.5.1 Airline operators, regardless of their means of filing flight plans, shall inform the AIMC by telephone of any subsequent changes to a filed Flight Plan (FPL) so that associated ATS message such as Delay (DLA), Modification (CHG) and Flight Plan Cancellation (CNL) can be sent by AIMC.
2.5.2 The AIMC will contact the airline operators’ Hong Kong office/handling agent for any verification/changes required, for example, rectification of routes and flight levels. Where appropriate, associated ATS message will be sent by AIMC after receiving confirmation from airline operators.
2.5.3 In order to avoid confusion, airline operators shall not send DLA, CHG or CNL on their own.
3 Procedures for the Submission of a Flight Plan and Subsequent Changes for Flights Inbound to HKIA or Transiting Hong Kong FIR
3.1 For flights inbound to HKIA or transiting Hong Kong FIR, airline operators shall file flight plans and subsequent changes by AFTN to VHHKZQZX at the aerodrome of departure or with the telecommunications service enroute.
4 Time of Submission
4.1 Airline operators can file a FPL up to 5 days (120 hours) prior to the EOBT.
4.2 Except where necessary for operational or technical reasons, any aircraft operating to or from Hong Kong or transiting Hong Kong FIR shall submit a flight plan at least 3 hours prior to the estimated off-block time (EOBT).
4.3 In any case, flight plan submitted with less than 3 hours prior to the EOBT may experience further ATFM delay when an ATFM measure is in force.
4.4 In the event of a delay of 15 minutes in excess of the EOBT last transmitted, the flight plan should be amended with the transmission of a Delay (DLA) message, or a new flight plan submitted and the old flight plan cancelled, whichever is applicable. For flights departing from Hong Kong, airline operators shall inform AIMC any delay of the EOBT in a filed FPL in accordance with the procedures as described in para
2.5.
5 Contents and Form of Flight Plan
5.1 For airline operators operating non-scheduled flights or general aviation flights at HKIA, aircraft identification used in Item 7 of the flight plan and flight number/call sign used for flight application via Electronic Filing System in Hong Kong CAD website <http://www.cad.gov.hk> shall be identical.
5.2 Because the Flight Data Processing System (FDPS) in Hong Kong is fully automated the flight plan data must be submitted in accordance with the standard format designed for the purpose. All operators are required to strictly comply with the route syntax specified in paragraphs
6 to
9. Any discrepancy made on FPL will be rejected by the system which can cause delay to the flight.
5.3 In addition to the flight plan requirements detailed in this section, operators shall refer to ENR 1.8 para
8 and strictly adhere to the flight levels prescribed in the Flight Level Assignment Scheme.
5.4 Any flight inbound to HKIA or transiting Hong Kong FIR, must insert in Item 18 of the flight plan form:
- the Date of Flight field in the form of DOF/yymmdd;
- the national registration letters/numbers of the aircraft if different from the aircraft identification in Item 7;
- the accumulated estimated elapsed time to the Hong Kong FIR in the form of EET/VHHK and without a space, a four figure group indicating hours and minutes.
5.5 Only specific indicators shall be used in Item 18 (Other Information) and adherence to the specific sequence of the indicators is mandatory.
5.6 Free text is not allowed for ‘STS/’ of Item 18, only specific indicators as prescribed in ICAO Doc 4444, Appendix 2 shall be used.
6 Flights To or From Hong Kong International Airport
6.1 Arriving at HKIA 1
|
Inbound Route |
Flight planned route within the Hong Kong FIR to be filled in Item 15 of the standard ICAO Flight Plan |
| (1) |
A470 |
DOTMI V512 ABBEY 2 |
| (2) |
M503 8 and 10 |
LELIM V591 ABBEY 2 |
| (3) |
A1/G581 |
ELATO V522 ABBEY 2 |
| (4) |
M501/A461 |
NOMAN V532 BETTY 3 |
| (5) |
A583 |
SABNO V542 BETTY 4 |
| (6) |
M772 |
ASOBA M772 DULOP Q1 CARSO V551 BETTY 4 |
| (7) |
M771 |
DOSUT M771 DULOP Q1 CARSO V551 BETTY 4 |
| (8) |
A1 |
IKELA P901 IDOSI V561 CANTO or IKELA A1 IDOSI V561 CANTO 5 |
| (9) |
R339/A202 |
SIKOU V571 CANTO 5 |
| (10) |
R473 |
SIERA |
| (11) |
--- |
ALLEY DCT CANTO 11 |
| (12) |
--- |
FOXTROT DCT CANTO 12 |
6.2 Departing from HKIA 6
|
Flight planned route within the Hong Kong FIR to be filled in Item 15 of the standard ICAO Flight Plan |
Connecting Route |
| (1) |
BEKOL |
A461 |
| (2) |
LEKEN V601 DOTMI |
A470 |
| (3) |
LEKEN V611 LELIM |
M503 9 and 10 |
| (4) |
DALOL V621 ELATO |
A1/G581 |
| (5) |
DALOL V631 ENVAR |
M750 |
| (6) |
DALOL V641 NOMAN |
A461/M501 |
| (7) |
DALOL V641 SKATE DCT KAPLI |
G86 |
| (8) |
DALOL V651 SABNO |
A583 |
| (9) |
PECAN V10 SIKOU |
R339/A202 |
| (10) |
PECAN V11 IDOSI A1 IKELA 7or
PECAN V11 IDOSI P901 IKELA 7 |
A1 |
| (11) |
PECAN V12 EPDOS L642 |
L642 |
| (12) |
PECAN DCT CHALI 13 |
--- |
| (13) |
PECAN DCT FOXTROT 14 |
--- |
| 1 |
To optimise the flight plan processing work flow, operators are not to include Standard Instrument Arrival (STAR) Procedures in flight plans and subsequent AFTN messages for all operations into HKIA. |
| 2 |
Cross ENPET at FL260. Do not descend without ATC clearance. |
| 3 |
Cross SONNY at FL260. Do not descend without ATC clearance. |
| 4 |
Cross CYBER at FL260. Do not descend without ATC clearance. |
| 5 |
Cross MAPLE at FL260. Do not descend without ATC clearance. |
| 6 |
To optimize the flight plan processing work flow, operators are not to include Standard Instrument Departure (SID) Procedures in flight plans and subsequent AFTN messages for all operations from HKIA. Operators departing from HKIA shall flight plan via the relevant Terminal Transition Route until exiting Hong Kong FIR/TMA to join the appropriate ATS route. |
| 7 |
Route via P901 at FL290 or above, or A1 at FL280 or below. To operate at FL290 or above aircraft must be RNP 10 compliant. |
| 8 |
Flights departing from Shanghai Pudong, Qingdao, Yantai or Dalian to HKIA shall route via M503. |
| 9 |
For destinations Shanghai Pudong, Qingdao, Yantai or Dalian only. |
| 10 |
In the event that M503 is not available, e.g. approval could not be obtained in time from relevant authority, operator should file flight plan via ATS Route A470. |
| 11 |
For flights departing from Macao International Airport. |
| 12 |
For flights departing from Zhuhai Jinwan Airport. FOXTROT coordinates: 214536.00N 1132200.00E. |
| 13 |
For flights landing in Macao International Airport. |
| 14 |
For flights landing in Zhuhai Jinwan Airport. FOXTROT coordinates: 214536.00N 1132200.00E. |
7 Flights To or From Macao International Airport Which Transit Hong Kong FIR
7.1 Arrival at Macao International Airport transiting Hong Kong FIR 1
|
Inbound Route |
Flight planned route within the Hong Kong FIR to be filled in Item 15 of the standard ICAO Flight Plan |
| (1) |
A470 |
DOTMI DCT SAMMI J101 SMT 7 |
| (2) |
A1/G581 |
ELATO J101 SMT 7 |
| (3) |
M501/A461 |
Not available 2 |
| (4) |
A583 |
SABNO DCT TOFEE DCT SUKER DCT ALDOM J103 ROBIN DCT CHALI 3 and 8 |
| (5) |
M772 |
ASOBA M772 DULOP M771 DUMOL J103 ROBIN DCT CHALI 8 |
| (6) |
M771 |
DOSUT M771 DUMOL J103 ROBIN DCT CHALI 8 |
| (7) |
A1 |
IKELA P901 IDOSI DCT DASON J104 CHALI 4and 9or
IKELA A1 IDOSI DCT DASON J104 CHALI 4and 9 |
| (8) |
R339/A202 |
SIKOU J104 CHALI 9 |
7.2 Departure from Macao International Airport transiting Hong Kong FIR 5
|
Flight planned route within the Hong Kong FIR to be filled in Item 15 of the standard ICAO Flight Plan |
Connecting Route |
| (1) |
NUDPI V601 DOTMI |
A470 |
| (2) |
NUDPI V611 LELIM |
M503 6 |
| (3) |
CONGA V621 ELATO |
A1/G581 |
| (4) |
CONGA V631 ENVAR |
M750 |
| (5) |
GRUPA V641 NOMAN |
A461/M501 |
| (6) |
GRUPA V651 SABNO |
A583 |
| (7) |
ALLEY V32 EPDOS L642 |
L642 |
| (8) |
ALLEY V31 IDOSI P901 IKELA 4or
ALLEY V31 IDOSI A1 IKELA 4 |
A1 |
| (9) |
ALLEY V10 SIKOU |
R339/A202 |
| (10) |
GRUPA DCT KAPLI |
G86 |
| 1 |
Operators may include the relevant Standard Instrument Arrival (STAR) Procedures (e.g. SMT5B, CHALI4A etc.) into the flight plan route if considered necessary. |
| 2 |
Flights from Manila FIR to Macao Airport should route via A583. In the event of bad weather, flights from Ho Chi Minh FIR that require to transit Manila FIR via diversionary route to Hong Kong FIR, should flight plan within Hong Kong FIR via A461 NOMAN DCT ALDOM J103 or expect radar vectors to join J103 by Hong Kong Radar at or below FL300. |
| 3 |
Flights to Macao International Airport transiting Hong Kong FIR via A583 SABNO should plan to cross SABNO at FL340 or below. |
| 4 |
Route via P901 at FL290 or above, or A1 at FL280 or below. To operate at FL290 or above aircraft must be RNP10 compliant. |
| 5 |
Operators departing from Macao International Airport transiting Hong Kong FIR shall flight plan via the relevant Terminal Transition Route until exiting the Hong Kong FIR/TMA to join the appropriate ATS/PBN route. |
| 6 |
For destinations Shanghai Pudong, Qingdao, Yantai or Dalian only. In the event that M503 is not available, e.g. approval could not be obtained in time from relevant authority, operator should file flight plan via ATS route A470. |
| 7 |
Cross NEDLE at FL230. Do not descend without ATC clearance. |
| 8 |
Cross ISBAN at FL200 and CHALI at FL110. Do not descend without ATC clearance. |
| 9 |
Cross COTON at FL120 and CHALI at FL110. Do not descend without ATC clearance. |
9 Other Flights Transiting the Hong Kong FIR
9.1 Flights transiting the Hong Kong FIR not specified in previous paragraphs
|
Entry Route |
Flight planned route within the Hong Kong FIR/TMA to be filled in Item 15 of the standard ICAO Flight Plan |
Connecting Route |
| (1) |
A470 |
DOTMI DCT SOUSA DCT CONGA V621 ELATO 1 |
A1/G581 |
| (2) |
DOTMI DCT SOUSA DCT CONGA V631 ENVAR 2 |
M750 |
| (3) |
DOTMI DCT ENROM DCT NOMAN |
A461/M501 |
| (4) |
DOTMI DCT ENROM DCT SABNO |
A583 |
| (5) |
DOTMI DCT ENROM DCT SULUX DCT EPKAL |
L642 |
| (6) |
DOTMI DCT ENROM DCT SULUX DCT IGLEG DCT IKELA |
A1 |
| (7) |
DOTMI DCT ENROM DCT ALLEY V10 SIKOU 6 |
A202/R339 |
| (8) |
A1/G581 |
ELATO DCT MAGOG DCT DOTMI |
A470 |
| (9) |
ELATO J101 PONTI DCT BEKOL |
A461 |
| (10) |
G86 |
KAPLI DCT MADRU DCT SULUX DCT IGLEG DCT IKELA |
A1 |
| (11) |
KAPLI DCT ALLEY V10 SIKOU 6 |
A202/R339 |
| (12) |
A461 |
NOMAN DCT SANKU DCT SOUSA V601 DOTMI |
A470 |
| (13) |
Not Available |
A202/R339 |
| (14) |
A583 |
SABNO DCT LEGOD DCT BEKOL |
A461 |
| (15) |
SABNO DCT SIKOU 6 |
A202/R339 |
| (16) |
M772 |
ASOBA M772 DULOP Q1 CARSO DCT NOBAD DCT SANKU DCT SOUSA V601 DOTMI |
A470 |
| (17) |
ASOBA M772 DULOP M771 DUMOL J103 BEKOL |
A461 |
| (18) |
M771 |
DOSUT M771 DULOP Q1 CARSO DCT NOBAD DCT SANKU DCT SOUSA V601 DOTMI |
A470 |
| (19) |
DOSUT M771 DUMOL DCT DAGBU DCT SIKOU 6 |
A202/R339 |
| (20) |
DOSUT M771 DUMOL J103 BEKOL |
A461 |
| (21) |
A1 |
IKELA DCT MORTU DCT NOBAD DCT SANKU DCT SOUSA V601 DOTMI |
A470 |
| (22) |
IKELA DCT MORTU DCT NOBAD DCT ELATO 1 and 3 |
A1 |
| (23) |
IKELA DCT MORTU DCT NOBAD DCT ENVAR 2 and 3 |
M750 |
| (24) |
IKELA DCT MORTU DCT NOBAD DCT KAPLI 5 |
G86 |
| (25) |
IKELA P901 IDOSI DCT DAGBU DCT SIKOU 4 and 6or
IKELA A1 IDOSI DCT DAGBU DCT SIKOU 4 and 6 |
A202/R339 |
| (26) |
IKELA P901 IDOSI DCT BIGEX A461 BEKOL 4or
IKELA A1 IDOSI DCT BIGEX A461 BEKOL 4 |
A461 |
| (27) |
B330/W18 |
TAMOT B330 BIGEX DCT DALOL V621 ELATO 1 |
A1 |
| (28) |
TAMOT B330 BIGEX DCT DALOL V621 ELATO 1 |
G581 |
| (29) |
TAMOT B330 BIGEX DCT DALOL V631 ENVAR 2 |
M750 |
| (30) |
TAMOT B330 BIGEX DCT DALOL V631 ENVAR 2 M750 DADON |
G581 |
| (31) |
TAMOT B330 BIGEX DCT GRUPA V641 NOMAN |
A461/M501 |
| (32) |
TAMOT B330 BIGEX DCT GRUPA V651 SABNO |
A583 |
| (33) |
TAMOT DCT ALLEY V32 EPDOS L642 |
L642 |
| (34) |
TAMOT DCT ALLEY V31 IDOSI P901 IKELA 4or
TAMOT DCT ALLEY V31 IDOSI A1 IKELA 4 |
A1 |
| (35) |
TAMOT DCT ALLEY V10 SIKOU 6 |
A202/R339 |
| (36) |
A202/R339 |
SIKOU DCT DAGBU DCT IDOSI P901 IKELA 4 and 6or
SIKOU DCT DAGBU DCT IDOSI A1 IKELA 4 and 6 |
A1 |
| (37) |
SIKOU DCT DAGBU DCT EPDOS L642 6 |
L642 |
| (38) |
SIKOU J104 CHALI DCT LENBU DCT GRUPA V641 NOMAN 6 |
A461/M501 |
| (39) |
SIKOU J104 CHALI DCT LENBU DCT GRUPA V651 SABNO 6 |
A583 |
| (40) |
SIKOU J104 CHALI DCT BEKOL 6 |
A461 |
| (41) |
SIKOU J104 CHALI DCT KAPLI 6 |
G86 |
| 1 |
Normally for non-RNAV 5 compliant or non-RVSM approved aircraft. |
| 2 |
To operate between FL290 and FL410 aircraft must be RNAV 5 compliant and RVSM approved. |
| 3 |
Route available only during the period 1700 - 0059 UTC, flight plan via G86 KAPLI during the period 0100 - 1659 UTC. (See ENR1.1 para 4 for details). |
| 4 |
Route via P901 at FL290 or above, or A1 at FL280 or below. To operate at FL290 or above aircraft must be RNP 10 compliant. |
| 5 |
Between 1700 - 2200 UTC, Taipei ACC only accepts eastbound traffic entering Taipei FIR via KAPLI transiting Taipei FIR to Fukuoka FIR and routing via G86 HCN G581/J7 PICHU Q13 IGURU or destined for aerodromes in Taipei FIR. |
| 6 |
See ENR 1.1 for ATC Procedures for the Use of ATS Route A202. |
9.2 Approval should be sought from ATS Supervisor for flights intended to operate into Hong Kong FIR on routes other than those contained in paragraph
9.1.
10 Arriving Cargo Aircraft and General Aviation Aircraft
10.1 To ensure that cargo flights are correctly identified, operators of cargo flights are required to include the information ‘RMK/CARGO’ in item 18, ‘Other Information’, of the ATC FPL for Hong Kong.
10.2 To ensure that general aviation flights that will be parking at the Business Aviation Centre are correctly identified, operators of these flights are required to include the information ‘RMK/BAC PARKING’ in item 18, ‘Other Information’, of the ATC FPL for Hong Kong.
11 RNAV Approved Aircraft
11.1 RNP 10
11.1.1 Operators of aircraft with on-board area navigation capability specified in ICAO Regional Supplementary Procedures (Doc 7030), shall include the following information on their flight plan:
| Item 10a |
Item 15 |
Item 18 after ‘PBN/’ |
| R |
True Mach Number and flight level at entry and exit point |
A1 |
11.1.2 See
ENR 1.8 for ATC application of RNAV criteria / Mach number technique.
11.2 RNP 4
11.2.1 Operators of aircraft with on-board area navigation capability specified in ICAO Regional Supplementary Procedures (Doc 7030), shall include the following information on their flight plan:
| Item 10a |
Item 15 |
Item 18 after ‘PBN/’ |
| RG |
True Mach Number and flight level at entry and exit point |
L1 |
11.2.2 See
ENR 1.8 for ATC Application of RNAV criteria / Mach number technique.
11.3 RNP 1
11.3.1 Operators of aircraft approved for RNP1 operations, shall include either of the following information in Item 10a and Item 18 of their flight plan:
| Item 10a |
Item 18 after ‘PBN/’ |
| RGDI |
O1 |
| RG |
O2 |
11.3.2 See GEN 1.5 para
3.5.3 for details of RNP 1 SID / STAR procedures and the Exemption Policy.
11.3.3 Flights of categories which are classified as exempted categories as specified in GEN 1.5 para
3.5.3.5 shall specify status of flight following the indicator STS in Item 18 of the flight plan form using appropriate ICAO designators (i.e. STS/HUM, STS/SAR, STS/STATE, STS/HEAD, STS/FLTCK). Flights of categories
d) to
f) shall denote the reasons following the indicator RMK in Item 18.
11.4 RNAV 5
11.4.1 Operators of aircraft approved for RNAV 5 operations, shall include one of the following information in Item 10a and Item 18 of their flight plan:
| Item 10a |
Item 18 after ‘PBN/’ |
| RGODI or RGSDI * |
B1 |
| RG |
B2 |
| RD |
B3 |
| ROD or RSD * |
B4 |
| RI |
B5 |
* S is used for standard equipment which includes O (VOR).
11.5 RNAV 2
11.5.1 Operators of aircraft approved for RNAV 2 operations shall include “R” in Item 10a and “C1” or “C2” after “PBN/” in Item 18 of their flight plan.
11.6 Authorization Required Approach (RNP-AR APCH) without Radius Fix (RF)
11.6.1 Operators of aircraft authorized to conduct RNP-AR APCH without RF shall include ‘RG’ in Item 10a and ‘PBN/T2’ in Item 18 of their flight plan.
12 RVSM Approved Aircraft
12.1 The Hong Kong controlled airspace between FL290 and FL410 inclusive are prescribed as Reduced Vertical Separation Minima (RVSM) airspace. RVSM approval is required to operate within RVSM airspace unless prior approval has been granted.
12.2 The letter ‘W’ shall be inserted in Item 10 (Equipment) of the flight plan to indicate that both the aircraft and operator are RVSM approved.
12.3 Operators on non-RVSM approved aircraft capable of operating at FL 280 or above, regardless of the requested flight level, shall insert the following information on their flight plan:
- Item 18 ‘STS/NONRVSM’.
13 Automatic Dependent Surveillance Broadcast (ADS-B) Approved Aircraft
13.1 Aircraft operator complying with the requirement stipulated in GEN 1.5 paragraph
3.7.6 shall indicate the appropriate ADS-B designator in Item 10 of the flight plan as follows:
- ‘B1’ for ADS-B with dedicated 1090 MHz ADS-B ‘out’ capability
- ‘B2’ for ADS-B with dedicated 1090 MHz ADS-B ‘out’ and ‘in’ capability
14 Repetitive Flight Plan System
14.1 A repetitive flight plan system which generally follows the provisions of ICAO PANS-ATM DOC 4444 is available to flights operating between:
- Taibei/Gaoxiong and Hong Kong;
- Jakarta and Hong Kong; and
- Kuala Lumpur and Hong Kong.
14.2 When filing a repetitive flight plan all operators shall include the following information on the RVSM approval status of the flight:
| (a) |
Item Q |
‘EQPT/W’, for flights with RVSM approval; or
‘STS/NONRVSM’, for flights without RVSM approval capable of operating at FL280 or above, regardless of the requested flight level. |