Transcript PBN - Overview

Performance Based Navigation
Erwin Lassooij
Technical Officer/ FLS section
IFALPA ATC Meeting
1
Presentation
overview
PBN – Background
PBN – Concept
PBN – Status
PBN – Implementation
IFALPA ATC Meeting
2
Aviation challenges
:
 Growing demand for RNAV approaches (safety,
accessibility)
 Growing demand for solutions to airspace
congestion
 Growing fuel efficiency requirements
 Growing Environmental requirements
 Most can be met with current technology, but
standardization and operational requirements
have to be put into place
IFALPA ATC Meeting
3
Background
ICAO RNP concept
 FANS identified need for performance based navigation and
developed Required Navigation Performance capability concept :
 To avoid need for ICAO selection between competing systems
 Manual on Required Navigation Performance (doc 9613)
 Addressed only the en-route phase of flight (RNP-10 and RNP-4) for
oceanic and remote applications
 No ICAO RNP requirements for continental enroute and terminal
applications. This led to:
 Proliferation of national standards
 Wide variety of functional requirements
 Variety of required navigation sensors
 Differing air crew requirements
 Lack of global harmonization
IFALPA ATC Meeting
4
Background
Industry’ s RNP concept
RNP concept has continued to evolve outside ICAO
 RTCA/EUROCAE defined performance and functional
requirements
 Industry‘s RNP requires performance monitoring and alerting
Conflict
 Current ICAO concept does not require performance
monitoring and alerting
 Now we have two RNP concepts.
IFALPA ATC Meeting
5
Are we now going the right way?
P
R
E
S
E
N
T
Europe
US
B-RNAV
Boeing
P-RNAV
Australia
RNP
US-RNAV
China
Airbus
Canada
RNP10
Japan
South
America
RNP 4
RNP/RNAV
F
U
T
U
R
E
Not safe, not efficient, costly, confusing
IFALPA ATC Meeting
6
RNP in relation to area navigation
Area
Navigation
Other
RNAV
RNP
IFALPA ATC Meeting
7
RNP-where we are today
Area
Navigation
RNP
RNAV (GNSS)
LAAS
Other
USRNAV A
Basic-GNSS
LNAV
USRNAV B
RNP
LNAV/VNAV
PRNAV
APV
SBAS
etc
LPV
GBAS
etc.
GAGAN
Baro-VNAV
GRAS
Galileo
WAAS
BRNAV
IFALPA ATC Meeting
RNAV
8
ICAO Recognizes the problems
 Need for focal point in ICAO to address problems
experienced with RNP Concept (GNSSP/4
recommendation 1/1)
 ANC approves establishment of Required
Navigation Performance Special operational
requirements Study Group (RNPSORSG) as
coordinating group
IFALPA ATC Meeting
9
Adjustment to the RNP
concept required
 Clear distinction between operations that require performance
monitoring and alerting and operations that don’t require
performance monitoring and alerting
 Functionality requirements
 Harmonization of current RNAV and RNP operations
 Development of new navigation specification to meet
operational demand.
 Need for clear operational approval requirements
 Need for clear implementation guidance
