NTSB CAROL · Event
Event ERA12LA034
Aircraft involved
Probable cause & findings
A total loss of engine power for undetermined reasons.
Factual narrative
On October 17, 2011, about 1115 eastern daylight time, a Diamond Aircraft Industries DA 20-C1, N828MA, was substantially damaged following a loss of engine power and collision with trees near Newnan, Georgia (CCO). The student pilot sustained minor injuries. The airplane was registered to Daughters Five LLC and operated by Falcon Aviation Academy under the provisions of 14 Code of Federal Regulations Part 91 as a solo, instructional flight. Visual meteorological conditions prevailed and no flight plan was filed. The local flight originated at CCO about 0900. The pilot reported the following. He flew the airplane to the Auburn, Alabama area and had returned to CCO for pattern work. After a full stop on runway 14 at CCO, he commenced another takeoff. During the initial climb, about 400 feet above ground level, the engine began lost power. Attempts to restore engine power were unsuccessful. The pilot was unable to return to the runway, and a forced landing was attempted in a field. The airplane struck two trees during the forced landing attempt and remained lodged in the trees. The empennage separated during the forced landing the wings sustained "heavy damage." An inspector with the Federal Aviation Administration (FAA) responded to the accident site and examined the wreckage. The fuel tanks were approximately half full of fuel. Fuel flowed freely out of the fuel drain when manually opened. There was no evidence of fuel contamination observed. External examination of the engine revealed no evidence of damage. The wreckage was recovered to the operator's facilities where a detailed examination of the fuel system and engine was performed on October 20, 2011. The FAA provided oversight of the examination, assisted by a representative from Continental Motors, Inc. The engine was prepared for a test run on the airframe, using the aircraft electrical and fuel systems. Prior to the run, a compression test of the cylinders was performed with no anomalies noted. The engine was then started and allowed to idle for a few minutes. Engine speed was increased to 1,700 rpm and a magneto check was accomplished with a 50 rpm drop noted on each magneto. The engine was then accelerated to 2,200 rpm. The engine accelerated normally. After 10 minutes of run time, the engine was shut down using the mixture control. The engine run did not reveal anomalies that would have prevented normal operation and production of rated horsepower. After the engine run, another compression check was performed with no anomalies noted. The bottom spark plugs were removed for inspection. The electrodes were normal in wear and exhibited dark, heavy deposits when compared to a Champion Check-A-Plug chart. The engine oil filter was opened and the element was free of particulate contamination. The engine fuel screen was clean and clear. Following a solo flight to a nearby airport, the student pilot returned to the origination airport for pattern work. After one full stop landing, he attempted another takeoff. About 400 feet above the ground, the engine began to lose power. Attempts to restore power were unsuccessful, so the pilot set up for a forced landing in a field. The airplane struck trees during the landing and remained lodged in the trees, sustaining substantial damage to the airframe. A postaccident examination revealed that the fuel tanks were half-full of fuel. No evidence of fuel contamination or starvation was found. The engine was successfully test run on the airframe. The reason for the 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).
- C Not determined-Not determined-(general)-(general)-Unknown/Not determined - C
- C Aircraft-Aircraft systems-Fuel system-(general)-Failure - C
Verbatim from NTSB's published report. Source file
NTSB_2011_ERA12LA034.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 ↗