Trajectory Operations

and Data Communications 

Presented by Steve Bradford
FAA “Master Plan” Development Process

2

Mid-Term Conops

Concept SHALLS

Operational Improvements

AAL218

160C

115 410

TWA320

160C

165 420

EA/NSIP

Roles & Responsibilities

Procedures

Workstation

LAN

Wx - Proc /

Display

Processor

Systems

Desired Benefits

2015

Delivered Benefits

Operational Increments

RNAV
Activity: Deployment Development Research & Concepts

Implementation 

Timeframe: Near-term

Mid-term

(3 – 10 year outlook)

Far-term

(10+ year outlook)

The implementation timeframe for new NAS services and Infrastructure 

are dictated by the nature of current and future activities 

OI1

OI2 NAS EA Service

Roadmaps

NAS EA 

Infrastructure 

Roadmaps

IOC Investment Analysis System 1

Investment Analysis System 2

FAA NextGen Planning:

Implementation Timeframes

Support Activity:

Concept Development
NSIP: NAS Enterprise Architecture Integration

• Objective: Integrate Portfolios, 

Increments and their relationships 

with the NAS EA, creating a 

consistent view for all stakeholders on 

NextGen plans and implementations

• Benefits: Common data source now 

used between EA and NSIP (reduces 

number of data calls and improves 

quality assurance); increased 

corporate access to information, i.e., 

Portfolio details, OI and increment 

timelines, etc.

• Detailed information on NSIP 2015 is 

available on the NAS EA Portal: 

https://nasea.faa.gov

4
NSIP: Content Overview

5

Success Criteria

NAS EA Service Roadmaps:

Operational Improvements

NSIP 2015: 122 Alpha and Bravo Increments

NSIP Operational Increments

System Dependencies

Benefits
Implementing Capabilities to realize TBO vision

Infrastructure Element Rationale

CATM WP5 • CTOP and use of Trajectory Option Set (TOS) for airborne flights

• Strategic Flow Management Application

• UFPF

TBFM WP4 • Enhanced Adjacent Center Metering

• Path Stretch

• Advanced Interval Management (A-IM) 

• Enhanced Arrival-Departure Scheduling

TBFM WP5 • TBFM scheduler to utilize precise trajectory information that is downlinked via EPP to develop more 

stable and feasible schedules.

Data Comm S1P2 • Full En Route Data Comm services 

TFDM Future • Provide access to surface/arrival data for FF-ICE

ERAM Future Work Package • Allocation of functions between ERAM and FOXS

• Approval of User Requests/Conflict Resolution Advisories

• Vertical Conformance Verification 

• FMS Offset (closed trajectory)

ATOP WP2 • Allocation of function to support “User Trajectory Planning” between ATOP and TFMS/CATM

• New DSTs to support TBO

• Accommodation of B2 Final

SWIM Segment 3 • Airborne access to SWIM to facilitate exchange of flight information 

Surface Traffic Management • Airport Configuration Planning

• Surface Scheduling Improvements

• Surface Capabilities including Taxi Routing and Surface Conformance

• Ground-Based support for flight deck Surface Trajectory Based Operations (STBO)

AIMM Segment 3 • Integration of SAA and Digital NOTAMs with NAS automation systems and Digitized static airspace 

constraint information in LOAs/SOPs 

NAS EA Investment

NSIP Increment
Implementing Capabilities to realize TBO vision

NAS EA Service Roadmaps:

Operational Improvements

• Prototype CHI for En Route Services

• Develop end-to-end operational scenarios and 

trials for testing

• Conduct system performance and loading 

analysis

• a

Support Activity Analyses

NSIP Operational Increments

NAS EA Infrastructure Roadmaps/NSIP

System Dependencies

DP 985 (2015, Q4): Final Investment 

Decision (FID) for Data Communications 

Segment 1 Phase 2 En Route Services Full
Transformation of Methods 

Procedural Based Control:

Control on Where We Think the 

Aircraft Is

• Landmark Navigation

• Radio Beacons

• Position Reports

Surveillance Based Control: 

Control on Where We Know the 

Aircraft Is

• VOR/DME

• RADAR

Trajectory Based Control: 

Control on Where We* Know 

the Aircraft Will Be

• RNP

• ADS-B

• DataComm

* Shared Trajectory

10
11
Information requirements in support of TBO

• Information exchange

 Shared Environment (AIM, WX, Constraints)

 Shared Trajectory (synchronized 

representations)

 Shared Adjustments
Required for Data Distribution

• Network 

 Cross-boundary coordination/distribution

• Information Protocols for

 Publish/subscribe

 Command and control – logon/address

• Connectivity 

 Ground-ground 

 Air-ground link(s)

• Messaging

 Datacomm 

 AAtS
Communication of Data is Multi-Layer

• Harmonization efforts 

 Messages

• SC214/WG78, FIXM

 Pipelines

• VDL-2, L-Band, Aeromacs, Satcomm, 

 Protocols

• ATN evolution

 Network 
Air Transportation – Coordination Today

Manage interactions through coordination between participants

Voice coordination 

and control

ATFM Automation

FOC 

Automation

FD 

Automation

ATC 

Automation

Flight Data Exchange across support automation

Limited In-Flight 

Coordination

Automation not 

Informed

High 

Uncertainty

Disparate 

Plans in 

Automation

Imprecise 

Execution

Imprecise 

execution

Plan not 

followed

Multiples Participants Control a Flight 

All Affect the Trajectory

Transform to Trajectory-Based: DecisionMaking, Control and Coordination
TBO Transformations

ATFM Automation

FOC 

Automation

FD 

Automation

ATC 

Automation

Transform Control Methods

Improved Control 

Precision Closed Trajectory Accurate Execution

Transform Control Tasks

Automation 

Informed

Transform Information

Trajectory 

Constraints

Negotiated 

Trajectory

Shared plans, consistent 

trajectories
Thank You