1. 2017/3/28
Hong Kong PBN implmentation ICAO GNSS Implementation Seminar/Workshop 26 March 2012
ICAO FPP fdsagsdfgsdgsdgasdfsadf 1

2. Latest Hong Kong PBN Implementation Roadmap
2017/3/28
Content
Latest Hong Kong PBN Implementation Roadmap
Publication of mandate requirements for Baisc-RNP1 and RNP4
New PBN procedures Implementation
New RNP AR APCH
Progress
Difficulties
ICAO FPP fdsagsdfgsdgsdgasdfsadf 2

3. Hong Kong PBN Implementation Plan ~ Approach
AIRSPACE
SHORT TERM ( )
MEDIUM TERM ( )
Long Term (Beyond 2016)
Approach
Implement RNP AR APCH Procedure to North RWY by 2010 [Implemented]
Implement RNP AR APCH Procedure to South RWY by 2012 (in progress)
Feasibility study of GBAS (in progress)
Trial of GBAS for capable aircraft/ operators
Consider use of appropriate Nav. Spec., e.g. Advance RNP APCH, within approach airspace
Subject to satisfactory results of the trial, consider GBAS as backup to the ILS
Consider use of other Nav. Spec. that suits the operation in HK.
Consider mandate the Nav. Spec. selected for aircraft operating within approach airspace by 2016+
Achieve 100% implementation of the Nav. Spec. selected within approach airspace 3
ICAO FPP fdsagsdfgsdgsdgasdfsadf

4. Hong Kong PBN Implementation Plan ~ Terminal
AIRSPACE
SHORT TERM ( )
MEDIUM TERM ( )
Long Term (Beyond 2016)
Terminal
(SID/STAR)
issue mandate for Basic-RNP1 SIDs/ STARs capability by 2013 [issued]
Implement Basic RNP1 application
Mandate Baisc RNP1 application for aircraft operating by 2013
Achieve 100% Basic RNP1 SID/STAR
AIC 03/12
12 Jan 2012 4
ICAO FPP fdsagsdfgsdgsdgasdfsadf

5. Hong Kong PBN Implementation Plan ~ Enroute
AIRSPACE
SHORT TERM ( )
MEDIUM TERM ( )
Long Term (Beyond 2016)
Enroute
Apply 50NM Longitudinal Separation on RNP10 Routes in 2008 [Implemented]
Trial operation for RNP4 on L642 & M771 by 2012 (pending)
issue mandate for RNP4 capability within HK en-route airspace by 2014 [issued]
Implement RNP4 within enroute airspace
Mandate RNP4 application for aircraft operating within en-route airspace by 2014
Achieve 100% RNP4 within en-route airspace
Consider mandate better navigation specification in accordance with the ICAO regional roadmap, e.g. RNP2
AIC 03/12
12 Jan 2012 5
ICAO FPP fdsagsdfgsdgsdgasdfsadf

6. Implementation of new RNP AR APCH
Background
Current RNP AR APCH RWY25R
Why new?
Procedure Details
Difficulties encountered
Q&A 6
ICAO FPP fdsagsdfgsdgsdgasdfsadf

7. Background: Current RNP AR APCH RWY25R (implemented in 2010)
Same Approach track as ILS APCH
Same Profile as ILS APCH
15NM long final
Improved MAP track (vs ILS) for better ATM 7
ICAO FPP fdsagsdfgsdgsdgasdfsadf

8. Why we need another new RNP AR APCH?
Reduce Noise level over highly populated area
Shorter track mile for flights from W and SW
Avoid Weather near Hong Kong highest mountain (Tai Mo Shan)
an alternate route when weather blocking traffic from joining current ILS/RNP APCH
ICAO FPP fdsagsdfgsdgsdgasdfsadf

9. RNP AR APCH Implementation Process in Hong Kong
Brief Hong Kong Implementation process for RNP AR APCH
Stakeholders consultation (Operators, ATC etc)
Primary Flight Procedure Design with Preliminary assessment
Primary ATC procedure study
Stakeholders consultation
Revised Design with Detail Flight Procedure assessment
Stakeholders Review (Operators, ATC, Regulator etc)
Flight Simulation (Ground validation)
Further revision
Detail ATC procedure development
Stakeholders Review
Safety assessment
Revised Flight and ATC procedure accommodating safety assessment outcome
Publication
Trial Operation with appropriate benchmarking (flight efficiency – environmental, track mile ; workload – both pilots and controllers) for 0.5 to 1 yr
Implementation
Obtain Feedback from stakeholders, continuous maintenance
Periodic Review 9
ICAO FPP fdsagsdfgsdgsdgasdfsadf

10. Difficulties Encountered: ATM Procedure Naming – DataBase issue
PBN TF 6 (Feb 2012) – WP12
ICAO recommendation
ICAO Doc 8168 Vol. II, Part I Section 4, Chapter 9
9.5.3 “Duplicate Procedure identification
e.g. RNAV(RNP) z Rwy25R
RNAV(RNP) y Rwy25R
Most FMS accept 6 character e.g.RNV25R
7 character is required e.g. RNVy25R
B777 & B748
Limited amount of aircraft can fly the procedure only
less flight can enjoy the benefits of shorter track miles and enhanced operating efficiency of the new procedures 10
ICAO FPP fdsagsdfgsdgsdgasdfsadf

11. The meeting is requested to note that:
Hong Kong has completed most of the short term PBN implementation projects and is expecting to accomplish all other short term PBN projects in 2012;
Hong Kong has published the mandate requirements for Basic-RNP 1 and RNP 4 (details please refer to Hong Kong AIC 03/12); and
The limitation of FMS, i.e. cannot accept RNP procedure identifications with more than 6 alpha-numeric places even the procedure is named in accordance with the ICAO procedure naming convention as stipulated in Doc 8168, will hinder the implementation of PBN procedures. ICAO may need to consider providing more guidance to assist States and operators in resolving the FMS limitation.

12. Q&A
ICAO FPP fdsagsdfgsdgsdgasdfsadf