2003 2005 Capabilities Working Group Report to the Steering Committee

1
2003 - 2005 Capabilities Working Group Report
to the Steering Committee
Roger Wall 2 December 1999
2
2
03-05 WG Participants
Air Line Pilots Association Air Transport
Association ATA CDM Working Group Aircraft
Owners and Pilots Association American
Airlines ARINC Center for Advanced Aviation
System Development Delta Air Lines Department of
Defense Federal Aviation Administration (ATO,
ATA, ARS, AOZ, ASD, AAR) FAA SETA Federal
Express National Aeronautics and Space
Administration National Air Traffic Controllers
Association National Business Aviation
Association United Airlines US Airways
3
03-05 August 1999 Recommendation Overview

• Address national flow issues
• Establish nationwide backbone infrastructure to
  predict airspace density, provide equitable
  resource allocation strategies, collaborative
  routing, and facilitate transition through ARTCC
  airspace
• Implement procedures and tools to support
  collaborative routing in response to dynamically
  changing traffic situations
• Implement collaborative routing down to the
  facility level
• Collaboration includes ATC facilities (ATCT,
  TRACONs, ARTCCs, ATCSCC), airline facilities
  (AOCs)
• Provide Uniform National Ultra-High Altitude
  service
• Leverage aircraft technologies to increase access
  to terminal and en route airspace
• Continue to reduce ocean separation standards
  with 30/30 or 30/5 min as goal

4
Assumptions

• FFP1 is successful
• National spectrum availability will be
  sufficient to support desired services
• The following are high priority activities and
  are or will be addressed in other forums
• SF21
• CPDLC
• WAAS/LAAS
• OASIS/DUATS
• RNAV/RNP routing
• Safety focused activities
• Near term procedures (identified in RTCA
  Addendum 2)
• ADS-B closely spaced parallels

5
Next Steps Assigned by Steering Committee for
December Meeting

• FAA immediately identify an advocate for 03 - 05
  capability implementation to influence budget
  plans
• FAA propose an implementation strategy for 03 -
  05 recommended capabilities
• 03-05 Working Group continue joint
  industry/government collaboration on refinement
  and assessment of recommendations
• First collaborative meeting between FAA and 03-05
  working group by mid-October 1999 (complete)
• Complete activities in time to brief December
  Steering Committee meeting
• 03-05 Working Group begin writing Addendum 3

6
Flow Problem Range
7
Required Functionality Overview
ATCSCC
ARTCC
TRACON
AIRPORT
Airspace redesign, Environment, Procedures, Sep
Stds, Spectrum, Training
Uniform National Ultra-High Altitude Service
Collaborative Routing
Extend Visual Ops
Dynamic Density Prediction
Improve Access to flight traffic info
Improve Surface Ops
Conflict Prediction Trial Planning
Arrival / Departure Routing, new TERPS
Equitable Resource Allocation
Surface Movement
Sequencing Spacing
Collaborative Routing
Departure Runway Balancing
Arrival Runway Balancing
Resource Allocation
Dynamic Resectorization
Cockpit situational awareness/ advanced Navigation
Inner Phase 200-100 Miles
Outer Phase 800-500 Miles
Middle Phase 500-200 Miles
8
Summary of Problem Priorities/Needs

• System-wide problems resulting in delays and
  other inefficiencies (e.g., en route congestion,
  severe weather)
• Improved information availability and flow
• System-wide problem prediction and equitable
  resource allocation
• Efficient aircraft movement thru en route
  airspace
• Increased use of RNAV/RNP capabilities to gain
  greater access to en route and terminal airspace
• Reduced separation and increased flexibility
• Flow efficiency within transition airspace
• Efficient arrival collection from en route
  airspace
• Efficient departure integration into overflight
  streams
• Airport acceptance and departure rates
• Increased arrival and departure throughput
• Inefficient airport surface operations
• Better information and management systems

9
Problem Priorities/Needs

• System-wide problems resulting in delays and
  other inefficiencies (e.g., en route congestion,
  severe weather)
• Improved information availability and flow
• System-wide problem prediction and equitable
  resource allocation
