Overall Trends
Total, fatal, and serious accidents in the selected range.
Search investigations, review source evidence, monitor watched reports, and trace long-term patterns from one calm, data-first workspace.
Fast key and full-text search with live filters, watches, and precise metadata.
Use quotes for exact phrase matches (for example "fuel selector valve").
Track fatal and non-fatal accident patterns across Part 91, Part 135, and Part 121 operations.
Major cases, deep-report coverage, and investigation media across decades of NTSB history.
Move quickly by aircraft, airport, operator, and time with indexes built for research, not wandering.
NTSB Reports is an independent research and search tool for public aviation accident and incident records. It brings NTSB aviation reports, structured fields, docket files, extracted figures, photos, videos, and update history into one searchable interface.
The goal is practical safety education: make it faster to find relevant investigations, compare similar events, review factual records, and understand the evidence behind probable-cause and preliminary reports.
The investigative work and source records belong to the National Transportation Safety Board and the published investigation record. This site is not affiliated with or endorsed by the NTSB.
Princeton, NJ
The pilot reported that, while landing at night, the airplane struck two deer on the runway. He added that he did not see the deer on the runway during the approach and landing. The airplane sustained substantial damage to the right horizontal stabilizer. The pilot reported that there were no preaccident mechanical failures or malfunctions with the airplane that would have precluded normal operation. The Federal Aviation Administration (FAA) Airport Facility Directory for the accident airport, stated, in part, "Deer and birds on and [in the vicinity of the airport]." The pilot stated that the airport's fencing was intermittent and that deer were frequently seen around the airport. The airport manager added that the airport's perimeter fence only covered the eastern and southern perimeter and that a deer strike occurred at least once every 2 years. However, according to the FAA Wildlife Strike Database the last reported wildlife strike at the accident airport occurred on April 10, 2012. The FAA's Part 139 CertAlert, No. 16-03, "Recommended Wildlife Exclusion Fencing," which provides airfield exclusion methods for deer and other large mammals, recommends constructing fencing "fully around the airfield without gaps."
Environmental issues-Physical environment-Object/animal/substance-Animal(s)/bird(s)-Ability to respond/compensate - C
The pilot reported that, while landing at night, the airplane struck two deer on the runway. He added that he did not see the deer on the runway during the approach and landing. The airplane substantial damage to the right horizontal stabilizer. The pilot reported that there were no preaccident mechanical failures or malfunctions with the airplane that would have precluded normal operation. The Federal Aviation Administration (FAA) Airport Facility Directory, for the accident airport, in part stated: "Deer and birds on and [in the vicinity of the airport]." The pilot stated that the airport's fencing was intermittent, and that deer were frequently seen in and around the airport. Airport Manager added that the airport's perimeter fence only covered the eastern and southern perimeter and that a deer strike occurred at least once every two years. According to the Federal Aviation Administration (FAA) Wildlife Strike Database, for the accident airport, the last reported wildlife strike occurred on April 10, 2012. The FAA maintains a comprehensive program to address wildlife hazard through a database and a reporting strike form. (For more information, see Form Approved OMB No. 2120-0045 in the public docket.) The FAA, under National Part 139 CertALert, No. 16-03, Recommended Wildlife Exclusion Fencing, provides airfield exclusion methods for deer and other large mammals. (For more information, see CertALert No. 16-03 in the public docket.)