Analysis of Conflict Resolution Methods for Manned and Unmanned Aviation Using Fast-Time Simulations

Research output: Chapter in Book/Conference proceedings/Edited volumeConference contributionScientificpeer-review

5 Citations (Scopus)
86 Downloads (Pure)


In the coming years, aviation will have to cope with an increase in the number of aircraft, and of drones purchased in the open market. The human intervention of Air Traffic Management (ATM) will be overburden with guaranteeing flight safety with hundreds of manned aircraft and Unmanned Aerial Vehicles (UAVs) operating simultaneously. Conflict Resolution (CR) models are under research, aiming at relieving the workload of ATM services and to enable UAVs to fly safely in the civil airspace. However, these are tested using different simulation tools and scenarios, making it impossible for a direct comparison. This paper compared the performance of commonly used CR methods under the same conditions both for manned and unmanned aviation. Disparities with previously conducted research using different scenarios show the importance of creating a standardized simulation library. Additionally, under the traffic scenarios considered, velocity obstacles (VO) based methods obtained a better performance safety-wise.
Original languageEnglish
Title of host publication9th SESAR Innovation Days 2nd – 5th December 2019
Number of pages8
Publication statusPublished - 2019
EventSIDs2019: 9th SESAR Innovation Days - Athens, Greece
Duration: 2 Dec 20195 Dec 2019
Conference number: 9

Publication series

NameSESAR Innovation Days


ConferenceSIDs2019: 9th SESAR Innovation Days
Abbreviated titleSIDs2019


  • Conflict
  • Detection and Resolution (CD&R)
  • Air Traffic Management (ATM)
  • U-Space
  • BlueSky ATM Simulator
  • Velocity Obstacles (VO)
  • Self-Separation
  • Conflict Detection and Resolution (CD&R)


Dive into the research topics of 'Analysis of Conflict Resolution Methods for Manned and Unmanned Aviation Using Fast-Time Simulations'. Together they form a unique fingerprint.

Cite this