IFALPA ATC Meeting
10
RNP revised towards PBN
PBN is anchored in detailed
navigation specifications, which
contain performance and
functionality requirements.
Area
Navigation
PBN
Other
Other
RNAV
RNP
RNAV
RNAV x
RNP x
No on-board
on-board
performance
monitoring
+ alerting
performance
monitoring
+ alerting
IFALPA ATC Meeting
11
Harmonization of existing navspecs
Simplification results
in lower costs for
Operators and ANSP
Area of
Application
Nav
accuracy
Designation of
navigation standard:
Current situation
Designation of
navigation
specification:
PBN concept
(new)
10
RNP 10
RNAV 10
(RNP 10 label)
4
RNP 4
RNP 4
EnRouteContinental
5
RNP 5
Basic RNAV
RNAV 5
En Route Continental
and Terminal
2
USRNAV type A
RNAV 2
Terminal
1
USRNAV type B and
P-RNAV
RNAV 1
Oceanic/
Remote
IFALPA ATC Meeting
12
Harmonization of RNAV operations not
covered by existing nav specs
Area of
Application
Nav
accuracy
(NM)
Basic-GNSS
SBAS
Terminal
1
Approach
1-0.3
Approach
Designation of
navigation standard:
Current situation
1-0.1
Basic-GNSS
(Baro-VNAV)
SBAS
RNP SAAAR (US)
IFALPA ATC Meeting
Designation of
navigation
specification:
PBN concept
(new)
Basic-RNP 1
RNP APCH
RNP AR APCH
13
Approach and Approach
landing
procedures
operation
vertical
guidance
required
minima type
Flight technique
NPA
RNP APCH
no
MDA
dive and drive
CDFA (e.g. using barovnav)
APV
RNP APCH
RNP AR APCH
barometric
DA
vertical guidance
SBAS APV I/II
geometric
DA
vertical guidance
GBAS Cat I
geometric
DA
vertical guidance
PA
IFALPA ATC Meeting
14
RNP SORSG
Performance Based Navigation Concept
Performance based
Navigation Concept
Navigation Specifications
containment
No without
perf. monitor
and alerting
RNP10
RNAV 10
Navigation Specifications
requiring
containment
Perf.
Monitor
and alerting
RNAV 5
RNAV 2
RNAV 1
RNP
4, Basic-RNP
RNP1,
RNP 2, 1
RNP
APCH,
RNP4,
RNP0.3 - 0.1
RNP AR APCH
RNP with addtional
requirements
(e.g. 3D, 4D)
Performance based navigation (PBN)
Area navigation based on performance requirements for
aircraft that are described in navigation specifications
IFALPA ATC Meeting
15
ICAO Provisions
Performance Based Navigation Manual
 PBN Manual to provide a “one-stop shop” for States on
how to implement RNAV and RNP in their airspace
 PBN Manual consists of two volumes:
 Volume I – Concept and Implementation Guidance
 Concept of PBN and how it is used
 Implementation Guidance to States / Regions
 Volume II – Implementing RNAV and RNP
 Compendium of Navigation Specifications
RNAV 10
RNAV 1
RNP APCH
RNAV 5
RNP 4
RNP AR APCH
RNAV 2
Basic RNP 1
Advanced RNP 1*
RNP 2*
* Work in progress
IFALPA ATC Meeting
16
Current status
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
IFALPA ATC Meeting
17
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: 100% by 2014
IFALPA ATC Meeting
18
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: 100% by 2016
IFALPA ATC Meeting
19
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
IFALPA ATC Meeting
20
Implementation
 Leadership role for ICAO
 Familiarization
 Implementation
 Optimization of ICAO provisions
 States
 Develop implementation plan by 31/12/2009
 Follow through with plan
 Stakeholders
 cooperate with States in their implementation
 commit the resources necessary to carry out their part of
the strategy
IFALPA ATC Meeting
21
Familiarization
- Computer Based Training
IFALPA ATC Meeting
22
Familiarization
“Introduction to PBN” Seminar
Moscow
Montreal
13-15 June 2007
14-18 April 2008
Brussels
21-25 April 2008
Cairo
Mexico City
New Delhi
12-14 November
23-27 June 2008
Bangkok
2007
Dakar
14-18 January
2008
Lima
17-21 September 2007
Nairobi
10-14 September 2007
21-25 January 2008
16-20 June 2008
IFALPA ATC Meeting
23
Summary
 PBN concept is established
 Familiarization is imminent
 ICAO must assume leadership role in
implementation:
 Close coordination between ANB, TCB and
regional offices necessary
 Speak with one voice to States and
stakeholders
 Commitment and active involvement required from
States and other stakeholders.
IFALPA ATC Meeting
24