Accident Velocity N51576,
ASN logo
ASN Wikibase Occurrence # 295602
 
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:Tuesday 1 July 2003
Time:11:40 LT
Type:Silhouette image of generic VELO model; specific model in this crash may look slightly different    
Velocity
Owner/operator:Private
Registration: N51576
MSN: DMO-0112
Total airframe hrs:760 hours
Engine model:Lycoming O-360-A1A
Fatalities:Fatalities: 0 / Occupants: 2
Aircraft damage: Substantial
Category:Accident
Location:Sebastian, Florida -   United States of America
Phase: Unknown
Nature:Private
Departure airport:Sebastion, FL (X26)
Destination airport:St. Petersburg-Clearwater International Airport, FL (PIE/KPIE)
Investigating agency: NTSB
Confidence Rating: Accident investigation report completed and information captured
Narrative:
The pilot stated that about 10 minutes after takeoff during cruise flight at 1,500 feet with the passenger flying the airplane, the engine briefly "shuddered", and the rpm dropped to 2,000, then to zero. He took the controls and attempted to restore engine power but was unsuccessful. He maneuvered the airplane for a forced landing in a field, and when the flight was approximately 20 feet above ground level he recognized there were drainage ditches in the field. The airplane was landed in the field, and during the landing roll the nose landing gear collapsed after traveling into a ditch. The airplane then slid into a second ditch, and came to rest approximately 158 feet from the first ditch impact location. Examination of the engine revealed the crankshaft was fractured at the No. 3 cylinder connecting rod journal; there was no evidence of lack of lubrication or fretting on the faying surfaces of the crankcase halves. Metallurgical examination of the crankshaft revealed the fracture surface was located in the aft radius of the No. 3 connecting rod journal; fatigue progression was noted to initiate from the intersection of the radius and the journal. The fracture propagated in a plane perpendicular to the journal surface from a single origin. The fatigue initiation site did not contain scoring marks or scratches. All connecting rod journals measured 2.114 inches. The No. 3 connecting rod journal superficial macro hardness was slightly below the minimum specified limit, while the core hardness was within limits. The overall aft radius was determined to be 0.152 inch, while a localized transition radius of .015 inch at the fatigue origin location was noted. The crankshaft had been to two FAA certified repair stations (FAA CRS), the first time on December 14, 1991, and the second time on August 2, 2001. Both repair stations rejected the crankshaft due to a crack in the No. 1 main bearing area. The records from the facility that inspected the crankshaft in 2001 indicate the No. 3 connecting rod journal measured 2.1193 inches at the time it was rejected; no work was performed to it. The owner reported that following the rejection in 2001, he took the crankshaft to another FAA CRS who reportedly ground two connecting rod journals and polished the crankshaft. The owner did not have a receipt or yellow tag for the work performed to the crankshaft. The engine was assembled, and had been operated 87.8 hours since being reassembled at the time of the crankshaft failure. The president of the FAA CRS that the owner of the airplane reported last worked on the crankshaft reported he did not have any records pertaining to the accident crankshaft. He also reported that he voluntarily closed his business in August 2002, to retire.

Probable Cause: The improper repair of the crankshaft by a FAA Certified Repair Station resulting in fatigue failure and subsequent total loss of engine power. A factor in the accident was the rough/uneven terrain encountered by the pilot during the landing roll in a field.

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

Sources:

NTSB MIA03LA139

Location

Revision history:

Date/timeContributorUpdates
13-Oct-2022 10:25 ASN Update Bot Added
01-Aug-2023 21:22 harro Updated

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