Federal Aviation Administration AP23 : a snapshot on Package2 ASAS-TN2 Seminar 14 April Paris By Dragos Tonea, Eurocontrol Roberta Massiah, FAA

2 Federal Aviation Administration Introduction Overview AP23 ASAS Package2 Way forward AP23 interaction with implementation

3 Federal Aviation Administration AP23 Overview  Joint FAA/Eurocontrol activity focusing on long term ADS-B and airborne separation assurance system (ASAS) applications (NASA is also actively involved in this effort)  Aims to use NextGen and Single European Sky ATM Research (SESAR) visions as framework for ConOps  Terms of Reference and first work plan were signed in 2007  Six working meetings to date  December 2007 : first public release of AP23 draft documents (FAA- EUROCONTROL steering committee for R&D- CCOM)

4 Federal Aviation Administration AP23 Overview: Deliverables  D1 – General data exchange  D2 – Methodology to prioritize applications for AP23  D3 – Concept of Use for Airborne Separation Assistance System (ASAS)  D4 – Draft proposal for a second set of ADS-B/ASAS applications (“Package 2”)  D5 - Draft White Paper on Issues Surrounding Airborne Separation

5 Federal Aviation Administration Package 2’s Relationship to Other Implementation Activities  EUROCONTROL’s CASCADE & FAA’s SBS Programmes  Development of Package 2 is related to multiple other FAA Surveillance & Broadcast Services (SBS) program activities  Application Integrated Work Plan (AIWP) – Timeline of SBS applications and enablers from present through 2025; guidance provided by AIWP Steering Committee  “Develop and guide implementation of a cohesive evolution plan, including considerations of avionics/ground infrastructure, applications, airspace controller/pilot procedures, and international harmonization, to bring operational benefit to users and enable the NextGen vision”  RTCA  Requirements Focus Group – Development of Package 1 & 1.5 requirements  Working Group 1 – Development of requirements for applications outside the scope of Package 1  ASAS Forum – ASAS research activities shared in a “TN-like” conference series

Federal Aviation Administration

7 Federal Aviation Administration ASAS Package2: Approach  Principles:  Airborne centric  Ask for contributions from ASAS community  Use SESAR/NextGen visions as framework  Be transparent and provide feedback to contributors in early stages of development  Key points  Feedback to contributors  Seek consultation on proposed method  Clearly identify scope of Package2 –done ( ASAS for transfer of separation, SESAR ATM capability 4&5)

8 Federal Aviation Administration ASAS Package2 Application Proposal Submission  AP23 elicited submissions for proposed applications from the aviation community via a web-based template (~10,000 addresses)  AP23 Application template v doc  Received back ~100 proposed applications  Not all unique  Varying degrees of completeness w.r.t. the template

9 Federal Aviation Administration Submitted Application Surface Separation Surface Alerting ASAS Package2 Application Proposal Submission Self Separation ASEP Others Trajectory Intrusion & Blunder Protection Trajectory Crossing and Passing Trajectory Merge, Follow and Interval Management Submitted Application

10 Federal Aviation Administration Surface Alerting Application Processing: Group& Identify commonalities Self Separation ASEP Others Trajectory Intrusion & Blunder Protection Trajectory Crossing and Passing Trajectory Merge, Follow and Interval Management Surface Separation

11 Federal Aviation Administration Traffic Data Functions Separation Assurance Functions Conflict Resolution Functions ASEP C&P in continental airspace Application

12 Federal Aviation Administration Application Processing  In order to reconcile the multitude of proposed applications, AP23 is currently in the process of a functional analysis  Created  Application Elements: a basic ASAS-enabled capability of an ASAS aircraft. Applications are an integration of one or more application elements and applied to a specified environment with appropriate procedures.  ASAS functions: the processes, calculations, and monitoring tasks that must be supplied by the ASAS avionics system to enable the application element. Application = Application Element + Applicable Domain + Applicable Conditions (e.g., maneuvering constraints, separation responsibility)

13 Federal Aviation Administration Current Application Elements Achieve Relative Position 1.Target-Point Merging 2.Target-Track Merging 3.Dynamic Path Merging 4.Pairwise Interval Achievement Maintain Relative Position 5.Pairwise Interval Maintenance 6.Track Following 7.Dynamic Path Following Maximize Use of Desired Trajectory (Airborne Separation) 8.Vertical Passing or Crossing 9.Lateral Passing or Crossing 10.Delegated Encounter Management 11.User Requested Maneuver Maximize Use of Desired Trajectory (Self Separation) 12.Conflict Detection 13.Conflict Resolution 14.Maneuvering Without Conflict Enable Applications 15.Identifying Designated Aircraft 16.Transferring Separation Responsibility

14 Federal Aviation Administration Current ASAS Functions (slide 1 of 2) Traffic Data Functions – those that assist in providing the necessary level of awareness of other aircraft involved in the application.  Identify reference aircraft  Track reference aircraft  Provide reference aircraft’s trajectory Merge Functions – those that provide the assistance necessary for planning the maneuvers to position the ASAS aircraft into a following position relative to a reference aircraft.  Compute maneuvers to  Compute merge location Follow Functions – those that provide the information necessary to define the maneuvers for following in sequence behind a reference aircraft.  Compute dependent following trajectory Manage Interval Functions – those that provide the safe achievement or maintenance of a desired interval between aircraft.  Compute speeds to achieve interval  Monitor interval conformance

15 Federal Aviation Administration Current ASAS Functions (slide 2 of 2) Separation Assurance Functions – those that provide the maintenance of separation from a reference aircraft during the process of applying other ASAS functions. (See the note at the end of this section regarding the distinction between Separation Assurance Functions and Conflict Detection and Conflict Resolution Functions.)  Monitor maintenance of separation  Compute guidance to maintain separation Conflict Detection Functions – those that support the determination of whether a given trajectory would likely place the aircraft in eventual separation loss with a reference aircraft.  Probe trajectory for conflicts  Conflict Alerting Conflict Resolution Functions – those that support the determination of the user-optimal flight path deviations from the desired trajectory, as well as the return maneuvers, that are necessary to ensure traffic separation.  Compute vertical maneuvers to provide separation  Compute lateral maneuvers to provide separation  Compute user-preferred trajectory to provide separation Trajectory Optimization Functions – those that support the optimal selection of trajectories, given higher-level constraints and objectives.  Compute traffic-constrained user-preferred trajectory  Compute maneuvering flexibility

16 Federal Aviation Administration Way forward  Package2 Contributors consultation started  Draft D4 sent for review and feedback to ASAS Package2 contributors  Get comments for next AP23 meeting (July, 2008)  Validate approach & start identifying lead applications to drive new avionics requirements generation  Autumn 2008 – second feedback cycle => update D4  Next AP23 release: December 2008 to FAA- EUROCONTROL steering committee for R&D CCOM

17 Federal Aviation Administration