ASN logo
ASN Wikibase Occurrence # 228401
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.

Time:08:52 LT
Type:Silhouette image of generic VELO model; specific model in this crash may look slightly different
Velocity XL-RG-5
Owner/operator:Net Trek Inc
Registration: N735D
MSN: 3RX180
Fatalities:Fatalities: 0 / Occupants: 2
Aircraft damage: Substantial
Location:St Cloud, near Lake Tohopekaliga, FL -   United States of America
Phase: Landing
Departure airport:Kissimmee Municipal Airport, FL (ISM/KISM)
Destination airport:Sebastian, FL (X26)
Investigating agency: NTSB
Confidence Rating: Accident investigation report completed and information captured
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.

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.


FAA register:


Accident investigation:
Investigating agency: NTSB
Status: Investigation completed
Download report: Final report

Revision history:

21-Aug-2019 18:59 Geno Added
21-Aug-2019 19:21 RobertMB Updated [Source]
21-Aug-2019 19:27 RobertMB Updated [Total fatalities, Location, Nature, Departure airport, Source, Narrative]
27-Mar-2021 08:19 ASN Update Bot Updated [Time, Other fatalities, Destination 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 Facebook FSF Twitter FSF Youtube FSF LinkedIn FSF Instagram

©2022 Flight Safety Foundation

701 N. Fairfax St., Ste. 250
Alexandria, Virginia 22314