CAASD Logo
About CAASD Our Work News and Events Library Documents

MITRE/CAASD

 


Flight Object Concept
 

View by Capability > FFP2 > Information Elements > Information Sharing

Contents:

Common Elements

Common Elements

    * All capabilities accessing the flight object will have read-only access to aircraft identifier, aircraft type, equipment in use, unique equipment-specific data link address, computer identifier, and transponder code.
    * * Flight object work in progress.

Capability provides one or more shared information elements to flight object -> Capability uses one or more information elements from flight object

This diagram lists the information elements that are common to more than one capability in the middle of the chart:

  • Candidates for information sharing among the FFP1 capabilities (see associated issue)
  • Not expected that sharing will be implemented until the beyond FFP2 time frame

Capabilities are listed around the edge by their appropriate domains.

Definitions

ADS-A
Automatic Dependent Surveillance - Addressable
AOC
Aeronautical Operations Control (Airline)
CDM
Collaborative Decision Making
CPDLC
Controller Pilot Data Link Communications
CRCT
Collaborative Routing Coordination Tools
FFP1
Free Flight Phase 1
FFP2
Free Flight Phase 2
FSM
Flight Schedule Monitor
HAS
High Altitude Service
pFAST
Passive Final Approach Tool
TMA
Traffic Management Advisor
TFM
Traffic Flow Management
URET
User Request Evaluation Tool
SMA
Surface Movement Advisor
TFM
Traffic Flow Management
TMC
Traffic Management Coordinator
TOA
Time of Arrival
Back to Top

List of common information elements, alphabetically by name

The tables below list all of the information elements common to more than one capability in the FFP1 time frame. For each information element, the table shows which capabilities use or provide that element. All capabilities accessing the flight object will have read-only access to aircraft identifier, aircraft type, equipment in use, unique data link address, and computer identifier.

Caveats

  • Information elements are candidates for information to be shared by the capabilities planned for the FFP1 time frame
  • Information elements actually implemented as part of the flight object in this time frame are yet to be determined (see related issues)
  • Control-related information will only be available to ATM service providers and their capabilities
  • Flight object work is still in progress for the data link capabilities

Candidate Information Element
for the FFP2 Time Frame
FFP2 Capability
Provides
Uses
Aircraft identifier CDM-CRCT  
Uses
  CDM-FSM  
Uses
  Data Link-CPDLC  
Uses
  Enhanced Oceanic Capabilities  
Uses
  HAS  
Uses
  pFAST  
Uses
  SMA  
Uses
  TMA  
Uses
  URET  
Uses
Aircraft type CDM-CRCT  
Uses
  CDM-FSM  
Uses
  Enhanced Oceanic Capabilities  
Uses
  HAS  
Uses
  pFAST  
Uses
  SMA  
Uses
  TMA  
Uses
  URET  
Uses
Airport, destination CDM-FSM  
Uses
  HAS  
Uses
  pFAST  
Uses
  SMA  
Uses
  TMA  
Uses
  URET  
Uses
Airport, origin CDM-FSM  
Uses
  HAS  
Uses
  SMA  
Uses
  URET  
Uses
Altitude CDM-CRCT  
Uses
  Enhanced Oceanic Capabilities
Provides
Uses
  HAS
Provides
Uses
  TMA  
Uses
  URET  
Uses
Altitude, filed cruise CDM-CRCT  
Uses
  HAS  
Uses
  URET  
Uses
Altitude, reported HAS
Provides
Uses
  pFAST  
Uses
  SMA  
Uses
  TMA  
Uses
  URET  
Uses
Computer identifier Data Link-CPDLC  
Uses
  Enhanced Oceanic Capabilities
Provides
Uses
  HAS
Provides
Uses
  TMA  
Uses
  URET  
Uses
Coordination estimates Enhanced Oceanic Capabilities
Provides
Uses
  URET  
Uses
Data link address, unique equipment-specific Data Link-CPDLC  
Uses
  Enhanced Oceanic Capabilities  
Uses
Data link messages (coordination, clearances) Data Link-CPDLC
Provides
 
  Enhanced Oceanic Capabilities
Provides
 
