CARE/ASAS/Activity 2: Validation Framework WP 1 ...

CARE/ASAS/VF-ISD-WP1-D2 ASAS in CARE

CARE-ASAS Activity 2: VF Project-WP1-D2 ASAS Scenario Repository – Version 1.0 – 08 August 2002 Isdefe ISCARE-021222-1L

CARE/ASAS Action

CARE/ASAS/Activity 2: Validation Framework

WP 1 Deliverable 2

ASAS SCENARIO REPOSITORY

Eurocontrol Reference: CARE/ASAS/Isdefe/ 02-031


CARE/ASAS Activity 2: VF Project-WP1- D2 ASAS Scenario Repository – Version 1.0 – 08 August 2002 page i Isdefe ISCARE-021222-1L

This page intentionally left blank


CARE/ASAS Activity 2: VF Project-WP1- D2 ASAS Scenario Repository – Version 1.0 – 08 August 2002 page ii Isdefe ISCARE-021222-1L

DOCUMENT REVIEW

Version Date Description Modifications

0.1 25/02/02 First draft

0.2 05/04/02 Draft of WP1 Deliverable 2 All

0.3 26/04/02 Final draft of WP1 Deliverable 2 Section 4.8.2.2

Annex B, Section 12

Annex B, Section 13

1.0 08/08/02 First issue Update of VDR data

DISTRIBUTION LIST

Consortium EUROCONTROL and CARE/ASAS Action Manager

Rosalind Eveleigh NATS Mick van Gool EUROCONTROL Agency

Jose Miguel de Pablo Aena Francis Casaux EUROCONTROL Agency

John Bennett QinetiQ Ulrich Borkenhagen EUROCONTROL Agency

Juan Alberto Herreria Isdefe

Brian Hilburn NLR


CARE/ASAS Activity 2: VF Project-WP1- D2 ASAS Scenario Repository – Version 1.0 – 08 August 2002 page iii Isdefe ISCARE-021222-1L

ACRONYM LIST A/C Aircraft 4D Four Dimensions (e.g. latitude, longitude, altitude and time) AA Autonomous Aircraft ACAS Airborne Collision Avoidance System ADS-B Automatic Dependent Surveillance – Broadcast APP Approach ASAS Airborne Separation Assurance System A-SMGCS Advanced Surface Movement Guidance and Control System ATC Air Traffic Control ATFM Air Traffic Flow Management ATM Air Traffic Management CARE Co-operative Actions of Research and development in EUROCONTROL CDTI Cockpit Display of Traffic Information CNS Communication, Navigation and Surveillance CWP Controller Working Position DialTFac Dialog Test Facility EACAC Evolutionary Air-ground Co-operative ATM Concepts EATMS European Air Traffic Management System EC European Community EEC EUROCONTROL Experimental Centre EFIS Electronic Flight Instrument System EMERALD Emerging RTD Activities of Relevance for ATM Concept Definition EMERTA Emerging Technologies Opportunities, Issues and Impact on ATM ETCAS Enhanced Traffic alert and Collision Avoidance System EUROCAE European Organisation for Civil Aviation Electronics EVA Enhanced Visual Acquisition EVP EATCHIP Validation Platform E-TIBA Enhanced Traffic information Broadcast by Aircraft FAST Full Aircraft Separation Transfer FFAS Free Flight Air Space FGCS Flight Guidance Control System FIS Flight Information Service FMS Flight Management System FTS Fast Time Simulation GNSS Global Navigation Satellite System GPS Global Positioning System HMI Human Machine Interface HLO High Level Objective HUD Head Up Display ICAO International Civil Aviation Organisation ID Identification IMC Instrumental Meteorological Conditions IFR Instrument Flight Rules ILS Instrument Landing System IMC Instrument Meteorological Conditions INS Inertial Navigation System IRS Inertial Reference System MAEVA Master ATM European Validation Plan MAS Managed Air Space MASS Multi Aircraft Simplified Simulator MCDU Multifunction Control and Display Unit MCS Multi aircraft Cockpit Simulator


CARE/ASAS Activity 2: VF Project-WP1- D2 ASAS Scenario Repository – Version 1.0 – 08 August 2002 page iv Isdefe ISCARE-021222-1L

MONA Monitoring Aids NATS National Air Traffic Services NLR National Aerospace Laboratory PRM Precision Radar Monitoring RTS Real Time Simulation RNAV Area Navigation RNP Required Navigation Precision RTCA Radio Technical Commission for Aeronautics RTD Research and Technical Development RVSM Reduced Vertical Separation Minima SMGCS Surface Movement Guidance and Control System SSR Secondary Surveillance Radar TCAS Traffic alert and Collision Avoidance System TIS Traffic Information Service TIS-B Traffic Information Service Broadcast TMA Traffic Manoeuvering Area UMAS Unmanaged Air Space VF Validation Framework VDR Validation Data Repository VFR Visual Flight Rules VHF Very High Frequency WI Work Item VMC Visual Meteorological Conditions WP Work Package


CARE/ASAS Activity 2: VF Project-WP1- D2 ASAS Scenario Repository – Version 1.0 – 08 August 2002 page v Isdefe ISCARE-021222-1L

REFERENCE LIST [1] CARE-ASAS Activity 2, “Towards a validation framework for ASAS applications”,

report, Edition 1, June 2001.

[2] NATS. Technical Proposal: CARE-ASAS Activity 2 Follow-up: Validation Framework. Version 1.0, September 2001.

[3] CARE-ASAS, Principles of Operation for the Use of ASAS. Version 7.1. June 2001.

[4] CARE-ASAS Activity 1, “Problem Dimension / Evaluation of Past studies – European ASAS literature and study review, 2000.

[5] ISDEFE. CARE-ASAS Activity 2, “Template for Validation of ASAS Applications”, Version 3.2, ISCARE-021154-1L, August 2002.

[6] ISDEFE. CARE-ASAS Activity 2, “Validation of ASAS Applications Template User Guide”, Version 3.1, ISCARE-021155-1L, February 2002.

[7] ISDEFE. CARE-ASAS Activity 2, “ASAS Scenario Repository Requirements to VDR”, Version 0.4, ISCARE-021156-1L, August 2002.

[8] ISDEFE. CARE-ASAS Activity 2, “Questionnaire to Collect Data of ASAS Application Validation Exercises”, February 2002.

[9] EEC. FREER FLIGHT-EACAC Real time experiment June 99, “Controller Handbook”, May 1999.

[10] EEC. FREER FLIGHT-EACAC Real time experiment June 99, “Pilot Notes”, May1999.

[11] EEC. FREER FLIGHT, “Investigations into Limited Delegation of Separation Assurance to the Cockpit”, June 1999.

[12] EEC. FREER FLIGHT-EACAC Real time experiment June 00, “Controller Handbook”, Version 1.0, May 2000.

[13] EEC. FREER FLIGHT-EACAC Real time experiment June 00, “Pilot Notes”, June 2000.

[14] EEC. FREER FLIGHT, “Procedures of delegation from the controller to the pilot”, Version 1.1, June 2000.

[15] EEC. FREER FLIGHT-EACAC Real time experiment November 2000, “Controller Handbook”, Version 2.1, November 2000.

[16] EEC. FREER FLIGHT-EACAC Real time experiment November 2000, “MCS Pilot Notes”, Version 1.0, November 2000.

[17] EEC. FREER FLIGHT-EACAC Real time experiment November 2000, “Pilot Notes”, November 2000.


CARE/ASAS Activity 2: VF Project-WP1- D2 ASAS Scenario Repository – Version 1.0 – 08 August 2002 page vi Isdefe ISCARE-021222-1L

[18] EEC. FREER FLIGHT, “Procedures of delegation from the controller to the pilot”, Version 2.1, November 2000.

[19] EEC. FREER FLIGHT-EACAC Real time experiment November 2001, “Controller Handbook”, Version 2.0, November 2001.

[20] EEC. FREER FLIGHT-EACAC Real time experiment November 2001, “MCS Pilot Notes”, November 2001.

[21] EEC. FREER FLIGHT-EACAC Real time experiment November 2001, “Pilot Notes”, November 2001.

[22] EEC. FREER FLIGHT, “Procedures of delegation from the controller to the pilot”, Version 2.2, November 2001.

[23] EEC. Freer-3. An Experimental Airborne Separation Assurance System.

[24] EEC. FAST: 1999 Pilot in the loop evaluation, July 2000.

[25] NATS. Towards an Operational Scenario for Longitudinal station keeping: An ASAS Application, November 1998.

[26] EMERALD, “WP5 – Assessment of emerging technologies: the specific case of ADS-B/ASAS”. Version 2.0, October 1998.

[27] EMERTA, “WP 3.1: ASAS feasibility and transition issues”. Version 2.0. March 2000.

[28] CENA. Off-line simulations of the ASAS Crossing Procedure. December 1998.

[29] CENA. Operational Assessment of Co-operative ASAS Applications. Version 1.0. January 1999.

[30] CENA. A Theoretical Assessment of Sector Capacity improvement Due to ASAS Concept. Version 1.2. June 1999.

[31] NLR. Designing for Safety: the Free Flight Air Traffic Management Concept.

[32] NLR. Free Flight: How low can you go?. DASC'02 paper.


CARE/ASAS Activity 2: VF Project-WP1- D2 ASAS Scenario Repository – Version 1.0 – 08 August 2002 page vii Isdefe ISCARE-021222-1L

TABLE OF CONTENTS 1. CARE/ASAS VALIDATION FRAMEWORK WP 1 OVERVIEW.........................................1 2. WI 1.5 ASAS SCENARIO REPOSITORY OVERVIEW .....................................................1 3. DOCUMENT SCOPE ........................................................................................................1 4. ASAS APPLICATIONS VALIDATION SCENARIOS..........................................................2

4.1. Data of the EEC RTS experiment for EACAC project, June 1999...........................4

4.1.1. Station Keeping and Traffic Merging in TMA airspace ...............................4

4.1.1.1. Validation scenario general co-ordinates ...................................4 4.1.1.2. High Level Objectives and ASAS applications ...........................4 4.1.1.3. Documents developing the VF elements....................................4 4.1.1.4. Correspondent template.............................................................7

4.1.2. Lateral and Vertical Crossing and Passing in En-route airspace................7

4.1.2.1. Validation scenario general co-ordinates ...................................7 4.1.2.2. High Level Objectives and ASAS applications ...........................7 4.1.2.3. Documents developing the Scenario elements ..........................8 4.1.2.4. Correspondent template...........................................................10

4.2. Data of the EEC RTS experiment for EACAC project, June 2000.........................11

4.2.1. Station Keeping and Traffic Merging in TMA airspace .............................11

4.2.1.1. Validation scenario general co-ordinates .................................11 4.2.1.2. High Level Objectives and ASAS applications .........................11 4.2.1.3. Documents developing the Scenario elements ........................11 4.2.1.4. Correspondent template...........................................................14

4.2.2. Lateral and Vertical Crossing and Passing in En-route airspace..............14


4.3. Data of the EEC RTS experiment for EACAC project, November 2000 ................18

4.3.1. Station Keeping and Traffic Merging in TMA airspace .............................18





CARE/ASAS Activity 2: VF Project-WP1- D2 ASAS Scenario Repository – Version 1.0 – 08 August 2002 page viii Isdefe ISCARE-021222-1L

4.4. Data of the EEC RTS experiment for EACAC project, November 2001 ................26 4.4.1. Station Keeping and Traffic Merging in TMA airspace .............................26




4.5. Data of the EEC RTS experiment for FREER-3 project.........................................35

4.5.1. Autonomous Aircraft in En-route airspace ................................................35


4.6. Data of the EEC RTS experiment for FAST project ...............................................37

4.6.1. Autonomous Aircraft in En-route airspace ................................................37


4.7. Data of the NATS experiment for Longitudinal Station Keeping ............................40

4.7.1. Longitudinal Station Keeping ....................................................................40


4.8. Data of the NLR experiments for Free Flight .........................................................43

4.8.1. Basic Cruise Free Flight Scenario, NLR-NASA ASAS .............................43


4.8.2. Autonomous Aircraft in TMA.....................................................................45

4.8.2.1. Validation scenario general co-ordinates .................................45


CARE/ASAS Activity 2: VF Project-WP1- D2 ASAS Scenario Repository – Version 1.0 – 08 August 2002 page ix Isdefe ISCARE-021222-1L

4.8.2.2. High Level Objectives and ASAS applications .........................45 4.8.2.3. Documents developing the Scenario elements ........................46 4.8.2.4. Correspondent template...........................................................47

4.9. Data of the CENA experiments for ASAS ..............................................................48

4.9.1. ASAS Crossing Procedure (ACP98) project.............................................48


4.9.2. Theoretical assessment of sector capacity due to ASAS concept

(ASAS_MBB99) ........................................................................................50 4.9.2.1. Validation scenario general co-ordinates .................................50 4.9.2.2. High Level Objectives and ASAS applications .........................50 4.9.2.3. Documents developing the Scenario elements ........................50 4.9.2.4. Correspondent template...........................................................52

4.10. Data of the University of Glasgow experiments for ASAS .....................................53

4.10.1. Multi-agent optimal ASAS operations (COAST) .......................................53


4.10.2. Optimal FFA/MAS Transition Methodology Development (T_MAT) .........53


4.11. Data of the EMERALD project ...............................................................................55

4.11.1. Closely Spaced Parallel Approaches in Instrumental Meteorological

Conditions.................................................................................................55 4.11.1.1. Validation scenario general co-ordinates .................................55 4.11.1.2. High Level Objectives and ASAS applications .........................55 4.11.1.3. Documents developing the Scenario elements ........................55 4.11.1.4. Correspondent template...........................................................57