• Efficient aircraft movement thru en route
  airspace
• Increased use of RNAV/RNP capabilities to gain
  greater access to en route and terminal airspace
• Reduced separation and increased flexibility
• Flow efficiency within transition airspace
• Efficient arrival collection from en route
  airspace
• Efficient departure integration into overflight
  streams
• Airport acceptance and departure rates
• Increased arrival and departure throughput
• Inefficient airport surface operations
• Better information and management systems

10
System-Wide Needs Solutions

• Need Improved information availability and flow
• 03-05 Recommendation Continue to expand CDM for
  all NAS users and FAA (ATCSCC and field
  facilities) to achieve
• An integrated and common set of tools for
  arrival/departure and en route constraint
  management
• A stable, robust communication infrastructure
  that provides for dynamic information exchange
• Distribution of constraint information and
  analytical measures of uncertainties associated
  with constraint/demand forecasts
• Common display mechanisms
• Equitable and efficient resource allocation
  mechanisms with user interaction
• A system impact assessment capability that
  measures the effectiveness of TFM initiatives
• Sufficient TFM bandwidth to support the items
  listed above

11
System-Wide Needs Solutions (contd)

• Need System-wide problem prediction and
  equitable resource allocation
• Accurate airspace density prediction
• Collaborative routing solutions to address
  specific sectors in specific areas
• Impact assessment of proposed solutions,
  including airspace reallocation
• Equitable allocation of limited resources to
  balance demand density across NAS
• 03-05 Recommendation
• Collaborative Routing
• Coordination Tools (CRCT)
• Priority RD
• Provide initial equitable allocation
• of limited resources

12
System-Wide Needs Solutions (
contd
)
Collaborative Routing Coordination Tools (CRCT)
ZSE
Seattle
2
ZMP
ZBW
Minneapolis
Boston
ZLC
1
1
1
Salt Lake
ZOB
ZAU
ZNY
2
Cleveland
ATCSCC
Chicago
New York
ZOA
1
1
1st Priority
ZDV
1
Oakland
ZID
Denver
2
ZKC
Indianapolis
2
ZDC
Kansas City
2
1
Washington
ZTL
ZLA
1
ZME
Atlanta
1
Los Angeles
ZAB
Memphis
1st Priority
1
Albuquerque
1
1
ZFW
2
1
2
2nd Priority
Fort Worth
ZJX
Jacksonville
ZHU
1
1
Houston
ZMA
Miami
Note This graphic may not print correctly.
Please see the numbers for priorities or refer to
the screen view.
13
System-Wide Needs Solutions (contd)

• Need Efficient aircraft movement thru en route
  airspace
• Eliminate restrictions - Impose constraints only
  as needed
• Expand NRP
• Reduce controller workload
• 03-05 Recommendation Expand use of Conflict
  Probe based on
• URET CCLD with enhancements

14
System-Wide Needs Solutions (
contd
)
URET CCLD Expansion
ZSE

Seattle
2
ZMP
ZBW

Minneapolis
Boston
ZLC

1
1
Salt Lake
ZOB
ZAU
ZNY


2
Cleveland
Chicago
New York
ZOA

ZDV

1
Oakland
ZID
Denver
2
ZDC
ZKC
Indianapolis
FFP1 Sites
1
Washington
Kansas City
2
ZTL
ZLA

1
ZME
1st Priority
1
Atlanta
Los Angeles
ZAB

Memphis
Albuquerque
2
1
ZFW

2nd Priority
1
Fort Worth
ZJX

1
Jacksonville
ZHU

1
Houston
ZMA

Miami
Note This graphic may not print correctly.
Please see the numbers for priorities or refer to
the screen view.
15
System-Wide Needs Solutions (contd)

• Need Efficient aircraft movement thru en route
  airspace
• Achieve uniform service across the NAS supporting
  Free Flight
• 03-05 Recommendation National Ultra-High
  Altitude Service
• Uniform definition of Ultra-High in all centers
• Uniform procedures for Ultra-High
• Domestic RVSM in Ultra-High Altitude Sectors
• Establish a NAS infrastructure that
• Is information, not sensor-based
• Provides consistent information independent of
  facility boundaries
