13.09.2014 Views

Published Report (DOT/FAA/CT-94-36)

Published Report (DOT/FAA/CT-94-36)

Published Report (DOT/FAA/CT-94-36)

SHOW MORE
SHOW LESS

You also want an ePaper? Increase the reach of your titles

YUMPU automatically turns print PDFs into web optimized ePapers that Google loves.

Controllers also submitted a report documenting their experiences<br />

during the simulation. The controller report is included as<br />

appendix H of this report.<br />

2.3.2 Simulation Pilot Operators.<br />

SPO's operated the TGF aircraft within the various traffic<br />

scenarios. Throughout the simulation, SPO's responded to<br />

controller instructions by entering aircraft heading and altitude<br />

changes using their specialized computer keyboard and display.<br />

SPO's performed their task from the Simulation Pilot Complex in<br />

the TGF at the <strong>FAA</strong> Technical Center.<br />

2.3.3 Test Director.<br />

Simulation runs and aircraft blunders were under the direction of<br />

the simulation test director. Three individuals assumed the role<br />

of test director throughout the simulation. These individuals<br />

have extensive ATC experience and were trained to work with the<br />

CPA Prediction Tool. The test director was responsible for<br />

initiating blunders based upon the information provided by the<br />

blunder scripts, the CPA Prediction Tool, and his expert<br />

judgment.<br />

2.3.4 Technical Observers.<br />

Four technical observers participated in the DIA simulation. All<br />

technical observers had past ATC experience, and some had <strong>FAA</strong><br />

supervisory experience. All technical obsenrers were familiar<br />

with the current MPAP project. Technical observers monitored<br />

controller actions during each simulation run. Their duties<br />

included documenting discrepancies between issued control<br />

instructions and actual aircraft responses; assisting with<br />

alerting responsible parties to correct any problems that may<br />

have occurred during the test (e.g., computer failure, stuck<br />

microphone); assisting controllers with the preparation of<br />

incident reports: and preparing a Technical Observer <strong>Report</strong> at<br />

the end of the simulation. This report included their opinions<br />

and conclusions concerning the conduct of the simulation as well<br />

as any recommendations to the MPAP TWG. The report is included<br />

as appendix I to this report.<br />

2.3.5 Simulation Observers.<br />

Simulation observers recorded information from the simulation,<br />

such as occurrences of blunders, NBO's, lost beacon signals<br />

(i.e., aircraft that went into coast), and system problems (e.g.,<br />

hardware/software failure, communications, etc.). One simulation<br />

observer was stationed in the Systems Display Laboratory, and<br />

another was located in the area of the test director.<br />

16

Hooray! Your file is uploaded and ready to be published.

Saved successfully!

Ooh no, something went wrong!