1. Trajectory Working Session Defining Data Elements Definitions September 17, 2013 Bob Humbertson, Booz Allen Hamilton Dawn McConkey, DigitaliBiz

2. Note from FIXM Office The attached file (copied below) contains the proposed milestones for the FIXM v3.0 development. Item #6 pertains to the data elements that we are looking to receive from your team, and item #14 indicates our initial proposal to begin our weekly Technical Review Meetings (TRMs) regarding the 4DT data elements from your team. However, upon further internal discussion, we’d like to begin these TRMs on 1 OCT. Would it be possible for your team to have all of your data elements (with definitions and other characteristics) uploaded to our FIXM collaboration tool NLT 30 SEP? If you’ll need more time to do so I think that would be OK. However, we’d still want to get the discussions going with the FIXM stakeholders. 2

3. Draft FIXM v3.0 Schedule 3 ActivityMilestoneNotesLead Actionee Conduct v3.0 kickoff8/29/2013 FAA Propose Draft v3.0 Development Schedule9/12/2013 BAH Complete Initial List of v2.0 Lessons Learned9/19/2013 BAH Complete Initial Triage of Remaining v2.0 DEs9/20/2013 Stakeholders Release Draft v2.1 to Internal Stakeholders for Review and Comment 10/4/2013 EU Submit Initial Scope of 4DT DEs10/11/2013 Would like 9/30/134DT Group Define Draft v3.0 Development Process10/15/2013 BAH, EU Propose Draft v3.0 Development Process for Internal Review and Comment 10/18/2013 To be discussed at the 10/24/13 International TIM BAH Define Final v3.0 Development Process10/31/2013 BAH Define Final v3.0 Schedule10/31/2013 BAH Define Scope for the Three Iterations10/31/2013 CCB Complete Final v2.1 for Internal Release10/31/2013 EU Refine Iteration 1 Scope11/8/2013 Stakeholders Conduct TRMs for Iteration 1 Development11/12/2013 BAH Complete Iteration 1 Development12/20/2013 Stakeholders Complete Iteration 1 Internal Review, Comment, and Update 1/10/2014 Digest iteration 1 comments, sync FIXM elements (CM, LM, DD), etc. Stakeholders Refine Iteration 2 Scope1/17/2014 Stakeholders Conduct TRMs for Iteration 2 Development1/21/2014 BAH Complete Iteration 2 Development2/21/2014 Stakeholders Complete Iteration 2 Internal Review, Comment, and Update 2/28/2014Digest iteration 2 comments, sync FIXM elements (CM, LM, DD), etc. Stakeholders

4. Draft FIXM v3.0 Schedule (2) 21Host FIXM Developer Virtual Conference3/5/2014 Meeting to obtain comments from greater aviation community. Take advantage of initial mini-global test in Feb, and completion of Iteration 1 (4DT) FAA 22Refine Iteration 3 Scope3/7/2014 Stakeholders 23Conduct TRMs for Iteration 3 Development3/11/2014 BAH 24Complete Iteration 3 Development4/11/2014 Stakeholders 25 Complete Iteration 3 Internal Review, Comment, and Update 4/18/2014 Digest iteration 3 comments, sync FIXM elements (CM, LM, DD), etc. Stakeholders 26Complete Comprehensive Review, Comment and Update5/9/2014 Final look by stakeholders of all FIXM artifacts Stakeholders 27 FIXM v3.0 DD candidate updated per stakeholder feedback & released to CCB 5/23/2014 BAH 28CCB review feedback due6/6/2014 CCB 29 FIXM v3.0 DD candidate updated per CCB feedback and published as final candidate 6/13/2014 BAH 30Publish FIXM v3.0 final candidate model & schema7/4/2014 Additional week added (versus v2.0) MIT-LL 31Freeze v3.0 Model & Schema7/25/2014Same time intervals as v2.0MIT-LL 32Complete v3.0 Final Package internal QA8/1/2014BAH 33Deliver final package8/15/2014BAH 34Complete ATIEC Booth Manning Schedule8/15/2014TASC 35Complete FIXM ATIEC Docs8/15/2014Stakeholders 36Participate in ATIEC 2014 8/26/2014 - 8/28/2014 Stakeholders 37Conduct FIXM v4.0 Kickoff8/29/2014FAA 4

5. 4D Point Identifies the location and time of a trajectory point 5

6. 4D Trajectory Point A container for information pertinent to single point in a trajectory. 6

7. Airspeed The airspeed of the flight at the 4D Point expressed as either True, Indicated or Mach airspeed. 7

8. Barometric Setting Indicates if the altitude is expressed as geometric or barometric. If barometric, the assumed barometer setting for the 4DT is indicated. 8

9. Point Range Provides a vertical, lateral or temporal range to a 4D Point when clearances are provided in the form of: block altitude clearances, offsets for deviations due to weather or assigned speed 9

10. Prediction Source Identifies the source parameters of the predicted point. 10

11. Reference Point For 4D Points that are associated with a waypoint on the expanded route, the reference point provides the expanded route waypoint enabling the 4DT to be linked with the route information. 11

12. Wind In predicted trajectory, the instantaneous wind vector used at the 4D Point for creating the 4D Trajectory 12

13. TCP Type Identifies the type(s) of trajectory change point (TCP) being described by the associated 4D Point. 13