Click for next page ( 32

The National Academies | 500 Fifth St. N.W. | Washington, D.C. 20001
Copyright © National Academy of Sciences. All rights reserved.
Terms of Use and Privacy Statement

Below are the first 10 and last 10 pages of uncorrected machine-read text (when available) of this chapter, followed by the top 30 algorithmically extracted key phrases from the chapter as a whole.
Intended to provide our own search engines and external engines with highly rich, chapter-representative searchable text on the opening pages of each chapter. Because it is UNCORRECTED material, please consider the following text as a useful but insufficient proxy for the authoritative book pages.

Do not use for reproduction, copying, pasting, or reading; exclusively for search engines.

OCR for page 31
31 Figure 39. Example output summary. tables are presented showing the average risk for each RSA sec- Software Field Test tion, the percentage of movements with higher risk, and the number of operations challenging each RSA section. Appendix G provides details of the plan to field test RSARA. The first table contains three user-defined fields: the air- The plan involved testing by eight volunteers from FAA staff, port annual traffic volume, the expected annual traffic growth airport operators, university professors, industry representa- rate, and the TLS. These values reflect the options entered tives, and consultants. The volunteers received the installa- during the analysis input phase and may be modified by the tion software with the user's guide to perform analysis and user directly in the output spreadsheet. When these parame- recommend changes. ters are changed, the average number of years between inci- A questionnaire was prepared to gather comments from the dents will change to reflect the new traffic volume estimated volunteers, and their notes were used to improve the beta ver- for future years. If the TLS is modified, the percentage of move- sion of the software. During the trial period, the research team ments above the TLS will change automatically to reflect the provided technical support by answering questions, solving new TLS value. installation problems, and fixing bugs.