slide1
Download
Skip this Video
Download Presentation
Trajectory Interchange Meeting Tuesday, October 9, 2012 – Thursday, October 11, 2012

Loading in 2 Seconds...

play fullscreen
1 / 7

Trajectory Interchange Meeting Tuesday, October 9, 2012 – Thursday, October 11, 2012 - PowerPoint PPT Presentation


  • 74 Views
  • Uploaded on

Trajectory Interchange Meeting Tuesday, October 9, 2012 – Thursday, October 11, 2012 Summary and Action Items. PURPOSE.

loader
I am the owner, or an agent authorized to act on behalf of the owner, of the copyrighted work described.
capcha
Download Presentation

PowerPoint Slideshow about ' Trajectory Interchange Meeting Tuesday, October 9, 2012 – Thursday, October 11, 2012' - kaseem-dalton


An Image/Link below is provided (as is) to download presentation

Download Policy: Content on the Website is provided to you AS IS for your information and personal use and may not be sold / licensed / shared on other websites without getting consent from its author.While downloading, if for some reason you are not able to download a presentation, the publisher may have deleted the file from their server.


- - - - - - - - - - - - - - - - - - - - - - - - - - E N D - - - - - - - - - - - - - - - - - - - - - - - - - -
Presentation Transcript
slide1

Trajectory Interchange Meeting

Tuesday, October 9, 2012 – Thursday, October 11, 2012

Summary and Action Items

slide2

PURPOSE

The Technical Interchange Meeting will establish a standard for the dynamic exchange of flight information so that ATM System Usersmay be supported in their operations.

The trajectory coordination and development will support 3 overarching NextGen/SESAR Coordination Plans:

3.1 – The common trajectory definition identifying the range of users for the trajectory, which will accommodate all uncertainties and provide robustness to meet operational need.

3.2 – The FIXM/FO identified as a common or special purpose messaging resource.

3.3 – The trajectory management/harmonization process which will set the context for the trajectory definition.

meeting fixm s schedule

*FIXM 3.0, introduced in August of 2014, will include the 4D Trajectory information.

  • *An agreement on
  • Deliverable definition
  • Deliverable format
  • Scenarios to be analyzed
  • Data elements
  • is needed for the FIXM development team by August 2013 to begin working on including 4D trajectories.
Meeting FIXM’s Schedule
summary and assumptions

Need for Lexicon

    • Definition of trajectory terms
  • Concepts:
    • Regions have their own concepts and resulting information need for TBO
    • Information exchange between Operators, ATSU and DSTs
  • FIXM Data Elements
    • A FIXM 4DT Core and Extensions
    • Scenario analysis enables refinement to core
    • Items expected to be used where performance needs dictate
  • Exchange
    • Agreed to exchange cleared trajectory and alternative trajectory items to support operations
    • Agreed to exchange input data at a level mitigating interoperability concerns
    • Focus on airborne trajectory (describing path in the air, may be described pre-departure)
    • No need to distinguish between aircraft or FOC as source of data
Summary and Assumptions
action items

Develop common trajectory definitions (suggest leverage AP-16)

  • Individual Regions investigate their own TBO Concepts for trajectory information items supporting their concepts
  • Joint development of inventory of common items for initial global set
  • Obtain exchange characteristics of identified scenarios and determine sufficiency
  • Analyze scenarios against the data elements identified as common among the regional concepts
  • Refine core elements
  • Identify rationale/justification for elements
  • Configuration Management of decisions and justifications
  • The FAA will elevate the need to begin the work to harmonize the trajectory management
Action Items
scenarios being considered

Nominal flight across multiple ANSPs

  • Trajectory computation through Area of Interest (including transition near a boundary)
  • Cross ANSP strategic flow including upstream constraint propagation
  • Alternative Planning such as reroutes during weather events
  • CONSIDERATIONS DURING ANALYSIS:
    • Mixed capabilities
    • Use of multiple trajectories and integration of operational data (including EPP)
    • Pre-departure trajectory creation and exchange
    • Multiple trajectory distinctions
    • Input from Trajectory Management
Scenarios being Considered
slide7

Beyond Package 1:

  • Identify performance requirements and parameters for trajectory information
  • Regional extensions such as DST to DST data exchange
  • Tabled discussion on trajectory management:
  • Tolerances/errors/operational range
  • Flight Plan Updating
ad