Geoff Burtenshaw

Directorate of Airspace Policy

UK Civil Aviation Authority
EASA Guidance Material for PBN
EASA Guidance Material for PBN
2 14 October 2008 PBN Implementation Task Force
Overview
Overview
Use and scope of navigation specifications
Navigation specifications and the approval process
Relationship with existing criteria
Navigation specification template
Status of EASA Guidance Material
Summary
3 14 October 2008 PBN Implementation Task Force
Use and Scope of Navigation
Use and Scope of Navigation
Specification by Flight Phase
Specification by Flight Phase
4 RNP 4
1 - 0.1 0.3 - 0.1 1 - 0.1 1 - 0.1 RNP AR APCH
1 0.3 1 1 RNP APCH
1 1 1 1 1 Basic-RNP 1
1 1 1 1 1 1 RNAV 1
2 2 2 RNAV 2
5 5 RNAV 5
10 RNAV 10 (RNP 10)
Missed Final Intermed Initial DEP
APPROACH
ARR
En Route
Continental
En Route
Oceanic /
Remote
FLIGHT PHASE
NAVIGATION
SPECIFICATION
PBN Manual includes airworthiness, operational and training guidance:
4 14 October 2008 PBN Implementation Task Force
Navigation Specification
Navigation Specification
Overview of Specific Navigation Services
Overview of Specific Navigation Services

D/D/IRU

RNP AR
APCH

RNP APCH

Basic-RNP 1

RNP 4

RNAV 2/1

RNAV 5

