ASN Wikibase Occurrence # 152237
This information is added by users of ASN. Neither ASN nor the Flight Safety Foundation are responsible for the completeness or correctness of this information.
If you feel this information is incomplete or incorrect, you can submit corrected information.
| Date: | Friday 4 January 2013 |
| Time: | 14:19 |
| Type: |  Beechcraft H35 Bonanza |
| Owner/operator: | Private |
| Registration: | N375B |
| MSN: | D-5121 |
| Year of manufacture: | 1957 |
| Engine model: | Continental IO-470 SERIES |
| Fatalities: | Fatalities: 3 / Occupants: 3 |
| Aircraft damage: | Destroyed |
| Category: | Accident |
| Location: | East of Flagler County Airport - KXFL, Palm Coast, FL -
 United States of America
|
| Phase: | Approach |
| Nature: | Private |
| Departure airport: | St.Lucie County, FL (FPR) |
| Knoxville, TN (DKX) | |
| Investigating agency: | NTSB |
| Confidence Rating: |  Accident investigation report completed and information captured |
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.
Accident investigation:
 |
|
Sources:
NTSB
FAA register: http://registry.faa.gov/aircraftinquiry/NNum_Results.aspx?NNumbertxt=375B
Location
Revision history:
| Date/time | Contributor | Updates |
|---|---|---|
| 04-Jan-2013 19:04 | Geno | Added |
| 05-Jan-2013 00:08 | Alpine Flight | Updated [Aircraft type] |
| 21-Dec-2016 19:28 | ASN Update Bot | Updated [Time, Damage, Category, Investigating agency] |
| 28-Nov-2017 14:05 | ASN Update Bot | Updated [Other fatalities, Nature, Departure airport, Destination airport, Source, Narrative] |
Corrections or additions? ... Edit this accident description
The Aviation Safety Network is an exclusive service provided by:
Quick Links:
| ASN Home | Send Correction / Feedback |
| FSF Home | Disclaimer | Copyright |
| Contact Us | Privacy Policy |
| Press / Media |
CONNECT WITH US:
©2024 Flight Safety Foundation