+ All Categories
Home > Documents > Advanced Safe Separation Technologies and Algorithms (ASSTAR) Project ASAS-TN2 Workshop #1 Malmö 26...

Advanced Safe Separation Technologies and Algorithms (ASSTAR) Project ASAS-TN2 Workshop #1 Malmö 26...

Date post: 18-Dec-2015
Category:
Upload: walter-james
View: 218 times
Download: 0 times
Share this document with a friend
Popular Tags:
30
Advanced Safe Separation Technologies and Algorithms (ASSTAR) Project ASAS-TN2 Workshop #1 Malmö 26 th -28 th September 2005 ASSTAR is a Specific Targeted REsearch Project (STREP) sponsored by The European Commission – Directorate General RTD - within the 6th Framework Programme (contract number AST4-CT-2004-516140). The programme started in January 2005 and has a duration of 30 months.
Transcript

Advanced Safe Separation Technologies and Algorithms (ASSTAR) Project

ASAS-TN2 Workshop #1Malmö

26th-28th September 2005

ASSTAR is a Specific Targeted REsearch Project (STREP) sponsored by The European Commission – Directorate General RTD - within the 6th Framework Programme (contract number AST4-CT-2004-516140).

The programme started in January 2005 and has a duration of 30 months.

page 2ASAS-TN2 Workshop#1, 26-28 September 2005

Contents

Project Overview

Work Package 1: Concept and Scenario Refinement

Separation Applications

– Pass Behind/In-front (ASEP-LC&P)

– Pass Above/Below (ASEP-VC&P)

– Enhanced Flight Level Change Procedure (ASEP-FLC)

– In Trail Follow (ASEP-ITF)

Self-Separation Applications

– Self Separation on an Organised Track System (SSEP-OTS)

Project Overview

page 4ASAS-TN2 Workshop#1, 26-28 September 2005

Consortium Partners

Consortium Partners

BAE Systems (UK)

(Project Co-ordinator)

National AerospaceLaboratory – NLR (NL)

Sistemi Innovativi per ilControllo del TrafficoAereo - Sicta (IT)

Direction des Services dela Navigation Aérienne

- DSNA (FR)

Euro Telematik (GE) University of Glasgow(UK)

Thales Avionics (FR) EUROCONTROLExperimental Centre (FR)

National Air TrafficServices - NATS (UK)

TechnologicalEducational Institute ofPiraeus (GR)

HELLAS JET (GR) University of Zilina (SL)

EUROCONTROL

page 5ASAS-TN2 Workshop#1, 26-28 September 2005

Project Overview

ASSTAR is a EC Framework 6 STREP

– Crossing and Passing Applications

– Delegation of separation responsibility

– Radar and Oceanic Environments

Research objectives support introduction in 2010+ time frame

– ASAS manoeuvre design and execution

– Definition of supporting procedures

– Air & Ground installation & implementation issues

– Benefits

– Safety assessment

– Impact on Regulations

page 6ASAS-TN2 Workshop#1, 26-28 September 2005

Project Objectives

Establish a number of well-defined ASAS Package 2/3 applications

Reach a common endorsement between the airlines and ANSPs of the proposed applications

Regular project user workshops are planned to ensure the involvement of key users at the detailed level

Public User Forums to achieve wider dissemination and elicit responses from a broad representation of the Air Transport community

page 7ASAS-TN2 Workshop#1, 26-28 September 2005

Work Package structure

WP1Concepts & Scenarios

WP3Oceanic

Simulations

WP2C&P in Radar

Airspace

WP5Implementation &Infrastructure

WP4Procedure Definition

WP6Safety

Assessment

WP7

Dissemination & Exploitation

User Forums

Package 2Applications &Procedures

Cost BenefitAnalysis & Results

Regulatory Impact

Work Package 1: Concept and Scenario Refinement(Work in Progress)

page 9ASAS-TN2 Workshop#1, 26-28 September 2005

Work Package 1

Define a set of applications and environments (scenarios) for the programme

Develop Operational Requirements Documents

– Separate sections for each application

Initial benefits review

Implementation/architecture options

Preliminary risk/safety analysis

page 10ASAS-TN2 Workshop#1, 26-28 September 2005

Operational Environment

page 11ASAS-TN2 Workshop#1, 26-28 September 2005

Application Scenario Environment PO-ASASCategory

Lateral Crossing Co-Altitude Pass Behind Radar / Enroute Separation

Lateral Crossing Co-altitude Pass In front Radar / Enroute Separation

Lateral Crossing Climbing Pass Behind Radar / Enroute Separation

Lateral Crossing Descending Pass Behind Radar / Enroute Separation

Vertical Crossing Climb above Radar / Enroute Separation

Vertical Crossing Descend below Radar / Enroute Separation

Lateral Passing Co-altitude overtake Radar / Enroute Separation

Vertical Crossing Opposing Traffic Radar / Enroute Separation

Vertical Crossing Flight Level Change Oceanic OTS / UPR Separation

Longitudinal Spacing Remain Behind Oceanic OTS / UPR Separation

Vertical Crossing In Trail Climb Oceanic OTS / UPR Separation

Vertical Crossing Leading Climb Oceanic OTS / UPR Separation

Vertical Crossing In trail Descent Oceanic OTS / UPR Separation

Vertical Crossing Leading descent Oceanic OTS / UPR Separation

Lateral Passing Co-altitude overtake Oceanic OTS Separation

Self Separation Oceanic Track System Oceanic OTS Self Separation

Self Separation Free-Flight Oceanic or Remote Self Separation

