FLIGHT FINDINGSAVIATION OCCURRENCE MAP
Back to map

ERA09FA093 · Beech 36

18 Dec 2008 · Louisville, KY, United States

Beech 36 · Accident: loss of engine power (total) on approach

From Chicago Midway International Airport (MDW) to Bowman Field (LOU)

Report a problem

Event

NTSB case
ERA09FA093
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
1 · all aircraft and ground
Ground fatalities
Unknown
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
Instrument Meteorological Cond

Beech 36

Aircraft type
Beechcraft 36
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
N7472N
Operator
Unknown
Onboard fatalities
Unknown
Route
From Chicago Midway International Airport (MDW), Chicago, ILTo Bowman Field (LOU), Louisville, KY
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
Approach · IFR final approach
Defining eventThe 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
Loss of engine power (total)
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

  • Personnel issues › Action/decision
  • Personnel issues › Task performance

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

NTSB narrative

The pilot was cleared for the Area Navigation (RNAV) Global Positioning System (GPS) approach for runway 24 at his destine airport. The weather at the airport was reported as visibility, 6 statute miles; mist, overcast clouds at 800 feet. When the airplane was about 9 miles from the airport, the pilot reported an emergency; advising of an “engine failure”. A witness on the ground observed the airplane flying low over the golfing community. The witness reported the weather was cold, with little wind, cloudy, and misty at the time, and the street lights and a car dealership across the highway were the only illumination for the area that dark morning. The airplane was on an approximate course of 340 degrees and about a height of 30 feet above ground level (agl) when the right wing made contact with a tree at the beginning of the fairway, which was located between a row of residential homes and a row of tall trees. The right wing and the gear separated at the wheel well inboard section, the airplane contacted the ground inverted and came to rest 175 feet down the fairway from the initial contact point. Examination of the engine revealed the crankshaft and counterweight assembly was fractured through at the forward fillet radius of the number 2 main bearing journal. The number 2 main bearing journal exhibited scoring consistent with bearing rotation. The number 2 main bearings’ fragments were located in the oil sump. The number 3 main bearing journal was fractured at the rear fillet area. Examination of the crankcase halves, revealed the presence of silk thread patterns and gasket making material on the sealing surfaces of the main bearing bosses, which is not part of the engine’s manufacturer maintenance instructions that resulted in improper torque valves obtained during the crankcase halves assembly. The number 2 main bearing boss was severely damaged on both the left and right case halves. The damage included rotational mechanical gouging and deformation of the boss area behind the bearing, including mushrooming deformation of the boss. The engine was overhauled 58 hour before the accident. Witnesses reported the pilot mentioned having oil pressure problems with the overhaul engine prior to the accident.

Probable cause

The pilot’s continued operation of the aircraft with known deficiencies. Contributing to this accident was the improper sealing of the engine case during overhaul.

Verbatim NTSB analysis and probable cause from the NTSB dataset

Sources

NTSB record ERA09FA093
Event ID
20081218X94024
Case number
ERA09FA093
Dataset
full-current
Source SHA-256
5cf380f0061817c0331a6b2d8cc7e0ee3a79bea469a1001dc5c10e56f35f5ab3
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: 2607f65b3dc5cde4344df85d9f13e9c8e380a66ce1ec92b955fa6bbe3f0547d5; retrieved 2026-09-13T19:52:23.118Z.