Velocity XL-5 near St. Cloud, FL — 2019-08-21
- Date
- 2019-08-21
- Location
- St. Cloud, FL, USA
- Aircraft
- Velocity XL-5
- Registration
- N735D
- Category
- Airplane
- Highest injury
- Serious
- Fatalities
- 0
- Phase of flight
- Initial climb
Probable cause
The pilot’s failure to properly secure the airplane electrical system’s positive/negative leads to the 24v battery, which resulted in a total loss of electrical and engine power in flight.
NTSB narrative
Shortly after takeoff, when the airplane was at an altitude of 2,000 ft, the engine and electrical system failed simultaneously. The pilot was unable to restart the engine and made a forced landing to an open field, during which the airplane flipped over and sustained substantial damage to the airframe and wings. The airplane wreckage was not located until about 4 hours and 25 minutes after the accident. The airplane’s engine was equipped with a dual electronic ignition system that required electrical power to operate. The pilot, who was also the builder, had wired the airplane’s electrical system, which was routed through a 24v battery, including the dual electronic ignition system. Postaccident examination revealed that the lugs that connected the positive and negative leads of the airplane’s electrical system to the 24v battery were not crimped properly and that the leads had separated from their lugs, which resulted in the complete loss of electrical and engine power. The airplane’s 406-MHz emergency locator transmitter (ELT) triggered on impact, and a beacon alert was sent and was received by the Air Force Rescue Coordination Center (AFRCC). The AFRCC called the pilot’s cell phone twice shortly after the accident, but the phone had been displaced during the accident sequence, and the pilot was unable to retrieve it to answer. The pilot’s daughter did not receive a call from the AFRCC even though she was listed as an emergency contact on his ELT registration form. A review of AFRCC’s response to the accident revealed that the on-duty controller attempted to locate the beacon and initially determined that the airplane was most likely airborne with an active ELT and closed out the incident. However, after several hours had passed, the controller observed the beacon alerts becoming more concentrated and contacted law enforcement, who located the airplane within 45 minutes. The AFRCC reported that they handled 38 other incidents that day and that the controller was in his first phase of training. However, they indicated that they would use this incident as a training aid for similar cases in the future.
Analysis
- Primary failure mode
- Mechanical failure
- First missed decision gate
- Proper crimping of electrical connections could have prevented the failure.
NTSB coding
Evidence available
- Photos
- 9 docket documents
Docket documents9
- PILOT/OPERATOR AIRCRAFT ACCIDENT REPORT, NTSB FORM 6120.1form
- RELEASE OF AIRCRAFT WRECKAGE, NTSB FORM 6120.15form
- STATEMENT OF PARTY REPRESENTATIVES TO NTSB INVESTIGATIONform
- NTSB ROC PILOT 2other
- NTSB ROC WITH PILOTother
- PHOTOSphotos
- CONTINENTAL AEROSPACE TECHNOLOGIES ENGINE EXAMINATION REPORTreport
- SURVIVAL FACTORS 6 - SPECIALIST'S FACTUAL REPORTreport
- NTSB WRECKAGE AND ENGINE EXAMINATION STATEMENTwreckage
Related mishaps
- BEECH F33A
2026-04-24 · Sanford, NC
- CESSNA 182T
2024-12-11 · Pearland, TX
- Raytheon Aircraft Company B200
2024-03-12 · Billings, MT
- VANS RV14
2023-09-04 · Orchard, TX
- CESSNA 210
2021-03-18 · Marianna, FL
- ZENITH CH 750
2020-09-20 · Montrose, MO