Applications, Scenarios & Environments

1 3 2 2

4 1 3

2

page 12ASAS-TN2 Workshop#1, 26-28 September 2005

Scenario & Application Priorities

Radar Environment

– Lateral Crossing Application (ASEP-LC&P)

Pass Behind (Co-altitude and descending/climbing)

Pass In-front

– Vertical Crossing Application (ASEP-VC&P)

Pass Above/Below

Non-Radar Environment

– Enhanced Flight Level Change Procedure (ASEP-FLC)

– Self-Separation on an OTS (SSEP-OTS)

– In Trail Follow (ASEP-ITF)

Separation Applications

page 14ASAS-TN2 Workshop#1, 26-28 September 2005

Separation responsibilities

Ground Air

Air Traffic Control

Conflict Detection

Situation Awareness

ExecuteConflict Prevention

Delegation ofSeparation

SelectConflict Resolution

Strategy

End Delegation

page 15ASAS-TN2 Workshop#1, 26-28 September 2005

Impact on Roles and ProceduresImpact on Roles and Procedures

Controller is responsible for:

– Conflict detection

– Initiation of the application

– Separation of other traffic from involved aircraft

Air crew is responsible for:

– Selection of conflict resolution strategy

– Execution of conflict resolution strategy

– Informing controller when conflict has been resolved

New procedures will be required

– Additional training for both controllers and flight crews

page 16ASAS-TN2 Workshop#1, 26-28 September 2005

ASEP-LC&P: Pass Behind

Targetaircraft

Clearanceaircraft Manoeuvre

Change Point

Closestpoint of

approach

Turning point route

End ofdelegation

page 17ASAS-TN2 Workshop#1, 26-28 September 2005

ASEP-LC&P: Pass behind

End ofdelegation

ManoeuvreChange Points

Targetaircraft

Clearanceaircraft

Closest pointof approach

Offset route

page 18ASAS-TN2 Workshop#1, 26-28 September 2005

ASEP-VC&P

RVSM entry / exit points

RVSM transition airspace

RVSM airspace Non-RVSM airspace

FL410

FL400

FL390

FL380

FL370

FL360

FL350

FL340

FL330

FL320

FL310

FL300

FL290

FL410

FL400

FL390

FL380

FL370

FL360

FL350

FL340

FL330

FL320

FL310

FL300

FL290

page 19ASAS-TN2 Workshop#1, 26-28 September 2005

Crossing & Passing

Based upon Package 1 application ASPA-C&P

– Separate vertical and horizontal separation applications

ASEP-LC&P (Lateral Crossing & Passing )

ASEP-VC&P (Vertical Crossing & Passing )

Differences

– Delegation of responsibility for separation

Similarities

– Manoeuvre types

– Application phases

page 20ASAS-TN2 Workshop#1, 26-28 September 2005

ASEP-FLC

page 21ASAS-TN2 Workshop#1, 26-28 September 2005

Enhanced Flight Level Change Procedure

Based upon Package 1 application ATSA-ITP

Differences

– Active monitoring phase during flight level change

– Aircraft are responsible for separation

Similarities

– Applicability conditions unchanged (Could be extended though)

page 22ASAS-TN2 Workshop#1, 26-28 September 2005

ASEP-ITF

page 23ASAS-TN2 Workshop#1, 26-28 September 2005

In Trail Follow

Based upon Package 1 application ASPA-S&M

Differences

– Aircraft are co-altitude in remain phase

– Aircraft are responsible for separation

– Extended duration (several hours)

– Spacing defined in minutes rather than seconds

Similarities

– Procedural termination condition - exit from track

– Merge instructions can be used to initiate spacing at track entry

Self-Separation Applications

page 25ASAS-TN2 Workshop#1, 26-28 September 2005

Self-Separation responsibilities

Ground Air

Air Traffic Control Situation Aw areness

Conflict Detection

SelectConflict Resolution

Strategy

ExecuteConflict Prevention

Delegation ofSelf-Separation

ControlMAS to SS Airspace

Transition

ControlSS Airspace to MAS

TransitionEnd Of Delegation

Flight InformationService

Status Reports

page 26ASAS-TN2 Workshop#1, 26-28 September 2005

Impact on Roles and ProceduresImpact on Roles and Procedures

Controller is responsible for:

– Transition from managed to self-separation airspace

– Transition from self-separation to managed airspace

– Provision of flight information services

Airborne domain is responsible for:

– Conflict detection

– Selection of conflict resolution strategy

– Execution of conflict resolution strategy

– Provision of flight status information

New procedures will be required

– Additional training for both controllers and flight crews

page 27ASAS-TN2 Workshop#1, 26-28 September 2005

Organised Track System

page 28ASAS-TN2 Workshop#1, 26-28 September 2005

Conflict Resolution Strategies

Vertical Profile

Ownship

Predicted PositionT minutes ahead

PredictedProtection Zone

Traffic

Horizontal Profile

Ownship

PredictedProtection Zone

Predicted PositionT minutes ahead

Traffic

Vertical Resolution

orLateral Resolution(Crossing traffic only)

Speed Resolution

page 29ASAS-TN2 Workshop#1, 26-28 September 2005

Forthcoming events

User Forum #1, April 2006

– Rome

– combined with ASAS-TN2 Workshop

User Forum #2, April 2007

– Amsterdam

– combined with ASAS-TN2 workshop

page 30ASAS-TN2 Workshop#1, 26-28 September 2005

THANK YOU

Contacts

[email protected]

[email protected]


Recommended