CARE/ASAS Activity 3: ASM workshop Br

1
CARE-ASAS Activity 3 ASMAutonomous Aircraft
OSED
2
Objectives and Tasks

• Objectives
• To provide relevant information for safety
  assessment
• RD work, not any implementation objectives
• Tasks
• Description of the operating environment and
  autonomous aircraft operations

3
OSED overview

• Operating environment characteristics
• Airspace and Traffic characteristics
• Application Description
• Expected benefits and constraints, human factors
  issues
• Operating method without and with ASAS
• Functional characteristics
• Capturing time constraints
• Information exchanges
• Exception handling (human and system failures and
  emergency/contingency procedures)
• Training

4
Airspace characteristics

• FFAS surrounded by MAS only
• Low/medium density and complexity
• 4D RNAV (at least RNP1) RVSM applied
• Segregated airspace Only suitably equipped
  aircraft authorised (ADS-B, CDTI, CDR
  capabilities) with qualified flight crew
• Airborne self-separation
• No fixed routes aircraft fly their user
  preferred routes
• Generic airspace

5
Airspace characteristics
6
Air Traffic Services

• No ATC support within FFAS
• New service FFAS flow management
• 3 levels
• Strategic / Pre-tactical / Tactical flow
  management
• Role
• To define an orderly flow of traffic
• To manage traffic global and local densities and
  traffic complexity to maintain them at
  appropriate level (E.g. Density shall remain
  under a maximum value)

7
Operations within FFAS (1/2)

• Three main phases
• Surrounding traffic surveillance and monitoring
• Flight crew aware of surrounding traffic using
  its CDTI
• Conflict detection and display
• Detection of conflicts occurring within CDR look
  ahead time (10min)
• Aural and visual alerts
• Display of traffic situation awareness and
  conflict information

8
Operations within FFAS (2/2)

• Conflict resolution and implementation
• Priority assigned to determine manoeuvring
  aircraft
• Cross check and comparison of own and conflicting
  priorities done by flight crew
• Flight crew has not priority
• Manual or automatic solution computation
• Flight crew has priority
• Maintain its 4D trajectory until the other
  aircraft has resolve the conflict.
• Both flight crews Monitoring of resolution
  manoeuvre

9
Operations within FFAS
Action and function
Message
10
Airborne functionality (1/3)

• Airborne surveillance
• Based on ADS-B and own navigation data
• Airborne conflict detection and resolution
• Conflict detection
• Based on surveillance function output and used
  aircraft state and intent information
• ASAS alerting system
• Three increasing levels Low / Medium / High
• Aural and visual alarms

11
Airborne functionality (2/3)

• Conflict resolution
• Manual solution
• Automatic solution
• Solver based on a priority rule based algorithm
  (EFR rules)
• Produce conflict free trajectories (two lateral
  ones and a vertical one otherwise) taking into
  account conflicting aircraft and all surrounding
  aircraft trajectories
• Integrate external constraints (e.g. not create
  high density zones, weather conditions, low cost)
• After solution computation, flight plan
  automatically updated in the FMS

12
Airborne functionality (3/3)

• HMI
• CDTI
• Display of
• Surrounding traffic,
• Conflict detection information
• Priority determination
• Conflict resolution
• ACAS display
• Priority given to ACAS display
• Others
• E.g. weather information

13
Emergency procedures

• Own aircraft
• Broadcast emergency messages (containing
  estimated positions) on VHF (and via ADS-B using
  the priority status field, if ADS-B emitter
  operating)
• Contact by radio previous or receiving controller
  to obtain the VHF frequency of the MAS sector
  below
• Join the vertical buffer zone below the FFAS
• Contact controller of the MAS sector
• Controller of the MAS below
• Provide solution to the aircraft in emergency
• Other aircraft
• Assure separation with the aircraft in emergency
  using voice position reports or ADS-B messages

14
MAS/FFAS transition
15
FFAS/MAS transition