Geoff BurtenshawDirectorate of Airspace Policy
UK Civil Aviation Authority
EASA Guidance Material for PBNEASA Guidance Material for PBN
214 October 2008 PBN Implementation Task Force
OverviewOverview
Use and scope of navigation specificationsNavigation specifications and the approval processRelationship with existing criteriaNavigation specification templateStatus of EASA Guidance MaterialSummary
314 October 2008 PBN Implementation Task Force
Use and Scope of Navigation Use and Scope of Navigation Specification by Flight PhaseSpecification by Flight Phase
4RNP 4
1 - 0.10.3 - 0.11 - 0.11 - 0.1RNP AR APCH10.311RNP APCH
11111Basic-RNP 1
111111RNAV 1222RNAV 2
55RNAV 510RNAV 10 (RNP 10)
MissedFinalIntermedInitial DEP
APPROACH
ARREn Route
Continental
En Route Oceanic / Remote
FLIGHT PHASE
NAVIGATION SPECIFICATION
PBN Manual includes airworthiness, operational and training guidance:
414 October 2008 PBN Implementation Task Force
Navigation SpecificationNavigation SpecificationOverview of Specific Navigation ServicesOverview 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/VORD/DIRUGNSS
514 October 2008 PBN Implementation Task Force
Use and Scope of Use and Scope of Navigation SpecificationsNavigation 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 ProceduresIncumbent 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
614 October 2008 PBN Implementation Task Force
Navigation Specifications and the Navigation Specifications and the Approval ProcessApproval Process
Navigation specifications are used by States as basis for aircraft certification and operational approvalA navigation specification does not in itself constitute regulatory guidance material
Aircraft approved by State of manufactureOperators approved in accordance with their National Operating Rules
Compliance with one navigation specification does not guarantee compliance with another
714 October 2008 PBN Implementation Task Force
Relationship with Existing CriteriaRelationship with Existing Criteria
Not re-inventing the wheelTaking existing criteria e.g., Orders, ACs, AMC, and TGL etc.A more logical structureCommon format and contentMore complete to enable uniform implementation
814 October 2008 PBN Implementation Task Force
Navigation SpecificationNavigation Specification TemplateTemplate
Common Organisation of Volume II, Parts B and CX.1 IntroductionX.2 ANSP ConsiderationsX.3 Navigation SpecificationX.4 References
Where “X” represents the chapter number
914 October 2008 PBN Implementation Task Force
Navigation SpecificationNavigation SpecificationSection X.3Section X.3
BackgroundApproval processAircraft requirementsOperating proceduresPilot knowledge and trainingNavigation databaseOversight of operators
1014 October 2008 PBN Implementation Task Force
Navigation SpecificationNavigation SpecificationSection X.3Section X.3 : Approval Process: Approval Process
Aircraft EligibilityMust be demonstratedCan be based on Aircraft Flight Manual or supplemental information
Operational ApprovalOperating proceduresFlight crew training Control of navigation database process, where required
Approval obtained in accordance with State operating rules
1114 October 2008 PBN Implementation Task Force
Navigation SpecificationNavigation SpecificationSection X.3Section X.3 Aircraft RequirementsAircraft Requirements
Performance RequirementsAccuracy, Integrity, Continuity, GNSS signal-in-spacePerformance monitoring and alerting
Only applicable for RNP systemsCriteria for Specific Navigation Services
Defines allowable systems and required performanceFunctional requirements
Just as important as performanceNavigation database requirements
When required
1214 October 2008 PBN Implementation Task Force
Navigation SpecificationNavigation SpecificationSection X.3Section X.3 Operating ProceduresOperating Procedures
Pre-flight planningGeneral operating procedures
During the flightPerformance expectations (deviation from path)
Pilot has critical role in performance monitoringContingency procedures
E.g. procedure in case of RNAV system failure
1314 October 2008 PBN Implementation Task Force
Navigation SpecificationNavigation SpecificationSection X.3Section X.3 Pilot Knowledge and TrainingPilot Knowledge and Training
Lists training tasks considered important, which may already be part of operator’s training program
System-specific information on how navigation system functions is vital to success
1414 October 2008 PBN Implementation Task Force
PBN Navigation Specifications PBN Navigation Specifications and EASA Guidance materialand EASA Guidance material
AMC 20-26RNP AR APCH
AMC 20-27RNP APCH
See RNAV 1Basic-RNP 1
PP045 Information paper (ops.013)RNP 4
JAA TGL No. 10RNAV 1
See RNAV 1RNAV 2
AMC 20-4RNAV 5
AMC 20-12RNAV 10 (RNP 10)
EASA Guidance MaterialNavigation Specification
1514 October 2008 PBN Implementation Task Force
Status of EASA Guidance MaterialStatus of EASA Guidance Material
AMC 20-12 (RNP 10)Published December 2006Recognition of FAA Order 8400.12a for RNP 10 operations
AMC 20-4 (Basic RNAV)Transposed from JAA TGL No. 2Published November 2003PBN navigation specification for RNAV 5 based directly on B-RNAV
1614 October 2008 PBN Implementation Task Force
Status of EASA Guidance MaterialStatus of EASA Guidance Material
JAA TGL No. 10 (Precision RNAV)Published November 2000P-RNAV fulfils all of the PBN requirements for RNAV 1 operations using DME/DME or GNSSEASA 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 optionPublication not until early 2011 due to slippage of the EASA Rulemaking ProgrammeP-RNAV = RNAV 2 where the environment does not support 1 NM accuracyP-RNAV = RNAV 1 = Basic RNP 1 where the sensor used is GNSS or the aircraft is RNP qualified
1714 October 2008 PBN Implementation Task Force
Status of EASA Guidance MaterialStatus of EASA Guidance Material
PP045 Information Paper (RNP 4)References
FAA Order 8400.33State 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/4AMC for RNP 4 drafted and RIA preparedPassed to EASA Rulemaking Directorate and assigned Tasking OPS.013Yet to appear in the Rulemaking Programme
1814 October 2008 PBN Implementation Task Force
Status of EASA Guidance MaterialStatus of EASA Guidance Material
AMC 20-27 (RNP APCH)EASA published NPA 2008-14 in May of this yearComment period closed and preparation of a Comment Response Document (CRD) underwayDue to complexity of issues and significant number of comments, will not be published before early 2009
AMC 20-26 (RNP AR APCH)Status – as aboveAMC 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
1914 October 2008 PBN Implementation Task Force
Status of EASA Guidance MaterialStatus 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 preparationPublication not until early 2011
2014 October 2008 PBN Implementation Task Force
SummarySummary
EASA has good coverage of existing PBN Navigation SpecificationsAMC either published or under development providing means for issuing airworthiness and operational approvalsConcerns regarding the slippage in the Rulemaking Programme and delayed AMC 20-16, AMC 20-28 and OPS.013General concern regarding ability of the Agency to keep pace with emerging Navigation Specifications
2114 October 2008 PBN Implementation Task Force
QUESTIONS?QUESTIONS?