ATL04LA058 · Cessna 152
Cessna 152 · Accident: loss of engine power en route
From Kinston, NC to Louisburg, NC
Event
- NTSB case
- ATL04LA058
- 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
- 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
- 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
- N93002
- Operator
- David Leahy
- Onboard fatalities
- Unknown
- Route
- From Kinston, NCTo Louisburg, NC
- 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
- Loss of engine power
- 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
- Engine assembly, crankcase › Fretted
- Fluid, oil › Starvation
- Other maintenance personnel › Maintenance, overhaul, major, inadequate
Approximate · Coordinates from the NTSB case API, which marks them as estimated or does not say; no uncertainty radius is established.
NTSB narrative
The CFI and student were completing a cross-country flight, and were six miles from the destination airport flying at 2500 feet, when the engine started to run rough for 20 to 30 seconds then quit. The CFI went through the emergency checklist but was unable to restart the engine. The CFI selected a nearby field for an emergency landing. During the landing roll, the nose wheel collided with a ditch and collapsed. Examination of the airplane revealed the nose gear collapsed, the propeller bent, and the firewall damaged. The engine teardown revealed wear and fretting on the main journals, and bearing movement that resulted in engine oil starvation to the crankshaft.. The center journal was loose and appears to have spun, cutting off the oil passage. The last engine overhaul was on January 22, 2001, and approximately 1,102.7 hours had been flown since that overhaul.
Probable cause
Other maintenance personnel's inadequate engine overhaul that resulted in engine case fretting and engine oil starvation.
Verbatim NTSB analysis and probable cause from the NTSB dataset
Sources
NTSB record ATL04LA058
- Event ID
- 20040106X00020
- Case number
- ATL04LA058
- 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, coordinates. 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: e14f10bb214c5ee6bb16d0b726696e79c5537cdcd14250c88d3d4e5e54b9e8bf; retrieved 2026-09-22T08:04:01.048Z.