SEA97LA090
1997-04-13 · PLENTYWOOD, Montana, United States · None · 1 aircraft · Status: Completed
Airport PWD
Current FAA registration · N33976
- Make / Model
- TAYLORCRAFT BC12-65
- Year of manufacture
- 1941 · 56 years old at event
- Engine
- CONT MOTOR A&C65 SERIES (65 hp)
- Seats / Engines
- 2 seats · 1 engine
- Last airworthiness date
- 19560407
- ADS-B equipped
- Yes — Mode-S A3BAAA
Source: FAA Aircraft Registry (releasable master file).
Aircraft involved
Probable cause & findings
the pilot's inadequate recovery from a bounced landing and failure to maintain control of the airplane. Factors relating to the accident included: the pilot's lack of recent experience in the tailwheel aircraft, his inadequate recurrent training, and rough/uneven terrain adjacent to the landing runway.
Factual narrative
On April 13, 1997, approximately 0900 mountain daylight time, a Taylorcraft BC12-65, N33976, was substantially damaged in a bounced landing and subsequent loss of control during touch-and-go landing practice at the Plentywood, Montana airport. The private pilot, the airplane's sole occupant, was not injured. Visual meteorological conditions prevailed and no flight plan had been filed for the local 14 CFR 91 flight from Plentywood. The pilot reported that he had not flown the Taylorcraft for one year prior to the accident and had made an appointment for later that morning for a biennial flight review (BFR). He stated that immediately before the accident, he did three uneventful touch-and-go's with the president of the Big Muddy Flying Club, which owned the aircraft. The club president (who stated he was not a flight instructor) exited the aircraft after the third touch-and-go, leaving the pilot as the sole occupant. The accident occurred on the pilot's first landing attempt as the sole occupant. The pilot stated that he "did not hold the plane off long enough", hit main wheels first and added power, which had no initial effect. He stated that at about the time the engine began to regain power, the right wing stalled, dropped, and dragged the ground, turning the airplane 90 degrees to the right. The aircraft then entered a wheat stubble field adjacent to the runway, struck a furrow, and flipped over. The pilot stated that he was landing on the east-to-west turf strip at the airport (runway 26 is 2,150 feet long and 60 feet wide, according to the U.S. Government Airport/Facility Directory) and that the weather at the time of the accident was good, with a left quartering headwind, but that winds in the general time frame of the flight varied from a left quartering headwind to a left quartering tailwind. An FAA aviation safety inspector from the Helena, Montana Flight Standards District Office (FSDO), who interviewed the accident pilot by telephone, reported that the pilot "could not provide a copy of his Flight Review logbook endorsement, as there had been no BFR within the last 24 months as required by the FAR", and that the pilot "had no recollection of having a logbook endorsement for flying conventional gear aircraft." Subsequent review of copies of the pilot's logbook, which had been furnished to the NTSB investigator-in-charge (IIC) by the pilot, revealed that the pilot had received a total of 9.4 hours of dual flight instruction in tailwheel aircraft between March 1990 and February 1995, all in the BC12. However, the pilot did not furnish any evidence of a tailwheel aircraft endorsement, nor of any tailwheel aircraft pilot-in-command time logged before April 15, 1991, per the requirements of 14 CFR 61.31(g). The most recent flight logged by the pilot in a tailwheel aircraft was in a BC12 on June 14, 1995. The most recent BFR documented in the logbook copy took place on February 11, 1990. The club president, who witnessed the accident, stated that he believed the hesitation in the engine's power response was most likely attributable to engine flooding due to excessively rapid throttle application by the pilot. An inspection authorization (IA) mechanic from Culbertson, Montana, who examined the aircraft's Continental A65-8 engine after the accident, reported to the NTSB IIC during an October 22, 1997 telephone inquiry that during his engine examination, he found no evidence of mechanical problems with the engine that would account for a preimpact loss of power. According to the pilot's accident report, his total flight time was 213.5 hours, including 12.8 hours in the accident aircraft. According to the Helena FSDO inspector, all of the pilot's tailwheel aircraft time was logged in the BC12. While landing, the airplane bounced, and the pilot advanced the throttle to added power, but there was an initial hesitation in engine response. As power was regained, the right wing dropped and dragged the ground, turning the airplane to the right. The airplane then entered a wheat stubble field, struck a furrow, and flipped over. No evidence of mechanical problems was found during a postflight examination of the engine. The pilot, who had 213.5 hours total time including 12.8 hours in the accident aircraft, could not furnish evidence of a current biennial flight review or of required qualification to act as pilot-in-command of tailwheel aircraft. He had received 9.4 hours of dual flight instruction in the accident aircraft, but the most recent dual instruction with a certificated flight instructor was over two years before the accident. The president of the flying club that owned the aircraft, witnessed the accident. He stated he believed the hesitation in engine response was due to engine flooding as a result of excessively rapid throttle application by the pilot. Source: NTSB Aviation Accident Database (Pre-2008 Archive) Retrieved: 2026-02-12
Verbatim from NTSB's published report. Source file
NTSB_1997_SEA97LA090.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 (stall, loss of control). All research papers
- 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…
- 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.
- Semantic Scholar 2024 · Article (International Conference on Networking and Services) Risk Assessment of Loss of Control In-Flight Trajectories for Urban Air Mobility Safety
In Urban Air Mobility (UAM), maintaining a minimum separation between aircraft is a safety requirement, which becomes challenging amidst congested air traffic and off-nominal conditions, such as Loss …