4.11.2. Longitudinal Station Keeping ....................................................................57


4.11.3. Autonomous Aircraft .................................................................................60


CARE/ASAS Activity 2: VF Project-WP1- D2 ASAS Scenario Repository – Version 1.0 – 08 August 2002 page x Isdefe ISCARE-021222-1L


4.12. Data of the EMERTA project..................................................................................64

4.12.1. Enhanced Visual Acquisition ....................................................................64


4.12.2. Station Keeping on Approach ...................................................................66


ANNEX A. REQUIREMENTS OF ASAS SCENARIO REPOSITORY TO VDR. 1. DOCUMENT SCOPE ........................................................................................................1 2. REQUIREMENTS CODIFICATION ...................................................................................1 3. ASAS REPOSITORY REQUIREMENTS TO VDR ............................................................1

3.1. General requirements ..............................................................................................1 3.2. Requirements from General Data ............................................................................3 3.3. Requirements from Operational Concept Objectives data.......................................5 3.4. Requirements from ASAS Application data .............................................................8 3.5. Requirements from the Template data ..................................................................11 3.6. Requirements from the Detailed Documents data .................................................11

ANNEX B. TEMPLATE FOR THE VALIDATION OF ASAS APPLICATIONS. 1. “EACAC_99_STATION_KEEPING”. EACAC 1999 REAL-TIME SIMULATION.

STATION KEEPING AND TRAFFIC MERGING IN TMA AIRSPACE...............................1 2. “EACAC_99_CROSSING_LAT_VERT”. EACAC 1999 REAL-TIME SIMULATION.

LATERAL AND VERTICAL CROSSING AND PASSING IN EN-ROUTE AIRSPACE ......2 3. “EACAC_JUN_00_STATION_KEEPING”. EACAC JUNE 2000 REAL-TIME

SIMULATION. STATION KEEPING AND TRAFFIC MERGING IN TMA AIRSPACE .......3 4. “EACAC_JUN_00_CROSSING_LAT_VERT”. EACAC JUNE 2000 REAL-TIME

SIMULATION. LATERAL AND VERTICAL CROSSING AND PASSING IN EN-ROUTE AIRSPACE ...........................................................................................................4

5. “EACAC_NOV_00_STATION_KEEPING”. EACAC NOVEMBER 2000 REAL-TIME SIMULATION. STATION KEEPING AND TRAFFIC MERGING IN TMA AIRSPACE .......5

6. “EACAC_NOV_00_CROSSING_LAT_VERT”. EACAC NOVEMBER 2000 REAL-TIME SIMULATION. LATERAL AND VERTICAL CROSSING AND PASSING IN EN-ROUTE AIRSPACE.....................................................................................................6

7. “EACAC_01_STATION_KEEPING”. EACAC 2001 REAL-TIME SIMULATION. STATION KEEPING AND TRAFFIC MERGING IN TMA AIRSPACE...............................7

8. “EACAC_01_CROSSING_LAT_VERT”. EACAC 2001 REAL-TIME SIMULATION. LATERAL AND VERTICAL CROSSING AND PASSING IN EN-ROUTE AIRSPACE ......8


CARE/ASAS Activity 2: VF Project-WP1- D2 ASAS Scenario Repository – Version 1.0 – 08 August 2002 page xi Isdefe ISCARE-021222-1L

9. “FREER-3_AUTONOMOUS_AIRCRAFT”. FREER-3. AN EXPERIMENTAL AIRBORNE SEPARATION ASSURANCE SYSTEM.........................................................9

10. “FAST_AUTONOMOUS_AIRCRAFT”. FAST (FULL AIRCRAFT SEPARATION TRANSFER): 1999 PILOT IN THE LOOP EVALUATION ...............................................10

11. “NATS_LONGITUDINAL_STATION_KEEPING”. TOWARDS AN OPERATIONAL SCENARIO FOR LONGITUDINAL STATION KEEPING: AN ASAS APPLICATION .....11

12. “NLR_BASIC_CRUISE_FF”. BASIC CRUISE FREE FLIGHT SCENARIO, NLR-NASA ASAS ....................................................................................................................12

13. “NLR_AUTONOMOUS_AIRCRAFT_TMA”. AUTONOMOUS AIRCRAFT IN TMA .........13 14. “CENA_ACP98”. ASAS CROSSING PROCEDURE .......................................................14 15. “CENA_ASAS_MBB99”. THEORETICAL ASSESSMENT OF SECTOR CAPACITY

DUE TO ASAS CONCEPT ..............................................................................................15 16. “UNIV_GLASGOW_COAST”. ASAS CO-OPERATIVE AND NON CO-OPERATIVE

FFA OPERATIONS .........................................................................................................16 17. EMERALD. CLOSELY SPACED PARALLEL APPROACHES IN INSTRUMENTAL

METEOROLOGICAL CONDITIONS................................................................................17 18. EMERALD. LONGITUDINAL STATION KEEPING .........................................................18 19. EMERALD. AUTONOMOUS AIRCRAFT ........................................................................19 20. EMERTA. ENHANCED VISUAL ACQUISITION..............................................................20 21. EMERTA. STATION KEEPING ON APPROACH............................................................21


CARE/ASAS Activity 2: VF Project-WP1- D2 ASAS Scenario Repository – Version 1.0 – 80 August 2002 page 1 Isdefe ISCARE-021222-1L

1. CARE/ASAS VALIDATION FRAMEWORK WP 1 OVERVIEW Work Package 1 (WP1) of CARE-ASAS-VF study, "Identification of ASAS Operational Scenarios", has as its objective to describe operating environments for en-route and TMA operations that are relevant to ASAS applications. Drawing on work done in other CARE/ASAS activities and European projects dealing with validation or ASAS, WP1 will define scenarios for ASAS applications, including at least the applications defined in Activity 3. This work is being undertaken in six work items (WI), as follows: WI 1.1 the consolidation of a draft scenario template; WI 1.2 a review of selected previous ASAS experiment scenarios; WI 1.3 the definition of dimensions for an ASAS reference scenario; WI 1.4 the definition of the reference scenario; WI 1.5 the creation of an ASAS scenario repository; and WI 1.6 a final report summarising all of the work done in WP1. The scenarios so defined will meet the overall objective of CARE-ASAS-VF, to make recommendations for a feasible generic validation framework, and provide guidance materials and case studies for applying the framework. 2. WI 1.5 ASAS SCENARIO REPOSITORY OVERVIEW Work Item 1.5 (WI 1.5) of the CARE/ASAS/VF is a collection of representative, previous scenarios used in ASAS experiments from the organisations included in the consortium. In order to complete the repository, the Consortium will also contact other organisations involved in ASAS activities in order to ask them for their scenarios developed for ASAS experiments. A database will be created gathering the results of the application of the scenario template to the past ASAS scenarios. A repository of these scenarios will be provided in electronic format. The success of this task is critically dependent on the timely provision of suitable data. 3. DOCUMENT SCOPE This document is the Deliverable 2 of CARE/ASAS/Activity 2: Validation Framework. After general introduction sections (1, 2 and 3), in the section 4 the document collects validation scenarios previously developed and used for validation exercises of ASAS applications. These validation scenarios and their associated data have been provided by different organisations, both internal and external to the consortium: • CENA (external). • EEC (external) • Glasgow University (external). • NATS (internal). • NLR (internal). • QinetiQ (internal). The exercises validation scenarios are addressed following a common data structure: first, the general data gathered according to [8], are presented to provide the overview of the exercise; second, the associated initial validation framework and scenario template [5] will drive to the elements considered for the exercise implementation.



For complementing the deliverable, the annex A of the document addresses the requirements required by CARE/ASAS/VF activity to VDR [7] in order to implement the ASAS repository within the VDR. These requirements are only regarding the functionalities required to VDR to fill up ASAS repository needs, not being the intention of defining requirements regarding VDR access, security, maintainability, flexibility, reliability and any other VDR characteristic apart from those defining VDR functions to permit the integration of the ASAS repository within VDR. 4. ASAS APPLICATIONS VALIDATION SCENARIOS The validation scenarios collected (and included in this document) from previous validation exercises of ASAS applications and the organisations that have provided the data and associated documents are listed hereafter: CENA ASAS Crossing Procedure (ACP98) August 1998. Theoretical assessment of sector capacity due to

ASAS concept (ASAS_MBB99) June 1999. EUROCONTROL Experimental Centre FREER-EACAC June 1999. FREER-EACAC June 2000. FREER-EACAC November 2000. FREER-EACAC November 2001. FREER-3, end 1997. FREER-FAST 1999. Glasgow University Multi-agent optimal ASAS operations (COAST). Optimal FFA/MAS Transition Methodology

Development (T_MAT). NATS Longitudinal Station Keeping, November 1998. NATS, QinetiQ EMERTA, Enhanced Visual Acquisition. EMERTA, Station Keeping on Approach. NLR Basic Cruise Free Flight, NLR-NASA ASAS. Airborne Self-Separation in TMA. QinetiQ EMERALD, Longitudinal Station Keeping. EMERALD, Closely Spaced Parallel Approaches. EMERALD, Autonomous Aircraft. The data of the exercises’ validation scenario are presented in four groups: • Validation scenario general co-ordinates, addressing general data for the exercises such

as organisation, references, focal points, dates, project/study or validation methodologies.

• ASAS applications and High Level Objectives (HLO), summarising the operational

concept objectives aimed by the validation exercise and introducing the ASAS category and ASAS application validated.

• Documents developing the scenario elements, listing the associated documents that

further develop the definition of the scenario. The documents are sorted by the scenario elements.



• Correspondent template, driving to the associated initial validation framework and scenario template [5]. The template contains resumed general data and the elements included in the validation scenario are marked.

All these data are included in the EUROCONTROL’s Validation Data Repository (VDR). To access the ASAS repository within the VDR, the user must connect with the following link: https://www.eurocontrol.int/eatmp/vdr/indexvdr.html, then select “VDR Repository” and after validating the login and the password, select the role “CARE/ASAS – Concept & Scenarios”.



4.1. Data of the EEC RTS experiment for EACAC project, June 1999 On the annex B of this document are presented the templates of the scenarios included in the repository. 4.1.1. Station Keeping and Traffic Merging in TMA airspace 4.1.1.1. Validation scenario general co-ordinates Scenario Identification: “EACAC_99_Station_Keeping”. EACAC 1999 Real-time Simulation. Station Keeping and Traffic Merging in TMA airspace

Scenario version: not defined

Author: Isabelle Grimaud & Carol Sheehan

Organisation: EUROCONTROL Experimental Centre (EEC)

Creation Date: 27th May 1999

Execution Date: 31st May - 4th June 1999 and 14th – 18th June 1999

Name of the Project/Study: EACAC (Evolutionary Air-ground Co-operative ATM Concepts) study of Freer Flight project

Validation Technique: Real Time Simulation

Validation Tool: HMI simplified version of the Denmark Interface developed for the SweDen 98 real time simulation + 2 Multi Cockpit Simulator (MCS) + 2 Multi Aircraft Simplified Simulator (MASS)

4.1.1.2. High Level Objectives and ASAS applications ASAS Category: Airborne Separation ASAS Application: Station Keeping in TMA considering flight level changes High Level Objectives: Improve Safety. Increase system capacity 4.1.1.3. Documents developing the VF elements Objectives:

• FREER FLIGHT-EACAC Real time experiment June 1999. Controller Handbook. Section 2 [9]

File: “controller handbook.pdf”

• FREER FLIGHT-EACAC Real time experiment June 1999. Investigations into Limited Delegation of Separation Assurance to the Cockpit [11]



File: “eacac_training.pdf”

Airspace Restrictions: not defined

Airspace Elements:

• FREER FLIGHT-EACAC Real time experiment June 1999. Controller Handbook. Section 7 & ANNEX 1 [9]


• FREER FLIGHT-EACAC Real time experiment June 1999. Pilot Handbook. Sections 8, 9, 10 & 13 [10]

File: “Pilot handbook.pdf”

Airspace Geographical Scope:

• FREER FLIGHT-EACAC Real time experiment June 1999. Pilot Handbook. Section 6 [10]


Traffic Volume and Complexity:



Traffic-Flight Schedule: not defined

Traffic-Aircraft Performance:



New ATS Involved: not defined

New Flight Rules: not defined

Separation Rules: not defined

Aircraft Sequencing Rules: not defined

Conflict Resolution Strategy Rules: not defined

Rules for Co-ordination and Transfer Procedures:



• FREER FLIGHT-EACAC Real time experiment June 1999. Pilot Handbook Section 7.3 [10]


Rules-New Phraseology:





Tasks Description:





Roles for the Different Actors in Each Task:


File: “controller handbook.pdf“



Ground Technology:

• FREER FLIGHT-EACAC Real time experiment June 1999. Controller Handbook. Sections 4 & 6 [9]


Airborne Technology:







4.1.1.4. Correspondent template The file which is the correspondent template to this validation exercise is: “Station_Keep_EACAC-Jun-99 Template.doc”. 4.1.2. Lateral and Vertical Crossing and Passing in En-route airspace 4.1.2.1. Validation scenario general co-ordinates Scenario Identification:“EACAC_99_Crossing_Lat_Vert”. EACAC 1999 Real-time Simulation. Lateral and Vertical Crossing and Passing in En-route airspace


Author: Isabelle Grimaud & Carol Sheehan



Execution Date: 31st May - 4th June 1999 and 14th – 18th June 1999.

