NTSB CAROL · Event
Event ERA17LA007
Aircraft involved
Probable cause & findings
A partial loss of engine power for reasons that could not be determined based on the available information.
Factual narrative
On October 6, 2016, about 1700 eastern daylight time, an experimental amateur-built Flying Flea HM14/360, N83165, was substantially damaged during a forced landing after takeoff from Waterbury Airport (N41), Plymouth, Connecticut. The private pilot was seriously injured. The personal flight was conducted under the provisions of Title 14 Code of Federal Regulations Part 91. Visual meteorological conditions prevailed, and no flight plan was filed for the flight, which originated from N41, about 1630.According to witnesses, the pilot was conducting touch-and-go landings. After about 30 minutes, the engine "sputtered" multiple times and the airplane subsequently descended into trees. The pilot was hospitalized, and according to his wife, he did not recall the accident. Examination of the airplane by a Federal Aviation Administration inspector revealed that both wings separated from the fuselage. The airplane was equipped with a BMW R100 motorcycle engine. An undetermined amount of fuel was observed in the fuel tank and examination of the fuel system did not reveal any fuel contamination. An examination of the airframe did not reveal any anomalies and no further examination of the engine was performed. Witnesses reported that they observed the pilot of the experimental, amateur-built airplane performing touch-and-go landings. The airplane flew for about 30 minutes before the engine lost power, and the airplane crashed into trees. The pilot did not recall the accident. Examination of the airframe did not reveal any anomalies. Fuel was observed in the fuel tank, and an examination of the fuel system did not reveal any fuel contamination. Although the wreckage examination revealed that the loss of engine power was likely not related to fuel quantity or fuel contamination, no additional examination of the engine was performed; thus, the reason for the partial loss of engine power could not be determined. Source: NTSB Aviation Accident Database Retrieved: 2026-02-12
NTSB Findings
Hierarchical cause / factor breakdown from the FAA bulk avdata database. Each finding tagged C (Cause) or F (Factor).
- F Not determined-Not determined-(general)-(general)-Unknown/Not determined - F
Verbatim from NTSB's published report. Source file
NTSB_2016_ERA17LA007.txt.
Findings + structured fields enriched from FAA avall.mdb.
Full investigation docket on
data.ntsb.gov ↗.
Beyond the agency record
Search this event elsewhere.
Pre-filled searches into the sources where news + community discussion of aviation events lives. External sources are reported, not agency. Treat them as signal that something happened, not as fact about what happened.
Entity-clustered aviation events in the press — last 24 hr + 30-day archive.
Official agency record + docket.
Investigative docket: factual reports, photos, transcripts.
Long-running aviation incident database (Flight Safety Foundation).
Community NTSB synthesis blog — often has photos and witness reports.
Gold-standard aviation incident blog.
Aviation industry news search.
GA pilot forum — informed but rumor-prone.
GA pilot subreddit search.
Tail-number page — flight history (free tier limited).
AOPA Air Safety Institute search.
Mainstream press coverage. Recent events only.
Privacy-preserving news search.
External links open in a new tab. We don't ingest their content; we deep-link search queries.
Related research
What the literature says.
Academic papers and agency reports matching this event's aircraft type or causal vocabulary (fuel contamination). Sourced from NASA NTRS, NTSB Safety Studies, FAA CAMI, AOPA Air Safety Institute, Embry-Riddle Scholarly Commons, arXiv, and the Semantic Scholar academic graph.
Browse the full corpus — academia portal ↗