A 5 T W A R D 0 a A C D 0 N s R R S h F E P i i P S n f O t S g R h R T S t o S A E e n T t R r I p , V O e I D N e o C C E t R r , E R t 2 N S E E 0 W 5 Q A 0

U AIRPORT R 0 0 E C S 1 H

T COOPERATIVE B E O D A

R RESEARCH D ACRP PROGRAM REPORT 50 I m p r o v e d

M Sponsored by o

d the Federal e l

s Aviation f

o Administration r

R Improved Models for i s k

A Risk Assessment of s s e s

s Runway Safety Areas m e n t o f R u n w a y S a f e t y A r e a s W P

ISBN 978-0-309-21321-9 N U e a o r . s m n

9 0 0 0 0 S P h - . i p i t n A P r N g o o t o I f s o i D t . t n a O 8 , g 9 r D e g 7 T C . 0 R B 9 780309 213219 ACRP OVERSIGHT COMMITTEE* TRANSPORTATION RESEARCH BOARD 2011 EXECUTIVE COMMITTEE*

CHAIR OFFICERS James Wilding CHAIR: Neil J. Pedersen, Administrator, Maryland State Highway Administration, Baltimore Metropolitan Washington Airports Authority (re- VICE CHAIR: Sandra Rosenbloom, Professor of Planning, University of Arizona, Tucson tired) EXECUTIVE DIRECTOR: Robert E. Skinner, Jr., Transportation Research Board VICE CHAIR MEMBERS Jeff Hamiel Minneapolis–St. Paul J. Barry Barker, Executive Director, Transit Authority of River City, Louisville, KY Metropolitan Airports Commission Deborah H. Butler, Executive Vice President, Planning, and CIO, Norfolk Southern Corporation, Norfolk, VA MEMBERS William A.V. Clark, Professor, Department of Geography, University of California, Los Angeles James Crites Eugene A. Conti, Jr., Secretary of Transportation, North Carolina DOT, Raleigh Dallas–Fort Worth International Airport James M. Crites, Executive Vice President of Operations, Dallas-Fort Worth International Airport, TX Richard de Neufville Paula J. Hammond, Secretary, Washington State DOT, Olympia Massachusetts Institute of Technology Adib K. Kanafani, Cahill Professor of Civil Engineering, University of California, Berkeley Kevin C. Dolliole Unison Consulting Susan Martinovich, Director, Nevada DOT, Carson City John K. Duval Michael R. Morris, Director of Transportation, North Central Texas Council of Governments, Arlington Austin Commercial, LP Tracy L. Rosser, Vice President, Regional General Manager, Wal-Mart Stores, Inc., Mandeville, LA Kitty Freidheim Steven T. Scalzo, Chief Operating Officer, Marine Resources Group, Seattle, WA Freidheim Consulting Steve Grossman Henry G. (Gerry) Schwartz, Jr., Chairman (retired), Jacobs/Sverdrup Civil, Inc., St. Louis, MO Jacksonville Aviation Authority Beverly A. Scott, General Manager and CEO, Metropolitan Atlanta Rapid Transit Authority, Tom Jensen Atlanta, GA National Safe Skies Alliance David Seltzer, Principal, Mercator Advisors LLC, Philadelphia, PA Catherine M. Lang Lawrence A. Selzer, President and CEO, The Conservation Fund, Arlington, VA Federal Aviation Administration Gina Marie Lindsey Kumares C. Sinha, Olson Distinguished Professor of Civil Engineering, Purdue University, West Los Angeles World Airports Lafayette, IN Carolyn Motz Daniel Sperling, Professor of Civil Engineering and Environmental Science and Policy; Director, Institute of Hagerstown Regional Airport Transportation Studies; and Interim Director, Energy Efficiency Center, University of California, Davis Richard Tucker Kirk T. Steudle, Director, Michigan DOT, Lansing Huntsville International Airport Douglas W. Stotlar, President and CEO, Con-Way, Inc., Ann Arbor, MI EX OFFICIO MEMBERS C. Michael Walton, Ernest H. Cockrell Centennial Chair in Engineering, University of Texas, Austin Paula P. Hochstetler EX OFFICIO MEMBERS Airport Consultants Council Sabrina Johnson Peter H. Appel, Administrator, Research and Innovative Technology Administration, U.S.DOT U.S. Environmental Protection Agency J. Randolph Babbitt, Administrator, Federal Aviation Administration, U.S.DOT Richard Marchi Rebecca M. Brewster, President and COO, American Transportation Research Institute, Smyrna, GA Airports Council International—North America Laura McKee Anne S. Ferro, Administrator, Federal Motor Carrier Safety Administration, U.S.DOT Air Transport Association of America John T. Gray, Senior Vice President, Policy and Economics, Association of American Railroads, Henry Ogrodzinski Washington, DC National Association of State Aviation Officials John C. Horsley, Executive Director, American Association of State Highway and Transportation Melissa Sabatine Officials, Washington, DC American Association of Airport Executives Robert E. Skinner, Jr. David T. Matsuda, Deputy Administrator, Maritime Administration, U.S.DOT Transportation Research Board Victor M. Mendez, Administrator, Federal Highway Administration, U.S.DOT William W. Millar, President, American Public Transportation Association, Washington, DC SECRETARY Tara O’Toole, Under Secretary for Science and Technology, U.S. Department of Homeland Security, Christopher W. Jenks Washington, DC Transportation Research Board Robert J. Papp (Adm., U.S. Coast Guard), Commandant, U.S. Coast Guard, U.S. Department of Homeland Security, Washington, DC Cynthia L. Quarterman, Administrator, Pipeline and Hazardous Materials Safety Administration, U.S.DOT Peter M. Rogoff, Administrator, Federal Transit Administration, U.S.DOT David L. Strickland, Administrator, National Highway Traffic Safety Administration, U.S.DOT Joseph C. Szabo, Administrator, Federal Railroad Administration, U.S.DOT Polly Trottenberg, Assistant Secretary for Transportation Policy, U.S.DOT Robert L. Van Antwerp (Lt. Gen., U.S. Army), Chief of Engineers and Commanding General, U.S. Army Corps of Engineers, Washington, DC Barry R. Wallerstein, Executive Officer, South Coast Air Quality Management District, Diamond Bar, CA

*Membership as of October 2010. *Membership as of March 2011. AIRPORT COOPERATIVE RESEARCH PROGRAM

ACRP REPORT 50

Improved Models for Risk Assessment of Runway Safety Areas

Manuel Ayres Jr. Hamid Shirazi Regis Carvalho Jim Hall Richard Speir Edith Arambula APPLIED RESEARCH ASSOCIATES, INC. Elkridge, MD

Robert David ROBERT E. DAVID & ASSOCIATES, INC. Fredericksburg, VA

Derek Wong London, UK

John Gadzinski FOUR WINDS CONSULTING Virginia Beach, VA

Subscriber Categories Aviation • Safety and Human Factors

Research sponsored by the Federal Aviation Administration

TRANSPORTATION RESEARCH BOARD

WASHINGTON, D.C. 2011 www.TRB.org AIRPORT COOPERATIVE RESEARCH PROGRAM ACRP REPORT 50

Airports are vital national resources. They serve a key role in trans- Project 04-08 portation of people and goods and in regional, national, and inter- ISSN 1935-9802 national commerce. They are where the nation’s aviation system ISBN 978-0-309-21321-9 connects with other modes of transportation and where federal respon- Library of Congress Control Number 2011928921 sibility for managing and regulating air traffic operations intersects with the role of state and local governments that own and operate most © 2011 National Academy of Sciences. All rights reserved. airports. Research is necessary to solve common operating problems, to adapt appropriate new technologies from other industries, and to introduce innovations into the airport industry. The Airport Coopera- COPYRIGHT INFORMATION tive Research Program (ACRP) serves as one of the principal means by which the airport industry can develop innovative near-term solutions Authors herein are responsible for the authenticity of their materials and for obtaining written permissions from publishers or persons who own the copyright to any previously to meet demands placed on it. published or copyrighted material used herein. The need for ACRP was identified in TRB Special Report 272: Airport Research Needs: Cooperative Solutions in 2003, based on a study spon- Cooperative Research Programs (CRP) grants permission to reproduce material in this sored by the Federal Aviation Administration (FAA). The ACRP carries publication for classroom and not-for-profit purposes. Permission is given with the understanding that none of the material will be used to imply TRB or FAA endorsement out applied research on problems that are shared by airport operating of a particular product, method, or practice. It is expected that those reproducing the agencies and are not being adequately addressed by existing federal material in this document for educational and not-for-profit uses will give appropriate research programs. It is modeled after the successful National Coopera- acknowledgment of the source of any reprinted or reproduced material. For other uses of tive Highway Research Program and Transit Cooperative Research Pro- the material, request permission from CRP. gram. The ACRP undertakes research and other technical activities in a variety of airport subject areas, including design, construction, mainte- nance, operations, safety, security, policy, planning, human resources, NOTICE and administration. The ACRP provides a forum where airport opera- tors can cooperatively address common operational problems. The project that is the subject of this report was a part of the Airport Cooperative Research The ACRP was authorized in December 2003 as part of the Vision Program, conducted by the Transportation Research Board with the approval of the Governing Board of the National Research Council. 100-Century of Aviation Reauthorization Act. The primary partici- pants in the ACRP are (1) an independent governing board, the ACRP The members of the technical panel selected to monitor this project and to review this Oversight Committee (AOC), appointed by the Secretary of the U.S. report were chosen for their special competencies and with regard for appropriate balance. The report was reviewed by the technical panel and accepted for publication according to Department of Transportation with representation from airport oper- procedures established and overseen by the Transportation Research Board and approved ating agencies, other stakeholders, and relevant industry organizations by the Governing Board of the National Research Council. such as the Airports Council International-North America (ACI-NA), The opinions and conclusions expressed or implied in this report are those of the the American Association of Airport Executives (AAAE), the National researchers who performed the research and are not necessarily those of the Transportation Association of State Aviation Officials (NASAO), and the Air Transport Research Board, the National Research Council, or the program sponsors. Association (ATA) as vital links to the airport community; (2) the TRB The Transportation Research Board of the National Academies, the National Research as program manager and secretariat for the governing board; and Council, and the sponsors of the Airport Cooperative Research Program do not endorse (3) the FAA as program sponsor. In October 2005, the FAA executed a products or manufacturers. Trade or manufacturers’ names appear herein solely because contract with the National Academies formally initiating the program. they are considered essential to the object of the report. The ACRP benefits from the cooperation and participation of airport professionals, air carriers, shippers, state and local government officials, equipment and service suppliers, other airport users, and research orga- nizations. Each of these participants has different interests and respon- sibilities, and each is an integral part of this cooperative research effort. Research problem statements for the ACRP are solicited periodically but may be submitted to the TRB by anyone at any time. It is the responsibility of the AOC to formulate the research program by iden- tifying the highest priority projects and defining funding levels and expected products. Once selected, each ACRP project is assigned to an expert panel, appointed by the TRB. Panels include experienced practitioners and research specialists; heavy emphasis is placed on including airport pro- fessionals, the intended users of the research products. The panels pre- pare project statements (requests for proposals), select contractors, and provide technical guidance and counsel throughout the life of the project. The process for developing research problem statements and Published reports of the selecting research agencies has been used by TRB in managing cooper- AIRPORT COOPERATIVE RESEARCH PROGRAM ative research programs since 1962. As in other TRB activities, ACRP project panels serve voluntarily without compensation. are available from: Primary emphasis is placed on disseminating ACRP results to the Transportation Research Board intended end-users of the research: airport operating agencies, service Business Office 500 Fifth Street, NW providers, and suppliers. The ACRP produces a series of research Washington, DC 20001 reports for use by airport operators, local agencies, the FAA, and other interested parties, and industry associations may arrange for work- and can be ordered through the Internet at shops, training aids, field visits, and other activities to ensure that http://www.national-academies.org/trb/bookstore results are implemented by airport-industry practitioners. Printed in the United States of America The National Academy of Sciences is a private, nonprofit, self-perpetuating society of distinguished scholars engaged in scientific and engineering research, dedicated to the furtherance of science and technology and to their use for the general welfare. On the authority of the charter granted to it by the Congress in 1863, the Academy has a mandate that requires it to advise the federal government on scientific and technical matters. Dr. Ralph J. Cicerone is president of the National Academy of Sciences.

The National Academy of Engineering was established in 1964, under the charter of the National Academy of Sciences, as a parallel organization of outstanding engineers. It is autonomous in its administration and in the selection of its members, sharing with the National Academy of Sciences the responsibility for advising the federal government. The National Academy of Engineering also sponsors engineering programs aimed at meeting national needs, encourages education and research, and recognizes the superior achievements of engineers. Dr. Charles M. Vest is president of the National Academy of Engineering.

The Institute of Medicine was established in 1970 by the National Academy of Sciences to secure the services of eminent members of appropriate professions in the examination of policy matters pertaining to the health of the public. The Institute acts under the responsibility given to the National Academy of Sciences by its congressional charter to be an adviser to the federal government and, on its own initiative, to identify issues of medical care, research, and education. Dr. Harvey V. Fineberg is president of the Institute of Medicine.

The National Research Council was organized by the National Academy of Sciences in 1916 to associate the broad community of science and technology with the Academy’s purposes of furthering knowledge and advising the federal government. Functioning in accordance with general policies determined by the Academy, the Council has become the principal operating agency of both the National Academy of Sciences and the National Academy of Engineering in providing services to the government, the public, and the scientific and engineering communities. The Council is administered jointly by both Academies and the Institute of Medicine. Dr. Ralph J. Cicerone and Dr. Charles M. Vest are chair and vice chair, respectively, of the National Research Council.

The Transportation Research Board is one of six major divisions of the National Research Council. The mission of the Transporta- tion Research Board is to provide leadership in transportation innovation and progress through research and information exchange, conducted within a setting that is objective, interdisciplinary, and multimodal. The Board’s varied activities annually engage about 7,000 engineers, scientists, and other transportation researchers and practitioners from the public and private sectors and academia, all of whom contribute their expertise in the public interest. The program is supported by state transportation departments, federal agencies including the component administrations of the U.S. Department of Transportation, and other organizations and individu- als interested in the development of transportation. www.TRB.org

www.national-academies.org COOPERATIVE RESEARCH PROGRAMS

CRP STAFF FOR ACRP REPORT 50

Christopher W. Jenks, Director, Cooperative Research Programs Crawford F. Jencks, Deputy Director, Cooperative Research Programs Michael R. Salamone, ACRP Manager Theresia H. Schatz, Senior Program Officer Joseph J. Brown-Snell, Program Associate Eileen P. Delaney, Director of Publications Margaret B. Hagood, Editor

ACRP PROJECT 04-08 PANEL Field of Safety

Dana L. Ryan, St. Louis Airport Authority, St. Louis, MO (Chair) Steven G. Benson, Coffman Associates, Lee Summitt, MO Diana S. Dolezal, Greater Toronto Airports Authority, Toronto, ON Alex M. Kashani, Metropolitan Washington Airports Authority, Washington, DC Deborah T. Marino, Titusville–Cocoa Airport Authority, Titusville, FL Phillip C. Miller, California DOT, Sacramento, CA Xiaosong “Sean” Xiao, Xcel Energy, Minneapolis, MN Michel Hovan, FAA Liaison Matthew J. Griffin, Airports Council International–North America Liaison Richard Pain, TRB Liaison

AUTHOR ACKNOWLEDGMENTS The research reported herein was performed under ACRP Project 4-08 by Applied Research Associates Inc. (ARA), Robert E. David & Associates, Inc. (RED), Dr. Derek Wong, and Mr. John Gadzinski. ARA was the prime contractor for this study, with RED, Dr. Wong and Four Winds Consulting serving as sub- consultants. Dr. Manuel Ayres, Principal Engineer at ARA, was the Principal Investigator; Mr. Hamid Shirazi, P.E., Project Engineer at ARA, was the Project Manager, and Mr. Richard Speir, ARA Mid-Atlantic Division Manager, served as Co-Principal Investigator. The other authors of this report are Mr. Regis Carvalho (ARA), Mr. Robert David (RED), Dr. Derek Wong, Consultant, Dr. Jim Hall, Mr. John Gadzinski (Four Winds), and Ms. Edith Arambula (ARA). The authors are very grateful for the guidance and help provided by the ACRP Panel for ACRP 4-08. A very important contribution to this study was provided by MITRE Corporation. They made available their comprehensive database of accidents, and it significantly improved the availability of information to develop the risk models presented in this study. The research team is particularly grateful to Mr. Wallace Feerrar and Mr. John LeBron, who kindly made the information available. The research team is also very grateful for the participation of eight volunteers listed in Appendix G to test the analysis software, and for the courtesy of Mr. Luis Rosa to authorize the use of his photos. FOREWORD

By Theresia H. Schatz Staff Officer Transportation Research Board

ACRP Report 50: Improved Models for Risk Assessment of Runway Safety Areas expands on the research presented in ACRP Report 3: Analysis of Aircraft Overruns and Undershoots for Runway Safety Areas to include the analysis of aircraft veer-offs, the use of declared dis- tances, the implementation of the Engineered Material Arresting System (EMAS) and the incorporation of a risk approach for consideration of obstacles in or in the vicinity of the RSA. A user-friendly risk analysis tool is provided for airport and industry stakeholders to quantify risk and support planning and engineering decisions when determining RSA requirements to meet an acceptable level of safety for various types and sizes of airports. The tool is interactive and versatile to help users determine the risk based on various input parameters.

Current standards for RSAs are fairly rigid because they depend only on the type and size of aircraft using the runway. However, numerous factors affecting operations may lead to aircraft overruns, undershoots, and veer-offs. In many instances, standard RSAs are not fea- sible because of constraints, such as obstacles or land unavailability. In such cases, it is essen- tial that alternatives be evaluated to minimize risk, to the extent practicable, in relation to site-specific conditions. For example, depending on the type of operation, the relationship between actual runway distance required and the actual runway distance available for both landing and takeoff can significantly affect the risk. An approach for risk assessment of RSAs has been developed under ACRP Report 3: Analysis of Aircraft Overruns and Undershoots for Runway Safety Areas. ACRP Report 3 pro- vides a risk-based assessment that is rational and accounts for the variability of several risk factors associated with aircraft overruns and undershoots. The findings in ACRP Report 3 are the basis for further research to quantify and assess risk in the RSA environment. Under- standing this level of risk under a given set of conditions is essential to address RSA enhance- ment opportunities. ACRP Report 50 contains an analysis tool on the accompanying CD. The user guide to the analysis tool is in Appendix I of the report and is also on the CD and software help file. In addition, a presentation documenting the research method has been posted on the proj- ect web page, under ACRP Project 04-08. This research effort was conducted by Applied Research Associates, Inc. as the prime contractor, with Dr. Manuel Ayres serving as Prin- cipal Investigator, and Robert E. David & Associates and Four Winds Consulting as sub-consultants. CONTENTS

1 Summary 3 Chapter 1 Background 3 Introduction 4 Project Goals 4 RSA Improvement Alternatives 7 Chapter 2 Research Approach 7 Functional Hazard Analysis 8 Accident and Incident Data 12 Normal Operations Data 12 Aircraft Data 13 Chapter 3 Modeling RSA Risk 13 Event Probability (Frequency Model) 15 Event Location Models 18 EMAS Deceleration Model 22 Accuracy of Models 23 Chapter 4 Consequence Approach 23 Modeling Approach for Risk 25 Implementation of Approach 27 Additional Simplifications 28 Chapter 5 Analysis Software 28 Overview 28 Software Capabilities 28 Input Data 30 Output and Interpretation 31 Software Field Test 32 Chapter 6 Model Validation 34 Validation of Frequency Models 35 Validation of Risk Model 37 Chapter 7 Conclusions and Recommendations for Further Research 37 Major Achievements 38 Limitations 39 Recommendations for Future Work 40 References 41 Abbreviations and Acronyms 43 Definitions A-1 Appendix A Functional Hazard Analysis Results B-1 Appendix B Summary of Accidents and Incidents C-1 Appendix C Sample of Normal Operations Data D-1 Appendix D Aircraft Database Summary E-1 Appendix E EMAS F-1 Appendix F Risk Criteria Used by the FAA G-1 Appendix G Plan to Field Test Software Tool H-1 Appendix H Summary of Results for Software/Model Tests I-1 Appendix I Software User’s Guide

Note: Many of the photographs, figures, and tables in this report have been converted from color to grayscale for printing. The electronic version of the report (posted on the Web at www.trb.org) retains the color versions. 1

SUMMARY Improved Models for Risk Assessment of Runway Safety Areas

The objective of this research project was to develop and validate a user-friendly software analysis tool that can be used by airport and industry stakeholders to quantify risk and sup- port planning and engineering decisions when determining runway safety area (RSA) requirements to meet an acceptable level of safety for various types and sizes of airports. The underlying basis was the approach presented in ACRP Report 3: Analysis of Aircraft Overruns and Undershoots for Runway Safety Areas. The improved models and methodol- ogy provided by this research effort provide the capability to evaluate declared distances and the use of engineered material arresting system (EMAS), as well as the ability to consider the effects of obstacles inside or in the vicinity of the RSA. The RSA is intended to prevent the following five types of events from becoming an acci- dent: landing overruns, landing undershoots, landing veer-offs, takeoff overruns and takeoff veer-offs. The risk analysis for each type of event is threefold and considers probability (aka frequency), location, and consequence. The models for probability and location are specific for the event type, while the model for consequences is applicable to all five event types. The models are based on evidence from worldwide accidents and incidents that occurred during the past 27 years. The analysis utilizes historical data from the specific airport and allows the user to take into consideration specific operational conditions to which move- ments are subject, as well as the actual or planned RSA conditions in terms of dimensions, configuration, type of terrain, and boundaries defined by existing obstacles. The combined estimates for the probability model and location model provide an esti- mate that the event will take place and that the aircraft will stop or touch down beyond a certain distance from the runway area or strike an existing obstacle at a given speed. Using these estimates for the distances defined by the RSA bounds or by existing obstacles, it is pos- sible to estimate the risk of accidents. User-friendly software was developed and tested to help with the analysis. Input data to the analysis includes historical information on operations and weather and the definition of the RSA conditions and obstacles. The computer program runs a simulation to assess the risk for each historical operation and outputs average risk levels and probability distribu- tions for each type of incident and each RSA section challenged by the operations. Results help the user identify areas of higher risk as well as compare different RSA alternatives. Finally, the models developed in this research were validated using actual data for a sam- ple of eight airports. The analysis results using actual data for these airports were compared to actual accident and incident rates over the past 25 years for each of these airports. The objective of this validation effort was to gain industry confidence on using the new method- ology and software tool. The outcome of this project is an RSA analysis tool that may benefit airport planners and engineers and that can be used to support safety risk assessments and actions. The approach 2

used and the software developed can be applied to evaluate any type of RSA improvement, including extending the RSA, using declared distances, and using EMAS, In addition, it is possible to analyze irregular RSA shapes and to consider the type of terrain and the presence of obstacles inside or in the vicinity of the RSA. The RSA analysis tool should be used only for planning purposes rather than to evaluate risk for real-time conditions or individual operations. In addition, the data used to develop the risk models included only multi-engine aircraft with maximum takeoff weight (MTOW) higher than 5,600 lb. The approach for consequences incorporated in the analysis was based solely on engineering judgment, rather than crashworthiness data. ACRP makes no warranties, expressed or implied, concerning the accuracy, completeness, reliability, usability, or suitability of any particular purpose of the information or the data contained in the program. The software tool should be used by airport professionals who are familiar with and qualified to perform RSA analysis. 3

CHAPTER 1 Background

Introduction mountable challenges due to terrain or environmental restric- tions such as wetlands. Landing and takeoff overruns, landing undershoots, and More recently, the introduction of Engineered Material Ar- landing and takeoff veer-offs account for most of the acci- resting Systems (EMASs) has provided an alternative to achieve dents that occur on or in the immediate vicinity of the run- safety levels similar to those provided by the standards, but way. Accident statistics show that, from 1959 to 2009, 55% using only 60% of the area. Another alternative that has been of the world’s jet fatal aircraft accidents occurred during used worldwide is the use of declared distances. For either of landing and takeoff phases of the flight and accounted for these alternatives there were no tools to help assess the true 51% of all onboard fatalities (Boeing 2010). Although in many safety benefits associated with the solution selected. cases the causal factors involve some type of human error, The study presented in ACRP Report 3 introduced a method- the conditions at the airport may contribute significantly to ology for risk assessment of RSAs that has been used to evaluate the probability and severity of the accidents. RSA alternatives by the industry. However, the methodology The runway safety area (RSA) is a graded and obstacle-free cannot be used to evaluate the use of EMAS, declared distances, rectangular-shaped area surrounding the runway that “should or safety areas for veer-off incidents. Moreover, the analysis is be capable, under normal (dry) conditions, of supporting air- complex and only prototype software was developed under planes without causing structural damage to airplanes or that study. injury to their occupants” (AC 150/5300-13 1989). The RSA This report is organized into seven chapters. This first chap- improves the safety of airplanes that undershoot, overrun, or ter provides the background and the objectives of the study, veer off the runway and has helped turn potential accidents as well as the basic alternatives used by the industry to im- into minor incidents. prove RSAs. The second chapter describes the five major types The rectangular dimensions of the RSA have changed over of incidents included in the analysis with major causes and the years and depend on the category of aircraft using the contributing factors. Moreover the chapter presents the data runway. In the 1960s, in an attempt to mitigate the severity of used for the modeling process. aircraft accidents, the FAA revised the airport standards for Chapter three explains the three-part approach to model RSA. The FAA RSA standard for most runways serving 14 CFR each type of incident. Also it presents the probability and Part 121 air carrier operations is an area that is 500 feet wide location models developed in this study and incorporated in centered on the runway and extends 1000 feet beyond each the approach. The next chapter describes the consequence end of the runway. approach and how it was implemented. Because many airports were built before the 1960s, when The approach and the models developed in this study were RSA dimension standards were smaller, some airports were incorporated into RSA analysis software named Runway Safety not complying with the new dimensions. In 1999, the FAA Area Risk Analysis (RSARA). Chapter 5 describes the soft- released Order 5200-8 and embarked upon a major effort to ware, and the required input and output information. Both upgrade safety areas that do not meet the current standards. the software and the models were validated using a sample of The goal is to have all possible improvements for Part 139 air- airports and their historical records for accidents and incidents ports completed by 2015. However, it is not practical for to run the analysis and compare actual and predicted incident some airports to extend their current RSA dimensions to and accident rates. The results for validating the analysis are meet the standards because they are landlocked or face insur- presented in Chapter 6. 4

Finally, Chapter 7 describes the major conclusions and rec- that may occur in those locations. Two of those sections are ommendations from this study. It also explains major achieve- located on each runway end and include the RSA portion im- ments and limitations. mediately before the arrival thresholds and beyond the depar- ture end of the runway. These are the sections that help mit- Project Goals igate consequences of aircraft overruns and undershoots. The third RSA section is lateral to the runway and extends over the The ultimate objective of this research was to develop a risk runway length on both sides of the runway. This is the area assessment tool that can be used to evaluate alternatives for that can help mitigate the severity of aircraft veer-off incidents. RSA improvements, with a capability to account for the use For the RSA sections located laterally to the runway, im- of EMAS, declared distances, the presence of obstacles, spe- provements can be made by removing obstacles and preparing cific operations, weather, and runway conditions. the area according to RSA standards to increase the runway New models were developed, and the capability to evalu- object free area (ROFA) width. In some cases this may be nec- ate risk for veer-off events was added to the approach pre- essary to introduce the operation of larger aircraft to increase sented in ACRP Report 3. Five sets of models were developed in capacity; however, they may be restrained to increase the ex- this study: landing overruns, landing veer-offs, landing under- isting runway separation distances to accommodate the larger shoots, takeoff veer-offs, and takeoff overruns. Each set includes airplane design group (ADG). three models: incident frequency, stop/touchdown location, There are four basic alternatives available to improve an and consequences. RSA when it does not meet the standards: The following were the specific goals that were achieved for ACRP Project 4-08: • Extend the RSA laterally and longitudinally. • Modify or relocate the runway to expand the RSA. 1. Update the ACRP Report 3 accident/incident database to • Implement declared distances by reducing the available incorporate aircraft overrun and undershoot accidents and runway distances and extending the RSA section adjacent incidents occurring after 2006. to the runway ends. 2. Collect data on aircraft runway veer-off accidents and in- • Use arresting systems to obtain a level of safety similar to cidents and integrate these data into the existing database. that provided by the standard RSA. 3. Develop risk models for frequency and location for each type of incident: landing overruns (LDOR); landing under- Any combination of such alternatives is also possible, and shoots (LDUS); landing veer-offs (LDVO), takeoff overruns the methodology presented in this report has the capability (TOOR), and takeoff veer-offs (TOVO). to analyze any such combinations. Each of these alternatives 4. Develop a practical approach to assess the impact of run- has advantages and disadvantages that are specific to each sit- way distance available on the probability of overruns, under- uation and that need to be assessed, as described in ensuing shoots, and veer-offs. sections of this report. 5. Develop a practical approach to assess risk and the impact It is important to note that airport operators can take addi- of using EMAS as an alternative to standard RSAs, or to tional actions to mitigate the probability of aircraft overruns, use declared distances and evaluate the safety impact of undershoots, and veer-offs. Some possible alternatives may reduced runway distance available. include the following: 6. Develop a practical approach to model incident conse- quences based on existing conditions and the presence of • Improve skid resistance and reduce undulations of runway obstacles inside or in the vicinity of the RSA. surface. 7. Develop user-friendly software that incorporates the • Monitor runway friction level to determine need to close methodology and models developed as a practical tool that the runway (e.g., ice conditions) and time for maintenance airport stakeholders may use to evaluate RSA alternatives. (e.g., rubber removal). 8. Field test the software developed. • Ensure accurate weather information and runway surface 9. Validate the new tool based on data gathered according to conditions are available to flight crews. an airport survey plan. • Improve airport capability to detect unusual weather con- ditions (e.g., wind shear). RSA Improvement Alternatives • Minimize the presence of obstacles in the vicinity of RSAs. • Upgrade visual and instrument landing aids to improve ac- General Considerations curacy of approach path. To facilitate understanding the role of an RSA, it can be di- • Coordinate operational restrictions with airlines and air traf- vided into three sections as a function of the types of incidents fic control (ATC) when adverse weather conditions arise. 5

• Publish RSA provision in the Aeronautical Information Pub- Existing RSA lication when RSA’s cannot comply with standards.

Although these actions can decrease the probability of un- desirable events, it is not possible to measure the impact of these risk mitigation actions on the total airport risk of seri- Improved RSA ous aircraft overruns, undershoots, and veer-offs. This study introduces a risk-based methodology for quan- titative evaluation of any of the alternatives or combinations 1000 ft of RSA improvement alternatives identified in FAA Order Figure 2. Relocating the runway. 5200.8 (1999). These alternatives are described below.

necessary to implement declared distances to accommodate a Extend the RSA larger RSA. Figure 3 shows an example to extend the RSA using An example of extending the RSA is shown in Figure 1. In this alternative. this case, the RSA adjacent to the right runway end and the This is a fast and low cost alternative for the airport opera- lateral area originally did not comply with the standard. tor; however, it may impact airport capacity, reduce payloads, This is a straightforward solution to improve an RSA and and/or degrade the level of safety under specific situations, is used to extend it to the runway ends or the lateral sections. which may lead to long-term consequences to the airport. In However, this alternative is not always feasible due to phys- the example provided, the runway was reduced to accommo- ical, environmental, or other constraints involved with date a larger RSA by reducing the landing distance available. implementation. Use of Arresting Systems Modify or Relocate the Runway When a full RSA cannot be achieved, the airport may use In Figure 2, the runway was relocated to the left to obtain a bed of lightweight concrete that is crushed under the wheels a standard RSA of 1000 ft in length. The relocation also may of a stray aircraft, causing energy from its forward motion to involve the change of runway direction. be absorbed, to bring the aircraft to a stop within a shorter Similar to the previous alternative, this solution may involve distance. A standard EMAS bed can reduce what would nor- very high costs, particularly if changing the runway direction mally be a 1000-ft RSA to 600 ft, or even less if the land is is necessary. In this case, a new runway must be constructed not available, depending upon the aircraft types using the to replace the existing one. For the example shown, to keep runway. Figure 4 presents an example of RSA improvement the distance available for landing, it is necessary to extend the using EMAS. runway to the left. This is an alternative that only became available in recent years and provides a feasible solution, particularly for land- Implement Declared Distances locked runways. The major disadvantages are the high initial cost, maintenance costs, the need to replace the bed when Declared distances are a means of obtaining a standard used, the need to periodically replace the bed due to natural safety area by reducing the usable runway length. When the deterioration, and it still requires some land area to be avail- RSA cannot be extended or the runway relocated, it may be able for installation.

Existing RSA Existing RSA

Improved RSA Improved RSA

1000 ft Figure 1. Extending the RSA. Figure 3. Using declared distances. 6

Existing RSA

EMAS Bed Improved RSA

Figure 4. Using EMAS. 7

CHAPTER 2 Research Approach

The development of this study included 11 tasks. These Functional Hazard Analysis steps are illustrated in Figure 5. The project started with a kick-off meeting and collection of As part of the literature review for this project, the research updated information, particularly to review the literature asso- team reviewed information on operational experience to de- ciated with runway veer-off incidents, which was not part of the velop a functional hazard analysis (FHA) for the types of in- cidents relevant to this study. A similar analysis conducted by previous ACRP study. Following the literature review, the re- Eddowes et al. (2001) was used for overruns and undershoots search team collected information to develop the risk models, in the ACRP Report 3 study, and a summary is presented in including accident and incident information, aircraft data to Appendix A. build a criticality factor into the frequency models, as well as An FHA is a formal and systematic process for the identi- complementing the normal operations data (NOD) for general fication of hazards associated with an activity. The purpose of aviation (GA) flights of aircraft with MTOW below 12,000 lb. the FHA was to determine relevant causal and contributing Three parallel tasks were carried out after the model data factors of veer-off, overrun, and undershoot accidents and were completed and reviewed: the development of risk models hazards to aircraft associated with aerodrome operations and for aircraft overruns, veer-offs, and undershoots; the develop- the physical design of airfields. ment of a test plan to validate the approach, the models, and the Overrun, veer-off, and undershoot incidents may be consid- analysis software; and the development of a software outline to ered in terms of the deviation of the aircraft from its intended present to the panel. An interim report was prepared and sub- path. The definition of the deviation for each incident type may mitted to the panel for discussion during the interim meeting. be summarized as follows: Following the meeting, the research team pursued tasks on two fronts. The first was the development, testing, and review • For overrun incidents, the “longitudinal deviation” is de- of the analysis software, and the second consisted of the prepa- scribed by the longitudinal distance traveled beyond the ration of data and actions to validate the study. expected accelerate/stop distance (for takeoff events) and The approved software framework was implemented using beyond the landing distance available (for landing events). Microsoft .Net and Microsoft Office tools (Excel and Access), • For veer-off incidents, the “lateral deviation” is described and a user manual was developed. Eight industry volunteers by the lateral distance traveled from the runway longitudi- were selected to test the beta version and provide comments nal edge. to enhance the solution and eliminate bugs. In parallel, the • For undershoot incidents, the “longitudinal deviation” is software team conducted tests to identify and eliminate bugs. described by the longitudinal distance from the point where A revised version of the software was used to run the analysis the aircraft actually touched down to the runway threshold. for airports selected for validation. • For both overrun and undershoot events, the “lateral de- Eight airports were selected to run the analyses for valida- viation” is the lateral distance to the extended runway tion. Accident and incident data for these airports, as well as centerline. operations and weather information covering 1 year, were col- lected. The risk estimates were then compared to the actual ac- The identification of factors associated with aircraft over- cident and incident rates for the airports. The research tasks, runs, undershoots, and veer-off was an important step prior to the models, and the results are summarized in this report, the collection of accident and incident data, as this information last task in this study. was required to develop the risk models presented in this study. 8

Literature Review

Collection and Preparation of Data Accident & Incident Aircraft Normal Operations

Development of Risk Development of Test Development of Models Plan Software Outline

Interim Meeting

Development of Execution of Test Plan Analysis Software Select airports Collect airport data Testing of Analysis Run analysis for selected airports Software Validate models & software Revised Software Final report

Figure 5. Study tasks.

Accident and Incident Data the runway ends and within 1000 ft of the runway centerline. The criteria represents the area where the overwhelming ma- Accident and incident data were collected from the following jority of runway excursions and undershoots occur and are sources: similar to those used in ACRP Report 3 and by the FAA (David • FAA Accident/Incident Data System (AIDS). 1990). Using such criteria, 1414 accidents and incidents were • FAA/National Aeronautics & Space Administration (NASA) identified to provide the information used to develop the Aviation Safety Reporting System (ASRS). frequency and location models. Events that took place since • National Transportation Safety Board (NTSB) Accident 1980 and for which reports were available were included in Database & Synopses. the database. • MITRE Corporation Runway Excursion Events Database Part of the data used to develop the frequency models was V.4 (2008). complemented from other sources of information, particu- • Transportation Safety Board of Canada (TSB). larly for aircraft, airport, and meteorological conditions. For • International Civil Aviation Organization (ICAO) Accident/ example, in some cases the weather information during the Incident Data Reporting (ADREP) system. incident was missing and the actual METAR for the airport • Australian Transport Safety Bureau (ATSB). was obtained. In other situations, the runway used was miss- • Bureau d’Enquêtes et d’Analyses pour la Sécurité de l’Avi- ing and the FAA Enhanced Traffic Management System Per- ation Civile (BEA). formance Metrics (ASPM) was consulted. • UK Air Accidents Investigation Branch (AAIB). • New Zealand Transport Accident Investigation Commission Filter Applied to the Data (TAIC). • Air Accident Investigation Bureau of Singapore. Criteria for filtering data were established to make the events • Ireland Air Accident Investigation Unit (AAIU). comparable. The first filter was an attempt to use information • Spain Comisión de Investigación de Accidentes e Incidentes from only specific regions of the world having accident rates de Aviación Civil (CIAIAC). that are comparable to the U.S. rate. This information was com- • Indonesia National Transportation Safety Committee bined with U.S. data to develop the location models. For the (NTSC). frequency models, only U.S. data were used because compre- • Netherlands Aviation Safety Board (NASB). hensive incident records are only available in the United States. The criteria used are shown in Table 1. More than 260,000 aviation accident and incident reports The accident and incident database was organized in Mi- were screened from 11 countries to identify the cases relevant crosoft Access. The ACRP Report 3 database was modified to to this study. Out of those, more than 140,000 events were simplify its use. The system provides the software tools needed screened from U.S. databases. The relevant events were fil- to utilize the data in a flexible manner and includes the capa- tered prior to gathering data from each report. bility to add, modify, or delete data from the database, make A list of accidents and incidents containing the cases used for queries about the data stored in the database, and produce model development is presented in Appendix B of this report. reports summarizing selected contents. Figure 6 shows the The list includes the accidents that occurred within 2000 ft of database organization. 9

Table 1. Filtering criteria for accidents and incidents.

Filter # Description Justification 1 Remove non-fixed wing aircraft entries Study is concerned with fixed wing aircraft accidents and incidents only 2 Remove entries for airplanes with Cut off criteria to maintain comparable level of pilot certified max gross weight < 6,000 lbs qualifications and aircraft performance to increase the validity of the modeling 3 Remove entries with unwanted FAR Some FAR parts have significantly different safety parts. Kept Part 121, 125, 129, 135 and regulations (e.g., pilot qualifications). The following selected Part 91 operations. cases were removed: o Part 91F: Special Flt Ops. o Part 103: Ultralight o Part 105: Parachute Jumping o Part 133: Rotorcraft Ext. Load o Part 137: Agricultural o Part 141: Pilot Schools o Armed Forces 4 Remove occurrences for unwanted Study focus is the runway safety area. Situations phases of flight when the RSA cannot help mitigating accident and incident consequences were discarded to increase model validity. 5 Remove all single engine aircraft and Piston engine aircraft are now used less frequently all piston engine aircraft entries in civil aviation and therefore have been removed, to increase the validity of the modeling. Moreover single and piston engine aircraft behave differently in accidents due to the lower energy levels involved and the fact that the major focus of this study is air carrier aircraft. 6 Remove all accidents and incidents It would be unfeasible to have an RSA with more when the point of first impact and the than 2000ft beyond the threshold or 1000ft from the wreckage final location is beyond runway centerline, the gain in safety is not 2000ft from runway end and 1000ft significant and both the previous ACRP study and from runway centerline. the FAA study used the 2000ft criteria (David 1990).

Figure 6. Accident and incident database for aircraft overruns, undershoots, and veer-offs. 10

Accidents/Incidents by Type

500

400

300

200 # of Events 100

0 LDOR LDUS LDVOFF TOOR TOVOFF ACC 138 51 111 61 22 INC 363 60 448 62 98 Type of Event Figure 7. Summary of accidents and incidents by type.

The database includes, for each individual event or opera- and incidents; veer-offs accounted for 48%; and undershoots tion, the reporting agency, the aircraft characteristics, the accounted for only 8% of the total number of events. runway and environmental conditions, event classification (ac- Figure 9 presents the number of incidents and accidents by cident or incident), and other relevant information such as year from 1978 to 2008. The number of events reported in the consequences (fatalities, injuries, and damage) and causal 1970s was relatively low, most likely due to underreporting or contributing factors required to develop the probability and lower volumes of traffic. The number of events increased models. A unique identifier was assigned to each event. slowly, and there is a sharp drop during the past 3 years. It is possible that some events are still undergoing the investiga- tion and that reports were not available by the time data col- Summary of Data lection was completed. Figure 7 presents the summary of accidents and incidents Figures 10 to 14 show the distribution of accidents and in- by type, and Figure 8 shows the relative percentages for each cidents according to their location. For overruns and under- type. Landing events accounted for 83% of the events. Over- shoots, the locations refer to the longitudinal distance from runs (landing and takeoffs) accounted for 44% of accidents the runway end. For veer-offs, it is the lateral distance from the runway longitudinal edge. Five hundred one landing overrun events were identified. Events by Type In approximately 95% of the events, the aircraft stopped within 1000 ft after overrunning the runway, and close to 77% stopped within 500 ft. TOOR TOVOFF 9% 8% One hundred eleven landing undershoot events were iden- tified, and in approximately 94% of the cases, the aircraft LDOR 35% touched the terrain within 1000 feet of the runway arrival end. Approximately 85% touched down within 600 feet and 80% within 500 feet. Veer-off distances were measured from the runway edge. Of the 559 cases of landing veer-off identified, in approxi- mately 80% of the cases the fuselage of the aircraft deviated less than 175 feet from the runway edge. For 88% of the events, the aircraft was within 250 feet of the runway edge. A total of 123 takeoff overrun accidents and incidents were LDVOFF identified. For approximately 83% of the cases, the stop loca- 40% LDUS tion was within 1000 feet of the runway departure end, and 8% for 56%, the aircraft stopped within 500 feet. Figure 8. Percentage of accidents and incidents Of the 120 takeoff veer-off accidents and incidents, in by type. approximately 76% of the cases the fuselage of the aircraft 11

Reported Events per Year 70

ACC 60 INC

50

40

30

20 Number of Occurrences 10

0 4 1978 1980 1982 1984 1986 1988 1990 1992 199 1996 1998 2000 2002 2004 2006 2008 Year Figure 9. Number of reported accidents and incidents from 1978 to 2008.

Location Distribution for LDOR Events Location Distribution for LDVO Events 120 70

100 60

50 80 40 60 30 # of Events 40 # of Events 20

20 10

0 0 0 50 100 300 500 700 900 100 150 200 250 300 350 400 450 500 1100 1300 1500 1700 190 More More Distance from Threshold (ft) Distance from Runway Edge (ft) Figure 10. Location distribution for landing Figure 12. Location distribution for landing overruns. veer-offs.

Location Distribution for LDUS Events Location Distribution for TOOR Events 35 30

30 25

25 20 20 15 15 # of Events # of Events 10 10

5 5

0 0

00 00 900 700 5 300 100 100 300 500 7 900 1900 1700 1500 1300 1100 Less 1100 1300 1500 1700 1900 More Distance from Threshold (ft) Distance from Threshold (ft) Figure 11. Location distribution for landing Figure 13. Location distribution for takeoff undershoots. overruns. 12

Location Distribution for TOVO Events Aircraft Data 20 One of the project goals was to incorporate a factor in the 18 models to account for the impact of aircraft performance and 16 available runway length on probability of incidents. When the 14 distance available is close to the distance required, the safety 12 margin is smaller during the aircraft landing or takeoff, and 10 the likelihood is greater that an overrun or veer-off will occur. 8

# of Events Compared to the ACRP Report 3 study, two new factors were 6 included in the improved models: the runway distance avail- 4 able for the operation (takeoff or landing) and the aircraft run- 2 way distance required under the operation conditions. The 0 runway available and required distances were gathered or esti- 0 0 5 5 50 00 100 150 200 2 300 350 400 4 5 More mated for each accident, incident, and normal operation, ac- Distance from Runway Edge (ft) cording to the procedures described in ensuing sections. The parameter introduced in the frequency models was the loga- Figure 14. Location distribution for takeoff veer-offs. rithm of the ratio between the distance required and the dis- tance available, to address the interaction between the two pa- rameters. When the criticality factor is close to zero, the ratio deviated less than 175 feet from the runway edge. In 85% of between the required and available distance is close to one. the events, the aircraft was within 250 feet of the runway edge. Aircraft dimensions and performance data were gathered from various sources, including aircraft manufacturers’ web- Normal Operations Data sites and other databases: Another key approach in this study was the use of NOD for • FAA Aircraft Characteristics Database. probability modeling. In the absence of information on risk – Source: FAA exposure, even though the occurrence of a factor (e.g., contam- – Website: (http://www.faa.gov/airports/engineering/ inated runway) could be identified as a contributor to many aircraft_char_database/) accidents, it is impossible to know how critical the factor is, • Eurocontrol Aircraft Performance Database V2.0 since many other flights may have experienced the factor with- – Source: Eurocontrol out incidents. With NOD, the number of operations that ex- perience the factor benignly, singly, and in combination can – Website: (http://elearning.ians.lu/aircraftperformance/). • be calculated; risk ratios can be generated; and the impor- FAA Aircraft Situation Display to Industry (ASDI)—Aircraft tance of risk factors can be quantified. This assessment may Types. allow the prioritization of resource allocation for safety im- – Source: FAA provement (Enders et al. 1996). – Website: (http://www.fly.faa.gov/ASDI/asdidocs/aircraft_ The same NOD used in the ACRP Report 3 study was used in types.txt). • this study. The data were complemented with information for Boeing Airplane Characteristics for Airport Planning. GA aircraft with MTOW lower than 12,500 lb and higher than – Source: The Boeing Company 6,000 lb. The NOD database comprises a large and representa- – Website: http://www.boeing.com/commercial/airports/ tive sample of disaggregate U.S. NOD covering a range of risk plan_manuals.html • factors, allowing their criticality to be quantified. The data and Airbus Airplane Characteristics for Airport Planning. the information on U.S. incidents and accidents were used as a – Source: Airbus Industrie sample to develop the frequency models only. A small sample – Website: airbus.com/Support/Engineering & Mainte- of the NOD used in this study is presented in Appendix C. nance/Technical data/Aircraft Characteristics • Incorporating this risk exposure information into the acci- Embraer Aircraft Characteristics for Airport Planning. dent frequency model enhances its predictive power and pro- – Source: Embraer vides the basis for formulating more risk-sensitive and respon- – Website: http://www.embraeraviationservices.com/ sive RSA policies. Accident frequency models need no longer english/content/aeronaves/ rely on simple crash rates based on just aircraft, engine, or op- eration type. As discussed in the following pages, factors pre- Aircraft performance data used to develop the probability viously ignored by airport risk assessments and RSA regulations models also were incorporated into the analysis software. A are accounted for using the models developed in this study. summary of the aircraft database is presented in Appendix D. 13

CHAPTER 3 Modeling RSA Risk

The analysis of RSA risk requires three models that con- in the terrain or into a water body adjacent to the RSA. In ad- sider probability (frequency), location and consequences. The dition, it takes into consideration the type of obstacle and the outcome of the analysis is the risk of accident during runway estimated collision speed to cause severe consequences. For excursions and undershoots. The three model approach is example, an aircraft colliding with a brick building may result represented in Figure 15. in severe consequences even at low speeds; however, the air- The first model is used to estimate the probability that an craft must be at a higher speed when striking a Localizer an- event will occur given certain operational conditions. This tenna mounted on a frangible structure for a similar level of probability does not address the likelihood that the aircraft severity. The collision speed is evaluated based on the loca- may strike an obstacle or will stop beyond a certain distance. tion of the obstacle and the typical aircraft deceleration for The model uses independent variables associated with causal the type of RSA terrain. The ensuing sections provide details and contributing factors for the incident. For example, under for each component of the risk model. The same model is used tailwind conditions it is more likely that an overrun will occur, for all five types of events (LDUS, LDOR, LDVO, TOOR, and this is one of the factors used in the models for overruns. and TOVO.) The aircraft performance is represented by the interaction be- The remainder of this chapter discusses the probability tween the runway distance required by the aircraft for the and location models. The consequence model is discussed in given conditions and the runway distance available at the air- Chapter 4. port. Although human and organizational factors are among the most important causes of aircraft accidents, it was not pos- Event Probability (Frequency Model) sible to directly incorporate these factors into the risk models. Since this model is specific for the event type, five different Similar to ACRP Report 3 model development procedures, models are required, e.g., one for landing overruns and another backward stepwise logistic regression was used to calibrate one for takeoff overruns. five frequency models, one for each type of incident: LDOR, The second component is the location model. The analyst LDUS, LDVO, TOVO, and TOOR. Various numerical tech- usually is interested in evaluating the likelihood that an air- niques were evaluated to conduct the multivariate analysis, craft will depart the runway and stop beyond the RSA or and logistic regression was the preferred statistical procedure strike an obstacle. The location model is used to estimate the for a number of reasons. This technique is suited to models probability that the aircraft stops beyond a certain distance with a dichotomous outcome (accident and non-accident) from the runway. As pointed out in ACRP Report 3 and by with multiple predictor variables that include a mixture of Wong (2007), the probability of an accident is not equal for all continuous and categorical parameters. Also, it is particu- locations around the airport. The probability of an accident in larly appropriate for case-control studies because it allows the proximity of the runways is higher than at larger distances the use of samples with different sampling fractions, depend- from the runway. Since this model is specific for the event ing on the outcome variable without giving biased results. type, five different models are required, e.g., one for landing Backward stepwise logistic regression was used to calibrate overruns and another one for takeoff overruns. the frequency models because of the predictive nature of the The last part is the consequence model. This model uses research, and the technique is able to identify relationships the location models to assess the likelihood that an aircraft missed by forward stepwise logistic regression (Hosmer and will strike an obstacle or depart the RSA and fall into a drop Lemeshow 2000). 14

Three-Part Risk Model

Event Location Consequences probability probability

operating conditions (airplane performance, type of RSA characteristics, type, size and operation, runway distance geometry, location of available and elevation, presence of EMAS obstacles weather conditions)

Risk Classification

Figure 15. Modeling approach.

To avoid the negative effects of multi-co-linearity on the the actual runway had not been identified for the NOD. The model, correlations between independent variables were first research team has gathered information on the runways used, tested to eliminate highly correlated variables, particularly if and the process allowed the calculation of the head/tailwind they did not significantly contribute to explaining the varia- components to be included in the model. tion of the probability of an accident. Another major improvement that has increased model ac- The basic model structure selected is a logistic equation, as curacy was the inclusion of a runway criticality factor. The follows: basic idea was to include a new parameter that could repre- sent the interaction between the runway distance required by 1 the aircraft and the runway distance available at the airport. P{} Accident_ Occurence = 1+ ebbXbXbX0112233++ + + ... The log of the ratio between the distance required and the dis- tance available was used. Positive values represent situations where when the distance available was smaller than the distance re- P{Accident_Occurrence} = the probability (0–100%) of an quired, and in this case, risk will be higher. The greater the accident type occurring given value is, the more critical is the operation because the safety certain operational conditions; margin decreases. The distance required is a function of the aircraft perform- Xi = independent variables (e.g., ceiling, visibility, crosswind, ance under specific conditions. Therefore, every distance re- precipitation, aircraft type, cri- quired under International Standards Organization (ISO) ticality factor); and conditions (sea level, 15 degrees centigrade) was converted to actual conditions for operations. Moreover, the distances bi = regression coefficients. were adjusted for the runway surface condition (wet, snow, Several parameters were considered for inclusion in the slush, or ice) and for the level of head/tailwind. The adjust- models. The backward stepwise procedure helps identify those ment factors applied to the distance required are presented in variables that are relevant for each type of event. Some of the Table 2. A correction for slope was not applied to adjust the independent variables are converted to binary form to avoid total distance required. spurious effects of non-linear relationships in the model ex- The use of NOD in the accident frequency model was a ponent. These binary variables are represented by only two major improvement introduced by Wong et al. (2006) and values, 0 or 1. In this case, the presence of the factor (e.g., rain) was maintained for this study. The analysis with NOD also is represented by 1, and the absence of the factor (e.g., no rain) adds to the understanding of cause-result relationships of the is represented by 0. five accident types. One significant improvement relative to the models pre- The technique used to develop the models is able to iden- sented in ACRP Report 3 is the use of tailwind and headwind. tify relationships missed by forward stepwise logistic regres- These variables were not present in previous models because sion (Hosmer and Lemeshow 2000). The predictor variables 15

Table 2. Adjustment factors used to correct required distances.

Local Factor Unit Reference Adjustment (i) Elevation (E) 1000 ft E = 0 ft (sea level) Fe = 0.07 x E + 1 (i) Temperature (T) deg C T = 15 deg C Ft = 0.01 x (T – (15 – 1.981 E) + 1 (ii) Tailwind (TWLDJ) for knot TWLDJ = 0 knot FTWJ = (RD + 22 x TWLDJ)/RD Jets (iii) Tailwind (TWLDT) for knot TWLDT = 0 knot FTWJ = (RD + 30 x TWLDT)/RD Turboprops (iii) Headwind (HWTOJ) for knot HWTOJ = 0 knot FTWJ = (RD + 6 x HWTOJ)/RD Jets (iii) Headwind (HWTOT) for knot HWTOJ = 0 knot FTWJ = (RD + 6 x HWTOT)/RD Turboprops (iii) Runway Surface Condition Yes/No Dry FW = 1.4 – Wet (W) (iv) Runway Surface Condition Yes/No Dry FS = 1.6 – Snow (S) (iv) Runway Surface Condition Yes/No Dry FSl = 2.0 – Slush (Sl) (iv) Runway Surface Condition Yes/No Dry FI = 3.5 – Ice (I) (iv) i – RD is the runway distance required in feet ii – temperature and elevation corrections used for runway design iii – correction for wind are average values for aircraft type (jet or turboprop) iv – runway contamination factors are those suggested by Flight Safety Foundation

were entered by blocks, each consisting of related factors, such curves were defined for each model to calculate the C-value. that the change in the model’s substantive significance could An example of this assessment is shown in Figure 16 repre- be observed as the variables were included. Table 3 summarizes senting the model for landing overruns. The area under the the model coefficients obtained for each model. curve for this model represents the C-value and is 87.4%. The Table 4 summarizes the parameters representing the ac- C-values for each of the five models developed were above curacy of each model obtained. The table presents the R2 78% and are considered excellent models. and C-values for each model. It is important to note that rel- The cut-off point is the critical probability above which the atively low R2 values are the norm in logistic regression (Ash model will class an event as an accident. The ROC curve plots and Schwartz 1999) and they should not be compared with all potential cut-off points according to their respective True the R2 of linear regressions (Hosmer and Lemeshow 2000). Positive Rates and False Positive Rates. The best cut-off point A better parameter to assess the predictive capability of a has an optimally high sensitivity and specificity. logistic model is the C-value. This parameter represents the area under the sensitivity/specificity curve for the model, Event Location Models which is known as Receiver Operating Characteristic (ROC) curve. The accident location models are based on historical acci- Sensitivity and specificity are statistical measures of the per- dent data for aircraft overruns, veer-offs, and undershoots. formance of a binary classification test. Sensitivity measures The accident location for overruns depends on the type of ter- the proportion of true positives that are correctly identified as rain (paved or unpaved) and if EMAS is installed in the RSA. such (the percentage of accidents and incidents that are cor- When EMAS is available, during landing and takeoff over- rectly identified when using the model). Specificity measures runs, the aircraft will stop at shorter distances, and typical de- the proportion of true negatives that are correctly identified celeration for the type of aircraft is used to assess the location (the percentage of normal operations that the model can cor- probability. rectly identify as non-incident). These two measures are closely Worldwide data on accidents and incidents were used to related to the concepts of Type I and Type II errors. A theoret- develop the location models. The model structure is similar to ical, optimal prediction can achieve 100% sensitivity (i.e., pre- the one used by Eddowes et al. (2001). Based on the accident/ dict all incidents) and 100% specificity (i.e., not predict a incident location data, five sets of complementary cumulative normal operation as an incident). A perfect model has a C-value probability distribution (CCPD) models were developed. With equal to 1.00. CCPDs, the fraction of accidents involving locations exceeding To assess how successful the models are in classifying flights a given distance from the runway end or threshold can be esti- correctly as “accident” or “normal” and to find the appropri- mated. When the CCPD is multiplied by the frequency of ac- ate cut-off points for the logistic regression models, the ROC cident occurrence, a complementary cumulative frequency 16

Table 3. Independent variables used for frequency models.

Variable LDOR LDUS LDVO TOOR TOVO Adjusted Constant -13.065 -15.378 -13.088 -14.293 -15.612 User Class F 1.693 1.266 User Class G 1.539 1.288 1.682 2.094 User Class T/C -0.498 0.017 Aircraft Class A/B -1.013 -0.778 -0.770 -1.150 -0.852 Aircraft Class D/E/F 0.935 0.138 -0.252 -2.108 -0.091 Ceiling less than 200 ft -0.019 0.070 0.792 Ceiling 200 to 1000 ft -0.772 -1.144 -0.114 Ceiling 1000 to 2500 ft -0.345 -0.721 Visibility less than 2 SM 2.881 3.096 2.143 1.364 2.042 Visibility from 2 to 4 SM 1.532 1.824 -0.334 0.808 Visibility from 4 to 8 SM 0.200 0.416 0.652 -1.500 Xwind from 5 to 12 kt -0.913 -0.295 0.653 -0.695 0.102 Xwind from 2 to 5 kt -1.342 -0.698 -0.091 -1.045 Xwind more than 12 kt -0.921 -1.166 2.192 0.219 0.706 Tailwind from 5 to 12 kt 0.066 Tailwind more than 12 kt 0.786 0.98 Temp less than 5 C 0.043 0.197 0.558 0.269 0.988 Temp from 5 to 15 C -0.019 -0.71 -0.453 -0.544 -0.42 Temp more than 25 C -1.067 -0.463 0.291 0.315 -0.921 Icing Conditions 2.007 2.703 2.67 3.324 Rain 0.991 -0.126 0.355 -1.541 Snow 0.449 -0.25 0.548 0.721 0.963 Frozen Precipitation -0.103 Gusts 0.041 -0.036 0.006 Fog 1.74 Thunderstorm -1.344 Turboprop -2.517 0.56 1.522 Foreign OD 0.929 1.354 -0.334 -0.236 Hub/Non-Hub Airport 1.334 -0.692 Log Criticality Factor 9.237 1.629 4.318 1.707 Night Conditions -1.36

Where:

Ref: Equipment Class C Large jet of MTOW 41k-255k lb (B737, A320 etc.) Heavy Acft AB Heavy jets of MTOW 255k lb+ (B777, A340, etc.) Large commuter of MTOW 41k-255k lb (Regional Jets, Commuter Acft D ERJ-190, CRJ-900, ATR42, etc.) Medium aircraft of MTOW 12.5k-41k lb (biz jets, Medium Acft E Embraer 120, Learjet 35 etc.) Small Acft F Small aircraft of MTOW 12.5k or less (small, Beech-90, Caravan, etc.) User Class Ref: C = Commercial User Class F Cargo User Class T/C Taxi/Commuter User Class G General Aviation Foreign OD Foreign origin/destination (yes/no) - Ref: domestic Ceiling (feet) Ref: Ceiling Height > 2500 ft Visibility (Statute Miles) Ref: Visibility > 8 SM Crosswind (knots) Ref: Crosswind < 2 kt Tailwind (knots) Ref: Tailwind < 5 kt Gusts (knots) Ref: No gusts Thunderstorms (yes/no) Ref: No thunderstorms Icing Conditions (yes/no) Ref: No icing conditions Snow (yes/no) Ref: No snow Rain (yes/no) Ref: No rain Fog (yes/no) Ref: No fog Air Temperature (deg C) Ref: Air temperature above 15 C and below 25C Non-Hub Airport (yes/no) Ref: Hub airport Log Criticality Factor If Log(CF) > 0, available runway distance is smaller than required distance Notes: Ref : indicates the reference category against which the odds ratios should be interpreted. Non-hub airpor t : airport having less than 0.05% of annual passenger boardings. 17

Table 4. Summary statistics for x frequency models.

Model R2 C LDOR 0.28 0.87 y LDUS 0.14 0.85 LDVO 0.32 0.88 TOOR 0.11 0.78 TOVO 0.14 0.82 Figure 17. X-Y origin for aircraft overruns. distribution (CCFD) is obtained. The latter quantifies the over- For the transverse distribution, the same model structure all frequency of accidents involving locations exceeding a given was selected. However, given the accident’s transverse loca- distance from the runway boundaries. tion for aircraft overruns and undershoots, in general, is Figures 17 to 19 show the axis locations used to represent not reported if the wreckage location is within the extended each type of incident. The reference location of the aircraft is runway lateral limits, it was necessary to use weight factors to its nose wheel. For overruns and undershoots, the x-y origin reduce model bias, particularly for modeling the tail of the is the centerline at the runway end. For veer-offs, the y-axis probability distribution. The model can be represented by the origin is the edge of the runway, not necessarily the edge of the following equation: paved area when the runway has shoulders. {}> = −bym For the longitudinal distribution, the basic model is: PLocationy e

PLocationx{}> = e−axn where P{Location>y} = the probability the overrun/undershoot where distance from the runway border (veer- P{Location > x} = the probability the overrun/undershoot offs) or centerline (overruns and under- distance along the runway centerline be- shoots) is greater than y; yond the runway end is greater than x; y = a given location or distance from the x = a given location or distance beyond the extended runway centerline or runway runway end; and border; and a, n = regression coefficients. b, m = regression coefficients. A typical longitudinal location distribution is presented in A typical transverse location distribution is presented in Figure 20. Figure 21, and the model parameters are presented in Table 5.

Figure 16. ROC curve for LDOR frequency model. 18

x

y

Figure 18. X-Y origin for aircraft undershoots.

length is adjusted for each type of aircraft according to MTOW and the EMAS bed length, according to the follow- ing steps: y 1. The maximum runway exit speed to hold the aircraft within the EMAS bed is calculated according to the 2 Figure 19. Y origin for aircraft veer-offs. model presented below. The adjusted R for this model is 89%.

For Table 5, the following are the parameters represented: vWS=−3. 0057 6 . 8329 log( )+ 31 . 1482 log( )

d = any given distance of interest; where: x = the longitudinal distance from the runway end; v = the maximum exit speed in m/s; P{d>x} = the probability the wreckage location exceeds dis- W = the maximum takeoff weight of the aircraft in kg; and tance x from the runway end; S = the EMAS bed length in meters. y = the transverse distance from the extended runway centerline (overruns and undershoots) or from the 2. The maximum runway exit speed estimated using the pre- runway border (veer-offs); and vious regression equation, along with the EMAS bed length P{d>y} = the probability the wreckage location exceeds dis- (SEMAS), is input in the following equation to calculate the tance y from the extended runway centerline (over- deceleration of the aircraft in the EMAS bed.

runs and undershoots) or from the runway border 2 = v (veer-offs). aEMAS 2S Figures 22–29 illustrate the models presented in Table 5. 3. The runway length factor is then estimated as follows:

EMAS Deceleration Model aEMAS RLF = aRSA The analysis tool developed in this research includes the capability to evaluate RSAs with EMAS beds. The details of 4. The runway length factor is then estimated as follows: the development are presented in Appendix E. The same location models for overruns are used when aEMAS RLF = EMAS beds are available in the RSA. However, the bed aRSA y x

n m P{Location x} e ax P{Location y} e by Probability location Exceeds Probability location Exceeds

P{Loc > x1} P{Loc > y1}

x X y y rwy end 1 Distance x from runway end rwy border 1 Distance y from runway border Figure 20. Typical model for aircraft overruns. Figure 21. Typical model for aircraft veer-offs. 19

Table 5. Summary of location models.

Type of Type of Model R2 # of Accident Data Points LDOR X 0.984941 99.8% 305 P{d x} e 0.00321x Y 0.4862 93.9% 225 P{d y} e 0.20983 y LDUS X 0.751499 98.7% 83 P{d x} e 0.01481x Y 0.773896 98.6% 86 P{d y} e 0.02159y LDVO Y 0.803946 99.5% 126 P{d y} e 0.02568y TOOR X 1.06764 99.2% 89 P{d x} e 0.00109x Y P{d y} e 0.04282y0.659566 98.7% 90

0.863461 TOVO Y P{d y} e 0.01639 y 94.2% 39

Prob=exp((-.00321)*X**(.984941)) R2=99.8% 1.0

0.8

0.6

0.4

0.2 Probability of Stopping Beyond X

0.0 0 400 800 1200 1600 2000 Distance X from Runway End (ft) Figure 22. Longitudinal location model for landing overruns.

Prob=exp((-.20983)*Y**(.486)) R2=93.9% 1.0

0.8

0.6

0.4

0.2 Probability of Stopping Beyond Y

0.0 0 200 400 600 800 1000 1200 Distance Y from Extended Runway Centerline (ft) Figure 23. Transverse location model for landing overruns. 20

Prob=exp((-.01481)*X**(.751499)) R2=98.7% 1.0

0.8

0.6

0.4

0.2 Probability of Touching Down Before X

0.0 0 400 800 1200 1600 2000 Distance X from Runway Arrival End (ft) Figure 24. Longitudinal location model for landing undershoots.

Prob=exp((-.02159)*Y**(.773896)) R2=98.6% 1.0

0.8

0.6

0.4

0.2 Probability of Touching Down Beyond Y

0.0 0 200 400 600 800 1000 Distance Y from Runway Extended Centerline (ft) Figure 25. Transverse location model for landing undershoots. 21

Prob=exp((-.02568)*Y**(.803946)) R2=99.5% 1.0

0.8

0.6

0.4

0.2 Probability of Stopping Beyond Y

0.0 0 200 400 600 800 1000 Distance Y from Runway Edge (ft) Figure 26. Lateral location model for landing veer-offs.

Prob=exp((-.00109)*X**(1.06764)) R2=99.2% 1.0

0.8

0.6

0.4

0.2 Probability of Stopping Beyond X

0.0 0 400 800 1200 1600 2000 Distance X from Runway End (ft) Figure 27. Longitudinal location model for takeoff overruns. 22

Prob=exp((-.04282)*Y**(.659566)) R2=98.7% 1.0

0.8

0.6

0.4

0.2 Probability of Stopping Beyond Y

0.0 0 200 400 600 800 1000 Distance Y from Extended Runway Centerline (ft) Figure 28. Transverse location model for takeoff overruns.

Prob=exp((-.01639)*Y**(.863461)) R2=94.2% 1.0

0.8

0.6

0.4

0.2 Probability of Stopping Beyond Y

0.0 0 200 400 600 800 1000 Distance Y from Runway Edge (ft) Figure 29. Lateral location model for takeoff veer-offs.

5. The equivalent length of conventional RSA is then cal- Accuracy of Models culated: There were five multivariate logistic frequency models, eight a exponential location models, and one log linear deceleration ==EMAS g SRSA SRLFSEMAS EMAS model developed in this study. The accuracy of these models is aRSA considered excellent, with C-values ranging from 0.78 to 0.88 With the equivalent RSA length, the RSA is adjusted for each for the frequency models. The location models had R2 values type of aircraft and is input into the standard location models ranging from 93.9% to 99.8%, and the deceleration model for presented in the previous section. EMAS presented an adjusted R2 of 89%. 23

CHAPTER 4 Consequence Approach

Risk is the likelihood of the worst credible consequence for with the probability of aircraft overruns and undershoots for a hazard. Many overruns, veer-offs, and undershoots have an assessment of risk. The approach is rational because it is resulted in aircraft hull loss and multiple fatalities, and there- based on physical and mathematical principles. fore, the worst credible level of consequences may be assumed to be catastrophic, according to the severity classification defined by the FAA and presented in Appendix F. Modeling Approach for Risk In some situations, a pilot may lose control of the aircraft, The basic idea was to assess the effect of different obstacles resulting in the destruction of the equipment with possible at various locations in the vicinity or inside the RSA. The fatalities, even when the aircraft accident takes place inside approach integrates the probability distributions defined by the RSA or the runway; however, in the majority of accidents, the location models with the location, size, and characteristics the RSA will offer some protection to mitigate consequences. of existing obstacles in the RSA and its vicinity. Consequences will depend on the type of structures and the The implementation of the approach required some simpli- level of energy during the aircraft collision. Possible obstacles fying assumptions so that it could be integrated with the fre- may include buildings, ditches, highways, fences, pronounced drops in terrain, unprepared rough terrain, trees, and even quency and location models. The following are the assumptions navigational aids (NAVAID) structures, like approach lighting used: system (ALS) towers and Localizer antennas, particularly if mounted on sturdy structures. 1. Aircraft overrunning, undershooting, or veering off the The energy of the aircraft during the collision is related to runway will strike the obstacle in paths parallel to the run- its speed when it strikes the obstacle, i.e., the greater speeds way direction. This assumption is necessary to define the are expected to result in more severe consequences. Also, the area of influence of the obstacle. consequences will depend on the type of obstacle. An aircraft 2. Four categories of obstacles are defined as functions of the striking a brick building at 40 mph may be destroyed whereas maximum speed that an aircraft may collide with an ob- if the obstacle is a perimeter fence less severe consequences stacle, with small chances of causing hull loss and injuries to are expected to occur. its occupants: The variables assumed to have an impact on consequences a. Category 1: Maximum speed is nil (e.g., cliff at the RSA resulting from overruns, veer-offs, and undershoots are: border, concrete wall). b. Category 2: Maximum speed is 5 knots (e.g., brick • Obstacle type, size, and location; buildings). • Aircraft size (wingspan) and speed; and c. Category 3: Maximum speed is 20 knots (e.g., ditches, • Number of obstacles and location distribution (shadowing). fences). d. Category 4: Maximum speed is 40 knots (e.g., frangible The basic approach is that presented in ACRP Report 3, as structures, ALS). summarized in the ensuing sections. Additional details on how 3. Severe damage and injuries are expected only if the aircraft it was incorporated in the analysis are provided. The approach collides within the central third of the wingspan and with a described in ACRP Report 3 was intended to model accident speed higher than the maximum for that obstacle category. and incident consequences so that they could be combined The concept is explained in the ensuing section. 24

4. The lateral distribution is random and does not depend on There are three distinct regions in this plot. The first re- the presence of obstacles. This is a conservative assumption gion (green) represents overruns that the aircraft departed because there are events when the pilot will avoid the ob- the runway but the exit speed was relatively low and the air- stacles if he has some directional control of the aircraft. craft came to a stop before reaching the existing obstacle. The accident/incident database contains a number of cases The consequences for such incidents associated with that when the pilot avoided ILS and ALS structures in the RSA. specific obstacle are expected to be none if the x-location is

smaller than D0. The main purpose of modeling consequences of aircraft ac- The rest of the curve represents events that the aircraft ex- cidents is to obtain an assessment of risk based on the likelihood ited the runway at speeds high enough for the wreckage path for the worst credible consequence. It was not deemed neces- to extend beyond the obstacle location. However, a portion sary to develop a consequence model for each type of accident, of these accidents will have relatively higher energy and should as was done to model frequency and location. The approach can result in more severe consequences, while for some cases the be used to address any of the five types of incidents included aircraft will be relatively slow when hitting the obstacle so that in the analysis. catastrophic consequences are less likely to happen. Using the

The basic idea is to use the location models to estimate the location model, if x-location is between D0 and D0+Δ, it may incident occurrences for which the aircraft will have high en- be assumed that no major consequences are expected if the ergy when striking an obstacle, thus resulting in serious con- obstacle is present. sequences. It should be noted that neither of the models used The value of Δ is estimated based on aircraft deceleration in the approach provides an estimate of the aircraft speed; over different types of terrain (paved, unpaved, or EMAS) however, using the location model and the average aircraft and crashworthiness speed criteria for aircraft. It should be deceleration during a runway excursion, it is possible to infer noted that Δ depends on the type of terrain, type and size of the probability that the speed is above a certain level when aircraft, and type of obstacle. Frangible objects in the RSA are reaching the obstacle. Figure 30 is used to illustrate the case less prone to causing severe consequences. It also should be for overruns and help understand the principle. This approach noted that lighter aircraft may stop faster and the landing gear was introduced in ACRP Report 3. configuration also may have an effect on the aircraft deceler- The x-axis represents the longitudinal location of the wreck- ation in soft terrain, but these factors are not accounted for in age relative to the runway departure end. The y-axis is the prob- this approach. ability that the wreckage location exceeds a given distance “x.” Using this approach, it is possible to assign three scenarios:

In this example, an obstacle is located at a distance D0 from the probability that the aircraft will not hit the obstacle (green the departure end, and the example scenario being analyzed region—resulting in none or minor consequences); the prob- is an aircraft landing overrun incident. Figure 30 shows an ex- ability that the aircraft will hit the obstacle with low speed and ponential decay model developed for the specific accident energy (yellow region—with substantial damage to aircraft but scenario, in this case, landing overruns. minor injuries); and the probability that the aircraft will hit the obstacle with high energy (orange region—with substantial damage and injuries). For those events with low energy when impacting the ob- stacle, it is possible to assume that, if no obstacle was present, Δ x the aircraft would stop within a distance from the location of the obstacle. The problem is then to evaluate the rate of Prob of Incident with d < Do P{d < Do } = 10 0% - P{d > Do } these accidents having low speeds at the obstacle location, Probability d Exceeds and this is possible based on the same location model. This Prob of Incident with d > Do P{d> D } low energy probability can be estimated by excluding the cases when the o P = P{d > D } - P{d > D + } low o o speed is high and the final wreckage location is significantly Prob of Incident with d > D + P{d > Do + } o beyond the obstacle location. high energy

Phigh = P{d > D o + } To complement the approach it is necessary to combine the longitudinal and transverse location distribution with the D D + o o Distance x from runway end presence, type, and dimensions of existing obstacles. The basic approach is represented in Figure 31 for a single and simple Do is distance to Obstacle, d is distance the aircraft came to stop

Area (yellow) between Do and D o + represents % occurrences at obstacle. low speed (energy) when hitting obstacle (low consequences) Laterally, if part of the obstacle is within the yellow zone, as Figure 30. Approach to model consequences of over- shown in Figure 32a, medium consequences are expected; how- run accidents. ever, if any part of the obstacle is within the orange zone, as 25

Combining this approach with the longitudinal distribution RSA y2 approach and the possibility of multiple obstacles, the risk for y x 1 accidents with severe consequences can be estimated using the following model: x (dist. to obstacle)

y m − m N ( −by by fi ) eeci − n = −+ax( iiΔ ) Figure 31. Modeling consequences. Psc ∑ e i=1 2

where shown in Figure 32b, and the speed is high, severe consequences N = the number of existing obstacles; are expected. If the obstacle is off the orange and yellow zones, a, n = regression coefficients for the x-model; and no consequences related to that obstacle are expected. Δι = the location parameter for obstacle i. In Figure 33, Obstacle 1 is located at a distance x1, y1 from Multiple obstacles may be evaluated using the same prin- the threshold and has dimensions W1 × L1. When evaluating the possibility of severe consequences, it is possible to assume this ciple. A shadowing effect also is taken into account when part + will be the case if the aircraft fuselage or a section of the wing of obstacle i 1 is behind obstacle i. Because it is assumed that close to the fuselage strikes the obstacle at high speed. Thus, aircraft will travel in paths parallel to the runway centerline, it is possible to assume the accident will have severe conse- any portion of the obstacle located behind at a distance greater than Δi is disregarded from the analysis. quences if the y location is between yc and yf, as shown in the figure. Based on the location models for lateral distance, the A quantitative assessment of risk likelihood will be obtained probability the aircraft axis is within this range can be calcu- as a function of operating conditions (aircraft, weather, runway lated as follows: distances available) and RSA dimensions and conditions (pres- ence of EMAS, presence, location, size, and type of obstacles, m −bym ee−byc − f etc.). For the analysis, the user may select the alternative to Psc = 2 evaluate the probability that an aircraft will go off the RSA or that severe consequences will take place. where = Psc the probability of high consequences; Implementation of Approach b, m = regression coefficients for the y-location model;

yc = the critical aircraft location, relative to the obstacle, The implementation of the proposed approach is best ex- closest to the extended runway axis; and plained using one example. Figure 34 depicts an area adjacent

yf = the critical aircraft location, relative to the obstacle, to the runway end with two obstacles. The area isn’t necessar- farther from the extended runway axis. ily the official airport RSA but any available area that can be

Wingspan (WS)

1/3 WS

a) Obstacle

Wingspan (WS)

1/3 WS

b) Obstacle

Figure 32. Lateral location versus consequences. 26

Lateral Location Probability Distribution

Pscsc

Obstacle

y

w1

yc yf Figure 33. Modeling likelihood of striking an obstacle.

Cliff

Obstacle 1 - Building x1 Category 2 x

Obstacle 2 - Tree Category 4 y x2

Figure 34. RSA scenario with obstacles. used by an aircraft overrunning the runway end. The example combined in a manner similar to that for the analysis without shows the safety area surrounded by a cliff limiting its bound- obstacles; however, the safety area is transformed to account aries. Obstacle 1 is not frangible and is classified as a Category 2 for the presence of the obstacles, as shown in Figure 35. obstacle (e.g., building), maximum collision speed of 5 knots, The area used to calculate the probability as a function of located at distance x1 from the runway end. For this obstacle, the aircraft stopping location is shown in green. It should be the maximum speed without severe consequences is estimated noted that the safety area in the shadow of Obstacle 1 is much to be 5 knots. A second obstacle is a small size tree classified as larger than that for Obstacle 2 for three reasons: Category 4, maximum speed of 40 knots, and located at dis- tance x2 from the runway end. The remaining safety area is de- 1. Obstacle 1 is wider than Obstacle 2. fined by the cliff surrounding the RSA and such boundary is 2. The maximum speed for striking Obstacle 1 (Category 2) classified as Category 1, maximum speed of 0 knots. is lower than that for Obstacle 2 (Category 4). The typical aircraft deceleration in unpaved surfaces is 0.22g, where g is the acceleration due to gravity (32.2 ft/s2). Using Table 6. Obstacle categories. the relationship between acceleration, velocity, and distance, Δ can be calculated as shown in Table 6. Obstacle Max Speed (ft) The Δ values presented will be used to reduce the safety Category (knots) (See Figure 30) 1 0 0 area so that only the effective portion where the aircraft may 2 5 20 stop without severe damage is considered in the analysis. To 3 20 80 perform the analysis, the frequency and location models are 4 40 320 27

Cliff 22=20ft

x

44=320ft=320ft y

Figure 35. Effective RSA for analysis.

3. Obstacle 1 is located closer to the runway end, and aircraft craft wingspan. Without this simplification, a different safety speed is higher at this point than that at the location of area configuration would be required for each aircraft, greatly Obstacle 2. increasing the time to do the analysis. Using the ADG wingspan reduced the process to six steps, one for each ADG. The analysis will provide the probability that the aircraft will A second simplification was also necessary to reduce the overrun the runway and the incident will have severe conse- time to perform the analysis. Although the obstacles are cat- quences, thus providing an estimate of risk. egorized according to the maximum speed to cause severe consequences, each type of aircraft will have a different max- Additional Simplifications imum speed. However, it would be very time-consuming to apply these differences in the calculations. Therefore, the Additional simplifications were necessary to implement the maximum speed in the proposed approach depends only on approach. One such simplification was the use of maximum the type of obstacle rather than the interaction between the aircraft design group (ADG) wingspan instead of the actual air- obstacle and the aircraft. 28

CHAPTER 5 Analysis Software

Overview – Average risk for each type of incident by runway, by RSA section, and total for the airport. One of the main project goals was to develop an analysis – The expected number of years to occur an accident for tool to incorporate the approach and the models developed a user-defined annual traffic volume and growth rate. in this study. The software is called Runway Safety Area Risk – Percentage of operations subject to a probability higher Analysis (RSARA). The program and the accompanying user’s than a user-defined target level of safety (TLS). guide are available on the accompany CD with this report. In – Graphical outputs with the distribution of risk for each addition, the user’s guide is available in Appendix I. RSA and each type of event. RSARA is a Windows-based system developed to facilitate characterizing analysis conditions and entering required data. The software main screen is shown in Figure 36. Input Data Input data required to run the analysis include the follow- Software Capabilities ing information:

RSARA was tailored to help airport stakeholders evaluate • Sample of historical operations data (date and time, aircraft different RSA alternatives. The software has the following model, runway used, type of operation, etc.). capabilities: • Sample of historical weather data for the airport covering the period of sample of historical operations (wind, tem- • Performs full risk assessment for multiple runways. perature, precipitation, visibility, etc.). • Enters multiple obstacles to each RSA scenario. • Characteristics of runways (elevation, direction, declared • Characterizes different categories for obstacles. distances). • Defines and analyzes non-standard (non-rectangular) RSA • Characteristics of RSAs (geometry, type of surface, pres- geometry. ence of EMAS, location, size and category of obstacles). • Analyzes with standard and non-standard EMAS beds. • General information (airport annual traffic volume, annual • Internally integrates operations and weather data from growth rate). separate files. • Automatically converts operations and weather data into Much of the input information is arranged in table format. parameters used by probability models. Operations and weather data are entered using Microsoft Excel • Includes database of aircraft with capability to add new or templates with automatic checks for value ranges and data edit existing aircraft. format. Figure 37 shows the program screen and template to • Automatically computes runway criticality factor for each input operations data. operation. The template for drawing the RSA area for overrun and un- • Automatically corrects for required distances (landing and dershoot was created using Microsoft Excel. It consists of a can- takeoff) based on elevation, temperature, wind, and runway vas area formed by a matrix of cells. Each cell corresponds to a surface condition. coordinate that is referenced to the center of the runway. The • Generates analysis reports from software with summaries default coordinate grid is set at 10 × 10 ft. If the RSA is larger of following parameters: than the available canvas, a new scale can be set at the top of the 29

Figure 36. RSARA—main program screen.

Figure 37. Example of input screen and template. 30

Figure 38. RSA characterization using Microsoft Excel. canvas template. The user assigns a letter or number to each cell Each folder contains the risk estimates for each type of to define the type of surface or category of obstacle. After enter- incident and individual operation and the total risk during ing a code, the color of the cell will change according to the sur- landings and takeoffs. The results for each individual runway face type or obstacle entered to facilitate the visualization of the are provided in separate output Excel files. The summary drawing. Tables with the codes describing the surface types and table provides the average risk for each type of accident and obstacles available are provided in the template. Figure 38 expected number of years for an accident to occur. The accu- shows an example of RSA defined with the tool. mulated risk distribution is provided in graphical form for each section of the RSA. Output and Interpretation The results for the entire airport are provided in one output Excel file. The user must create the output files for each runway When the analyses are completed, the user may see the results prior to creating the output file for the airport. An example pre- using the Output option of the main menu. There are two senting the summary of results for the whole airport is shown types of results: runways or the consolidated results for the in Figure 39. The main table contains a summary of average risk whole airport. Within each of these options, the user can view levels for each type of incident and for all incidents. Risk levels the results for risk of events taking place outside the RSA or are shown in terms of accident rates per number of operations view the analysis output for the risk of accidents. and expected number of years to occur one accident. Additional 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. 32

CHAPTER 6 Model Validation

The improved risk models were validated by comparing less than 5600 lb and other movements non-relevant to this the results of the analysis for a sample of airports to their as- study. The volume and the number of accidents and incidents sociated historical accident rates. The eight airports listed in were used to estimate the frequency rates and accident rates Table 7 were selected using random stratified sampling tech- for each airport and type of event. niques to run the analysis with the new models and analysis The analysis software proved to work well for each case study. software; the results are compared to the actual rate of acci- There were no bugs identified during the software runs, and dents at the selected airports. None of the selected airports the results looked rational and within expected ranges for the were part of the NOD used to develop the risk models. individual airports. The analysis runs with the eight airports also served to test Table 8 contains the events for each airport occurring dur- the software. To run the risk analysis, one year of historical ing the analysis period. Figure 40 summarizes the total num- operations data were obtained for each airport. Data for air- ber of accidents and incidents occurring at the eight airports ports were collected and consolidated. Operations data were since 1981. The majority of the cases were landing veer-offs, retrieved from the FAA Operations & Performance Data and, for most types of events, the number of incidents was and Aeronautical Information Management Laboratory. The larger than the number of accidents. One notable exception weather data were obtained from the National Oceanic and was the case for TOORs. It is true that the number of cases is Atmospheric Administration (NOAA) database for the mete- quite small for a sample of eight airports; however it is notable orological stations serving each airport. that there were fewer TOOR incidents compared to accidents. Historical accident and incident information for the airport Approximately 50% of TOOR in the accident/incident data- was obtained from the NTSB, AIDS, and ASRS databases. base developed for this study were incidents, and it may be an Although the analysis was conducted to obtain risk assess- indication of higher severity for TOOR. When comparing the ment estimates, information on frequency calculated in the location models for TOOR and LDOR, the percentage of air- analysis also was used to compare expected and actual fre- craft stopping at any given distance is larger during the takeoff, quency rates for each type of incident. Similarly, actual and compared to landing overruns. estimated accident rates were compared to evaluate the need A summary of analysis results is presented in Table 9. More to make adjustments to the models. Table 8 presents the rel- details on the analysis and additional results are presented in evant accidents and incidents identified for the eight airports Appendix H. It is important to note that the RSA configurations selected. RSA’s and obstacles were characterized using satel- used for the analysis at Yeager Airport were representative of lite pictures from Google Earth, and RSA files were created conditions prior to the recent improvements that included the for each runway. extension of RSA’s and implementing EMAS. The main reason Relevant traffic volume information from 1981 to 2009 was for using these data for Yeager is that the plan was to compare estimated from information available in the FAA Air Traffic the analysis results with historical accident/incident rates. As Activity Data System (ATADS). Part of the annual air traffic expected, risk for Yeager was the highest because its RSAs volume was extrapolated to estimate the total volume for the before the recent improvements were considerably smaller sample period. An average annual growth rate of 5% was than current FAA standards. assumed for air traffic in the period between 1981 and 1999 For simplicity, all analyses were conducted using the av- when air traffic information was not available online. The erage annual operations during the past 10 years. The ex- volumes were adjusted to remove operations of aircraft with pected number of years between critical events is based 33

Table 7. List of airports for model/software validation.

State Airport Name Location ID City Hub FL Miami International MIA Miami L AK Ted Stevens Anchorage ANC Anchorage M International MO Lambert-St Louis International STL St Louis M WA Spokane International GEG Spokane S SD Joe Foss Field FSD Sioux Falls N WV Yeager CRW Charleston N AZ Deer Valley International DVT Phoenix GA FL Ft Lauderdale Executive FXE Ft Lauderdale GA

Table 8. Accidents and incidents at selected airports.

Aircraft Airport Date Country City/State Source Event Type Event Class ICAO Code Code 07/01/1981 US Saint Louis, MO NTSB LDVO Incident DC6 STL 07/24/1981 US Charleston NTSB LDUS Accident BE60 CRW 10/15/1981 US Saint Louis, MO AIDS LDVO Incident DC6 STL 2/24/1983 US Anchorage, AK AIDS LDVO Incident LJ24 ANC 10/26/1983 US Saint Louis, MO NTSB LDUS Accident CV3 STL 12/23/1983 US Anchorage, AK NTSB TOOR Accident DC10 ANC 9/28/1987 US Saint Louis, MO AIDS LDUS Incident MD80 STL 12/26/1987 US Fort Lauderdale, FL AIDS LDVO Incident AC11 FXE 10/14/1988 US Anchorage, AK AIDS LDVO Incident YS11 ANC 10/23/1989 US Anchorage, AK MITRE LDOR Incident B741 ANC 1/6/1990 US Miami, FL 4-01NTSB TOOR Accident L29A MIA 02/17/1991 US Spokane, WA NTSB LDVO Accident MU2B GEG 03/11/1993 US Saint Louis, MO NTSB LDVO Accident DC93 STL 8/28/1993 US Fort Lauderdale, FL AIDS LDVO Incident LJ23 FXE 08/29/1993 US Charleston NTSB LDOR Accident MU2B CRW 7/27/1994 US Sioux Falls, SD AIDS LDVO Incident T18 FSD 11/29/1994 US Spokane, WA AIDS TOVO Incident B731 GEG 06/23/1995 US Miami, FL NTSB LDVO Accident C402 MIA 11/19/1995 US Anchorage, AK AIDS LDUS Incident C441 ANC 12/19/1995 US Saint Louis, MO AIDS LDVO Incident DC91 STL 9/17/1996 US Miami, FL AIDS TOVO Incident BE18 MIA 11/15/1996 US Sioux Falls, SD MITRE LDOR Incident DC91 FSD 8/7/1997 US Miami, FL 4-01NTSB TOOR Accident DC85 MIA 2/19/1999 US Miami, FL 4-01ASRS LDUS Incident A30B MIA 10/15/2000 US Anchorage, AK NTSB TOOR Incident B741 ANC 10/16/2000 US Saint Louis, MO AIDS LDVO Incident MD80 STL 10/20/2000 US Saint Louis, MO ASRS LDOR Incident MD82 STL 04/07/2001 US Anchorage, AK AIDS TOVO Incident B190 ANC 01/01/2002 US Miami, FL 4-01NTSB LDOR Incident MD83 MIA 06/15/2002 US Fort Lauderdale, FL AIDS LDVO Incident SW3 FXE 12/01/2002 US Spokane, WA AIDS LDOR Incident DH8A GEG 12/20/2002 US Spokane, WA 4-01ASRS LDOR Incident DH8A GEG 8/16/1999 US Fort Lauderdale, FL MITRE LDVO Accident CL60 FXE 4/17/2003 US Fort Lauderdale, FL AIDS LDVO Incident SBR1 FXE 6/12/2003 US Fort Lauderdale, FL AIDS TOOR Incident LJ24 FXE 8/9/2003 US Fort Lauderdale, FL AIDS LDVO Incident SBR1 FXE 2/20/2004 US Fort Lauderdale, FL 4-01NTSB LDOR Accident LJ25 FXE 3/31/2004 US Fort Lauderdale, FL NTSB LDVO Accident C402 FXE 7/19/2004 US Fort Lauderdale, FL 4-01NTSB LDOR Accident LJ55 FXE 09/08/2004 US Charleston NTSB TOOR Accident C402 CRW 12/1/2005 US Sioux Falls, SD AIDS LDVO Incident SW4 FSD 6/6/2006 US Fort Lauderdale, FL AIDS TOVO Incident SW3 FXE 2/4/2007 US Miami, FL NTSB LDVO Incident DC87 MIA 11/1/2007 US Fort Lauderdale, FL AIDS LDOR Incident GLF2 FXE 1/27/2008 US Spokane, WA AIDS LDOR Incident B731 GEG 5/23/2008 US Fort Lauderdale, FL AIDS LDVO Incident SBR1 FXE 01/19/2010 US Charleston NTSB TOOR Accident CRJ2 CRW 34

25 compared to the actual frequency for the eight airports. Accidents Incidents The second step was to compare the risk levels estimated 20 Total from the analysis with the actual risk rates for the sample of airports. 15

10 Validation of Frequency Models

Number of Events 5 Figure 41 presents incident frequency rates for each type of incident and for three different estimates: the historical 0 LDOR LDUS LDVO TOOR TOVO frequency rate in the United States, the actual incident rate Type of Incident/Accident for the sample of eight airports, and the estimated frequency rate for the sample of airports. The rates for the sample Figure 40. Summary of accidents and incidents at were calculated based on the weighted average for the eight surveyed airports since 1981. airports. The actual rate represents the total number of in- cidents from 1981 to 2009 divided by the total volume of on the average annual volume of operations during the past operations during the same period. The figure shows these 10 years and the average level of risk for the entire airport, results in both graphical and tabular format. Some differ- as shown in column 5 of Table 9. A “critical event” is the ences were expected given the small sample size of eight airports focus of the analysis, and it may be an incident or an acci- surveyed. dent. When running the analysis for risk, a critical event is The results presented in Figure 41 demonstrate excellent considered a single accident or an event in which substan- agreement between the accident rates for the sample of air- tial damage to the aircraft and/or injury to passengers is the ports and the historical rate for all the airports in the United consequence. States. The results concur that the sample of airports is rep- The most critical runway end is identified based on the resentative of conditions for the population of airports in the risk of overruns and undershoots only. This risk is associated United States. The largest difference was found for landing with the operations challenging the RSA adjacent to the run- veer-offs; however, the incident rate, particularly for Fort way end. The runway end is identified based on the approach Lauderdale Executive Airport, was unusually high during the end of the runway. The last two columns of Table 9 contain analysis period. the incident type with the highest chance of occurring and The second conclusion drawn from these results is that the the associated runway. actual frequency rates for the eight airports agreed with the es- The validation effort was divided in two steps. The first timated frequency rates for this sample. It is important to note step was to determine that the eight airports selected were that frequency rates involve both accidents and incidents, with representative of conditions across the United States. Al- no distinction for the level of severity. though this is not an analysis required for validating the The plot in Figure 41 also shows excellent agreement between approach, the comparison helped gain confidence of the actual and estimated frequency values for each type of incident. applicability of the risk assessment to other airports. Also, Therefore, there is no need to recalibrate the frequency models the estimated frequency rates of the airport sample were or to apply adjustment factors.

Table 9. Summary of analysis results for airports selected for validation.

Average Annual Airport Most Frequent Avrg Avrg # of Years Highest Risk Volume of Ops No. of Incident and Associated Airport State Airport for One Accident Runway for Past 10 yrs Runways Runway *** Risk to Occur End** (in 2009) Incident Type Rwy ANC AK 293K (290K) 3 2.1E-07 16 14 LDVO 14/32 CRW* WV 50K (71K) 2 5.5E-06 17 15 LDOR 15 FSD SD 69K (86K) 2 3.1E-07 38 15 LDOR 15 FXE FL 169K (261K) 2 8.3E-07 13 31 LDOR 31 GEG WA 82K (81K) 2 4.1E-07 33 21 LDVO 03/21 STL MP 209K (226K) 4 1.8E-07 28 24 LDVO 06/24 DVT AZ 153K (376K) 2 3.7E-07 15 07L TOVO 07L/25R MIA FL 380K (384K) 4 1.4E-07 19 30 LDVO 12/30 * Risk estimated for condition before RSA improvements completed in 2007. ** Runway end with highest probability of overruns and undershoots only. *** Incident with highest probability of occurrence. 35

1.4E-06 U.S. Historical 1.2E-06 Actual for Sample 1.0E-06 Estimated for Sample 8.0E-07 6.0E-07 4.0E-07

Incident Rate (inc/ops) 2.0E-07 0.0E+00 LDOR LDUS LDVO TOOR TOVO U.S. Historical 9.5E-07 2.4E-07 1.2E-06 2.4E-07 2.6E-07 Actual for Sample 5.8E-07 2.6E-07 1.1E-06 3.7E-07 2.1E-07 Estimated for Sample 1.2E-06 2.9E-07 7.0E-07 3.1E-07 2.6E-07 Type of Incident Figure 41. Actual frequency of incidents for sample of air- ports compared to historical rates.

Validation of Risk Model of any type divided by the total number of operations in the pe- riod evaluated is the actual accident rate for the airport. The second part of the validation effort consisted of the com- Comparison of the actual rate for each type of accident at parison of actual risk rates with those estimated for the sam- each airport is not very helpful because the number of events ple of eight airports. The estimated risk is associated with the is relatively low, given the sample size of airports used in the likelihood of an accident, rather than an incident. According validation. Therefore, the analysis consisted of comparing the to NTSB, accident is defined as an occurrence associated with rates for the whole sample of eight airports. The comparison is the operation of an aircraft where as a result of the operation, made for each type of accident and for the total accident rate. any person receives fatal or serious injury or any aircraft re- The first analysis compared the proportion between acci- ceives substantial damage. This is also the definition used in dents and the total number of incidents. This was an impor- this report to characterize an aircraft accident. tant analysis to validate the consequence approach developed Data presented in Table 8 contain the accidents that took in this study. Three types of ratios were calculated for each place at the eight sample airports from 1981 to 2009. The ratio type of accident: the estimated ratio for the sample of eight between the actual number of accidents in that period divided airports, the actual ratio for the sample, and the historical by the volume of landings or takeoffs at the airport provides the ratio in the United States. The results are shown in Figure 42 actual rate for each type of event. The total number of accidents in both graphical and tabular form.

80% U.S. Historical 70% Actual for Sample 60% Estimated for Sample 50% 40% 30% 20%

Risk vs Frequency Ratio 10% 0% LDOR LDUS LDVO TOOR TOVO Total U.S. Historical 24.7% 48.5% 18.6% 50.0% 18.0% 25.7% Actual for Sample 27.3% 40.0% 25.0% 71.4% 0.0% 31.9% Estimated for Sample 31.6% 22.4% 25.6% 27.9% 30.1% 28.5% Type of Accident Figure 42. Percentage of accidents to the total number of incidents. 36

4.5E-07 U.S Historical 4.0E-07 Actual for Sample 3.5E-07 Estimated for Sample 3.0E-07 2.5E-07 2.0E-07

Average Risk 1.5E-07 1.0E-07 (accidents/operations) 5.0E-08 0.0E+00 LDOR LDUS LDVO TOOR TOVO Total U.S Historical 2.3E-07 1.2E-07 2.2E-07 1.2E-07 4.7E-08 3.7E-07 Actual for Sample 1.6E-07 1.1E-07 2.6E-07 2.6E-07 0.0E+00 4.0E-07 Estimated for Sample 3.7E-07 6.4E-08 1.8E-07 8.6E-08 7.9E-08 3.9E-07 Type of Accident Figure 43. Percentage of accidents to the total number of incidents.

Again, the results are in excellent agreement with the excep- number of accidents for the sample. The last analysis for valida- tion of the ratio for TOVO since none of the airports included tion was the comparison of actual and estimated risk levels for in the sample had this type of incident. This can be attributed to the sample of airports. The results are presented in Figure 43. chance, since the estimate is in good agreement with the his- Again, the results between estimated and actual values are torical level in the United States. The number of accidents is in excellent agreement. The validation study demonstrates very low when using only eight airports, and larger variations the applicability of the approach and the models developed in were expected when comparing the parameters based on the this study. 37

CHAPTER 7 Conclusions and Recommendations for Further Research

RSA standards have changed over the years to improve 3. Develop a practical approach to assess the impact of: runway safety, but many existing airports were built under older, less distance available on the probability of overruns, under- demanding standards. To comply with the current standards, shoots, and veer-offs; the availability of EMAS as an alterna- some airports face enormous challenges due to physical, eco- tive to standard RSAs; the use of declared distances; and the nomical, and environmental restrictions. presence of obstacles in the RSA or its vicinity. Safety levels associated with the protection provided by 4. Develop user-friendly software that incorporates the meth- RSA’s can be different from airport to airport. Two airports odology and models developed as a practical tool that air- with similar runway lengths and RSA configurations may have port stakeholders may use to evaluate RSA alternatives. very different conditions related to operations and weather. 5. Field test the software developed and validate the new tool Factors like aircraft model, runway elevation, visibility condi- and models based on data gathered according to an airport tions, and availability of NAVAID’s also have an impact on the survey plan. risk of each operation. When airports do not comply with the RSA standards and Each of these goals was accomplished, and the major there is a need to improve existing conditions, it is necessary achievements are presented below. to evaluate the alternatives that can be most effective to reduce risk and compare the safety levels achieved and the associated costs for each option. Major Achievements The objective of this study was to develop a software tool Extended Database of Accidents that can be used for risk assessments associated with incidents and Incidents occurring in the RSA. The basis of the approach used in this study was presented The database developed under the study presented in ACRP in ACRP Report 3. Analysis capabilities were enhanced by Report 3 included 459 aircraft overrun and undershoot acci- improving the risk models to address the analysis of runway dents and incidents occurring from 1980 to 2006. The database declared distances, the use of EMAS, and incorporating the was expanded significantly to 1414 events with the inclusion approach to evaluate the presence of obstacles in or in the of overruns and undershoots occurring from 2006 to 2009, vicinity of the RSA. In addition, it is now possible to evalu- and the addition of veer-off events and information provided ate the risk of aircraft veer-off in the lateral sections of the by MITRE. RSA. The result is a powerful tool to help the aviation indus- Additional events were identified using a manual search of try perform risk assessments. the FAA incident databases and the accidents and incidents in- The major goals of this study can be summarized as follows: volving GA aircraft with MTOW between 5,600 and 12,000 lb, which had been excluded from the ACRP Report 3 study. 1. Update the ACRP Report 3 accident/incident database to The comprehensive database is organized with editing and incorporate aircraft overrun and undershoot accidents querying capabilities, and information is available according and incidents occurring after 2006 and include runway to different categories including synopsis of the event, air- veer-off events occurring since 1980. craft involved, airport and weather characteristics, level of 2. Develop risk models for frequency and location for each consequences, wreckage location, and major causal and con- type of incident. tributing factors. 38

Development of Improved Risk Models Development of Software Tool The models presented in ACRP Report 3 were improved, The approach and the improved models were integrated and new ones to address veer-offs were developed. Five sets into analysis software for risk assessment of RSA. The tool, of frequency and location models were developed, including called RSARA, is user-friendly and practical, and allows the models for LDOVs, LDVOs, LDUSs, TOORs, and TOVOs. user to consider each of the factors impacting RSA risk. These types of events constitute the great majority of aircraft The software works as a simulation tool to estimate risk for incidents that challenge the runway RSA. each operation from an annual sample of operations for an New data and new factors were incorporated into the new airport. The historical sample data include flight operations models. Two of the most important ones were the runway data, like aircraft model, runway used, and the type of oper- criticality factor and the tail/head wind component. The run- ation, as well as the weather conditions to which each of these way criticality factor was defined as the ratio between the run- operations was subjected. way distance required and the runway distance available for Within the software, the definition of RSA areas is a very the operation. The higher this value is, the smaller is the safety simple process based on Microsoft Excel spreadsheets. The margin for the operation, and it represents the relationship procedure is as easy as drawing the RSA in a plan view and between the runway and aircraft performance. defining the RSA surface type: unpaved, paved, or EMAS. The output is comprehensive, and risk estimates are pro- Development of Approach to Evaluate EMAS vided by type of incident, runway, and RSA section challenged. Risk results are provided in terms of accidents per number of EMAS has proved to be a successful alternative when the RSA operations or the expected number of years to occur an acci- area available at the runway ends is shorter than the standard. dent, and are compatible with the criteria set by the FAA. The improved deceleration capability provided by EMAS is an Histograms of risk help users identify the percentage of important consideration when performing an RSA analysis. operations subject to risk levels higher than a desired TLS. The approach presented in ACRP Report 3 did not address the possibility of using EMAS; ACRP 04-08 filled this gap. A Model and Software Validation simplified approach based on data provided by Engineered Arresting Systems Corporation (ESCO), the manufacturer of The risk models were developed and calibrated based on a EMAS, was developed and incorporated into the software. worldwide dataset of accidents and incidents. A second effort The approach used can help airport stakeholders verify the was conducted to verify and validate the models using NOD safety benefits of using EMAS beds, even when non-standard and RSA conditions for eight airports that were not used to configurations are used. create the NOD used to develop the models. The verification was a key step to demonstrate the applica- Development of Approach to Assess Impact bility of the innovative approach and models developed in this of Declared Distances research. The comparison between estimated and actual fre- quency and risk rates showed excellent agreement, despite the Statistics were used to demonstrate that the likelihood of small sample of airports used in this study. Analysis output landing and takeoff incidents may depend on the safety mar- for the eight airports and their historical records of accidents gin available for the operation relative to the runway distance and incidents helped to prove the validity of the approach and required by the aircraft. analysis software. In this project, the estimate of frequency of incidents incor- The volunteers selected to test the models provided feed- porates a runway criticality factor defined as the ratio between back to the research team that was used to improve software the runway distance required and the distance available. Al- and eliminate bugs. though the runway distance can only be calculated using the actual aircraft weight, and this information is difficult to ob- Limitations tain, other factors may be used for modeling. Some of these factors include the basic distance required for standard con- Although an intensive effort was made to develop a very ditions, the runway elevation, the air temperature, the wind, comprehensive tool, there are some limitations that users and the runway surface conditions. In this project, the land- should be aware of. Some of those limitations are related to ing distance required is estimated based on each of those fac- data availability, and some are related to the computer time tors for the specific type of aircraft. to perform an analysis. The incorporation of these factors into the frequency mod- One important limitation is that the tool is helpful for els is used to help assess the impact of the declared runway planning purposes only. Neither the models nor the software distances on risk of overruns, veer-offs, and undershoots. should be used to estimate risk during real-time operations. 39

Only aircraft manufacturers can use actual aircraft data dur- ments and planning efforts. The approach can be similar to ing operations to estimate actual aircraft performance. the one presented in this study—using evidence of aircraft ac- The models and the approach were developed using actual cidents in the vicinities of airports to develop risk models data from accident and incident reports, and the models are based on causal and contributing factors to aircraft accidents. simply based on evidence gathered from that type of informa- The study should address the risk of accidents in areas within tion. For example, to estimate the runway distance required, a a 10-mile radius of the runway. basic distance for the type of aircraft and model was used and The methodology should consider local factors, historical corrected for temperature, elevation, wind, and surface charac- operation conditions for the airport, and the type of land use for teristics. Wind corrections are considered to be average adjust- specific regions near the airport runways. The recommended ments, and surface conditions are estimated based on weather study would improve the capability of land use committees and conditions only, rather than relying on actual runway friction. airport operators to assess third-party risk associated with air- It was not possible to incorporate the touchdown location craft accidents in the vicinity of airports. or the approach speed during landing. These are important The approach should be rational, non-prescriptive, and factors that may lead to accident, but there are no means to provide a quantitative assessment of third-party risk associ- account for these factors, except for assuming average values ated with aircraft operations at a specific airport. The study with a certain probability distribution that will lead to some should associate aircraft operations with existing runway and level of model uncertainty. environmental conditions, and aircraft type for a specific air- Additional simplifications were necessary to address the in- port. Thus, the results of such a study would help decision teraction of incidents with existing obstacles. In many cases, makers to evaluate alternatives and associated safety benefits. the pilot is able to have some directional control of the aircraft and avoid some obstacles. The approach simply assumes that Development of Risk Tool for Airspace the aircraft location is a random process and the deviation Analysis in Vicinity of Runways from the runway centerline follows a normal probability dis- The RSA analysis methodology and software presented tribution and that, during overruns and undershoots, the air- in this study can only address the ground roll phase of op- craft follows a path that is parallel to the runway centerline. eration; however, aircraft have both lateral and vertical de- One major limitation to obtain more accurate models and viations from their nominal flight path during landing and estimates is the difficulty in accounting for human factors. takeoff operations. Some type of human error was present in the majority of the Currently, the aviation industry still relies on the Collision events reported, and this factor is reflected as a component of Risk Model (CRM) developed in the 1960s with very limited the model error. data to evaluate risk during instrument approaches during the Also, obstacle categories were defined according to the max- non-visual segment and missed approach phases. The CRM imum speed to avoid an accident with substantial damage to has many limitations and does not cover all phases of the flight the aircraft and possibly injuries to its occupants. The classifi- and types of approach. Only data for precision approach Cat- cation was defined in this project using engineering judgment egories I and II can be evaluated using the existing model. and assuming that consequences depend only on the collision There is a need to have an updated CRM that can be used to speed and the area of the aircraft that has collided with the ob- prioritize risk mitigation actions associated with obstacles in stacle. Again, only engineering judgment was used to classify the vicinity of the runway. different types of obstacles according to the categories. Currently, the FAA is developing a tool called Airspace Sim- ulation and Analysis Tool (ASAT) that has comprehensive Recommendations for Future Work capabilities and accounts for aircraft performance, NAVAIDs, environmental conditions, terrain, wake turbulence, and hu- Extend Analysis for Non-RSA Areas man factors. However, the tool is not available to other air- Even with its limitations, the approach presented in this port stakeholders. report is quite robust for the analysis of RSA. It takes into The improved tool should have the capability to assess risk consideration many local factors and specific conditions to associated with fixed or movable obstacles when they are very provide estimates of risk. close to the runway. It should address all types of approach Still, the analysis presented can only cover the areas in the (visual, non-precision, precision, and possibly global position- immediate vicinity of the runway. The development of a risk- ing system [GPS] approach technology). Many airports would based methodology to evaluate land use compatibility and benefit from such a tool for safety management associated with third-party risk could be very helpful to support State require- the presence of obstacles. 40

References

AENA, “Operation of A-380 Aircraft on Alternate Aerodrome Sporad- Enders, J., Dodd, R., Tarrel, R., Khatwa, R., Roelen, A., Karwal, A. ically,” Report Code EXA 34, AENA, Aeropuertos Espanoles y Nave- “Airport Safety: A Study of Accidents and Available Approach-and- gacion Aerea, Division of Operations, Infrastructure and Apron Landing Aids.” Flight Safety Digest, Flight Safety Foundation, VA, Department, April 2005. March 1996. Annual Review of Aircraft Accident Data, U.S. Air Carrier Operations, FAA AC 150/5200-37, Introduction to Safety Management Systems (SMS) Calendar Year 2005, National Transportation Safety Board, NTSB/ for Airport Operators, U.S. Department of Transportation, Federal ARC-09/01, PB2009-106372, Notation 7502F, March 9, 2009. Aviation Administration, Washington, D.C., February 2007. Ash, A., and M. Schwartz, “R2: a Useful Measure of Model Performance FAA AC 150/5300-13, Airport Design, U.S. Department of Transporta- when Predicting a Dichotomous Outcome,” Statistics in Medicine, tion, Federal Aviation Administration, September 1989. 18(4), 1999, pp. 375–384. FAA Order 5200.11, FAA Airports (ARP) Safety Management System, ATSB, “Runway Excursions—Part 1: A Worldwide Review of Commer- August 2010. cial Jet Aircraft Runway Excursions,” Australian Transport Safety FAA Order 5200.8, Runway Safety Area Program, October 1999. Board, Aviation Research and Analysis, AR-2008-018(1), Final Flight Safety Foundation (FSF), “Reducing the Risk of Runway Excur- Report, 2009. sions,” Report of the Runway Safety Initiative, May 2009. Ayres, Manuel Jr., et al. ACRP Report 1: Safety Management Systems for Hall, Jim, et al. ACRP Report 3: Analysis of Aircraft Overruns and Under- Airports, Volume 2: Guidebook, Transportation Research Board of shoots for Runway Safety Areas, Transportation Research Board of the National Academies, Washington, DC, 2009. the National Academies, Washington, DC, 2008. Boeing, “Commercial Aircraft Design Characteristics—Trends and Hosmer, D., and S. Lemeshow, Applied Logistic Regression. John Wiley Growth Projections,” International Industry Working Group & Sons, Hoboken, 2000. (IIWG), 5th Ed., January 2007. Wong, D. K. Y., Appleyard, A., Caves, R. and Pitfield, D., “The Devel- Boeing, “Statistical Summary of Commercial Jet Airplane Accidents, opment of Models of the Frequency of Aircraft Accidents Near Air- Worldwide Operations, 1959–2010,” July 2010. ports,” presented at 9th ATRS World Conference, Rio de Janeiro, David, R., Location of Aircraft Accidents/Incidents Relative to Runways. Brazil, July 2005. DOT/FAA/AOV 90-1. Office of Safety Oversight, Federal Aviation Wong, D. K. Y., D. E. Pitfield, R. E. Caves and A. J. Appleyard, The Devel- Administration, Washington DC, 1990. opment of Aircraft Accident Frequency Models, Loughborough Uni- Eddowes, M., J. Hancox and A. MacInnes, “Final Report on the Risk versity, Loughborough, Leicestershire, United Kingdom, 2006, 8 pp. Analysis in Support of Aerodrome Design Rules,” AEAT/RAIR/ Wong, D. K. Y., The Modeling of Accident Frequency Using Risk Exposure RD02325/R/002 Issue 1, A Reported Produced for the Norwegian Data for the Assessment of Airport Safety Areas, Ph.D. dissertation, Civil Aviation Authority, December 2001, 202 pp. University of Loughborough, Leicestershire, United Kingdom, 2007. 41

Abbreviations and Acronyms

AAIB UK Air Accidents Investigation Branch AAIU Ireland Air Accident Investigation Unit ACRP Airport Cooperative Research Program ADG Airplane Design Group ADREP ICAO Accident/Incident Data Reporting ASDI Aircraft Situation Display to Industry AIDS FAA Accident/Incident Data System AIP Airport Improvement Program ALS Approach Lighting System ASAT Airspace Simulation and Analysis Tool ASPM Aviation System Performance Metrics ASRS FAA/NASA Aviation Safety Reporting System ATADS Air Traffic Activity Data System ATC Air Traffic Control ATSB Australian Transport Safety Bureau BEA Bureau d’Enquêtes et d’Analyses pour la Sécurité de l’Aviation Civile CCFD Complementary Cumulative Frequency Distribution CCPD Complementary Cumulative Probability Distribution CFR Code of Federal Regulations CIAIAC Comisión de Investigación de Accidentes e Incidentes de Aviación Civil CRM Collision Risk Model EMAS Engineered Material Arresting System ESCO Engineered Arresting Systems Corporation FAA Federal Aviation Administration FAR Federal Aviation Regulation FHA Functional Hazard Analysis GA General Aviation GPS Global Positioning System ICAO International Civil Aviation Organization ISO International Standards Organization LDOR Landing Overrun LDUS Landing Undershoot 42

LDVO Landing Veer-off MTOW Maximum Takeoff Weight NASA National Aeronautics and Space Administration NASB Netherlands Aviation Safety Board NAVAID Navigational Aids NOAA National Oceanic and Atmospheric Administration NOD Normal Operations Data NTSB National Transportation Safety Board NTSC Indonesia National Transportation Safety Committee RLF Runway Length Factor ROC Receiver Operating Characteristic ROFA Runway Object Free Area RSA Runway Safety Area RSARA Runway Safety Area Risk Assessment (software tool) TAIC New Zealand Transport Accident Investigation Commission TOOR Takeoff Overrun TLS Target Level of Safety TOVO Takeoff Veer-off TRB Transportation Research Board TSB Transportation Safety Board of Canada 43

Definitions

Acceptable Level of Risk: likelihood of an event when proba- ple fatalities; or there was one fatality and the airplane was bility of occurrence is small, whose consequences are so slight, substantially damaged. or whose benefits (perceived or real) are so great, that individ- METAR: aviation routine weather report. uals or groups in society are willing to take or be subjected to the risk that the event might occur. Nonconformity: non-fulfillment of a requirement. This in- cludes but is not limited to non-compliance with Federal reg- Accident: an unplanned event or series of events that re- ulations. It also includes an organization’s requirements, sults in death, injury, or damage to, or loss of, equipment or policies, and procedures, as well as requirements of safety risk property. controls developed by the organization. Consequence: the direct effect of an event, incident, or acci- Overrun or Overshoot: a departure of the aircraft from the dent. In this study it is expressed as a health effect (e.g., death, end of the intended landing runway surface. injury, exposure) or property loss. Quantitative Risk Analysis: incorporates numerical esti- Fatal Injury: any injury that results in death within 30 days of mates of frequency or probability and consequence. the accident. Risk: the combination of the likelihood and the consequence Hazard: the inherent characteristic of a material, condition, of a specified hazard being realized. It is a measure of harm or or activity that has the potential to cause harm to people, loss associated with an activity. property, or the environment. Risk Analysis: the study of risk in order to understand and Hazard Analysis: the identification of system elements, events quantify risk so it can be managed. or material properties that lead to harm or loss. Hazard analy- sis may also include evaluation of consequences from an event Risk Assessment: determination of risk context and accept- or incident. ability, often by comparison to similar risks. Hull Loss: airplane totally destroyed or damaged and not Runway Criticality: term introduced in this study to repre- repaired. sent the relationship between the runway distance required by a given aircraft and specific operational conditions, and the Incident: a near miss episode, malfunction, or failure with- runway distance available for that operation (landing or take- out accident-level consequences that has a significant chance off). Runway criticality is represented mathematically by the of resulting in accident-level consequences. ratio between the runway distance required and the runway Likelihood: expressed as either a frequency or a probability. distance available. A higher ratio means a lower safety margin Frequency is a measure of the rate at which events occur over and greater operation criticality. time (e.g., events/year, incidents/year, deaths/year). Probabil- Safety: absence of risk. Safety often is equated with meeting a ity is a measure of the rate of a possible event expressed as a measurable goal, such as an accident rate that is less than fraction of the total number of events (e.g., one-in-ten-million, an acceptable target. However, the absence of accidents does 1/10,000,000, or 1 × 10-7). not ensure a safe system. To remain vigilant regarding safety, it Major Accident: an accident in which any of three condi- is necessary to recognize that just because an accident has not tions is met: the airplane was destroyed; or there were multi- happened, it does not mean that it cannot or will not happen. 44

Safety Management System: the formal, top-down business- of the aircraft, and that would normally require major repair like approach to managing safety risk. It includes systematic or replacement of the affected component. procedures, practices, and policies for the management of Target Level of Safety (TLS): the degree to which safety is to safety (including safety risk management, safety policy, safety be pursued in a given context, assessed with reference to an assurance, and safety promotion). acceptable or tolerable risk. Safety Risk Management: the systematic application of poli- Undershoot: an event when the aircraft lands short of a run- cies, practices, and resources to the assessment and control of way or planned landing spot. risk affecting human health and safety and the environment. Hazard, risk, and cost/benefit analysis are used to support de- Veer-off: an aircraft running off the side of the runway dur- velopment of risk reduction options, program objectives, and ing takeoff or landing roll. prioritization of issues and resources. Worst Credible Condition: the most unfavorable condi- Substantial Damage: damage or failure that adversely affects tions or combination of conditions that it is reasonable to the structural strength, performance, or flight characteristics expect will occur. A-1

APPENDIX A Functional Hazard Analysis Results

Introduction nel, and specialist risk assessors. The objective of the workshop is to explore all relevant operational scenarios and identify haz- As described in the body of this report, one of the subtasks ards associated with them. The output of the FHA is a “hazard of this project was to carry out a functional hazard analysis log,” including all hazards identified and preliminary informa- (FHA) for aircraft overruns, undershoots, and veer-offs based tion about them that can be provided by the workshop team. on information gathered in the literature review. The objec- tive of this subtask was to identify the most relevant factors Summary of Relevant associated with such events to support the data collection effort Factors Identified for accidents and incidents. Identifying such factors causing or contributing to such events was also part of the modeling Table A1 summarizes the factors that are believed to lead process involved in this study. to overrun, undershoot, and veer-off accidents and incidents FHAs often are conducted in the form of a brainstorming based on FHA studies and literature review. Most of these fac- workshop involving a multi-disciplinary team, for example in- tors were identified in ACRP Report 3 and other studies, but cluding pilots, air traffic controllers, airside operations person- some were added based on available reports from other sources.

Table A1. Summary of factors causing or contributing to aircraft overrun, undershoot, and veer-off occurrences.

Event Category Factor Landing Overrun Weather Tail Wind (LDOR) Cross Wind Wind variations (gusts, shear) Visibility Ceiling Temperature Airfield Surface contaminants and friction (water, snow, ice, slush, rubber deposits) Landing Distance Available (LDA) Slopes (longitudinal and transverse) Altitude Runway profile System faults Pilot Landing long Unstabilized approach Landing fast High threshold crossing height “Pressonits” Incorrect (delay) application of thrust reverse (if available) and spoilers Incorrect (delay) application of brakes Delayed nose-wheel lowering ‘Over-consideration’ for comfort Incorrect interpretation of reported operation conditions Landing on the wrong runway Aircraft Landing Distance Required (LDR) Weight System faults (e.g. brake systems failure) (continued on next page) A-2

Table A1. (Continued).

Event Category Factor Takeoff Overrun Weather Tail Wind (TOOR) Wind variations (gusts, shear) Cross wind Temperature Airfield Accelerate-Stop Distance Available (ASDA) Surface contaminants and friction (water, snow, ice, rubber deposits) in case of aborted takeoff Slopes (longitudinal and transverse) in case of aborted takeoff Altitude Pilot Delay to abort takeoff when required Incorrect (delay) application of thrust reverse (if available) and spoilers, in case takeoff is aborted Incorrect (delay) application of brakes, in case takeoff is aborted Incorrect interpretation of reported operation conditions Selection of wrong runway Aircraft System or component malfunction require to abort takeoff Accelerate-Stop Distance Required (ASDR) Landing Weather Visibility Undershoot Ceiling (LDUS) Wind variations (gusts, shear) Temperature Crosswind Airfield System faults Availability of navigational aids Altitude Pilot Approach too low Attempt to land too close to arrival end of the runway Misinterpretation of approach procedures Visual illusion resulting incorrect pilot response Aircraft System faults Stall speed Approach speed Takeoff Veer-Off Weather Crosswind (TOVO) Wind gusts Heavy rain Airfield Runway contamination (water, snow, ice, rubber) Bird strike Runway undulation Construction work Pilot/Crew Abort takeoff above V1 Incorrect performance calculation Incorrect CG Incorrect runway distance available Aircraft Engine power loss Blown tire Undercarriage collapse Loss of directional control Landing Veer-Off Weather Cross wind (LDVO) Wind gusts Tailwind Turbulence Windshear Airfield Runway contamination (water, snow, ice, slush, rubber) Snow banks Pilot Hard landing with landing gear failure Unstabilized approach Go around not conducted Touchdown long Touchdown hard/bounce Aircraft Spontaneous collapse of undercarriage Asymmetric forces due to thrust reverse problem Asymmetric forces due to braking problem Steering control system malfunction B-1

APPENDIX B Summary of Accidents and Incidents

The following table presents a summary of the overrun, veer-off, and undershoot accidents and incidents identified in the databases screened. Some events are reported in more than one database, and to avoid repeating the events during the consolidation of records, the reported event date, event type, aircraft type, and location were used to eliminate the repeated records. B-2 (ft) Veer-off Veer-off Maximum (ft) Location Y (ft) Location X Code Airport Code ICAO Aircraft Aircraft Class Event Type Event LDOR Incident B741 LDOR Incident YSSY 325 60 N/A Source Australia Civil Aviation City/State Country Date 7/18/1971 Australia Sydney 7/18/1971 Australia LA AIDS 1/17/1978 US TX Charles, 5/2/1978 US CWF CVLP N/R Tyler, Incident 8/16/1978 LDOR Lake N/R 2/15/1979 US US IL AIDS IL 8/1/1979 US N/A Waukegan, 8/10/1979 US Mattoon, CA AIDS N/R MU2 AC68 Soda Springs, ID LDOR 9/11/1979 US CYWM AIDS Incident TYR AR AB Hayward, Accident TSB LDOR N/R N/R 11/21/1979 US SBR1 MTO Fayetteville, N/R AIDS G159 LDOR Incident AIDS Incident CA 4/7/1980 Canada Athabasca, LDOR Canada UGN N/A AIDS N/R N/R Carlsbad, 7/29/1980 US N/R LA LDOR 8/7/1980 Incident SW3 LDOR Incident HWD Houma, N/A N/A N/R AIDS N/R FYV 9/6/1980 N/R UK 12/20/1980 LDOR AIDS N/A Canada N/R MI US 2/1/1981 US N/R LDOR Incident Incident LJ24 3/29/1981 England North Seal River, MB DE Bedfordshire Leeds Bradford Pontiac, AC11 LDOR N/A Incident HUM CRQ 5/1/1981 AIDS N/A N/R Canada TSB AIDS Teterboro, NJ Castle, 100 5/6/1981 US C550 US AAIB PTK OH MU2 Incident ILG N/R N/R 7/2/1981 US LDOR UK AAIB LDOR New Incident U78 LDOR N/R QC YZG 7/17/1981 US DHC6 0 Cleveland, N/R AIDS NE Incident N/R Incident TSB L29A AIDS LDOR N/A LDOR N/R 8/1/1981 Canada 152 Salluit, Accident EGGW Little Rock, AR DHC6 N/R LDOR Lincoln, CL60 N/R CGF N/A 9/13/1981 US N/R Incident Canada LDOR MA N/A Incident CEG8 0 AIDS 12/9/1981 US N/A N/A NM N/R Boston, VISC AIDS LDOR N/R AIDS N/R Albuquerque, AIDS N/A LJ25 LDOR Incident LBA N/A Incident LNK N/R FA20 AC6L LDOR Incident ABQ DC10 LDOR N/R N/R Incident N/A N/R BOS LDOR TEB N/R 50 Incident N/R AC68 N/A N/R N/R N/A 0 N/A LIT N/R N/A N/A N/R N/A N/R N/A B-3 (continued on next page) San Juan AIDS LDOR Incident DC10 JSJ 300 0 N/A Puerto Rico 12/11/1981 1/1/1982 UK 1/12/1982 US Cambridge TX 1/12/1982 US AAIB CBG TX N/R Dallas, Incident 2/15/1982 LDOR Dallas, UK N/R 2/19/1982 US US TX AIDS 2/19/1982 US CA MITRE N/A Harlingen, 2/26/1982 US GA NTSB Oakland, H25A LDOR Incident Los Angeles, CA ADS 10/1/1982 UK H25A LDOR Incident ADS Atlanta, N/R AIDS 11/11/1982 US 1241 PR Scatsa B721 LDOR Incident Juan, 11/20/1982 US NTSB HRL N/R NTSB 0 299 San GA 12/18/1982 US FA20 LDOR Incident OAK Atlanta, MITRE MI 12/27/1982 US N/R BE9L LDOR N/A Incident AAIB PDK 0 Pellston, IA 4/19/1983 600 N/A A748 LDOR UK Incident N/R Dubuque, LDOR 6/24/1983 US NTSB LDOR SCS Canada HI Incident L101 N/R NTSB 7/15/1983 US 280 Incident N/A TN Kailua/Kona, SJU N/A Gaspe Airport, QC MITRE MITRE 7/20/1983 US B731 IL Blountville, LDOR N/R N/R AC80 9/10/1983 US Accident NTSB N/A CO LDOR Chicago, YS11 LDOR ATL Incident Canada TSB LDOR LAX Incident 9/20/1983 US KOA DC91 NY Incident N/A Burlington, E110 N/R 450 PLN N/R GLF2 10/21/1983 US NTSB NTSB LDOR TRI Accident DBQ Massena, LDOR N/R 80 IL 10/25/1983 US N/R 110 N/R NTSB Bloomington, 0 Accident VA 11/29/1983 UK BE9L N/A DC85 LDOR LDOR ITR Incident Accident ORD H25A MITRE Norfolk, 12/22/1983 US N/R 100 N/A 225 0 LJ35 0 Sumburgh N/R LDOR CO Accident 1/30/1984 US MSS YGP CA Eagle, 587 N/A NTSB N/A LDOR 2/12/1984 US 0 NY 0 WI Incident Avalon, F27 2/28/1984 US N/R York, AAIB N/A Oshkosh, N/A 30 N/A BMI A748 NTSB 3/30/1984 US NTSB YBX UK HI 30 LDOR MITRE New Accident TSB N/A MITRE DC85 N/A LDOR LDOR Accident N/R 4/2/1984 Incident A748 QC Kailua/Kona, NGU MITRE DC10 LJ24 6/23/1984 US N/A N/R LDOR 0 Canada LDOR JFK IL LSI Accident 7 Accident DC93 US LDOR AVX LDOR Incident OSH 7/6/1984 Canada LJ25 Blanc-Sablon, N/R Accident N/R 660 Chicago, N/R 131 LDOR Incident 11/1/1984 UK EGE KOA N/A N/R N/R N/R 35 NTSB N/A N/A Little Rock, AR 129 N/R Bristol 70 N/R N/A N/R N/A B701 LDOR N/A Incident N/A ORD NTSB 600 AAIB N/A N/A N/A A30B LDOR UK Incident BRS 0 N/R LDOR N/R N/A Accident CL60 N/A LIT 50 60 N/A B-4 (ft) Veer-off Veer-off Maximum (ft) Location Y (ft) Location X N/R N/A Code Airport Code ICAO Aircraft Aircraft LJ24 Unknown Class Event Type Event Source City/State Country Date 5/27/1985 6/11/1985 UK 6/27/1985 England TX Leeds US 7/12/1985 US WI Worth, Leeds Bradford NTSB 8/28/1985 US Bay, Fort Van Nuys, CA 9/23/1985 US MITRE IL Green LJ35 10/19/1985 US LDOR Accident FTW AAIB Chicago, BA11 UK AAIB LDOR IN Incident 11/7/1985 US 459 GRB TN MI N/R Bloomington, 1/2/1986 US NTSB NTSB L101 Sparta, NTSB LDOR 100 Accident 1/31/1986 US EGNM 147 LDOR Detroit, CA N/R CA FA10 2/8/1986 US NTSB LDOR NTSB Accident DPA Incident Lancaster, N/A 0 2/21/1986 US 1200 Carlsbad, LDOR PA DC10 N/A AIDS DTW L101 100 LDOR VISC NTSB Accident Incident 2/27/1986 US LDOR H25A PA BMG CRQ Erie, LDOR MU30 SRB 1100 Accident 100 Accident 3/13/1986 US 0 320 LBA SC Accident 359 LDOR Coatesville, N/A FL AC11 C550 LDOR Incident 5/7/1986 US NTSB WJF N/A 119 Charleston, IN N/R NTSB 8/2/1986 US 538 NTSB Hollywood, NTSB 20 VNY N/A 75 N/A FA10 10/14/1986 US LJ24 Bedford, LDOR HWO Accident N/R 40N N/R Accident DC91 MA 10/25/1986 US 1300 LDOR NTSB LDOR ERI 400 Accident DC91 LDOR N/A Incident NH CHS Beverly, N/R H25A NC 1/5/1987 US BFR N/A 180 33 677 870 N/A Accident Charlotte, LDOR 1/29/1987 US Lebanon, 250 IL N/A MITRE MITRE 0 0 3/12/1987 70 200 LJ35 Chicago, NTSB OK LEB Incident 9/9/1987 US N/R LDOR N/A US N/A LDOR 10/6/1987 US MITRE Tulsa, N/A BE9L N/A WA N/A Accident N/R 10/21/1987 BVY LDOR B731 AIDS Kennewick, Accident N/A NTSB DC91 US LDOR N/R Des Moines, IA 10/28/1987 US Incident N/A MDW CLT N/R LJ35 OK 11/4/1987 US TUL PA Incident 516 N/R LDOR JS31 Bartlesville, LDOR 11/23/1987 US N/R Accident N/R S98 Williamsport, MITRE San Luis Obispo, CA AIDS N/R NTSB TN 450 75 Nashville, MITRE N/A N/A BE9L LDOR N/A Incident IPT 0 LDOR AIDS 100 CVLT Accident N/A LDOR BVO LDOR 918 0 Incident N/A LDOR Incident Incident DC85 B721 SW4 0 BNA N/A DSM 50 SBP 50 N/A 0 N/R 0 N/A N/R N/A N/A 12/15/1984 Canada 1/5/1985 1/31/1985 US KY Sioux Lookout, ON US IL 5/8/1985 US London, Chicago, Canada TSB NTSB AIDS Oklahoma City, OK LDOR SW4 Incident NTSB LDOR LDOR Accident Accident LOZ C500 380 YXL 0 LDOR 502 Accident LJ25 N/A OK15 0 N/R N/A N/R N/A B-5 (continued on next page) 2/3/1988 US Denver, CO 2/3/1988 US 6/17/1988 CA Denver, 7/15/1988 US MITRE US Diego, FL DC85 DEN 8/1/1988 US MITRE 30 Incident San LDOR 8/19/1988 US Pensacola, FL NTSB MU2 LDOR West Palm Beach, FL Accident 9/19/1988 US 0 MYF KY Pensacola, PNS MD88 N/R 320 9/22/1988 US Incident NTSB MI LDOR ASRS Paducah, 9/23/1988 US KY N/A N/R Fremont, 90 ASRS 10/14/1988 US Paducah, LDOR NTSB Incident NT WA 10/19/1988 US PNS N/A N/A LDOR MITRE Lake, Seattle, TSB LDOR GA 10/21/1988 Canada 78 Incident PAH Happy LDOR Canada C550 Columbus, Incident 11/10/1988 US LDOR N/R Accident Incident 3FM DHC6 SW4 LDOR Incident LJ24 CA 644 11/13/1988 US MITRE PAH ASRS 0 200 Burbank, N/R TN 11/17/1988 US N/R PBI Nashville, 150 OR 12/19/1988 US LA LDOR Incident 0 MITRE B721 N/A LDOR Bend, N/A SC 12/30/1988 US NTSB CA Incident N/R MITRE Rouge, SEA Charleston, N/A 30 Jose, 1/9/1989 US DC91 BTR 300 Incident 50 LSF San LDOR LDOR 1/12/1989 US LA Baton ASRS TN N/A Incident B17 N/A NTSB LDOR MITRE 400 1/19/1989 US 0 Incident SW4 Rouge, ASRS Crossville, BUR 2/15/1989 US BNA 0 NY AIDS 0 Baton 470 LDOR LDOR 2/19/1989 US 0 LDOR N/R Incident OH N/A Incident LJ25 Binghamton, LJ35 LDOR Accident NTSB Incident 2/20/1989 US BTR IL BDN Covington, SJC C500 CHS LDOR 200 Incident 0 2/27/1989 US ASRS CSV N/A N/R NY 200 Bloomington, 150 N/R MITRE N/R LDOR 3/19/1989 US Accident N/A BGM N/A NTSB IL Poughkeepsie, 200 0 3/19/1989 LDOR N/A Chicago, Incident SH36 LDOR 0 N/R Incident N/A N/R 0 CVG 3/19/1989 US BMI C550 US DC LDOR 60 80 Accident POU N/R 3/23/1989 US ASRS VA N/A 700 Washington, N/A ASRS 3/29/1989 US N/A KY Roanoke, N/R N/A -140 N/A N/A Daytona Beach, FL 4/1/1989 CA 100 LDOR Incident Owensboro, NTSB ORD MITRE 4/12/1989 US LDOR CA Incident Diego, N/A 500 N/A UK DCA ASRS 4/19/1989 US MITRE 150 N/A Diego, LJ25 San MU30 LDOR LDOR Incident OWB Accident 5/4/1989 ASRS ROA N/R 30 San 200 B752 LDOR Incident 0 Leeds Bradford SAN US N/R N/R LDOR LDOR Incident 10 N/A SAN 280 N/A Incident N/R N/A UK AAIB El Monte, CA N/A 50 N/A LDOR AIDS N/A DAB Incident SH36 50 LBA LDOR N/R Incident 0 C500 EMT N/R N/A N/R N/A N/R N/A B-6 (ft) Veer-off Veer-off Maximum (ft) Location Y (ft) Location X Code Airport Code ICAO Aircraft Aircraft Class Event Type Event Source City/State Queenstown TAIC LDOR Incident B461 ZQN 318 82 N/A 82 318 ZQN B461 Incident LDOR Queenstown TAIC Country New Zealand Date 5/18/1989 US MS NC 6/5/1989 US Jackson, MITRE 7/18/1989 US Greensboro, IL BE20 GSO MITRE 7/27/1989 US N/R Incident WY LDOR Chicago, 10/18/1989 US CO Jackson, N/R MU30 LDOR Incident JAN Vista, 10/19/1989 US NTSB N/R MITRE NTSB Monte DE 10/23/1989 US N/A Dover, AK 12/13/1989 US DC10 LDOR N/R Incident B731 LDOR ORD Incident Anchorage, IL 12/30/1989 US JAC N/R LDOR Island N/R Incident Chicago, DC91 AZ 1/19/1990 US MITRE N/A CO ASRS ASN FL MVI Howe Tucson, N/R 4/5/1990 US Denver, N/R N/R Lord 4/22/1990 Australia NTSB Pensacola, LDOR MITRE Incident B741 N/A C501 LDOR ASRS NTSB LDOR F86 4/28/1990 Accident Incident N/A LDH ANC Incident N/R PNS LDOR 250 N/R N/R LDOR DOV Incident DC91 LDOR Incident LDOR 200 N/R DEN MDW 0 B731 N/A Accident 100 304 N/R TUS N/A 3803 0 0 N/A 30 N/A 175 N/A N/A N/A N/A 7/18/1990 US WI 7/19/1990 US WY Milwaukee, 7/29/1990 US NTSB WY Jackson, 8/19/1990 Jackson, ASRS MU30 10/4/1990 US US MWC LDOR TX Accident N/R MITRE 2/14/1991 US OH Dallas, LDOR 3/12/1991 US Incident MN N/R B731 Cleveland, JAC LDOR Incident Santa Ana, CA 3/19/1991 US JAC NTSB 310 NC MITRE Alexandria, N/R AIDS 3/29/1991 MO N/A Raleigh, 6/19/1991 US GNAT LDOR GLF2 US 0 ADS City, Incident ASRS LDOR BKL N/R Accident N/R ASRS 6/26/1991 ASRS MU30 250 LDOR Incident AXN Kansas TN N/R 7/2/1991 US US N/A LDOR N/R Incident N/A Sioux City, IA 8/10/1991 US 150 LDOR Columbia, MCI NC Incident NTSB RDU N/R 500 8/19/1991 US 150 WA LJ23 LDOR Charlotte, N/A MRC 543 Kansas City, MO 8/19/1991 US N/A Accident LDOR NC Seattle, AIDS N/A 0 Incident 10/6/1991 US MITRE 0 ME 38 Charlotte, 11/19/1991 US ASRS CA MITRE Augusta, ASRS B762 LDOR Angeles, 11/26/1991 Incident N/A CLT N/A NTSB ASRS N/A Los US 50 LDOR LDOR Incident LDOR SEA SNA Incident CLT LDOR 25 Incident SW4 LDOR 80 Accident AUG 0 LDOR AC11 Los Angeles, CA 75 20 Incident Incident 30 B721 SUX LAX 0 N/A 0 MITRE 150 MCI N/R N/A 0 N/A 0 N/R N/A LDOR N/R Incident N/A N/A N/R B731 N/A LAX N/A N/R N/R N/A B-7 (continued on next page) Papeete France BEA LDOR Accident B741 PPT 230 197 N/A 197 230 PPT B741 Accident LDOR BEA Papeete France French Polynesia 12/23/1991 US CA 3/31/1992 UK FL MITRE Carlsbad, 4/19/1992 US Lauderdale, Aberdeen 4/23/1992 US MI ASTR LDOR Fort Incident NTSB FLL 5/19/1992 US IA MT N/R Detroit, AAIB 6/17/1992 US Rapids, B461 NTSB Bozeman, IL LDOR UK Accident ABZ 7/1/1992 US LDOR NTSB N/R ASRS Cedar LJ25 479 Accident 7/11/1992 US Chicago, WY SBR1 CRQ LDOR CID Accident 7/19/1992 US AIDS DC85 N/A IL LDOR 50 43 Cheyenne, YIP 212 Accident LDOR Incident 7/19/1992 MITRE BZN B752 N/R Chicago, ORD 25 150 Incident 7/29/1992 US LDOR N Mariana WY 0 WI N/A Rota Island B190 LDOR 8/7/1992 US 75 ASRS Incident N/R CYS Jackson, 0 0 8/19/1992 US MITRE N/R Milwaukee, WI MITRE B721 8/23/1992 US MKE N/A N/A N/R KY LDOR Incident Incident Milwaukee, LDOR NC N/A ORD N/R 9/8/1992 US N/A ASRS N/A 30 B752 Louisville, LDOR N/R Incident MITRE 11/7/1992 US ASRS JAC Wilmington, MITRE AZ ILM MU30 N/A N/R N/R 11/22/1992 US Incident N/A LDOR LDOR Incident Phoenix, 0 MKE OH 11/27/1992 UK MD88 LDOR Incident SDF N/R 250 N/R Cleveland, NTSB 2/13/1993 US N/R ME LDOR Southampton N/A 2/19/1993 US 0 NTSB N/A ME N/A Portland, SBR1 Incident N/R 4/27/1993 US LDOR PHX Accident CO Portland, AAIB NTSB 1500 4/29/1993 UK Denver, ASRS N/A LDOR N/A 5/24/1993 US LDOR LJ25 US Accident TX 120 Accident B731 LDOR 5/26/1993 England Incident NTSB Southampton CLE PWM Killeen, MO 330 SOU ROP LDOR 6/4/1993 US Incident BC 200 N/A AAIB PWM 246 260 MITRE Pine Bluff, AR DC91 7/21/1993 Canada AIDS Springfield, C550 LDOR Tofino, DEN Accident LDOR UK FA10 Accident 50 10 SOU SGF 1 8/26/1993 US Incident N/R ID LDOR 630 0 0 0 TSB 9/12/1993 FA10 LDOR Hailey, Incident N/R ILE N/A NTSB 0 30 N/R 0 N/A N/A N/A NTSB CVLT LDOR N/A Incident YAZ 152 N/R N/A N/A FA10 LDOR LDOR Accident SUN N/A 20 850 Accident N/A E120 260 N/A PBF N/A 687 50 N/A 9/19/1993 US DC 9/29/1993 England Norwich Washington, ASRS 12/4/1993 US OR Corvallis, AAIB LDOR Incident AIDS DCA BA11 LDOR UK Incident NWI 50 89 L29B LDOR Incident CVO 0 N/R 0 N/R N/A N/A N/A B-8 (ft) Veer-off Veer-off Maximum (ft) Location Y (ft) Location X Code Airport Code ICAO Aircraft Aircraft Class Event Type Event Source City/State Country Date 1/19/1994 1/19/1994 US US OH 1/20/1994 BC Wilmington, ASRS 1/21/1994 Canada US Terrace, TSB Windsor Locks, CT 1/27/1994 US B461 LA LDOR IL Incident YXT Canada LDOR 1/27/1994 US Incident 415 MI NTSB Chicago, ILN Roads, MITRE Teterboro, NJ 2/1/1994 US SF34 10 Pontiac, HZR DC 420 2/8/1994 US MITRE Accident 39 New LDOR AIDS 2/19/1994 US MITRE Washington, CO 20 0 LDOR DC85 LDOR DCA 2/19/1994 US NTSB Incident MD80 PA 50 ORD DC N/A Rifle, Incident 59 LDOR LJ35 LDOR 3/19/1994 US Incident Incident College, ASRS N/A Washington, PTK ASRS 3/19/1994 US 50 DC91 30 N/A OH State ASRS 4/26/1994 US 0 IN LDOR JS32 Columbus, LDOR Incident BDL 6/13/1994 US LDOR N/A Incident UNV ASRS WV 0 Anderson, DCA 20 Korea Accident B461 LDOR Jeju 7/22/1994 US Incident 250 WY RIL Lewisburg, MU30 N/R AIDS N/A MITRE 8/10/1994 S 630 LDOR Jackson, Incident 0 8/19/1994 US TEB CMH 50 N/A GA 260 LJ35 MITRE LDOR CVLP Incident LDOR 10/8/1994 US Incident 70 AID PA LWB Savannah, N/R 130 N/R 10/10/1994 US N/R TX N/A ASRS 0 B731 Pittsburgh, LDOR N/A Incident ADREP Antonio, 11/4/1994 JAC MITRE N/A 0 N/R 61 AIDS San 11/17/1994 US US A30B LDOR LDOR N/A CJU Accident Incident N/R MT 12/7/1994 US N/A B190 LDOR SAV Incident NY 1427 PIT N/A 2 Bozeman, 1/19/1995 US 0 GA N/A Batavia, LDOR N/R LJ35 Little Rock, AR 1/24/1995 US Accident 3278 WI AIDS Atlanta, GA SAT AIDS N/A 2/1/1995 US 30 N/R Milwaukee, N/A N/A N/R 2/17/1995 US NTSB AIDS Atlanta, GA MITRE AB 2/19/1995 US ASRS LDOR C550 N/A LDOR IL Incident Atlanta, Incident TSB N/A DC91 GVQ 2/19/1995 US N/R B731 DC85 LDOR ATL N/R IL Incident LDOR BZN Hinton, Chicago, Incident 470 ATL Incident LDOR MKE 2/22/1995 US MITRE CEC4 256 MU30 IL 250 290 100 Chicago, Incident LDOR LDOR 3/1/1995 Canada Jasper ASRS N/R 90 N/A Chicago, 0 DC85 LDOR Incident 3/19/1995 US ASRS ATL Incident 0 HI 0 0 N/R N/A 4/29/1995 US MITRE N/A DC91 IL LDOR Incident Honolulu, ORD N/A DC10 LDOR 200 Incident Chicago, N/R ORD ASRS LIT DC10 N/A LDOR N/A Incident 10 ORD N/A N/R MITRE -70 N/A DC10 N/R LDOR Incident HNL 0 N/R DC85 100 LDOR Incident ORD N/A N/R N/A 70 N/R N/A N/R N/A N/A N/A B-9 (continued on next page) 5/11/1995 Canada Wabush, NL 5/11/1995 Canada Wabush, MA 6/7/1995 US TSB 7/26/1995 US Hyannis, MN AIDS 8/21/1995 US AZ Minneapolis, NTSB C500 9/19/1995 US HYA AR B721 300 LDOR Incident Mesa, Incident LDOR YWK 9/19/1995 US 299 SC C550 Fayetteville, LDOR ASRS Accident 0 12/8/1995 US FCM IL Charleston, 800 MITRE 12/9/1995 US 21 ASRS WY Chicago, 12/14/1995 US LDOR N/A Incident LJ23 LDOR 0 Jackson, Incident FYV MI 12/19/1995 US FFZ MITRE CA 52 MD88 LDOR N/A Incident CHS AIDS Leicestershire N/R Detroit, Angeles, 1/1/1996 England AAIB F70 50 Bankstown Incident ASRS B721 Los EMA LDOR LDOR 1/2/1996 Australia 377 Incident N/A ORD 0 N/R UK Leicestershire 40 MU30 1/5/1996 England LDOR Incident AIDS JAC 160 30 1/19/1996 US N/R ATSB WY LDOR N/A AAIB Incident AIDS B731 1/26/1996 US CA N/A 0 TN A37 Jackson, N/A N/A PA BWU N/R LAX Incident DC85 LDOR N/R EMA 2/7/1996 US LDOR N/R SW2 Incident Incident LJ55 Sparta, 20 MMH LDOR Lakes, MITRE Incident 160 LDOR 2/7/1996 US Bradford, N/R DET N/R NTSB N/A N/A 2/19/1996 US Mammoth TX AIDS 0 E120 485 LDOR B190 Incident BFD N/A 2/19/1996 US 100 JAC N/A 870 GA Accident Houston, LDOR N/R 2/20/1996 US DC Savannah, FA20 LDOR N/A 825 0 NTSB Incident 2/20/1996 US SRB DC N/A ASRS Washington, N/R NTSB 279 2/20/1996 US CO N/A Washington, DC91 AIDS LDOR 2/28/1996 US IAH Accident GA N/A Rifle, LDOR N/A 0 Incident 51 B731 LDOR 3/25/1996 US Incident SAV ID B721 DCA NB Savannah, YQM 154 300 Incident TSB 4/3/1996 250 B731 LDOR LDOR Incident NTSB Hailey, DCA NTSB 4/3/1996 Canada Moncton, 140 150 0 N/A Canada US 50 0 8/13/1996 UK AIDS DC91 LDOR Incident H25B LDOR SAV 9/28/1996 US Incident 75 N/A RIL OH Northolt N/A 201 10/6/1996 US N/A 1000 Traverse City, MI CA Chillicothe, N/A C500 LDOR Incident 10/14/1996 NTSB SUN N/A 0 Salinas, 80 US AAIB 40 10/29/1996 US AIDS LJ25 MU2 IL 11/1/1996 US LDOR MITRE UK Accident LDOR OH Accident NHT RZT Waukegan, N/A 748 N/A 0 15 Cleveland, Las Vegas, NV F86 LDOR Incident ASRS MITRE SNS 115 LDOR 147 N/R N/A MD88 LDOR Incident LDOR Incident AIDS CLE N/A Incident CL60 N/R 285 N/A AT43 UGN N/R TVC N/A 0 LDOR N/R N/R Incident N/A AC68 N/A N/R VGT 400 N/A 0 N/A B-10 (ft) Veer-off Veer-off Maximum (ft) Location Y (ft) Location X Code Airport Code ICAO Aircraft Aircraft Class Event Type Event Source City/State Country Date 11/11/1996 US OH 11/11/1996 US Cleveland, OH 11/15/1996 US SD Cleveland, Falls, 11/19/1996 US AIDS Sioux HI 12/6/1996 US MO MITRE NTSB MA Honolulu, 12/22/1996 US NTSB Bedford, City, LDOR ID 1/1/1997 US LJ35 MKC LDOR 105 Incident MD80 WY AIDS ASRS Accident LDOR Hailey, Incident DC91 LDOR 1/3/1997 US CLE Kansas Incident MD88 FSD CLE 1/21/1997 US 1000 Jackson, 200 IN AIDS N/R GLF2 1/25/1997 530 LDOR Incident LDOR N/A BED AIDS Bloomington, NTSB JAC Incident DC10 WW24 2/19/1997 US N/R 60 US IL 0 Incident HNL LDOR N/R 2/27/1997 US 35 SC Chicago, 25 BE30 N/R LDOR 3/12/1997 US Accident BMG 0 LDOR TX Greenville, 600 Incident CL60 Provincetown, MA 4/10/1997 US ASRS N/A CA NTSB IL N/A Houston, SUN N/A N/A 5/21/1997 US 0 Diego, N/A 0 N/R Bloomington, NTSB AIDS MITRE 6/25/1997 England NTSB London LJ35 B731 LDOR Incident LDOR San FL Accident ORD GMU 7/3/1997 US 350 10 JS41 LDOR OK N/R Incident E120 7/5/1997 US MU30 N/A N/A LDOR Pensacola, LDOR BMI Incident SGR Accident AIDS NKX N/R 145 7/15/1997 1300 LDOR Ardmore, 0 NTSB 0 B190 N/A PNS 7/30/1997 Italy AAIB US Incident Incident N/R SBR1 LDOR ADM 0 60 N/R 0 8/3/1997 C402 IA Florence Accident LDOR N/A N/R 8/19/1997 US B461 N/A LDOR Moines, Incident US 0 N/A EGLC PVC NTSB Avon Park, FL Islands 11/29/1997 Wales 99 Common N/A N/A Des N/A 12/7/1997 England Fairwood Channel AAIB AAIB 80 SW3 ADREP N/A 12/19/1997 US LDOR Accident 10 East Hampton, NY DSM 867 GA 12/19/1997 US NTSB AT43 LDOR F27 FLR Accident PA Savannah, LDOR LDOR TN 1/6/1998 US Accident AIDS Incident 394 VAMP City N/A EGJB 0 Memphis, EGFH 130 1/7/1998 UK 0 Pittsburgh, NTSB ASRS N/R 1/16/1998 London C500 0 AGC LDOR ASRS 375 AAIB 30 1/19/1998 US Accident US LDOR ME N/A N/R Accident LDOR LDOR B461 1/19/1998 US LCY 75 AK Incident 144 Portland, Incident B721 LJ35 LDOR N/A N/A 1/22/1998 US LDOR N/A Incident CO SAV Mekoryuk, Incident ASRS DC10 N/A Van Nuys, CA 0 C560 ASRS N/A 20 MEM AVO Denver, 75 B721 LDOR HTO MITRE Incident 1800 N/A PWM LDOR Incident 215 0 MYU AIDS 355 0 330 DC85 LDOR Incident DEN 0 N/R 550 40 N/A N/R N/A LDOR 30 N/A N/A Incident N/A N/A GLF4 N/A VNY N/R N/R N/A B-11 (continued on next page) 1/22/1998 US CO NE 2/3/1998 US ON Denver, 2/18/1998 Canada Omaha, TSB Peterborough, 2/23/1998 AIDS AIDS 2/26/1998 US US PA C414 OMA MI 100 FA10 LDOR Incident 3/4/1998 US Incident LDOR DC85 YPQ LDOR Pittsburgh, Incident DEN 236 3/11/1998 US Manistee, 0 CO N/R AIDS NTSB Van Nuys, CA 3/14/1998 US ME Aspen, C650 MBL 0 150 3/14/1998 US N/R ME Accident Portland, LDOR N/A WW24 LDOR AGC Incident 3/25/1998 US 24 OH MITRE Portland, 0 MITRE N/A 3/31/1998 AIDS Columbus, N/A AZ AIDS 4/1/1998 US B461 LDOR US AIDS Incident MD81 LDOR 0 ASE Incident PWM N/A 4/19/1998 US 600 Chinle, NE N/R MD80 5/19/1998 US LDOR Incident PWM AIDS GA CL60 Lincoln, LDOR 600 LDOR Incident Des Moines, IA 0 OSU 5/23/1998 US N/R N/A FL Atlanta, C421 N/R E91 AIDS 6/19/1998 Incident Incident LDOR N/R 15 Orlando, N/A 6/21/1998 Spain ASRS LJ35 US N/R N/A N/R Ibiza MITRE NTSB 7/14/1998 US C650 PA LDOR A748 Incident XKS N/A LNK 449 VNY 7/14/1998 US Accident TSB DC91 N/A LDOR PA LDOR N/A N/R Incident ON Pittsburgh, ATL LJ24 Fishers Island, NY 7/22/1998 UK LDOR 200 Accident AIDS 0 Pittsburgh, ORL 50 Canada LDOR 8/6/1998 Canada Kasabonika, 500 N/R TSB MITRE Belfast A320 8/28/1998 US NTSB 0 Incident LDOR MN Accident Spain LEIB B731 LDOR N/A Incident 250 9/26/1998 England N/A 0 B731 Fairoaks LDOR PIT B721 Incident Minneapolis, AIDS PIT 10/24/1998 UK 0 N/R AAIB N/R N/A 150 DSM 11/19/1998 US B461 LDOR LDOR UK Incident AAIB N/A Southampton BE30 LDOR BHD N/R GA 12/18/1998 US Incident FCM N/R C560 23 N/R LDOR UK Accident N/A Atlanta, N/R Accident NY 12/18/1998 US FRK C500 AAIB 765 N/A Rochester, N/A NY 12/24/1998 US N/A UK N/R 0 Rochester, RI 12/26/1998 US ASRS LDOR AIDS 0B8 Incident 140 F100 N/R Providence, WY 12/29/1998 US MITRE N/A SOU Jackson, WY 1/19/1999 US AIDS OH N/A 115 N/A LDOR 262 Jackson, LDOR 1/20/1999 US Incident DC85 CA LDOR Incident Wilmington, B721 MITRE N/A ASRS ATL Incident B721 ROC Chino, AIDS 0 85 ROC LDOR 600 Incident 0 MD80 600 LDOR DC85 LDOR PVD Incident ILN Incident AIDS B731 N/R 800 JAC LDOR 0 0 N/A Incident BE30 110 N/R GLF2 LDOR JAC Incident CNO 100 N/R N/A 150 46 N/A N/A N/R N/A N/A N/A 0 0 N/A N/A N/A B-12

(ft) Veer-off Maximu m (ft) Location Y (ft) Location X Code Airport XCN N/R N/R N/A

Code ICAO Aircraft

Class Event Incident Type Event Source Canada TSB LDOR Accident SW4 YHD 300 0 N/A ASRS LDOR , CA NTSB LDOR Accident GLF2 VNY 1072 451 N/A City/State Amsterdam Netherland TSB LDOR Incident B741 EHAM 100 Manila 0 N/A Country Netherlan ds Philippines Date 2/8/1999 2/16/1999 2/18/1999 US 3/9/1999 US 4/17/1999 US ys Van Nu 4/28/1999 US Columbus, NE 5/4/1999 US Indianapolis, IN 5/8/1999 US Beckley, WV 6/1/1999 US Crossville, TN NTSB 6/19/1999 US MITRE MA Sparta, TN 7/1/1999 US F28 New York, NY NTSB NL 7/19/1999 US YYT Hyannis, Accident TSB MN 420 LDOR AIDS NTSB LDOR Little Rock, AR 7/30/1999 US MN LDOR John's, Minneapolis, ASRS LJ60 Canada HYA 90 7/30/1999 US Accident 745 MN Accident LDOR Minneapolis, AIDS Incident MU30 NTSB AIDS 8/1/1999 Canada St. LDOR DC85 Minneapolis, MITRE NTSB 0 B721 LDOR OLU Incident N/A 8/5/1999 LDOR MSP Accident MN B721 IND LDOR 125 BE40 8/9/1999 US Incident Incident B721 LDOR MSP Incident 150 US AIDS MSP N/A 100 8/14/1999 FA10 LDOR Minneapolis, LDOR BKW 100 30 0 DC10 LDOR MSP 8/19/1999 US 200 US Accident MN Incident CSV Incident LDOR Shetland SF34 216 0 9/6/1999 Scotland Accident Mineral Point, WI FA20 0 0 Minneapolis, ASRS MD82 0 9/19/1999 US N/R MN N/A JFK SRB LIT Saranac Lake, NY 0 9/19/1999 Ireland Shannon Minneapolis, N/A ASRS AIDS DC10 LDOR 0 Incident AAIB Bangkok 9/23/1999 Thailand N/A N/A MSP 350 140 200 800 C208 9/26/1999 US N/R 135 N/A EGPB AIDS GA DC91 Accident LDOR Incident LDOR 10/19/1999 France MSP Gainesville, N/A 30 0 25 ON Paris NTSB 11/22/1999 Canada ASRS LDOR 0 N/A 0 ATSB Dryden, 20 N/A 12/13/1999 US Incident LDOR LJ24 N/A N/A GA 0 12/29/1999 LDOR MD11 Accident LDOR B741 BE99 Incident GVL SNN NC LDOR Atlanta, US Accident 1/1/2000 US BKK Incident 274 N/R 1049 N/A 1/19/2000 US B721 MRJ N/A Charlotte, N/A IN ASRS N/A ASRS N/R 1/20/2000 US 100 MITRE 59 TN Gary, Traverse City, MI DC91 CLT SLK N/R 225 Incident LDOR Sparta, N/A N/A LDOR LDOR N/A Incident 0 30 C550 Incident MITRE MITRE MD11 ASRS CDG PDK N/R 190 20 B721 LDOR Incident N/A GYY FA10 LDOR Incident N/R SRB LDOR 0 N/R 50 N/A 0 Accident N/R DC91 N/R N/A N/A TVC N/A N/A N/A N/R N/R N/A 1/27/2000 US Dallas, TX NTSB LDOR Accident MU30 DAL N/R N/R N/A 2/16/2000 Japan Sapporo ADREP LDOR Accident YS11 OKD N/R N/R N/A 2/29/2000 US Houston, TX MITRE LDOR Incident B731 IAH N/R N/R N/A 3/5/2000 US Burbank, CA NTSB LDOR Accident B731 BUR 200 200 N/A 3/12/2000 US Jackson, WY NTSB LDOR Accident LJ60 JAC 160 0 N/A 3/17/2000 US Hyannis, MA NTSB LDOR Accident F900 HYA 667 0 N/A 3/21/2000 US Killeen, TX NTSB LDOR Accident SF34 ILE 175 3 N/A 4/1/2000 US Eagle, CO AIDS LDOR Incident H25A EGE 9 0 N/A 5/18/2000 US Milwaukee, WI AIDS LDOR Incident AC56 MWC 228 0 N/A 6/29/2000 US Joliet, IL NTSB LDOR Accident BE20 JOT 170 0 N/A 7/1/2000 England Coventry UK AAIB LDOR Accident F27 CVT 852 98 N/A 7/23/2000 Canada Dorval, QC Canada TSB LDOR Incident B741 YUL 700 0 N/A 8/9/2000 US Portland, OR AIDS LDOR Incident C402 PDX 250 0 N/A 9/1/2000 Canada Ottawa, ON ASRS LDOR Incident B721 YOW 100 0 N/A 9/15/2000 Canada Ottawa, ON Canada TSB LDOR Incident B721 YOW 234 0 N/A 10/20/2000 US Saint Louis, MO ASRS LDOR Incident MD82 STL 807 225 N/A 11/28/2000 Canada Fredericton, NB Canada TSB LDOR Incident F28 YFC 320 0 N/A 12/18/2000 Canada Windsor, ON Canada TSB LDOR Incident A124 YQG 340 0 N/A French 12/24/2000 Papeete France BEA LDOR Accident DC10 PPT 230 82 N/A Polynesia 12/29/2000 US Charlottesville, VA NTSB LDOR Accident JS41 CHO 60 0 N/A 1/1/2001 US Glasgow, KY ASRS LDOR Incident BE9L GLW N/R N/R N/A 2/4/2001 US Ft. Pierce, FL NTSB LDOR Accident LJ25 FPR N/R N/R N/A 2/13/2001 US Olympia, WA NTSB LDOR Accident BE20 OLM 442 0 N/A 3/4/2001 US Phoenix, AZ NTSB LDOR Incident B731 PHX 75 0 N/A 3/9/2001 US Bridgeport, CT NTSB LDOR Accident H25A BDR 22 0 N/A 3/12/2001 US Telluride, CO AIDS LDOR Incident LJ35 TEX N/R N/R N/A 3/17/2001 France Lyon France BEA LDOR Incident B731 LYS 279 197 N/A 3/20/2001 US Shreveport, LA ASRS LDOR Incident E110 SHV 110 0 N/A 3/20/2001 US El Paso, TX ASRS LDOR Incident ELP 150 0 N/A 4/4/2001 Canada St. John's, NL Canada TSB LDOR Accident B731 YYT 75 53 N/A 5/28/2001 US Chicago, IL MITRE LDOR Incident B731 ORD 205 0 N/A (continued on next page) B-13 B-14

(ft) Veer-off Maximu m (ft) Location Y (ft) Location X N/R N/R N/A Code Airport Unknown

Code ICAO Aircraft Class Event Type Event LDOR Incident DC85 SIN 968 197 N/A Source AAIB Singapore , CA AIDS LDOR Incident C550 VNY N/R N/R N/A ys City/State Santo Domingo ASRS LDOR Incident B721 SDQ 200 0 N/A Country Dominican Republic Date 6/14/2001 7/20/2001 US 8/16/2001 US 8/28/2001 US Van Nu 8/30/2001 US Portland, ME 11/19/2001 US Saint Paul, MN Unknown 12/1/2001 Unknown Detroit, MI 12/13/2001 US Olathe, KS US ASRS 12/14/2001 AIDS US 1/1/2002 Philadelphia, PA 1/19/2002 Telluride, CO US NTSB AIDS 1/22/2002 US Philadelphia, PA LDOR AIDS LDOR 2/10/2002 US ASRS Incident Miami, FL 3/25/2002 US Incident SF34 AIDS Atlanta, GA AIDS LDOR C404 3/26/2002 US LDOR Elberta, AL PWM Accident 5/1/2002 LDOR US Incident LDOR STP FA10 Cleveland, OH 5/2/2002 MU30 Incident 50 US Incident Anderson, IN LDOR GLF5 5/23/2002 NTSB DET LDOR N/R AIDS C550 US Erie, PA 6/1/2002 US Incident Incident AIDS OJC NTSB 679 PHL SW3 Baltimore, MD C560 6/20/2002 Australia 0 Leakey, TX NTSB N/R 200 LDOR Darwin 7/12/2002 Olathe, KS TEX 250 PHL LDOR Incident 8/13/2002 Ireland 120 LDOR LDOR NTSB Incident MD83 MITRE N/R N/R 8/30/2002 US MU30 Incident Accident N/A Dublin LDOR 0 N/A MIA 9/10/2002 MU30 0 US NTSB BE40 PDK Accident 9/15/2002 Canada AIDS N/A CGF MU30 LDOR LDOR N/R Big Bear City, CA 590 N/R 4AL7 ATSB 11/2/2002 US 440 Gander, NL Lexington, KY AID Accident Incident 11/22/2002 106 Ireland N/R BE40 N/A LDOR DC91 NTSB N/A US 12/1/2002 LDOR N/A 30 Sligo Accident N/A La Porte, TX 135 AAIU BWI LDOR ERI US 0 C560 12/13/2002 NTSB Incident 0 Singapore N/R Incident Canada TSB Soldotna, AK C500 680 12/20/2002 Singapore 49R LDOR 40 B731 US Spokane, WA 12/20/2002 N/A 50 LDOR LDOR OJC Accident AIDS US YPDN 560 C550 N/A LDOR N/A Accident Incident 0 DC85 AIDS N/A 44 N/R Spokane, WA SH36 Accident AAIU 0 L35 LJ25 AIDS White Plains, NY YQX N/A LDOR EIDW 50 406 LEX 900 Incident N/R 47 LDOR 0 N/A ASRS ASRS LDOR C550 N/A 410 Incident LDOR Accident N/A ASTR PPO 30 F27 Incident 0 N/A 0 DH8A SXQ LDOR LDOR N/A 100 10 SXL GEG Incident Incident N/R DH8A H25A N/A 328 N/R N/A GEG N/A 0 HPN N/A N/R 100 200 98 N/R N/A N/A 0 0 N/A N/A N/A N/A 1/6/2003 US Cleveland, OH NTSB LDOR Accident E145 CLE 785 0 N/A 1/6/2003 US Rifle, CO AIDS LDOR Incident GLF4 RIL 160 0 N/A 1/17/2003 Spain Melilla CIAIAC LDOR Accident F50 MLN 710 90 N/A 1/30/2003 England Norwich UK AAIB LDOR Incident E135 NWI 426 33 N/A 2/8/2003 US Bethel, AK MITRE LDOR Incident LJ25 BET N/R N/R N/A 2/15/2003 Italy Florence AIDS LDOR Incident B741 FLR 770 0 N/A 2/15/2003 US Rifle, CO AIDS LDOR Incident CL60 RIL 27 0 N/A 2/17/2003 US Eagle, CO MITRE LDOR Incident LJ60 EGE N/R N/R N/A 2/17/2003 US Eagle, CO AIDS LDOR Incident LJ60 EGE N/R N/R N/A 2/20/2003 Italy Sigonella ASRS LDOR Incident B741 NSY 800 0 N/A 2/27/2003 US Lewisburg, TN AIDS LDOR Incident FA20 LUG 150 0 N/A 3/4/2003 US Stockton, CA AIDS LDOR Incident GLF5 SCK N/R N/R N/A 3/27/2003 US Waukegan, IL MITRE LDOR Incident MU2 UGN N/R N/R N/A 5/18/2003 US Houston, TX NTSB LDOR Accident BE30 IWS 20 0 N/A 5/20/2003 US Minneapolis, MN ASRS LDOR Incident B731 MSP 200 0 N/A 5/28/2003 England Leeds UK AAIB LDOR Incident C560 LBA 525 86 N/A 5/30/2003 US New York, NY NTSB LDOR Incident MD11 JFK 238 0 N/A 7/1/2003 Unknown Unknown ASRS LDOR Incident FA10 Unknown N/R N/R N/A 7/13/2003 US Evansville, IN AIDS LDOR Incident LJ60 EVV 150 0 N/A 9/19/2003 US Del Rio, TX NTSB LDOR Accident LJ25 DRT 1600 100 N/A 10/1/2003 Belgium Liège ASN LDOR Accident B741 LGG 260 0 N/A 11/5/2003 US Naples, FL AIDS LDOR Incident C650 APF N/R N/R N/A 11/17/2003 US Tulsa, OK AIDS LDOR Incident LJ24 RVS 183 0 N/A 1/2/2004 US Pensacola, FL AIDS LDOR Incident MD80 PNS 100 0 N/A 1/3/2004 US Minocqua, WI AIDS LDOR Incident C500 ARV N/R N/R N/A 1/25/2004 US Greensboro, NC AIDS LDOR Incident JS41 GSO N/R N/R N/A 2/20/2004 US Fort Lauderdale, FL NTSB LDOR Accident LJ25 FXE 1689 220 N/A 2/29/2004 US San Diego, CA AIDS LDOR Incident AC68 MYF N/R N/R N/A 3/1/2004 US Mobile, AL AIDS LDOR Incident C500 BFM N/R N/R N/A 3/19/2004 US Pueblo, CO AIDS LDOR Incident E120 PUB N/R N/R N/A 3/20/2004 Unknown Unknown ASRS LDOR Incident B190 Unknown 25 0 N/A 3/26/2004 US Watertown, NY AIDS LDOR Accident B190 ART N/R N/R N/A (continued on next page) B-15 B-16 (ft) Veer-off Veer-off Maximum (ft) Location Y (ft) Location X 25 0 N/A Code Airport Unknown Code ICAO Aircraft Aircraft Class Event Type Event Source City/State Country Date 4/19/2004 Canada Chibougamau, QC Canada TSB BE10 QC LDOR Accident YMT 4/19/2004 Canada 500 Canada Chibougamau, 4/20/2004 5/12/2004 US 0 US AZ 5/20/2004 US HI Mesa, KY 6/3/2004 US Honolulu, N/A New Orleans, LA 6/23/2004 US ON Lexington, AIDS TX AIDS ASRS 7/14/2004 Canada FL Ottawa, LJ55 Houston, NTSB TSB LEX 7/19/2004 US Incident E145 N/R LDOR LDOR Lauderdale, Incident ASRS YOW AIDS FA10 B762 Canada LDOR LDOR 7/20/2004 US Incident Incident 300 FL FFZ HNL Fort LJ55 N/R NY LDOR 8/5/2004 US 75 Accident N/R FXE Tallahassee, NC 950 8/5/2004 US 0 AIDS E145 ASRS LDOR N/A Watertown, Incident IAH LDOR N/R 8/20/2004 Oxford, 0 CL60 50 ART 23 Incident 280 LDOR AIDS Incident Unknown DC91 LDOR Incident TLH N/A N/A Unknown B731 400 LJ25 55 30 HNZ N/A N/A Incident N/R LDOR MSY 0 N/R N/A N/A 200 N/A ASRS N/A 0 LDOR Incident B731 N/A 10/1/2004 11/10/2004 US US 12/1/2004 12/5/2004 US ON Panama City, FL 12/16/2004 Canada CA US Panama City, FL WI Oshawa, 1/1/2005 US Diego, AIDS TSB Teterboro, NJ 1/3/2005 US Madison, ASRS LDOR Canada AIDS Pine Bluff, AR PA31 1/12/2005 US SH36 MYF Accident San AIDS 255 FL Incident LDOR YOO Düsseldorf 1/24/2005 Germany CL60 MSN N/R Jacksonville, Incident 600 LDOR NTSB 0 2/28/2005 US NTSB NC N/R 3/8/2005 LDOR NTSB Lincolnton, B350 LDOR ASN 0 5/20/2005 US LDOR AIDS N/A Accident CRG NC Incident A342 N/A ON US YYZ 1000 557 6/14/2005 US Accident Incident TSB LDOR MA LDOR Wallace, 8/2/2005 Canada Toronto, 30 BE20 B741 LJ35 LDOR LDOR LDOR Norwood, Incident Accident Canada DUS Accident 20 AIDS N/A 8/13/2005 US IPJ CA Teterboro, NJ VA AIDS 2050 GLF4 PFN Accident 9/23/2005 US N/A 300 Diego, PFN Portsmouth, FA10 AIDS 50 10/5/2005 AIDS C500 N/A TEB LDOR Incident San FA10 ACZ LDOR N/R Incident 10/29/2005 US 0 OWD US PBF 220 50 NTSB 400 ON TN 11/15/2005 Canada 100 L18 LDOR N/A BE40 LDOR Incident Incident Hamilton, MYF Nashville, PVG 0 240 200 0 TSB N/A N/R N/R Jacksonville, FL LDOR Canada AIDS ASTR 0 Accident LDOR 490 0 CYHM N/R 272 N/A N/A Incident 0 NTSB N/A H25B LDOR N/A Incident BE20 100 N/A N/A JWN N/A TEB 700 LDOR N/A N/A 230 Incident 0 BE58 0 JAX N/A N/R N/A N/R N/A Accident 12/8/2005 US Chicago, IL NTSB LDOR B737 MDW 500 5 N/A 12/29/2005 US Indianapolis, IN AIDS LDOR Incident LJ25 EYE 20 0 N/A 2/5/2006 England Bedfordshire AAIB LDOR Incident CL60 EGGW 98 0 N/A 2/11/2006 Kuwait Kuwait City AIDS LDOR Incident MD11 OKBK 80 0 N/A 2/20/2006 Unknown Unknown ASRS LDOR Incident MD11 Unknown 220 0 N/A 2/28/2006 US Albuquerque, NM AIDS LDOR Incident LJ25 AEG N/R N/R N/A 3/3/2006 US Teterboro, NJ AIDS LDOR Incident F900 TEB N/R N/R N/A 3/8/2006 Canada Powell River, BC Canada TSB LDOR Accident PA31 CYPW 113 0 N/A 5/30/2006 US Mosinee, WI AIDS LDOR Incident CL60 CWI 400 0 N/A 6/22/2006 Scotland Aberdeen UK AAIB LDOR Incident D328 ABZ 1148 40 N/A 10/6/2006 US Las Vegas, NV AIDS LDOR Incident B190 VGT N/R N/R N/A 10/10/2006 Norway Sørstokken ASN LDOR Accident B461 SRP 500 0 N/A 10/10/2006 England Hampshire AAIB LDOR Incident SW4 EGHL 34 0 N/A 10/13/2006 US Burbank, CA AIDS LDOR Incident GLF2 BUR N/R N/R N/A 12/2/2006 US Seattle, WA AIDS LDOR Incident DH8A SEA N/R N/R N/A 12/12/2006 US Great Bend, KS AIDS LDOR Incident PA31 GBD N/R N/R N/A 1/26/2007 US Pontiac, MI AIDS LDOR Incident CL60 PTK N/R N/R N/A 2/18/2007 US Cleveland, OH NTSB LDOR Accident E170 CLE 310 160 N/A 2/20/2007 England London AAIB LDOR Incident B461 EGLC 33 0 N/A NTSC 3/7/2007 Indonesia Yogyakarta LDOR Accident B731 WARJ 252 30 N/A Indonesia 3/29/2007 US Oklahoma City, OK AIDS LDOR Incident GALX PWA 500 0 N/A 4/12/2007 US Traverse City, MI NTSB LDOR Accident CL60 TVC 500 0 N/A 5/1/2007 US Philadelphia, PA AIDS LDOR Incident C560 PHL 100 0 N/A 6/20/2007 US Laramie, WY NTSB LDOR Accident B190 LAR 160 481 N/A 7/18/2007 US Minneapolis, MN AIDS LDOR Incident B731 MSP 120 0 N/A 11/1/2007 US Fort Lauderdale, FL AIDS LDOR Incident GLF2 FXE 500 0 N/A 12/1/2007 US Madison, WI AIDS LDOR Incident CL60 MSN 45 0 N/A 12/10/2007 US Idaho Falls, ID AIDS LDOR Incident MD80 IDA N/R N/R N/A 1/27/2008 US Spokane, WA AIDS LDOR Incident B731 GEG 500 0 N/A 1/30/2008 US Decatur, IL AIDS LDOR Incident B752 DEC N/R N/R N/A 2/25/2008 US Jackson, WY NTSB LDOR Incident A320 JAC 116 140 N/A (continued on next page) B-17 B-18 (ft) Veer-off Veer-off Maximum (ft) Location Y (ft) Location X Code Airport Code ICAO Aircraft Aircraft Class Event Type Event Source AIDS LDOR Incident MD80 FNL 10 0 10 N/A FNL MD80 Incident AIDS LDOR City/State Fort Collins/Loveland, CO Country Date 3/7/2008 US Columbus, OH 3/7/2008 US 3/15/2008 Columbus, AIDS US 5/4/2008 US B731 CMH 267 Incident LDOR 6/24/2008 US MA 0 12/28/2008 US San Antonio, TX Nantucket, NY TX 1/4/2009 US AIDS Houston, 2/28/2009 US N/A Syracuse, GA AIDS MI AIDS 4/3/1978 US SW3 LDOR Savannah, Incident AIDS E145 5/31/1978 US ACK SYR Detroit, MT AIDS Incident N/R LDOR N/R 6/29/1978 US AIDS PA Lewistown, N/R AIDS 1/10/1979 US TX N/R LDOR LDOR Ebensburg, DC10 CL60 DTW LDOR -50 Incident Incident 1/27/1979 US OK Incident SAV AIDS LDUS GU N/A Lubbock, AIDS 750 Incident 8/17/1979 US N/A City, MU2 LDUS BPT 0 Agana, Incident AIDS LJ35 LWT 8/28/1979 US MP N/R 50 Oklahoma MU2 LDUS 0 Incident FA20 12/21/1979 US LDUS 9G8 AIDS Accident PWA Saipan, SAT N/A -200 VT N/R 12/22/1979 US LJ24 LDUS N/R Incident LBB Burlington, CO 7/25/1980 US 0 AIDS FL N/A -120 0 240 LDUS B721 N/R Incident Denver, 10/19/1980 US N/A GUM AIDS Tampa, -278 AZ 10/22/1980 US 0 B721 LDUS N/A Incident Phoenix, N/A AZ 3/12/1981 US GSN AIDS N/A 0 OH AIDS 0 N/R LDUS Phoenix, 4/18/1981 Incident BA11 Cincinnati, N/A AIDS 11/26/1981 US US AIDS BTV N/R B721 LDUS LDUS AIDS Incident N/A GA 1/19/1982 US -100 TPA Incident TX B721 Augusta, -50 5/16/1982 DEN N/A Rockport, N/A LDUS SBR1 LDUS Incident Sand Point, AK LUK 1/23/1983 Incident US B721 0 -50 LDUS -50 NTSB AIDS 0 3/20/1983 US PHX Incident US DC91 IL IL PHX 7/7/1983 US -500 Chicago, SW3 0 0 LDUS AIDS Hooper Bay, AK -500 Accident 12/12/1983 US N/A Rochelle, RKP LDUS N/A -1821 New York, NY AIDS PA 12/21/1983 US Incident 0 AIDS B721 WA Coatesville, 0 MI 1/5/1984 US AGS N/A 317 BE20 RPJ N/A NTSB TX Incident Detroit, LDUS -300 4/8/1984 US N/R NTSB Seattle, SBR1 LDUS LDUS Incident ORD AIDS NTSB N/A Austin, N/A N/R N/R Incident N/A 0 B721 NTSB AIDS SEA LDUS Incident -360 YS11 LDUS LDUS N/A SBR1 Accident N/R LJ25 40N AUS 0 Incident -50 LDUS Accident SDP LDUS LDUS N/A -20 N/A DHC6 BE20 Accident 0 Incident DET N/A -300 HPB DC85 -125 250 N/A -1270 JFK 0 0 N/A -200 50 N/A N/A 0 N/A N/A 7/12/1984 US Mcalester, OK NTSB LDUS Accident BE18 MLC N/R N/R N/A 5/12/1985 US Lake Geneva, WI NTSB LDUS Accident FA10 C02 -13 5 N/A 6/28/1985 US Charlotte, NC NTSB LDUS Accident PAY3 CLT -1800 0 N/A 8/2/1985 US Dallas, TX NTSB LDUS Accident L101 DFW -6336 360 N/A 9/25/1985 US Dutch Harbor, AK NTSB LDUS Accident B731 DUT N/R N/R N/A 2/7/1986 US Mekoryuk, AK NTSB LDUS Accident DHC6 MYU N/R N/R N/A 2/8/1986 US Harlingen, TX AIDS LDUS Accident B721 HRL -250 0 N/A 5/20/1986 US Hutchinson, KS NTSB LDUS Incident SW3 HUT -3 0 N/A 7/1/1986 US Lincoln, NE NTSB LDUS Accident SW4 LNK -243 0 N/A 9/29/1986 US Liberal, KS NTSB LDUS Accident SBR1 LBL -21 0 N/A 1/4/1987 US Hudson, NY AIDS LDUS Incident LJ55 1B1 -100 0 N/A 2/11/1987 US Oneonta, NY NTSB LDUS Accident BE99 N66 -10 100 N/A 6/22/1987 US Atlanta, GA AIDS LDUS Incident DH8A ATL N/R N/R N/A 9/28/1987 US Saint Louis, MO AIDS LDUS Incident MD80 STL -30 0 N/A 11/23/1987 US Homer, AK NTSB LDUS Accident B190 HOM -159 0 N/A 12/5/1987 US Lexington, KY NTSB LDUS Accident H25A LEX N/R N/R N/A 2/16/1988 US Groton, CT AIDS LDUS Incident SF34 GON -150 0 N/A 6/1/1988 US New York, NY NTSB LDUS Incident B741 JFK N/R N/R N/A 7/26/1988 US Morristown, NJ NTSB LDUS Accident LJ35 MMU -660 75 N/A 9/19/1988 US San Diego, CA ASRS LDUS Incident SAN -50 0 N/A 12/19/1988 US Sandusky, OH ASRS LDUS Incident SKY -60 0 N/A 3/15/1989 US Lafayette, IN NTSB LDUS Accident YS11 LAF -510 13 N/A 4/13/1989 US Scottsdale, AZ NTSB LDUS Accident H25B SCF -10 0 N/A 5/6/1989 US Columbia, TN NTSB LDUS Accident E110 MRC -2350 20 N/A 7/19/1989 US Sioux City, IA NTSB LDUS Accident DC10 SUX -198 761 N/A 8/21/1989 US Gold Beach, OR NTSB LDUS Accident BE9L 4S1 -50 150 N/A 12/26/1989 US Pasco, WA NTSB LDUS Accident JS31 PSC -1200 20 N/A 1/17/1990 US West Point, MS NTSB LDUS Accident BE40 M83 -6 0 N/A 1/19/1990 US Little Rock, AR NTSB LDUS Accident GLF2 LIT -1600 0 N/A 5/4/1990 US Wilmington, NC NTSB LDUS Accident NOMA ILM -600 0 N/A 11/29/1990 US Sebring, FL NTSB LDUS Accident C550 SEF -100 60 N/A 12/16/1990 US Marshfield, WI AIDS LDUS Incident C500 MFI N/R N/R N/A (continued on next page) B-19 B-20 (ft) Veer-off Veer-off Maximum (ft) Location Y (ft) Location X Code Airport Code ICAO Aircraft Aircraft Class Event Type Event Source City/State Hong Kong ASRS LDUS Incident B741 HKG -150 0 N/A Hong Kong ASRS LDUS Incident B741 HKG -900 0 N/A Country Hong Kong Hong Kong Date 12/20/1990 US OR 5/15/1991 US TN Mcminnville, 10/19/1991 US Nashville, AIDS AK 11/15/1991 DE NTSB Allakaket, US 6/16/1992 US Castle, AK NTSB 8/8/1992 US LDUS NTSB New B721 LDUS Incident Incident FA10 11/5/1992 Nuiqsut, BNA Brigham City, UT BE20 MMV -408 NTSB LDUS 7/19/1993 US Accident US ILG MA N/R BE99 LDUS AQT 7/30/1993 US -1320 -50 MA BE99 Accident 0 Nantucket, Accident LDUS AIDS 12/8/1993 ASRS AET 0 N/R Nantucket, San Antonio, TX 0 1/24/1994 AIDS -100 US 2/19/1995 US N/A US OR LDUS Incident WY N/A 3/3/1995 US ACK N/A City 30 N/A LDUS B731 LDUS AIDS Portland, -150 Incident Dallas, TX 6/19/1995 Panama ACK Gillette, Panama -50 ASRS NTSB Incident Key Largo, FL 9/18/1995 US 0 CA GCC ASRS WW24 -50 N/A H25A 10/12/1995 US Chino, Accident 0 LDUS B721 OH LDUS 11/19/1995 US LDUS Incident BMC 0 PDX TN LDUS B741 NTSB Cleveland, N/A AK 1/7/1996 US Incident NTSB -350 PTY NTSB Incident Anchorage, 8/31/1996 US -350 N/R Nashville, N/A NTSB TX SW4 NTSB N/A 0 10/19/1996 US AIDS SW3 DC91 Lubbock, BNA LDUS AK -90 0 Accident NY 4/7/1997 US CNO LDUS Accident SAT LDUS LDUS -1000 AIDS LDUS Flushing, 8/13/1997 US N/R Stebbins, GLF2 KY Accident 0 N/A Incident NTSB LDUS Incident 75 8/14/1997 US CLE N/R Incident GA N/A C441 Lexington, B731 NTSB PA31 WBB LJ35 -153 B721 LDUS N/R NTSB Incident 10/19/1997 ANC Accident Dalton, LDUS LBB N/A N/A N/R N/A -10 0 DFW 07FA N/R NTSB LDUS FA20 N/R LDUS MD88 Accident LEX Accident -1095 LGA 0 N/R -13 -35 N/A BE20 -303 N/A LDUS Accident DNN -1105 N/A 215 N/A 0 N/A 95 135 0 N/A N/A N/A N/A N/A 11/13/1997 US IL WV 2/9/1998 US Wheeling, Chicago, 2/19/1998 NTSB NTSB B721 ORD -300 Accident LDUS LDUS 500 BE65 Accident HLG N/A -90 125 N/A 2/11/1999 2/19/1999 US US FL 3/30/1999 England Newquay Miami, 3/30/1999 US AR Grand Island, NE ASRS Rogers, AAIB NTSB AIDS A30B LDUS Incident MIA -75 C550 LDUS Incident LJ35 LDUS EGHQ -266 Accident ROG -12 0 LDUS 0 100 Incident N/A GLF5 N/A N/A GRI N/R N/R N/A 5/19/1999 US New York, NY ASRS LDUS Incident B762 JFK -100 0 N/A 9/24/1999 Canada St. John's, NL Canada TSB LDUS Accident A320 YYT -250 0 N/A 12/30/2000 US Salt Lake City, UT AIDS LDUS Incident MD90 SLC -400 0 N/A French 5/25/2001 Cayenne France BEA LDUS Incident A343 CAY -98 0 N/A Guiana 6/12/2001 US Salina, KS NTSB LDUS Accident LJ25 SLN -2254 85 N/A 9/19/2001 US Indianapolis, IN NTSB LDUS Accident BE20 IND -621 0 N/A 10/20/2001 US Houston, TX ASRS LDUS Incident B731 IAH -100 0 N/A 1/15/2002 US Kings Ford, MI AIDS LDUS Incident SW3 IMT N/R N/R N/A 7/26/2002 US Tallahassee, FL NTSB LDUS Accident B721 TLH -1677 454 N/A 10/15/2002 Canada Ontario, ON AIDS LDUS Incident B741 ONT -50 0 N/A 10/20/2002 US Ontario, CA ASRS LDUS Incident B741 ONT -45 0 N/A 1/5/2003 US Oklahoma City, OK AIDS LDUS Incident SBR1 PWA N/R N/R N/A 4/9/2003 US Du Bois, PA NTSB LDUS Accident SH33 DUJ -500 -50 N/A 6/28/2003 US Goodnews, AK NTSB LDUS Accident SW3 GNU -100 0 N/A 10/9/2003 US Montague, CA AIDS LDUS Incident BE99 1O5 N/R N/R N/A 11/18/2003 US Dallas, TX NTSB LDUS Accident C550 DFW -350 0 N/A 1/26/2004 US Prescott, AZ AIDS LDUS Incident C560 PRC N/R N/R N/A 6/6/2004 US San Jose, CA AIDS LDUS Incident H25A SJC N/R N/R N/A 8/25/2004 US Venice, FL NTSB LDUS Accident C550 VNC -30 0 N/A 1/9/2007 Canada Fort St. John, BC Canada TSB LDUS Incident JS31 CYXJ -320 0 N/A 12/17/2007 US Vernal, UT AIDS LDUS Incident BE99 VEL -50 0 N/A 7/13/2008 US Saratoga Springs, NY AIDS LDUS Incident LJ45 5B2 N/R N/R N/A 9/15/2008 US Nantucket, MA AIDS LDUS Incident C414 ACK N/R N/R N/A 1/27/2009 US Lubbock, TX NTSB LDUS Accident AT43 LBB -630 0 N/A 1/10/1978 US White Plains, NY AIDS LDVO Incident SBR1 HPN N/A N/A N/R 1/25/1978 US Owensboro, KY AIDS LDVO Incident FA10 OWB N/A N/A N/R 1/26/1978 US Flint, MI AIDS LDVO Incident LJ25 FNT N/A N/A N/R 9/4/1978 US Angier, NC AIDS LDVO Incident 78NC N/A N/A N/R 9/5/1978 US Lafayette, IN AIDS LDVO Incident C500 LAF N/A N/A N/R 1/29/1979 US Independence, KS AIDS LDVO Incident SW3 IDP N/A N/A N/R 2/2/1979 US Grand Rapids, MI AIDS LDVO Incident LJ24 GRR N/A N/A N/R (continued on next page) B-21 B-22 (ft) Veer-off Veer-off Maximum (ft) Location Y (ft) Location X N/A N/R N/A N/R Code Airport Unknown Unknown Code ICAO Aircraft Aircraft Class Event Type Event Source City/State Country Date 2/7/1979 US Elko, NV 2/7/1979 US 2/28/1979 US Elko, TN 4/4/1979 Morristown, AIDS AIDS 4/29/1979 US AK US EKO 7/28/1979 US N/A ID Incident Fairbanks, LDVO 8/15/1979 US SW2 LDVO TX AIDS Incident Downey, N/A MOR 12/29/1979 Dayton, N/A OH Campbellton, AIDS IL US AIDS 1/6/1980 US N/R GLF5 LDVO Incident PAFA N/A Chicago, N/A C500 LDVO Incident AIDS AC68 LDVO 0XA5 Incident Van Nuys, CA U58 N/A AIDS N/R N/A WW24 N/A Incident LDVO N/A N/R N/A AIDS N/R LDVO N/R Incident LJ23 LDVO DAY Incident GLF5 N/A VNY N/A N/A N/A N/R N/R 1/16/1980 US WV 3/11/1980 US NY Clarksburg, AIDS Peter 3/13/1980 US MD Islip, 10/1/1980 England Saint Hagerstown, AIDS 10/2/1980 US GA7 LDVO OH Incident AIDS CKB AAIB 10/26/1980 US N/A Cleveland, SW4 NY 11/18/1980 US LDVO Incident DE AIDS HGR Flushing, C500 Castle, 12/5/1980 US SW3 N/A LDVO N/A LDVO Incident NY Accident EGJJ ISP New 1/13/1981 US N/A AIDS IL FA10 Islip, LDVO AIDS N/A Incident N/A N/R 2/11/1981 US CLE IN Savoy, N/A N/A 3/17/1981 US AZ N/A Indianapolis, CO N/R LDVO AIDS AIDS 9/6/1981 US Incident LDVO SW2 N/A Tucson, 548 AIDS Incident SW3 10/2/1981 US Denver, N/R KY ILG LGA 10/15/1981 US AC90 AIDS AIDS MO LDVO AC90 Incident N/R LDVO Incident ISP Lexington, N/A IND N/A AC68 Louis, LDVO 10/31/1981 US Incident AIDS CMI GLF2 DEN N/A N/A N/A Saint Incident AIDS MS N/A 11/23/1981 US LDVO UT MN LJ24 LDVO Incident N/A Jackson, N/A Paul, 12/17/1981 TUS N/A N/A N/A SW2 LDVO AIDS City, Incident N/A N/A Saint US 1/2/1982 US LEX AIDS N/R LDVO GA N/R N/A BE20 AIDS N/R CDC 1/6/1982 US N/R Incident N/R DC6 Cedar N/A Incident N/A N/R LDVO 1/15/1982 US Atlanta, STL GA N/A Van Nuys, CA N/A LDVO 2/2/1982 AIDS N/R N/A Incident Atlanta, FA10 LDVO Incident 2/24/1982 BE20 N/R SW2 STP N/R US PDK Incident N/A JAN 4/8/1982 LDVO AIDS US N/A N/A AIDS 5/18/1982 N/A N/A US US Port Clinton, OH SW2 LDVO Incident N/R N/A N/R Chicago, IL N/A Teterboro, NJ LDVO N/R AIDS Gillette, WY N/R Incident LJ24 NTSB AIDS LDVO VNY NTSB Incident N/A LDVO BE20 LDVO Incident LDVO Incident SW4 PCW LJ35 N/A Incident G159 N/A ORD TEB GCC N/A N/R N/A N/A N/A N/A N/A N/R N/A N/R N/R 20 5/21/1982 US Dayton, OH NTSB LDVO Incident BA11 DAY N/A N/A N/R 6/8/1982 US Gillette, WY NTSB LDVO Incident G159 GCC N/A N/A N/R 6/16/1982 US Scottsbluff, NE AIDS LDVO Incident SW4 BFF N/A N/A N/R 9/5/1982 England Stansted Mountfitchet AAIB LDVO Incident DC85 EGSS N/A N/A 238 10/13/1982 US Atlanta, GA AIDS LDVO Incident H25A Unknown N/A N/A N/R 1/3/1983 US Sacramento, CA AIDS LDVO Incident SW3 SAC N/A N/A N/R 2/5/1983 US Atlanta, GA AIDS LDVO Incident MU30 PDK N/A N/A N/R 2/6/1983 US Saint Paul Island, AK AIDS LDVO Incident LJ24 SNP N/A N/A N/R 2/16/1983 US Manchester, NH AIDS LDVO Incident WW24 MHT N/A N/A N/R 2/24/1983 US Anchorage, AK AIDS LDVO Incident LJ24 ANC N/A N/A N/R 3/1/1983 US Houston, TX AIDS LDVO Incident AC11 HOU N/A N/A N/R 3/1/1983 US Corpus Christi, TX AIDS LDVO Incident SW3 CRP N/A N/A N/R 3/17/1983 US Denver, CO AIDS LDVO Incident AC90 DEN N/A N/A N/R 3/22/1983 US Ulysses, KS AIDS LDVO Incident BE20 ULS N/A N/A N/R 3/27/1983 US Chicago, IL AIDS LDVO Incident LJ55 PWK N/A N/A N/R 4/5/1983 US Hutchinson, KS NTSB LDVO Accident AC50 HUT N/A N/A 5 4/14/1983 US Elkhart, IN AIDS LDVO Incident SW2 GSH N/A N/A N/R 5/6/1983 US Lincoln, NE AIDS LDVO Incident SW3 LNK N/A N/A N/R 6/1/1983 US Las Vegas, NV NTSB LDVO Accident C402 VGT N/A N/A 88 7/18/1983 US El Paso, TX AIDS LDVO Incident LJ25 ELP N/A N/A N/R 9/12/1983 US Destin, FL AIDS LDVO Incident C500 DTS N/A N/A N/R 11/8/1983 US Franklin, PA NTSB LDVO Accident BE18 FKL N/A N/A 130 11/11/1983 US Cleveland, OH AIDS LDVO Incident G159 LNN N/A N/A N/R 11/23/1983 US Chicago, IL AIDS LDVO Incident LJ55 PWK N/A N/A N/R 11/28/1983 US Johnstown, PA AIDS LDVO Incident G159 JST N/A N/A N/R 2/22/1984 US Cordova, AK NTSB LDVO Incident E110 CDV N/A N/A 10 7/3/1984 US Denver, CO NTSB LDVO Incident B722 Stapleton N/A N/A N/R 7/7/1984 US Gualala, CA NTSB LDVO Accident C500 Q69 N/A N/A N/R 7/8/1984 US Oakland, CA AIDS LDVO Incident SBR1 OAK N/A N/A N/R 8/18/1984 US Cedar City, UT AIDS LDVO Incident CDC N/A N/A N/R 9/29/1984 US Houston, TX NTSB LDVO Incident DHC6 IAH N/A N/A 30 12/5/1984 US Minneapolis, MN AIDS LDVO Incident SW2 MSP N/A N/A N/R (continued on next page) B-23 B-24 (ft) Veer-off Veer-off Maximum (ft) Location Y (ft) Location X N/A N/R N/A N/R N/A N/R Code Airport Unknown Unknown Unknown Code ICAO Aircraft Aircraft Class Event Type Event Source City/State Country Date 12/12/1984 US MI 12/19/1984 Detroit, US 12/19/1984 US AR 1/29/1985 Springdale, 1/31/1985 US US AIDS CO Salt Lake City, UT 3/30/1985 AIDS Denver, 9/28/1985 US US CO AIDS LDVO Dobbins Afb, GA 10/25/1985 US AIDS Incident LJ24 Broomfield, LDVO AIDS CA 11/14/1985 US Incident SBR1 YIP Monterey, Fort Lauderdale, FL IL 12/5/1985 US NTSB XNA LJ35 IN LDVO Incident N/A Bloomington, N/A DEN 12/20/1985 US WW24 LDVO BJC LDVO Incident AIDS Lafayette, N/A NTSB AIDS OH N/A Incident AIDS N/A Cleveland, N/A N/A LDVO LJ25 N/A LDVO AIDS LDVO Incident WW24 Accident Incident N/R H25A F27 LDVO MRY LDVO N/R Incident N/R LAF SLC L188 N/R N/A N/A BMI Incident LDVO C402 MGE N/A N/A Incident LJ35 N/A N/A FLL N/A N/A N/R N/R N/A N/A N/R N/A N/R N/A 70 50 2/21/1986 US TX 5/16/1986 Dallas, IL 7/1/1986 US US 8/17/1986 US Chicago, CA AIDS 10/30/1986 US AIDS MO Llano, Laramie, WY Louis, 11/6/1986 US MA LJ35 FA10 DPA LDVO Incident Saint Incident AIDS N/A 11/20/1986 US LDVO NY AIDS Bedford, IL Plains, 1/9/1987 US N/A AIDS AIDS AIDS White 2/25/1987 NTSB Bloomington, LDVO LDVO N/R Incident AC90 2/27/1987 US B190 Accident OK US BMI MI 46CN Incident N/A AIDS N/A LDVO AC95 3/16/1987 US LDVO Incident City, BED LDVO Kalamazoo, Incident C550 N/A 3/18/1987 US N/A AIDS GA N/A LDVO Oklahoma FL HPN Durango, CO F900 5/1/1987 US LDVO Incident Atlanta, N/R OKC N/A N/A Accident AIDS 8/12/1987 US N/A Jacksonville, N/R IN WW24 AZO LDVO Incident BE99 9/18/1987 US N/A AIDS LJ25 NV CRG Marion, 200 Incident N/A LDVO N/A N/A 10/23/1987 US LAR NTSB Reno, N/A CA 11/17/1987 N/A C550 AIDS LDVO Incident N/R PDK Avalon, US 12/9/1987 N/R N/A N/A AIDS N/R N/R 12/14/1987 US US CL60 LDVO Incident LDVO IL MZZ 12/24/1987 US NTSB N/A N/A Port Angeles, WA AC68 Chicago, LDVO CO 12/26/1987 US Incident N/A FL Incident RNO N/A Aspen, B732 Van Nuys, CA Lauderdale, N/R AIDS N/A LDVO Fort NTSB C402 Accident AIDS N/A DRO AVX 90 N/R AIDS N/A LDVO Incident AIDS AC11 N/R N/A LDVO FXE Incident LDVO BE20 N/A LDVO N/A MDW Incident Incident WW24 N/A ASE BE99 N/A LDVO 130 N/A N/A N/A CLM Incident C550 N/A N/R N/R N/A N/R VNY N/R N/A N/A N/A 50 N/R 12/27/1987 US Denver, CO NTSB LDVO Incident MD80 DEN N/A N/A 70 1/4/1988 US Belmar, NJ AIDS LDVO Incident LJ25 BLM N/A N/A N/R 1/7/1988 US Oakland, CA AIDS LDVO Incident GLF5 OAK N/A N/A N/R 1/13/1988 US Fort Lauderdale, FL AIDS LDVO Incident LJ25 FLL N/A N/A N/R 1/21/1988 US Dallas, TX AIDS LDVO Incident FA10 DAL N/A N/A N/R 1/22/1988 US Starkville, MS AIDS LDVO Incident AC90 STF N/A N/A N/R 2/2/1988 US Denver, CO NTSB LDVO Accident CVLT DEN N/A N/A 5 2/4/1988 US Newburgh, NY AIDS LDVO Incident LJ55 SWF N/A N/A N/R 2/19/1988 US Lansing, MI AIDS LDVO Incident L29B LAN N/A N/A N/R 3/15/1988 US Teterboro, NJ AIDS LDVO Incident BE20 TEB N/A N/A N/R 4/15/1988 US Seattle, WA NTSB LDVO Accident DH8A SEA N/A N/A 1675 7/31/1988 US Saint Louis, MO AIDS LDVO Incident BE20 SUS N/A N/A N/R 8/29/1988 US Bakersfield, CA AIDS LDVO Incident AC90 BFL N/A N/A N/R 9/21/1988 US Van Nuys, CA AIDS LDVO Incident C500 VNY N/A N/A N/R 10/7/1988 US Durango, CO AIDS LDVO Incident BE20 DRO N/A N/A N/R 10/14/1988 US Anchorage, AK AIDS LDVO Incident YS11 ANC N/A N/A N/R 3/2/1989 US Rifle, CO AIDS LDVO Incident SBR1 RIL N/A N/A N/R 3/3/1989 US Rockford, IL AIDS LDVO Incident WW24 RFD N/A N/A N/R 3/17/1989 US Waukegan, IL AIDS LDVO Incident FA10 UGN N/A N/A N/R 3/31/1989 US Windsor Locks, CT AIDS LDVO Incident CL60 BDL N/A N/A N/R 10/19/1989 US Waukegan, IL AIDS LDVO Incident C650 UGN N/A N/A N/R 11/28/1989 US Houma, LA AIDS LDVO Incident C550 HUM N/A N/A N/R 12/10/1989 US Denver, CO AIDS LDVO Incident WW24 APA N/A N/A N/R 12/27/1989 US Merced, CA AIDS LDVO Incident LJ25 MCE N/A N/A N/R 1/24/1990 US Olathe, KS AIDS LDVO Incident LJ55 IXD N/A N/A N/R 2/20/1990 US Chicago, IL AIDS LDVO Incident C650 ARR N/A N/A N/R 6/6/1990 US Alton, IL AIDS LDVO Incident LJ35 ALN N/A N/A N/R 8/8/1990 US Ames, IA AIDS LDVO Incident SBR1 AMW N/A N/A N/R 10/12/1990 US Burlington, VT AIDS LDVO Incident B190 BTV N/A N/A N/R 11/18/1990 US Atlanta, GA AIDS LDVO Incident FA10 PDK N/A N/A N/R 12/10/1990 US Indianapolis, IN AIDS LDVO Incident AC90 IND N/A N/A N/R 1/9/1991 US Philadelphia, PA AIDS LDVO Incident WW24 PNE N/A N/A N/R (continued on next page) B-25 B-26 (ft) Veer-off Veer-off Maximum (ft) Location Y (ft) Location X Code Airport Code ICAO Aircraft Aircraft Class Event Type Event Source City/State Mayaguez NTSB LDVO Incident C212 MAZ N/A N/A 45 Country Puerto Rico Date 1/13/1991 US PA 1/30/1991 US OH Palmyra, 2/5/1991 Cleveland, AIDS 2/15/1991 US AIDS KY US OH 3/3/1991 US Louisville, 4/10/1991 US AC68 Columbus, LDVO AIDS AIDS VA Incident 58N SBR1 LDVO Incident CGF 5/1/1991 Cochran, GA N/A LJ35 Richmond, N/A OSU 6/11/1991 US Incident N/A AIDS LDVO WA SW3 US LDVO Incident 7/19/1991 US N/A SDF NC N/A Seattle, N/A IL N/A 9/5/1991 US SBR1 Boone, NTSB LDVO Incident RIC N/R 11/11/1991 US N/R AIDS Waukegan, N/R Oxford, CT AIDS N/A N/A NY 1/10/1992 AIDS FA10 UGN Rochester, 1/27/1992 US N/A KS US Incident DHC6 KY LDVO LDVO N/A Incident N/R BFI LDVO 3/31/1992 US City, AIDS N/A N/A Louisville, LDVO AIDS Incident NTSB 4/11/1992 NC14 Incident AIDS N/R Garden N/A Coeur D Alene, ID N/R 4/12/1992 US US N/A NY LDVO LDVO 4/20/1992 US Incident N/A IL Incident GCK Albany, LJ35 B190 LDVO Incident 4/24/1992 US AIDS N/A N/R LOU OH LDVO ROC Waukegan, N/A 48A South Lake Tahoe, CA AIDS N/R 6/24/1992 N/A AIDS Cleveland, Accident N/A AIDS AIDS WW24 N/A N/A GLF4 LDVO N/A Incident LDVO N/R ALB FA10 OXC LDVO Incident UGN N/A N/R LJ35 LDVO N/A Incident Incident CGF LDVO N/A N/R N/A LJ35 N/A N/A N/A Incident N/A COE SW2 N/R N/R N/A 75 N/R N/A TVL 100 N/A N/A N/A N/R N/R 6/25/1992 US Boston, MA FL AIDS US 6/25/1992 SW4 BOS N/A Boston, NTSB AC90 PIE Petersburg, 8/2/1992 US Incident N/A N/A LDVO Accident LDVO 12/26/1992 US Saint 85 N/A KS 2/21/1993 US WI WA Wellington, AIDS 3/24/1993 US N/R FL Grove, Bellingham, AIDS 4/14/1993 AIDS AIDS Soldiers Creek, 8/7/1993 US C560 FL US LDVO 7FL6 Incident N/A WS51 AIDS Incident B461 N/A 8/28/1993 US LDVO LDVO Incident Spruce Lauderdale, BLI LDVO N/A 8/30/1993 US Incident CT SW2 N/A Fort N/A LJ23 Dallas, TX 11/9/1993 US LDVO Incident N/R IN EGT Hartford, FXE OH 12/22/1993 US N/A N/A N/A SW3 CGF N/A Indianapolis, N/R US AIDS MITRE AIDS VT 1/3/1994 N/A Cleveland, Accident Morrisville, N/R N/A LDVO N/A 25 NTSB BE40 AIDS LDVO SBR1 Incident LDVO Incident HFD IND N/R N/A N/A N/R LDVO N/A N/A Incident LDVO BE20 MVL Accident N/R N/A N/R DC10 DFW N/A N/A N/R N/A 175 1/25/1994 US Lexington, KY AIDS LDVO Incident SW2 LEX N/A N/A N/R 2/10/1994 US Chicago, IL AIDS LDVO Incident FA50 ORD N/A N/A N/R 2/24/1994 US Teterboro, NJ AIDS LDVO Incident WW24 TEB N/A N/A N/R 4/14/1994 US Lincoln, NE AIDS LDVO Incident FA10 LNK N/A N/A N/R 5/15/1994 US Coeur D Alene, ID AIDS LDVO Incident SW4 COE N/A N/A N/R 6/8/1994 US Beckley, WV AIDS LDVO Incident MU30 BKW N/A N/A N/R 6/30/1994 US Gambell, AK AIDS LDVO Incident BE18 GAM N/A N/A N/R 7/6/1994 US Point Lookout, MO AIDS LDVO Incident BE20 PLK N/A N/A N/R 7/7/1994 US Las Vegas, NV AIDS LDVO Incident C402 LAS N/A N/A N/R 7/17/1994 US Plymouth, FL AIDS LDVO Incident X04 N/A N/A N/R 7/27/1994 US Sioux Falls, SD AIDS LDVO Incident T18 FSD N/A N/A N/R 8/13/1994 US Santa Fe, NM AIDS LDVO Incident SAF N/A N/A N/R 8/28/1994 US Oakland, CA AIDS LDVO Incident LJ24 OAK N/A N/A N/R 8/31/1994 US Fort Smith, AR AIDS LDVO Incident BE20 FSM N/A N/A N/R 9/2/1994 US Chicago, IL AIDS LDVO Incident DC91 MDW N/A N/A N/R 9/17/1994 US Parkersburg, WV AIDS LDVO Incident WW24 PKB N/A N/A N/R 9/26/1994 US Fort Lauderdale, FL MITRE LDVO Incident C402 FLL N/A N/A 60 10/17/1994 US Grand Canyon, AZ MITRE LDVO Incident C402 GCN N/A N/A 50 10/20/1994 US Dyersburg, TN AIDS LDVO Incident SBR1 DYR N/A N/A N/R 10/25/1994 US Shreveport, LA AIDS LDVO Incident BE18 SHV N/A N/A N/R 10/26/1994 Unknown Unknown AIDS LDVO Incident BE18 Unknown N/A N/A N/R 10/27/1994 US Washington, PA AIDS LDVO Incident SW3 AFJ N/A N/A N/R 11/1/1994 US Fort Lauderdale, FL MITRE LDVO Incident C402 FLL N/A N/A N/R 11/15/1994 US Fort Lauderdale, FL AIDS LDVO Incident B731 FLL N/A N/A N/R 11/23/1994 US Akron, OH AIDS LDVO Incident AC90 CAK N/A N/A N/R 12/13/1994 US Chicago, IL AIDS LDVO Incident SBR1 DPA N/A N/A N/R 1/10/1995 US Cahokia, IL AIDS LDVO Incident FA20 CPS N/A N/A N/R 1/26/1995 US Lexington, KY AIDS LDVO Incident SW4 LEX N/A N/A 35 1/31/1995 US Chinle, AZ AIDS LDVO Accident C421 E91 N/A N/A N/R 3/3/1995 US Salt Lake City, UT AIDS LDVO Incident SW4 SLC N/A N/A N/R 3/7/1995 US Tupelo, MS AIDS LDVO Incident H25A TUP N/A N/A N/R 4/10/1995 US Dallas, TX AIDS LDVO Incident C402 DAL N/A N/A N/R (continued on next page) B-27 B-28 (ft) Veer-off Veer-off Maximum (ft) Location Y (ft) Location X Code Airport Code ICAO Aircraft Aircraft Class Event Type Event Source City/State Amsterdam NTSB LDVO Incident B742 EHAM N/A N/A N/R N/A N/A EHAM B742 Incident LDVO Amsterdam NTSB Country Netherlands Date 5/2/1995 US Shreveport, LA 5/2/1995 US 5/5/1995 AIDS Shreveport, 5/17/1995 US LA BE18 SHV US CA N/A Incident 6/3/1995 US LDVO Shreveport, NE 6/7/1995 US AIDS Susanville, AIDS N/A 6/30/1995 US Omaha, Rapid City, SD MI C421 SVE N/R 7/17/1995 US Incident N/A CA AIDS LDVO PA BE18 LDVO Saginaw, Incident SHV 7/24/1995 US NY OMA STAR N/A N/A N/A Allentown, Nuys, MITRE AIDS Incident 8/1/1995 US LDVO AIDS AIDS Binghamton, B752 OR AIDS VNY N/A N/A N/R 8/3/1995 US Incident Van N/A LDVO OR 8/3/1995 US FA10 LDVO Portland, Incident N/R N/A F28 MBS LDVO Incident MITRE LJ55 8/14/1995 US LDVO N/R N/A Incident Portland, CO D328 ABE BGM PDX NTSB N/R LDVO N/A 8/18/1995 US Incident N/A N/A LDVO OH Denver, D328 PDX N/A 9/14/1995 US N/A Incident GA N/A Accident Columbus, LDVO N/A N/A 9/16/1995 US MITRE AC90 AIDS SC Atlanta, N/A N/R 62 10/23/1995 US PR Charleston, B752 N/R N/R RAP LDVO Juan, Accident 11/8/1995 US AIDS N/R APA AIDS MI B731 LDVO Incident N/A San 11/17/1995 US CMH N/A Saginaw, N/A AIDS TX 11/21/1995 US LJ24 LDVO Incident MD80 N/A LDVO Incident CHS AIDS Brenham, PDK ID 12/10/1995 N/A N/A N/A Rexburg, N/R LDVO AIDS N/A Incident N/R BE18 C402 LDVO N/A Incident N/A MBS AIDS SJU N/A N/R N/R N/A LDVO N/R Incident WW24 N/A 11R LDVO Incident BE30 N/A N/A N/R RXE N/A N/R N/A N/A N/R N/R 12/19/1995 US MO Louis, 1/24/1996 US MI Saint AIDS 1/26/1996 US GA Detroit, 1/31/1996 US NJ Atlanta, TN 2/2/1996 US MITRE Morristown, LDVO 2/28/1996 AIDS AIDS Incident DC91 Memphis, AIDS FA10 STL 3/20/1996 US LDVO Accident US DTW TN N/A WV MEM CVLP N/A 4/2/1996 US N/A E120 WW24 Incident LDVO MMU LDVO Incident Portland, Incident LDVO AL N/A ATL 4/6/1996 US Beckley, N/A N/A N/A AIDS AIDS AIDS Grand Canyon, AZ 4/20/1996 US N/A Birmingham, NM N/A CO N/R N/A SH33 H25A EGBB 5/1/1996 US BKW N/A N/R N/A AIDS Incident Incident Albuquerque, LDVO LDVO MITRE 5/10/1996 LJ25 LDVO Denver, N/A Incident N/R N/R N/A PLD AIDS 0 US N/A N/R LDVO Incident N/R AEG SBR1 DEN N/A Incident N/A LDVO LDVO N/A Dallas, TX N/A Accident N/A 75 PA31 N/R N/R GCN NTSB N/A LDVO N/A Incident B733 N/R DFW N/A N/A 75 5/16/1996 US Houston, TX MITRE LDVO Accident MU2 HOU N/A N/A N/R 7/5/1996 US Moultonboro, NH AIDS LDVO Incident C414 5M3 N/A N/A 175 7/27/1996 US Saint Paul, MN AIDS LDVO Incident CONI STP N/A N/A N/R 8/3/1996 US West Palm Beach, FL AIDS LDVO Incident B731 PBI N/A N/A N/R 9/30/1996 US Aspen, CO MITRE LDVO Accident ASTR ASE N/A N/A N/R 10/9/1996 US Pittsburgh, PA AIDS LDVO Incident LJ25 AGC N/A N/A N/R 12/11/1996 US Grand Forks, ND AIDS LDVO Incident LJ35 GFK N/A N/A N/R 12/15/1996 US Honolulu, HI NTSB LDVO Accident DH8A HNL N/A N/A N/R 12/20/1996 US Denver, CO AIDS LDVO Incident LJ25 DEN N/A N/A N/R 1/3/1997 US Watertown, SD AIDS LDVO Incident WW24 ATY N/A N/A N/R 1/3/1997 England Liverpool AAIB LDVO Accident SH33 EGGP N/A N/A N/R 1/8/1997 US El Paso, TX AIDS LDVO Incident FA20 ELP N/A N/A N/R 1/16/1997 US Terre Haute, IN AIDS LDVO Incident DC85 HUF N/A N/A 20 1/23/1997 US Lebanon, MO AIDS LDVO Incident C402 LBO N/A N/A N/R 1/24/1997 US Washington, IN AIDS LDVO Incident C500 DCY N/A N/A 22 1/24/1997 US Chicago, IL AIDS LDVO Incident C550 Unknown N/A N/A N/R 2/2/1997 US Grand Forks, ND AIDS LDVO Incident DC91 GFK N/A N/A N/R 2/5/1997 US New York, NY AIDS LDVO Incident B741 JFK N/A N/A N/R 2/14/1997 US Ames, IA AIDS LDVO Incident SW4 AMW N/A N/A N/R 2/22/1997 US Alma, MI AIDS LDVO Incident C550 AMN N/A N/A N/R 3/4/1997 US Abilene, TX MITRE LDVO Incident SW4 ABI N/A N/A 5 3/5/1997 US Cleveland, OH NTSB LDVO Accident CLE N/A N/A 115 3/10/1997 US Boise, ID AIDS LDVO Incident WW24 BOI N/A N/A 230 3/20/1997 US Hailey, ID MITRE LDVO Accident SBR1 SUN N/A N/A N/R 3/27/1997 US San Carlos, CA MITRE LDVO Accident BE10 SQL N/A N/A N/R 4/18/1997 US Rangeley, ME AIDS LDVO Incident BE20 8B0 N/A N/A N/R 5/14/1997 US Arcata, CA AIDS LDVO Incident JS431 ACV N/A N/A N/R 5/19/1997 US New Orleans, LA AIDS LDVO Incident B721 MSY N/A N/A N/R 7/21/1997 US Elko, NV MITRE LDVO Accident DHC6 EKO N/A N/A N/R 7/31/1997 US Newark, NJ MITRE LDVO Accident MD11 EWR N/A N/A 505 8/13/1997 US Seattle, WA MITRE LDVO Accident B190 SEA N/A N/A 37 9/24/1997 US Lake Charles, LA AIDS LDVO Incident BE20 CWF N/A N/A N/R (continued on next page) B-29 B-30 (ft) Veer-off Veer-off Maximum (ft) Location Y (ft) Location X Code Airport Code ICAO Aircraft Aircraft Class Event Type Event Source City/State Amsterdam Netherland TSB LDVO Accident B752 EHAM N/A N/A 20 N/A N/A EHAM B752 Accident LDVO TSB Amsterdam Netherland Country Netherlands Date 9/24/1997 11/25/1997 US US 12/11/1997 US IL 12/24/1997 Chicago, Salt Lake City, UT Billings, MT NTSB AIDS NTSB LDVO Incident C560 LDVO PWK Incident N/A B732 LDVO Accident SLC N/A SH36 N/A BIL N/R N/A N/A N/A 75 765 12/27/1997 US CO 12/29/1997 US IL Denver, NY 1/8/1998 US Newburgh, 1/20/1998 Chicago, 2/22/1998 US AIDS AIDS AIDS US OK 2/26/1998 US AL LJ35 Lawton, PWK N/A Incident 2/26/1998 US LDVO AL Birmingham, MITRE LDVO LDVO Saranac Lake, NY MITRE 2/27/1998 England Leeds Incident N/A Incident SW3 MD80 Birmingham, NTSB 3/10/1998 US SWF F28 APA OH LDVO Accident SF34 N/R LDVO Incident N/A 3/18/1998 US IA BHM NTSB LAW N/A CO Cleveland, F28 N/A N/A LDVO Accident 3/31/1998 US AIDS Moines, BHM Denver, AIDS N/A 4/1/1998 N/A N/A N/A N/A AAIB Des 4/3/1998 AIDS MD80 US LDVO LDVO N/A Incident CLE 6/19/1998 B721 235 LDVO N/R 75 Incident N/A US N/R DSM OR SF34 LDVO Incident Accident 8/5/1998 US N/A US EGNM N/A LJ25 LDVO Incident N/R B190 APA 8/12/1998 US Bend, N/A Las Vegas, NV CA N/A N/A 8/17/1998 US N/A West Palm Beach, FL AK SLK Kneeland, AIDS AR Fishers Island, NY 9/4/1998 US 5 N/A AIDS Nome, MITRE N/R C421 N/R 9/11/1998 S21 AIDS Springdale, N/A AIDS Incident LDVO N/A 9/12/1998 AIDS N/R US AIDS C402 ASG PA31 LDVO N/A Incident Incident 9/13/1998 N/A LDVO O19 US LDVO 9/16/1998 Mexico N/A US N/A N/A Guadalajara C402 55 LDVO Incident LDVO Accident Houston, TX 9/28/1998 US OME CO N/A LDVO C402 N/A N/R Hot Springs, AR 10/1/1998 US Incident CO Pueblo, Las Vegas, NV Incident 11/1/1998 US NTSB C402 15 GA N/A PBI Denver, N/R C500 11/1/1998 US MITRE NTSB GA Atlanta, AIDS VGT B735 11/8/1998 US AIDS 10 LDVO TX Accident N/A MMGL Atlanta, N/A C551 0B8 LDVO 11/27/1998 US AIDS MITRE Accident PUB Amarillo, N/A N/A TX NTSB N/A CL60 LDVO B731 Incident AIDS LDVO N/A DEN LDVO Austin, Accident ATL LDVO N/A N/A N/A N/A B732 6 Accident LDVO Accident ATL Incident LDVO N/A B763 B731 LDVO Incident N/A N/A MITRE AMA N/R SW4 N/A N/A N/A Incident EFD N/R SW3 N/A N/R 235 HOT LDVO N/A N/R L29A Accident N/A AUS N/R VGT N/R N/A N/R N/A N/A N/A N/A N/A N/A 135 N/R N/R N/R 12/10/1998 US Charlotte Amalie, VI MITRE LDVO Accident BE18 STT N/A N/A N/R 12/10/1998 US Monroe, MI AIDS LDVO Incident SW3 TTF N/A N/A N/R 12/17/1998 US Traverse City, MI MITRE LDVO Accident AT43 TVC N/A N/A 85 12/17/1998 US Traverse City, MI NTSB LDVO Accident AT43 TVC N/A N/A N/R 12/17/1998 US Los Angeles, CA MITRE LDVO Accident LJ55 LAX N/A N/A N/R 12/20/1998 US Denver, CO AIDS LDVO Incident H25B APA N/A N/A N/R 12/26/1998 US Jackson, WY AIDS LDVO Incident B731 JAC N/A N/A N/R 12/27/1998 US Weiser, ID AIDS LDVO Incident BE20 S87 N/A N/A N/R 1/2/1999 US Springfield, MO AIDS LDVO Incident SGF N/A N/A N/R 1/3/1999 US Muskegon, MI AIDS LDVO Incident B190 MKG N/A N/A N/R 1/6/1999 US Plymouth, IN NTSB LDVO Accident AC50 C65 N/A N/A 20 1/8/1999 US Columbus, OH AIDS LDVO Incident MD80 CMH N/A N/A N/R 1/14/1999 US Youngstown, OH NTSB LDVO Accident C421 YNG N/A N/A N/R 1/14/1999 US Youngstown, OH MITRE LDVO Accident C421 YNG N/A N/A 5 1/22/1999 US Hyannis, MA MITRE LDVO Accident B190 HYA N/A N/A 10 1/22/1999 US Columbus, OH MITRE LDVO Accident C650 CMH N/A N/A 75 1/22/1999 US Oakland, CA AIDS LDVO Incident LJ25 OAK N/A N/A N/R 2/13/1999 US State College, PA AIDS LDVO Incident JS31 UNV N/A N/A N/R 2/17/1999 Bahamas Nassau NTSB LDVO Accident DC3 MYNN N/A N/A N/R 2/24/1999 Unknown Unknown AIDS LDVO Incident SW3 Unknown N/A N/A N/R 3/18/1999 US Lincoln, NE AIDS LDVO Incident LJ25 LNK N/A N/A N/R Papua New 4/23/1999 Freida River NTSB LDVO Accident DHC6 FAQ N/A N/A N/R Guinea 5/14/1999 US Hickory, NC MITRE LDVO Accident BE10 HKY N/A N/A 195 5/18/1999 US Georgetown, SC AIDS LDVO Incident BE20 GGE N/A N/A N/R 5/21/1999 US Midland, TX AIDS LDVO Incident F27 MAF N/A N/A N/R 5/21/1999 US South Bend, IN AIDS LDVO Incident F28 SBN N/A N/A N/R 8/16/1999 US Fort Lauderdale, FL MITRE LDVO Accident CL60 FXE N/A N/A 50 9/14/1999 Spain Girona Spain TSB LDVO Accident B752 LEGE N/A N/A 408 10/11/1999 US Miami, FL MITRE LDVO Accident SW4 OPF N/A N/A N/R 11/7/1999 Spain Barcelona Spain TSB LDVO Accident F100 LEBL N/A N/A 254 11/12/1999 US Fremont, OH AIDS LDVO Incident SW3 S24 N/A N/A 50 (continued on next page) B-31 B-32 (ft) Veer-off Veer-off Maximum (ft) Location Y (ft) Location X Code Airport Code ICAO Aircraft Aircraft Class Event Type Event Source City/State Country Date 11/18/1999 US KS 11/27/1999 US Guatemala Lawrence, ID 12/21/1999 Guatemala Boise, 1/28/2000 US NJ AIDS 1/28/2000 US AR Newark, 2/15/2000 BEA Fayetteville, MITRE MITRE 2/16/2000 AIDS LDVO US Incident SW4 2/25/2000 US US GA SW4 MI LDVO LWC Accident LDVO 3/6/2000 US FYV LDVO FA20 B731 Accident LDVO DC10 Atlanta, Incident N/A Accident FM N/A EWR Escanaba, MI 4/2/2000 US BOI Adrian, MGGT N/A N/A FL Palm Springs, CA 4/4/2000 US AIDS N/A Yap, AIDS N/A N/A 4/19/2000 US N/A Miami, MA PA31 N/A ADG N/A AIDS 5/2/2000 Incident NTSB LJ25 N/R AIDS N/A LDVO LDVO MITRE Incident Hyannis, N/R FTY 150 5/2/2000 France FA20 B721 Lyon OPF N/A YAP US N/A N/A IL Incident AIDS N/A Incident 58 LDVO LDVO 5/5/2000 US N/A N/R N/A N/R MA N/R 5/8/2000 US N/A N/A IA Cahokia, N/A BET LDVO LDVO LJ35 5/18/2000 LDVO AIDS AIDS Incident AIDS Nantucket, Saint Paul, MN N/R HYA N/R Rapids, B190 Accident 6/5/2000 US N/A Incident N/R Barbados CID C402 MD80 C402 BEA B190 CPS ACK AL N/A N/A Incident Incident Incident 6/7/2000 US N/A MD80 LDVO LDVO LDVO Cedar Bridgetown LJ35 AIDS N/A Accident 7/16/2000 US LYS Birmingham, N/A N/A AIDS ESC CO N/A N/A Accident AK PSP LDVO SW4 8/24/2000 US N/A EGBB WI Incident Denver, MITRE LDVO N/R N/R LDVO N/R N/A 1550 9/22/2000 N/A Milwaukee, N/A N/A 9/26/2000 US AIDS AIDS US NTSB 500 NC Bethel, US LDVO 9/29/2000 N/R Charlotte, 10/16/2000 US MO Incident US N/A B190 BE40 LDVO LDVO Incident MITRE Incident N/A MKE DEN Missoula, MT Louis, 10/22/2000 C402 N/A N/A LDVO Saint AIDS 10/29/2000 Ireland DC3 LDVO Accident CLT Cork STP Show Low, AZ Incident 11/5/2000 France N/A N/A 75 N/A Paris N/R NTSB 11/10/2000 US LDVO N/R N/A ND 11/19/2000 US N/R Incident MI MD80 N/A STL Dickinson, AIDS Rapids, 12/13/2000 US AIDS BGI Grand N/A FL 12/14/2000 US N/R AIDS LDVO AAIU Pensacola, N/A GA BEA N/A Accident Atlanta, N/A LDVO BE99 MITRE LDVO Incident DC91 LDVO LDVO Incident B741 B190 GRR LDVO Incident Incident Accident F50 N/R CDG AIDS N/R MSO DIK N/A N/A N/A LDVO C421 C421 Accident EICK N/A N/A PNS N/A N/A SOW N/A LDVO N/A Incident SW4 N/A N/R N/A 446 PDK N/A N/R N/A N/A N/A N/R 143 N/R N/A N/A N/R N/R N/R 12/17/2000 US Farmingdale, NY AIDS LDVO Accident BE10 FRG N/A N/A N/R 12/22/2000 US Holland, MI AIDS LDVO Incident FA10 HLM N/A N/A N/R 1/15/2001 US Two Harbors, MN AIDS LDVO Incident BE20 TWM N/A N/A N/R 1/21/2001 US New York, NY NTSB LDVO Incident A320 JFK N/A N/A 15 2/7/2001 Spain Balboa Spain TSB LDVO Accident A320 LEBB N/A N/A 20 2/13/2001 US Salina, KS AIDS LDVO Incident C650 SLN N/A N/A N/R 2/20/2001 US Manassas, VA AIDS LDVO Incident SF34 HEF N/A N/A N/R 3/3/2001 US Fort Lauderdale, FL MITRE LDVO Accident C402 FLL N/A N/A 30 3/9/2001 US Denver, CO AIDS LDVO Incident D328 DEN N/A N/A N/R 3/16/2001 US Cedar Rapids, IA AIDS LDVO Incident B721 CID N/A N/A N/R 3/18/2001 US Monument Valley, UT AIDS LDVO Incident DHC6 UT25 N/A N/A 88 3/24/2001 US Pittsburgh, PA AIDS LDVO Incident E145 PIT N/A N/A N/R 4/19/2001 US Denver, CO AIDS LDVO Incident H25B APA N/A N/A N/R 4/26/2001 US Saint George, UT AIDS LDVO Incident LJ25 SGU N/A N/A N/R 6/4/2001 US Las Vegas, NV MITRE LDVO Accident PA31 VGT N/A N/A N/R 6/10/2001 US Miami, FL AIDS LDVO Incident BE18 OPF N/A N/A N/R 6/12/2001 US Kotzebue, AK AIDS LDVO Incident B731 OTZ N/A N/A N/R 7/10/2001 England Exeter AAIB LDVO Incident AN12 EGTE N/A N/A N/R 8/25/2001 US Kansas City, MO MITRE LDVO Accident B731 MCI N/A N/A 30 10/24/2001 Canada Peace River, AB Canada TSB LDVO Incident DH8A CYPE N/A N/A 176 11/29/2001 US Flagstaff, AZ NTSB LDVO Accident BE99 FLG N/A N/A N/R 1/5/2002 US Sacramento, CA AIDS LDVO Incident B731 SMF N/A N/A N/R 1/10/2002 US Fort Collins/Loveland, CO AIDS LDVO Incident LJ35 FNL N/A N/A N/R 2/3/2002 Ireland Dublin AAIU LDVO Incident MD11 EIDW N/A N/A 12 3/4/2002 US Chicago, IL AIDS LDVO Incident BE20 DPA N/A N/A N/R 3/12/2002 US Albuquerque, NM MITRE LDVO Accident C402 ABQ N/A N/A N/R 3/13/2002 US Salt Lake City, UT AIDS LDVO Incident LJ25 SLC N/A N/A 15 3/17/2002 US Laramie, WY AIDS LDVO Incident BE20 LAR N/A N/A N/R 3/27/2002 Canada Toronto, ON Canada TSB LDVO Incident F28 CYYZ N/A N/A 15 3/28/2002 US Jackson, WY AIDS LDVO Incident GLF4 JAC N/A N/A N/R 4/16/2002 Canada Winnipeg, MB Canada TSB LDVO Accident SW3 CYWG N/A N/A 0 5/10/2002 US Meridian, MS AIDS LDVO Incident SW2 MEI N/A N/A 100 (continued on next page) B-33 B-34 (ft) Veer-off Veer-off Maximum (ft) Location Y (ft) Location X Code Airport Code ICAO Aircraft Aircraft Class Event Type Event Source City/State Country Date 6/15/2002 US Fort Lauderdale, FL AIDS 6/15/2002 US Lauderdale, 6/19/2002 US OR Fort SW3 7/25/2002 US LDVO Incident SC Prineville, FXE 8/28/2002 US N/A AZ AIDS Columbia, 9/7/2002 Spain AIDS Madrid Phoenix, 9/15/2002 N/A FL BE30 AIDS LDVO NTSB Incident 9/21/2002 US S39 US Lauderdale, N/A A346 TSB LEMD D328 LDVO N/R Incident 11/22/2002 US N/A Incident FL CAE LDVO NS Fort IL A320 B731 N/A N/A N/A GA7 Lauderdale, 1/6/2003 US AIDS LDVO LDVO CYHZ Incident Accident Spain PHX Incident TSB LDVO FLL N/A Fort N/A Rock Springs, WY 2/2/2003 Canada Enfield, Chicago, N/A 33 N/A N/A Canada 2/7/2003 AIDS N/A N/R LDVO NTSB 0 2/15/2003 US SW4 Accident N/A GA C525 N/R N/A US MDW Incident 2/16/2003 US FLL LDVO IL N/R Marietta, N/A N/R 2/20/2003 US N/A SD Cahokia, AIDS 2/28/2003 US LDVO Mountain Village, AK CA N/R Pierre, NV 3/2/2003 US MITRE N/A Accident AIDS Oakland, NC SBR1 3/8/2003 US LDVO B190 Incident Reno, RYY AIDS SW3 AIDS N/A LDVO 3/25/2003 US Accident Kinston, CPS OH N/R AIDS MITRE RKS 4/16/2003 US N/A FL AZ F27 Columbus, N/A AIDS H25B SBR1 LDVO RNO Incident LDVO BE99 4/17/2003 US ISO LDVO N/A PIR Accident Incident AIDS Lauderdale, Incident LDVO OAK Yuma, N/A LDVO N/A N/A 5/24/2003 US N/A N/A Incident TX N/R Fort N/A SBR1 5/28/2003 US N/A LDVO FL Incident C402 MI FXE AIDS AIDS BE20 Amarillo, LDVO N/R CA Incident N/A N/A OSU 7/3/2003 US N/A N/R 75 Detroit, SBR1 N/A MITRE Lauderdale, FXE N/A 8/9/2003 US MOU N/A Incident Carlsbad, LDVO N/R N/R AIDS VA C421 LDVO N/A Incident 9/3/2003 US B731 Fort NYL AIDS N/A N/A LDVO Accident N/A AMA N/A F900 9/13/2003 US N/A Richmond, CRQ AIDS MT Incident N/A N/R LDVO N/R N/R 9/22/2003 US ON N/R MS SW4 MU2 Butte, N/A LDVO Incident RIC N/A N/A 9/26/2003 Canada Incident DET LDVO N/A Toronto, TSB Gulfport, N/A N/A ASTR LDVO 10/20/2003 Incident CYYZ N/A N/R N/R AIDS Canada N/R AIDS N/A US 12/4/2003 N/A 12/15/2003 US N/A US N/R N/R DH8A LDVO B731 Incident BTM ME 12/18/2003 US LDVO Incident N/R GPT N/A Key West, FL Bangor, 350 TN N/A Memphis, Little Rock, AR N/A N/A AIDS MITRE AIDS N/R N/R AIDS LDVO LDVO MD11 Incident Accident D228 MEM BGR N/A LDVO N/A LDVO Incident N/A Incident PA31 N/A C560 EYW N/R N/R LIT N/A N/A N/A N/A N/R N/R 1/14/2004 US Saint Louis, MO AIDS LDVO Incident FA10 SUS N/A N/A N/R 1/15/2004 Canada Dryden, ON Canada TSB LDVO Incident SW4 CYHD N/A N/A 30 1/17/2004 US Rapid City, SD NTSB LDVO Incident CL60 RAP N/A N/A N/R 1/21/2004 US Pueblo, CO MITRE LDVO Accident FA20 PUB N/A N/A 150 1/24/2004 Singapore Singapore Singapore AAI LDVO Incident B772 WSSS N/A N/A 20 1/29/2004 US Huntsville, AL AIDS LDVO Incident CVLP HSV N/A N/A N/R 2/6/2004 US Richmond, VA AIDS LDVO Incident C560 FCI N/A N/A 20 2/6/2004 US Kansas City, MO AIDS LDVO Incident C550 MKC N/A N/A N/R 2/15/2004 US Chicago, IL AIDS LDVO Incident LJ35 DPA N/A N/A N/R 2/25/2004 Canada Edmonton, AB Canada TSB LDVO Incident B731 CYEG N/A N/A 185 3/3/2004 US Saint Paul Island, AK AIDS LDVO Incident SW4 SNP N/A N/A N/R 3/4/2004 US Springdale, AR MITRE LDVO Accident BE20 ASG N/A N/A N/R 3/4/2004 US Broomfield, CO AIDS LDVO Incident F900 BJC N/A N/A N/R 3/15/2004 US Manhattan, KS NTSB LDVO Accident B190 MHK N/A N/A 5 3/19/2004 US Utica, NY MITRE LDVO Accident LJ35 UCA N/A N/A 20 3/31/2004 US Fort Lauderdale, FL NTSB LDVO Accident C402 FXE N/A N/A N/R 5/9/2004 US San Juan, PR NTSB LDVO Accident AT72 SJU N/A N/A 112 5/11/2004 US Roseau, MN AIDS LDVO Incident BE9L ROX N/A N/A N/R 5/15/2004 US Oakland, CA AIDS LDVO Incident AC52 OAK N/A N/A N/R 6/11/2004 US Dallas, TX NTSB LDVO Incident E135 DFW N/A N/A N/R 6/14/2004 US Pittsburgh, PA AIDS LDVO Incident B731 PIT N/A N/A N/R 6/16/2004 US Indianapolis, IN AIDS LDVO Incident C550 TYQ N/A N/A N/R 8/10/2004 US Grand Canyon, AZ AIDS LDVO Incident DHC6 GCN N/A N/A N/R 8/31/2004 Canada Moncton, NB Canada TSB LDVO Incident B721 CCG4 N/A N/A 200 9/3/2004 US Houston, TX AIDS LDVO Incident GLF2 HOU N/A N/A N/R 9/21/2004 Canada La Ronge, SK Canada TSB LDVO Accident SW4 CYVC N/A N/A 275 9/21/2004 US Garden City, KS AIDS LDVO Incident B190 GCK N/A N/A N/R 10/29/2004 US Dubuque, IA AIDS LDVO Incident E145 DBQ N/A N/A N/R 11/5/2004 US Houston, TX AIDS LDVO Incident WW24 HOU N/A N/A N/R 11/21/2004 US Denver, CO AIDS LDVO Incident MD80 DEN N/A N/A N/R 11/29/2004 US Eagle, CO MITRE LDVO Accident GLF4 EGE N/A N/A N/R 12/1/2004 Canada Saint-Georges, QC Canada TSB LDVO Accident BE30 CYSG N/A N/A 95 (continued on next page) B-35 B-36 (ft) Veer-off Veer-off Maximum (ft) Location Y (ft) Location X Code Airport Code ICAO Aircraft Aircraft Class Event Type Event Source City/State Rotterdam Netherland TSB LDVO Incident SW4 EHRD N/A N/A 38 N/A N/A EHRD SW4 Incident LDVO TSB Rotterdam Netherland Country Netherlands Date 12/4/2004 12/8/2004 US 12/9/2004 US US GA 12/13/2004 US Atlanta, Mc Allen, TX OH 12/14/2004 US QC Cleveland, Twin Falls, ID OH 12/19/2004 Canada AIDS Gaspé, Cleveland, 12/20/2004 AIDS QC US 12/24/2004 Canada B721 AIDS MITRE TSB LDVO Incident OH Kuujjuaq, ATL 1/4/2005 US LDVO AIDS Canada N/A PA31 TSB Accident OK LDVO 1/6/2005 US AB Cleveland, MITRE CYGP LDVO Canada Incident LJ35 Cedar Rapids, IA BE10 AC90 Accident CGF N/A LDVO 1/20/2005 Canada N/A Stillwater, N/A LDVO Calgary, AIDS Incident CYVP BKL MU30 TSB Accident LDVO DC91 1/25/2005 US LDVO N/A MO CGF Incident CO CYYC N/A N/A N/A LJ35 Accident LDVO Canada N/A SWO 1/28/2005 US N/R N/A MITRE N/A Incident City, LDVO CVLT AIDS Montrose, 1/31/2005 US Incident N/R N/A N/A WA AIDS Kansas N/A N/A OH MFE 2/7/2005 US SW3 60 QC N/A Everett, MD80 LDVO Incident MCI 2/21/2005 Canada N/R 40 LDVO Columbus, AIDS 40 TSB Bromont, H25A N/A N/A SW4 N/R LDVO LDVO CZBM TWF AIDS Accident Incident N/A 3/11/2005 US WI MTJ N/R CMH Accident MD80 Canada N/A 3/23/2005 Incident N/A LJ25 LDVO N/A Milwaukee, N/A N/A N/A 3/26/2005 MITRE BE18 US LDVO Incident PAE N/A N/A 4/26/2005 US CID US N/R GA N/A 5 250 CL60 LDVO 5/28/2005 US Accident MKE MITRE CO Lawrenceville, N/A N/A N/R Brigham City, UT 5/31/2005 N/A N/A Denver, DC SW3 475 El Paso, TX LDVO 6/8/2005 US Accident US N/A LZU MITRE N/R N/A 6/15/2005 AIDS Washington, AIDS SF34 N/R TX IAD 7/1/2005 US Incident N/A 571 US N/A LDVO CO ME N/A Teterboro, NJ 7/8/2005 US FL Amarillo, MD80 US AIDS LDVO Incident DEN MITRE N/A AIDS 7/15/2005 LJ25 N/A Islesboro, Eagle, LJ35 EGE N/A AMA AIDS N/A N/R C402 Lauderdale, LDVO FLL MITRE Accident Charlotte Amalie, VI 8/9/2005 US 754 LDVO 785 Incident N/A LDVO N/A Accident C404 N/A 57B N/A LDVO 8/10/2005 US MITRE Incident Fort Incident SD AIDS N/A LDVO 331 N/A 9/11/2005 LJ24 LDVO 150 Spearfish, N/R N/A 9/12/2005 N/R US AIDS Incident BMC LDVO N/R C680 LDVO Accident N/A BE20 LDVO Las Vegas, NV Incident SW3 SPF Incident ELP N/A C402 TEB N/A N/A N/A AIDS STT N/A N/R N/A N/A N/R LDVO N/A Incident N/A N/R DHC6 30 VGT N/R N/A N/A N/R 9/23/2005 US TX Dallas, AIDS C402 LDVO Incident ADS N/A N/A N/R 10/6/2005 US Hayden, CO AIDS LDVO Incident C500 HDN N/A N/A 5 11/17/2005 US Jamestown, NY AIDS LDVO Incident H25A JHW N/A N/A N/R 12/1/2005 US Sioux Falls, SD AIDS LDVO Incident SW4 FSD N/A N/A N/R 12/3/2005 US Ann Arbor, MI AIDS LDVO Incident D328 ARB N/A N/A 50 12/13/2005 US Kotzebue, AK AIDS LDVO Incident DC6 OTZ N/A N/A N/R 12/26/2005 Canada Winnipeg, MB Canada TSB LDVO Incident A319 CYWG N/A N/A 15 12/27/2005 US Marquette, MI AIDS LDVO Incident B190 SAW N/A N/A N/R 2/1/2006 US Yakutat, AK AIDS LDVO Incident B731 YAK N/A N/A N/R 2/12/2006 US New York, NY AIDS LDVO Incident A345 JFK N/A N/A 100 2/25/2006 England London AAIB LDVO Incident A344 EGLL N/A N/A 0 2/25/2006 US Trenton, NJ AIDS LDVO Incident F900 TTN N/A N/A N/R 3/10/2006 US Dallas, TX AIDS LDVO Incident L29B DAL N/A N/A N/R 3/13/2006 US Houston, TX AIDS LDVO Incident B731 IAH N/A N/A N/R 3/20/2006 US Minneapolis, MN AIDS LDVO Incident A30B MSP N/A N/A N/R 4/27/2006 Australia Mabuiag Island ATSB LDVO Incident C206 YMAA N/A N/A 170 5/2/2006 US Chicago, IL AIDS LDVO Incident E145 ORD N/A N/A N/R 5/18/2006 US Fairbanks, AK AIDS LDVO Incident MD80 AFA N/A N/A N/R 6/12/2006 US Kaunakakai, HI AIDS LDVO Incident BE99 MKK N/A N/A N/R 7/28/2006 US Memphis, TN NTSB LDVO Accident MD11 MEM N/A N/A N/R 8/6/2006 US Salina, KS AIDS LDVO Incident H25A SLN N/A N/A 150 8/13/2006 England Middlesex AAIB LDVO Accident BE58 EGLD N/A N/A 164 9/16/2006 US Modesto, CA AIDS LDVO Incident LJ35 MOD N/A N/A N/R 9/20/2006 England Bedfordshire AAIB LDVO Incident C750 EGGW N/A N/A 12 10/27/2006 US Louisville, KY AIDS LDVO Incident E135 SDF N/A N/A N/R 10/30/2006 France Rouen BEA LDVO Incident AT43 LFOP N/A N/A 144 11/11/2006 US Indianapolis, IN AIDS LDVO Incident B721 IND N/A N/A N/R 12/14/2006 US Sarasota, FL AIDS LDVO Incident WW24 SRQ N/A N/A N/R 1/8/2007 US Denver, CO AIDS LDVO Accident BE30 APA N/A N/A N/R 1/12/2007 US Denver, CO AIDS LDVO Incident SW4 DEN N/A N/A N/R 1/13/2007 US Laramie, WY AIDS LDVO Incident SW3 LAR N/A N/A N/R 1/17/2007 England Southampton AAIB LDVO Incident CRJ1 EGHI N/A N/A 52 2/4/2007 US Miami, FL NTSB LDVO Incident DC87 MIA N/A N/A N/R (continued on next page) B-37 B-38 (ft) Veer-off Veer-off Maximum (ft) Location Y (ft) Location X Code Airport Code ICAO Aircraft Aircraft Class Event Type Event Source City/State Country Date 2/14/2007 2/17/2007 US US IN 2/20/2007 Indianapolis, AIDS 2/24/2007 US AR Teterboro, NJ 3/4/2007 US US TN AIDS BE20 4/4/2007 US Fayetteville, LDVO Accident EYE Cordova, AK 4/13/2007 BE20 N/A DE Knoxville, FYV AIDS N/A Incident LDVO Dallas, TX 4/16/2007 US AIDS LA US Castle, C560 AIDS RKW N/A N/A N/A 4/23/2007 US Incident Rouge, AIDS LDVO New 7/30/2007 US NTSB WI N/A N/R Baton IA 22 Teterboro, NJ 8/7/2007 US C680 LDVO Incident Madison, ILG AC68 LDVO LDVO Incident N/R 8/23/2007 BTR NTSB Ankeny, N/A N/A AIDS Incident 9/30/2007 US AIDS US TX LDVO WW24 10/9/2007 AIDS N/A C650 N/A Houston, IKV Accident Incident E145 11/17/2007 N/A LDVO LDVO TEB US Incident LDVO MSN C402 AIDS US Westhampton, NY 11/25/2007 US N/R N/A N/R N/A Incident MN 1/15/2008 France N/A CKU E145 Paris LDVO NTSB Minneapolis, N/A Chicago, IL N/R 1/15/2008 US WW24 SGR LDVO Incident WI AIDS Vineyard Haven, MA N/A Incident 1/17/2008 US N/A DAL MN Kenosha, N/R D328 AIDS 1/19/2008 US N/A AK Bigfork, N/A AIDS 1/30/2008 N/A LDVO LDVO Dillingham, TEB NJ Incident GA7 AIDS NTSB AIDS 2/1/2008 US N/A BEA US 20 Accident WY FCM 2/3/2008 US SH33 20 AIDS UT LDVO MO Morristown, Incident LJ60 ENW N/A LDVO N/A N/A 2/13/2008 US BE30 N/A LDVO B731 Jackson, Incident AIDS LDVO C560 City, Incident N/A FOZ MMU A30B Louis, AIDS DLG LDVO Incident Incident Incident West Palm Beach, FL AIDS 3/1/2008 US CDG LDVO FOK N/R N/A LDVO N/A C560 Cedar N/A WI N/A SUS N/A GALX N/A CL60 3/8/2008 US Incident JAC N/A Saint AIDS LDVO N/A Incident N/A Incident LDVO N/A N/A 4/9/2008 115 AIDS N/A MVY E120 Milwaukee, A320 LDVO N/A Incident N/R N/R N/A CDC N/R NTSB N/A 4/12/2008 US NY DC91 N/A MKE US N/A N/A N/R Incident N/R ORD 4/24/2008 6 LDVO FL 39 N/R 75 Potsdam, AIDS LDVO E110 N/A N/A 5/23/2008 US FL N/A LDVO US Accident Lauderdale, PTD AIDS N/A 5/24/2008 US Incident N/A Oklahoma City, OK Lauderdale, 10 Fort N/A SBR1 N/R 6/13/2008 US LDVO GLF5 Incident GA FXE Fort N/A C402 Sterling, CO N/R N/A LDVO AIDS Incident FLL Atlanta, PBI N/A N/A N/R N/R N/A AIDS N/A N/A NTSB LDVO N/R N/R C560 LDVO Incident PDK N/R Incident N/A N/A STAR LDVO N/A HSD Accident N/R C421 N/R N/A STK N/A N/A 10 N/A N/R 7/3/2008 US Destin, FL AIDS LDVO Incident C525 DTS N/A N/A N/R 7/15/2008 US Portland, OR AIDS LDVO Incident C402 TTD N/A N/A N/R 9/7/2008 US San Antonio, TX AIDS LDVO Incident CL60 SAT N/A N/A N/R 9/19/2008 US Van Nuys, CA AIDS LDVO Incident EGRT VNY N/A N/A N/R 9/22/2008 US Chicago, IL NTSB LDVO Incident B752 ORD N/A N/A 35 10/3/2008 US Lewiston, ID AIDS LDVO Incident SW4 LWS N/A N/A N/R 11/27/2008 US Ironwood, MI AIDS LDVO Incident B190 IWD N/A N/A N/R 1/12/2009 US Chicago, IL AIDS LDVO Incident LJ55 ARR N/A N/A 20 1/13/2009 US Kodiak, AK AIDS LDVO Incident B731 ADQ N/A N/A N/R 4/27/2009 US Nantucket, MA AIDS LDVO Incident C402 ACK N/A N/A N/R 1/27/1978 US Nashville, TN AIDS TOOR Incident B721 BNA 150 0 N/A 2/13/1980 US Chicago, IL AIDS TOOR Incident C500 Unknown N/R N/R N/A 2/19/1981 US Pittsburg, PA AIDS TOOR Incident DC91 PTS N/R N/R N/A 3/4/1981 US Hagerstown, MD AIDS TOOR Incident C500 HGR N/R N/R N/A 2/3/1982 US Philadelphia, PA NTSB TOOR Accident DC10 PHL 600 0 N/A 4/16/1982 US Tucson, AZ AIDS TOOR Incident DC85 TUS N/R N/R N/A 6/4/1982 US Wichita, KS NTSB TOOR Accident BE65 AAO 300 50 N/A 7/5/1982 US Boise, ID MITRE TOOR Incident DC91 BOI 50 0 N/A 7/9/1982 US New Orleans, LA NTSB TOOR Accident B721 MSY 2376 564 N/A 9/13/1982 US Denver, CO NTSB TOOR Incident SW3 DEN 10 0 N/A 10/3/1982 US New Orleans, LA MITRE TOOR Incident B721 MSY 443 0 N/A 1/11/1983 US Detroit, MI NTSB TOOR Accident DC85 DTW 299 1200 N/A 7/2/1983 US King Salmon, AK AIDS TOOR Incident DC7 AKN N/R N/R N/A 11/23/1983 US Perris, CA AIDS TOOR Incident DHC6 L65 N/R N/R N/A 12/3/1983 US Olney, TX AIDS TOOR Incident FA10 SPS N/R N/R N/A 12/23/1983 US Anchorage, AK NTSB TOOR Accident DC10 ANC 1434 40 N/A 5/31/1984 US Denver, CO NTSB TOOR Accident B721 DEN 1074 0 N/A 7/28/1984 US Waterville, ME NTSB TOOR Accident LJ25 WVL 100 10 N/A 1/17/1985 US Flushing, NY MITRE TOOR Incident B721 LGA N/R N/R N/A 1/21/1985 US Johnstown, PA NTSB TOOR Accident LJ25 JST N/R N/R N/A 4/3/1985 US Grand Rapids, MI NTSB TOOR Accident DHC6 GRR N/R N/R N/A (continued on next page) B-39 B-40 (ft) Veer-off Veer-off Maximum (ft) Location Y (ft) Location X Code Airport Code ICAO Aircraft Aircraft Class Event Type Event Source City/State San Juan NTSB TOOR Accident DC10 SJU 63 161 N/A Country Puerto Rico Date 6/27/1985 6/27/1985 US San Juan, PR 6/27/1985 US Juan, 8/13/1985 US NL WI San NTSB 7/20/1986 Canada Wabush, Madison, TSB VT B731 8/6/1986 US TOOR Accident YWK DC10 200 Canada TOOR NTSB SJU Accident 5/12/1987 US LA Rutland, PA 140 NTSB 5/26/1987 US Orleans, NTSB Pittsburgh, 0 LJ23 LJ55 TOOR 7/16/1987 US Accident RUT MSN MS NTSB N/R New Accident 0 CO TOOR 900 8/3/1987 US JS31 Jackson, TOOR Accident N/R MSY 9/21/1987 Denver, N/A LJ35 1180 TOOR Accident 0 NTSB AGC 9/24/1987 NTSB US N/A N/A 1320 10/5/1987 US 20 A30B US DEN CA N/R Incident JCOM TOOR 11/15/1987 JAN 300 TOOR Accident N/A Oakland, N/R US Tyndall AFB, FL N/R 12/19/1987 US N/A AIDS Twin Falls, ID AK 5/21/1988 N/A N/A N/R Bethel, 6/27/1988 UK US NTSB Denver, CO 8/16/1988 US LJ25 TOOR Incident OH N/A Newcastle OAK 8/19/1988 US NTSB 50 MITRE OH Cleveland, Dallas, TX 8/31/1988 NTSB AAIB Cleveland, TOOR 9/11/1988 US NTSB ASRS TOOR BA11 0 TOOR UK Incident C208 NCL Accident 11/15/1988 US SW3 US Incident TOOR 161 TOOR Accident BET CLE MN 8/19/1989 LA LJ35 TOOR 837 Incident N/R NTSB Minneapolis, Dallas, TX Accident 8/25/1989 US CLE N/A US Orleans, MITRE 0 NTSB TOOR SW4 500 New Orleans, LA 9/13/1989 US PAM IN 387 New N/R Accident 9/20/1989 US B721 TOOR NY Incident Warsaw, TWF FL MSY 300 DC91 230 New Orleans, LA 1/6/1990 US N/A TOOR 600 TOOR AIDS N/A Flushing, Incident DC91 NTSB 1/30/1990 US N/A AIDS Miami, Stapleton 245 NY MSP Accident N/A NTSB 1300 3/13/1990 0 NY MI DC10 330 ASRS NTSB Rochester, -50 3/12/1991 US US L29A MITRE York, WW24 US MIA TOOR ASW Incident B731 1180 TOOR 1000 TOOR DFW Accident NTSB 7/22/1991 Accident LGA Detroit, TOOR TOOR 1144 LJ23 DET 828 New NTSB 0 194 N/A 325 100 7/31/1991 US DC91 TOOR Incident Incident CO ROC 0 Accident Accident 1112 0 TOOR DC85 Teterboro, NJ 250 TOOR TOOR N/A L29A JFK B721 Accident Denver, N/A 0 835 Incident N/A N/A N/A N/A MSY 0 AIDS DFW N/A 0 MITRE 550 N/A 400 2833 B721 TOOR Incident N/A DEN N/A MSY 150 TOOR N/A 0 0 800 0 Incident LJ35 N/A 0 TEB N/A N/A 250 N/A 0 N/A 10/11/1991 US Dallas, TX MITRE TOOR Incident JS31 DFW N/R N/R N/A 1/31/1992 US Bellingham, WA MITRE TOOR Incident B461 BLI N/R N/R N/A 4/15/1992 US Charlotte, NC NTSB TOOR Incident F28 CLT 100 0 N/A 4/19/1992 US Charlotte, NC ASRS TOOR Incident CLT 200 -130 N/A 7/30/1992 US New York, NY NTSB TOOR Accident L101 JFK N/R N/R N/A 8/19/1992 US Washington, DC MITRE TOOR Incident SW4 DCA 170 0 N/A 12/18/1992 US Mccall, ID NTSB TOOR Accident FA10 MYL 500 50 N/A 4/19/1993 US Merced, CA NTSB TOOR Accident JS31 MCE 200 250 N/A 9/19/1993 France Troyes France BEA TOOR Incident SW4 QYR 885 98 N/A 9/29/1993 France Besançon France BEA TOOR Accident FA10 QBQ 99 49 N/A 11/2/1993 US Houston, TX AIDS TOOR Incident CL60 HOU 200 0 N/A 3/2/1994 US Flushing, NY NTSB TOOR Accident LGA 500 0 N/A 4/6/1994 US Jackson, WY AIDS TOOR Incident C421 JAC N/R N/R N/A 5/19/1994 US Texarkana, TX ASRS TOOR Incident SF34 TXK 80 0 N/A 7/13/1994 US Atlantic City, NJ NTSB TOOR Accident LJ35 ACY 446 0 N/A 8/26/1994 US New Orleans, LA NTSB TOOR Accident FA20 NEW 500 0 N/A 5/23/1995 US Rogers, AR NTSB TOOR Accident LJ35 ROG 1200 0 N/A 6/25/1995 US Atlanta, GA MITRE TOOR Incident LJ35 ATL N/R N/R N/A 9/18/1995 US Ames, IA AIDS TOOR Incident C402 AMW N/R N/R N/A 9/21/1995 US Houston, TX AIDS TOOR Incident LJ25 HOU 225 0 N/A 10/19/1995 Canada Vancouver, BC TSB TOOR Incident DC10 YVR 400 141 N/A 5/1/1996 US Albuquerque, NM NTSB TOOR Accident SBR1 ABQ 212 212 N/A 7/8/1996 US Nashville, TN NTSB TOOR Accident B731 BNA 750 -100 N/A 8/1/1996 UK Cambridge UK AAIB TOOR Incident EGSC N/R N/R N/A 8/14/1996 US Pottstown, PA NTSB TOOR Accident PA31 N47 1429 457 N/A 8/16/1996 England Liverpool AAIB TOOR Incident A748 LPL 718 200 N/A 1/10/1997 US Bangor, ME NTSB TOOR Accident B190 BGR N/R N/R N/A 1/19/1997 Italy Rome ASRS TOOR Incident DC10 FCO N/R N/R N/A 6/13/1997 US San Antonio, TX AIDS TOOR Incident C421 SAT N/R N/R N/A 8/7/1997 US Miami, FL NTSB TOOR Accident DC85 MIA 575 0 N/A 11/29/1997 Canada Island Lake, MB Canada TSB TOOR Accident B190 YIV 200 0 N/A

(continued on next page) B-41 B-42 (ft) Veer-off Veer-off Maximum (ft) Location Y (ft) Location X Code Airport Code ICAO Aircraft Aircraft Class Event Type Event Source City/State Eelde Netherland TSB TOOR Accident MD88 EHGG 100 0 N/A 0 100 EHGG MD88 Accident TOOR TSB Eelde Netherland Country Netherlands Date 2/20/1998 England Norwich 3/19/1998 US OR 3/30/1998 UK Portland, AAIB 5/12/1998 US MI Stansted JPRO TOOR NTSB UK Incident 6/23/1998 US NWI DC Monroe, N/R 6/23/1998 US DC Washington, S601 AIDS AAIB TOOR 7/19/1998 US NTSB Accident PDX NC N/R Washington, AIDS N/R A748 8/28/1998 TOOR UK NU Incident STN Raleigh, FA20 12/3/1998 Canada LJ60 TOOR US 386 TOOR Incident Accident Iqaluit, N/A TTF IAD N/R TSB ASRS 11/11/1999 US LJ60 A748 TOOR AB N/R Incident TOOR 250 Accident YFB IAD TSB IL 5/11/2000 Canada Canada 0 800 DC91 Edmonton, TOOR N/R Incident N/A YEG Chicago, El Paso, TX N/R 8/17/2000 US Canada B721 TOOR IL Incident 500 0 RDU 10/15/2000 US -100 200 N/R Ottawa, N/A N/A AK 10/19/2000 US NTSB 0 NY Anchorage, N/A CA 1/4/2001 US N/A 0 N/A AIDS NTSB MITRE Concord, 2/1/2001 NTSB Schenectady, LJ35 TOOR SCH N/A BE20 3/17/2001 US Accident 470 Accident MI TOOR US SC7 NTSB TOOR N/A CGX Incident 3/22/2001 France Detroit, 8N2 Orleans TOOR 300 0 TOOR 8/16/2001 Incident B741 N/R 8/24/2001 US ANC US Accident NTSB TOOR San Luis Obispo, CA NY BE30 Accident 100 690 FA20 11/18/2001 US N/A N/R BEA CCR Ithaca, PA31 MD MITRE TOOR Accident WI 4/1/2002 US LFOZ OK A320 590 496 TOOR France Accident DTW ELP NTSB Delavan, ASRS Traverse City, MI N/A 5/20/2002 US 530 Cambridge, 0 N/A City, NTSB 10/3/2002 US BE40 FL CGE -66 WA 75 Oklahoma C550 Incident 0 2010 AIDS TOOR TOOR AIDS TOOR 6/12/2003 US 73 Accident PWA LJ25 MITRE Lauderdale, Everett, TOOR 700 Accident ITH 7/17/2003 Incident N/A N/A 0 Fort 1000 AIDS LJ24 TOOR WW24 Incident N/A 0 TOOR 0 N/A FXE Incident DHC6 TOOR 1000 SBP 10 N/A C59 C500 TOOR Incident Incident PAE 0 N/R N/A 35 N/R LJ25 N/A N/A N/R N/R TVC N/A 0 N/A N/A 630 0 N/A N/A 7/22/2003 US PA MN 8/7/2003 US Pittston, 8/17/2003 US Duluth, CT 11/11/2003 US MITRE MITRE DLH Groton, WW24 6 IL 12/16/2003 Incident TOOR HUNT AVP Chicago, US TOOR 10/14/2004 Accident AIDS 740 Canada 0 NTSB 0 Halifax, NS LJ25 TOOR Teterboro, NJ Incident GON N/A 125 TOOR N/A C560 Accident 0 NTSB PWK Canada TSB 500 TOOR N/A 0 TOOR Accident B741 Incident CL60 N/A YHZ TEB 1750 188 40 0 N/A N/A 12/20/2004 US El Paso, TX ASRS TOOR Incident LJ25 ELP 200 0 N/A 2/2/2005 US Teterboro, NJ MITRE TOOR Accident CL60 TEB 545 0 N/A 3/9/2005 US Tupelo, MS NTSB TOOR Accident CL60 TUP 120 30 N/A 5/9/2005 US Brownwood, TX NTSB TOOR Accident SBR1 BWD 1300 0 N/A 7/25/2005 Australia Nhill ATSB TOOR Incident PA31 YNHL 162 0 N/A 8/1/2006 US Angola, IN AIDS TOOR Incident C560 ANQ 75 0 N/A 8/27/2006 US Lexington, KY NTSB TOOR Accident CRJ1 LEX 975 0 N/A 1/25/2007 France Pau ASN TOOR Accident F100 PUF 1598 100 N/A 4/30/1970 Italy Rome ATSB TOVO Incident B701 LIRF N/A N/A 370 3/1/1978 US Lawrence, KS AIDS TOVO Incident AC80 LWC N/A N/A N/R 2/21/1979 US Detroit, MI AIDS TOVO Incident DC85 DET N/A N/A N/R 11/18/1980 US Rochester, NY AIDS TOVO Incident FA10 ROC N/A N/A N/R 6/23/1981 US Philadelphia, PA AIDS TOVO Incident H25A PHL N/A N/A 500 12/9/1981 US San Diego, CA AIDS TOVO Incident C500 Unknown N/A N/A N/R 12/16/1981 US Des Moines, IA AIDS TOVO Incident WW24 DSM N/A N/A N/R 2/3/1982 US Detroit, MI AIDS TOVO Incident SW3 Unknown N/A N/A N/R 3/30/1982 US Chicago, IL NTSB TOVO Incident SW4 ORD N/A N/A 70 7/14/1982 US Santa Fe, NM AIDS TOVO Incident SW4 SAF N/A N/A N/R 7/11/1983 US Morristown, NJ AIDS TOVO Incident SBR1 MMU N/A N/A N/R 1/11/1984 US Old Town, ME AIDS TOVO Incident BE20 OLD N/A N/A N/R 1/12/1984 US Plymouth, MA AIDS TOVO Incident SW3 PYM N/A N/A N/R 1/23/1984 US Chicago, IL NTSB TOVO Incident DC86 ORD N/A N/A N/R 10/25/1984 US Houston, TX AIDS TOVO Incident LJ35 SGR N/A N/A N/R 12/19/1984 US Detroit, MI NTSB TOVO Accident BE18 YIP N/A N/A N/R 2/5/1986 US Philadelphia, PA AIDS TOVO Incident CL60 PHL N/A N/A N/R 2/7/1986 US Brigham City, UT AIDS TOVO Incident WW24 BMC N/A N/A N/R 3/22/1986 US Melbourne, FL AIDS TOVO Incident GLF2 MLB N/A N/A N/R 11/29/1986 Puerto Rico San Juan NTSB TOVO Incident DHC6 Unknown N/A N/A N/R 1/22/1987 US Washington, DC AIDS TOVO Incident C650 IAD N/A N/A N/R 2/26/1987 US Denver, CO NTSB TOVO Accident LJ35 APA N/A N/A 80 3/24/1987 US Dallas, TX NTSB TOVO Accident CVLT DFW N/A N/A 95

(continued on next page) B-43 B-44 (ft) Veer-off Veer-off Maximum (ft) Location Y (ft) Location X Code Airport Code ICAO Aircraft Aircraft Class Event Type Event Source City/State Country Date 9/3/1988 US South Saint Paul, MN AIDS MN AC90 IL SGS 2/8/1988 US N/A Paul, Incident TOVO 2/24/1988 Springfield, AIDS N/A Saint 9/3/1988 US US SW3 SPI N/R 10/22/1988 US Incident South TOVO N/A TX 10/29/1988 US DC Houston, Morganton, NC CO N/A 1/6/1989 US AIDS Aspen, 6/20/1989 US Washington, KY N/R AIDS 7/11/1989 US FA10 IAD NY Frankfort, NTSB Incident N/A TOVO 8/16/1989 US NTSB TX AIDS Rochester, FL 4/6/1990 US N/A AIDS TOVO Dallas, Incident 8/17/1990 US LJ24 Orlando, MA N/R SW3 TOVO TOVO Incident TOVO AIDS 1/7/1991 HOU CL60 Accident AIDS FFT Nantucket, F27 TOVO Incident N/A MCO ASE 4/15/1991 US N/A AIDS N/A WW24 Accident TX ROC US Incident TOVO BE18 4/26/1991 N/A N/A N/A Houston, AC90 TOVO Incident N/A N/A 7/19/1991 US DAL US NM SW4 TOVO Incident N/A MRN AIDS N/A N/R 10/31/1991 US ACK LA N/A Kansas City, MO NTSB Albuquerque, N/A N/R KS 1/10/1992 US N/R Rouge, N/A AIDS N/A N/R Wichita, Teterboro, NJ 1/28/1994 US H25A TOVO Incident DC3 300 DC N/A HOU Baton TOVO Accident NTSB N/A 1/31/1994 US ABQ N/R IN Washington, N/A AC90 TOVO MITRE Incident AIDS 3/31/1994 US BTR N/R N/A FL Anderson, N/A N/A 9/14/1994 US AIDS NY N/A DC91 Orlando, TOVO NTSB Incident IAD 9/20/1994 US TOVO NH N/A N/R Rochester, TOVO N/A AIDS 11/29/1994 US Incident 50 LJ31 62 AIDS Incident DC3 Portsmouth, CO TOVO AIDS Accident WA 9/1/1995 US B733 ICT N/R AID N/A TOVO Spokane, 12/17/1995 US N/A Denver, SW4 TOVO Incident N/A SW2 TOVO Incident ORL MCI Incident PA 12/20/1995 US AIDS NY GLF2 ROC TOVO 700 Incident N/A AIDS PSM N/A N/A Philadelphia, SW4 York, 1/10/1996 US N/A SW3 MA N/A APA AIDS N/A New Incident N/A 1/25/1996 US TOVO VI N/A KY NTSB Hyannis, N/A 50 TEB N/A 1/27/1996 US TOVO OR N/A Louisville, Corix, NTSB AIDS Incident N/R B731 4/7/1996 US N/R AIDS N/R TOVO STX DHC6 Pendleton, N/A GEG N/R N/A N/A TOVO N/R Incident LJ55 5/30/1996 US Saint B741 Accident Accident NJ AIDS TOVO N/A C560 PHL 6/6/1996 TOVO JFK Incident N/A HYA Newark, LJ35 TOVO Incident N/A N/A SDF N/A US SW4 N/A N/A TOVO 145 40 Incident N/A AIDS PDT N/A N/A N/A N/A N/A N/R San Luis Obispo, CA CL60 TOVO Incident N/R N/R N/A EWR 55 N/A N/R N/R MITRE N/R N/A TOVO N/R Accident JS31 SBP N/A N/A 5 9/17/1996 US Miami, FL AIDS TOVO Incident BE18 MIA N/A N/A N/R 10/30/1996 US Chicago, IL MITRE TOVO Accident GLF4 PWK N/A N/A 25 12/10/1996 US Chicago, IL AIDS TOVO Incident AC56 PWK N/A N/A N/R 12/30/1996 US Orlando, FL MITRE TOVO Incident DC85 MCO N/A N/A 75 1/10/1997 US Bangor, ME NTSB TOVO Accident B190 BGR N/A N/A 10 1/19/1997 US Aspen, CO AIDS TOVO Incident LJ35 ASE N/A N/A N/R 1/25/1997 US Hayden, CO AIDS TOVO Incident B731 HDN N/A N/A N/R 2/22/1997 US Austin, TX AIDS TOVO Incident BE30 AUS N/A N/A N/R 3/6/1997 US Providence, RI AIDS TOVO Incident C650 PVD N/A N/A 50 3/14/1997 US Concord, NH AIDS TOVO Incident SW3 POH N/A N/A N/R 5/1/1997 US Ontario, CA AIDS TOVO Incident SW4 KONT N/A N/A N/R 10/24/1997 US Portland, ME AIDS TOVO Incident LJ24 PWM N/A N/A N/R 10/28/1997 England East Midlands AAIB TOVO Incident SF34 EGNX N/A N/A 90 1/10/1998 US San Francisco, CA AIDS TOVO Incident A320 SFO N/A N/A N/R 1/30/1998 US Missoula, MT AIDS TOVO Incident SW4 MSO N/A N/A N/R 3/2/1998 US Johnstown, PA AIDS TOVO Incident JS31 JST N/A N/A N/R 3/10/1998 US Detroit, MI AIDS TOVO Incident C212 YIP N/A N/A N/R 5/1/1998 US Fort Lauderdale, FL AIDS TOVO Incident SW4 FLL N/A N/A N/R 6/30/1998 England Stansted Mountfitchet AAIB TOVO Incident JS31 EGSS N/A N/A 417 11/23/1998 US Long Beach, CA AIDS TOVO Incident BE18 LGB N/A N/A N/R 12/19/1998 US Colorado Springs, CO AIDS TOVO Incident B731 COS N/A N/A 20 1/8/1999 US Lewistown, MT AIDS TOVO Incident SW4 LWT N/A N/A N/R 8/8/1999 US Chicago, IL AIDS TOVO Incident B731 MDW N/A N/A N/R 9/24/1999 US Chicago, IL AIDS TOVO Incident C402 MDW N/A N/A N/R 10/1/1999 US Louisville, KY AIDS TOVO Incident FA10 SDF N/A N/A N/R 11/19/1999 France Paris BEA TOVO Accident B731 CDG N/A N/A 35 2/3/2000 US Peru, IN AIDS TOVO Accident BE20 I76 N/A N/A N/R 3/16/2000 US Fort Lauderdale, FL NTSB TOVO Accident C402 FLL N/A N/A 330 5/21/2000 US Nantucket, MA AIDS TOVO Incident C402 ACK N/A N/A N/R 7/31/2000 US Las Vegas, NV AIDS TOVO Incident B731 LAS N/A N/A N/R 12/28/2000 US Erie, PA AIDS TOVO Incident LJ25 ERI N/A N/A 15 3/10/2001 US Bar Harbor, ME AIDS TOVO Incident B190 BHB N/A N/A N/R (continued on next page) B-45 B-46

(ft) Veer-off Maximu m 60 (ft) Location Y (ft) Location X N/A N/A Code Airport EHAM

Code ICAO Aircraft B741 Class Event Incident Type Event TOVO Source Netherland TSB City/State Amsterdam Country Netherlands Date 4/7/2001 8/28/2001 US 3/9/2002 US 7/20/2002 US Anchorage, AK 9/21/2002 US Chicago, IL 9/29/2002 US Chicago, IL 12/8/2002 US Ardmore, OK AIDS 12/13/2002 US Chicago, IL US 2/17/2003 MITRE Hawthorne, CA 3/16/2003 US New Orleans, LA AIDS AIDS 4/2/2003 US TOVO Manassas, VA 5/28/2003 US NTSB Incident TOVO ND AIDS Richmond, VA AIDS 8/18/2003 B190 Accident Bismarck, Cedar City, UT AK SW3 6/4/2004 US TOVO US TOVO MITRE AIDS ANC 6/17/2004 US Fairbanks, TOVO Incident PA AIDS Incident AIDS DPA TOVO 7/29/2005 F2TH N/A GLF2 TOVO Accident NTSB Lancaster, LJ35 SW4 TOVO Incident AFA Incident St Augustine, FL SW4 11/8/2005 US Incident TOVO US N/A CA N/A BIS TOVO Incident MDW AIDS ADM C560 1/20/2006 England Glasgow WW24 N/A Accident Eureka, N/A HHR N/A TOVO 1/21/2006 US N/A N/A ID NEW MDW MITRE TOVO LJ35 TOVO Mount Pleasant, SC Incident 1/29/2006 Incident N/A AIDS N/A N/R N/A LNS Caldwell, N/A N/A SW4 Incident 1/30/2006 N/A FL US E120 AIDS N/A AAIB AIDS HEF AIDS N/R N/R N/A 2/20/2006 US PA31 TOVO RIC TOVO SW3 Incident Lauderdale, EKA N/A CDC FXE 340 6/6/2006 US N/A Incident US N/A TOVO N/A N/A N/A N/A Accident AT43 Las Vegas, NV 7/27/2006 US TOVO AC68 Incident TOVO Fort Incident KY EGPK N/A 175 EUL N/A N/A BE40 N/R N/A 55 Las Vegas, NV 8/12/2006 US N/A N/A TOVO TX Louisville, Casper, WY N/R 5/22/2007 England Exeter N/R AIDS N/R SGJ N/A N/A 25 Amarillo, Incident N/A Sydney 7/14/2007 Australia AIDS N/R N/A N/A BE20 AIDS 11/11/2007 Canada TSB 17 N/A B721 TOVO N/R Incident US 1/19/2008 SDF 250 LRO NTSB TOVO N/A LJ31 TOVO 2/14/2008 US N/R Incident 35 US NC AAIB AMA TOVO ATSB N/A 5/26/2008 US Incident N/A WA N/A Greensboro, N/A Kansas City, MO Incident AIDS 8/20/2008 US A319 IL HUNT EGTE Everett, TOVO N/A N/A Accident A319 TOVO New York, NY B731 12/20/2008 US TOVO Incident N/R Chicago, YSSY LAS N/A AIDS CO N/A AIDS DC85 Incident TOVO 45 Incident N/A 50 GSO LAS SW4 Denver, AIDS N/A N/A N/A AIDS SW3 TOVO N/R Incident N/A CPR PAE N/A NTSB C525 N/R 165 TOVO N/A Accident PWK TOVO N/A N/A N/A 25 Incident N/A N/A TOVO TOVO B731 N/A LJ60 Accident DEN Incident N/R N/A 40 N/A N/R MKC B741 N/R N/A JFK N/A 25 N/A 525 N/A N/A N/R N/R C-1

APPENDIX C Sample of Normal Operations Data al 1 Exampleofnormaloperationsdata. Table C1. ADS 20040501 0 2 1 1 42 15 0 NHASWFADS 20040501 1575 0 2 4 15 15 0 10.00 0 0 0 0 1 14 0 ADS NHASWF 15.7 20040501 1575 2 4 1 4 2 0 0 18 1.4 0 10.00 0 0 NHASWF 0 0 1 14 0 ADS 15.7 20040501 3000 2 4 1 4 2 0 1 18 1.4 0 0 0 0 30 10.00 1 0 0 0 0 0 0 16 NHASWF 0 1.6 ADS 20040501 3000 2 4 1 1 2 0 0 19 0 0 0 30 10.00 1 0 0 0 0 0 0 16 NHASWF 0 1.6 ADS 20040501 3000 1 4 1 4 2 0 0 19 0 1 0 30 10.00 4 0 0 0 0 0 0 15 NHASWF 1 1.5 ADS 20030501 3000 2 4 1 4 2 0 0 23 0 1 0 30 10.00 4 0 0 0 0 0 0 15 NHASWF 1 1.5 ADS 20030501 3000 2 4 1 4 2 0 0 23 0 1 0 30 10.00 2 0 0 0 0 0 0 23 NHASWF 0 2.3 ADS 0 241 7 0 20021101 3000 0 1 0 30 10.00 NHASWF 2 0 0 0 0 0 0 23 0 2.3 ADS 1280 0 2315 7 0 20021101 NHASWF ADS 1280 0 241 8 0 20021101 NHASWF ADS 1083 0 241 9 0 20021101 NHASWF ADS 1083 0 241 9 0 20021101 NHASWF ADS 1083 20020201 2 4 1 1 2 0 0 11 NHASWF ADS 20020201 3000 2 4 1 4 2 0 0 11 1 0 0 0 0 0 0 7 10.00 NHASWF 0 0 0.53 ADS 30 20020201 3000 0 0.7 1 5 1 1 2 0 0 11 1 0 0 0 0 0 0 7 10.00 NHASWF 0 0 0.53 ADS 30 20040501 3000 0 0.7 2 4 1 1 2 0 0 22 1 0 0 0 0 0 0 7 10.00 NHASWF 0 0 0.53 ADS 30 20020201 3000 0 0.7 2 4 1 1 2 0 0 17 10.00 2 0 0 0 0 0 0 12 NHASWF ADS 0 1 20020201 0.24 30 3000 2 4 1 1 2 0 0 17 2 0 0 0 0 0 0 0 1.2 9 10.00 NHASWF 0 1 0.48 ADS 30 20020201 3000 0 0.9 2 4 1 4 2 0 0 17 2 0 0 0 0 0 0 9 10.00 NHASWF 0 1 0.48 ADS 30 20040501 3000 0 0.9 2 4 1 4 2 0 1 23 2 0 0 0 0 0 0 9 10.00 NHASWF 0 1 0.48 ADS 30 20040501 3000 0 0.9 2 4 1 4 2 0 0 23 10.00 2 0 0 0 0 0 0 11 NHASWF 0 1 0.57 30 3000 0 1.1 10.00 2 0 0 0 0 0 0 11 0 1 0.57 30 0 1.1 LOCID

YYYYMMDD

HOUR

FLT_TYPE

TERRAIN

HUB

USER_CLASS

ETMSARR

NEQPT_CLASS

NEQPT_TYPE

Wx Stratum

CEILING Ft 0 1 5.000 90 0 0 0.38 12.8 0 1 5.000 90 0 0.9 0 0 0.38 12.8 0 21 4.000 90 0 0.9 0 0 1 0.38 10.8 0 1 4.000 90 0 0.9 0 0 0.24 10.8 0 1 4.000 90 0 0.9 0 0 0.24 10.8 0.9 0

VIS Sm

TEMP

Fog

Icing

Elec. Storm

Frozen Precip

Snow

PRECIP FINAL

Light

XWIND Knts

Light2

PRECIP FINAL2

CEILING100FT

TEMP10C

DawnDusk C-3

Table C2. Codes used for NOD.

Field Notes LOCID Airport IATA/FAA code YYYYMMDD Date HOUR Local Time FLT_TYPE Foreign Origin/destination = 1; Domestic = 0 Significant terrain (code 1) if the terrain within the plan view exceeds 4,000 feet above the airport elevation, or if the terrain within a 6.0 nautical mile radius of the Airport Reference Point rises to at least 2,000 feet above the TERRAIN airport elevation. HUB 1 Hub; 2 Non-hub USER_CLASS 1 Commercial; 2 Air Taxi; 3 Freight; 4 GA ETMSARR Arrival counts ETMSDEP Departure counts 1 A/B (255000lbs+/B757 Heavy); 2 C(41000-255000lbs Large Jet); 3 D(41000-255000lbs Large commuter); 4 E (12500-41000lbs Medium); 5 F NEQPT_CLASS (<12500lbs Small) NEQPT_TYPE 1 Turboprop; 2 Jet Wx Stratum For stratified sampling purposes CEILING Ft Ceiling in feet VIS Sm Visibility capped Max 10SM TEMP Degree C Fog Yes = 1; No = 0 Icing Yes = 1; No = 0 Elec. Storm Yes = 1; No = 0 Frozen Precip Yes = 1; No = 0 Snow Yes = 1; No = 0 PRECIP FINAL 0 None; 1 Trace/Light; 2 Moderate; 3 Heavy Light 1 Day; 2 Night; 3 Dawn; 4 Dusk APP XIND Knts In knots DEP XWIND Knts In knots Light2 0 Day; 1 Night/Dawn/Dusk PRECIP FINAL2 0 None; 1 Trace/Light/Moderate/Heavy CEILING100FT Ceiling capped Max 3000ft DawnDusk 0 Day/Night; 1 Dawn/Dusk D-1

APPENDIX D Aircraft Database Summary D-2 (kts) Speed Speed Approach V2 (kts) (ft) Landing Distance (ft) Takeoff Distance (lb) MTOW (#) Engines Type Engine Height (ft) (ft) Length (ft) Wingspan Code ICAO Manufacturer Manufacturer Aircraft Name A-300 Airbus A30B 147.1 177.5 54.3 Jet 2 378,534 7,349.1 5,026.2 160 135 138 138 138 160 138 135 135 145 5,026.2 145 4,265.1 135 4,429.1 4,724.4 7,349.1 5,249.3 160 4,593.2 140 5,741.5 130 7,185.0 378,534 150 7,250.7 5,026.2 150 150 145 150 130,073 145 145 141,096 145 2 162,040 7,349.1 145 145 182,984 135 5,905.5 145 150 5,905.5 2 5,790.7 2 Jet 160 378,534 6,003.9 2 6,299.2 2 7,545.9 6,561.7 Jet 7,545.9 6,594.5 4,888.5 Jet 2 9,071.5 54.3 Jet 9,071.5 Jet 10,498.7 507,063 7,513.1 10,301.8 Jet 41.2 507,063 9,744.1 38.6 606,271 38.6 177.5 606,271 330,693 2 54.3 38.6 811,301 2 811,301 4 2 1,234,589 103.2 Jet 4 111.2 Jet Jet 4 177.5 123.3 147.1 Jet 4 146.0 51.8 Jet 4 57.1 Jet 55.3 111.9 Jet 147.1 54.8 111.9 153.1 Jet 55.3 111.9 A30B 192.9 56.1 111.9 208.7 56.8 144.0 A306 194.8 79.1 Mohawk 298 A318 208.7 Aerostar 600 A319 197.8 A310 222.8 A-300 Airbus A320 197.8 247.0 A-300-600 Airbus A321 197.8 239.5 A-310-200/300 Airbus 197.8 Aerospatiale A-318 Airbus A332 208.2 N262 A-319 Airbus Aerostar A333 208.2 A-320 Airbus A342 261.8 AEST A-321 Airbus 71.9 A343 A-330-200 Airbus A345 A-330-300 Airbus 36.7 A346 63.3 A-340-200 Airbus A388 A-340-300 Airbus 34.8 20.3 A-340-500 Airbus A-340-600 Airbus Turboprop 12.8 A-380-800 Airbus 2 Alenia ATR-42-200/300 Piston Alenia ATR-72-200/210 Avro 748 23,369 ATR Jetsream 31 2 ATR Jetsream 32 2,296.6 AT43 Jetsream 41 1,312.3 6,305 AT72 100 King Air 100 80.7 33 Debonair 1,804.5 Bae Systems 88.9 Beech 55 Baron Avro 110 Bae Systems Beech 60 Duke 1,148.3 74.5 JS31 Bae Systems Beech 76 Duchess 89.2 JS32 95 A748 Beech 99 Airliner JS41 Beech 24.9 52.0 25.3 Beech 52.0 Beech 94 Turboprop 98.2 BE10 60.4 Beech 47.1 Beech Turboprop BE33 BE55 47.1 2 Beech 66.9 45.9 63.4 2 17.5 BE60 BE76 33.5 17.7 37.7 BE99 36,817 24.9 Turboprop 18.4 40.0 39.4 38.1 47,399 Turboprop 3,608.9 Turboprop 25.6 27.9 45.9 2 Turboprop 4,921.3 15.4 33.8 3,280.8 2 29.2 2 3,608.9 2 8.2 9.5 Turboprop 44.6 110 15,562 12.5 110 9.5 16,226 46,495 104 5,905.5 2 14.4 Piston Piston 24,000 105 5,150.9 Piston 4,265.1 3,280.8 Piston Turboprop 4,921.3 4,002.6 11,795 110 1 2 2,034.1 4,265.1 2 110 2 1,476.4 2 110 125 110 3,064 5,071 125 2,132.5 100 16,755 6,768 120 3,902 105 1,148.3 1,476.4 3,280.8 1,968.5 2,132.5 111 1,476.4 984.3 2,952.8 1,312.3 1,968.5 95 115 75 95 85 90 107 70 98 76 D-3 (continued on next page) B707-100 Boeing B701 130.9 144.7 42.3 Jet 4 190,003 8,694.2 6,496.1 139 139 150 125 130 137 137 145 135 6,496.1 139 140 5,249.3 145 125 145 130 4,921.3 140 141 4,921.3 159 150 8,694.2 144 139 152 6,889.8 135 152 4,593.2 140 4,593.2 8,202.1 160 145 4,593.2 9,842.5 154 190,003 149 4,921.3 170 4,593.2 120,999 173 4,265.1 5,905.5 178 6,003.9 135 4,593.2 169,095 185 5,249.3 142 4 5,249.3 210,101 8,595.8 6,561.7 130 5,577.4 2 6,233.6 4,921.3 130 6,233.6 6,233.6 110,121 150 3 Jet 145 115,500 5,905.5 7,217.8 3 145 Jet 124,495 7,545.9 6,988.2 145 160 138,494 7,545.9 Jet 10,000.0 157 160 10,465.9 42.3 115,500 2 Jet 123,988 160 2 10,498.7 29.5 4,593.2 146,211 2 10,826.8 5,905.5 155,492 170 2 10,826.8 34.3 Jet 4,921.3 174,198 2 Jet 34.1 144.7 2 5,905.5 735,021 Jet 975,001 124.0 2 5,905.5 826,403 Jet 150 7,841.2 6,233.6 2 37.2 826,403 Jet 8,530.2 133.2 37.2 2 5,577.4 Jet 874,993 8,858.3 153.2 130.9 36.6 4 Jet 9,514.4 36.6 93.2 160 4 4 Jet 10,498.7 9,514.4 36.6 4 Jet 94.0 255,031 40.8 108.0 100.2 4 Jet 272,491 40.8 9,514.4 Bonanza V35B 107.9 B701 109.6 Jet 395,002 40.6 King Air F90 Jet B712 5,905.5 119.4 Jet 412,000 910,002 40.6 Super King Air 300 93.0 101.7 2 Jet 449,999 64.2 102.5 Premier 1A B721 93.0 2 64.2 110.3 B707-100 Boeing B722 94.8 2 545,005 4 64.2 Beech 9,514.4 129.5 B717-200 Boeing 64.3 94.8 2 Jet Beech 64.2 138.2 B727 Stage 3 Noise Acft B731 94.8 2 Beech Jet Jet 229.0 BE35 B727-100 Boeing 112.6 B732 Jet BE30 229.0 B727-200 Boeing 112.6 B733 Boeing Beechcraft 2 Jet BE9T 449,999 45.1 229.0 B737 Stage 3 Noise Acft 112.6 B734 33.4 64.3 Jet PRM1 44.8 229.2 246.9 54.5 B727Q B737-100 Boeing 112.6 B735 45.9 52.9 B737-200 Boeing 195.3 B736 Boeing Jet 26.3 2 44.5 107.9 52.6 B737-300 Boeing 195.7 B737 44.0 231.9 55.8 39.8 155.2 B737Q B737-400 Boeing 195.7 B738 7.6 153.2 Jet 177.4 46.0 B737-500 Boeing 195.6 B739 14.8 224.4 61.5 159.2 93.0 B737-600 Boeing B741 34.1 213.0 180.2 Turboprop B737-700 Boeing B742 Piston 15.3 55.8 201.3 B737-800 Boeing 124.8 B743 94.0 Turboprop 2 B737-900 Boeing 124.8 B744 Jet 1 Jet 209.1 B747-100 Boeing 156.1 37.2 B748 B744ER 201.3 2 B747-200 Boeing 156.1 13,889 B747-300 Boeing 170.3 B752 3,400 3 2 1,870.1 Jet B747-400 Boeing B753 10,950 170.3 B747-400ER Boeing 199.9 B762 1150 1,771.7 210,101 B747-8 Boeing B763 12,500 115 2 B757-200 Boeing 9,842.5 B764 1480 3,792.0 B757-300 Boeing B764ER 4,921.3 103 B767-200 Boeing B772 110,121 3,170.0 145 B767-300 Boeing 5,905.5 B767-400 Boeing 150 B767-400ER Boeing 70 4,593.2 B777-200 Boeing 121 145 137 108 D-4

(kts) Speed Approach 125 140 V2 (kts) (ft) Landing Distance (ft) Takeoff Distance (lb) MTOW (#) Engines Type Engine Height (ft) (ft) Length (ft) Wingspan B462 86.4 93.7 28.2 Jet 4 93,035 3,379.3 4,051.8 125 125 Code ICAO

British British Aerospace BA11 Aerospace 93.5 107.0 25.4 Jet 2 99,651 7,470.5 4,757.2 140 129 Manufacturer Aircraft Name B777-200LR B777-300 B777-300ER B787-8 Dreamliner BMD-90 BD-700 Global Express Boeing Boeing Bombardier B772LR BAC 1-11 Boeing Boeing GLEX 212.6 BAE-146-200 B788 B773ER B773 CL-600 Challenger 93.8 209.1 212.6 Boeing RJ-100 Regional Jet 197.2 199.9 RJ-200 Regional Jet 61.5 99.4 242.3 MD90 186.1 RJ-700 Regional Jet Canadair 242.3 Canadair RJ-900 Regional Jet 61.8 24.9 107.8 55.5 CL60 Jet Canadair Aviocar 61.5 CRJ1 Canadair 500 Citation 152.6 CRJ2 61.8 Jet Jet Canadair Cessna 120 Jet Jet CRJ7 69.6 2 Commuter 31.2 CRJ9 69.6 68.4 Skyhawk 76.2 2 2 87.9 766,001 2 2 Cessna Jet 76.4 87.9 9,514.4 Cessna 106.7 20.7 Casa 775,002 Cessna Caravan 1 484,001 98,106 5,577.4 C150 Cessna 659,998 118.8 20.7 9,514.4 Cessna C500 24.8 2 6,135.2 9,842.5 C172 C212 Rocket Jet 24.6 5,905.5 C120 33.5 Jet Cessna 1,358.3 Utililiner 5,905.5 Jet C182 139 47.2 164,244 C185 160 Cessna Jet 35.8 120 66.6 168 32.8 C208 21.7 7,217.8 Jet 2 Chancellor 145 36.1 2 43.6 Cessna 126 36.2 C210 145 Cessna 2 Golden Eagle 26.9 3,937.0 53.1 2 52.2 21.0 6.9 Corsair 140 47,399 28.2 14.4 Cessna C340 47,600 2 25.8 36.7 Cessna C402 Cessna Cessna 441 Conquest 21.7 8.9 47,399 5,249.3 37.7 140 Piston 72,753 Cessna 500 Citation 1 C414 9.2 38.1 Turboprop C421 5,249.3 7.8 28.2 Jet 44.2 C404 80,491 Cessna 501 Citation 1SP 4,593.2 Piston Cessna 5,249.3 14.1 Cessna 4,593.2 135 2 1 6,168.0 41.0 34.4 Piston 4,849.1 Cessna 40.0 Piston 9.8 49.5 Cessna Piston 36.4 Turboprop 135 C425 2 1 5,118.1 135 C441 135 12.5 33.8 16,976 C500 1,499 135 170 33.8 1 C501 1 11.8 39.0 Piston 1 1 44.3 135 49.3 10,847 2,952.8 2,315 150 11.8 Piston 820.2 47.2 11.8 47.2 Piston 13.1 1,640.4 8,001 3,274.3 2,800 1 35.8 1,450 3,351 39.0 984.3 656.2 100 Piston 1,870.1 Piston 43.6 2 1,640.4 Piston 43.6 656.2 2 12.8 650.0 650.0 524.9 120 13.1 4,012 55 81 1,476.4 14.4 2 1,348.4 Turboprop 14.4 2 460.0 Turboprop 60 2 5,975 125 610.0 1,312.3 85 6,305 55 65 2 1,476.4 2,132.5 2 Jet 65 6,746 104 2,221.1 Jet 6,834 8,444 92 70 1,640.4 1,765.1 1,706.0 8,598 1,968.5 2,296.6 9,855 95 95 2 75 2,296.6 2 2,460.6 2,460.6 1,968.5 1,804.5 110 100 100 100 95 2,132.5 10,847 1,148.3 10,847 105 94 96 100 105 3,274.3 3,274.3 110 1,870.1 100 1,870.1 120 120 108 125 D-5 (continued on next page) DHC5 65.0 49.5 19.4 Turboprop 2 12,500 1,640.4 984.3 80 77 984.3 2 1,640.4 Turboprop DHC5 65.0 12,500 49.5 19.4 DH8A 85.0 73.2 24.6 Turboprop 2 34,502 2,952.8 2,952.8 100 100 100 2,952.8 2 2,952.8 Turboprop DH8A 85.0 34,502 73.2 24.6 DH8D 93.2 107.6 27.2 Turboprop 2 63,930 4,265.1 3,608.9 115 115 115 3,608.9 2 4,265.1 Turboprop 63,930 27.2 DH8D 93.2 107.6 Canada Canada DHC7 93.2 80.7 26.2 Turboprop 4 47,003 2,952.8 3,280.8 90 83 Canada DHC7 3,280.8 93.2 4 Turboprop 80.7 2,952.8 26.2 47,003 Canada Canada DH8C 89.9 84.3 24.6 Turboprop 2 41,099 3,608.9 3,280.8 110 90 Canada DH8C 3,280.8 89.9 2 Turboprop 84.3 3,608.9 24.6 41,099 Canada De Havilland De Havilland De Havilland De Havilland De Havilland Ultra Cessna C560 45.3 48.9 13.8 Jet 2 15,895 3,159.4 2,919.9 105 108 105 2,919.9 3,159.4 15,895 2 Jet 13.8 48.9 45.3 C560 Cessna 525 Citation CJ1 Cessna 550 Citation 2 Cessna 560 Citation 5 Cessna Ultra Cessna Cessna 650 Citation 3 Cessna C525 Cessna 750 Citation 10 Cessna Stationair 6 C550 Cessna 46.9 Cessna T303 Crusader Cessna Cessna T310 52.2 Citation CJ2 C650 42.7 Cessna C750 Cessna Citation CJ3 47.2 Citation Excel 53.5 13.8 C206 C303 64.0 Falcon 10 Falcon 200 15.1 Cessna 55.4 35.8 Jet Falcon 2000 39.0 72.2 Cessna Falcon 50 Cessna C310 16.8 Jet Cessna Falcon 900 28.2 19.0 30.5 C25A 2 C25B DHC-5 Buffalo 37.1 Dassault C56X Jet 13.5 9.8 Dassault 49.5 2 Jet Dassault 10,399 49.5 FA10 31.8 55.8 FA20 Piston Piston 46.9 Dassault 3,080.7 F2TH 15,102 2 Dassault 2 46.9 42.9 10.8 51.8 2,749.3 53.5 3,280.8 FA50 13.8 2 63.3 1 F900 30,997 115 13.8 Piston 3,002.0 45.5 35,699 17.1 56.4 61.9 5,249.3 66.3 115 107 Jet 63.3 5,159 5,708.7 3,638 Jet 2 2,952.8 17.4 Jet 60.8 108 3,818.9 1,748.7 23.3 66.3 820.2 125 2 125 1,460.0 29.4 5,498 2 Jet 1,476.4 114 2 24.9 Jet Jet 85 130 12,375 1,663.4 75 Jet 12,375 110 19,200 1,791.3 2 3,418.6 Jet 2 2 92 3,418.6 95 2,985.6 3,461.3 3 29,013 2,985.6 115 18,739 2,919.9 35,803 3 110 115 5,249.3 115 118 5,249.3 38,801 3,608.9 46,738 118 125 5,249.3 4,593.2 120 4,921.3 120 3,608.9 107 2,296.6 120 114 125 113 100 104 DHC-7 Dash 7 DHC-8-100 Dash 8 DHC-8-300 Dash 8 DHC-8-400 Dash 8 Aircraft Douglas DC8Q 142.4 150.6 42.3 Jet 4 324,961 9,842.5 6,561.7 130 137 137 130 137 150 127 127 130 130 130 6,561.7 160 140 140 6,561.7 140 6,561.7 9,842.5 6,561.7 4,921.3 4,921.3 9,842.5 4,921.3 9,842.5 10,006.6 324,961 6,889.8 6,889.8 324,961 6,889.8 349,874 4 357,204 110,099 4 110,099 Jet 4 121,109 4 Jet 2 Jet 2 42.3 Jet 2 Jet 42.3 Jet 42.3 Jet 43.0 150.6 27.5 150.6 27.6 187.3 28.0 187.3 142.4 119.4 142.4 119.4 142.4 133.5 148.3 DC8Q 89.6 89.6 DC85 93.5 DC86 DC87 DC-8 Stage 3 Noise DC91 Aircraft Douglas DC93 DC-8-50 Douglas DC94 DC-8-60 Douglas DC-8-70 Douglas DC-9-10 Douglas DC-9-30 Douglas DC-9-40 Douglas D-6 (kts) Speed Speed Approach V2 (kts) (ft) Landing Distance (ft) Takeoff Distance (lb) MTOW (#) Engines Type Engine Height (ft) (ft) Length (ft) Wingspan D328 68.8 69.3 23.9 Turboprop 2 30,843 3,280.8 3,937.0 110 110 110 3,937.0 3,280.8 2 Turboprop 30,843 D328 68.8 23.9 69.3 Code GLF4 77.8 88.3 24.3 Jet 2 73,193 5,249.3 3,280.8 145 128 145 GLF4 77.8 24.3 88.3 Jet 3,280.8 5,249.3 2 73,193 GLF2 68.1 79.1 Jet 2 65,301 141 ICAO Dornier J328 68.8 69.9 23.6 Jet 2 33,510 4,265.1 3,937.0 135 120 135 Dornier J328 68.8 23.6 69.9 3,937.0 Jet 4,265.1 Dornier 2 33,510 Fairchild- Fairchild- Aerospace GLF5 93.5 96.5 25.9 Jet 2 145 145 2,900.3 90,689 5,150.9 Aerospace Aerospace GLF3 77.8 83.0 24.6 Jet 2 145 136 3,280.8 69,710 5,905.5 Aerospace Aerospace AC95 52.2 43.0 15.1 Turboprop 2 100 500 1,640.4 11,199 1,640.4 Gulfstream Gulfstream Gulfstream Gulfstream Gulfstream Gulfstream Gulfstream Gulfstream Gulfstream Gulfstream Manufacturer Manufacturer Aircraft Name Ilyushin IL-62 Ilyushin IL-96 Ilyushin Ilyushin IL62 IL96 141.7 197.2 174.2 181.4 40.7 57.4 Jet Jet 4 4 363,763 595,248 10,826.8 9,186.4 7,545.9 150 6,561.7 150 152 150 G-1159D Gulfstream 5 G-1159C Gulfstream 4 G-1159A Gulfstream 3 DC-9-50 Douglas DC95 93.5 133.5 27.9 Jet 2 121,109 6,889.8 4,921.3 140 132 132 140 140 135 4,921.3 130 4,921.3 145 145 130 6,889.8 125 6,889.8 140 140 4,429.1 121,109 4,461.9 135 121,109 4,176.5 4,340.6 6,561.7 130 2 2 5,774.3 5,393.7 6,745.4 46,734 Jet 4,429.1 Jet 44,070 2 79,344 27.9 6,561.7 105,359 27.9 Jet 2 46,734 2 133.5 2 133.5 22.2 Jet 2 Jet Jet Jet 93.5 93.5 22.2 98.0 22.2 32.3 34.7 DC95 65.7 98.0 DC95 86.4 98.1 118.9 68.9 DC-9-50 Douglas E145 65.7 DC-9-50 Douglas 85.3 E45X EMB-110 Bandeirante 94.2 EMB-120 Brasilia EMB-145 Embraer Embraer E135 EMB-145XR Embraer E170 Embraer 140 E110 Embraer E190 Embraer 175 Embraer 195 E120 50.2 ERJ-135 Embraer ERJ-170 Embraer 65.0 46.6 ERJ-190 Embraer Embraer Embraer 328 Jet Envoy 3 E140 16.1 Embraer 65.6 E175 Turboprop E195 21.0 65.7 85.3 2 Turboprop 94.2 93.3 103.9 2 13,007 126.8 22.1 31.9 3,937.0 26,455 34.6 4,265.1 Jet 4,593.2 Jet 90 Jet 4,593.2 2 120 92 2 2 120 46,518 82,673 107,564 6,069.6 7,362.2 7,149.0 4,527.6 4,137.1 130 4,206.0 140 140 135 145 145 G-1159 Gulfstream 2 Fairchild-Dornier 328 F-27 Friendship F-28 Fellowship Fokker 100 Fokker 50 Fokker 70 Fokker Greyhound C2 Fokker 695 JetProp Commander 980/1000 F27 Fokker F28 Fokker 95.1 Grumman F100 Fokker 88.8 F50 C2 75.8 92.2 F70 89.9 27.9 95.1 80.7 116.5 27.9 95.5 Turboprop 82.7 27.9 57.7 101.4 2 Jet 27.2 18.4 27.9 Jet 44,996 Turboprop Turboprop 2 Turboprop 2,296.6 2 2 2 2 72,995 1,968.5 100 43,982 5,577.4 95,659 54,426 71,981 3,280.8 3,608.9 120 5,577.4 2,608.3 4,265.1 135 3,608.9 4,593.2 1,476.4 3,937.0 120 135 105 125 125 120 130 105 120 D-7 (continued on next page) ASTR 52.8 126 55.4 18.0 130 Jet 2,952.8 5,249.3 2 24,648 MD11 169.9 200.8 57.7 155 160 Jet 6,889.8 10,170.6 3 630,500 MD81 107.8 147.7 30.2 150 Jet 140 5,200.1 3 6,732.3 149,500 MD88 107.8 147.7 30.2 150 Jet 140 5,200.1 3 6,732.3 149,500 GALX 58.1 62.3 21.3 130 125 Jet 3,444.9 2 5,905.5 34,851 WW24 44.9 52.2 15.7 129 Jet 125 2,460.6 2 4,839.2 22,928 Israel Israel Israel Douglas DC10 165.4 180.4 58.1 136 Jet 150 5,905.5 Douglas 9,842.5 3 572,009 Douglas MD80 107.8 147.7 30.2 Jet 150 140 Douglas 5,200.1 3 6,732.3 149,500 Douglas MD82 107.8 147.7 30.2 Jet 150 140 Douglas MD83 107.8 147.7 30.2 5,200.1 3 6,732.3 Jet 149,500 150 140 Douglas 5,200.1 3 6,732.3 160,001 Industries Industries Industries Aerospace Aerospace Aerospace Aerospace Aerospace McDonnell McDonnell McDonnell McDonnell McDonnell McDonnell McDonnell MD-80 MD-82 LR-1 Marquise Aerostar 200 Mitsubishi MU2 Mooney M20P 39.0 35.1 33.1 23.3 12.8 Turboprop 8.2 2 Piston 10,053 1 2,132.5 1,968.5 2,579 120 1,476.4 88 820.2 70 70 MD-11 MD-81 MD-83 MD-88 Electra Lockheed L188 99.1 104.3 32.8 Turboprop 4 112,987 4,265.1 2,952.8 120 130 120 2,952.8 4,265.1 112,987 4 Turboprop 32.8 104.3 Learjet 24 99.1 Learjet 25 Learjet 31 Learjet 35 Learjet 35 L188 Learjet 45 Learjet 55 Learjet Learjet 60 Learjet AC-130 Spectre Learjet LJ24 Electra Lockheed Learjet LJ25 L-1011 TriStar Learjet LJ31 35.1 P-3 Orion Learjet LJ35 35.4 Learjet Lockheed LJ35 43.6 DC-10 43.0 Learjet LJ45 39.4 47.6 C130 LJ55 Lockheed 39.4 48.6 LJ60 47.9 48.6 12.1 132.5 L101 43.6 Lockheed 48.6 12.5 44.0 58.1 12.1 97.8 155.5 Jet Jet 55.1 12.1 P3 Jet 58.7 14.1 38.7 178.1 Jet 14.8 99.7 2 Jet 2 Turboprop 14.8 55.4 2 Jet 2 Jet 116.8 4 14,991 13,001 2 Jet Jet 15,498 2 3,937.0 0.0 155,007 18,298 2 3,608.9 18,298 2,952.8 3,608.9 Turboprop 2 4,265.1 3 19,511 2,952.8 130 4,265.1 2,624.7 21,010 2,952.8 130 4 4,265.1 23,104 429,990 2,952.8 137 120 140 4,593.2 2,952.8 120 140 7,874.0 5,249.3 135,000 130 3,280.8 125 140 5,905.5 3,608.9 125 140 140 150 140 140 128 138 140 134 1126 Galaxy 1124 Westwind 1125 Astra D-8 (kts) Speed Speed Approach V2 (kts) (ft) Landing Distance (ft) Takeoff Distance (lb) MTOW (#) Engines Type Engine Height (ft) (ft) Length (ft) Wingspan Code ICAO Manufacturer Manufacturer Aircraft Name Astra Pilatus PC7 34.1 32.2 10.5 Turboprop 1 6,393 984.3 1,312.3 90 90 85 70 90 110 75 1,312.3 1,804.5 73 1,640.4 984.3 1,968.5 75 984.3 80 6,393 1,968.5 9,921 80 5,203 1 80 1,312.3 4,799 1 2 75 4,586 1,312.3 2 Turboprop Turboprop 2 65 Piston 1,312.3 Piston 984.3 Piston 10.5 60 14.1 984.3 10.3 10.2 11.2 2,551 4,762 656.2 32.2 47.2 30.8 1 3,792 27.1 2 31.2 820.2 34.1 39.4 Piston 53.1 2 37.0 1,676 Piston 37.4 P68 7.5 PC7 Piston PC12 1 PA23 9.8 Observer Partenavia 24.1 PA27 P-180 Avanti 8.5 Piston Astra Pilatus Eagle Pilatus Apache Piper 36.0 28.5 Arrow 4 9.2 27.6 Aztec Piper Piaggio Cherokee Lance Cherokee Six PA24 P180 23.0 Cheyenne 2 39.0 38.7 Cheyenne 3 45.9 Cheyenne 400 Piper Piper Comanche Piper 35.1 47.2 Malibu Meridian Piper PA44 Malibu Mirage P32R P28T PA34 Piper 12.8 Navajo Chieftain PA32 Piper PA-28-140 Cherokee Piper 36.1 35.4 PA38 Turboprop PA-28R Cherokee Arrow PAY2 Piper 36.1 Seminole Piper PAY3 2 PAY4 28.2 27.2 Piper Seneca Piper Piper 42.7 Piper Piper P46T Tomahawk Piper 26.9 47.6 47.6 8.5 11,552 8.2 Twin Comanche PA46 36.4 P28R P28A PA31 400 Beechjet 43.0 8.2 2,952.8 43.3 43.3 90 King Air Piston Piston 43.0 12.8 29.9 35.1 40.7 2,952.8 Bae 125-1000 1900 29.5 14.8 Piston 17.1 Bae 125-700/800 Turboprop 120 Piper 1 1 28.5 Beech 24.3 24.0 Turboprop 32.5 11.5 Turboprop Raytheon Beech 36 Bonanza 120 2 1 Raytheon B190 11.5 PA30 Beech 58 Baron Turboprop 58.1 2 Raytheon 3,616 7.9 13.1 7.2 2,910 2 110 113 57.7 Turboprop Raytheon BE40 2 Raytheon 15.4 2,706.7 Super King Air 200 3,773.0 16,954 8,995 1 BE9L 3,616 Super King Air 350 1,640.4 Piston 36.0 1,148.3 H25C Raytheon Piston H25B 11,244 Piston Piston 43.6 12,059 1,804.5 2,132.5 1,640.4 656.2 50.2 Raytheon Raytheon BE36 2,296.6 25.0 51.5 2,296.6 4,740 1 54.5 75 2,460.6 2 Raytheon 48.6 1 1,804.5 1 70 2,132.5 BE58 BE20 2,132.5 100 27.6 35.4 1,476.4 8.3 75 53.8 B350 51.2 105 75 4,299 13.8 125 6,504 70 2,491 1,476.4 2,425 37.7 54.5 100 14.1 26.6 105 75 17.1 Piston 1,476.4 18.0 110 58.1 80 1,312.3 984.3 Jet 984.3 Turboprop 29.9 44.0 1,476.4 8.5 1,968.5 75 46.6 2 Jet Jet 984.3 984.3 80 2 90 14.8 9.7 2 Piston 70 14.4 65 75 Turboprop 3,600 100 10,099 2 2 Piston Turboprop 16,094 70 1 65 2 2,296.6 3,937.0 30,997 2 27,403 2 1,246.7 3,638 3,608.9 12,500 6,233.6 5,577.4 100 14,991 130 1,870.1 2,916.7 5,512 1,148.3 2,952.8 100 3,280.8 125 111 125 1,771.7 1,476.4 2,296.6 2,690.3 115 75 132 125 1,968.5 120 103 100 75 110 96 D-9 SBR1 44.5 48.3 Jet 2 20,000 120 AC90 46.7 44.4 15.0 Turboprop 2 Turboprop 10,251 AC90 46.7 15.0 44.4 97 Rockwell Rockwell Rockwell Rockwell International AC50 48.9 International 36.7 15.1 Piston 2 6,746 1,312.3 1,312.3 80 97 International AC80 46.8 44.5 Turboprop 2 11,199 97 International Aero Commander 500 Sabreliner 60 Turbo Commander 680 Turbo Commander 690 SD3-60 Short SH36 74.8 70.9 24.0 Turboprop 2 27,117 4,265.1 3,608.9 110 100 110 3,608.9 4,265.1 27,117 2 Turboprop 24.0 70.9 74.8 SH36 SAAB 2000 SAAB 340 C-23 Sherpa SD3-60 Short Short SC-7 Skyvan Fairchiled 300 SAAB Socata TBM-700 SAAB Short SB20 Short SF34 Swearingen 81.4 SH33 SC7 TBM SW3 70.2 74.8 89.6 TBM7 65.0 46.3 64.6 25.3 58.1 40.0 40.0 42.3 23.0 Turboprop 16.4 34.1 15.1 Turboprop 16.7 2 Turboprop Turboprop 13.8 Turboprop 2 2 46,297 2 Turboprop 2 28,440 4,265.1 1 22,597 13,669 4,265.1 4,265.1 12,566 3,608.9 110 1,968.5 3,608.9 4,265.1 6,614 3,608.9 110 2,296.6 110 4,265.1 100 2,132.5 90 115 115 1,640.4 96 120 90 85 80 E-1

APPENDIX E EMAS

The Federal Aviation Administration (FAA) requires that To estimate aEMAS, data provided by ESCO were used as standard-size runway safety areas (RSA) be provided to mini- shown next. For aRSA a maximum runway exit speed of v = 70 mize the risks associated with aircraft overruns and under- knots and a standard RSA dimension of S = 1,000 feet was 2 shoots. In some instances, however, natural or manmade obsta- employed in Eq. 1, resulting in aRSA = 2.156 m/s . cles, local developments, surface conditions, or environmental The data included the necessary lengths and estimated air- constraints make it difficult or impossible to comply with the craft performance in terms of the maximum runway exit speed. FAA standards. The study includes values for a spectrum of aircraft models and As part of the study described in ACRP Report 3, historical maximum takeoff weights (MTOW). Table E1 lists the aircraft records of accidents and incidents were compiled and used to manufacturers, models, and MTOW that are included in the develop risk models for overrun and undershoot events. How- ESCO data. Table E2 shows the data provided by ESCO. ever, the study did not address the evaluation of RSAs when The maximum runway exit speed for all aircrafts models EMAS is used. The models used in the approach developed in was combined in a single dataset and employed in a regression this study are based on data provided by ESCO. analysis to generate the model for the maximum runway exit To evaluate the risk mitigation provided by EMAS, it is nec- speed (v) in terms of the EMAS length and aircraft MTOW. essary to normalize the EMAS distance to an equivalent con- A total of 84 data points were included in the regression. A ventional RSA distance so that the value can be used directly logarithmic transformation was performed on the EMAS in the location probability models for landing and takeoff length and the aircraft weight before performing the analy- overruns. No adjustments are necessary to the distances en- sis. The resulting regression equation is listed next, where W tered into the location models for landing undershoots. is the MTOW of the aircraft in kg and S the EMAS bed length To accomplish this, the length of the conventional RSA is in meters. modified by a runway length factor (RLF), which is calculated by taking into account the effectiveness of the EMAS in de- vWS=−3. 0057 6 . 8329 log( )+ 31 . 1482 log( ) [Eq. 3] celerating a specific type of aircraft. In other words, the length The R-squared of the linear regression was 0.89, and the of the conventional RSA is increased to provide an equivalent standard error was equal to 2.91m/s. Figure E2 shows the re- distance where the aircraft can stop when entering the EMAS bed at a certain speed. Figure E1 shows the schematics of an lationship between the reported ESCO maximum runway exit RSA with EMAS and its equivalent conventional RSA. speeds and the predicted speed values obtained using Eq. 3. The relationship between the aircraft deceleration, a, the The 45-degree angle dashed line represents the equality line aircraft speed when entering the RSA, v, and the RSA length, between the values. S, is as follows: The maximum runway exit speed estimated using the regres- sion equation (Eq. 3), along with the EMAS bed length (SEMAS), v 2 was input in Eq. 1 to estimate the deceleration of the RSA with a = [Eq. 1] 2S EMAS bed (aEMAS). The runway length factor was then esti- mated as follows: In addition, since the speed of the aircraft entering the RSA is assumed to be the same for the same aircraft entering the aEMAS RLF = [Eq. 4] equivalent conventional RSA, it is established that: aRSA

= 2 aSEMAS EMAS aS RSA RSA [Eq. 2] where aRSA is 2.156 m/s as explained before. E-2

x1

Regular Terrain x1

Regular RSA-EQ

L Terrain

RLF·x2 RSA-EMAS L

EMAS x2

a) b) Figure E1. Schematic of a) RSA with EMAS and b) equivalent conventional RSA.

Table E1. Aircraft models included in ESCO data.

Aircraft Manufacturer Aircraft Model MTOW (×103 lb) Airbus A-319 (B737) 141.0 A-320 (B737) 162.0 A-340 567.0 Boeing B-737-400 150.0 B-747 870.0 B-757 255.0 B-767 407.0 B-777 580.0 Cessna CITATION 560 16.3 Canadair CRJ-200 53.0 CRJ-700 75.0 Embraer EMB-120 28.0 ERJ-190 (ERJ170) 51.0 McDonnell Douglas MD-83 (MD 82) 160.0 E-3

Table E2. Data provided by ESCO. 50 45 Speed EMAS Speed Aircraft Weight (lb) (knots) (feet) (m/s) 40 A319(B737) 141,000 80 550 41.2 35 A319(B737) 141,000 79 350 40.6 30 A319(B737) 141,000 40 120 20.6 A320(B737) 162,000 80 550 41.2 25 A320(B737) 162,000 75 350 38.6 20 A320(B737) 162,000 37 120 19.0 15 A340 567,000 70 550 36.0 A340 567,000 50 350 25.7 10 A340 567,000 28 120 14.4 5 B747 870,000 66 550 34.0 B747 870,000 47 350 24.2 0

B747 870,000 29 120 14.9 Predicted max speed entering EMAS bed (m/s) 0 1020304050 B757 255,000 80 550 41.2 Reported max speed entering EMAS bed (m/s) B757 255,000 58 350 29.8 B757 255,000 31 120 15.9 Figure E2. Relationship between reported and B767 407,000 75 550 38.6 predicted maximum aircraft speeds entering the B767 407,000 54 350 27.8 EMAS bed. B767 407,000 30 120 15.4 B777 580,000 70 550 36.0 B777 580,000 50 350 25.7 B777 580,000 29 120 14.9 Subsequently, based on the relationship established in Eq. 2, CITATION 560 16,300 80 550 41.2 RLF was multiplied by the length of the EMAS bed to estimate CITATION 560 16,300 77 350 39.6 the equivalent length of the conventional RSA: CITATION 560 16,300 48 120 24.7 CRJ 200 53,000 80 550 41.2 aEMAS g CRJ 200 53,000 80 350 41.2 SRSA ==SRLFSEMAS EMAS [Eq. 5] CRJ 200 53,000 45 120 23.1 aRSA CRJ 700 75,000 80 550 41.2 CRJ 700 75,000 77 350 39.6 Note that, depending on the RSA configuration and the type CRJ 700 75,000 41 120 21.1 of aircraft, different operations will generate different RLFs. EMB 120(SAAB340) 28,000 75 550 38.6 EMB 120(SAAB340) 28,000 70 350 36.0 EMB 120(SAAB340) 28,000 41 120 21.1 ERJ 190(ERJ170) 51,800 80 550 41.2 ERJ 190(ERJ170) 51,800 65 350 33.4 ERJ 190(ERJ170) 51,800 37 120 19.0 MD 83(MD 82) 160,000 80 550 41.2 MD 83(MD 82) 160,000 70 350 36.0 MD 83(MD 82) 160,000 35 120 18.0 F-1

APPENDIX F Risk Criteria Used by the FAA

Although the main objective of this research was to de- determining severity. Table F1 provides the FAA specific def- velop a tool to help airport planners evaluate RSA alterna- initions of severity. tives, the basis for the analysis was a quantitative assessment Likelihood is an expression of how often an event can be ex- of risk associated with runway excursions and undershoots. pected to occur at the worst credible severity. Table F2 shows Risk is the composite of the likelihood of the occurrence FAA likelihood definitions. A risk classification (high, medium, and severity of the outcome or effect (harm) of the hazard. or low) is provided based on the FAA risk matrix shown in Severity is the measure of how bad the results of an event are Figure F1 and the likelihood and severity scenario for each predicted to be. Likelihood should be considered only after hazard.

Table F1. FAA severity definitions (FAA 2010).

Hazard Severity Classification

Minimal Minor Major Hazardous Catastrophic 5 4 3 2 1 No damage to - Minimal damage - Major damager to - Severe damage to - Complete loss of aircraft but to aircraft; aircraft and/or aircraft and/or aircraft and/or minimal injury or - Minor injury to minor injury to serious injury to facilities or fatal discomfort of little passengers; passenger(s)/ passenger(s)/ injury in consequence to - Minimal worker(s); worker(s); passenger(s)/wor passenger(s) or unplanned airport - Major unplanned - Complete ker(s); workers operations disruption to unplanned airport - Complete limitations (i.e. airport closure; unplanned airport taxiway closure); operations; - Major unplanned closure and - Minor incident - Serious incident; operations destruction of involving the use - Deduction on the limitations (i.e. critical facilities; of airport airport's ability to runway closure); - Airport facilities emergency deal with adverse - Major airport and equipment procedures conditions damage to destroyed equipment and facilities- F-2

Table F2. FAA likelihood levels (FAA 2010).

ATC Operational General Airport Specific Per Facility3 NAS-wide4 Probability of Expected to occur Expected to occur Expected to occur occurrence per more than once per more than once per every 1-2 days operation is equal week or every week A to or greater than 2500 departures -3 -4 Frequent 1x10 (4x10 ), whichever occurs sooner Probability of Expected to occur Expected to occur Expected to occur occurrence per about once every about once every several times per operation is less month or 250,000 month month B than 1x10-3, but departures (4x10-6),

Probable equal to or greater whichever occurs than 1x10-5 sooner Probability of Expected to occur Expected to occur Expected to occur occurrence per about once every about once every 1 about once every operation is less year or 2.5 million -10 years few months C than 1x10-5 but departures (4x10-7), Remote equal to or greater whichever occurs than 1x10-7 sooner Probability of Expected to occur Expected to occur Expected to occur occurrence per once every 10-100 about once every about once every 3 operation is less years or 25 million 10-100 years years D than 1x10-7 but departures (4x10-8), Remote

Extremely equal to or greater whichever occurs than 1x10-9 sooner Probability of Expected to occur Expected to occur Expected to occur occurrence per less than every 100 less than once less than once operation is less years every 100 years every 30 years E than 1x10-9 Extremely Improbable

Note: Occurrence is defined per movement.

Figure F1. FAA risk matrix (FAA 1988, 2010). G-1

APPENDIX G Plan to Field Test Software Tool

Objective Portability The objective of this task was to test the software developed Before the release of a beta version, the software was for risk analysis of runway safety areas (RSA) developed under evaluated for portability using different computers with ACRP 4-08. The feedback obtained helped improve the final various operational systems (e.g., Windows 7, Windows software and mitigate any problems associated with its instal- XP). The objective was to search for possible conflicts with lation, operation, and analysis of results. computer operational systems and supporting software This plan describes the procedures used for testing the soft- versions. ware developed in this project. It includes the identification of volunteer stakeholders that utilized a beta version to carry out analysis with sample data provided. Installation The installation was tested on different computers to check for problems with installation of the files required Phase I to run the program and the supporting software that is During this phase, the software was evaluated during devel- required. The analysis software makes use of common opment before a final beta version was released to volunteers Microsoft Office products, including Excel and Access. for testing. The user must have such software to run the risk assess- ment analysis. Access is necessary to handle the various databases, and Excel is used to characterize the RSA’s, Software Development the type of terrain, and the existing obstacles with their and Algorithm Tests classification. During this phase the software algorithms and database management procedures were tested before a beta version Preliminary Testing was created. The research team installed the software and ran some analy- sis using the guidance material prepared. Any problems Input Data Quality Assurance (QA) detected were solved before the final beta release was provided Users may input incorrect information, use units that are not to volunteers for testing. compatible, or enter the correct information in incorrect fields. Several help features were incorporated, including the checking Phase II of values to ensure the input was within allowable ranges. The analysis software includes features to check missing During this phase, a beta version of the software was tested data and advise the user to make the necessary corrections. by volunteers. Despite the attempts to make the software tool The software will not run if there are missing data or if the as user-friendly and practical as possible, the research team values are outside normal ranges. asked the volunteers that are familiar with airport planning G-2

Table G1. List of volunteers to test analysis software.

Name Stakeholder Organization Comments Doug Mansel Airport Oakland International Chair of ACI-NA Operator Airport Operations and Technical Affairs Committee Mike Hines Airport Metropolitan MWAA Planner Operator Washington Airport Authority Don Andrews Consultant Reynolds, Smith and Airport planning Hill Tom Cornell Consultant Landrum and Brown Consultant Amiy Varma Professor University of North Chair of TRB Committee Dakota of Aircraft/ Airport Compatibility Ernie Professor University of Member of TRB Heymsfield Arkansas Committee of Aircraft/ Airport Compatibility Michael A. Government FAA - AAS-100 Engineer in the Airport Meyers Engineering Division Ken Jacobs Government FAA – APP-400 FAA Liaison for ACRP 4- 01 and the analysis methodology rationale to provide additional Assist Volunteers suggestions to improve software and to identify any software A helpdesk was established to assist volunteers, answering bugs they encountered. questions and resolving software issues, particularly with instal- To facilitate the assessment, data for a couple of airports lation. Volunteers could ask for help by phone or by e-mail. The was prepared and provided to the volunteers to run the phone number and e-mail address was included in the beta ver- analysis. sion user manual. Table G1 presents the list of eight software beta testers. The research team proposed a small number of volunteers to facil- itate obtaining meaningful feedback and to ensure the research Track Problems/Bugs and Fixes team could provide the necessary support to these volunteers The beta testers’ feedback was recorded. Bugs were fixed as during the beta testing period. soon as possible, and the updated software was distributed to the beta testers. Suggested improvements were considered and Perform Tests modifications made, as warranted, both during the beta test- ing phase and after. Beta testers installed the software and ran analyses. A user manual was provided to the testers as well. Feed- Retest back was requested through a basic questionnaire that so- licited comments on the use of the software, practicality, After all bugs were fixed and improvements made, another documentation, etc. round of internal tests to fix any new bugs was carried out. G-3

ACRP 4-08—Improved Models for Risk Assessment of Runway Safety Areas (RSA) Analysis Software Evaluation Questionnaire The purpose of this software beta testing effort is to test and help improve the software for analysis of runway safety areas. Although measuring software effectiveness is no easy task, the feedback provided will help identify the need for critical improve- ments to the software.

Name:______Organization: ______Position: ______

1. How easy was it to install the software? a. Difficult to install b. I had problems c. About right d. Easy to install

Comments: ______

2. How easy was it to follow the user guide and documentation? a. Very difficult to follow b. It is necessary to understand risk assessment to use it c. Simple guidance but satisfactory for the purpose d. Easy to follow

Comments: ______

3. Are the screens user-friendly and easy to understand? a. No b. I had a few problems (see my comments) c. Easy to follow

Comments: ______

4. Was it easy to input operational data? a. No b. I had a few problems (see my comments) c. Yes G-4

Comments: ______

5. Was it easy to input weather data? a. No b. I had a few problems (see my comments) c. Yes

Comments: ______

6. Was it easy to understand output results? a. No b. I had a few problems (see my comments) c. Yes

Comments: ______

7. Please list the good and the bad points of the software. ______

8. Would you use this software again? a. Yes b. Possibly (see my comments) c. No (see my comments) ______

9. How long did it take to run the “Example 1” analysis?______minutes

10. Any other comments that you care to offer. ______H-1

APPENDIX H Summary of Results for Software/Model Tests

The research team gathered data for the analysis of eight air- Additional information on individual analyses can be pro- ports and conducted the analyses using the analysis software vided upon request. Such information includes operations developed in this study. Results obtained for each airport are data, weather data, runway characteristics including declared presented in this appendix and are compared to historical distances, files defining each of the runway safety areas for air- accident rates. This effort is intended to validate the models craft overruns, undershoots, and veer-offs, as well as output developed in Task 4 and the software developed in Task 8. files from analyses. Results are shown for each airport. H-2 H-3 H-4 H-5 H-6 H-7 H-8 H-9 I-1

APPENDIX I Software User’s Guide I-2 I-3 I-4 I-5 I-6 I-7 I-8 I-9 I-10 I-11 I-12 I-13 I-14 I-15 I-16 I-17 I-18 I-19 I-20 I-21 I-22 I-23 I-24 I-25 I-26 I-27 I-28 I-29 I-30 I-31 I-32 I-33 I-34 I-35 I-36 I-37 I-38 I-39 I-40 I-41 I-42 I-43 I-44 I-45 I-46 Abbreviations and acronyms used without definitions in TRB publications: AAAE American Association of Airport Executives AASHO American Association of State Highway Officials AASHTO American Association of State Highway and Transportation Officials ACI–NA Airports Council International–North America ACRP Airport Cooperative Research Program ADA Americans with Disabilities Act APTA American Public Transportation Association ASCE American Society of Civil Engineers ASME American Society of Mechanical Engineers ASTM American Society for Testing and Materials ATA Air Transport Association ATA American Trucking Associations CTAA Community Transportation Association of America CTBSSP Commercial Truck and Bus Safety Synthesis Program DHS Department of Homeland Security DOE Department of Energy EPA Environmental Protection Agency FAA Federal Aviation Administration FHWA Federal Highway Administration FMCSA Federal Motor Carrier Safety Administration FRA Federal Railroad Administration FTA Federal Transit Administration HMCRP Hazardous Materials Cooperative Research Program IEEE Institute of Electrical and Electronics Engineers ISTEA Intermodal Surface Transportation Efficiency Act of 1991 ITE Institute of Transportation Engineers NASA National Aeronautics and Space Administration NASAO National Association of State Aviation Officials NCFRP National Cooperative Freight Research Program NCHRP National Cooperative Highway Research Program NHTSA National Highway Traffic Safety Administration NTSB National Transportation Safety Board PHMSA Pipeline and Hazardous Materials Safety Administration RITA Research and Innovative Technology Administration SAE Society of Automotive Engineers SAFETEA-LU Safe, Accountable, Flexible, Efficient Transportation Equity Act: A Legacy for Users (2005) TCRP Transit Cooperative Research Program TEA-21 Transportation Equity Act for the 21st Century (1998) TRB Transportation Research Board TSA Transportation Security Administration U.S.DOT United States Department of Transportation