Name of the Project/Study:EACAC (Evolutionary Air-ground Co-operative ATM Concepts) study of Freer Flight project


Validation Tool: HMI simplified version of the Denmark Interface developed for the SweDen 98 real time simulation + 2 Multi Cockpit Simulator (MCS) + 2 Multi Aircraft Simplified Simulator (MASS)

4.1.2.2. High Level Objectives and ASAS applications ASAS Category: Airborne Separation ASAS Application: ASAS Crossing procedure in en-route airspace & Vertical Crossing High Level Objectives: Improve Safety. Increase system capacity



4.1.2.3. Documents developing the Scenario elements Objectives:



• FREER FLIGHT-EACAC Real time experiment June 1999. Investigations into Limited Delegation of Separation Assurance to the Cockpit



Airspace Elements:

• FREER FLIGHT-EACAC Real time experiment June 1999. Controller Handbook. Section 7 & ANNEX 1 [9]






















• FREER FLIGHT-EACAC Real time experiment June 1999. Pilot Handbook Section 7.3 [10]







Tasks Description:







File: “controller handbook.pdf“





Ground Technology:








4.1.2.4. Correspondent template The file which is the correspondent template to this validation exercise is: “Crossing_Lat_Vert_EACAC-Jun-99 Template.doc”.



4.2. Data of the EEC RTS experiment for EACAC project, June 2000 4.2.1. Station Keeping and Traffic Merging in TMA airspace 4.2.1.1. Validation scenario general co-ordinates Scenario Identification: “EACAC_Jun_00_Station_Keeping”. EACAC June 2000 Real-time Simulation. Station Keeping and Traffic Merging in TMA airspace

Scenario version: 1.0

Author: Isabelle Grimaud, Carol Sheehan, Anne Cloerec & Karim Zeghal



Execution Date: 19th June - 30th June 2000



Validation Tool: Environment will be similar to today using progress strips

4.2.1.2. High Level Objectives and ASAS applications ASAS Category: Airborne Separation

ASAS Application: Station Keeping in TMA considering flight level changes

High Level Objectives: Improve Safety. Increase system capacity. Decrease controller workload. Improve flight efficiency and flexibility



File: “EACAC_CTLHandbook_June00.pdf”


Airspace Elements:

• FREER FLIGHT-EACAC Real time experiment June 2000. Controller Handbook. Sections 7, 11 & 12 [12]





File: “Pilot_Handbook.pdf”






File: “EACAC_CTLHandbook_June.pdf”











• FREER FLIGHT-EACAC Real time experiment June 2000. Pilot Handbook Section 5, 6 & 7 [13]


• FREER FLIGHT-EACAC Real time experiment June 2000. Procedures of delegation from the controller to the pilot. Section 4 [14]

File: “EACAC_Procedures1.1.pdf”




• FREER FLIGHT-EACAC Real time experiment June 2000. Pilot Handbook. Section 6 & 7 [13]




Tasks Description:










• FREER FLIGHT-EACAC Real time experiment June 2000. Procedures of delegation from the controller to the pilot [14]


Ground Technology:








• FREER FLIGHT-EACAC Real time experiment June 2000. Pilot Handbook. Sections 4 & 6 [13]


4.2.1.4. Correspondent template The file which is the correspondent template to this validation exercise is: “Station_Keep_EACAC-Jun-00 Template.doc”. 4.2.2. Lateral and Vertical Crossing and Passing in En-route airspace 4.2.2.1. Validation scenario general co-ordinates Scenario Identification: “EACAC_Jun_00_Crossing_Lat_Vert”. EACAC June 2000 real-time Simulation. Lateral and Vertical Crossing and Passing in En-route airspace


Author: Isabelle Grimaud, Carol Sheehan, Anne Cloerec & Karim Zeghal



Execution Date: 19th June - 30th June 2000



Validation Tool: Environment will be similar to today using progress strips


ASAS Application: ASAS Crossing procedure in en-route airspace & Vertical Crossing








Airspace Elements:

• FREER FLIGHT-EACAC Real time experiment June 2000. Controller Handbook. Sections 7, 11 & 12 [12]






















• FREER FLIGHT-EACAC Real time experiment June 2000. Pilot Handbook Section 5, 6 & 7 [13]





• FREER FLIGHT-EACAC Real time experiment June 2000. Pilot Handbook. Section 6 & 7 [13]




Tasks Description:












• FREER FLIGHT-EACAC Real time experiment June 2000. Procedures of delegation from the controller to the pilot [14]


Ground Technology:






• FREER FLIGHT-EACAC Real time experiment June 2000. Pilot Handbook. Sections 4 & 6 [13]


4.2.2.4. Correspondent template The file which is the correspondent template to this validation exercise is: “Crossing_Lat_Vert_EACAC-Jun-00 Template.doc”.



4.3. Data of the EEC RTS experiment for EACAC project, November 2000 4.3.1. Station Keeping and Traffic Merging in TMA airspace 4.3.1.1. Validation scenario general co-ordinates Scenario Identification: “EACAC_Nov_00_Station_Keeping”. EACAC November 2000 Real-time Simulation. Station Keeping and Traffic Merging in TMA airspace


Author: Isabelle Grimaud, Carol Sheehan, Laurence Rognin & Karim Zeghal


Creation Date: 6th November 2000

Execution Date: 13rd November - 24th November 2000



Validation Tool: Simplified version of EVP (Eatchip Validation Platform) + Pseudo pilot position (MASS) + MCS (Multi Cockpit Simulator)





• FREER FLIGHT-EACAC Real time experiment November 2000. Controller Handbook. Section 2 [15]

File: “controllerhandbook_2.pdf”


Airspace Elements:

• FREER FLIGHT-EACAC Real time experiment November 2000. Controller Handbook. Sections 7, 11 & 12 [15]




• FREER FLIGHT-EACAC Real time experiment November 2000. MCS Pilot Notes. Sections 8, 9, 10 & 11 [16]

File: “MCS_PILOTHNDBK_BK.pdf”

• FREER FLIGHT-EACAC Real time experiment November 2000. Pilot Notes. Sections 9, 10, 11 & 12 [17]

File: “PSEUDO_PILOTHNDBK.pdf”


• FREER FLIGHT-EACAC Real time experiment November 2000. MCS Pilot Notes. Section 8 [16]


• FREER FLIGHT-EACAC Real time experiment November 2000. Pilot Notes. Section 9 [17]



• FREER FLIGHT-EACAC Real time experiment November 2000. Controller Handbook. Sections 2 & 5 [15]
















• FREER FLIGHT-EACAC Real time experiment November 2000. MCS Pilot Notes. Section 5, 6 & 7 [16]




• FREER FLIGHT-EACAC Real time experiment November 2000. Procedures of delegation from the controller to the pilot. Section 4 [18]



• FREER FLIGHT-EACAC Real time experiment November 2000. MCS Pilot Notes. Section 6 & 7 [16]


• FREER FLIGHT-EACAC Real time experiment November 2000. Pilot Notes. Sections 6, 7 & 8 [17]




Tasks Description:














• FREER FLIGHT-EACAC Real time experiment November 2000. Procedures of delegation from the controller to the pilot [18]


Ground Technology:






• FREER FLIGHT-EACAC Real time experiment November 2000. MCS Pilot Notes. Sections 4 & 6 [16]


• FREER FLIGHT-EACAC Real time experiment November 2000. Pilot Notes. Sections 3 & 5 [17]


4.3.1.4. Correspondent template The file which is the correspondent template to this validation exercise is: “Station_Keep_EACAC-Nov-00 Template.doc”.



4.3.2. Lateral and Vertical Crossing and Passing in En-route airspace 4.3.2.1. Validation scenario general co-ordinates Scenario Identification: “EACAC_Nov_00_Crossing_Lat_Vert”. EACAC November 2000 Real-time Simulation. Lateral and Vertical Crossing and Passing in En-route airspace


Author: Isabelle Grimaud, Carol Sheehan, Laurence Rognin & Karim Zeghal



Execution Date: 13rd November - 24th November 2000



Validation Tool: Simplified version of EVP (Eatchip Validation Platform) + Pseudo pilot position (MASS) + MCS (Multi Cockpit Simulator)








Airspace Elements:

• FREER FLIGHT-EACAC Real time experiment November 2000. Controller Handbook. Sections 7, 11 & 12 [15]





• FREER FLIGHT-EACAC Real time experiment November 2000. MCS Pilot Notes. Section 5, 6 & 7 [16]







• FREER FLIGHT-EACAC Real time experiment November 2000. MCS Pilot Notes. Section 6 & 7 [16]






Tasks Description:
















Ground Technology:










4.3.2.4. Correspondent template The file which is the correspondent template to this validation exercise is: “Crossing_Lat_Vert_EACAC-Nov-00 Template.doc”.



4.4. Data of the EEC RTS experiment for EACAC project, November 2001 4.4.1. Station Keeping and Traffic Merging in TMA airspace 4.4.1.1. Validation scenario general co-ordinates Scenario Identification: “EACAC_01_Station_Keeping”. EACAC 2001 Real-time Simulation. Station Keeping and Traffic Merging in TMA airspace


Author: Isabelle Grimaud, Carol Sheehan, Eric Hoffman, Laurence Rognin & Karim Zeghal



Execution Date: 26th November - 14th December 2001



Validation Tool: The environment is similar to today environment, making use of progress strips. However, interactions with the radar labels, allowing marking functions dedicated to delegation, is available.






File: “EACAC'01 ControllerHandbook2.0.pdf”


File: “mcs_pilot_notes.pdf”




File: “Pseudo_Pilot_NOV01.pdf”


Airspace Elements:

• FREER FLIGHT-EACAC Real time experiment November 2001. Controller Handbook. Section 7 & ANNEX 1 [19]




• FREER FLIGHT-EACAC Real time experiment November 2001. Pilot Notes. Sections 9, 10, 11, 12 & 13 [21]










Traffic-Flight Schedule:


















• FREER FLIGHT-EACAC Real time experiment November 2001. MCS Pilot Notes. Section 5, & 7 [20]


• FREER FLIGHT-EACAC Real time experiment November 2001. Pilot Notes. Section 6, 7 & 8 [21]



File: “EACAC_Procedures 2.2.pdf”










Tasks Description:














Ground Technology:










4.4.1.4. Correspondent template The file which is the correspondent template to this validation exercise is: “Station_Keep_EACAC-Nov-01 Template.doc”. 4.4.2. Lateral and Vertical Crossing and Passing in En-route airspace 4.4.2.1. Validation scenario general co-ordinates Scenario Identification: “EACAC_01_Crossing_Lat_Vert”. EACAC 2001 Real-time Simulation. Lateral and Vertical Crossing and Passing in En-route airspace


Author: Isabelle Grimaud, Carol Sheehan, Eric Hoffman, Laurence Rognin & Karim Zeghal



Execution Date: 26th November - 14th December 2001



Validation Tool: The environment is similar to today environment, making use of progress strips. However, interactions with the radar labels, allowing marking functions dedicated to delegation, is available.














Airspace Elements:





• FREER FLIGHT-EACAC Real time experiment November 2001. Pilot Notes. Sections 9, 10, 11, 12 & 13 [21]




























• FREER FLIGHT-EACAC Real time experiment November 2001. MCS Pilot Notes. Section 5, & 7 [20]


• FREER FLIGHT-EACAC Real time experiment November 2001. Pilot Notes. Section 6, 7 & 8 [21]













Tasks Description:
















Ground Technology:








4.4.2.4. Correspondent template The file which is the correspondent template to this validation exercise is: “Crossing_Lat_Vert_EACAC-Nov-01 Template.doc”.



4.5. Data of the EEC RTS experiment for FREER-3 project 4.5.1. Autonomous Aircraft in En-route airspace 4.5.1.1. Validation scenario general co-ordinates Scenario Identification: “FREER-3_Autonomous_Aircraft”. FREER-3. An Experimental Airborne Separation Assurance System [23]


Author: Richard Irvine


Creation Date: End 1997

Execution Date: September 1998 – February 1999

Name of the Project/Study: FREER-3


Validation Tool: 6 B-747-200s, 1 METRO, 2 FOKKER 28s & 1 BEECH 200

4.5.1.2. High Level Objectives and ASAS applications ASAS Category: Airborne Self-Separation ASAS Application: Autonomous Aircraft High Level Objectives: not defined 4.5.1.3. Documents developing the Scenario elements Objectives: not defined


Airspace Elements:

• FREER-3. An Experimental Airborne Separation Assurance System

File: “ASAS freer3.pdf”










Traffic-Aircraft Performance: not defined






Rules for Co-ordination and Transfer Procedures: not defined

Rules-New Phraseology: not defined

Tasks Description:



Roles for the Different Actors in Each Task: not defined

Ground Technology: not defined




4.5.1.4. Correspondent template The file which is the correspondent template to this validation exercise is: “Autonomous_Aircraft_FREER-3 template.doc”.



4.6. Data of the EEC RTS experiment for FAST project 4.6.1. Autonomous Aircraft in En-route airspace 4.6.1.1. Validation scenario general co-ordinates Scenario Identification: “FAST_Autonomous_Aircraft”. FAST (Full Aircraft Separation Transfer): 1999 Pilot in the loop evaluation [24]


Author: Sylvie Grand-Perret


Creation Date: not defined

Execution Date: March to December 1999

Name of the Project/Study: SCS-M-21/FAST study within the FREER FLIGHT project


Validation Tool: Multi aircraft Cockpit Simulator (MCS) + PLUME traffic generator + Dialog Test Facility (DialTFac) supervision tool

