Premium research interface

The modern interface for aviation safety intelligence.

Search investigations, review source evidence, monitor watched reports, and trace long-term patterns from one calm, data-first workspace.

63k+
Reports indexed
1940-2026
Coverage
Recent
Last data refresh
Featured Report

Loading…

Loading featured report…

Loading…
Open Report

Safety trends by operating rule

Track fatal and non-fatal accident patterns across Part 91, Part 135, and Part 121 operations.

Loading trend charts…

Browse the aviation graph

Move quickly by aircraft, airport, operator, and time with indexes built for research, not wandering.

Last Data Update

By Decade

By Month

Aircraft Manufacturer

More manufacturers

Airports

More airports

Operators

More operators

About

Aviation safety reports, made easier to study

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.

FAQs

NTSB Report

November 20, 1997 · Cessna 172 · N92042

Salem, IN

Overview

Report Status
Final with probable cause
Event Type
Accident
Date
November 20, 1997
Injury Outcomes
1 injury (1 serious injury)
Location
Salem, IN
Aircraft
Cessna 172
Tail Number
N92042
Operator
Donald J Rauch
Injuries
Serious
Aircraft Damage
Substantial
NTSB Number
CHI98LA040

The pilot had topped off the fuel at Evansville, Indiana, before continuing on to Wilmington, Ohio. The alternator circuit breaker popped during climb out and he reset it. After flying approximately twenty minutes, the pilot saw smoke curling from under the instrument panel. Louisville Approach gave the pilot radar vectors to Salem, Indiana. The pilot activated the runway lights, but he did not turn on the airplane's landing lights. He tried to lower the flaps, but they did not operate. He reported that he thought he was high enough, but got too low, and the airplane hit trees. The airplane came to rest about 1,000 feet east of the airport. There were indications that the airplane's left wing had impacted a tree, and the airplane had spun around. Both propeller blades had leading edge and chordwise scratching. The airplane's electrical system was examined, but the reason for the electrical malfunction was not determined.

NTSB Probable Cause

the pilot's misjudgment of distance and altitude, while on final approach to land at night. Factors relating to the accident included: an undetermined electrical malfunction, inoperative flaps, darkness, the pilot not using the landing light, and the proximity of trees to the runway.

Full Narrative

On November 19, 1997, at 2000 eastern standard time, a Cessna 172, N92042, was destroyed when it impacted the terrain while attempting to land at the Salem Municipal Airport, Salem, Indiana. The private pilot was seriously injured. The 14 CFR Part 91 flight had departed Evansville Regional Airport, Evansville, Indiana, en route to the Airborne Airpark, Wilmington, Ohio. The pilot reported that he had been experiencing an electrical problem and had diverted to Salem Municipal Airport to make a precautionary landing. Visual meteorological conditions prevailed and an IFR flight plan had been filed. The pilot reported that he was returning to Wilmington, Ohio, with the airplane after it had received its annual maintenance inspection in Wellington, Kansas. The pilot reported that the airplane had a history of electrical problems, and that the voltage regulator had been replaced as part of the annual inspection. The airplane's logbook indicated that the annual inspection had been signed off on November 19, 1997, the same day as the accident flight. The pilot reported that he had topped off the fuel at Evansville, Indiana, before continuing on to Wilmington, Ohio. He reported that the alternator circuit breaker popped during climb out and he reset it. After flying approximately twenty minutes, the pilot saw smoke curling from under the instrument panel. He reported that he was alarmed at the amount of smoke and decided to get the airplane on the ground as soon as possible. He called Louisville Approach Control and informed them about the smoke in the cockpit. Louisville Approach gave radar vectors to Salem, Indiana. The pilot activated the runway lights by keying the airplane's radio microphone five times. He decided not to turn on the landing lights. He tried to lower the flaps, but they did not work. He reported that he thought he was high enough, but got too low and hit trees. He reported that he attempted to apply full engine power after hitting the trees, but there was no response. The pilot's only other recollection of the accident was when the people were removing him from the wreckage. The wreckage was located about 1,000 feet east of the airport. The airplane's left wing indicated that it had impacted a tree and the airplane had spun around. Propeller marks were evident on nearby branches. Both propeller blades had leading edge and chordwise scratching. About 19 gallons of fuel was recovered by the salvage personnel. The airplane's electrical system was examined but the reason for the electrical malfunction was not determined. The maintenance facility which had performed the annual inspection had flown the airplane for about 4.3 hours prior to the pilot departing from Wellington, Kansas. The maintenance facility reported there were no indications of an electrical problem during the 4.3 hours of flight.

Flight

Event TypeAccident
Event Time20:00 EST
Nearest AirportSalem Municipal (0nm)
Runway28
Runway Length2500 ft
Runway Width65 ft
Flight Plan FiledIFR
Aircraft FireNo
Aircraft ExplosionNo

Aircraft

AircraftCessna 172
Tail NumberN92042
Aircraft CategoryAir
DamageSubstantial
OperatorDonald J Rauch
Operating RulePart 91
Engines1
Engine TypeReciprocating
Engine DetailsLycoming · O-360-A4M · Reciprocating · 180
Seats4

People & Injuries

Injury Summary1 injury (1 serious injury)
Fatal0
Serious1
Minor0
Uninjured0
Total1
Crew 1Age 51 · Third Class

Conditions

ConditionsVMC
LightBright Night
Wind200° @ 7 kt
Visibility10 sm
CeilingBroken clouds 25000 ft
Temperature / Dew Point48 / 36 C
Altimeter30.00 inHg
Observation Time00:56
Weather SourceWFAC

Appendix: Source Data