NTSB CAROL · Event
Event WPR18LA105
Aircraft involved
Probable cause & findings
Impact with powerlines and terrain after takeoff for reasons that could not be determined based on the available information.
Factual narrative
On March 10, 2018, about 1655 Pacific standard time, a Piper PA-28-180, N6611J, was substantially damaged when it was involved in an accident near Montague, California. The pilot and two passengers were not injured. The airplane was operated as a Title 14 Code of Federal Regulations Part 91 personal flight. The pilot reported that he was performing touch-and-go takeoffs and landings when he "took off and something wasn't right." The pilot explained that the engine did not lose power, but the airplane was not "producing lift." The pilot performed a forced landing, during which the airplane contacted power lines and subsequently impacted terrain about 1 mile east of the runway. Examination of the airplane revealed substantial damage to the wings and fuselage. Flight control continuity was established from the cockpit controls to the respective flight control surfaces. The wing flap torque tubes were consistent with the flaps being retracted at the time of impact. The propeller remained attached to the engine. Both propeller blades exhibited chordwise scoring and leading-edge gouges. The engine remained attached to the fuselage and displayed no major visible impact damage. During a test run, the engine ran smoothly and continuously at various power settings. There was no evidence of preimpact mechanical malfunctions or anomalies that would have precluded normal operation. The pilot reported that, during takeoff following a touch-and-go landing, the airplane would not climb. The pilot subsequently performed a forced landing, during which the airplane contacted power lines and terrain, resulting in substantial damage to the wings and fuselage. Following the accident, the engine was successfully run on the airframe at various power settings with no anomalies noted. Flight control continuity was established throughout the airframe, and there was no evidence of any preimpact malfunctions or anomalies that would have precluded normal operation of the airplane. Given the available information, the reason for the impact with powerlines and terrain after takeoff 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).
- C Not determined-Not determined-(general)-(general)-Unknown/Not determined
- — Aircraft-Aircraft oper/perf/capability-Performance/control parameters-Climb rate-Not attained/maintained
Verbatim from NTSB's published report. Source file
NTSB_2018_WPR18LA105.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.