310 likes | 681 Views
ICAO PBN Implementation. Presentation Overview. PBN – Goals PBN – Roles PBN – Plans PBN – Tools. PCO/ PIRG. CO2 Emissions. Cost. ?. ?. Setting The Framework Implementation of a Global ATM System. GOO 5 : Optimized Airspace and Route Structures. Accountability.
E N D
Presentation Overview • PBN – Goals • PBN – Roles • PBN – Plans • PBN – Tools
PCO/PIRG CO2 Emissions Cost ? ? Setting The FrameworkImplementation of a Global ATM System GOO 5 : Optimized Airspace and Route Structures Accountability Global Operational Outcomes and KPI Directors, RDs and Chief of Offices Demand vs. Capacity Section / Unit Chiefs Airspace Organization and Management Section / Unit Chiefs Anx 6 ANP Anx 11 PANSATM GM Programme RDs, TOs and ROs Project by Region
Why Implement PBN? At a global level, • To reduce controlled flight into terrain (CFIT) • To increase efficiency • To increase capacity • To increase aerodrome access • To address environmental issues
ICAO implementation goals States and/or regions develop an implementation plan by 2009 to achieve the following goals • where RNAV operations are required, enroute (oceanic and continental) and terminal ATS routes should be implemented according to PBN by 2016, and • all instrument runway ends should have an approach procedure with vertical guidance (APV), either as the primary approach or as a back-up for precision approaches by 2016
PBN implementation goals Enroute airspace (where RNAV ops required) Area of operation: Oceanic and remote airspace • Applicable navigation specifications: RNAV 10 and RNP 4 • Implementation strategy: 100% implementation by 2010 Area of operation: Enroute continental • Applicable navigation specifications: RNAV 5, 2, and 1 • Implementation strategy: 70% by 2010, 100% by 2014
PBN Implementation Goals Terminal airspace (where RNAV ops required) • Area of operation: Terminal area • Applicable navigation specifications: RNAV 1, 2 and Basic-RNP 1 • Implementation strategy: 30% by 2010, 60% by 2014, 100% by 2016
PBN implementation goals Approach Area of operation: Approach (RNP) • Applicable navigation specifications: • RNP APCH • RNP AR APCH (if normal straight-in approach is operationally not feasible) • Implementation strategy: • All instrument runways: • APV to all runway ends by 2016 • NPA where APV is operationally not possible
ImplementationICAO Leadership role • Familiarization • States, Stakeholders, ICAO • Implementation • Planning assistance • Execution assistance • Verification • Development and maintenance of ICAO provisions
Implementation Role: ICAO Headquarters • Organize seminars • Website for info/FAQ on PBN (www.icao.int/pbn) • Assist in PIRGs with setting PBN goals and developing regional PBN implementation plans “PBN Roadmaps” • Coordinate and assist in PBN implementation planning and execution • (sub) Regions • States and other stakeholders • Identify and address follow-on training needs and other potential obstacles to implementation
APANPIRG/18 Recommendations • Conclusion 18/52 – Establishment of a Regional Performance Based Navigation Task Force (PBN/TF) • Conclusion 18/53 – Development of State PBN Implementation Plans • Conclusion 18/54 – Globally Harmonized SARPS and Guidance Material for PBN • Conclusion 18/55 – Designation of Contact Person for PBN Implementation
Implementation Role: Regional Office • Assist in organizing seminars • Provide focal points for PBN at the RO • Monitor implementation progress in the Region • Coordinate development of Regional PBN implementation plan “PBN Roadmap” • Manage regional PBN Task Force • Coordinate implementation planning and execution for PBN enroute operations • 1st level of assistance in Region for PBN implementation planning and execution for terminal and approach operations
Implementation Role: States • Participate in development of Regional PBN implementation plan “PBN Roadmap” • Develop State PBN implementation plan by the end of 2009 • Provide focal point for PBN implementation • Involve other stakeholders in PBN implementation • Identify issues or “Showstoppers” that could delay implementation, and relay to ICAO • WGS 84 is a “Showstopper” if not done
State PBN Implementation Plan This guidance to stakeholders should: • Address the planned evolution of navigation, as one of the key systems supporting air traffic management, • Describe the RNAV and RNP navigation applications that should be implemented in at least the short and medium term, in the State
State PBN Implementation Plan Why is the PBN Implementation Plan or Roadmap needed? • To implement the regional PBN plans at the State level and address PBN implementation strategy at the national level • To provide proper guidance and direction to the domestic air navigation service provider(s), airspace operators and users, regulating agency, as well as foreign operators who operate or plan to operate in the State • Assist the main stakeholders plan a gradual transition to the RNAV and RNP concepts • Assist the stakeholders in planning their investment strategies during the future transition
Implementation Role: Stakeholders • Cooperate with States in their planning and implementation • Commit the resources necessary to carry out their part of the strategy for regional and State implementation
Familiarization Tools:“Introduction to PBN” Seminars Brussels 22-25 April 2008 Montreal 12-15 June 2007 Baku 15-18 April 2008 Cairo 12-15 November 2007 New Delhi 18-20 September 2007 Santo Domingo 24-27 June 2008 Bangkok 11-14 September 2007 Abuja 15-18 January 2008 Nairobi 22-25 January 2008 Lima 17-20 June 2008
Implementation: Tools • Final draft of PBN manual is finalized and posted on ICAO-NET • State Letter with Navigation Specifications is on ICAO-NET • AN 11/45-07/22, 27 April 2007 • State Letter with flight plan provisions • AN 11/13-2.5-07/35, 25 May 2007 • State Letter with PBN terminology changes to Annexes 2, 3, 4, 6, 10, 11 and 15 • AN 11/45-07/52, 20 July 2007
Implementation: Tools • ICAO RNP AR Procedure Design Manual (Draft) to be available by October 2007 • ICAO Quality Assurance Manual for Flight Procedure Design- consists of four volumes (3 to be ready in draft form in October 2007: • Volume 1 – Flight Procedure Design Quality Assurance System; • Volume 2 – Flight Procedure Designer Training; • Volume 3 – Flight Procedure Design Software Validation; • State implementation plan template • Implementation checklist
Implementation: Tools For possible future development: • Specialized training for Controllers, Regulators, Procedure Designers • Flight Operational Safety Assessment (FOSA) guidance • Model regulations and operational approval documents • Helicopter-specific PBN nav spec provisions • RNP 2 Nav spec for enroute, advanced RNP 1 for terminal, advanced RNP APCH
Summary • ICAO must assume leadership role in implementation • Commitment and active involvement required from States and other stakeholders • State PBN implementation plans to be complete by end of 2009 • The benefits of PBN only come with implementation