NTSB CAROL · Event
Event SEA00LA174
Registry · N6BQ
FAA Aircraft Registry record.
Make / Model
LANCAIR LANCAIR 320
Year of manufacture
1998 · 2 years old at event
Engine
LYCOMING 0-320 SERIES (180 hp)
Seats / Engines
2 seats · 1 engine
Last airworthiness date
19981222
ADS-B equipped
Yes — Mode-S A7C2B5
Registrant of record
BEARD BRADLEY A
Source: FAA Aircraft Registry (releasable master file).
Aircraft involved
Probable cause & findings
The pilot's failure to take adequate remedial action upon encountering aircraft control difficulties during landing. Factors included gusty wind conditions and the pilot's failure to maintain aircraft control during landing.
Factual narrative
On August 31, 2000, approximately 1610 Pacific daylight time, a Beard Lancair 320 amateur-built experimental airplane, N6BQ, was substantially damaged in a loss of control and subsequent gear collapse during landing on runway 34 at the Bend, Oregon, municipal airport. The private pilot-in-command of the aircraft and a private pilot-rated passenger aboard the aircraft were not injured in the accident. Visual meteorological conditions, with winds from 330 degrees true at 16 knots, were reported at Roberts Field, Redmond, Oregon, at 1556. A visual flight rules (VFR) flight plan was filed for the 14 CFR 91 personal flight from Hanford, California, to Bend. The pilot stated that the flight proceeded uneventfully until the landing. He stated that after the airplane landed, "events occurred very rapidly" and that he was "not exactly certain of what took place", but stated that "the wind picked the plane back up into the air far enough that I added some power so that we would not stall." The pilot reported that the airplane "may have bounced once again", but that in any event he decided to go around at this point and added power. However, he stated, "the plane was very difficult to control and the plane was no longer over the runway, but off to the left side." The pilot stated that the airplane's propeller then struck the ground, and that the airplane then slid 50 to 100 feet and its landing gear collapsed. The pilot reported that no mechanical failure or malfunction was involved in the accident. Reported winds at Redmond, about 9 nautical miles north of the accident site, changed from out of 330 degrees at 16 knots at 1556 to out of 350 degrees at 16 knots, gusting to 23 knots, at 1656. According to the U.S. Government Airport/Facility Directory, Bend Municipal runway 34 is 5,005 feet long and 75 feet wide, and is asphalt-surfaced. The runway 34 threshold is displaced 210 feet due to a road running perpendicular to the approach end, leaving a usable landing distance of 4,795 feet. The airport is equipped with a wind cone and a landing tee, and is serviced by UNICOM. The pilot stated that after the airplane landed, 'the wind picked the plane back up into the air far enough that I added some power so that we would not stall.' The pilot reported that the airplane 'may have bounced once again', but that in any event he decided to go around at this point and added power. However, he stated, 'the plane was very difficult to control and the plane was no longer over the runway, but off to the left side.' The pilot stated that the airplane's propeller then struck the ground, and that the airplane then slid 50 to 100 feet and its landing gear collapsed. The pilot reported that no mechanical malfunction or failure was involved. Reported winds at Redmond, Oregon, about 9 nautical miles north of the accident site, changed from out of 330 degrees at 16 knots at 1556 to out of 350 degrees at 16 knots, gusting to 23 knots, at 1656. Source: NTSB Aviation Accident Database (Pre-2008 Archive) Retrieved: 2026-02-12
Verbatim from NTSB's published report. Source file
NTSB_2000_SEA00LA174.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 ↗