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.
Williamstown, NJ
After takeoff, the pilot determined that the weather was worse than reported, and he returned to the departure airport. While on final approach, the airplane began to "settle," and the pilot was "slow" in his response. He added power, but the airplane struck wires and terrain prior to the approach end the runway. When asked about the performance and handling of the airplane, the pilot responded, "The airplane was fine. The engine was running perfectly. I'm not blaming anyone but me." In a subsequent conversation, the pilot added that he managed the airport, knew the wires were there, and that they were marked.
The pilot's misjudgment of distance/altitude, and his failure to maintain obstacle clearance.
On July 15, 2005, at 0530 eastern daylight time, a Grumman G-164A, N48408, was substantially damaged when it struck wires, then collided with terrain while on final approach to the Southern Cross Airport (C01), Williamstown, New Jersey. The certificated commercial pilot was not injured. Visual meteorological conditions prevailed for the local positioning flight that departed Southern Cross Airport, about 0525. No flight plan was filed for the flight conducted under 14 CFR Part 91. The pilot provided both a written statement and a telephone interview. He explained that the purpose of the flight was to check the local weather where he was contracted to spray crops. After takeoff, he determined that the weather was worse than reported, and he returned to the airport. The pilot stated that while on final approach, the airplane began to "settle," and that he was "slow" in his response. The pilot increased engine power, but the airplane struck wires and terrain prior to the approach end of runway 09. When asked about the performance and handling of the airplane, the pilot responded, "The airplane was fine. The engine was running perfectly. I'm not blaming anyone but me." In a subsequent conversation, the pilot added that he managed the airport, knew the wires were there, and that they were marked. The pilot held a commercial pilot certificate with ratings for airplane multi-engine land, single engine land, single engine sea, and instrument airplane. He also held a flight instructor certificate with a rating for airplane single engine land. The pilot was issued a Federal Aviation Administration (FAA) second-class medical certificate on March 4, 2005. He reported 17,444 hours of flight experience, approximately 2,500 hours of which were in make and model. The weather reported at Philadelphia International Airport (PHL), 16 nautical miles northwest of the airport included wind from 140 degrees at 3 knots. There were scattered clouds at 500 feet, and an overcast layer at 1,000 feet. The visibility was 5 miles in fog.