Accident Velocity 173 RG N415MK,
ASN logo
ASN Wikibase Occurrence # 22559
 
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 22 August 2008
Time:06:28
Type:Silhouette image of generic VELO model; specific model in this crash may look slightly different    
Velocity 173 RG
Owner/operator:Private
Registration: N415MK
MSN: DM0253
Total airframe hrs:5 hours
Engine model:Lycoming IO-360-C1C
Fatalities:Fatalities: 1 / Occupants: 1
Other fatalities:2
Aircraft damage: Destroyed
Category:Accident
Location:Las Vegas, NV. -   United States of America
Phase: Take off
Nature:Private
Departure airport:Las Vegas, NV (VGT)
Destination airport:Las Vegas, NV (VGT)
Investigating agency: NTSB
Confidence Rating: Accident investigation report completed and information captured
Narrative:
Shortly after takeoff from the airport, local air traffic controllers noted that the experimental amateur-built airplane was flying lower than expected, and not gaining altitude. The airplane reached a maximum altitude of about 300 feet above the ground and continued for approximately 30 seconds before descending into a residential area and impacting an occupied residence.

The accident flight was the first time the pilot had flown the airplane, and the first time the airplane took off from this particular airport. The airplane had been flown by the owner/builder for about five hours prior to the accident, and at a different airport in the area. Following the first five hours of flight, the owner/builder decided to disassemble the wings of the airplane and tow it to the accident airport because he noticed that the airplane's ground roll during the initial test flights was longer than he expected, and that oil was observed leaking from the engine cowling. The airplane was not flown again until the accident flight, and after the leaking had been corrected.

Prior to the airplane conducting any flights, it received a special airworthiness certificate as an experimental amateur-built airplane by a Federal Aviation Administration (FAA) designated airworthiness representative (DAR).

The purpose of the accident flight was to test the airplane's performance with engine boost from a noncertified, belt-driven supercharger that is normally used in automotive applications. (The supercharger had been installed by the owner/builder prior to the airplane’s certification review by the DAR; however, the accident flight was the first flight in which the supercharger control would be fully activated). The pilot had been assisting the owner/builder throughout the certification and flight testing processes.

Postaccident examination did not reveal any preimpact anomalies with the airframe. However, the examination of the engine and accessories revealed that the supercharger belt was found lodged behind the idler pulley. No signatures consistent with rotation during the impact sequence were found during examination of the supercharger, which is indicative of the belt being detached from the supercharger. Typically, supercharger belt tension is maintained through the use of an idler pulley on a sliding adjustable plate that is secured to the supercharger housing by three bolts, designed to be secured with safety wire, in 2-inch-long adjustment slots. No safety wire was found on the bolts, and one of the bolts was observed missing. Additionally,the idler plate was in a position 1/4-inch short of the most slack belt setting (i.e. 1-3/4 inches into the 2-inch adjustment toward slack), with witness marks consistent with it being in that position at impact.

The owner/builder performed a prior flight with the supercharger set to zero boost and he reported that the airplane's performance was poor. The investigation revealed that the supercharger manufacturer, in its instructions and publications, cautioned that the engine should perform like a normally aspirated engine in the event of a belt failure, but advised that ground tests should be done with the belt removed in order to simulate a failure. The manufacturer also noted that a belt failure in flight would result in a richer than normal fuel mixture, and that the pilot should compensate by adjusting the mixture in order to maintain adequate engine power. The investigation revealed that the owner/builder did not test the engine with the supercharger belt removed, and that he also had removed the idler pulley's lips in an attempt to resolve an alignment issue with the belt.

At the time of the accident, the airplane was still flying within the “Phase 1” initial flight testing operating limitations specified by the DAR who certified the airplane as experimental amateur-built. These limitations indicated that, “after a minimum time of five (5) hours” the airplane could be flown for 25 hours of operations “while based at [the accident airport]; OR, a one time flight to the "A
Probable Cause: A partial loss of engine power during initial climb due to the detachment of the engine supercharger drive belt. The detachment resulted from the owner/builder's inadequate installation of the supercharger system and belt-tensioning adjustment.

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

Sources:

NTSB

Location

Revision history:

Date/timeContributorUpdates
22-Aug-2008 11:33 angels one five Added
23-Aug-2008 22:25 78Delta Updated
21-Dec-2016 19:14 ASN Update Bot Updated [Time, Damage, Category, Investigating agency]
21-Dec-2016 19:16 ASN Update Bot Updated [Time, Damage, Category, Investigating agency]
21-Dec-2016 19:20 ASN Update Bot Updated [Time, Damage, Category, Investigating agency]
03-Dec-2017 11:55 ASN Update Bot Updated [Cn, Operator, 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