4.6.1.2. High Level Objectives and ASAS applications ASAS Category: Airborne Self-Separation

ASAS Application: Autonomous Aircraft

High Level Objectives: Improve Safety. Increase system capacity. Improve flight efficiency and flexibility


• FAST: 1999 Pilot in the loop evaluation. Sections 1, 4.1 & 4.2

File: “FAST_1999 pilot evaluation.pdf”


Airspace Elements: not defined


• FAST: 1999 Pilot in the loop evaluation. Section 4.1





• FAST: 1999 Pilot in the loop evaluation. Section 4.1



• FAST: 1999 Pilot in the loop evaluation. ANNEX A




New Flight Rules:

• FAST: 1999 Pilot in the loop evaluation. Section 2


Separation Rules:

• 1999 Pilot in the loop evaluation. Sections 2.1 & 4.2



Conflict Resolution Strategy Rules:

• 1999 Pilot in the loop evaluation. Sections 2.1, 2.2, 2.3, 2.4, 3.5, 3.5.1 & 3.5.2




Tasks Description:

• FAST: 1999 Pilot in the loop evaluation. Sections 2, 5.2.3 & ANNEX A



• FAST: 1999 Pilot in the loop evaluation. ANNEX A




• Ground Technology: not defined


• FAST: 1999 Pilot in the loop evaluation. Sections 2, 2.1, 3.1, 3.2, 3.3, 3.4, 3.5, 3.5.1 & 3.5.2


4.6.1.4. Correspondent template The file which is the correspondent template to this validation exercise is: “Autonomous_Aircraft_FAST template.doc”.



4.7. Data of the NATS experiment for Longitudinal Station Keeping 4.7.1. Longitudinal Station Keeping 4.7.1.1. Validation scenario general co-ordinates Scenario Identification: “NATS_Longitudinal_Station_Keeping”. Towards an Operational Scenario for Longitudinal station keeping: An ASAS Application [25]


Author: S.J. Sharkey & G.C. Richmond

Organisation: NATS

Creation Date: November 1998

Execution Date: not defined

Name of the Project/Study: R&D Report 9872

Validation Technique: not defined

Validation Tool: not defined


ASAS Application: Longitudinal Station Keeping on cruise

High Level Objectives: Reduce controller workload. Increase system capacity. Improve flight efficiency and flexibility


• Towards an Operational Scenario for Longitudinal station keeping: An ASAS Application. Sections 1.3, 1.4 & 3.6 [25]

File: “longitudinal station keeping_NATS.doc”



Airspace Geographical Scope: not defined

Traffic Volume and Complexity: not defined





• Towards an Operational Scenario for Longitudinal station keeping: An ASAS Application. Section 4.4 [25]



New Flight Rules:



Separation Rules:

• Towards an Operational Scenario for Longitudinal station keeping: An ASAS Application. Sections 1.2, 3.2, 4.2 & 4.4 [25]


Aircraft Sequencing Rules:










Tasks Description:

• Towards an Operational Scenario for Longitudinal station keeping: An ASAS Application. Sections 1.2 & 4.2 [25]





• Towards an Operational Scenario for Longitudinal station keeping: An ASAS Application. Sections 3.2, 3.3, 4.2 & 4.3 [25]


Ground Technology:

• Towards an Operational Scenario for Longitudinal station keeping: An ASAS Application. Sections 3.5 & 4.5 [25]



• Towards an Operational Scenario for Longitudinal station keeping: An ASAS Application. Sections 1.2, 3.5 & 4.5 [25]


4.7.1.4. Correspondent template The file which is the correspondent template to this validation exercise is: “Longitudinal_Station_Keeping_NAST template.doc”.



4.8. Data of the NLR experiments for Free Flight 4.8.1. Basic Cruise Free Flight Scenario, NLR-NASA ASAS 4.8.1.1. Validation scenario general co-ordinates Scenario Identification: “NLR_Basic_Cruise_FF”.


Author: J.M. Hoekstra ([email protected])

Organisation: NLR/NASA/FAA/RLD

Creation Date: 1997

Execution Date: 1997

Name of the Project/Study: TBD NASA/NLR Free Flight with Airborne Separation Assurance

Validation Technique: RTS (Human in the loop with airline pilots)

Validation Tool: NLR Research Flight Simulator


ASAS Application: Airborne self separation in segregated en-route airspace on cruise

High Level Objectives: Improve safety. Increase system capacity. Improve flight efficiency and flexibility

4.8.1.3. Documents developing the Scenario elements The documents can be viewed from the following web sites: “Designing for Safety: the Free Flight Air Traffic Management Concept” http://www.nlr.nl/public/hosted-sites/freeflight/downloads/fftp.pdf Objectives:

• Designing for Safety: the Free Flight Air Traffic Management Concept. Chapter 10. [31]

File: “fftp.pdf”
















New Flight Rules:

• Designing for Safety: the Free Flight Air Traffic Management Concept. Chapters 4 & 15. [31]


Separation Rules:

• Designing for Safety: the Free Flight Air Traffic Management Concept. Chapters 4 &15. [31]




• Designing for Safety: the Free Flight Air Traffic Management Concept. Chapters 4 &15. [31]




Tasks Description: not defined




• Designing for Safety: the Free Flight Air Traffic Management Concept. Chapters 1-3. [31]






4.8.1.4. Correspondent template The file which is the correspondent template to this validation exercise is: “Basic_Cruise_Free_Flight_NLR Template.doc”. 4.8.2. Autonomous Aircraft in TMA 4.8.2.1. Validation scenario general co-ordinates Scenario Identification: “NLR_Autonomous_Aircraft_TMA”. Scenario version: not defined Author: J.M. Hoekstra Organisation: NLR/NASA/FAA/RLD Creation Date: 2001 Execution Date: 2001/2002 Name of the Project/Study: NASA/NLR Free Flight with Airborne Separation Assurance Validation Technique: Human in the loop with airline pilots Validation Tool: NLR Research Flight Simulator Traffic Manager 4.8.2.2. High Level Objectives and ASAS applications ASAS Category: Airborne Self-Separation

ASAS Application: Airborne self separation in TMA for ATC-controlled airspace, segregated en-route airspace and mixed-equipage en-route airspace.

High Level Objectives: Improve safety. Increase system capacity. Improve flight efficiency and flexibility



4.8.2.3. Documents developing the Scenario elements The “Free Flight: How low can you go?". DASC'02 paper is not yet “public available”. Please contact Dr. Jacco M. Hoekstra ([email protected]) for further information. Objectives: Free Flight: How low can you go?. DASC'02 paper. [32]



Airspace Geographical Scope: Free Flight: How low can you go?. DASC'02 paper. [32]

Traffic Volume and Complexity: Free Flight: How low can you go?. DASC'02 paper. [32]






New Flight Rules:

• For descent: Designing for Safety: the Free Flight Air Traffic Management Concept. Chapters 4 & 15. [31]

• For terminal area: Free Flight: How low can you go?. DASC'02 paper. [32]


Separation Rules:

• For descent: Designing for Safety: the Free Flight Air Traffic Management Concept. Chapters 4 & 15. [31]





• Designing for Safety: the Free Flight Air Traffic Management Concept. Chapters 4 & 15. [31]







• Free Flight: How low can you go?. DASC'02 paper. [32]

Tasks Description:

• Free Flight: How low can you go?. DASC'02 paper. [32]








4.8.2.4. Correspondent template The file which is the correspondent template to this validation exercise is: “Autonomous_Aircraft_TMA_NLR Template.doc”.



4.9. Data of the CENA experiments for ASAS 4.9.1. ASAS Crossing Procedure (ACP98) project 4.9.1.1. Validation scenario general co-ordinates Scenario Identification: “CENA_ACP98”

Scenario version: Version 1.0

Author: Beatrice Raynaud

Organisation: CENA

Creation Date: August 1998

Execution Date: November 1998

Name of the Project/Study: ASAS Crossing Procedure (ACP)

Validation Technique: Off-line simulations (based on modified radar data)

Validation Tool: ROSALIE (Required Off-line Simulator for ASAS Logic Implementation and Evaluation)


ASAS Application: ASAS crossing procedure in en-route airspace on cruise

High Level Objectives: Improve flight efficiency and flexibility. Pilot’s acceptability (through ACAS/ASAS compatibility)


• Operational Assessment of Co-operative ASAS Applications. [29]

File: “CENA_ACP98_paper.ps”




• Off-line simulations of the ASAS Crossing Procedure. [28]

File: “CENA_ACP98_slides.ppt”









New Flight Rules:



Separation Rules:








Rules-New Phraseology: N/A

Tasks Description:












4.9.1.4. Correspondent template The file which is the correspondent template to this validation exercise is: “CENA_ACP98_template.doc”. 4.9.2. Theoretical assessment of sector capacity due to ASAS concept

(ASAS_MBB99) 4.9.2.1. Validation scenario general co-ordinates Scenario Identification: “CENA_ASAS_MBB99”

Scenario version: Version 1.2

Author: Thierry Miquel

Organisation: CENA

Creation Date: 07/1999

Execution Date: 07/1999

Name of the Project/Study: Theoretical assessment of sector capacity due to ASAS concept

Validation Technique: Analytical modelling

Validation Tool: MBB model


ASAS Application: ASAS crossing procedure in en-route airspace on cruise. Vertical crossing on cruise

High Level Objectives: Increase system capacity.


• A Theoretical Assessment of Sector Capacity Improvement Due to ASAS Concept. [30]



File: “CENA_ASAS_MBB99_paper.ps”


Airspace Elements:







Traffic-Equipment Type:





Separation Rules:






Rules-New Phraseology: N/A

Tasks Description:








Ground Technology: N/A

Airborne Technology: N/A

4.9.2.4. Correspondent template The file which is the correspondent template to this validation exercise is: “CENA_ASAS_MBB99_template.doc”.



4.10. Data of the University of Glasgow experiments for ASAS 4.10.1. Multi-agent optimal ASAS operations (COAST) 4.10.1.1. Validation scenario general co-ordinates Scenario Identification: “Univ_Glasgow_COAST”. ASAS Co-operative and non co-operative FFA operations

Scenario version: Beta

Author: C Goodchild, M Vilaplana

Organisation: University of Glasgow


Execution Date: N/A

Name of the Project/Study: Multi-agent optimal ASAS operations

Validation Technique: Monte Carlo Simulations

Validation Tool: COAST CO-operative Airborne Separation Tool --- PC Matlab/Simulink/State Flow, Bespoke C++ program

4.10.1.2. High Level Objectives and ASAS applications ASAS Category: Airborne Traffic Situational Awareness

ASAS Application: Enhanced Visual Acquisition (EVA) on cruise and flight level change. Optimised transition between MAS/TMA and FFA. Strategic ASAS through flight plans. Merging ASAS equipped aircraft with non ASAS aircraft

High Level Objectives: Improve safety. Enhance approaches.

4.10.1.3. Documents developing the Scenario elements Documents to be delivered by June 2002. Please contact with Mr. Colin Goodchild ([email protected]) for further information on the exercises. 4.10.1.4. Correspondent template The file which is the correspondent template to this validation exercise is: “Univ_Glasgow_COAST Template.doc”. 4.10.2. Optimal FFA/MAS Transition Methodology Development (T_MAT) 4.10.2.1. Validation scenario general co-ordinates Scenario Identification: “Univ_Glasgow_T_MAT”. ASAS FFA to MAS/TMA Transition



Scenario version: Beta

Author: C Goodchild, Fraser McGibbon

Organisation: University of Glasgow


Execution Date: N/A

Name of the Project/Study: Optimal FFA/MAS Transition Methodology Development

Validation Technique: Monte Carlo Simulations

Validation Tool: Transfer Management Tool (T-MAT) --- PC Matlab/Simulink/State Flow, Bespoke C++ program


ASAS Application: Strategic ASAS through flight plans. Merging ASAS equipped aircraft with non ASAS aircraft in MAS

High Level Objectives: Sectorless airspace capability.

4.10.2.3. Documents developing the Scenario elements Documents to be delivered by June 2002. Please contact with Mr. Colin Goodchild ([email protected]) for further information on the exercises. 4.10.2.4. Correspondent template Not defined.



4.11. Data of the EMERALD project 4.11.1. Closely Spaced Parallel Approaches in Instrumental Meteorological

Conditions 4.11.1.1. Validation scenario general co-ordinates Scenario Identification: “EMERALD_Close_Spaced_Paral_Appr”.

Scenario version: N/A

Author: Michel Guettier, Francis Casaux, Thierry Michel, Sarah Sharkey, Gerard Sainthuille, Guilhem de Cazenove, Pascal Dias, Ken Carpenter, R. P. Bill Booth, Martin Downes

Organisation: DERA/CENA/SEXTANT/Thomson/Sofreavia

Creation Date: October 1998

Execution Date: N/A

Name of the Project/Study: EMERALD

Validation Technique: N/A

Validation Tool: N/A


ASAS Application: Closely spaced parallel approaches

High Level Objectives: Decrease controller workload. Increase pilot’s confidence. Increase system capacity. Improve airport arrival planning. Improve reliability of flight time


• EMERALD. WP5. Assessment of Emerging Technologies: the Specific Case of ADS-B/ASAS. Annex B. [25]

File: “EMERALD_Volume6.pdf”

Airspace Restrictions:









Traffic-Aircraft Performance



New ATS Involved: N/A

New Flight Rules: N/A

Separation Rules:

















Tasks Description:






Ground Technology:






4.11.1.4. Correspondent template The file which is the correspondent template to this validation exercise is: “Close_Spaced_Paral_Appr_EMERALD Template.doc”. 4.11.2. Longitudinal Station Keeping 4.11.2.1. Validation scenario general co-ordinates Scenario Identification: “EMERALD_Long_Station_Keeping”.





Execution Date: N/A







ASAS Application: Longitudinal Station Keeping

High Level Objectives: Decrease controller workload. Decrease number of voice communications between controller and flight crew. Increase system capacity. Improve flow management. Improve reliability of flight time. Optimise flight profile. Achieve fuel savings


• EMERALD. WP5. Assessment of Emerging Technologies: the Specific Case of ADS-B/ASAS. Annex A. [25]





Airspace Elements:















Separation Rules:















Tasks Description:








Ground Technology: EMERALD. WP5.

• Assessment of Emerging Technologies: the Specific Case of ADS-B/ASAS. Annex A. [25]





4.11.2.4. Correspondent template The file which is the correspondent template to this validation exercise is: “Long_Station_Keep_EMERALD Template.doc”. 4.11.3. Autonomous Aircraft 4.11.3.1. Validation scenario general co-ordinates Scenario Identification: “EMERALD_Autonomous_Aircraft”.





Execution Date: N/A







ASAS Application: Airborne self separation in ATC-controlled airspace in TMA. Airborne self separation in segregated en-route airspace in TMA. Airborne self separation in mixed-equipage en-route airspace in TMA

High Level Objectives: Increase system capacity. Improve reliability of flight time. Achieve fuel savings. Reduce en-route charges


• EMERALD. WP5. Assessment of Emerging Technologies: the Specific Case of ADS-B/ASAS. Annex C. [25]



Airspace Elements:












New Flight Rules:





Separation Rules:









Tasks Description:






Ground Technology:








4.11.3.4. Correspondent template The file which is the correspondent template to this validation exercise is: “Autonomous_Aircraft_EMERALD Template.doc”.



4.12. Data of the EMERTA project 4.12.1. Enhanced Visual Acquisition 4.12.1.1. Validation scenario general co-ordinates Scenario Identification: “EMERTA_Enh_Visual_Acquis”.


Author: David Bowen. R.P.Bill Booth. Ben Stanley. Robin Garrity. Eric Vallauri. Jean-Etienne Deraet. Patrick Giles

Organisation: DERA/Sofreavia/AIRSYS/NATS

Creation Date: March 2000

Execution Date: N/A

Name of the Project/Study: EMERTA



4.12.1.2. High Level Objectives and ASAS applications ASAS Category: Airborne Traffic Situational Awareness ASAS Application: Enhanced Visual Acquisition High Level Objectives: Improve safety. Increase efficiency of visual procedures 4.12.1.3. Documents developing the Scenario elements Objectives:

• EMERTA. WP 3.1: ASAS feasibility and transition issues. Section 5.2. [26]

File: “EMERTA_WP3.1Ver2.0.pdf”


Airspace Elements:














New Flight Rules:



Separation Rules:









Tasks Description:






Ground Technology:








4.12.1.4. Correspondent template The file which is the correspondent template to this validation exercise is: “Enh_Visual_Acquis_EMERTA Template.doc”. 4.12.2. Station Keeping on Approach 4.12.2.1. Validation scenario general co-ordinates Scenario Identification: “EMERTA_Station_Keeping_Apprach”.


Author: David Bowen. R.P.Bill Booth. Ben Stanley. Robin Garrity. Eric Vallauri. Jean-Etienne Deraet. Patrick Giles

Organisation: DERA/Sofreavia/AIRSYS/NATS

Creation Date: March 2000

Execution Date: N/A

Name of the Project/Study: EMERTA




ASAS Application: Station Keeping on Approach

High Level Objectives: Decrease controller workload. Increase pilot confidence. Increase pilot situational awareness. Increase system capacity
















Separation Rules:









Tasks Description:








Ground Technology:






4.12.2.4. Correspondent template The file which is the correspondent template to this validation exercise is: “Station_Keep_Appr_EMERTA Template.doc”.


CARE/ASAS Activity 2: VF Project-WP1- D2 ASAS Scenario Repository – Version 1.0 – 08 August 2002 Isdefe ISCARE-021222-1L

Annex A. Requirements of ASAS Scenario Repository To VDR.


CARE/ASAS Activity 2: VF Project-WP1- D2 ASAS Scenario Repository – Version 1.0 – 08 August 2002 page A.1 Isdefe ISCARE-021222-1L

1. DOCUMENT SCOPE Previous to the development of the ASAS repository, the possibility to implement this repository within the VDR currently developed by EUROCONTROL has been proposed. As VDR is a general database to include validation exercises in a wide range of applications and goals and ASAS applications validation exercises are particular ones with special peculiarities, some sort of requirements from ASAS repository must be required to VDR to guarantee that VDR complies with the peculiarities of ASAS validation scenarios in order to assure the compatibility between ASAS data and VDR. This document addresses the requirements required by CARE/ASAS/VF activity to VDR in order to implement the ASAS repository within the VDR. These requirements are only regarding the functionalities required to VDR to fill up ASAS repository needs. It is not the intention of current document to define requirements regarding VDR access, security, maintainability, flexibility, reliability and any other VDR characteristic apart from those defining VDR functions to permit the integration of the ASAS repository within VDR. 2. REQUIREMENTS CODIFICATION The requirements stated in this document are codified using the following structure (Rq-xxxx.yy) to open the requirement and (End-Rq) to end the requirement, where: • Rq means “requirement”.

• xxxx is the order number for the requirement within the document.

• yy is the number of the specification document revision where the requirement was reviewed by last time.

• End means the wording of the requirement is finished. All any other text that is not located between (Rq-xxxx.yy) and (End-Rq) is not a requirement.

3. ASAS REPOSITORY REQUIREMENTS TO VDR 3.1. General requirements (Rq-0001.04) VDR storage features The VDR shall enable the input, storage and reading of ASAS validation scenarios. (End-Rq) (Rq-0010.04) VDR additional features The VDR shall enable the input, storage and reading of metrics, parameters and results for all the ASAS scenarios stored. (End-Rq)



(Rq-0015.04) ASAS data output The VDR shall enable the display, printing and downloading of ASAS scenarios. (End-Rq) (Rq-0020.04) ASAS data security The VDR shall guarantee the ASAS scenarios data proprietary and confidentiality allowing data access only to authorised persons (End-Rq) (Rq-0025.04) ASAS data in the VDR The ASAS scenario data contained in VDR will be compounded of the following fields: • General scenario data • High Level Objectives aimed by the validation exercise • ASAS application • Template with the selected elements to create the scenario (in a file) • Further details of the elements forming the scenario (in file(s)) (End-Rq) (Rq-0030.01) Data reports The VDR shall provide reports of the stored ASAS scenarios under petition. The reports shall contain the following information: • General scenario data • High Level Objectives • ASAS application • Name of the template file • List of the names of the files of the documents detailing the elements (End-Rq) (Rq-0035.01) Data reports output By clicking on the ASAS scenario identification the report will be ready for display, printing or downloading. (End-Rq) (Rq-0040.01) Hyperlinks VDR shall provide hyperlinks to the following documents:



• Template file • Files of the documents detailing the elements (End-Rq) (Rq-0045.01) Hyperlinks actions By clicking on the template/documents hyperlinks, three options will be presented: • Display of the document • Printing of the document • Download of the document (End-Rq) (Rq-0050.04) ASAS scenario queries The VDR shall permit queries by the following two options: • High Level Objectives • ASAS application • Validation technique (End-Rq) (Rq-0055.04) Data of the queries The queries shall present the list of the ASAS scenarios stored complying the input for the query with the following associated data: • Validation technique • ASAS scenario identification • Project • Organisation • Creation date (End-Rq) 3.2. Requirements from General Data (Rq-0100.04) General data definition The VDR shall enable the user to input following general data related with the ASAS scenario: • ASAS scenario Identification • Version • Project • Organisation • Author



• Creation Date • Trial Date • Validation Technique • Validation Tool (End-Rq) (Rq-0105.04) Validation techniques definition The VDR shall enable the user to input the validation technique by selecting one from the following list:

− Judgmental/Survey − Analytical − Fast Time Simulation − Real Time Simulation

(End-Rq) (Rq-0110.01) General data fields size The size of the general data fields shall be large enough to permit large identifications (e.g. 30 characters). (End-Rq) (Rq-0115.01) Free text box Additionally to the general data inputs, the VDR shall permit the user to input a free text. (End-Rq) (Rq-0120.01) Free text size The size of the free text field shall be 200 characters at least. (End-Rq) (Rq-0125.04) General data display The general data shall be presented to the user when the ASAS scenario is called. (End-Rq) (Rq-0130.01) General data printing The general data shall be printed in one of two following cases: • When requested by the user • When printing the associated template



(End-Rq) 3.3. Requirements from Operational Concept Objectives data (Rq-0200.01) ASAS category The VDR shall allow the user to select among one of the following ASAS categories: • Airborne Traffic Situational Awareness • Airborne Spacing • Airborne Separation • Airborne Self-separation (End-Rq) (Rq-0210.04) ASAS category vs. objectives As the high level objectives are ASAS category dependent, before selecting the objectives, the VDR shall enable the user to select the ASAS category. (End-Rq) (Rq-0220.04) High Level Objectives groups The operational concept objectives are clustered in the next groups, independently of the ASAS category: • Safety • Capacity • Economics • Environment • Security (End-Rq) (Rq-0230.04) High level objectives within “Airborne Traffic Situational Awareness” category For Airborne Traffic Situational Awareness category, the objectives to be presented within each group are as follows: • Safety

− Decrease risk of faults in aircraft identification − Improve safety − Increase pilot’s situational awareness − Reduce runway incursions and collisions − Decrease number of voice communications between controller and flight crew

• Capacity



− Enhance approaches − Increase efficiency of visual procedures − Improve airport surface operations

• Economics • Environment • Security (End-Rq) (Rq-0240.04) High level objectives within “Airborne Spacing” category For Airborne Spacing category, the objectives to be presented within each group are as follows: • Safety

− Improve safety − Increase pilot’s situational awareness − Decrease number of voice communications between controller and flight crew

• Capacity

− Increase capacity in a sector − Increase sector length − Improve flow management − Improve airport arrival planning − Decrease controller workload

• Economics • Environment • Security (End-Rq) (Rq-0250.04) High level objectives within “Airborne Separation” category For Airborne Separation category, the objectives to be presented within each group are as follows: • Safety

− Improve safety − Increase pilot’s situational awareness − Decrease number of voice communications between controller and flight crew − Increase pilot’s confidence

• Capacity

− Increase capacity − Increase sector length − Improve flow management − Improve airport arrival planning



− Decrease controller workload • Economics

− Improve flight efficiency and flexibility − Improve reliability of flight times − Optimise flight profile − Achieve fuel savings

• Environment

− Achieve fuel savings • Security (End-Rq) (Rq-0260.04) High level objectives within “Airborne Self-separation” category For Airborne Self-separation category, the objectives to be presented within each group are as follows: • Safety

− Improve safety − Increase pilot’s situational awareness − Decrease number of voice communications between controller and flight crew − Increase pilot’s confidence

• Capacity

− Increase system capacity − Improve flight efficiency and flexibility − Decrease controller workload

• Economics

− Optimise flight profile − Achieve fuel savings − Improve reliability of flight times − Reduce en-route charges

• Environment

− Achieve fuel savings • Security (End-Rq)



(Rq-0270.04) Objectives input After selecting the ASAS category, the user shall select the objective group from the list in (Rq-0220.04). Within the objective group, the VDR shall enable the user to input the high level objectives by clicking the selected ones from the lists in (Rq-0230.04), (Rq-0240.04), (Rq-0250.04) and (Rq-0260.04). (End-Rq) 3.4. Requirements from ASAS Application data (Rq-0300.01) ASAS category The selection made according to (Rq-0200.01) will be valid for ASAS application. (End-Rq) (Rq-0310.01) ASAS category vs. ASAS application As the ASAS applications are ASAS category dependent, the VDR shall enable the user to select the ASAS applications according to the selection made following (Rq-0200.01). (End-Rq) (Rq-0320.01) ASAS applications within “Airborne Traffic Situational Awareness” category For Airborne Traffic Situational Awareness category, the ASAS applications with their optional flight phases to be presented are as follows: IN THE AIR • Enhanced Visual Acquisition (EVA):

− Cruise − Flight level change

• Enhanced Visual Approaches:

− Approach • Enhanced “See and Avoid”:

− Cruise − Flight level change

• Enhanced Traffic Information Broad-cast by Aircraft (E-TIBA):

− Cruise − Flight level change − Approach



ON THE GROUND • Improved taxi/runway occupancy awareness:

− On the ground (End-Rq) (Rq-0330.01) ASAS applications within “Airborne Spacing” category For Airborne Spacing category, the ASAS applications with their optional flight phases to be presented are as follows: • In-descent spacing:

− Approach • Level flight spacing:

− Cruise • Lateral crossing and passing:

− Cruise • Vertical Crossing:

− Cruise (End-Rq) (Rq-0340.01) ASAS applications within “Airborne Separation” category For Airborne Separation category, the ASAS applications with their optional flight phases to be presented are as follows: • Time-based sequencing:

− Ascent − Approach

• ASAS crossing procedure in en-route airspace:

− Cruise • Station keeping in en-route airspace:

− Cruise • Station keeping in TMA:

− Flight level changes



− Approach • Vertical Crossing:

− Cruise • Closely spaced parallel approach:

− Approach (End-Rq) (Rq-0350.01) ASAS applications within “Airborne Self-separation” category For Airborne Self-separation category, the ASAS applications with their optional flight phases to be presented are as follows: • Airborne self separation in ATC-controlled airspace:

− Cruise − Flight level change − TMA

• Airborne self separation in segregated en-route airspace

− Cruise − TMA

• Airborne self separation in mixed-equipage en-route airspace:

− Cruise − TMA

(End-Rq) (Rq-0360.01) ASAS application input After selecting the ASAS category, the VDR shall enable the user to input the ASAS application by clicking the selected ones from the lists in (Rq-0320.01), (Rq-0330.01), (Rq-0340.01) and (Rq-0350.01). (End-Rq) (Rq-0370.04) ASAS application vs. ASAS scenario Each ASAS scenario is joined to only one ASAS application. (End-Rq)



3.5. Requirements from the Template data (Rq-0400.04) Template storing The VDR shall store the validation template file associated to each ASAS application scenario input in the VDR. (End-Rq) (Rq-0410.01) Template access The VDR shall enable the access to the template by clicking on the hyperlink. (End-Rq) (Rq-0420.01) Template output The VDR shall enable to display, print or download the template. (End-Rq) 3.6. Requirements from the Detailed Documents data (Rq-0500.04) Documents storing The VDR shall store the files of the documents detailing the ASAS application scenario associated to each ASAS application scenario input in the VDR. (End-Rq)



(Rq-0510.04) Documents list The documents to be stored and hyperlinked are following: • High Level Objectives • Airspace: Restrictions • Airspace: Elements • Airspace: Geographical Scope • Traffic: Volume and Complexity • Traffic: Flight Schedule • Traffic: Aircraft Performance • ATS Involved: New Services • Rules: New Flight Rules • Rules: Separation • Rules: Aircraft Sequencing • Rules: Conflict Resolution Strategy • Rules: Co-ordination and Transfer Procedures • Rules: New Phraseology • Tasks: Tasks Description • Actors: Roles for the Different Actors in Each Task • Technology: Ground Technology • Technology: Airborne Technology (End-Rq) (Rq-0520.01) Documents access The VDR shall enable the access to the documents by clicking on the hyperlink. (End-Rq) (Rq-0530.01) Documents output The VDR shall enable to display, print or download the template. (End-Rq)


CARE/ASAS Activity 2: VF Project-WP1- D2 ASAS Scenario Repository – Version 1.0 – 08 August 2002 Isdefe ISCARE-021222-1L

Annex B. Template for the Validation of ASAS Applications.


CARE/ASAS Activity 2: VF Project-WP1- D2 ASAS Scenario Repository – Version 1.0 – 08 August 2002 page B.1 Isdefe ISCARE-021222-1L

1. “EACAC_99_STATION_KEEPING”. EACAC 1999 REAL-TIME SIMULATION. STATION KEEPING AND TRAFFIC MERGING IN TMA AIRSPACE Validation Technique: Real Time Simulation ASAS CATEGORY: Airborne Separation Scenario ID: EACAC_99_Station_Keeping Project: Freer Flight/EACAC Flight crew is responsible for separation assurance from a target aircraft, with limits in time, distance and scope. Controller retains all other separation responsibility. Organisation: EEC Creation Date: 27/05/1999

ACTORS ASAS APPLICATION & ASSOCIATED FLIGHT PHASES

HIGH LEVEL OBJECTIVE(S)

AIRSPACE TRAFFIC AIR TRAFFIC SERVICES INVOLVED

RULES TASKS Performer Supervisor

TECHNOLOGY

Obtain surveillance data

Tactical controller Flight crew Technology

Tactical controller Flight crew

• FLIGHT RULES: IFR VFR New rules Manage surveil-

lance data Tactical controller Technology


• VOLUME: Very High High Medium Low

Broadcast surveil-lance data



COMPLEXITY

• LONGITUDINAL SEPARATION: Time Distance Tolerance

Identify equipment level of aircraft


Tactical controller

• Time-based sequencing: Ascent Approach

AIRCRAFT PERFORMANCE

Request delegation on separation as-surance responsi-bility


Tactical controller • LATERAL SEPARATION: Distance Tolerance

Accept delegation on separation assurance responsibility

Flight crew Flight crew • ASAS crossing procedure in en-route airspace: Cruise

• RESTRICTIONS: Applicable in any

controlled airspace Applicable in

exclusively reserved airspace Capacity/flow

restrictions

• TIMEFRAME 2001-2005 2005-2010 2010-2015 2015-2020

Perform separation assurance from des-ignated aircraft

Flight crew Flight crew

• AIRCRAFT TYPE:

• PHRASEOLOGY: Standard New (define)

GROUND • Communications:

Voice Data link Inter-sector information

transfer • Surveillance: Radar coverage TIS-B ADS-B CWP HMI with aircraft

equipment, ID and delegation status Controller assistance

position tool Sequencing tool Separation monitoring

tool Recovering tool

• ATM Planning Automation

Assure separation from surrounding aircraft

Planning controller Tactical controller Flight crew Technology

Tactical controller

Interruption of the application



ICAO A B C D E F H

FAA Heavy Medium Turboprop Medium Turbojet Light

• RVSM: Yes No

Take responsibility after airborne equipment failure

Tactical controller Tactical controller

• Station keeping in en-route airspace: Cruise

Transfer to next sector


Fix separation in time or distance

Planning controller Tactical controller

Planning controller

• FLIGHT

SCHEDULE Time Aircraft ID Aircraft model Equipment Trajectory

Fix time or length of the segment


Planning controller

• Station keeping in TMA: Flight level changes Approach

Decide clearances and instructions


Tactical controller

Maintain traffic sit-uational awareness

Flight crew Tactical controller

Define joining point & flight level to begin application


• EQUIPMENT

TYPE: Equipped* Unequipped Mixed % equipped aircraft

* At least one equipped aircraft is mandatory

AIRCRAFT SEQUENCING

CONFLICT

RESOLUTION STRATEGY

CO-ORDINATION AND TRANSFER PROCEDURES

Line up the a/c in the staggered approach pattern


• Vertical Crossing: Cruise

Follow the control-ler’s clearances and instructions

Flight crew Technology

Flight crew

See and avoid other traffic

Tactical controller Planning controller Flight crew


• Closely spaced parallel approach: Approach

• SAFETY Improve safety Increase pilot’s

situational awareness Decrease number of

voice communica-tions between con-troller and flight crew Increase pilot’s

confidence • CAPACITY Increase capacity Increase sector

length Improve flow

management Improve airport ar-

rival planning Decrease controller

workload • ECONOMICS Improve flight effi-

ciency and flexibility Improve reliability

of flight times Optimise flight

profile Achieve fuel savings

• ENVIRONMENT Achieve fuel savings

• SECURITY

• TYPES: MAS UMAS FFAS

• AREAS:

En-route TMA Airport

• ELEMENTS:

Routes Waypoints Flight levels Sectors En-route Descent/Ascent Special areas and alternative routes Terrain topo-graphy Atmospheric conditions

• GEOGRAPHICAL

SCOPE Central Europe Eastern Europe Scandinavia North Atlantic Mediterranean

ATC FIS TIS-B APP Alert Service GNSS ATFM Performance Management New Services

TRAINED FLIGHT CREWS*

* Mandatory on equipped aircraft

Use TCAS, if ins-talled


AIRBORNE Redundancy

• Communications: Voice Data link

• Surveillance: Mode-S TCAS II/ETCAS Audio/visual alerts Traffic information

processing Surveillance data

processing Spacing function pro-

cessing • Navigation: GNSS with augmen-

tation FMS Automatic separation

management (connec-tion with FGCS)

• Display: CDTI/EFIS/MCDU HUD



2. “EACAC_99_CROSSING_LAT_VERT”. EACAC 1999 REAL-TIME SIMULATION. LATERAL AND VERTICAL CROSSING AND PASSING IN EN-ROUTE AIRSPACE Validation Technique: Real Time Simulation ASAS CATEGORY: Airborne Spacing Scenario ID: EACAC_99_crossing Project: Freer Flight/EACAC Flight crews achieve and maintain a given spacing from designated aircraft. The controller maintains responsibility Organisation: EEC Creation Date: 27/05/1999





TECHNOLOGY




• FLIGHT RULES: IFR VFR New rules Manage surveill-

ance data Tactical controller Technology

Tactical controller

• In-descent spacing: Approach




Tactical controller

COMPLEXITY

• SEPARATION: Time Distance



Tactical controller

Identify operational status of aircraft equipment

Technology Flight crew


controlled airspace Capacity/flow

restrictions

• TIMEFRAME 2001-2005 2005-2010 2010-2015 2015-2020



GROUND • Communications: Voice Data link Inter-sector information


equipment, ID and delegation status


• AIRCRAFT TYPE:

• Level flight spacing: Cruise



Tactical controller ICAO A B C D E F H


AIRCRAFT SEQUENCING

CONFLICT

RESOLUTION STRATEGY

CO-ORDINATION

AND TRANSFER PROCEDURES

Interrupt the appli-cation


Tactical controller





Planning controller

• Lateral crossing and passing: Cruise

• FLIGHT



Fix time or length of

the segment Planning controller Tactical controller

Planning controller



Tactical controller • EQUIPMENT


* At least one equipped aircraft mandatory

• RVSM: Yes No














length Improve flow








• SECURITY


• AREAS:

En-route TMA

• ELEMENTS:

Routes Waypoints Flight levels Sectors En-route Descent/Ascent Special areas and alternative routes Terrain topo-

graphy Atmospheric

conditions • GEOGRAPHICAL







AIRBORNE • Communications: Voice Data link



processing Spacing function

processing • Navigation: GNSS with augmen-

tation FMS

• Display: CDTI/EFIS/MCDU



3. “EACAC_JUN_00_STATION_KEEPING”. EACAC JUNE 2000 REAL-TIME SIMULATION. STATION KEEPING AND TRAFFIC MERGING IN TMA AIRSPACE Validation Technique: Real Time Simulation ASAS CATEGORY: Airborne Separation Scenario ID: EACAC_Jun_00_Station_Keeping Project: Freer Flight/EACAC Flight crew is responsible for separation assurance from a target aircraft, with limits in time, distance and scope. Controller retains all other separation responsibility. Organisation: EEC Creation Date: 03/05/2000





TECHNOLOGY











COMPLEXITY




Tactical controller











restrictions

• TIMEFRAME 2001-2005 2005-2010 2010-2015 2015-2020



• AIRCRAFT TYPE:











Tactical controller




ICAO A B C D E F H


• RVSM: Yes No








Planning controller

• FLIGHT




Planning controller




Tactical controller





• EQUIPMENT



AIRCRAFT SEQUENCING

CONFLICT

RESOLUTION STRATEGY







Flight crew









length Improve flow








• SECURITY


• AREAS:


• ELEMENTS:


• GEOGRAPHICAL







AIRBORNE Redundancy











4. “EACAC_JUN_00_CROSSING_LAT_VERT”. EACAC JUNE 2000 REAL-TIME SIMULATION. LATERAL AND VERTICAL CROSSING AND PASSING IN EN-ROUTE AIRSPACE Validation Technique: Real Time Simulation ASAS CATEGORY: Airborne Separation Scenario ID: EACAC_Jun_00_Crossing_Lat_Vert Project: Freer Flight/EACAC Flight crew is responsible for separation assurance from a target aircraft, with limits in time, distance and scope. Controller retains all other separation responsibility. Organisation: EEC Creation Date: 03/05/2000





TECHNOLOGY











COMPLEXITY




Tactical controller











restrictions

• TIMEFRAME 2001-2005 2005-2010 2010-2015 2015-2020



• AIRCRAFT TYPE:











Tactical controller




ICAO A B C D E F H


• RVSM: Yes No








Planning controller

• FLIGHT




Planning controller




Tactical controller





• EQUIPMENT



AIRCRAFT SEQUENCING

CONFLICT

RESOLUTION STRATEGY







Flight crew









length Improve flow








• SECURITY


• AREAS:


• ELEMENTS:


• GEOGRAPHICAL







AIRBORNE Redundancy











5. “EACAC_NOV_00_STATION_KEEPING”. EACAC NOVEMBER 2000 REAL-TIME SIMULATION. STATION KEEPING AND TRAFFIC MERGING IN TMA AIRSPACE Validation Technique: Real Time Simulation ASAS CATEGORY: Airborne Separation Scenario ID: EACAC_Nov_00_Station_Keeping Project: Freer Flight/EACAC Flight crew is responsible for separation assurance from a target aircraft, with limits in time, distance and scope. Controller retains all other separation responsibility. Organisation: EEC Creation Date: 06/11/2000





TECHNOLOGY











COMPLEXITY




Tactical controller











restrictions

• TIMEFRAME 2001-2005 2005-2010 2010-2015 2015-2020



• AIRCRAFT TYPE:











Tactical controller




ICAO A B C D E F H


• RVSM: Yes No








Planning controller

• FLIGHT




Planning controller




Tactical controller





• EQUIPMENT



AIRCRAFT SEQUENCING

CONFLICT

RESOLUTION STRATEGY







Flight crew









length Improve flow








• CAPACITY


• AREAS:


• ELEMENTS:


• GEOGRAPHICAL







AIRBORNE Redundancy











6. “EACAC_NOV_00_CROSSING_LAT_VERT”. EACAC NOVEMBER 2000 REAL-TIME SIMULATION. LATERAL AND VERTICAL CROSSING AND PASSING IN EN-ROUTE AIRSPACE Validation Technique: Real Time Simulation ASAS CATEGORY: Airborne Separation Scenario ID: EACAC_Nov_00_Crossing_Lat_Vert Project: Freer Flight/EACAC Flight crew is responsible for separation assurance from a target aircraft, with limits in time, distance and scope. Controller retains all other separation responsibility. Organisation: EEC Creation Date: 06/11/2000





