曝光台 注意防骗
网曝天猫店富美金盛家居专营店坑蒙拐骗欺诈消费者
Wait for Acknowledgment. When a radio message is sent to an aircraft for any reason, the controller waits for acknowledgment to ensure the message was received and understood. If an acknowledgement is not received within a short time, the controller attempts to contact the aircraft and repeat the message.
Sector Scan. This task represents the process by which the controller scans the radar display and updates his or her mental picture of aircraft positions, courses, altitudes, and speeds.
Conflict Check. The controller must periodically check for potential conflicts (loss of minimum separation) between aircraft within the sector. For this specification, it was assumed that this task is accomplished by comparing the planned flight path for each aircraft to those for all other aircraft in the sector. If the planned flight paths are projected to lose separation, then a potential conflict is identified. Conflicts may be of two types, overtaking and crossing. If a potential conflict is identified, then the conflict resolution module is initiated in order to determine the action required to prevent the conflict from actually occurring.
Flight Plan Deviation Check. In addition to checking for conflicts between aircraft, the controller must check periodically to ensure that aircraft are maintaining their approved flight paths. This is done by comparing the aircraft position, heading, speed, altitude, and climb/descent rate obtained from the most recent sector scan to the planned flight path as represented in the controller’s intended plan. If a deviation is identified, then the controller must determine how to resolve it, as described in the Resolve Deviation task below.
Exiting Aircraft Check. The controller must also identify aircraft that are approaching the sector boundary and must therefore be handed off to the downstream sector. The controller compares each aircraft’s position and course to the known sector boundary. If an exiting aircraft is identified then a handoff is performed. The handoff is performed by alerting the next sector through an input to the computer automation system, which flashing the aircraft data block on the radar display, and by sending a message to the subject aircraft to change frequencies and contact the downstream controller.
Resolve Deviation. Upon identifying an aircraft that is deviating from its approved flight path, the controller must formulate an appropriate response. If the deviation is in heading, altitude, or speed, the controller resends the previous clearance and instructs the aircraft to return to its assigned flight path. If the deviation is from the assumed climb/descent rate, the controller needs to check whether the aircraft’s observed flight path will generate any unanticipated conflicts and react accordingly.
Conflict Resolution Tasks
Resolve Overtaking Conflict. For this version of the specification, it is assumed that overtaking conflicts can only be resolved by reducing the speed of the trailing aircraft. When a potential overtaking conflict is identified, the controller checks the available response time from the current speed information, and may request additional information (such as the current Mach number) from the aircraft. The controller then instructs the trailing aircraft to slow to the speed of the leading aircraft at an appropriate time to ensure that the minimum required separation is maintained.
Resolve Crossing Conflict. For this version of the specification, it is assumed that overtaking conflicts can only be resolved by changing the speed of one of the aircraft. When a potential crossing conflict is identified, the controller determines the appropriate speed change required of one of the aircraft to avoid the conflict and issues this clearance.
CAT Tasks
Receive PIREP. When PIREPs are received, the controller acknowledges the report and adds the information to his or her mental model of turbulence conditions in the sector.
中国航空网 www.aero.cn
航空翻译 www.aviation.cn
本文链接地址：
DEVELOPMENT OF FAST-TIME SIMULATION TECHNIQUES(35)
