Hostname: page-component-74656f9884-2dmjx Total loading time: 0 Render date: 2026-11-07T03:20:03.864Z Has data issue: false hasContentIssue false

Strategic Conflict Detection and Resolution Using Aircraft Intent Information

Published online by Cambridge University Press:  01 December 2009

Marco Porretta*
Affiliation:
(Imperial College London)
Wolfgang Schuster
Affiliation:
(Imperial College London)
Arnab Majumdar
Affiliation:
(Imperial College London)
Washington Ochieng
Affiliation:
(Imperial College London)
Rights & Permissions [Opens in a new window]

Abstract

A number of automated decision support tools will be required in the future air traffic management system to enable continued provision of safe and efficient services in increasingly congested skies. In particular, Conflict Detection and Resolution (CDR) tools should allow for early detection of possible conflicts and propose safe and efficient resolution manoeuvres to avoid loss of separation. However, current approaches in the open literature not only use different levels of aircraft intent information but also make a number of assumptions on models of aircraft motion. Furthermore, information relevant to aircraft performance is often not considered with the consequence of the resulting resolution strategies being potentially unreliable. This paper presents an enhanced, strategic, pairwise, performance-based and distributed CDR algorithm. It accounts for the weaknesses of current approaches by using the maximum level of aircraft intent information together with a novel trajectory prediction model. Numerical results for representative conflict scenarios show that the proposed CDR method is able to generate conflict-free trajectories for participating aircraft while taking into account the actual aircraft capabilities to perform the recommended resolution manoeuvres.

Information

Type
Research Article
Copyright
Copyright © The Royal Institute of Navigation 2009
Figure 0

Figure 1. Basic framework for the proposed trajectory prediction model.

Figure 1

Figure 2. The CFT determination process for a generic aircraft, k: square blocks denote processes; diamond blocks indicate decisions; parallelogram blocks specify data which may be modified during the CFT computation procedure; cylinder blocks denote data which are not modified; full line connectors indicate algorithm execution flow; and dashed line connectors specify data flow.

Figure 2

Figure 3. – CR stage: input and output.

Figure 3

Figure 4. The pairwise CR algorithm: square blocks denote processes; diamond blocks indicate decisions.

Figure 4

Figure 5. Examples relevant to the FS Harmonisation stage. Vertical profile (right): peaks and valleys are eliminated through suitable modifications for the altitudes associated with TCP2, TCP4 and TCP6. Horizontal profile (left): the TCP3 leads the aircraft back to the sector entry point and is then removed from the FS; the aircraft will fly directly from the TCP2 to the TCP4.

Figure 5

Figure 6. – Flowchart of the RTCPs determination process.

Figure 6

Figure 7. Absolute and intruder relative systems.

Figure 7

Figure 8. The protected zone in the intruder RS: Top view (Left) and side view (Right).

Figure 8

Table 1. Scheme used for conflict-case identification.

Figure 9

Figure 9. A possible strategy to solve an example of conflict-case D: Top view (Left) and side view (Right).

Figure 10

Figure 10. Super conflict in the horizontal plane: Horizontal trajectories.

Figure 11

Figure 11. Super conflict in the horizontal plane: Minimum horizontal separation over time.

Figure 12

Figure 12. Wall conflict in the horizontal plane: Horizontal trajectories.

Figure 13

Figure 13. Wall conflict in the horizontal plane: Minimum horizontal separation over time.

Figure 14

Table 2. Super conflict in the vertical plane.

Figure 15

Figure 14. Super conflict in the vertical plane: Horizontal trajectories.

Figure 16

Figure 15. Super conflict in the vertical plane: Vertical trajectories.

Figure 17

Table 3. Super conflict in the vertical plane.

Figure 18

Figure 16. Wall conflict in the vertical plane: Horizontal trajectories.

Figure 19

Figure 17. Wall conflict in the vertical plane: Vertical trajectories.