Wirestrike Accident Beechcraft E33 Bonanza N7011N,
ASN logo
ASN Wikibase Occurrence # 139281
 
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:Sunday 16 October 2011
Time:12:56
Type:Silhouette image of generic BE33 model; specific model in this crash may look slightly different    
Beechcraft E33 Bonanza
Owner/operator:Fly Corona!
Registration: N7011N
MSN: CD-1123
Year of manufacture:1967
Total airframe hrs:5545 hours
Engine model:Continental IO-470 SERIES
Fatalities:Fatalities: 3 / Occupants: 3
Aircraft damage: Substantial
Category:Accident
Location:About 10 miles east of Barstow, CA, US -   United States of America
Phase: En route
Nature:Private
Departure airport:Las Vegas, NV (KVGT)
Destination airport:Corona, CA (KAJO)
Investigating agency: NTSB
Confidence Rating: Accident investigation report completed and information captured
Narrative:
While in cruise flight, the pilot transmitted that he was in trouble and thought the airplane had experienced a propeller failure. The air traffic controller provided the pilot with instructions to the nearest airport, which was about 21 miles away. The pilot radioed that he thought that he could make it and began a descent toward the airport. A witness near the accident site observed the airplane flying in a southwesterly direction about 500 feet above ground level. As the airplane approached a set of suspended power lines, it pitched up 15 degrees, increased altitude by 100 to 200 feet, yawed to the right, made two 360-degree rotations descending vertically, and impacted terrain, consistent with an aerodynamic stall/spin.

Postaccident examination of the engine revealed a 2-inch hole in the top of the crankcase between the Nos. 3 and 4 cylinders. The No. 1 piston connecting rod had separated from the crankshaft, bending the end cap flat with no thermal discoloration evident. Laboratory examination of the bearing insert half identified circumferential wear marks on the back side of the bearing insert. The wear marks on the backside of the intact insert, the lack of heat damage to the connecting rod journal, and the lack of heat damage to the connecting rod and end cap suggest that the bearing began to spin, which led to extrusion/ejection of half of the connecting rod bearing. Once the bearing was free, fragments of bearing material worked their way up between the piston and the cylinder wall causing damage to and embedding in the piston skirt. The increased clearances between the connecting rod end cap and connecting rod journal caused large stress amplitudes that resulted in a fatigue fracture of the connecting rod bolts.

In 1998, after 1,002 hours of operation, the engine was top overhauled. A top overhaul does not inspect or replace items inside the crankcase, such as the main bearings or connecting rod bearings. At the time of the accident, the engine had accumulated 2,601 hours. The engine manufacturer recommends that the time between overhaul be 1,500 hours or every 12 years.
Probable Cause: A loss of engine power due to the separation of a connecting rod, and the pilot's failure to maintain airplane control during a sudden maneuver to avoid power lines during the descent, which resulted in an unrecoverable aerodynamic stall and subsequent spin. Contributing to the accident was noncompliance with the manufacturer-recommended engine overhaul schedule.

Accident investigation:
cover
  
Investigating agency: NTSB
Report number: WPR12FA012
Status: Investigation completed
Duration: 1 year and 7 months
Download report: Final report

Sources:

NTSB

Location

Revision history:

Date/timeContributorUpdates
17-Oct-2011 00:18 dfix Added
17-Oct-2011 04:04 Alpine Flight Updated [Time, Aircraft type, Registration, Cn, Operator, Destination airport, Source, Narrative]
17-Oct-2011 04:41 RobertMB Updated [Aircraft type, Operator, Location, Nature, Departure airport, Destination airport, Source, Narrative]
25-Oct-2011 13:01 Geno Updated [Operator, Source, Narrative]
08-Jun-2015 08:23 Anon. Updated [Narrative]
21-Dec-2016 19:26 ASN Update Bot Updated [Time, Damage, Category, Investigating agency]
27-Nov-2017 17:20 ASN Update Bot Updated [Operator, Other fatalities, 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:

CONNECT WITH US: FSF on social media FSF Facebook FSF Twitter FSF Youtube FSF LinkedIn FSF Instagram

©2024 Flight Safety Foundation

1920 Ballenger Av, 4th Fl.
Alexandria, Virginia 22314
www.FlightSafety.org