Premium research interface

The modern interface for aviation safety intelligence.

Search investigations, review source evidence, monitor watched reports, and trace long-term patterns from one calm, data-first workspace.

63k+
Reports indexed
1940-2026
Coverage
Recent
Last data refresh
Featured Report

Loading…

Loading featured report…

Loading…
Open Report

Safety trends by operating rule

Track fatal and non-fatal accident patterns across Part 91, Part 135, and Part 121 operations.

Loading trend charts…

Browse the aviation graph

Move quickly by aircraft, airport, operator, and time with indexes built for research, not wandering.

Last Data Update

By Decade

By Month

Aircraft Manufacturer

More manufacturers

Airports

More airports

Operators

More operators

About

Aviation safety reports, made easier to study

NTSB Reports is an independent research and search tool for public aviation accident and incident records. It brings NTSB aviation reports, structured fields, docket files, extracted figures, photos, videos, and update history into one searchable interface.

The goal is practical safety education: make it faster to find relevant investigations, compare similar events, review factual records, and understand the evidence behind probable-cause and preliminary reports.

The investigative work and source records belong to the National Transportation Safety Board and the published investigation record. This site is not affiliated with or endorsed by the NTSB.

FAQs

NTSB Report

April 21, 2017 · Piper PA 22-150 160 · N9975D

Kernville, CA

Overview

Report Status
Final with probable cause
Event Type
Accident
Date
April 21, 2017
Injury Outcomes
3 injuries (3 serious injuries)
Location
Kernville, CA
Aircraft
Piper PA 22-150 160
Tail Number
N9975D
Injuries
Serious
Aircraft Damage
Substantial
NTSB Number
WPR17LA088

The airline transport pilot reported that, shortly after takeoff for a personal, local flight, during which he applied full throttle, as the airplane reached about 100 ft above ground level (agl) or less, and with usable runway behind the airplane, he noted that the engine power was decreasing, and that the airplane was not climbing as expected. Despite the pilot’s checking the controls and confirming they were in their correct positions, the airplane continued to lose altitude. He realized that the engine was not producing sufficient power to climb to or maintain 75 ft agl and added that he maintained a “high deck angle” because he was “trying to maintain lift without stalling.” He then turned toward an open clearing for an emergency landing as the airplane continued to lose altitude. During the turn, the main landing gear wheels clipped a tree right before the clearing, followed by the airplane nosing over and coming to rest inverted. The passengers reported that the airplane departed midfield with a “very high…angle of attack,” which did not fluctuate even during the stall, and that he never lowered the airplane’s nose. One of the passengers stated that the engine sounded normal and ran at full power throughout the flight. The airframe and engine examinations revealed no evidence of any preaccident mechanical malfunctions or failures that would have precluded normal operation. The damage to both propeller blades exhibited leading edge gouging, S-bending, torsional twisting and chordwise striation along the length of the blade, which is consistent with the production of engine power. Despite the pilot’s reports about an engine issue, based on the witness statements and engine examination results, the engine likely did not experience any in-flight issues. Rather the pilot’s maintaining a high pitch angle throughout the flight likely resulted in his exceedance of the airplane’s critical angle of attack and a subsequent aerodynamic stall/mush. Because the airplane’s current empty weight was not available for review, gross weight at the time of the accident was not determined. Additionally, due to the modifications that had been made to the airplane, no performance information was available to review that accurately characterized the airplane’s expected performance during the attempted takeoff.

NTSB Probable Cause

The pilot’s exceedance of the airplane's critical angle of attack, which resulted in an aerodynamic stall/mush.

Full Narrative

