CHI98LA040 · Cessna 172
Cessna 172 · Accident: airframe, component or system failure en route
From Evansville Regional Airport (EVV) to Wilmington Airpark (ILN)
Event
- NTSB case
- CHI98LA040
- Event typeAccident: someone killed or seriously injured, or the aircraft substantially damaged (NTSB definition). Incident: an occurrence that affected or could have affected safety, short of that. Glossary
- Accident
- InvestigationHow far the investigation had got when the record was published: preliminary, ongoing, final or completed. Unknown where the source does not say. Glossary
- Completed
- API-reported fatalities
- 0 · all aircraft and ground
- Ground fatalities
- 0
- OperationWhat kind of flying it was, grouped by the rules it flew under: airline (US Part 121), air taxi and commuter (Part 135), general aviation (Part 91 and similar), military or government. Glossary
- General aviation
- WeatherVisual meteorological conditions (VMC): good enough to fly by looking outside. Instrument conditions (IMC): cloud or low visibility, flying by instruments. Glossary
- Visual Meteorological Cond
Cessna 172
- Aircraft type
- Cessna 172
- Category
- Airplane
- RegistrationThe aircraft's tail number, such as N12345 or G-ABCD. Registrations are reissued, so the same one years apart can be a different aircraft. Glossary
- N92042
- Operator
- Donald J. Rauch · private individual
- Onboard fatalities
- Unknown
- Route
- From Evansville Regional Airport (EVV), Evansville, INTo Wilmington Airpark (ILN), Wilmington, OH
- Aircraft age
- Not recorded
- Flight rulesThe regulations the flight operated under: in the US, Part 91 (general aviation), Part 121 (airlines), Part 135 (air taxi and commuter) and others; for flights abroad, the NTSB's coarser commercial or non-commercial code. Glossary
- Part 91: General Aviation
- Phase of flightThe stage of the flight when things started to go wrong: standing, taxi, takeoff, initial climb, en route, maneuvering, approach or landing. Glossary
- En route · cruise
- First occurrenceThe single coded event the NTSB judges best describes what happened (records from 2008 on). Older records name the first occurrence in the sequence instead. Glossary
- Airframe, component or system failure
- Also codedOther events the NTSB coded in the sequence, such as a wire strike after a loss of power. Flight Findings uses them for its kinds of event. Glossary
- Tree(s)
- DamageDestroyed: beyond practical repair. Substantial: damage that affects the structure, performance or handling and normally needs major repair. Minor: less than that. Glossary
- Substantial
Cause areas
- Pilot in command › Distance/altitude, misjudged
Approximate · Coordinates as recorded by the NTSB; no uncertainty radius is established.
NTSB narrative
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.
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.
Verbatim NTSB analysis and probable cause from the NTSB dataset
Sources
NTSB record CHI98LA040
- Event ID
- 20001208X09150
- Case number
- CHI98LA040
- Dataset
- historical-pre2008
- Source SHA-256
- 89e2df6d848e7ab3b42e7d7c7a03ff403303057a26ca04c95b3ea67201c3ce74
Source notes (4)
- Unreviewed is an editorial label, not an investigation status. API-sourced is not report-checked or human-reviewed. Explicit event totals are used without summing aircraft injury tables; onboard allocation is withheld. Unknown values remain unknown. The operation category is mapped from the NTSB-reported FAR part and has not been reviewed.
- Filled from the NTSB case API where the bulk record had no value: local date, investigation status. Values present in the bulk record are kept.
- The date is the local date; the NTSB stores the UTC date 1997-11-20.
- API snapshot SHA-256: c611db34e3134055994bc227970095d5b8bbef2459a2a2267179e39651a37705; retrieved 2026-09-21T11:44:31.691Z.