z-logo
Premium
Efficient air traffic conflict resolution by minimizing the number of affected aircraft
Author(s) -
Idan M.,
Iosilevskii G.,
BenYishay L.
Publication year - 2010
Publication title -
international journal of adaptive control and signal processing
Language(s) - English
Resource type - Journals
SCImago Journal Rank - 0.73
H-Index - 66
eISSN - 1099-1115
pISSN - 0890-6327
DOI - 10.1002/acs.1169
Subject(s) - air traffic control , flight plan , workload , plan (archaeology) , computer science , air traffic management , order (exchange) , conflict resolution , operations research , aeronautics , transport engineering , real time computing , aerospace engineering , engineering , business , archaeology , finance , law , political science , history , operating system
The paper addresses local conflict resolution in dense air traffic scenarios. Currently, air traffic can reach a few thousands of aircraft airborne simultaneously over Europe or U.S., with predictions that it will grow significantly during the next two decades. All this traffic is expected to be organized well in advance and updated before take‐off, providing each aircraft a conflict‐free flight plan. Deviations from this plan, caused by the difference between the actual and predicted weather, equipment malfunctions, operational or airport delays, etc., may create in‐flight conflicts that will have to be resolved in a matter of minutes. Since real‐time re‐organization of the entire traffic is impractical due to high computational complexity, local re‐planning, affecting only the aircraft involved in the conflicts, is in order. In this paper we suggest a rapid local re‐planning algorithm. Its efficiency is attained by re‐computing new trajectories only for a minimal number of aircraft that resolves the conflicts. Finding optimal trajectories only for those aircraft not only reduces the computational effort, but also reduces average pilot workload. Copyright © 2010 John Wiley & Sons, Ltd.

This content is not available in your region!

Continue researching here.

Having issues? You can contact us here