CEN11LA014
2010-10-11 · Fowlerville, Michigan, United States · Serious · 1 aircraft · Status: Completed
Airport 65G
N53DB has since been reassigned. It is now registered to a different aircraft (KENNY BLAISE MRV-4, built 2025), which was not involved in this event.
Aircraft involved
Probable cause & findings
The pilot's loss of control during a go-around maneuver following a bounced landing. Contributing to the accident was the pilot's limited experience in the make and model airplane.
Factual narrative
On October 11, 2010, about 1516 eastern daylight time, an amateur-built Drake Acro Sport 1 biplane, N53DB, impacted trees and terrain at the Maple Grove Airport (65G), Fowlerville, Michigan. The pilot had been conducting takeoffs and landings on runway 27 (3,050 feet by 110 feet, turf) and was attempting a go-around at the time of the accident. The pilot was seriously injured. The airplane sustained substantial damage to the wings and fuselage. The aircraft was registered to and operated by the pilot under the provisions of 14 Code of Federal Regulations Part 91. Visual meteorological conditions prevailed for the flight, which was not operated on a flight plan. The local flight departed from 65G at an undetermined time. A witness reported that the pilot had overshot the runway and executed a go-around prior to the accident. On the accident approach, the airplane touched down hard and bounced. He heard the sound of the engine increase, but not to a level consistent with takeoff power. He noted that the nose of the airplane was high. The airplane began to "waffle" and turn to the left, low over the trees. He commented that the airplane was rolling as he lost sight of it. He then heard the sound of the crash. The pilot did not have any recollection of the events leading up to the accident. The airplane impacted a wooded area south of the airport. Sections of the wings were separated from the fuselage. They were located adjacent to the fuselage. The ailerons were dislocated from the wings and were located with the wreckage. The aft fuselage was deformed. The elevators and rudders remained attached to the horizontal and vertical stabilizers, respectively. Control continuity was confirmed from the elevators and rudder to the cockpit controls. A postaccident examination of the airframe did not reveal any anomalies consistent with a preimpact failure. A detailed examination of the engine did not reveal any anomalies which would have precluded the production of full power. The airplane recording hour meter indicated 10.7 hours. The accident airplane was issued an amateur-built, experimental airworthiness certificate on April 9, 2010. Maintenance records included an entry noting the issuance of the airworthiness certificate. One additional entry, dated April 23, 2010, indicated the successful completion of the transponder and altitude reporting equipment testing. There were no subsequent entries in the maintenance records provided. A review of pilot's logbook indicated a total flight time of 695.5 hours, with 20.6 hours in tailwheel equipped aircraft. The available logbook information included 3 entries related to the accident airplane. The first was dated June 4, 2010, and noted a local flight of 0.7 hours, with 1 landing. The entry also included the comment, "Prop strike on landing." The second entry was dated October 1, 2010, and indicated a flight duration of 1.6 hours, with 1 landing. This entry included the notation, "First successful flight by R. D." The third entry was dated October 6, 2010, and indicated a flight duration of 1.1 hours, with 1 landing. This was the final entry in the available records. A logbook endorsement indicated the satisfactory completion of a flight review on May 25, 2010. Weather conditions recorded at the Livingston County Airport (OZW), located about 7 miles southeast of 65G, at 1515, included clear skies and northwest winds at 6 knots. A witness reported that during landing the airplane touched down hard and bounced. He heard the sound of the engine increase, but not to a level consistent with takeoff power. He noted that the nose of the airplane was high. The airplane appeared to become unsteady and turned to the left, low over the trees. He commented that the airplane was rolling as he lost sight of it. He then heard the sound of the crash. A postaccident examination of the airframe and engine did not reveal any anomalies consistent with a preimpact failure or malfunction. The pilot had logged 3 flights in the amateur-built airplane prior to the accident flight, with a total of 3 landings. Source: NTSB Aviation Accident Database Retrieved: 2026-02-12
NTSB Findings
FAA avdata. C = Cause, F = Factor.
- C Personnel issues-Task performance-Use of equip/info-Aircraft control-Pilot - C
- F Personnel issues-Experience/knowledge-Experience/qualifications-Total experience w/ equipment-Pilot - F
Verbatim from NTSB's published report. Source file
NTSB_2010_CEN11LA014.txt.
Findings + structured fields enriched from FAA avall.mdb.
Full investigation docket on
data.ntsb.gov ↗.
Search this event elsewhere
External sources are reported, not agency: signal that something happened, not fact about what happened.
- TallyAero Live Wire Aviation press
- NTSB CAROL Agency ↗
- NTSB Docket Agency ↗
- Aviation Safety Network Aviation press ↗
- Kathryn's Report Aviation press ↗
- Aviation Herald Aviation press ↗
- AVweb Aviation press ↗
- Pilots of America Community ↗
- Reddit /r/flying Community ↗
- FlightAware Aviation press ↗
- AOPA accident database Aviation press ↗
- Google News News ↗
- DuckDuckGo News ↗
Related research
Matched on aircraft type or causal vocabulary (loss of control, go-around, maintenance). All research papers
- NTSB Aircraft Accident Reports 2002 · Accident report Loss of Control and Impact with Pacific Ocean — Alaska 261
Alaska Airlines Flight 261 (MD-83) Pacific Ocean, January 31, 2000 — 88 fatalities. Definitive investigation of the Alaska 261 pitch-runaway-and-loss-of-control crash.
- Embry-Riddle Scholarly Commons 2026 · Journal article (IJAAA) From Reactive to Predictive: A hybrid Trust-Mediated Adoption Framework for Data-Driven Maintenance in Distributed-Authority Aviation Environments
Modern aviation maintenance operates within increasingly data-intensive technological environments, yet the operational integration of predictive maintenance into routine decision-making remains incon…
- Semantic Scholar 2026 · Article (Reliability Engineering & System Safety) Understanding human error in military aviation maintenance: The role of Performance shaping factors, cognitive workload and error orientation
- Embry-Riddle Scholarly Commons 2025 · Journal article (JAAER) A Scoping Review of Aviation Loss of Control Inflight Research
Loss of control – inflight (LOC-I) contributes to aircraft accidents at unacceptably high rates. Significant industry efforts and research have aimed to improve LOC-I prevention, detection, and recove…
- NASA NTRS 2025 · Conference Paper A Training Study to Improve Monitoring During A Go-Around
As part of an FAA program to improve go-around (GA) safety, we were asked to determine if we could improve the performance of the Pilot Monitoring (PM) during a GA maneuver.
- Semantic Scholar 2025 · Article (Applied Sciences) Decision-Making Framework for Aviation Safety in Predictive Maintenance Strategies
The implementation of predictive maintenance (PM) in aviation presents unique challenges due to strict safety requirements, complex operational environments, and regulatory constraints.