FLIGHT FINDINGSAVIATION OCCURRENCE MAP
Back to map

ERA13FA105 · Beech H35

4 Jan 2013 · Palm Coast, FL, United States

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

From Treasure Coast International Airport (FPR) to Knoxville Downtown Island Airport (DKX)

Report a problem

Event

NTSB case
ERA13FA105
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
3 · 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 H35

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
N375B
Operator
Unknown
Onboard fatalities
Unknown
Route
From Treasure Coast International Airport (FPR), St.Lucie County, FLTo Knoxville Downtown Island Airport (DKX), Knoxville, TN
Aircraft age
About 56 years (built 1957)
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
Destroyed

Cause areas

  • Aircraft › Aircraft oper/perf/capability
  • Aircraft › Aircraft power plant

Approximate · Coordinates from the NTSB case API, not marked as estimated; no uncertainty radius is established.

NTSB narrative

The airplane departed under visual flight rules and was at an altitude of about 7,500 feet when the pilot reported vibrations and an "oil pressure problem." Airports in the area were under instrument meteorological conditions with cloud ceilings of 900 to 1,000 feet above ground level (agl). An air traffic controller provided the pilot with radar vectors for an airport surveillance radar (ASR) approach to a nearby airport that did not have a published ASR procedure. The airplane was about 2.5 miles northwest of the airport, at an altitude of about 5,300 feet agl, when the pilot reported that the engine oil pressure was "zero" with "cool cylinders." The controller did not obtain nor did the pilot provide any additional information about the engine's power status. During the next approximately 7 minutes, the airplane continued past the airport to a point about 6.5 miles northeast before the controller vectored the airplane to the south and then west to the final approach course. The airplane subsequently struck trees and a residence about 3/4 mile from the approach end of the runway. A postcrash fire destroyed the airframe and engine.

Postaccident examination of the airplane revealed that the engine sustained a fractured No. 4 connecting rod due to oil starvation. The connecting rod punctured the crankcase, which resulted in a total loss of engine power. The crankshaft oil transfer passage at the No. 4 journal sustained mechanical damage during the accident sequence and contained displaced journal material. All other oil passages were unrestricted. The airplane's maintenance logbooks were destroyed during the accident. Maintenance performed on the airplane about 1 month before the accident included the replacement of the Nos. 1 and 4 cylinders; however, it could not be determined if this maintenance played a role in the accident. The reason for the oil starvation could not be determined.

Review of the air traffic control transcripts and interviews with the controllers revealed that they vectored the airplane such that it was unable to reach the airport. This was likely due to the weather conditions and the controllers' incomplete understanding of the airplane's mechanical condition (complete loss of power), which the pilot did not provide.

At the time of the accident, the pilot was using medication for hypertension and had well-controlled diabetes. It was unlikely that either condition significantly affected the pilot's performance at the time of the accident.

Probable cause

A total loss of engine power after the failure of the No. 4 connecting rod due to oil starvation, which resulted in a subsequent forced landing. Contributing to the accident was the pilot’s failure to clearly state that the aircraft had lost all power and the air traffic controllers’ incomplete understanding of the emergency, which resulted in the controllers vectoring the airplane too far from the airport to reach the runway.

Verbatim NTSB analysis and probable cause from the NTSB dataset

Sources

NTSB record ERA13FA105
Event ID
20130104X61334
Case number
ERA13FA105
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, 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: 9cac534630f3931bce1763a8222a5a1b5ec4f394cf3f1bf7994dd0abb16c1b71; retrieved 2026-09-14T15:51:35.045Z.