FLIGHT FINDINGSAVIATION OCCURRENCE MAP
Back to map

CHI92LA130 · Cessna 152

18 Apr 1992 · Hanover, IN, United States

Kentucky Flying Service Cessna 152 · Accident: partial loss of engine power (non-mechanical) en route

From Bowman Field (LOU) to an unrecorded destination

Report a problem

Event

NTSB case
CHI92LA130
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 152

Aircraft type
Cessna 152
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
N46034
Onboard fatalities
Unknown
Route
From Bowman Field (LOU), Louisville, KYTo not recorded
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
Partial loss of engine power (non-mechanical)
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

No findings designated as a cause are recorded in the NTSB data yet.

Approximate · Coordinates as recorded by the NTSB; no uncertainty radius is established.

NTSB narrative

THE FLIGHT INSTRUCTOR PILOT OF THE ACCIDENT AIRPLANE REPORTED A PARTIAL LOSS OF ENGINE POWER AS HE WAS GIVING INSTRUCTION IN POWER OFF AND APPROACH TO LANDING STALLS TO A DUAL STUDENT. HIS ATTEMPTS TO CORRECT THE CONDITION WERE NOT SUCCESSFUL AND HE PERFORMED A FORCED LANDING. DURING THE LANDING ROLL THE AIRPLANE NOSED DOWN IN SOFT TERRAIN. WEATHER CONDITIONS CONDUCIVE TO THE FORMATION OF CARBURETOR ICE (TEMPERATURE 74 DEGREES, DEWPOINT 60 DEGREES FAHRENHEIT) WERE PRESENT.

Probable cause

INADEQUATE REMEDIAL ACTION BY THE PILOT IN COMMAND WHEN THE ENGINE LOST PARTIAL POWER DURING CRUISE FLIGHT. FACTORS IN THE ACCIDENT WERE THE PRESENCE OF CARBURETOR ICING CONDITIONS, AND SOFT TERRAIN IN THE AREA SELECTED FOR A FORCED LANDING.

Verbatim NTSB analysis and probable cause from the NTSB dataset

Sources

NTSB record CHI92LA130
Event ID
20001211X14401
Case number
CHI92LA130
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: investigation status. Values present in the bulk record are kept.
  • The date is the local date, which is the same as the UTC date the NTSB stores.
  • API snapshot SHA-256: e4883b80a811713a3dc6ea5310c4e0c27d3cf5cb0e31fa1d1779ce794d40fec0; retrieved 2026-09-23T03:13:32.896Z.