FLIGHT FINDINGSAVIATION OCCURRENCE MAP
Back to map

NYC04LA090 · Cessna 152

21 Mar 2004 · Greenville, KY, United States

Cessna 152 · Accident: loss of engine power en route

From Bowling Green Warren County Regional Airport (BWG) to Kentucky Dam State Park Airport (M34)

Report a problem

Event

NTSB case
NYC04LA090
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
N4468V
Operator
Unknown
Onboard fatalities
Unknown
Route
From Bowling Green Warren County Regional Airport (BWG), Bowling Green, KYTo Kentucky Dam State Park Airport (M34), Gilbertsville, 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
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

  • Fluid, oil › Exhaustion
  • Fluid, oil › Loss, total

Approximate · Coordinates from the NTSB case API, which marks them as estimated or does not say; no uncertainty radius is established.

NTSB narrative

While on a solo cross-country flight, at 3,500 feet, the engine oil pressure began to drop. The engine then began to sputter, and subsequently lost all power. The pilot performed a forced landing to a field, where the left and right wings struck small trees. The airplane came to rest in thick briar brush. Examination of the engine revealed that there was no oil remaining in the engine. Oil residue was observed streaking from the engine cowling area, rearward along the surface of the main fuselage. No ruptures or leaks were observed to the engine. Both the engine oil filler cap and dipstick were secured. Prior to departing on the on the flight, the pilot added 2 quarts of oil to the engine, which gave the engine a total of 4 quarts.

Probable cause

The total loss of engine power due to a total loss of engine oil for undetermined reasons, which resulted in a forced landing and subsequent collision with trees.

Verbatim NTSB analysis and probable cause from the NTSB dataset

Sources

NTSB record NYC04LA090
Event ID
20040329X00382
Case number
NYC04LA090
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: 673d633a5cbec2e41b320bded59e69575fa36cdb2e51dd3f52cbe111b6f2a373; retrieved 2026-09-22T07:50:29.656Z.