NTSB CAROL · Event
Event CEN16FA378
Aircraft involved
Probable cause & findings
The pilot's improper control inputs during takeoff, which resulted in the exceedance of the airplane's critical angle of attack and subsequent departure stall, and loss of airplane control.
Factual narrative
HISTORY OF FLIGHTOn September 20, 2016, about 1820 central daylight time, a Piper PA-28-235 airplane, N8983W, impacted terrain near Lee's Summit, Missouri. The pilot and passenger were fatally injured, and the airplane was substantially damaged. The airplane was registered to and operated by TEKO Air, LLC, Des Moines, Iowa, as a 14 Code of Federal Regulations Part 91 personal fight. Visual meteorological conditions existed near the accident site about the time of the accident, and no flight plan had been filed. The cross-country flight originated from Ankeny Regional Airport, Des Moines, Iowa, and was en route to Lee's Summit Municipal Airport (KLXT), Lee's Summit, Missouri. A review of the airplane's radar flight track revealed that the airplane was on a southernly heading to KLXT and then made a straight-in approach to runway 18. As the airplane neared KLXT, a passenger filmed the approach section of the flight using her phone, which was found on scene. The camera captured portions of the approach to the runway. The approach appeared normal; however, during the landing flare, the airplane drifted slightly right. The camera then recorded the sound of the engine power increasing, followed immediately by the airplane touching down right of the runway centerline. The camera captured images of the control yoke, which showed the pilot manipulating it aft and turning it left. The sound was consistent with the engine at high power until the end of the recording. The National Transportation Safety Board's (NTSB) Personal Electronic Device Specialist's Factual Report is located in the docket for this accident. Several witnesses reported seeing segments of the accident flight. Additionally, several of the airport's security cameras captured portions of the flight. A review of the security camera videos and witness statements revealed that the airplane touched down on runway 18 and then lifted off in a nose-high, right-wing-low attitude. The airplane then made a steep, right climbing turn; one witness reported that the airplane reached about 200 to 300 ft above ground level. The airplane completed a 180° turn with about a 90° bank angle and then entered a rapid descent, impacted terrain in a right-wing-down, nose-low attitude, slid along the ramp, and came to rest on its right side. PERSONNEL INFORMATIONThe pilot held a private pilot certificate, which was issued on June 9, 2016, with an airplane single-engine land rating. Additionally, he held a control tower operator certificate. The pilot was issued a third-class medical certificate on Sept 29, 2015. A review of the pilot's logbook revealed that he had 92.3 total flight hours, 18.2 hours of which were accrued since the pilot certificate was issued, with the last entry dated September 14, 2016. AIRCRAFT INFORMATIONThe accident airplane was a Piper PA-28-235, which is a low-wing, single-engine airplane with fixed landing gear. It was powered by a reciprocating 235-horsepower Lycoming, six-cylinder engine that drove a fixed-pitch propeller. A review of the airplane's maintenance records revealed that the last annual inspection was conducted on December 31, 2015, at a total time of 2,780.32 hours. A review of the engine maintenance records revealed that the engine was removed, overhauled, and reinstalled on August 22, 2016, at an airframe tachometer time of 2,822.2 hours. The tachometer read 2,883.6 hours at the accident site. METEOROLOGICAL INFORMATIONAt 1853, the weather observation facility at KLXT recorded wind from 190° at 10 knots, 10 miles visibility, clear sky, temperature 90°F, dew point 73°F, and an altimeter setting of 30.04 inches of mercury. AIRPORT INFORMATIONThe accident airplane was a Piper PA-28-235, which is a low-wing, single-engine airplane with fixed landing gear. It was powered by a reciprocating 235-horsepower Lycoming, six-cylinder engine that drove a fixed-pitch propeller. A review of the airplane's maintenance records revealed that the last annual inspection was conducted on December 31, 2015, at a total time of 2,780.32 hours. A review of the engine maintenance records revealed that the engine was removed, overhauled, and reinstalled on August 22, 2016, at an airframe tachometer time of 2,822.2 hours. The tachometer read 2,883.6 hours at the accident site. WRECKAGE AND IMPACT INFORMATIONThe on-site examination of the wreckage revealed that the airplane impacted terrain and an asphalt ramp just behind a building west of runway 18. Propeller cuts in the asphalt and ground scars were consistent with a right-wing-down, nose-low impact. The right wing had separated from the fuselage and was located about 92 ft from, and west of, the initial impact point. The wreckage path was 305 ft long and proceeded from the initial impact point on a heading of about 340° to the main wreckage, which consisted of the fuselage, left wing, empennage, and engine compartment. The two-bladed propeller had separated from the engine's crankshaft flange and was located about 20 ft beyond the main wreckage. About 8 inches of one propeller blade was torn off, whereas the other blade was severely distorted. There was no postcrash fire. The airplane's left wing remained with the fuselage but was only partially attached. An undetermined amount of fuel remained in the left- and right-wing fuel tanks. An area near the right wing showed evidence of a fuel spill. The main cabin floor and engine firewall were pushed back into the cabin area, and the front, right side of the fuselage had also sustained extensive damage. The top engine cowling was impact separated and was located along the wreckage path. The empennage sustained major damage to the right side of the stabilator. Left aileron continuity was established from the control surface to the bellcrank; the aileron control and balance cable were attached to the left bellcrank, aileron control wheel chain, and right bellcrank. The right aileron remained attached; however, the control rod was broken, and the bellcrank had separated, pulled through wing ribs, and was found with the fuselage. Rudder control continuity was established to the cockpit rudder pedals. The flap handle was in the retracted position; however, due to damage to the flap controls, the actual position of the flaps during landing could not be determined. The engine sustained impact damage and was examined on-site by the NTSB and a technical representative from the engine manufacturer. The engine was cut from the airframe and hung by a forklift to aid examination. The bottom set of spark plugs were removed and exhibited light-colored combustion deposits, and the electrodes exhibited normal wear signatures. The engine was rotated by hand; a thumb suction compression test was conducted, and continuity through the engine valve train and accessory section was confirmed. The left and right magnetos were removed from the engine and tested by hand; spark was observed on each terminal. The fuel pump and carburetor were examined, and no abnormalities were noted. No preimpact abnormalities were noted during the airframe or engine examinations. MEDICAL AND PATHOLOGICAL INFORMATIONThe Office of the Jackson County Medical Examiner, Kansas City, Missouri, conducted an autopsy on the pilot. The cause of death was determined to be "multiple blunt force injuries." The Federal Aviation Administration's Bioaeronautical Sciences Research Laboratory, Oklahoma City, Oklahoma, conducted toxicological testing on specimens from the pilot. The tests were negative for ethanol and tested drugs. The pilot and one passenger were on a cross-country flight in a single-engine airplane. Review of the airplane's radar flight track revealed that it was on a southerly heading to the destination airport and made a straight-in approach to runway 18. As the airplane neared the airport, a passenger filmed the approach section of the flight using her phone. A review of the footage showed that the approach appeared normal; however, during the landing flare, the airplane drifted slightly right. The camera then recorded the sound of the engine power increasing, followed immediately by the airplane touching down right of the runway centerline. The engine power then increases (likely either for a touch-and-go or for a go-around) and the airplane begins to climb in a right bank. The camera also captured images of the control yoke, which showed the pilot manipulating it aft and turning it left. Several witnesses also reported seeing segments of the accident flight, and several of the airport's security cameras captured portions of the flight. A review of the videos and witness statements confirmed that the airplane touched down on the runway and then lifted off in a nose-high, right-wing-low attitude. The airplane then entered a steep right climbing turn; one witness reported that the airplane reached about 200 to 300 ft above ground level. The airplane then completed a 180° turn with about a 90° bank angle; entered a rapid descent; impacted terrain in a right-wing-down, nose-low attitude; slid along the ramp; and came to rest on its right side. An examination of the engine and airframe did not reveal any preimpact abnormalities. Based on the available information, the pilot overcontrolled the airplane during takeoff, which resulted in it exceeding its critical angle of attack that led to an aerodynamic stall and loss of airplane 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).
- C Personnel issues-Action/decision-Action-Incorrect action selection-Pilot - C
- C Personnel issues-Task performance-Use of equip/info-Aircraft control-Pilot - C
- C Aircraft-Aircraft oper/perf/capability-Performance/control parameters-Angle of attack-Not attained/maintained - C
- — Personnel issues-Experience/knowledge-Experience/qualifications-Total experience in position-Pilot
Verbatim from NTSB's published report. Source file
NTSB_2016_CEN16FA378.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, go-around, maintenance). Sourced from NASA NTRS, NTSB Safety Studies, FAA CAMI, AOPA Air Safety Institute, Embry-Riddle Scholarly Commons, arXiv, and the Semantic Scholar academic graph.
- Embry-Riddle Scholarly Commons 2023 · Conference paper
The Value of Strong Partnerships to Build a Successful Aviation Maintenance Career Pathway Program for Transitioning Military Service Members
The aerospace industry is competing with other industries for a qualified workforce, and many of those competing industries are investing heavily in creating workforce development pipelines.
- 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…
- 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 …
- 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.
- Flight Safety Foundation 2024 · FSF / AeroSafety World
Go-Around Safety Forum Findings
Foundation Go-Around Safety Forum technical findings — examines why pilots fail to execute go-arounds when criteria are met (stabilized approach gate not met, energy state out of envelope, traffic con…
Browse the full corpus — academia portal ↗