1 / 12

Hong Kong PBN implmentation ICAO GNSS Implementation Seminar/Workshop 26 March 2012

Hong Kong PBN implmentation ICAO GNSS Implementation Seminar/Workshop 26 March 2012. 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.

celine
Download Presentation

Hong Kong PBN implmentation ICAO GNSS Implementation Seminar/Workshop 26 March 2012

An Image/Link below is provided (as is) to download presentation Download Policy: Content on the Website is provided to you AS IS for your information and personal use and may not be sold / licensed / shared on other websites without getting consent from its author. Content is provided to you AS IS for your information and personal use only. Download presentation by click this link. While downloading, if for some reason you are not able to download a presentation, the publisher may have deleted the file from their server. During download, if you can't get a presentation, the file might be deleted by the publisher.

E N D

Presentation Transcript

  1. Hong KongPBN implmentation ICAO GNSS Implementation Seminar/Workshop 26 March 2012

  2. 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

  3. Hong Kong PBN Implementation Plan ~ Approach 3

  4. AIC 03/12 12 Jan 2012 Hong Kong PBN Implementation Plan ~ Terminal 4

  5. AIC 03/12 12 Jan 2012 Hong Kong PBN Implementation Plan ~ Enroute 5

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

  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

  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

  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

  10. Difficulties Encountered: ATMProcedure 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

  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

More Related