Data link messages (position, wind, weather) Data Link-CPDLC
Provides
 
  Enhanced Oceanic Capabilities
Provides
 
Delay needed pFAST
Provides
 
  TMA
Provides
 
Departure time, actual CDM-CRCT  
Uses
  CDM-FSM  
Uses
Departure time, proposed SMA  
Uses
  TMA  
Uses
Departure time, scheduled CDM-CRCT  
Uses
  CDM-FSM
Provides
Uses
  HAS  
Uses
  URET  
Uses
Equipment in use Data Link-CPDLC  
Uses
  Enhanced Oceanic Capabilities  
Uses
Position, reported Data Link-ADS-A  
Uses
  Enhanced Oceanic Capabilities  
Uses
Problems, predicted Enhanced Oceanic Capabilities
Provides
 
  URET
Provides
 

On to remaining elements
Back to Top

Candidate Information Element
for the FFP2 Time Frame
FFP2 Capability
Provides
Uses
Radar track position HAS
Provides
Uses
  pFAST  
Uses
  SMA  
Uses
  TMA  
Uses
  URET  
Uses
Required frequency and type of ADS-A reports Data Link-ADS-A
Provides
 
  Enhanced Oceanic Capabilities
Provides
 
Route CDM-CRCT  
Uses
  Enhanced Oceanic Capabilities
Provides
Uses
  HAS
Provides
Uses
  TMA  
Uses
  URET  
Uses
Route, filed CDM-CRCT  
Uses
  HAS  
Uses
  URET  
Uses
Runway, landing pFAST
Provides
 
  SMA
Provides
 
Sector, controlling Enhanced Oceanic Capabilities  
Uses
  HAS
Provides
Uses
  URET  
Uses
Sector, receiving Enhanced Oceanic Capabilities  
Uses
  HAS
Provides
Uses
  URET  
Uses
Speed CDM-CRCT  
Uses
  Enhanced Oceanic Capabilities
Provides
Uses
  HAS
Provides
Uses
  TMA  
Uses
  URET  
Uses
Speed and direction, calculated HAS
Provides
Uses
  pFAST  
Uses
  SMA  
Uses
  TMA  
Uses
  URET  
Uses
Speed, filed cruise CDM-CRCT  
Uses
  HAS  
Uses
  URET  
Uses
TFM reroute, proposed CDM-CRCT
Provides
 
  URET  
Uses
Time at downstream fixes, estimated HAS
Provides
 
  URET
Provides
 
Time at fix, TMA-scheduled TMA
Provides
 
  URET  
Uses
TOA at runway, estimated pFAST
Provides
 
  SMA
Provides
 
Transponder code Data Link-CPDLC  
Uses
  HAS
Provides
 
Trial plans Enhanced Oceanic Capabilities
Provides
 

Top of Page

Key Operational Needs for Sharing Flight Object Information

  • Improved flight information sharing and update, reflecting flight intent and user preferences
  • Increased availability of recorded history information for post analysis processing

Top of Page

Opportunities to Share Information

  • URET, TMA, and enhanced oceanic capabilities can share predicted boundary crossing information
    • URET could use scheduled meter fix time from TMA as a constraint, showing the controller a predicted problem if meter fix time won't be met
    • URET and enhanced oceanic capabilities could use each other's estimated coordination times to better model flight's transition between oceanic and en route airspace
  • Traffic Flow Management can send reroutes developed using CRCT to sectors for problem checking (by enhanced URET) and implementation
  • SMA can use pFAST predictions for more accurate processing
    • Landing runway
    • Time of touchdown on runway

Top of Page

Additional Desired Information Elements

  • More accurate actual departure times (URET, TMA, Oceanic)
  • User-provided flight characteristics for climbs and descents (URET, TMA, pFAST, Oceanic)
  • Flight intent and user preferences
  • RNAV route (more detail from air traffic control)
  • What user would do if not cleared otherwise
  • What user would prefer to do to avoid a known problem

Top of Page

Site Links

Go to Baseline

Go to Free Flight Phase 1 (FFP1)

Go to Free Flight Phase 2 (FFP2)

Go to Beyond FFP2

top of page