Download presentation
Presentation is loading. Please wait.
Published byMaud Dennis Modified over 9 years ago
1
PBN Deployment – New Zealand Domestic Airspace CAA PBN Forum November 18 2009 Auckland
2
Background Drivers Modern FMS Ground aids reaching end of life Operational efficiency Environmental ICAO IATA
3
70 % rule FAA experience. Less than 70% users able to use – don’t implement More than 70% users able to use – implement and withdraw conventional
4
In the beginning Establish RNAV as the default language/method of navigation and ATM at AA, WN and CH –1/. RNAV STAR –2/. RNAV SID –3/. RNAV En-route between –4/. RNAV approach as supplement to ILS
5
Followed by Establishing RNAV as default language/method of navigation and ATM at all airports with regional control towers –1/. HN, RO, TG –2/. NV, DN, WP –3/. NS, WB –4/. OH, PM, NP –5/. NR, GS
6
Ideal roll out – ATC perspective Airport specific - implement as a package RNAV STAR RNAV Approach RNAV SID Separation charts to enable management Staff training
7
Current anomalies/difficulties Some regional airports have parts of the package. Result of nav aids reaching end of life. Mixed fleet equipage. Complex lateral separations Mixed messages.
8
Existing PBN procedures RNP10 (RNAV 10) in OCA RNP4 Trans-Tasman RNAV Enroute RNAV SIDs and STARs RNAV(GNSS) 57 locations APV @ 16 runways RNP AR @ Queenstown RNP AR @ RO, AA, WN, CH coming
9
So what’s to come Establish/confirm the Regional PBN Plan Initial scoping meeting – July 09 ATC planning meeting - 5,6,7,8 Oct 09 Feedback from regional CCs Ongoing coordination with users. User meeting 1 Dec 09 Generic Tower Model established (Feb 2010)
10
Generic Regional Tower model McDonalds Supermarket From RNAV En-route to Feeder Fix RNAV STAR to Approach. Approach will be RNAV (GNSS). Upgrade to APV (Baro V NAV). Need to limit choices Assume VORs (used as approach aid) will go ? ICAO – PBN APV to all instrument runways by 2016
11
Chunks – step one Queenstown By itself – unique – jet – terrain – RNP AR Current ATM very inefficient with regards to traffic “flow” Departure example, 23 minute delay once RNP approach “committed”. Review in progress. Next meeting 23, 24, November
12
Chunks - step two RO, HN, TG Plan Feb, March, April2010 Implement Nov2010
13
Chunks – step three NV, DN, WP PlanMay, June2010 NS, WB PlanJuly, Aug2010 OH, PM, NP PlanSept, October2010 NR, GS PlanFeb March2011 Implement through 2011
14
PBN – Issues/Considerations Customer needs – sort this out first Fleet capability Charting standards Procedure design capability Regulator capability (rules) to approve PBN operations Public vs. Tailored RNP AR ATM considerations - Mixed mode operations What noise there is gets concentrated Who’s going to pay?
15
PBN – Issues/Considerations (2) Equipment performance standards RAIM Prediction service Back-up procedures Contingency – DME/DME, DVOR Flight planning requirements – ATM Training requirements
16
ATM system ability A lost message. ATM system still needs to monitor and assist the aircraft with PBN Current ground system could provide much more. Off track alert - Turn initiation - Cleared altitude vs actual climb For ATC to use this ability aircraft need Enhanced mode s - capable of up grade to ADS-B
17
RNAV Arrivals – Noise Concentration
19
Thank you
Similar presentations
© 2024 SlidePlayer.com. Inc.
All rights reserved.