Upload
others
View
2
Download
0
Embed Size (px)
Citation preview
September, 2005
Naverus, Inc. 1
September, 2005
THIRD ICAO CAR/SAM RNP/RNAV SEMINAR
September, 2005
2
AGENDA
What is Performance-Based Nav?
The Four Components
About Criteria
Practical Examples
Safety, Access, Efficiency, Capacity
How to Make it Work
September, 2005
3
WHAT IS PERFORMANCE-BASED NAV?
A method of airspace management that establishes
nav system requirements, instead of specifications, that
permits safety, access, efficiency, and capacity.
September, 2005
4
WHAT IS PERFORMANCE-BASED NAV?
Benefits of Performance-based NAS well known
Opportunity to improve safety and economics simultaneously, by combining:
Criteria
Aircraft
Operations
ATS
September, 2005
5
WHY PERFORMANCE-BASED?
RNP or RNAV?ContainmentWith complete contingency planning
Nav system failuresEngine failuresPre- or post-MAP go-aroundSpeedsWinds
September, 2005
6
OK, BUT HOW?
Containment, by definition, requires incorporation of total system performance Regulatory basis emerging
CriteriaAircraft systemsOperationsATS implementation
Navigation system integrityDME/DME availabilityGPSNav Data
September, 2005
Naverus, Inc. 2
September, 2005
7
RNAVSBAS GBAS
NoGBNA
OK, BUT HOW?
Starting with RNAV 5 and 2 routes (8 nm center)RNAV SIDs/STARs at 2 and 1RNP SAAAR 0.10 approachesSBAS in parallelGBAS in parallel
September, 2005
8
NAVERUS OVERVIEW
Company:Founded February 2003Based in Renton, Washington41 people
Strengths:People, processes, and tools for necessary scale and cycle timeFocus on performance and operationsFlight management systems and navigation dataSupport for regulators
September, 2005
9
NAVERUS OVERVIEW
Naverus produces performance-based navigation solutions for operators
Full range of productsProcedures
Operations and maintenance services
Regulatory support products
Flight data monitoring
September, 2005
10
NAVERUS PRODUCT OVERVIEW
Operations Deployment Obstacle surveys, validation flights
Support for regulatory ops approval
Operations & MaintenanceGPS Performance Dispatch
Departure performance engineering
Sapphire: Nav data change monitoring
Flight data monitoring analysis
September, 2005
11
RNP OPERATIONS: WHAT HAVE WE LEARNED?
May, 1995 to now: 10+ years of RNP
Focus on multi-sensor aircraft with AFM authorization for RNP Operations
Experience with Boeing/Airbus aircraft has validated:
Airworthiness of aircraft & multi-sensor systemsSuitability of procedure design criteriaOperational elementsATS
September, 2005
12
AIRWORTHINESS OF AIRCRAFT & SENSORS
Flight Data Monitoring
AvailabilityIntegrityGPS accuracy (HFOM)Barometric VNAV performanceLateral & verticalpath tracking
Distribution of ANP Values
0
20
40
60
80
100
120
140
160
180
200
-
0.0
2
0.0
4
0.0
6
0.0
8
0.1
0
0.1
2
0.1
4
0.1
6
0.1
8
0.2
0
0.2
2
0.2
4
0.2
6
0.2
8
0.3
0
ANP (nm)
Obs
erva
tion
s
September, 2005
Naverus, Inc. 3
September, 2005
13
AIRWORTHINESS OF AIRCRAFT & SENSORS
2 x RNP 0.15 nm
1 x RNP 0.15 nm
GPS SPS Std 95%
GPS Measured, Worst Site, 95%
GPS Measured, Avg, 95%
Flight Technical Error, Measured, 95%
September, 2005
14
AIRWORTHINESS OF AIRCRAFT & SENSORS
Crosstrack FTE Histogram
0
50
100
150
200
250
300
350
400
-0.06 -0.04 -0.02 0.00 0.02 0.04 0.06 0.08
Deviation
Obs
erva
tions
Mean: -0.002 nmStandard Deviation: 0.0146 nmTotal points: 573Implied FTE (2σ): 0.0285 nm
September, 2005
15
AIRWORTHINESS OF AIRCRAFT & SENSORS
Vertical FTE Histogram
0
10
20
30
40
50
60
70
80
90
100
-80 -60 -40 -20 0 20 40 60 80Deviation (ft)
Obs
erva
tions
Mean: 0.35 ftStandard Deviation: 17.82 ftTotal points: 365Obs > -49' 99.73%
September, 2005
16
CRITERIA
Range of criteria dealing with performance-based navigationPANS-OPS
FAA 8260
FAA Notice
Naverus
September, 2005
17
CRITERIA
SPECIALFAA AC 120-29A
Special SAAARFAA N 8000.300
Public SAAARFAA Order 8260.52
Public RNAV PANS-OPS/TERPS
Perform
ance
App
licab
ility
September, 2005
18
September, 2005
Naverus, Inc. 4
September, 2005
19
CRITERIA
0
2
4
6
8
10
12
14
16
18
20
0
50
10
0
15
0
20
0
25
0
30
0
35
0
40
0
45
0
50
0
55
0
60
0
65
0
70
0
75
0
80
0
85
0
90
0
95
0
10
00
10
50
11
00
11
50
12
00
12
50
13
00
13
50
14
00
HAT (ft)
# of
App
roac
hes
RNP 0.10 RNP 0.30
September, 2005
20
OPERATIONAL ELEMENTS
Procedures & process demonstrated for:Insuring integrity of navigation databases
Forecasting GPS availability
Flight crew & dispatch training
Flight crew procedures
Ops SpecsDefines operational requirements
September, 2005
21
ATS CONSIDERATIONS
ATSNeed the clearance!WestJet has RNP to every runway endATS integration
STAR integrationRNP transitions where it makes sense
Reduced separation standardsReduced radar requirements
September, 2005
22
AGENDA
What is “RNP”?
The Four Components
About Criteria
Practical Examples
Safety, Access, Efficiency, Capacity
How to Make it Work
September, 2005
23
W002W.23
September, 2005
24
September, 2005
Naverus, Inc. 5
September, 2005
25
September, 2005
26
W002W.26
September, 2005
27
JUNEAU, ALASKA
Runway 8 IFR arrival: 1000+ feet and 2+ milesRunway 26 IFR arrival: none
September, 2005
28
RUNWAY 8 MISSED APPROACH POINT
September, 2005
29
OFFSET LDA APPROACH
September, 2005
30
RNP RNAV RW08
September, 2005
Naverus, Inc. 6
September, 2005
31
JUNEAU GASTINEAU CHANNEL
September, 2005
32
RNP RNAV RW26
September, 2005
33
RNP RNAV RW26
September, 2005
34
September, 2005
35
SAN FRANCISCO, CALIFORNIA
September, 2005
September, 2005
Naverus, Inc. 7
September, 2005
37
September, 2005
38
Washington, DC
September, 2005
39
Washington, DC
September, 2005
40
Washington, DC
September, 2005
41
Washington, DC
September, 2005
42
CUSTOMERS WORLDWIDE
B737-300
B737-700
B737-800
B747-400
B757-200
A320
September, 2005
Naverus, Inc. 8
September, 2005
43
TYPICAL IMPLEMENTATION FLOW
Start Project
Preliminary Design
Prototype Design
Validation Test Flight
Ops Approval
Flight
Digital Terrain Model
ALPHA Design
BETA Design
Final Revisions
Customer/ATS Concurrence?
YESNO
Customer/ATS Concurrence?NO
YES
Understand requirementsValidate designSecure Ops ApprovalDeploy
September, 2005
44
NAVERUS RESULTS: IMPROVED ACCESS
Before RNP:Limited to B737-300, special crew
Additional Qualified Pilot on Jump Seat forContingency
Departure constraints:Limited Payload - Block 24 seatsLow Wx in Australia: tech stop in Christchurch, refuel
Departure minima: 4200’ (AMSL) & 5 km
With RNP:
Use B737-800, any crew
Departure constraints reduced:
Full plane passenger capacity
No refueling hop –straight to Sydney with fuel to spare
September, 2005
45QUEENSTOWN, NZ (NZQN) September, 2005
46QUEENSTOWN, NZ (NZQN)
September, 2005
47QUEENSTOWN, NZ (NZQN) September, 2005
48
QUEENSTOWN, NZ (NZQN)
September, 2005
Naverus, Inc. 9
September, 2005
49
RNP RNAV 1 RW 27
September, 2005
50
RNP RNAV 1 RW 09
September, 2005
51
RNP RNAV 3 RWY 09
September, 2005
52
ECHO ONE DEPARTURE
September, 2005
53
ENGINE FAIL RW 27
September, 2005
54
HEAVY ONE DEPARTURE
September, 2005
Naverus, Inc. 10
September, 2005
55
ENGINE-FAIL RW 09
September, 2005
56
RNP RNAV = SAFETY
Stabilizes approaches; reduces CFIT risk
Positive vertical and lateral guidance
Improves safety by providing the best available contingency plan and easy crew compliance in rare event of failure
Optimizes path for terrain/obstacle avoidance
Simplifies crew training thereby reducing training costs, assures maximum safety
Coding procedures standardizes operations
BenefitFeature
September, 2005
57
RNP RNAV = IMPROVED ACCESS
Improves access at airports with weather/terrain challenges
Reduces minima [DA(h)] for approach
Provides better access to operators now, without waiting for deployment of ground-based infrastructure
Relies on on-board avionics, not ground-based infrastructure
Allows tailoring of flight path to satisfy air traffic/airspace constraints, abate noise, environmental, or political concerns
Tight/consistent containment
BenefitFeature
September, 2005
58
5km
5km
13780’ (2077’)
12614’ (903’)
ILS
RNP 0.3
09Lhasa ZULS
1 nm1.25 nm.50 nm
1060’ (776’)1220’ (923’)548’ (250’)
GPSNDBRNP 0.1
24Guam PGUM (preliminary)
5 km5 km2000 m
3800’ (2629’)4200’ (3029’)1421’ (250’)
VOR DME CVOR DME BRNP 0.1
23Queenstown NZQN
3 nm3 nm1 nm
3560’ (2151’)2840’ (1431’)1736’ (360’)
RNAV (GPS)NDB-BRNP 0.1
34Kelowna CYLW
VisibilityDA(h)ApproachRwyAirport
NAVERUS RESULTS: IMPROVED ACCESS
September, 2005
59
EFFICIENCY GAINS: WEST JET
TIM MORGAN, Senior VP Ops & Co-founder of West JetFrom Aviation Week, 2/28/2005:
September, 2005
60
September, 2005
Naverus, Inc. 11
September, 2005
61
?Asset utilization
?Lower minimums
?Navaid outages
?Training/ops simplification
?Payback of development costs, in weeks
Payback
?Averted delays, /week
?Route savings, per airport
Assumptions
Net Benefit
SUBSTANTIAL TOTAL BENEFITS
September, 2005
62
RNP RNAVSBAS GBAS
NoGBNA
How do you get started?
Use 8260.52, AC 90-RNP now (“public”)Focus on a controlled set of aircraftAccommodate specials and use the appropriate criteria where safety dictatesContinue to work augmentation programs to expand all-weather operations capabilityUse available expertise and experience to accelerate early benefits and justify equipage
September, 2005
THIRD ICAO CAR/SAM RNP/RNAV SEMINAR
September, 2005
64
Backup Slides
September, 2005
65
September, 2005
66