performance based navigation (pbn) study group – final meeting pbn manual status may 18, 2012 dave...

Performance Based Navigation (PBN)Study Group – Final Meeting

PBN Manual Status

May 18, 2012

Dave NakamuraChair, PBNSG

Copyright © 2006 Boeing. All rights reserved.

Topics

• Background

• Volume I and II, Navigation Specifications, Attachments & Appendices

• Conclusions


Roland RawlingsPedro Rivas[Bjarni Stephansson]Theo Van de VenDave Van NessHonghai Yang Rick LeedsMichinobu Utsunomiya,Hirotaka MoriJohn KastenDave BehrensRob EaglesRoss DennersteinIan MallettHouston AnthonyGrady BoyceVeronique TraversAndrew BeadleRon TidyThomas BuchananKoichiro KuboDirk NoordewierRon Doggett

Dave NakamuraErwin LassooijJeff CochraneWaldemar KrolakBenoit RoturierAntoine HerveGeoff BurtenshawMark SteinbickerBarry MillerNick TallmanJoe McCarthyFranca PavličevićAlex FisherChristophe CaillaudMichel CalvetBarbara Cassidy[Julio Cesar de Souza Pereira]Carlos CirilloDidier DelibesEd HajekMakoto EguchiPatrick HarbordEduardo JuranovicHenrik Nielsen

PBN Study GroupMembers and Advisors


BackgroundWork Program

Copyright © 2006 Boeing. All rights reserved.5

Nav Applications

Com Surv ATM

Airspace Concept

Nav

RNP SpecificationsRNAV Specifications

RNAV10(RNP 10)

RNAV 5RNAV 2 RNAV 1

RNP 2RNP 1

Advanced RNP RNP 0.3

RNP APCHRNP AR APCH

RNP w/Added

Requirements e.g. 3D, 4D

RNP 4

Nav Specifications Nav Infrastructure

BackgroundICAO Performance Based Navigation Concept


NAVIGATION SPECIFICATION

FLIGHT PHASE

En Route Oceanic / Remote

En Route Continental ARR

APPROACH

DEPInitial Intermed Final Missed RNAV 10 (RNP 10) 10

RNAV 5 5 5

RNAV 2 2 2 2

RNAV 1 1 1 1 1 1 1

RNP 4 4

RNP 2 2 2

RNP 1 1 1 1 1 1

Advanced RNP 2 2 or 1 1** 1** 1** 0.3 1** 1**

RNP 0.3 0.3 0.3 0.3 0.3 0.3

RNP APCH 1 1 0.3 1

RNP AR APCH 1 - 0.1 1 - 0.1 0.3 - 0.1 1 - 0.1

Applications reflect performance/functional requirements

BackgroundNavigation Specifications

** includes optional function of RNP scalability


Volume I

Step 1 Agree Operational

Requirement

Step 2 Create PBN

Implementation Team

Step 4Analyse Reference

Scenario

PROCESS 1Identify Navigation specification for

implementation

Step 3 Agree Objectives, Scope and Time

Scales

Iteratio

ns

Step 5Safety and

Performance Criteria

Step 6CNS/ATM

Assumptions, Enablers & Constraints

Step 7Design Routes and

Holds

Step 8Initial Procedure

Design

Step 9Design Volumes and

Sectors

Ite

rati

on

s

Itera

tion

s

Regulator Input

Regulator Input

User Requirements

Step 10Confirm ICAO

Navigation Specification

Itera

tion

s

Nav Spec not fit for purpose

Nav Spec fit for purpose

Go to Process 2

Resolve in coordination with

ICAO

Vol I, Part B

Major update to implementation processes based upon lessons learned and feedback from ICAO/FAA/ EUROCONTROL PBN Seminars


Attachment C to Vol I

ObjectiveProvide a high level summary of operational approval processes for general awareness, and complement the new operations approval manual.

RationaleOperations approval identified from seminars, Go Team activities and general enquiries as one of the major hurdles for the global implementation of PBN.

Volume IOperations Approval Guidance


Chapter 2, Vol II, Part C

