Runway excursion Accident Beechcraft G58 Baron N7122T,
ASN logo
ASN Wikibase Occurrence # 287561
 
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 20 July 2012
Time:10:45 LT
Type:Silhouette image of generic BE58 model; specific model in this crash may look slightly different    
Beechcraft G58 Baron
Owner/operator:W H Hampton Iii
Registration: N7122T
MSN: TH-2325
Year of manufacture:2011
Total airframe hrs:54 hours
Engine model:Continental IO-550
Fatalities:Fatalities: 0 / Occupants: 2
Aircraft damage: Substantial
Category:Accident
Location:Medford, Oregon -   United States of America
Phase: Landing
Nature:Private
Departure airport:Palm Springs International Airport, CA (PSP/KPSP)
Destination airport:Medford-Rogue Valley International, OR (MFR/KMFR)
Investigating agency: NTSB
Confidence Rating: Accident investigation report completed and information captured
Narrative:
The owner/pilot reported that all aspects of the personal cross-country flight were uneventful until touchdown when the airplane immediately experienced directional control issues. The airplane subsequently veered off the right side of the runway and struck a sign and a ditch before it came to rest. All three landing gear were fracture-separated from the airplane during the accident sequence.

The right and left main landing gear torque links exhibited different damage patterns. None of the attachment hardware for the left torque link knee joint was located. The lack of any landing gear operating anomalies during the accident flight's taxi, takeoff, gear retraction, and gear extension sequences, combined with the damage patterns to the left main landing gear torque links, were consistent with the knee joint attachment bolt being present through at least the beginning of the failure sequence on landing and with the bolt being at least partially installed during the landing. Further, the available evidence did not indicate that a pre-existing mechanical failure of the knee joint bolt had occurred.

For the bolt to partially back out of its proper position, the retaining nut would have to be missing either due to the cotter key being lost as a result of mechanical failure or absent because it was never installed. If the cotter key was damaged or the nut was improperly torqued, it is possible that multiple taxi, takeoff, and landing cycles could have damaged and eventually caused the cotter key, the nut, or the bolt to fail, but no evidence was found to support that scenario. The two mechanics who repaired the left main landing gear strut 7 months before the accident reported that the cotter key was installed during the repair. Although the pilot asserted that the cotter key was never installed, he and another pilot had completed 32 flights, not including the accident flight, in the airplane since that time, thus, providing 33 opportunities to detect its absence during their respective preflight inspections, yet neither did so. In addition, those flights were accomplished after renewed attention to the left main landing gear because of the strut repair; however, neither pilot noted any missing hardware. Based on the available evidence, which did not include the attachment hardware, the underlying reason for the loss of directional control could not be determined.

Probable Cause: A loss of directional control on landing for reasons that could not be determined based on the available evidence.

Accident investigation:
cover
  
Investigating agency: NTSB
Report number: WPR12LA324
Status: Investigation completed
Duration:
Download report: Final report

Sources:

NTSB WPR12LA324

Location

Revision history:

Date/timeContributorUpdates
04-Oct-2022 12:06 ASN Update Bot Added
17-Nov-2022 22:39 Ron Averes Updated [Aircraft type, 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