FLIGHT FINDINGSAVIATION OCCURRENCE MAP
Back to map

CEN24FA167 · Vertical Aviation Technologies Hummingbird 260L

29 Apr 2024 · Spring Branch, TX, United States

Vertical Aviation Technologies Hummingbird 260L · Accident en route

From Kestrel Airpark (1T7) to Kestrel Airpark (1T7)

Report a problem

Event

NTSB case
CEN24FA167
Event typeAccident: someone killed or seriously injured, or the aircraft substantially damaged (NTSB definition). Incident: an occurrence that affected or could have affected safety, short of that. Glossary
Accident
InvestigationHow far the investigation had got when the record was published: preliminary, ongoing, final or completed. Unknown where the source does not say. Glossary
Completed
API-reported fatalities
2 · all aircraft and ground
Ground fatalities
0
OperationWhat kind of flying it was, grouped by the rules it flew under: airline (US Part 121), air taxi and commuter (Part 135), general aviation (Part 91 and similar), military or government. Glossary
General aviation
WeatherVisual meteorological conditions (VMC): good enough to fly by looking outside. Instrument conditions (IMC): cloud or low visibility, flying by instruments. Glossary
Visual Meteorological Cond

Vertical Aviation Technologies Hummingbird 260L

Category
Helicopter
RegistrationThe aircraft's tail number, such as N12345 or G-ABCD. Registrations are reissued, so the same one years apart can be a different aircraft. Glossary
N829SH
Operator
Unknown
Onboard fatalities
Unknown
Route
From Kestrel Airpark (1T7), Spring Branch, TXTo Kestrel Airpark (1T7), Spring Branch, TX
Aircraft age
About 12 years (built 2012)
Flight rulesThe regulations the flight operated under: in the US, Part 91 (general aviation), Part 121 (airlines), Part 135 (air taxi and commuter) and others; for flights abroad, the NTSB's coarser commercial or non-commercial code. Glossary
Part 91: General Aviation
Phase of flightThe stage of the flight when things started to go wrong: standing, taxi, takeoff, initial climb, en route, maneuvering, approach or landing. Glossary
En route
Defining eventThe single coded event the NTSB judges best describes what happened (records from 2008 on). Older records name the first occurrence in the sequence instead. Glossary
Unknown or undetermined
DamageDestroyed: beyond practical repair. Substantial: damage that affects the structure, performance or handling and normally needs major repair. Minor: less than that. Glossary
Destroyed

Cause areas

  • Aircraft › Aircraft power plant

Approximate · Coordinates as recorded by the NTSB; no uncertainty radius is established.

NTSB narrative

The pilot departed in the experimental helicopter with a pilot-rated passenger to perform a golf ball drop for a charity event. Flight track data showed that the beginning of the flight was not captured, as the first data point indicated the helicopter was in flight and was approximately 4.3 miles to the northeast of the departure airport and about 1.8 miles to the northwest of the planned golf ball drop location. The data showed the helicopter flying to the southwest of the first data point. The helicopter continued to travel to the southwest, and it then turned to the southeast where the data terminated shortly thereafter at the accident site, which was located about 1.4 miles to the northwest of the departure airport. Multiple witnesses near the accident site heard the engine produce sputtering and coughing noises just prior to impact. Security camera footage showed the helicopter impact a grass field in a residential area, in front of a house. A postimpact explosion and fire occurred, which consumed the wreckage. While no mechanical anomalies were found during the airframe and the engine examination, the examination was limited due to the extensive fire damage present. Multiple golf balls were found in the wreckage, which is indicative that the golf ball drop was not completed. The recovered flight track data showed that the helicopter was possibly flying back to the departure airport; however, the intended flight path was not established. The pilot had previously contacted the helicopter kit manufacturer about ethanol in fuel “eating up” the fuel bladder in the helicopter and causing the fuel lines to “clog.” The kit manufacturer offered to sell the pilot a new fuel bladder to install in the helicopter, but they never heard back from the pilot. According to the FAA, ethanol in automobile fuel is not compatible with the rubber seals and other materials used in aircraft, which could cause fuel system deterioration and malfunction. The current helicopter maintenance records were not available for review, and the investigation was unable to determine what maintenance had been performed on the airframe and the engine in the several years prior to the accident. Based upon the statements of multiple witnesses, the engine likely sustained a total loss of engine power, which resulted in a forced landing and a subsequent impact with terrain. While it is possible that the cause of the loss of the engine power may have been due to the deterioration of the fuel system from the presence of ethanol in fuel, the extensive fire damage precluded examination. Due to heart disease, the pilot was at increased risk of a sudden impairing or incapacitating cardiac event, including angina, arrhythmia, or heart attack. There is no autopsy evidence that such an event occurred. However, such an event does not leave reliable autopsy evidence if it occurs immediately before death. The pilot’s toxicological results indicated use of gabapentin, which the FAA considers a “do not fly” medication. Based on the gabapentin levels measured in the pilot’s heart blood, he was possibly experiencing some effects from his use of the gabapentin; however, specific effects are uncertain and whether he may have been impaired could not be determined based on the level detected alone.

Probable cause

A total loss of engine power for undetermined reasons, which resulted in a forced landing and a subsequent impact with terrain.

Verbatim NTSB analysis and probable cause from the NTSB dataset

Sources

NTSB record CEN24FA167
Event ID
20240429194169
Case number
CEN24FA167
Dataset
full-current
Source SHA-256
5cf380f0061817c0331a6b2d8cc7e0ee3a79bea469a1001dc5c10e56f35f5ab3
Source notes (4)
  • Unreviewed is an editorial label, not an investigation status. API-sourced is not report-checked or human-reviewed. Explicit event totals are used without summing aircraft injury tables; onboard allocation is withheld. Unknown values remain unknown. The operation category is mapped from the NTSB-reported FAR part and has not been reviewed.
  • Filled from the NTSB case API where the bulk record had no value: investigation status, cause areas. Values present in the bulk record are kept.
  • The date is the local date, which is the same as the UTC date the NTSB stores.
  • API snapshot SHA-256: b5437adc1382695712146fa1b621186c390e4ac7708c26aac1813baf32b4d2aa; retrieved 2026-09-15T08:13:06.446Z.