TECHNOLOGY











COMPLEXITY




Tactical controller











restrictions

• TIMEFRAME 2001-2005 2005-2010 2010-2015 2015-2020



• AIRCRAFT TYPE:











Tactical controller




ICAO A B C D E F H


• RVSM: Yes No








Planning controller

• FLIGHT




Planning controller




Tactical controller





• EQUIPMENT



AIRCRAFT SEQUENCING

CONFLICT

RESOLUTION STRATEGY







Flight crew









length Improve flow








• SECURITY


• AREAS:


• ELEMENTS:


• GEOGRAPHICAL







AIRBORNE Redundancy











7. “EACAC_01_STATION_KEEPING”. EACAC 2001 REAL-TIME SIMULATION. STATION KEEPING AND TRAFFIC MERGING IN TMA AIRSPACE Validation Technique: Real Time Simulation ASAS CATEGORY: Airborne Separation Scenario ID: EACAC_01_Station_Keeping Project: Freer Flight/EACAC Flight crew is responsible for separation assurance from a target aircraft, with limits in time, distance and scope. Controller retains all other separation responsibility. Organisation: EEC Creation Date: 20/11/2001





TECHNOLOGY











COMPLEXITY




Tactical controller











restrictions

• TIMEFRAME 2001-2005 2005-2010 2010-2015 2015-2020



• AIRCRAFT TYPE:











Tactical controller




ICAO A B C D E F H


• RVSM: Yes No








Planning controller

• FLIGHT




Planning controller




Tactical controller





• EQUIPMENT



AIRCRAFT SEQUENCING

CONFLICT

RESOLUTION STRATEGY







Flight crew









length Improve flow








• SECURITY


• AREAS:


• ELEMENTS:


• GEOGRAPHICAL







AIRBORNE Redundancy











8. “EACAC_01_CROSSING_LAT_VERT”. EACAC 2001 REAL-TIME SIMULATION. LATERAL AND VERTICAL CROSSING AND PASSING IN EN-ROUTE AIRSPACE Validation Technique: Real Time Simulation ASAS CATEGORY: Airborne Separation Scenario ID: EACAC_01_Crossing_Lat_Vert Project: Freer Flight/EACAC Flight crew is responsible for separation assurance from a target aircraft, with limits in time, distance and scope. Controller retains all other separation responsibility. Organisation: EEC Creation Date: 20/11/2001





TECHNOLOGY











COMPLEXITY




Tactical controller











restrictions

• TIMEFRAME 2001-2005 2005-2010 2010-2015 2015-2020



• AIRCRAFT TYPE:




transfer • Surveillance: Radar coverage TIS-B ADS-B CWP HMI with air-craft







Tactical controller




ICAO A B C D E F H


• RVSM: Yes No








Planning controller

• FLIGHT




Planning controller




Tactical controller





• EQUIPMENT



AIRCRAFT SEQUENCING

CONFLICT

RESOLUTION STRATEGY







Flight crew









length Improve flow








• SECURITY


• AREAS:


• ELEMENTS:


• GEOGRAPHICAL







AIRBORNE Redundancy











9. “FREER-3_AUTONOMOUS_AIRCRAFT”. FREER-3. AN EXPERIMENTAL AIRBORNE SEPARATION ASSURANCE SYSTEM Validation Technique: Real Time Simulation ASAS CATEGORY: Airborne Self-separation Scenario ID: FREER-3_Autonomous_Aircraft Project: FREER-3 Flight crews are responsible for separating their aircraft from all surrounding traffic under specific conditions and in specified airspace. Organisation: EEC Creation Date: end 1997





TECHNOLOGY





• FLIGHT RULES: IFR New rules

Manage and process surveillance data



COMPLEXITY Broadcast surveil-lance data



• RESTRICTIONS: Applicable in a new

class of segregated airspace to be defined Capacity/flow

restrictions • SEPARATION:

Time Distance Tolerances Co-ordinate transfer

of aircraft to non FFAS

Tactical controller Tactical controller • FLIGHT SCHEDULE Time Aircraft ID Aircraft model Equipment Trajectory

Report technology performances de-gradation


Flight crew

Assume responsibi-lity for technology failures on airborne equipment



• Airborne self separation in ATC-controlled airspace:

Cruise Flight level change TMA

• TIMEFRAME 2001-2005 2005-2010 2010-2015 2015-2020


Assume responsibi-lity for technology failures on ground equipment




transfer • Surveillance: Radar coverage No radar coverage TIS-B ADS-B CWP HMI with aircraft


tool Traffic density control &

estimation tool MONA


• AIRCRAFT TYPE: Perform separation assurance


Flight crew



Flight crew

ICAO A B C D E F H


• RVSM: Yes No

Request delegation on separation assurance responsibility


Tactical controller

Manage the FFAS traffic complexity and density

Planning controller Planning controller

• Airborne self separation in segregated en-route airspace Cruise TMA

Define an orderly flow of traffic (stra-tegic, pre-tactical and tactical)



• EQUIPMENT TYPE: Equipped* Mixed % equipped aircraft

* Equipped aircraft are mandatory in segregated airspace

AIRCRAFT SEQUENCING

CONFLICT

RESOLUTION STRATEGY

CO-ORDINATION



Planning controller Tactical controller Technology

Tactical controller



Request exit from FFAS





Flight crew




• Airborne self separation in mixed-equipage en-route airspace: Cruise TMA



voice communica-tions between con-troller and flight crew

• CAPACITY Increase system

capacity Improve flight effi-

ciency and flexibility Decrease controller

workload • ECONOMICS Optimise flight

profile Achieve fuel savings Improve reliability

of flight times Reduce en-route

charges • ENVIRONMENT Achieve fuel savings

• SECURITY

• TYPES: MAS UMAS FFAS New types

• AREAS:

En-route TMA Airport New areas

• ELEMENTS:

Boundaries (space and time) Entry and exit points Transition zones Vertical Descent/ Ascent buffer zone (for emergencies) Special areas and alternative routes Terrain topo-graphy Atmospheric conditions

• GEOGRAPHICAL


ATC FIS TIS-B Alert Service GNSS ATFM Performance Management New Services





AIRBORNE Redundancy



processing Surveillance data pro-

cessing (ADS-B) Conflict detection &

resolution system • Navigation: GNSS with augmen-

tation FMS 4D RNAV RNP1 Flight data system Automatic management

of the separation (connection with FGCS)




10. “FAST_AUTONOMOUS_AIRCRAFT”. FAST (FULL AIRCRAFT SEPARATION TRANSFER): 1999 PILOT IN THE LOOP EVALUATION Validation Technique: Real Time Simulation ASAS CATEGORY: Airborne Self-separation Scenario ID: FAST_Autonomous_Aircraft Project: SCS-M-21/FAST Flight crews are responsible for separating their aircraft from all surrounding traffic under specific conditions and in specified airspace. Organisation: EEC Creation Date: July 2000





TECHNOLOGY













class of segregated airspace to be defined

Capacity/flow restrictions • SEPARATION:

Time Distance Tolerances Co-ordinate transfer





Flight crew




• Airborne self separation in ATC-controlled airspace:

Cruise Flight level change TMA

• TIMEFRAME 2001-2005 2005-2010 2010-2015 2015-2020





transfer • Surveillance: Radar coverage No radar coverage TIS-B ADS-B CWP HMI with aircraft







Flight crew



Flight crew

ICAO A B C D E F H


• RVSM: Yes No



Tactical controller









AIRCRAFT SEQUENCING

CONFLICT RESOLUTION STRATEGY

CO-ORDINATION




Tactical controller








Flight crew







ciency and flexibi-lity Decrease controller





• SECURITY


• AREAS:


• ELEMENTS:

Boundaries (space and time) Entry and exit points Transition zones Vertical Descent/ Ascent buffer zone (for emergencies) Special areas and alternative routes Terrain topo-graphy Atmospheric conditions

• GEOGRAPHICAL








AIRBORNE Redundancy





resolution system • Navigation: GNSS with augmen-

tation FMS 4D RNAV RNP1 Flight data system Automatic management





11. “NATS_LONGITUDINAL_STATION_KEEPING”. TOWARDS AN OPERATIONAL SCENARIO FOR LONGITUDINAL STATION KEEPING: AN ASAS APPLICATION Validation Technique: Not Defined ASAS CATEGORY: Airborne Separation Scenario ID: NATS_Longitudinal_Station_Keeping Project: R&D REPORT 9872 Flight crew is responsible for separation assurance from a target aircraft, with limits in time, distance and scope. Controller retains all other separation responsibility. Organisation: NATS Creation Date: Nov/1998





TECHNOLOGY











COMPLEXITY




Tactical controller






Accept delegation on separation as-surance responsi-bility





restrictions

• TIMEFRAME 2001-2005 2005-2010 2010-2015 2015-2020 Perform separation

assurance from des-ignated aircraft


• AIRCRAFT TYPE:



transfer • Surveillance: Radar coverage TIS-B ADS-B CWP HMI with aircraft equipment, ID and delegation status Controller assistance position tool Sequencing tool Separation monitoring





Tactical controller




ICAO A B C D E F H


• RVSM: Yes No








Planning controller

• FLIGHT




Planning controller




Tactical controller





• EQUIPMENT



AIRCRAFT SEQUENCING








Flight crew









length Improve flow








• SECURITY


• AREAS:


• ELEMENTS:


• GEOGRAPHICAL







AIRBORNE Redundancy


• Surveillance: Mode-S TCAS II/ETCAS Audio/visual alerts Traffic information processing Surveillance data








12. “NLR_BASIC_CRUISE_FF”. BASIC CRUISE FREE FLIGHT SCENARIO, NLR-NASA ASAS Validation Technique: Real Time Simulation ASAS CATEGORY: Airborne Self-separation Scenario ID: NLR_Basic_Cruise_FF Project: NLR-NASA ASAS Flight crews are responsible for separating their aircraft from all surrounding traffic under specific conditions and in specified airspace. Organisation: NLR-NASA Creation Date: TBD





TECHNOLOGY









COMPLEXITY Broadcast surveillance data





restrictions • SEPARATION: Time Distance Tolerances Co-ordinate transfer





Flight crew




• Airborne self separation in ATC-controlled airspace: Cruise Flight level change TMA

• TIMEFRAME 2001-2005 2005-2010 2010-2015 2015-2020






transfer • Surveillance: Radar coverage No radar coverage TIS-B ADS-B CWP HMI with air-craft







Flight crew



Flight crew

ICAO A B C D E F H


• RVSM: Yes No



Tactical controller



• Airborne self separation in segregated en-route airspace

Cruise TMA






AIRCRAFT SEQUENCING

CONFLICT

RESOLUTION STRATEGY

CO-ORDINATION




Tactical controller








Flight crew















• SECURITY


• AREAS:


• ELEMENTS:

Boundaries (space and time)

Entry and exit points Transition zones Vertical Descent/

Ascent buffer zone (for emergencies) Special areas and

alternative routes Terrain topography Atmospheric








AIRBORNE Redundancy





resolution system • Navigation:

GNSS with augmen-tation

FMS 4D RNAV RNP1 Flight data system Automatic management





13. “NLR_AUTONOMOUS_AIRCRAFT_TMA”. AUTONOMOUS AIRCRAFT IN TMA Validation Technique: Real Time Simulation ASAS CATEGORY: Airborne Self-separation Scenario ID: NLR_Autonomous_Aircraft_TMA Project: NLR ASAS Flight crews are responsible for separating their aircraft from all surrounding traffic under specific conditions and in specified airspace. Organisation: NLR Creation Date: TBD





TECHNOLOGY



















Flight crew





• TIMEFRAME 2001-2005 2005-2010 2010-2015 2015-2020













Flight crew



Flight crew

ICAO A B C D E F H


• RVSM: Yes No



Tactical controller









AIRCRAFT SEQUEN-CING

CONFLICT

RESOLUTION STRATEGY

CO-ORDINATION




Tactical controller








Flight crew















• SECURITY


• AREAS:


• ELEMENTS:


Entry and exit points Transition zones Vertical Descent/


alternative routes Terrain topo-

graphy Atmospheric








AIRBORNE Redundancy












14. “CENA_ACP98”. ASAS CROSSING PROCEDURE Validation Technique: Fast Time Simulation ASAS CATEGORY: Airborne Separation Scenario ID: CENA_ACP98 Project: ASAS Crossing Procedure (ACP) Flight crew is responsible for separation assurance from a target aircraft, with limits in time, distance and scope. Controller retains all other separation responsibility. Organisation: CENA Date: 08/1998





TECHNOLOGY











COMPLEXITY




Tactical controller







Flight crew Flight crew • ASAS crossing procedure in en-route airspace:

Cruise




restrictions

• TIMEFRAME 2001-2005 2005-2010 2010-2015 2015-2020



• AIRCRAFT TYPE:










Tactical controller




ICAO A B C D E F H

FAA Heavy Medium

Turboprop Medium

Turbojet Light

• RVSM: Yes No








Planning controller

• FLIGHT




Planning controller




Tactical controller





• EQUIPMENT



AIRCRAFT SEQUENCING

CONFLICT

RESOLUTION STRATEGY

CO-ORDINATION







Flight crew









length Improve flow








• SECURITY


• AREAS:


• ELEMENTS:


• GEOGRAPHICAL







AIRBORNE Redundancy



