11.07.2015 Views

1998 - Draper Laboratory

1998 - Draper Laboratory

1998 - Draper Laboratory

SHOW MORE
SHOW LESS
  • No tags were found...

Create successful ePaper yourself

Turn your PDF publications into a flip-book with our unique Google optimized e-Paper software.

Table 7. Safety statistics at 1700-ft, 2500-ft, and 3400-ft runway spacing.analysis of flight safety issues as well as safe air traffic controlpractices. Of particular note is a recently completed project (Ref.[14]) in which the safety analysis methodology described in thispaper was used to evaluate whether a proposed automatedsystem for scheduling landings did significantly improve theperformance of air traffic controllers. Notable features of thisstudy included the use of actual flight data and landing siteconfigurations from the Dallas-Fort Worth (DFW) airport andthe introduction of ground-based flight control using groundbasedradar tracking systems for surveillance. Current work isunderway to examine the safety and other operational effectsfrom the use of the Wide Area Augmentation System (WAAS) forCategory I landings of equipped aircraft. The WAAS isenvisioned as a configuration of 35 known reference stations toaugment and enhance the accuracy of the GPS system.AcknowledgmentWe are pleased to thank Milton Adams, Andrew Parsons, andStephan Kolitz of <strong>Draper</strong> <strong>Laboratory</strong> and Peter Kostiuk ofLogistics Management Institute for their ongoing support andcritical review of this project.References[1] Federal Aviation Administration, “Airman’s InformationManual-Official Guide to Basic Information and Procedures,”U.S. Department of Transportation, 4 April 1991.[2] FAA Precision Runway Monitor Program Office, “PrecisionRunway Monitor Demonstration Report,” Report#DOT/FAA/RD-91/5, February 1991.[3] Boeing Commercial Airplane Group, “Parallel RunwayRequirement Analysis Study,” NASA Contractor Report191549, NASA Langley Research Center; Hampton, Virginia;Volume 1, December 1993.[4] Shank, E. and K. Hollister, “A Statistical Risk AssessmentModel for the Precision Runway Monitor System,” ATCAConference Proceedings, 1992.[5] Kuchar, J., “Methodology for Alerting-System PerformanceEvaluation,” AIAA Journal of Guidance, Control, andDynamics, Vol. 19, No. 2, March-April 1996, pp. 438-444.[6] Koczo, S., “Coordinated Parallel Runway Approaches,” NASAContractor Report 201611, NASA Langley Research Center,Hampton, Virginia, October 1996.[7] Waller, C.W. and C.H. Scanlon, eds., Proceedings of theNASA Workshop on Flight Deck Centered Parallel RunwayApproaches in Instrument Meteorological Conditions, NASAConference Publication 10191, NASA Langley ResearchCenter, Hampton, Virginia, December 1996.[8] Carpenter, B. and J. Kuchar, “A Probability-Based AlertingLogic for Aircraft on Parallel Approach,” NASA ContractorReport 201685, NASA Langley Research Center, Hampton,Virginia, April 1997.[9] Allinger, D., G. Rosch, M. Adams, P. Kostiuk, “An IntegratedSafety Analysis Methodology for Emerging Air TransportTechnologies,” Final Report, LMI-NS605S1, http://techreports.larc.nasa.gov/ltrs/PDF/<strong>1998</strong>/cr/NASA-98-cr207660.pdf[10] “Final Draft (Draft 7) of Minimum Aviation SystemPerformance Standards: Required Navigation Performance forArea Navigation,” RTCA Paper No. 097-96/SC181-060, 4March 1996.[11] “Draft 3.1 of Minimum Aviation System PerformanceSpecification (MASPS) for ADS-B,” December 16, 1996.[12] Babcock, P., A. Schor, G. Rosch, Reliability ModelingMethodology for IAPR Safety Analysis, The Charles Stark<strong>Draper</strong> <strong>Laboratory</strong>, Inc., Cambridge, Massachusetts, June1997.[13] Butler, R.W. and A.L. White, “Sure Reliability Analysis,Program and Mathematics,” NASA Technical Paper 2764,NASA Langley Research Center, Hampton, Virginia, March1988.[14] Kolitz, S., M. Adams, P. Kostiuk, G. Shapiro, “An IntegratedSafety Analysis of CTAS at DFW,” 25 September 1997.An Integrated Safety Analysis Methodology for Emerging Air Transport Technologies10

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

Saved successfully!

Ooh no, something went wrong!