Terminal RNAV Procedure Implementation in the USA

1
Terminal RNAV Procedure Implementation in the USA

• Jeff Formosa
• 31January 2001

2
Acknowledgements

• FAA
• RNAV/RNP Program Office - ATP - 104
• Jeff Williams - Manager
• MITRE is supporting the FAA in implementing RNAV
  procedures
• Airlines
• Frank Alexander - Northwest Airlines
• Tracy Barnett - US Airways Airlines
• Jim Kaiser - American Airlines
• Steve Shaffer - Atlantic Coast Airlines
• Bill Vaughn - Continental Airlines
• NATCA
• John Raily - National
• Kevin Clearly - Eastern Region

3
Overview

• Status of RNAV activities
• Process streamlining and use of tools
• Benefits
• Issues
• Summary and Next Steps

4
RNAV Activities/Status(Approx.. 14,000 revenue
flights as of January 2001)
5
Highlights of Key Features of Process

• Collaborative effort
• FAA, lead carrier, controller union (NATCA),
  Jeppesen, and CAASD
• New streamlined process and design tool has
  reduced implementation time
• 20 steps repeatable process TARGETS tool
• Bi-weekly telecon and e-mail
• Start with overlay historical routes or vector
  procedures
• Eliminates environmental hurdles
• Prioritized list of procedures for incremental
  implementation
• Lead Carrier flight simulator testing
• Obtain Jeppesen Tailored RNAV chart
• Live validation period
• Public charting and public use

6
(No Transcript)
7
TARGETS(Design - Flyability - Simulation)
8
Waypoint Data Distribution
Degrees Minutes Seconds
Decimal Degrees
Degrees Minutes
9
Benefits of RNAV

• Improve Pilot/Controller situation awareness
• Reduced A/G communications
• Positive feedback from controllers and pilots
• Improve airspace and aircraft efficiencies
• Expected noise mitigation
• Foundation for USA National Airspace Redesign

10
KPHL - SPUDS1
11
(No Transcript)
12
RNAV Air/Ground Communications Reduction Benefit
ORD
DEN
DTW
MSP
OAK
BOS
EWR
LAX
PHL
LAS
ATL
PHX
STL
DFW
MIA
reduction in air/ground communications
Key assumptions Nominal air-ground Comm.
reduction of 4 Equipage levels
13
Key Issues Being Worked

• Automation Controller ability to distinguish
  between RNAV and non-RNAV aircraft
• Host automation
• Track-Ball Reroute
• ARTS scratch pad
• Charting Procedures
• Departure procedures and STARs
• Depicting multiple runways and multiple flows
• Increase to number of required charts
• Flight Management Computers
• Capabilities, ARINC changes, Leg types, Capacity
• Mixed equipage operations
• FAA Orders
• Criteria
• Phraseology
• Transition to RNP

14
Newark RNAV Departure Procedure
15
Summary - To Date

• RNAV procedures development is a collaborative
  effort
• Utilize a repeatable 20-step process and new FAA
  tool (TARGETS)
• Lessons Learned added to the process and TARGETS,
  and incorporated into FAA Orders, 7110.65, AIM,
  etc.
• Positive pilot and controller feedback
• Benefits
• Important Issues
• Charting
• Modify Automation to handle mix-equipage
  operations
• Phraseology
• Varying levels of avionics performance

16
Next Steps

• Procedure development
• Non-Overlays
• New FAA Regions
• Lessons learned
• Continue tracking and documenting
• Work with FAA and Industry - FAA Orders,
  automation, controller education, support,
  phraseology
• Conduct detailed benefits analysis
• RNAV process education
• Facility training, road shows, workshops

17
(No Transcript)