RNAV 10
D/VOR D/D IRU GNSS
5 14 October 2008 PBN Implementation Task Force
Use and Scope of
Use and Scope of
Navigation Specifications
Navigation Specifications
ICAO navigation specifications do not address all
airspace requirements (e.g., comm, surv) necessary for
operation in a particular airspace, route or area
These will be listed in the AIP and ICAO Regional
Supplementary Procedures
Incumbent upon States to undertake a safety
assessment in accordance with provisions outlined
in Annex 11 and PANS-ATM, Chapter 2
ICAO PBN Manual provides a standardised set of
criteria, but is not a stand-alone certification document
Examples: RNP 4, RNAV 1, RNP AR APCH
6 14 October 2008 PBN Implementation Task Force
Navigation Specifications and the
Navigation Specifications and the
Approval Process
Approval Process
Navigation specifications are used by States as basis for aircraft
certification and operational approval
A navigation specification does not in itself constitute regulatory
guidance material
Aircraft approved by State of manufacture
Operators approved in accordance with their National
Operating Rules
Compliance with one navigation specification does not guarantee
compliance with another
7 14 October 2008 PBN Implementation Task Force
Relationship with Existing Criteria
Relationship with Existing Criteria
Not re-inventing the wheel
Taking existing criteria e.g., Orders, ACs, AMC, and
TGL etc.
A more logical structure
Common format and content
More complete to enable uniform implementation
8 14 October 2008 PBN Implementation Task Force
Navigation Specification
Navigation Specification
Template
Template
Common Organisation of Volume II, Parts B and C
X.1 Introduction
X.2 ANSP Considerations
X.3 Navigation Specification
X.4 References
Where X represents the chapter number
9 14 October 2008 PBN Implementation Task Force
Navigation Specification
Navigation Specification
Section X.3 Section X.3
Background
Approval process
Aircraft requirements
Operating procedures
Pilot knowledge and training
Navigation database
Oversight of operators
10 14 October 2008 PBN Implementation Task Force
Navigation Specification
Navigation Specification
Section X.3 Section X.3 : Approval Process : Approval Process
Aircraft Eligibility
Must be demonstrated
Can be based on Aircraft Flight Manual or supplemental
information
Operational Approval
Operating procedures
Flight crew training
Control of navigation database process, where required
Approval obtained in accordance with State operating rules
11 14 October 2008 PBN Implementation Task Force
Navigation Specification
Navigation Specification
Section X.3 Section X.3 Aircraft Requirements Aircraft Requirements
Performance Requirements
Accuracy, Integrity, Continuity, GNSS signal-in-space
Performance monitoring and alerting
Only applicable for RNP systems
Criteria for Specific Navigation Services
Defines allowable systems and required performance
Functional requirements
Just as important as performance
Navigation database requirements
When required
12 14 October 2008 PBN Implementation Task Force
Navigation Specification
Navigation Specification
Section X.3 Section X.3 Operating Procedures Operating Procedures
Pre-flight planning
General operating procedures
During the flight
Performance expectations (deviation from path)
Pilot has critical role in performance monitoring
Contingency procedures
E.g. procedure in case of RNAV system failure
13 14 October 2008 PBN Implementation Task Force
Navigation Specification
Navigation Specification
Section X.3 Section X.3 Pilot Knowledge and Training Pilot Knowledge and Training
Lists training tasks considered important, which may
already be part of operators training program
System-specific information on how navigation
system functions is vital to success
14 14 October 2008 PBN Implementation Task Force
PBN Navigation Specifications
PBN Navigation Specifications
and EASA Guidance material
and EASA Guidance material
AMC 20-26
RNP AR APCH
AMC 20-27
RNP APCH
See RNAV 1
Basic-RNP 1
PP045 Information paper (ops.013)
RNP 4
JAA TGL No. 10
RNAV 1
See RNAV 1
RNAV 2
AMC 20-4
RNAV 5
AMC 20-12
RNAV 10 (RNP 10)
EASA Guidance Material
Navigation Specification
15 14 October 2008 PBN Implementation Task Force
Status of EASA Guidance Material
Status of EASA Guidance Material
AMC 20-12 (RNP 10)
Published December 2006
Recognition of FAA Order 8400.12a for RNP 10
operations
AMC 20-4 (Basic RNAV)
Transposed from JAA TGL No. 2
Published November 2003
PBN navigation specification for RNAV 5 based
directly on B-RNAV
16 14 October 2008 PBN Implementation Task Force
Status of EASA Guidance Material
Status of EASA Guidance Material
JAA TGL No. 10 (Precision RNAV)
Published November 2000
P-RNAV fulfils all of the PBN requirements for RNAV 1
operations using DME/DME or GNSS
EASA transposing JAA guidance into AMC (AMC 20-16)
Updating criteria, bringing more into line with the PBN
Manual and adding RF path terminator as an option
Publication not until early 2011 due to slippage of the EASA
Rulemaking Programme
P-RNAV = RNAV 2 where the environment does not support
1 NM accuracy
P-RNAV = RNAV 1 = Basic RNP 1 where the sensor used is
GNSS or the aircraft is RNP qualified
17 14 October 2008 PBN Implementation Task Force
Status of EASA Guidance Material
Status of EASA Guidance Material
PP045 Information Paper (RNP 4)
References
FAA Order 8400.33
State Letter Ref AN 13/33.7-04/86
PBN Manual Doc 9613
Other operational material e.g., EU-OPS 1.243, Annex 6 and
Doc 7030/4
AMC for RNP 4 drafted and RIA prepared
Passed to EASA Rulemaking Directorate and assigned
Tasking OPS.013
Yet to appear in the Rulemaking Programme
18 14 October 2008 PBN Implementation Task Force
Status of EASA Guidance Material
Status of EASA Guidance Material
AMC 20-27 (RNP APCH)
EASA published NPA 2008-14 in May of this year
Comment period closed and preparation of a Comment
Response Document (CRD) underway
Due to complexity of issues and significant number of
comments, will not be published before early 2009
AMC 20-26 (RNP AR APCH)
Status as above
AMC goes beyond the PBN Manual in terms of scope i.e.,
includes departure operations and application on
procedures more advanced than those designed in
accordance with ICAO RNP AR Manual, Doc 9905
19 14 October 2008 PBN Implementation Task Force
Status of EASA Guidance Material
Status of EASA Guidance Material
Although not in the PBN Manual, EASA is also
catering for SBAS APV approach operations (LPV)
Draft AMC 20-28 in preparation
Publication not until early 2011
20 14 October 2008 PBN Implementation Task Force
Summary
Summary
EASA has good coverage of existing PBN Navigation
Specifications
AMC either published or under development
providing means for issuing airworthiness and
operational approvals
Concerns regarding the slippage in the Rulemaking
Programme and delayed AMC 20-16, AMC 20-28 and
OPS.013
General concern regarding ability of the Agency to
keep pace with emerging Navigation Specifications
21 14 October 2008 PBN Implementation Task Force
QUESTIONS?
QUESTIONS?