NTSB CAROL · Event
Event CHI98LA040
Aircraft involved
Probable cause & findings
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.
Factual 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. 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. Source: NTSB Aviation Accident Database (Pre-2008 Archive) Retrieved: 2026-02-12
Verbatim from NTSB's published report. Source file
NTSB_1997_CHI98LA040.txt.
Findings + structured fields enriched from FAA avall.mdb.
Full investigation docket on
data.ntsb.gov ↗.
Beyond the agency record
Search this event elsewhere.
Pre-filled searches into the sources where news + community discussion of aviation events lives. External sources are reported, not agency. Treat them as signal that something happened, not as fact about what happened.
Entity-clustered aviation events in the press — last 24 hr + 30-day archive.
Official agency record + docket.
Investigative docket: factual reports, photos, transcripts.
Long-running aviation incident database (Flight Safety Foundation).
Community NTSB synthesis blog — often has photos and witness reports.
Gold-standard aviation incident blog.
Aviation industry news search.
GA pilot forum — informed but rumor-prone.
GA pilot subreddit search.
Tail-number page — flight history (free tier limited).
AOPA Air Safety Institute search.
Mainstream press coverage. Recent events only.
Privacy-preserving news search.
External links open in a new tab. We don't ingest their content; we deep-link search queries.
Related research
What the literature says.
Academic papers and agency reports matching this event's aircraft type or causal vocabulary (maintenance). Sourced from NASA NTRS, NTSB Safety Studies, FAA CAMI, AOPA Air Safety Institute, Embry-Riddle Scholarly Commons, arXiv, and the Semantic Scholar academic graph.
- NASA NTRS 2019 · Conference Paper
Crash Testing and Simulation of a Cessna 172 Aircraft: Pitch Down Impact Onto Soft Soil
During the summer of 2015, NASA Langley Research Center conducted three full-scale crash tests of Cessna 172 (C-172) aircraft at the NASA Langley Landing and Impact Research (LandIR) Facility.
- NASA NTRS 2019 · Technical Memorandum (TM)
Simulating the Impact Response of Three Full-Scale Crash Tests of Cessna 172 Aircraft
During the summer of 2015, a series of three full-scale crash tests were performed at the Landing and Impact Research Facility located at NASA Langley Research Center of Cessna 172 aircraft.
- Embry-Riddle Scholarly Commons 2026 · Journal article (IJAAA)
From Reactive to Predictive: A hybrid Trust-Mediated Adoption Framework for Data-Driven Maintenance in Distributed-Authority Aviation Environments
Modern aviation maintenance operates within increasingly data-intensive technological environments, yet the operational integration of predictive maintenance into routine decision-making remains incon…
- Semantic Scholar 2025 · Article (Applied Sciences)
Decision-Making Framework for Aviation Safety in Predictive Maintenance Strategies
The implementation of predictive maintenance (PM) in aviation presents unique challenges due to strict safety requirements, complex operational environments, and regulatory constraints.
- Embry-Riddle Scholarly Commons 2024 · Journal article (JAAER)
Low-Resource Automatic Speech Recognition Domain Adaptation – A Case-Study in Aviation Maintenance
With timeliness and efficiency being critical in the aviation maintenance industry, the need has been growing for smart technological solutions that optimize and streamline the different underlying ta…
- Embry-Riddle Scholarly Commons 2024 · Journal article (JAAER)
A New Trajectory in UAV Safety: Leveraging Reinforcement Learning for Distance Maintenance Under Wind Variations
In the field of aviation, safety is a critical cornerstone, and the operation of Unmanned Aerial Vehicle (UAV) systems is deeply connected with this principle.
Browse the full corpus — academia portal ↗