. Determine latest time speed change clearance can be issued to maintain required separation
. Formulate clearance for trailing aircraft to reduce speed to speed of leading aircraft
– If necessary, check desired speed with trailing aircraft [“American 123. Boston Center. Can you reduce speed to mach 0.74?”]
– Wait for response and note ability to comply [“Boston Center. American 123. Affirmative.”]
. Issue clearance [“American 123. Boston Center. Reduce speed to mach 0.74 for spacing.”]
. Initiate Wait for Acknowledgment task
Resolve Crossing Conflict
Causal Event:
. Crossing conflict identified
Controller Actions:
. Determine groundspeeds and distances of both aircraft from crossing waypoint
. Determine second aircraft to reach the crossing waypoint (subject aircraft)
. Determine mach number of subject aircraft
– Query aircraft for mach number [“American 123. Boston Center. Say mach number.”]
– Wait for response and note response contents [“Boston Center. American 123 is at mach 0.80.”]
. Formulate clearance for subject aircraft to reduce speed to resolve the conflict
– If necessary, check desired speed with aircraft [“American 123. Boston Center. Can you reduce speed to mach 0.74?”]
– Wait for response and note response contents [“Boston Center. American 123. Affirmative.”]
. Issue clearance [“American 123. Boston Center. Reduce speed to mach 0.74 for traffic.”]
. Initiate Wait for Acknowledgment task
Clear Air Turbulence Module
The relationship between the tasks involved in responding to clear air turbulence is shown in Figure D-4 and described in more detail below.
Figure D-4 Clear Air Turbulence Management Tasks
Receive PIREP
Causal Event:
. Pilot transmits CAT report [“Boston Center. American 123 is getting moderate chop at flight level 390.”]
Controller Actions:
. Update reported CAT database
Respond to Ride Information Request
Causal Event:
. Pilot requests information about ride reports at a specific altitude [Boston Center. American 123. How is the ride at flight level 350?”]
Controller Actions:
. Compare subject aircraft position and pilot query to reported CAT database
. If no relevant ride reports are available then determine if it is possible to query other aircraft
– If other aircraft are in the area, query other aircraft [“Delta 46. Boston Center. How is your ride?”]
– Wait for response and note information [“Boston Center. Delta 46 has been getting moderate turbulence for the last 10 miles.”]
– Update CAT database as appropriate
. Send relevant information to subject aircraft [“American 123. Boston Center. Several reports of moderate chop at flight level 350 for the next 30 miles.”]
Check for Better Ride
Causal Event:
. Pilot asks the controller to identify altitudes with a better ride [Boston Center. American 123. Can you find us some smoother air?”]
Controller Actions:
. Compare subject aircraft position to reported CAT database
. Send relevant information to subject aircraft [“American 123. Boston Center. Smooth air reported at FL 350”]
Evaluate Requested Maneuver
Causal Event:
. Pilot request for vertical maneuver to avoid CAT [“Boston Center. American 123. Request climb to FL350 for smooth air.”]
Controller Actions:
. Perform Sector Scan task to update aircraft positions and speeds
中国航空网 www.aero.cn
航空翻译 www.aviation.cn
本文链接地址：DEVELOPMENT OF FAST-TIME SIMULATION TECHNIQUES IN THE NATION(50)