• Facilitates the introduction of improved
  surveillance information
• Requirements include
• Spectrum allocation changes
• Coordination with RTCA SC-192
• FAA domestic RVSM focal point

16
System-Wide Needs Solutions (contd)

• Need Increased Access to En Route and Terminal
  Airspace
• 03-05 Recommendation Account for the RNAV/RNP
  capability of fixed wing and rotary aircraft in
  Terminal Airspace
• Provide more/improved ingress egress routes
• Provide more/improved transitions through
  terminal airspace (VFR IFR)
• Provide new approaches and departures based on
  RNAV/RNP (procedures, airport obstruction
  surveys, EIS, new TERPS, lighting requirements)
• 03-05 Recommendation Account for the RNAV/RNP
  capability of aircraft in En Route Airspace
• Provide communications capability and procedures
  to allow traversing low-altitude areas that do
  not have radar coverage

17
System-Wide Needs Solutions (concld)

• Need Reduced separation and increased
  flexibility in oceanic airspace
• 30nmi/30nmi or 30nmi/5 min separation standards
• Capability to conduct paired maneuvers
• More flexibility and access in the Gulf, WATRS,
  and Caribbean through improved navigation and
  surveillance
• 03-05 Recommendations
• Continue to support initiatives addressed in
  other forums (e.g., ADS (Contract), ADS
  (Broadcast), CPDLC, RVSM, CDTI, etc.)
• Ground infrastructure to support their use

18
Problem Priorities/Needs

• System-wide problems resulting in delays and
  other inefficiencies (e.g., en route congestion,
  severe weather)
• Improved information availability and flow
• System-wide problem prediction and equitable
  resource allocation
• Efficient aircraft movement thru en route
  airspace
• Increased use of RNAV/RNP capabilities to gain
  greater access to en route and terminal airspace
• Reduced separation and increased flexibility
• Flow efficiency within transition airspace
• Efficient arrival collection from en route
  airspace
• Efficient departure integration into overflight
  streams
• Airport acceptance and departure rates
• Increased arrival and departure throughput
• Inefficient airport surface operations
• Better information and management systems

19
Transition Needs Solutions

• Need Efficient arrival collection from en route
  airspace
• Manage arrivals to meet Airport/TRACON/Area
  acceptance rates
• 03-05 Recommendation Expand use of Single
  Center Traffic Management Advisor (TMA)
• Single center/1 major airport
• (FFP1 TMA-SC)
• Priority RD TMA-MC
• Multiple centers/1 major airport
• Multiple centers/1 major airport

20
SEA
ZSE
3
ZBW
ZLC
MSP
1
3
BOS
ZMP
1
DTW
ZAU
2
ZOB
ZNY
ZOA
N90
SLC
ZDV
ORD
1
CVG
PIT
PHL
SFO
DEN
ZID
SDF
Potomac
2
STL
ZKC
LAS
1
2
ZDC
ZLA
MEM
CLT
ZTL
LAX
PHX
ZME
ZAB
2
ATL
ZFW
FFP1 Sites
3
2
DFW
ZJX
1
IAH
1st Priority
MCO
2
ZHU
2
2nd Priority
ZMA
3
3rd Priority
21
Transition Needs Solutions (concld)

• Need Efficient departure integration into and
  across en route streams
• 03-05 Recommendation Priority RD
• Departure integration into and across en route
  streams

22
Problem Priorities/Needs

• System-wide problems resulting in delays and
  other inefficiencies (e.g., en route congestion,
  severe weather)
• Improved information availability and flow
• System-wide problem prediction and equitable
  resource allocation
• Efficient aircraft movement thru en route
  airspace
• Increased use of RNAV/RNP capabilities to gain
  greater access to en route and terminal airspace
• Reduced separation and increased flexibility
• Flow efficiency within transition airspace
• Efficient arrival collection from en route
  airspace
• Efficient departure integration into overflight
  streams
• Airport acceptance and departure rates
• Increased arrival and departure throughput
• Inefficient airport surface operations
• Better information and management systems