processing Surveillance data pro-cessing Spacing function pro-


tation FMS Automatic separation management (connec-tion with FGCS)




15. “CENA_ASAS_MBB99”. THEORETICAL ASSESSMENT OF SECTOR CAPACITY DUE TO ASAS CONCEPT Validation Technique: Analytical ASAS CATEGORY: Airborne Separation Scenario ID: CENA_ASAS_MBB99 Project: Theoretical assessment of sector capacity due to ASAS concept Flight crew is responsible for separation assurance from a target aircraft, with limits in time, distance and scope. Controller retains all other separation responsibility. Organisation: CENA Date: 13/07/1999





TECHNOLOGY











COMPLEXITY




Tactical controller











restrictions

• TIMEFRAME 2001-2005 2005-2010 2010-2015 2015-2020 Perform separation

assurance from des-ignated aircraft


• AIRCRAFT TYPE:










Tactical controller




ICAO A B C D E F H


• RVSM: Yes No








Planning controller

• FLIGHT




Planning controller




Tactical controller





• EQUIPMENT



AIRCRAFT SEQUENCING

CONFLICT

RESOLUTION STRATEGY

CO-ORDINATION







Flight crew









length Improve flow








• SECURITY


• AREAS:


• ELEMENTS:


• GEOGRAPHICAL







AIRBORNE Redundancy




cessing Spacing function pro-







16. “UNIV_GLASGOW_COAST”. ASAS CO-OPERATIVE AND NON CO-OPERATIVE FFA OPERATIONS Validation Technique: Fast Time Simulation ASAS CATEGORY: Airborne Traffic Situational Awareness Scenario ID: Univ_Glasgow_COAST Project:Strategic/Tactical ASAS STUDY The flight crew’s knowledge of the surrounding traffic situation is enhanced and their decision process is improved. No responsibility transfer. Organisation: ATM Research Group University of Glasgow Date: 1999/2000





TECHNOLOGY




• FLIGHT RULES: IFR VFR New rules Manage surveillance

data Tactical controller Technology

Tactical controller




Tactical controller

IN THE AIR • Enhanced Visual Acquisition (EVA):

Cruise Flight level change

COMPLEXITY




• AIRCRAFT TYPE: • Enhanced Visual Approaches: Approach



Tactical controller


Voice Data link

• Surveillance: Radar coverage Radar information processing TIS-B ADS-B CWP HMI with aircraft ID





Planning controller

ICAO A B C D E F H

FAA Heavy Medium Turboprop Medium Turbojet Light • RVSM:

Yes No



Planning controller

• Enhanced “See and Avoid”: Cruise Flight level change



Tactical controller



Tactical controller

• EQUIPMENT TYPE: Equipped Unequipped Mixed % equipped aircraft





Tactical Controller Planning controller Flight crew

• Enhanced Traffic Information Broad-cast by Aircraft (E-TIBA): Cruise Flight level change Approach

• RESTRICTIONS: Applicable in all

types of airspace and also on the airport surface Capacity/flow

restrictions


• AREAS:


• ELEMENTS:

Routes Waypoints Flight levels Sectors Descent/Ascent Special areas and alternative routes Terrain topo-graphy

Atmospheric conditions

• GEOGRAPHICAL


• FLIGHT SCHEDULE Time Aircraft ID Aircraft model Equipment Trajectory

ATC FIS TIS-B APP Alert Service GNSS ATFM Performance

Management New Services

AIRCRAFT SEQUENCING

CONFLICT

RESOLUTION STRATEGY

CO-ORDINATION


Use TCAS, if ins-talled (not for ASAS only as safety back-up)


AIRBORNE • Communications:

Voice Data link

• Surveillance: Mode-S TCAS II/ETCAS Audio/visual alerts Traffic informa-tion


processing • Navigation:

GPS FMS



TWR controller Flight crew Technology

TWR controller Flight crew

Manage surveil-lance data

TWR controller Manage

TWR controller

• TIMEFRAME 2001-2005 2005-2010 2010-2015 2015-2020 Broadcast surveil-

lance data TWR controller Flight crew Technology

TWR controller

Perform separation assurance from designated aircraft

TWR controller TWR controller


Voice Data link

• Surveillance: SMGCS A-SMGCS CWP HMI with aircraft

ID • ATM

Planning Automation



TWR controller






TWR controller

ON THE GROUND • Improved taxi/runway occupancy

awareness: On the ground

• SAFETY Decrease risk of

faults in aircraft identification

Improve safety Increase pilot’s

situational awareness Reduce runway in-

cursions and colli-sions Decrease number of


• CAPACITY Enhance approaches Increase efficiency

of visual procedures Improve airport

surface operations • ECONOMICS • ENVIRONMENT • SECURITY

• AREAS: Airport

• ELEMENTS:

Airport layout Terrain topo-graphy Weather condi-tions

• AIRPORT CATE-

GORY: Cat I Cat II Cat IIIa Cat IIIb

FIS Surface Control Surface Guidance


• STANDARD

PHRASE-OLOGY: Yes (define) No

AIRCRAFT

SEQUEN-CING AIRPORT USAGE




Voice Data link

• Surveillance: Mode-S

• Navigation: GPS




17. EMERALD. CLOSELY SPACED PARALLEL APPROACHES IN INSTRUMENTAL METEOROLOGICAL CONDITIONS Validation Technique: Not Applicable ASAS CATEGORY: Airborne Separation Scenario ID: EMERALD_Close_Spaced_Paral_Appr Project: EMERALD Flight crew is responsible for separation assurance from a target aircraft, with limits in time, distance and scope. Controller retains all other separation responsibility. Organisation: DERA/CENA/SEXTANT/Thomson/Sofreavia Creation Date: 10/1998





TECHNOLOGY











COMPLEXITY




Tactical controller











restrictions

• TIMEFRAME 2001-2005 2005-2010 2010-2015 2015-2020



• AIRCRAFT TYPE:




transfer • Surveillance:

Radar coverage TIS-B ADS-B CWP HMI with air-craft


Controller assistance position tool

Sequencing tool Separation monitoring





Tactical controller




ICAO A B C D E F H


• RVSM: Yes No








Planning controller

• FLIGHT




Planning controller




Tactical controller





• EQUIPMENT



AIRCRAFT SEQUENCING








Flight crew








Increase pilot’s confidence

• CAPACITY Increase capacity Increase sector

length Improve flow








• SECURITY


• AREAS:


• ELEMENTS:


• GEOGRAPHICAL







AIRBORNE Redundancy





cessing • Navigation:


FMS Automatic separation





18. EMERALD. LONGITUDINAL STATION KEEPING Validation Technique: Not Applicable ASAS CATEGORY: Airborne Separation Scenario ID: EMERALD_Long_Station_Keeping Project: EMERALD Flight crew is responsible for separation assurance from a target aircraft, with limits in time, distance and scope. Controller retains all other separation responsibility. Organisation: DERA/CENA/SEXTANT/Thomson/Sofreavia Creation Date: 10/1998





TECHNOLOGY











COMPLEXITY




Tactical controller










exclusively reserved airspace

Capacity/flow restrictions

• TIMEFRAME 2001-2005 2005-2010 2010-2015 2015-2020



• AIRCRAFT TYPE:



Voice Data link Inter-sector informa-tion transfer

• Surveillance: Radar coverage TIS-B ADS-B CWP HMI with aircraft


Controller assistance position tool Sequencing tool Separation monitoring





Tactical controller




ICAO A B C D E F H


• RVSM: Yes No








Planning controller

• FLIGHT




Planning controller




Tactical controller





• EQUIPMENT



AIRCRAFT SEQUENCING








Flight crew










length Improve flow








• SECURITY


• AREAS:


• ELEMENTS:


• GEOGRAPHICAL







AIRBORNE Redundancy






tation FMS Automatic separation management (connec-tion with FGCS)




19. EMERALD. AUTONOMOUS AIRCRAFT Validation Technique: Not Applicable ASAS CATEGORY: Airborne Self-separation Scenario ID: EMERALD_Autonomous_Aircraft Project: EMERALD Flight crews are responsible for separating their aircraft from all surrounding traffic under specific conditions and in specified airspace. Organisation: DERA/CENA/SEXTANT/Thomson/Sofreavia Creation Date: 10/1997





TECHNOLOGY



















Flight crew





• TIMEFRAME 2001-2005 2005-2010 2010-2015 2015-2020







Controller assistance tool

Traffic density control & estimation tool MONA




Flight crew



Flight crew

ICAO A B C D E F H


• RVSM: Yes No



Tactical controller









AIRCRAFT SEQUENCING

CONFLICT

RESOLUTION STRATEGY

CO-ORDINATION




Tactical controller








Flight crew










ciency and flexibi-lity Decrease controller





• SECURITY


• AREAS:


• ELEMENTS:


Entry and exit points

Transition zones Vertical Descent/


alternative routes Terrain topography Atmospheric








AIRBORNE Redundancy












20. EMERTA. ENHANCED VISUAL ACQUISITION Validation Technique: Not Applicable ASAS CATEGORY: Airborne Traffic Situational Awareness Scenario ID: EMERTA_Enh_Visual_Acquis Project:EMERTA The flight crew’s knowledge of the surrounding traffic situation is enhanced and their decision process is improved. No responsibility transfer. Organisation: DERA/Sofreavia/AIRSYS/NATS Date: 05/03/2000





TECHNOLOGY




• FLIGHT RULES: IFR VFR New rules Manage surveillance

data Tactical controller Technology

Tactical controller




Tactical controller

IN THE AIR • Enhanced Visual Acquisition (EVA):

Cruise Flight level change

COMPLEXITY




• AIRCRAFT TYPE: • Enhanced Visual Approaches: Approach



Tactical controller


Voice Data link

• Surveillance: Radar coverage Radar information processing TIS-B ADS-B CWP HMI with aircraft ID





Planning controller

ICAO A B C D E F H

FAA Heavy Medium Turboprop Medium Turbojet Light • RVSM:

Yes No



Planning controller

• Enhanced “See and Avoid”: Cruise Flight level change



Tactical controller



Tactical controller

• EQUIPMENT TYPE: Equipped Unequipped Mixed % equipped aircraft





Tactical Controller Planning controller Flight crew

• Enhanced Traffic Information Broad-cast by Aircraft (E-TIBA): Cruise Flight level change Approach

• RESTRICTIONS: Applicable in all

types of airspace and also on the airport surface Capacity/flow

restrictions


• AREAS:


• ELEMENTS:

Routes Waypoints Flight levels Sectors Descent/Ascent Special areas and alternative routes Terrain topo-graphy Atmospheric conditions

• GEOGRAPHICAL


• FLIGHT SCHEDULE Time Aircraft ID Aircraft model Equipment Trajectory

ATC FIS TIS-B APP Alert Service GNSS ATFM Performance

Management New Services

AIRCRAFT SEQUENCING

CONFLICT

RESOLUTION STRATEGY

CO-ORDINATION


Use TCAS, if installed



Voice Data link



processing • Navigation:

GPS FMS





Manage surveillance data

TWR controller Manage

TWR controller

• TIMEFRAME 2001-2005 2005-2010 2010-2015 2015-2020 Broadcast surveil-

lance data TWR controller Flight crew Technology

TWR controller

Perform separation assurance from designated aircraft



Voice Data link

• Surveillance: SMGCS A-SMGCS CWP HMI with aircraft

ID • ATM

Planning Automation



TWR controller






TWR controller

ON THE GROUND • Improved taxi/runway occupancy

awareness: On the ground

• SAFETY Decrease risk of

faults in aircraft identification

Improve safety Increase pilot’s

situational awareness Reduce runway in-

cursions and colli-sions

Decrease number of voice communica-tions between con-troller and flight crew

• CAPACITY Enhance approaches Increase efficiency

of visual procedures Improve airport

surface operations • ECONOMICS • ENVIRONMENT • SECURITY

• AREAS: Airport

• ELEMENTS:

Airport layout Terrain topography Weather conditions

• AIRPORT CATE-

GORY: Cat I Cat II Cat IIIa Cat IIIb

FIS Surface Control Surface Guidance


• STANDARD

PHRASE-OLOGY: Yes (define) No

AIRCRAFT

SEQUENCING AIRPORT USAGE




Voice Data link

• Surveillance: Mode-S

• Navigation: GPS




21. EMERTA. STATION KEEPING ON APPROACH Validation Technique: Not Applicable ASAS CATEGORY: Airborne Separation Scenario ID: EMERTA_Station_Keeping_Appr Project: EMERTA Flight crew is responsible for separation assurance from a target aircraft, with limits in time, distance and scope. Controller retains all other separation responsibility. Organisation: DERA/Sofreavia/AIRSYS/NATS Creation Date: 05/03/2000





TECHNOLOGY











COMPLEXITY




Tactical controller











restrictions

• TIMEFRAME 2001-2005 2005-2010 2010-2015 2015-2020



• AIRCRAFT TYPE:



transfer • Surveillance:

Radar coverage TIS-B ADS-B CWP HMI with air-craft


position tool Sequencing tool Separation monitoring tool Recovering tool




Tactical controller




ICAO A B C D E F H


• RVSM: Yes No








Planning controller

• FLIGHT




Planning controller




Tactical controller





• EQUIPMENT



AIRCRAFT SEQUENCING








Flight crew










length Improve flow








• SECURITY


• AREAS:


• ELEMENTS:


• GEOGRAPHICAL







AIRBORNE Redundancy









CARE/ASAS/Activity 2: Validation Framework WP 1 ...

Documents

Transcript of CARE/ASAS/Activity 2: Validation Framework WP 1 ...