Performance Based Navigation PBN Canadian Implementation Presentation to

Performance Based Navigation (PBN) Canadian Implementation Presentation to Air Transport Association of Canada 9 November 2010

Presentation Overview • PBN Background – Performance Based Navigation – Why PBN? • PBN in Canada – – Current status Coordination Framework Short, Medium and Long term plans and timelines

Performance-Based Navigation GNSS Moving towards Primary Navigation • Leveraging aircraft capabilities • Safety, Capacity, Efficiency Today Q RNAV & RNP Q Future Vision Optimize benefits: Ground-Based Primary Navigation 3 • Airspace design • CNS technologies • Traffic Flow Management

Why PBN? - Benefits • Facilitates more efficient design of airspace and procedures • Improves safety, access, capacity, predictability, and operational efficiency. • Minimizes reliance on ground based navigation routing and infrastructure • Reduces aviation impact on the environment – Less fuel burn and GHG emissions – Less noise pollution 4

PBN IN CANADA 5

PBN in Canada • May 2010 – PBN Framework document developed. Linked to a Concept of Operations • Sept 2010 – NAV CANADA received implementation feedback from the ATOCC PBN Coordination Group • October 2010 – Transport Canada committed to the creation of a CARAC Working Group to review the intent of PBN changes and the requirement for regulatory structure • October 2010 – NAV CANADA short term implementation strategies provided to the aviation community through the ATOCC / ANSNAC meetings

ATOCC PBN Coordination Group • A combined NAV CANADA and customer group plus ADHOC industry experts coordinating activities and milestones – Scope of related issues is expanding – NAV CANADA PBN Coordination Manager : Jeff Cochrane • Goal is efficient and effective extraction of benefits from latest technology and coordinated implementation of PBN – – Cooperative/collaborative approach Coordinated investment Examination of ATC and Aircrew procedures Coordination of testing and implementation of new or revised procedures – “Now” and future targets

Linking the Objectives ANSP Infrastructure Customer Certification and qualification Regulatory enablers 8

PBN Framework - Purpose • To align NAV CANADA and our customer expectations, priorities and objectives for the implementation of PBN concepts in Canada over the next 10 - 15 years • To implement where feasible – Coordinated with customer equipage plans 9

Implementation Strategy Short Term (2010 -15) • • Continue with the Windsor/Toronto/Montreal Airspace Review Implement RNP 10 in Edmonton FIR Convert remaining CMNPS and RNPC airspace to PBN Develop prioritized list of airports for PBN and commence terminal redesigns based on PBN concepts • Address AIS targets of opportunity • Cyclic reviews • Continue to implement 3 rd party RNP designs • Develop internal capability for RNP design • Decommission non-essential ground based nav aids • Educating NAV CANADA and the aviation community on PBN • Explore viability of a Canadian or US test site for GBAS evaluation 12

Implementation Strategy Medium Term (2015 -20) • Continue Terminal airspace reviews in accordance with a prioritized list • Re-assess and re-define the low level airspace structure in concert with the surveillance strategy, to incorporate PBN concepts • Continue to expand the implementation of GNSS procedures as customer equipage expands 12

Implementation Strategy Long Term (2020 and beyond) • Transition to a full PBN capability • 4 D RNP operations and a gate to gate flight management environment • Ground based navigation aid infrastructure is reduced to the lowest possible • Back up capability based on risk assessment/vulnerability study • Regulatory change is required 12

13 13

What is PBN? • Transition from ground based sensor navigation to area navigation (RNAV) • Framework for defining navigation performance requirements/ specifications in terms of: – Accuracy, Integrity, Availability, Continuity, Functionality • A toolbox of navigation specifications that can be applied to a specific type of airspace to improve and standardize operations • Includes both RNAV and RNP as types of specifications 14

RNAV and RNP • Area Navigation or RNAV – Enables aircraft to navigate point to point by using onboard navigation equipment and updates from ground based ( DME) , aircraft based (inertial units) or space based ( GNSS satellite) navigation systems. • Required Navigation Performance or RNP – Same as RNAV except RNP aircraft have onboard performance monitoring and alerting capability 15

Performance Based Navigation RNAV Routes RNAV SIDs RNAV STARs RNP Restricted approaches RNAV approaches Reduced reliance on ground based navigation aids 16

Customer Perspective • Departure Phase – Standard Instrument Departures for every departure runway that quickly allows aircraft to join their route to destination • En-route Phase – Routes that are flexible based on that day’s operating conditions and upper winds. – If flexible routes are not possible then a network of RNAV and RNP direct routes is preferred • Arrival Phase – Standard Arrivals that provide least track miles to the initial approach fix, preferably with a CDA profile from top of descent • Approach Phase – A runway aligned with lateral and vertical guidance for every runway end that terrain allows - Reference IATA 17