APPENDIX D:  CONTROLLER TASK SPECIFICATION
This appendix presents a detailed specification of the tasks performed by an en-route sector controller, with particular attention to tasks involved in responding to the occurrence of clear air turbulence (CAT) within the sector.  These tasks have been grouped into the three modules described in Chapter V:  Basic Sector Management, Conflict Resolution, and Clear Air Turbulence.
The relationships among these three modules are shown in Figure D-1.
Figure D-1  Relationships among Primary Functional Modules

Flight Path Representation
The controller maintains a mental representation of the projected flight path of each aircraft expressed in terms of a sequence of waypoints with associated altitudes and estimated arrival times.  The controller will need to maintain a distinction between the cleared or intended flight path, based on the clearances issued to the aircraft, and the actual or expected flight path, based on the surveillance information obtained by the controllers.
Basic Sector Management Module
The relationships among the tasks involved in sector management are shown in Figure D-2 and described in more detail below.
Figure D-2  Sector Management Tasks

 
Sector Management
Causal Event:
. Continuous task

Controller Actions:
. Determine time since last Sector Scan, initiate Sector Scan if necessary

. For each aircraft in sector, initiate Conflict Check task

. For each aircraft in sector, initiate Flight Plan Deviation Check task

. For each aircraft in sector, determine distance to sector exit waypoint and initiate Exiting Aircraft Check task if necessary

Respond to Radio Message
Causal Event:
. Radio message received

Controller Actions:
. Identify type of radio message

. Initiate appropriate task in response

Receive Handoff
Causal Event:
. Aircraft approaches sector, handoff initiated (target data block flashes) by upstream sector

Controller Actions:
. Create a new entry in the sector aircraft list with Aircraft ID and status

. Note aircraft position and speed and add to the data in the sector aircraft list

. Obtain aircraft type and flight plan from flight progress strip (FPS) and link data to sector aircraft list entry (FPS message sent as part of handoff procedure)

. Perform Conflict Check task for new aircraft

Issue Handoff Clearance
Causal Event:
. Aircraft handoff call received from subject aircraft  [“Boston Center.  American 123 with you level at flight level 330.”]

Controller Actions:
. Perform Turbulence Check task for new aircraft

. Issue clearance and turbulence alert if necessary [“American 123.  Boston Center.  Maintain flight level 330.” or “American 123.  Boston Center.  Maintain flight level 330.  Be advised reports of moderate turbulence in 10 miles.”]

. Initiate Wait for Acknowledgement task

Turbulence Check
Causal Event:
. Aircraft handoff call received

Controller Actions:
. Compare subject aircraft position and planned flight path to prior CAT reports

. Depending on location and severity of prior CAT reports, formulate turbulence alert to be included with the handoff clearance if required

Wait for Acknowledgement
Causal Event:
. Clearance or query issued to aircraft

Controller Actions:
. Wait 10 seconds after issuing message

. If acknowledgement has not been received, reissue message and reinitiate Wait for Acknowledgment task

. End task when acknowledgement received

Sector Scan
Causal Events:
. Receive Handoff task
　
中國航空網(wǎng) m.k6050.com
航空翻譯 www.aviation.cn
本文鏈接地址：DEVELOPMENT OF FAST-TIME SIMULATION TECHNIQUES(48)