. Periodic scan initiated by Sector Management task

Controller Actions:
. Obtain current reported positions, altitudes and speeds for all entries on the aircraft list from sector surveillance process and add information to the entries in the aircraft list

Conflict Check
Causal Events:
. Receive Handoff task

. Periodic check initiated by Sector Management task

Controller Actions:
. Check for overtaking conflicts

. Identify entries in aircraft list on the same flight path as subject aircraft and identify preceding aircraft

. Compare speed of preceding aircraft to speed of the subject aircraft to determine if an overtaking conflict will occur (compare projected arrival times at each common waypoint to determine if a conflict will occur before both aircraft reach the waypoint)

. If a conflict will occur then initiate Resolve Overtaking Conflict task

. Check for crossing conflicts

. Identify entries in aircraft list that have crossing flight paths with the subject aircraft within conflict look-ahead time

. For crossing aircraft, determine if aircraft will lose horizontal separation while crossing

. For crossing aircraft that lose horizontal separation, determine if altitudes will be less than 1000 ft. (2000 ft. above FL 290) while horizontal separation is lost to determine if a conflict will occur

. If a conflict will occur then initiate Resolve Crossing Conflict task

Flight Plan Deviation Check
Causal Events:
. Periodic check initiated by Sector Management task

Controller Actions:
. Compare position and speed of subject aircraft to expected position and speed based on current planned flight path

. If the observed position or speed is not within a given tolerance of flight plan then initiate Resolve Deviation task

Exiting Aircraft Check
Causal Event:
. Periodic check initiated by Sector Management task

Controller Actions:
. Determine distance of subject aircraft from exiting waypoint

. If distance is within given tolerance, then perform handoff:

– Send handoff alert to downstream sector

– Send message to aircraft to change frequency  [“American 123.  Boston Center.  Change frequency and contact Boston Center on 123.4.  Good day.”]

Resolve Deviation
Causal Event:
. Deviation from flight plan detected

Controller Actions:
. Determine type of deviation (course, speed, altitude or climb/descent rate)

. If the deviation is course then instruct aircraft to return to correct course [“American 123.  Boston Center.  Turn right 15 degrees to re-intercept J42.”]

. If the deviation is speed or altitude then resend last speed or altitude clearance  [“American 123.  Boston Center. Maintain flight level 350 mach 0.76.”]

. If the deviation is climb/descent rate, then check if deviation will result in a conflict

– If the deviation will not result in a conflict then no action is required

– If the deviation will result in a conflict then replan the climb/descent and issue new clearance to subject aircraft

Conflict Resolution Module
The relationships among the tasks involved in conflict resolution are shown in Figure D-3 and described in more detail below.
Figure D-3  Conflict Resolution Tasks

Resolve Overtaking Conflict
Causal Event:
. Overtaking conflict identified

Controller Actions:
. Determine time conflict will occur

. Determine speed of leading aircraft

– Query leading aircraft for mach number and/or other flight data [“American 123.  Boston Center.  Say mach number.”]

– Wait for response and note mach number [“Boston Center.  American 123 is at mach 0.80.”]
　
中國航空網 m.k6050.com
航空翻譯 www.aviation.cn
本文鏈接地址：DEVELOPMENT OF FAST-TIME SIMULATION TECHNIQUES IN THE NATION(49)