FLIGHT FINDINGSAVIATION OCCURRENCE MAP
Back to map

WPR17FA171 · Cessna 172N

29 Jul 2017 · Big Bear, CA, United States

Cessna 172N · Accident during initial climb

From Big Bear City Airport (L35) to Apple Valley Airport (APV)

Report a problem

Event

NTSB case
WPR17FA171
Event typeAccident: someone killed or seriously injured, or the aircraft substantially damaged (NTSB definition). Incident: an occurrence that affected or could have affected safety, short of that. Glossary
Accident
InvestigationHow far the investigation had got when the record was published: preliminary, ongoing, final or completed. Unknown where the source does not say. Glossary
Completed
API-reported fatalities
2 · all aircraft and ground
Ground fatalities
Unknown
OperationWhat kind of flying it was, grouped by the rules it flew under: airline (US Part 121), air taxi and commuter (Part 135), general aviation (Part 91 and similar), military or government. Glossary
General aviation
WeatherVisual meteorological conditions (VMC): good enough to fly by looking outside. Instrument conditions (IMC): cloud or low visibility, flying by instruments. Glossary
Visual Meteorological Cond

Cessna 172N

Aircraft type
Cessna 172
Category
Airplane
RegistrationThe aircraft's tail number, such as N12345 or G-ABCD. Registrations are reissued, so the same one years apart can be a different aircraft. Glossary
N5381J
Operator
Unknown
Onboard fatalities
Unknown
Route
From Big Bear City Airport (L35), Big Bear City, CATo Apple Valley Airport (APV), Apple Valley, CA
Aircraft age
About 37 years (built 1980)
Flight rulesThe regulations the flight operated under: in the US, Part 91 (general aviation), Part 121 (airlines), Part 135 (air taxi and commuter) and others; for flights abroad, the NTSB's coarser commercial or non-commercial code. Glossary
Part 91: General Aviation
Phase of flightThe stage of the flight when things started to go wrong: standing, taxi, takeoff, initial climb, en route, maneuvering, approach or landing. Glossary
Initial climb
Defining eventThe single coded event the NTSB judges best describes what happened (records from 2008 on). Older records name the first occurrence in the sequence instead. Glossary
Miscellaneous/other
DamageDestroyed: beyond practical repair. Substantial: damage that affects the structure, performance or handling and normally needs major repair. Minor: less than that. Glossary
Substantial

Cause areas

  • Aircraft › Aircraft oper/perf/capability
  • Environmental issues › Conditions/weather/phenomena
  • Personnel issues › Task performance

Approximate · Coordinates from the NTSB case API, not marked as estimated; no uncertainty radius is established.

NTSB narrative

The commercial pilot and passenger departed in the airplane from the airport, which was located at an elevation of 6,752 ft mean sea level (msl). Airport surveillance video showed that the airplane became increasingly slow during the initial climb after takeoff. A witness reported that, as the airplane approached the end of the runway, it stopped climbing and entered a nose-high pitch attitude that the witness described as "hanging by the prop." The airplane then turned 90° to the downwind leg of the airport traffic pattern and sank as the wings rocked back and forth before it disappeared behind trees. The wreckage orientation indicated that the airplane maintained a southerly heading before it descended into the tree line. The airplane impacted the ground in a nose-down attitude with partial forward bending of the tail, consistent with an aerodynamic stall. Postaccident examination of the airplane did not reveal any preimpact anomalies.

The density altitude about the time of the accident exceeded 9,100 ft msl. The effects of high density altitude conditions on takeoff performance include increased takeoff roll distance and reduced rate of climb. Review of performance charts indicated that the airplane should have been able to climb at a rate around 440 ft per minute; however, the video indicated that the airplane was climbing at a rate of 340 ft per minute. It is likely that, experiencing degraded airplane performance due to the density altitude, the pilot responded by increasing the airplane's pitch attitude in an attempt to improve its rate of climb. The pilot subsequently exceeded the airplane's critical angle of attack, which resulted in an aerodynamic stall and impact with terrain.

The pilot's primary flight experience was in turbine engine-equipped rotorcraft, and he had recently received a checkout in the accident airplane make and model that included high density altitude operation and mixture leaning procedures. The airplane's mixture control was found in the full rich position after the accident; however, the position of the control before and during the takeoff could not be determined. If the pilot departed in the high density altitude environment without leaning the fuel/air mixture control or subsequently enrichened the fuel/air mixture control to troubleshoot the airplane's reduced takeoff performance, this would have further reduced the available engine power and the airplane's climb rate.

Probable cause

The pilot's exceedance of the airplane's critical angle of attack during takeoff in high density altitude conditions, which resulted in an aerodynamic stall, loss of control, and subsequent impact with terrain.

Verbatim NTSB analysis and probable cause from the NTSB dataset

Sources

NTSB record WPR17FA171
Event ID
20170730X40056
Case number
WPR17FA171
Dataset
full-current
Source SHA-256
5cf380f0061817c0331a6b2d8cc7e0ee3a79bea469a1001dc5c10e56f35f5ab3
Source notes (4)
  • Unreviewed is an editorial label, not an investigation status. API-sourced is not report-checked or human-reviewed. Explicit event totals are used without summing aircraft injury tables; onboard allocation is withheld. Unknown values remain unknown. The operation category is mapped from the NTSB-reported FAR part and has not been reviewed.
  • Filled from the NTSB case API where the bulk record had no value: investigation status, coordinates. Values present in the bulk record are kept.
  • The date is the local date, which is the same as the UTC date the NTSB stores.
  • API snapshot SHA-256: 1d1ccd467e4e018d0b43bba7e859a3327863f91cadce9af879676b6d98bd1e30; retrieved 2026-09-15T06:11:15.791Z.