2003 - 2005 Capabilities Working Group Report to the ... · Problem Priorities/Needs System-wide problems resulting in delays and other* inefficiencies (e.g., en route congestion,

1

RTCA Select Committee on Free Flight Implementation

2003 - 2005 CapabilitiesWorking Group Report to the

Steering CommitteeRoger Wall

2 December 1999

2


2


03-05 WG ParticipantsAir Line Pilots AssociationAir Transport AssociationATA CDM Working GroupAircraft Owners and Pilots AssociationAmerican AirlinesARINCCenter for Advanced Aviation System DevelopmentDelta Air LinesDepartment of DefenseFederal Aviation Administration (ATO, ATA, ARS, AOZ, ASD, AAR)FAA SETAFederal ExpressNational Aeronautics and Space AdministrationNational Air Traffic Controllers AssociationNational Business Aviation AssociationUnited AirlinesUS Airways

3


03-05 August 1999 RecommendationOverview

• Address national flow issues• Establish nationwide backbone infrastructure to predict airspace

density, provide equitable resource allocation strategies,collaborative routing, and facilitate transition through ARTCCairspace

• Implement procedures and tools to support collaborative routingin 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 terminaland en route airspace

• Continue to reduce ocean separation standards with 30/30 or30/5 min as goal

4


Assumptions

• FFP1 is successful

• National spectrum availability will be sufficient to supportdesired services

• The following are high priority activities and are or will beaddressed 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 Committeefor December Meeting

• FAA immediately identify an advocate for 03 - 05 capabilityimplementation to influence budget plans

• FAA propose an implementation strategy for 03 - 05recommended capabilities

• 03-05 Working Group continue joint industry/governmentcollaboration on refinement and assessment ofrecommendations

• First collaborative meeting between FAA and 03-05working group by mid-October 1999 (complete)

• Complete activities in time to brief December SteeringCommittee meeting

• 03-05 Working Group begin writing Addendum 3

6


Flow Problem Range

7


Required Functionality OverviewATCSCC ARTCC TRACON AIRPORT

Airspace Redesign, Environment, Procedures, Sep Stds, Spectrum, Training

DynamicDensity

Prediction

EquitableResourceAllocation

DynamicResectorization

CollaborativeRouting

Conflict PredictionTrial Planning

Sequencing &Spacing

ResourceAllocation

SurfaceMovement

Arrival / DepartureRouting,

new TERPS

Inner Phase:200-100 Miles

CollaborativeRouting

Cockpit situational awareness/advanced Navigation

Uniform National Ultra-High Altitude Service

DepartureRunway

BalancingArrival

Runway Balancing

Improve Surface Ops

ExtendVisual OpsImprove Access

to flight & traffic info

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 toen 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 otherinefficiencies (e.g., en route congestion, severe weather)• Improved information availability and flow









10


System-Wide Needs & Solutions • Need: Improved information availability and flow

• 03-05 Recommendation: Continue to expand CDMfor all NAS users and FAA (ATCSCC and fieldfacilities) 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 (cont’d) • Need: System-wide problem prediction and equitable

resource allocationaAccurate airspace density prediction

aCollaborative routing solutions to address specific sectors inspecific areas

a Impact assessment of proposed solutions, including airspacereallocation

• Equitable allocation of limited resources to balance demanddensity across NAS

• 03-05 Recommendation:• Collaborative RoutingCoordination Tools (CRCT)

• Priority R&D:• Provide initial equitable allocationof limited resources

12


System-Wide Needs & Solutions (cont’d)Collaborative Routing Coordination Tools (CRCT)

Note: This graphic may not print correctly. Please see the numbers for priorities or refer tothe screen view.

��

��

��

��

��

��

��

��

��

ZSESeattle

ZLC Salt Lake

ZMP Minneapolis

ZOA Oakland

ZLA Los Angeles

ZABAlbuquerque

ZFW Fort Worth

ZAU Chicago

ZOB Cleveland

ZTL Atlanta

ZJX Jacksonville

ZDC Washington

ZBWBoston

ZNY New York

ZMA Miami

ZHU Houston

ZKC Kansas City

ZME Memphis

ZID Indianapolis

ZDV Denver

ATCSCC1st Priority

1st Priority

2nd Priority

1

2

11

1

1

1

1

1

1 1

1

1

1

1

12

2

2

2

2

2

13


System-Wide Needs & Solutions (cont’d)

• 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 (cont’d)URET CCLD Expansion


ZSE Seattle

ZLC Salt Lake

ZMPMinneapolis

ZOA Oakland

ZLA Los Angeles

ZDV Denver

ZAB Albuquerque ZFW

Fort Worth

ZAU Chicago

ZOB Cleveland

ZTL Atlanta

ZJX Jacksonville

ZDC Washington

ZBW Boston

ZNY New York

ZMA Miami

ZHU Houston

ZKC Kansas City

ZME Memphis

ZID Indianapolis FFP1 Sites

1st Priority

2nd Priority

1

2

1

1

1

1

1

1

1

1

1

2

2

2

2

15


System-Wide Needs & Solutions (cont’d)

• Need: Efficient aircraft movement thru en route airspace• Achieve uniform service across the NAS supporting Free Flight

• 03-05 Recommendation: National Ultra-High AltitudeService• 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 (cont’d)• 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 TerminalAirspace• 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/RNPcapability 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 (concl’d)• 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

U.S. Oceanic Airspace

18



*

System-wide problems resulting in delays and otherinefficiencies (e.g., en route congestion, severe weather)• Improved information availability and flow









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 ofSingle Center Traffic ManagementAdvisor (TMA)• Single center/1 major airport

(FFP1 TMA-SC)

• Priority R&D: TMA-MC• Multiple centers/1 major airport

• Multiple centers/>1 major airport

JFK

LGA

EWR

TEB

ZDC

ZOBZNY

x

x

PHLx

DCA

IAD

BWI

20


Transition Needs & SolutionsTMA Expansion

•Deploy SC-TMA•Research McTMA to improve arrival efficiency to NY area (including PHL)•Use results of McTMA research in 03-05 for NY/PHL area as proven successful•When TMA MC is available, all sites should be upgraded to TMA MC


��

��

��

��

��

��

ZSE

ZLC

ZMP

ZOA

ZLA

ZABZFW

ZAU ZOB

ZTL

ZJX

ZDC

ZBW

ZNY

ZMA ZHU

ZKC

ZME

ZID

ZDV

FFP1 Sites

1st Priority

2nd Priority

3rd Priority

Potomac

N90

PHL

BOS

CLT

CVG

DTW

IAH

MEM

SDF

LAS

MCO

ORD

PHX

PIT

SEA

SLC

STL

LAX

SFODEN

MSP

DFW

ATL

1

2

3

1

1

1

1

2

22

2

2

23

3

3

21


Transition Needs & Solutions (concl’d)

• Need: Efficient departure integration into and acrossen route streams

• 03-05 Recommendation:Priority R&D:• Departure integration into and across en route streams

22



*










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 activitiesaddressed in other forums that can help address this need

24


Arrival/Departure Needs & SolutionspFAST

MSP

STL

ATL

DFW

LAX

��

CLT

CVG

IAH

LASSFOPHL

LGA

JFK

EWR

TEB

N90

BWI

DCA

IAD

POTOMAC

FFP1 Sites

1st Priority

2nd Priority

3rd Priority

ORDDTW

NOCAL

1

2

3

1

1

1

1

1

1

1

22

2

3

BOS 3

Note: pFAST at SFO should be modified to create spaces inarrival traffic to accommodate departures

When active FAST becomes available, the pFAST sitesshould be upgraded to aFAST

Note: This graphic may not print correctly. Please see the numbers forpriorities or refer to the screen view.

25


Arrival/Departure Needs & Solutions (concl’d)

• 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 R&D• Arrival and departure wake vortex detection

• Departure management in TRACON airspace

26



*










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/UserCollaboration to implement User Initiatives

• Priority R&D:• Conduct research in parallel with ongoing user initiatives

28


Implementation Definition

• Implementation of capabilities means delivery of servicesand benefits with the appropriate changes in airspacedesign, procedures, systems, logistics, labor negotiations,certification, etc.

29


Technology & Implementation Readiness

6

5

4

3

2

1

9

8

7

6

5

4

3

2

1TRL

Operate Implementation Capability

Qualify Implementation Capability

Develop Implementation Capability

Define Requirements & Transfer Technology

Develop Specific Operational/MaintenancePlans & Procedures

Conduct Functional Demonstrations &Operational Evaluations

Define Concept of Use within TargetOperational Environment

Define Target Timeframe, Infrastructure,and Operational Environment

Describe Proposed Capability

FAA Investment Decision

IRL

Actual System Proven In Operation

Actual System Qualified by Demonstration

System Prototype Demonstration in an Operational Environment

System/Subsystem Model or Prototype Demonstration in a Relevant Environment

Component and/or Breadboard Validation in a Relevant Environment

Component and/or Breadboard Validationin Laboratory Environment

Analytical & Experimental CriticalFunction - Characteristic Proof-of-Concept

Technology Concept and/or Application Formulated

Basic Principles Observed and Reported

R&D Program Goal

30


Barriers to Implementation

• HW/SW for capabilities that have been identifiedcan be available in 03-05, however the followingmust also, at a minimum, be addressed in orderto realize benefits in 03-05:• Airspace design

• Environmental impact

• Labor negotiations

• Procedures

• Training

• Certification

• Spectrum

• Bandwidth (deployment and information)

31


Priority R&D

• Additional R&D activities have been identified asaddressing priority needs and should bemerged/accelerated to facilitate development of thebest 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 R&D include:• Evolutionary progression toward distributed decision

making• Increased collaboration among users and service providers• Wake vortex sensing and prediction

32


AcronymsaFAST Active Final Approach Spacing ToolADS-B Automatic Dependent Surveillance - BroadcastATM Air Traffic ManagementC/AFT CNS/ATM Focus TeamCAP Collaborative Arrival PlannerC/B Cost BenefitCDM Collaborative Decision MakingCDTI Cockpit Display of Traffic InformationCNS Communications, Navigation, and SurveillanceCPDLC Controller-Pilot Datalink CommunicationCRCT Collaborative Routing and Coordination ToolsE/DA En Route/Descent AdvisorEDP Expedite Departure PathFFP1 Free Flight Phase OneMNS Mission Need StatementPARR Problem Analysis, Resolution and RankingpFAST Passive Final Approach Spacing ToolRVSM Reduced Vertical Separation MinimaSF 21 Safe Flight 21SG Sub-GroupSMA Surface Management AdvisorSMS Surface Management SystemSWG Surveillance Working GroupTMA-MC Multi Center TMA (McTMA)TMA-SC Single Center Traffic Management AdvisorURET User Request Evaluation Tool

Documents

2003 - 2005 Capabilities Working Group Report to the ... · Problem Priorities/Needs System-wide problems resulting in delays and other* inefficiencies (e.g., en route congestion,