NYC99LA207 · Cessna 152
Cessna 152 · Accident: loss of engine power en route
From Shenandoah Valley Regional Airport (SHD) to Hanover County Municipal Airport (OFP)
Narrative check · The NTSB narrative appears to contradict this record's departure or destination. Values are shown as recorded, not corrected; compare with the narrative.
Event
- NTSB case
- NYC99LA207
- 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
- N49014
- Operator
- Erik Michalski
- Onboard fatalities
- Unknown
- Route Possible conflict
- From Shenandoah Valley Regional Airport (SHD), Weyers Cave, VATo Hanover County Municipal Airport (OFP), Ashland, VA
- 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
- 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
- Fuel exhaustion
- 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, fuel › Exhaustion
- Pilot in command › In-flight planning/decision, improper
Approximate · Coordinates as recorded by the NTSB; no uncertainty radius is established.
NTSB narrative
The pilot departed for an estimated 2.5 hour cross-country flight. During the flight, the pilot calculated the airplane would have over an extra hour of fuel onboard after the total trip, and he flew an additional .75 hours. While returning to the departure airport, the airplane experienced a partial power loss, which was followed by a total loss of engine power. During the ensuing forced landing, the airplane's left wing struck a telephone pole, and the empennage contacted a fence. Examination of the wreckage revealed no fuel in the airplane's left fuel tank, and about 1/2 gallon remained in the right fuel tank. After fuel was supplied to the engine fuel lines, the engine started and performed satisfactorily. Review of the airplane's rental log, and Hobbs meter revealed the airplane had been operated for 3.4 hours. According to the Airplane Operating Manual, the airplane's total fuel capacity was 26 gallons, of which 1 1/2 gallons were unusable. Additionally, the airplane's endurance chart indicated about 3.4 hours of endurance at 75 percent power.
Probable cause
Fuel exhaustion as a result of the pilot's improper in-flight planning/decision.
Verbatim NTSB analysis and probable cause from the NTSB dataset
Sources
NTSB record NYC99LA207
- Event ID
- 20001212X19632
- Case number
- NYC99LA207
- 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: 77f1249e118ae064f303b447e68549bfc4417be619eda352f53ef30b5607ea2a; retrieved 2026-09-22T14:16:23.223Z.