NTSB CAROL · Event
Event CEN11LA194
Registry · N46089
FAA Aircraft Registry record.
Make / Model
TAYLORCRAFT DCO-65
Engine
CONT MOTOR A&C65 SERIES (65 hp)
Seats / Engines
2 seats · 1 engine
Last airworthiness date
19581118
ADS-B equipped
Yes — Mode-S A59D2D
Registrant of record
TANSKY STANLEY SEELEY
Source: FAA Aircraft Registry (releasable master file).
Aircraft involved
Probable cause & findings
The pilot's failure to maintain adequate airspeed while maneuvering, which resulted in an aerodynamic stall.
Factual narrative
On February 15, 2011, approximately 1630 eastern standard time, a Taylorcraft DCO-65 airplane, N46089, sustained substantial damage when it impacted terrain following a loss of control while maneuvering near Americus, Indiana. The commercial pilot sustained fatal injuries and passenger sustained serious injuries. The airplane was registered to a private individual and operated by the pilot under the provisions of 14 Code of Federal Regulations Part 91 as a personal flight. Visual meteorological conditions prevailed for the flight, and a flight plan was not filed. The local flight departed the Purdue University Airport (LAF), Lafayette, Indiana, at 1608. According to a Federal Aviation Administration (FAA) inspector who interviewed the passenger, the passenger met the pilot at the airport prior to the local flight. The pilot performed a preflight walk-around inspection and added three gallons of fuel to each wing fuel tank. In addition, the pilot added an unknown amount of oil to the engine. The airplane departed the airport from runway 10 in a eastbound direction and climbed to 1,500 feet. The passenger was unsure whether 1,500 feet was mean sea level or above ground level. The pilot then flew north following a river towards a friend's lake. At some point, the flight headed back in a eastbound direction, when the pilot executed a turn (the passenger did not recall the direction of the turn) back towards the west to return to the airport. During the turn, the pilot stated, "oh my god" and the airplane nose dropped and the airplane descended straight down. The airplane impacted wooded terrain and came to rest in a nose down vertical attitude against some trees. Examination of the airplane by a FAA inspector revealed the forward fuselage was crushed, the wings were bent and buckled, and the engine was partially separated. Flight control continuity was established to all flight control surfaces. Several cuts, consistent with the airplane propeller, were noted on an adjacent tree. There was no evidence of mechanical malfunction or failure with the engine or airframe. A portable global positioning system (GPS) unit was located in the airplane and forwarded to the NTSB vehicle recorders laboratory for data extraction. The data extraction determined the unit was not powered during the accident flight. The airplane's most recent annual inspection was completed in October 2010, at a total airframe time of approximately 1,100 hours. The pilot's family reported the pilot had accumulated approximately 500 hours total flight time, and the airplane owner reported the pilot had approximately 30 hours in the accident airplane. The pilot succumbed to the injuries he sustained during the accident on February 26, 2011. An autopsy and toxicological tests were not performed. Prior to the local flight, the pilot performed a preflight inspection and fueled the airplane with three gallons in each wing fuel tank. The passenger reported that the takeoff and flight were normal. During the return flight to the departure airport, the airplane stalled and descended into wooded terrain resulting in substantial damage. The airplane impacted several trees and came to rest in a nose down vertical attitude. Postaccident examination of the airplane revealed the forward fuselage was crushed, the wings were bent and buckled, and the engine was partially separated. Flight control continuity was established to all flight control surfaces. There was no evidence of mechanical malfunction or failure with the engine or airframe. 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 Aircraft-Aircraft oper/perf/capability-Performance/control parameters-Airspeed-Not attained/maintained - C
- C Personnel issues-Task performance-Use of equip/info-Aircraft control-Pilot - C
Verbatim from NTSB's published report. Source file
NTSB_2011_CEN11LA194.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 (stall, loss of control). Sourced from NASA NTRS, NTSB Safety Studies, FAA CAMI, AOPA Air Safety Institute, Embry-Riddle Scholarly Commons, arXiv, and the Semantic Scholar academic graph.
- Semantic Scholar 2016 · Article (Interacción)
Trajectory Recovery System: Angle of Attack Guidance for Inflight Loss of Control
This paper describes the design and development of an ecological display to aid pilots in the recovery of an In-Flight Loss of Control event due to a Stall (ILOC-S).
- NTSB Aircraft Accident Reports 2010 · Accident report
Loss of Control on Approach — Colgan Air Flight 3407
Colgan Air 3407 / Continental Connection (Q400) Buffalo NY, February 12, 2009 — 50 fatalities. Definitive investigation of the Colgan 3407 stall-stick-pusher crash on approach to Buffalo.
- NASA NTRS 2026 · Conference Paper
Computational Analysis of Steady State Aerodynamics of Transonic Truss-Braced Wing Configuration in Deep Stall
This study presents a computational investigation of steady state aerodynamics of the Subsonic Ultra-Green Aircraft Research (SUGAR) Transonic Truss-Braced Wing (TTBW) configuration over a wide range …
- 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…
- arXiv 2025 · arXiv preprint
Quadratic Programming Approach to Flight Envelope Protection Using Control Barrier Functions
Ensuring the safe operation of aerospace systems within their prescribed flight envelope is a fundamental requirement for modern flight control systems.
- SKYbrary (Eurocontrol) 2024 · SKYbrary article
Loss of Control In-Flight (LOC-I) — SKYbrary Knowledge Base
SKYbrary comprehensive knowledge-base entry on Loss of Control In-Flight — definitions, contributing factors, accident case studies (Air France 447, Colgan 3407), and prevention strategies.
Browse the full corpus — academia portal ↗