Accident Beechcraft 58 Baron N472TL,
ASN logo
ASN Wikibase Occurrence # 42857
 
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:Thursday 30 October 1997
Time:17:48 LT
Type:Silhouette image of generic BE58 model; specific model in this crash may look slightly different    
Beechcraft 58 Baron
Owner/operator:Charles F. Ross
Registration: N472TL
MSN: TH1112
Year of manufacture:1980
Total airframe hrs:2750 hours
Engine model:Continental I0-520-CB
Fatalities:Fatalities: 6 / Occupants: 6
Aircraft damage: Destroyed
Category:Accident
Location:New Berlin, Sangamon County, IL -   United States of America
Phase: En route
Nature:Executive
Departure airport:Macomb, IL (KMQB)
Destination airport:
Investigating agency: NTSB
Confidence Rating: Accident investigation report completed and information captured
Narrative:
The twin-engine airplane began its instrument flight loaded about 800 pounds beyond its certificated maximum gross take off weight. Shortly after reaching its assigned altitude of 7,000 feet above mean sea level, the pilot advised the FAA controller, '...we have an engine problem.' The problem was not identified during a subsequent radio transmission. Shortly after the pilot's last radio transmission, witnesses on the ground observed the airplane in a counterclockwise flat spin. The on-scene examination revealed the left engine had suffered a mechanical failure. Continuity of the flight, engine, fuel and propeller controls was established. An oil film was found on the left engine's nacelle, inboard half of the wing, left side of the fuselage and the horizontal stabilizer and elevator. The left engine case had fractured near the number 2 cylinder. Examination of the case fracture surfaces revealed fatigue failure at its initiation point. The fatigue extended about 7 inches from its origin. Additionally, the number 2 cylinder connecting rod had separated from the crankshaft journal. Maintenance records showed the engine had a crankcase crack that was not covered by an FAA Airworthiness Directive or engine manufacturer specifications. The maintenance personnel informed the pilot about the crack. Examination of the airplane's hangar floor revealed a pool of fresh oil beneath the area where the left engine would have been positioned. Oil-based tire imprints made by the left main landing gear tire were found on the hangar floor that lead from the oil pool to the ramp outside the hangar. The pilot's logbook records showed he had received 4 hours of multi-engine flight instruction during one flight session on one day. The next day the logbook showed the pilot had received 10-hours of multi-engine instruction during 2 flight sessions. He obtained his multi-engine rating on the third day. Before these instructional entries were made there were 6 other flight instruction entries showing, 'X Country IFR.'

Probable Cause: A loss of engine power due to separation of the left engine's number 2 connecting rod as a result of fatigue failure. Also causal was the pilot's failure to maintain adequate airspeed which resulted in a stall/spin. Contributing to the accident was the pilot's operation of the aircraft with known deficiencies and exceeding the maximum gross weight of the airplane.

Accident investigation:
cover
  
Investigating agency: NTSB
Report number: CHI98FA028
Status: Investigation completed
Duration: 2 years and 7 months
Download report: Final report

Sources:

NTSB CHI98FA028
FAA register: 2. FAA: http://registry.faa.gov/aircraftinquiry/NNum_Results.aspx?omni=Home-N-Number&nNumberTxt=472TL

Location

Revision history:

Date/timeContributorUpdates
24-Oct-2008 10:30 ASN archive Added
03-Mar-2016 22:49 Dr.John Smith Updated [Time, Operator, Location, Departure airport, Source, Narrative]
21-Dec-2016 19:24 ASN Update Bot Updated [Time, Damage, Category, Investigating agency]
19-Aug-2017 12:17 Aerossurance Updated [Time, Operator, Location, Departure airport, Source]
08-Apr-2024 12:00 ASN Update Bot Updated [Time, Cn, Operator, Other fatalities, Departure airport, Source, Narrative, Category, Accident report]

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