23
Arrival/Departure Needs Solutions

• Need Increased arrival throughput
• Improve efficiency of operations within terminal
  airspace to single and multiple major airports
• 03-05 Recommendations
• Expand use of Passive Final Approach Spacing Tool
  (pFAST) - Airport
• Passive Final Approach Spacing Tool (pFAST) -
  TRACON
• Note CNS capabilities (e.g., ADS-B/CDTI) are
  activities addressed in other forums that can
  help address this need

24
Arrival/Departure Needs Solutions
pFAST
3
BOS
MSP
ORD
1
DTW
LGA
N
JFK
1
9
EWR
0
TEB
NOCAL
1
STL
3
SFO
1
LAS
PHL
1
2
CVG
BWI
P
O
2
T
DCA
O
2
CLT
M
1
IAD
A
C
ATL
LAX
DFW
FFP1 Sites
1
IAH
1
1st Priority
2
2nd Priority
3
3rd Priority
25
Arrival/Departure Needs Solutions (concld)

• Need Increased arrival/departure throughput
• Reduce arrival/departure separation due to wake
  vortex
• More efficient utilization of TRACON airspace for
  departures
• 03-05 Recommendation Priority RD
• Arrival and departure wake vortex detection
• Departure management in TRACON airspace

26
Problem Priorities/Needs

• System-wide problems resulting in delays and
  other inefficiencies (e.g., en route congestion,
  severe weather)
• Improved information availability and flow
• System-wide problem prediction and equitable
  resource allocation
• Efficient aircraft movement thru en route
  airspace
• Increased use of RNAV/RNP capabilities to gain
  greater access to en route and terminal airspace
• Reduced separation and increased flexibility
• Flow efficiency within transition airspace
• Efficient arrival collection from en route
  airspace
• Efficient departure integration into overflight
  streams
• Airport acceptance and departure rates
• Increased arrival and departure throughput
• Inefficient airport surface operations
• Better information and management systems

27
Airport Surface Needs Solutions

• Need Better information and management systems
• Digital TMA data to users for all airports using
  TMA
• Taxi Departure Clearance
• Runway Load Balancing
• Ramp Status
• Conformance Monitoring
• Surveillance
• Recommendation for 03-05 Expanded FAA/User
  Collaboration to implement User Initiatives
• Priority RD
• Conduct research in parallel with ongoing user
  initiatives

28
Implementation Definition

• Implementation of capabilities means delivery of
  services and benefits with the appropriate
  changes in airspace design, procedures, systems,
  logistics, labor negotiations, certification, etc.

29
Technology Implementation Readiness
9
Operate Implementation Capability
Actual System Proven In Operation
Actual System Qualified by Demonstration
8
Qualify Implementation Capability
System Prototype Demonstration in an Operational
Environment
7
Develop Implementation Capability
Define Requirements Transfer Technology
System/Subsystem Model or Prototype
Demonstration in a Relevant Environment
Component and/or Breadboard Validation in a
Relevant Environment
Component and/or Breadboard Validation in
Laboratory Environment
Analytical Experimental Critical Function -
Characteristic Proof-of-Concept
Technology Concept and/or Application Formulated
Describe Proposed Capability
Basic Principles Observed and Reported
TRL
IRL
30
Barriers to Implementation

• HW/SW for capabilities that have been identified
  can be available in 03-05, however the following
  must also, at a minimum, be addressed in order to
  realize benefits in 03-05
• Airspace design
• Environmental impact
• Labor negotiations
• Procedures
• Training
• Certification
• Spectrum
• Bandwidth (deployment and information)

31
Priority RD

• Additional RD activities have been identified as
  addressing priority needs and should be
  merged/accelerated to facilitate development of
  the best capabilities including
• Departure EDP with other departure efforts
• En Route E/DA, Direct-to, En Route Spacing Tool,
  and PARR
• Surface Surface Management System
• Arrival Active FAST
• Other areas for priority RD include
• Evolutionary progression toward distributed
  decision making
• Increased collaboration among users and service
  providers
• Wake vortex sensing and prediction

32
03-05 Need and Capability Summary
33
Acronyms