ObjectiveRNP 2 is primarily intended for a diverse set of en route applications; particularly in geographic areas with little or no ground NAVAID infrastructure, limited or no ATS surveillance, and low to medium density traffic , Oceanic/Remote and Continental applications

RationaleThis provides a solution where RNP routes can be implemented as an element of improved airspace design and traffic flow.

Issues• The higher continuity option will need to be

addressed through operational approval and flight planning.

Volume II Navigation SpecificationsImplementing RNP 2



ObjectiveProvide for RNP operations where the RNP is applicable to all phases of flight, and with RNAV holding, parallel offset, & Radius to Fix as required and Fixed Radius Transition and RNP scalability from 0.3 to 1.0 NM, for terminal airspace, as options.

RationaleProvides• A means for a single aircraft qualification • Improved airspace capabilities via Advanced RNP

functionality • Significantly enhanced approach and departure

capabilities

Issue• This provides value through it’s operational

applications but is sufficiently complex that additional ICAO information and implementation guidance is strongly recommended.

Volume II Navigation SpecificationsImplementing Advanced RNP



ObjectiveProvide for RNP operations predicated on rotorcraft RNP systems using TSO-C145()/C146() functionality

RationaleRotorcraft RNP systems contain the capability for performing RNP operations where improved heliport access and routing through dense airspace is facilitated. Note: This may also be used for qualified fixed wing aircraft.

.

Volume II Navigation SpecificationsImplementing RNP 0.3



ObjectiveExtend RNP AR to address departure.

RationaleInitial specification only addresses approach, omitting departure. AR operations are needed for departures from some of the very same runways where AR approach exists.

Issues• Not accomplished due to lack of a focal and

time. A future action is required due to the demand for departure guidance material.

• Outgrowth of discussions identified the need for guidance material concerning use of PBN for one engine inoperative.procedures e.g., at ICAO Ops Panel.

Volume II Navigation SpecificationsImplementing RNP AR APCH


Appendix to Vol II, Part C

ObjectiveProvide for fixed radius turns in non-RNP AR APCH applications, where operational improvements can be achieved e.g. environment, access and terrain/obstacles are not a factor. Applicable only on RNP terminal airspace procedures (SID/STAR) and on approach operations outside of the final approach segment.

RationaleProvide a predictable and repeatable ground track where fixed ground tracks are required to achieved reduced separation minima, improved traffic flow, or reliable turn performance.

Volume II Navigation SpecificationsRadius To Fix (RF) Path Terminator


Appendix to Vol II, Part C

ObjectiveProvide for fixed radius transitions along RNP ATS routes [for use with Advanced RNP and RNP 2]

RationaleProvide a predictable and repeatable ground track where fixed ground tracks are required to achieved reduced separation minima, improved traffic flow, or reliable turn performance.

Volume II Navigation SpecificationsFixed Radius Transition (FRT)


Volume IISample Airspace Concept Based On Nav Specs

Attachment B to Vol II

ObjectiveProvide examples of route spacing achieved per flight phases [with and without radar surveillance] using PBN in specific environments

RationaleFollowing the removal of Attachment B to Annex 11, it was necessary to locate the sample route spacing in another ICAO document. It also is a response to frequent enquiries on the subject.


Conclusions

• PBNSG has completed its work on the update to the PBN Manual.

• It is recommended that ICAO proceed with publishing the manual.

• Shortcomings with filing of PBN in the 2012 ATC FPL identified, which will need to be addressed pre-FF ICE.

• Consequential changes [for routes with FRT] are required to ICAO documentation including Annex 11.

• It is recommended that ICAO develop supporting guidance/information for the new navigation specifications, especially Advanced RNP.

• The timeline for implementation will need to reflect development of supporting guidance material and implementation processes by States.

• It is anticipated that future actions will be necessary post-PBNSG to support implementation.

• The PBNSG is willing to support ICAO on PBN related papers to ANC/12.


Thank You

performance based navigation (pbn) study group – final meeting pbn manual status may 18, 2012 dave...

Documents

advanced rnp rnp

rnp operations

rnp routes

advanced rnp slide

rnp apch rnp ar apch

c objective rnp

advanced rnp functionality

pbnsg slide