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.
Blue Earth, MN
The pilot reported that, while approaching the destination airport in night, marginal visual meteorological conditions, he turned on the pilot-controlled runway lights. He added that he began a descent to the runway without observing the runway lights or airport and encountered "ground fog" about 200 to 300 ft above ground level (agl). He further added that he continued the descent to the runway while referencing the navigational moving map and GPS altitude on his electronic flight bag (EFB) application ForeFlight. Subsequently, while in a left turn, the airplane impacted terrain about 1 nautical mile south of the runway. The left wing, firewall, and fuselage sustained substantial damage. The pilot reported that there were no preaccident mechanical malfunctions or failures with the airplane that would have precluded normal operation. He added that, while en route, he reset his airplane-installed barometric pressure altimeter to the GPS altitude indicated on his EFB, which resulted in a "300 ft. error." An automated weather observing station, about 14 nautical miles west of the accident airport, recorded visibility at 2 1/2 statute miles, light rain, mist, and an overcast cloud ceiling at 300 ft agl.
The pilot's decision to continue the night, visual flight into instrument meteorological conditions, which resulted in controlled flight into terrain while on final approach. Contributing to the accident was the pilot's improper use of an electronic flight bag.
The pilot reported that while approaching the destination airport, in night marginal visual meteorological conditions, he turned on the pilot controlled runway lights. He added that he began a descent to the runway, without observing the runway lights or airport, and encountered "ground fog" about 200 to 300 ft. above the ground. He further added that he continued the descent to the runway while referencing the navigational moving map and GPS altitude on his electronic flight bag (EFB) application ForeFlight. Subsequently, while in a left turn, the airplane impacted terrain about one nautical mile south of the runway. The left wing, firewall, and fuselage sustained substantial damage. The pilot reported that there were no preaccident mechanical malfunctions or failures with the airplane that would have precluded normal operation. He added that while enroute, he reset his airplane installed barometric pressure altimeter to the GPS altitude indicated on his EFB, which resulted in a "300 ft. error." An automated weather observing station, about 14 nautical miles west of the accident airport, recorded visibility at 2 ½ statute miles, light rain, mist, and an overcast cloud ceiling at 300 ft. above ground.