NTSB CAROL · Event
Event WPR19FA124
Aircraft involved
Probable cause & findings
The pilots' inadvertent exceedance of the airplane's critical angle of attack following an inflight collision with a bird.
Factual narrative
HISTORY OF FLIGHTOn April 29, 2019, about 1413 Pacific daylight time, a Vans Aircraft RV-6 airplane, N90LK, was substantially damaged when it was involved in an accident near La Center, Washington. The pilot and flight instructor were fatally injured. The airplane was operated as a Title 14 Code of Federal Regulations Part 91 instructional flight. According to the pilot's wife, the purpose of the flight was to conduct the pilot's flight review, and he was scheduled to meet the instructor at the airport about 1330. The instructor’s daughter reported that it was common for him to fly to Daybreak Airport (WA46), La Center, Washington, for landing and takeoff practice. About 1515, a pilot landing at WA46 saw airplane wreckage in a pond located under the final approach path to runway 31. A review of radar data at about the time of the accident and in the area of WA46 located two targets. One was determined to be the accident airplane, and the other was that of the airplane that located and reported the wreckage. The first radar return with altitude data was recorded at 1404:33 at an altitude of 1,100 ft, about 1/2-mile northeast of Grove Field (1W1), Camas, Washington. The data showed that the airplane was on a northerly heading for about 11 miles before it turned west, directly toward W46. The data showed that the airplane flew parallel to the runway at WA46 at an altitude of 2,500 ft mean sea level (msl). As shown in figure 2, the airplane completed a descending 180° left turn and entered a left downwind for runway 31, where it leveled off at an altitude of about 500 ft above ground level (agl). The final radar target was captured at 1413:42 and depicted the airplane nearly abeam the runway 31 threshold, about 500 ft agl. Figure 1. View of the last portion of radar data along with the airport location and accident site. WRECKAGE AND IMPACT INFORMATIONThe airplane came to rest in a shallow (1-2 ft) floodplain pond along the extended centerline of runway 31 and about 1,000 ft from the threshold. The airplane was upright, in an approximate 15° nose down attitude, on a heading of about 130°. All major structural components of the airplane remained attached or partially attached to the airplane. The pond contained numerous upright flagged sticks which marked planted saplings. These sticks/flags were regularly and closely (3-5 ft) spaced. Almost all sticks surrounding the airplane, including some below the upraised empennage, were undisturbed. The fuselage was fractured and buckled at both the firewall and the aft cockpit bulkhead. The engine and cowl were displaced up and to the right. The aft fuselage was also displaced to the right. The lower forward fuselage displayed significant upward crush damage direction, and the two fixed main landing gear legs and wheel assemblies were displaced aft and up. Both wings remained attached to the fuselage, but with significant leading edge crush damage in the aft direction. The flaps were found in the fully-retracted position, as was the cockpit flap handle. The left aileron was separated from the wing at its outboard end but remained attached inboard. The right aileron remained completely attached to the wing. The left wing fuel tank cap was absent, but the right wing fuel cap was present and securely installed. The horizontal and vertical stabilizers, as well as their respective balance weights and control surfaces, remained attached and undamaged. The engine was partly covered in mud, but no evidence of catastrophic mechanical failure was observed. The two-blade metal propeller remained attached to the engine. One blade was bent aft, and the other blade was essentially undamaged. Bird remains were found on the right (outboard) arm/clothing of the flight instructor. Examination of the recovered wreckage revealed that a considerable amount of dry mud/dirt covered a majority of the engine. During removal of the dirt from the engine, evidence of bird remains was found in multiple areas, including feathers embedded into the upper right engine mount attachment bolt area and surrounding the engine-driven fuel pump. Examination of the engine revealed no evidence of any preexisting mechanical malfunction. Flight control continuity was established throughout the airframe to all primary flight control surfaces. Examination of the collected bird remains was conducted by the Feather Identification Lab of the Smithsonian Institution. The remains were consistent with an adult Green-Winged Teal, a species common to the geographic region as well as the specific accident locale (flooded field). MEDICAL AND PATHOLOGICAL INFORMATIONPilot The Clark County Medical Examiner, Vancouver, Washington, performed an autopsy of the pilot. The cause of death was "multiple blunt force injuries." The Federal Aviation Administration (FAA) Forensic Sciences Laboratory conducted forensic toxicology examinations on specimens from the pilot; no carbon monoxide or ethanol were detected. Salicylate and Ibuprofen were detected in the urine. Instructor The Clark County Medical Examiner, Vancouver, Washington, performed an autopsy of the instructor. The cause of death was "multiple blunt force injuries," and that the autopsy revealed no significant natural disease. The FAA Forensic Sciences Laboratory conducted forensic toxicology examinations on specimens from the instructor; no carbon monoxide, ethanol, or tested-for drugs were detected. The pilot and flight instructor were conducting a local flight as part of a flight review. Radar data showed that the airplane departed and proceeded to a nearby airport, where it entered the traffic pattern. The last recorded radar target was located abeam the end of the runway, at an altitude of about 500 ft above ground level. There were no known witnesses to the accident sequence. The airplane came to rest upright, partially submerged within a pond, about 1,000 ft from the approach end of the runway. Wreckage and impact signatures from surrounding terrain were consistent with a near-vertical impact. Examination revealed no anomalies with the airframe or engine that would have precluded normal operation. Bird remains were found on the right (outboard) arm/clothing of the flight instructor and within the engine compartment. The remains were identified as a species common to the accident locale. It is likely that a bird strike occurred while the airplane was maneuvering in the traffic pattern for landing, resulting in a breach of the canopy/windscreen. Given the lack of mechanical anomalies and the orientation of the wreckage, it is likely that the pilots became distracted and exceeded the airplane's critical angle of attack, which resulted in an aerodynamic stall/spin and loss of control. 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).
- — Personnel issues-Task performance-Use of equip/info-Use of equip/system-Pilot
- — Aircraft-Aircraft oper/perf/capability-Performance/control parameters-Angle of attack-Capability exceeded
- — Environmental issues-Physical environment-Object/animal/substance-Animal(s)/bird(s)-Contributed to outcome
- — Personnel issues-Psychological-Attention/monitoring-Attention-Pilot
- — Personnel issues-Task performance-Use of equip/info-Aircraft control-Pilot
Verbatim from NTSB's published report. Source file
NTSB_2019_WPR19FA124.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 ↗