ERA14LA052 · Beech V35
Beech V35 · Accident: loss of engine power (total) on approach
From Norfolk International Airport (ORF) to Birmingham-Shuttlesworth International Airport (BHM)
Event
- NTSB case
- ERA14LA052
- 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
Beech V35
- Aircraft type
- Beechcraft 35
- 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
- N5655D
- Operator
- Kent Ewing
- Onboard fatalities
- Unknown
- Route
- From Norfolk International Airport (ORF), Norfolk, VATo Birmingham-Shuttlesworth International Airport (BHM), Birmingham, AL
- Aircraft age
- About 46 years (built 1967)
- 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
- 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
- Aircraft › Aircraft power plant
Approximate · Coordinates as recorded by the NTSB; no uncertainty radius is established.
NTSB narrative
The pilot reported that, during approach, he heard a "loud pop" and that the engine then lost total power. The airplane was too far away to glide to the destination airport, so the pilot chose to perform a forced landing to a field, which resulted in substantial damage to the fuselage.
Subsequent teardown examination of the engine revealed evidence of oil starvation at the No. 2 connecting rod, which resulted in its separation from the crankshaft and its subsequent puncturing of a hole in the crankcase. The oil tube from the main bearing to the No. 2 connecting rod was found clear and unrestricted. At some point during the life of the engine, the interior of the rocker covers had been coated with an unapproved material. The coating material had been flaking off during operation and had been cleaned from two of six of the rocker covers. The four remaining covers still contained the coating material, but it could not be determined if the material caused the oil restriction because none of the material was found in any of the oil or oil passages. However, it is possible that any restricting material dislodged and escaped during the engine failure.
Probable cause
The failure of the No. 2 connecting rod due to oil starvation, which resulted in a total loss of engine power.
Verbatim NTSB analysis and probable cause from the NTSB dataset
Sources
NTSB record ERA14LA052
- Event ID
- 20131128X23259
- Case number
- ERA14LA052
- 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: 4fe8a8bbe9eb9a07c3d92bb6389844031f30941d06fb91f59d17238cdfd1d741; retrieved 2026-09-15T23:09:06.756Z.