**This report was modified on 2/23/2022. Please refer to the public docket for this accident to view the original report.** On April 20, 2017, about 1845 Pacific daylight time, a Piper PA-22-150 airplane, N9975D, was substantially damaged when it was involved in an accident near Kern Valley Airport (L05), Kernville, California. The pilot and two passengers were seriously injured. The airplane was operated as a Title 14 Code of Federal Regulations Part 91 personal flight. The pilot reported that, shortly after takeoff, during which he applied full throttle, and when the airplane was about 100 ft above ground level (agl) or less and with the usable runway behind the airplane, he noticed that the engine power was decreasing, and that the airplane was not climbing as expected. He checked the throttle and mixture control, and both were full forward, and he checked the fuel selector, and magnetos, and both were positioned to the “both” setting, but the airplane continued to lose altitude. He realized that the engine was not producing sufficient power to climb to or maintain 75 ft agl and added that he maintained a “high deck angle” because he was” trying to maintain lift without stalling.” He then quickly turned toward an open, sandy spot for an emergency landing as the airplane continued to lose altitude. During the turn, the main landing gear wheels clipped a tree right before the small clearing, followed by the airplane nosing over inverted. The two passengers reported that the airplane departed midfield with a “very high angle of attack,” which did not fluctuate even during the stall, and that the pilot never lowered the airplane’s nose. One of the passengers stated that the engine sounded normal and ran at full power throughout the flight. A GoPro camera was recovered from the wreckage. The recording was taken from inside the airplane and began with the airplane taking off. The impact was captured at an elapsed time of about 5 minutes. The recording indicated that the engine could be heard operating until the time of impact. Views of the tachometer gage showed engine operation in the normal range. Kern Valley Airport is not equipped with a weather reporting facility. The nearest automated weather observation system was located at the Meadows Field Airport (BFL), Bakersfield, CA about 36 nm southwest of Kernville. The 1854 weather reported a temperature of 22o C, dewpoint 7oC, and an altimeter setting of 30.12 in hg. The airport elevation at Bakersfield is 509 feet msl. The density altitude at this location was calculated as 1,347 ft. The National Oceanic and Atmospheric Administration (NOAA) High-Resolution Rapid Refresh (HRRR) atmospheric model sounding near L05 at 1900 PDT on April 20, 2017, indicated that at 2,997 ft mean sea level (msl), which is the lowest reading for the sounding, density altitude was calculated as 3,996 ft msl. Kern Valley airport’s elevation is 2,614 ft. During the engine examination, the engine was found still attached to the airframe via the engine mount. The carburetor had separated from the mounting flange. The two-bladed, fixed-pitch propeller remained attached to the propeller hub at the crankshaft flange. Both propeller blades exhibited leading edge gouging, S-bending, torsional twisting and chordwise striation along the length of the blades. The crankshaft was rotated by hand utilizing the propeller. Thumb compression was observed in proper firing order on all four cylinders. Mechanical and valve train continuity was established. The left and right magnetos remained securely attached to the engine at their respective mounting pads. The ignition harness was secure at each magneto. Magneto-to-engine timing was within manufacturer’s limits. Both magnetos were removed and rotated manually. Each magneto produced spark at the end of the respective spark plug lead, and the drives of each magneto remained intact and undamaged. The spark plugs were removed and according to the Champion Spark Plugs chart AV-27 “Check-A Plug” the spark plug electrodes exhibited coloration consistent with normal operation. Examination of the engine revealed no evidence of any preaccident mechanical malfunctions or failures that would have precluded normal operation.

Flight

Event TypeAccident
Event Time18:59 PDT
Nearest AirportKern Valley (1nm S)
Flight Plan FiledNone
Flight Plan ActivatedNo
Aircraft FireNo
Aircraft ExplosionNo

Aircraft

AircraftPiper PA 22-150 160
Tail NumberN9975D
Aircraft CategoryAir
DamageSubstantial
Operating RulePart 91
Engines1
Engine TypeReciprocating
Engine DetailsLycoming · O-360-A4A · Reciprocating
Seats2

People & Injuries

Injury Summary3 injuries (3 serious injuries)
Fatal0
Serious3
Minor0
Uninjured0
Total3
Crew 1Age 37 · First Class · Serious
Crew 2Serious
Crew 3Serious

Conditions

ConditionsVMC
LightDaylight
Wind320° @ 10 kt
Visibility10 sm
CeilingNone
Temperature / Dew Point45 C
Altimeter30.12 inHg
Observation Time01:54
Weather SourceWFAC

Appendix: Source Data