FLIGHT FINDINGSAVIATION OCCURRENCE MAP
Back to map

WPR18FA035 · Cessna 152

19 Nov 2017 · Tehachapi, CA, United States

Cessna 152 · Accident: loss of control in flight while maneuvering

From Tehachapi Municipal Airport (TSP) to an unrecorded destination

Report a problem

Event

NTSB case
WPR18FA035
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
1 · 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 152

Aircraft type
Cessna 152
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
N24987
Operator
Unknown
Onboard fatalities
Unknown
Route
From Tehachapi Municipal Airport (TSP), Tehachapi, CATo not recorded
Aircraft age
About 40 years (built 1977)
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
Maneuvering
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
Loss of control in flight
DamageDestroyed: beyond practical repair. Substantial: damage that affects the structure, performance or handling and normally needs major repair. Minor: less than that. Glossary
Destroyed

Cause areas

  • Environmental issues › Conditions/weather/phenomena
  • Personnel issues › Psychological
  • Personnel issues › Task performance

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

NTSB narrative

The private pilot departed on a personal flight in visual meteorological conditions during the early evening and flew to a nearby airport, where he parked the airplane and walked to a nearby restaurant. He returned to the airplane about an hour later, which was about 20 minutes after the end of civil twilight. Surveillance video captured the accident airplane depart the runway and enter a right traffic pattern, which was the opposite of the published left traffic pattern and took the airplane over unlit pasture and hills. The imagery then depicted the airplane enter a rapid descent on what appeared to be the right downwind leg of the traffic pattern. The airplane disappeared from view consistent with ground impact. The descent duration was about 7 seconds.

The airplane impacted a pasture north of the airport. The debris field indicated that the airplane impacted the ground with a relatively shallow flight path angle, in a nose- and right-wing low attitude, with a significant amount of horizontal energy.

All major airplane and engine components were identified in the wreckage, and no indications of any pre-impact mechanical deficiencies or failures were observed. The flaps were in the fully retracted position, which was the climb-cruise configuration, likely indicative that the pilot was not attempting a landing when the impact occurred. The undamaged condition of the artificial horizon gyro rotor and internal case suggested a possibility that the device was not operating, but the actual operating status of the instrument at the time of the accident could not be determined. Even if the artificial horizon was inoperative, external visual references should have been sufficient to enable the pilot, albeit possibly with some difficulty, to maintain the proper airplane attitude and flight path.

Some fibrous lint-like material was found in the carburetor fuel inlet screen; the material was foreign to the airplane fuel system, but it was not determined when or by what means the lint was introduced into the system. The lint did not appear to have any adverse effect on engine operation; propeller damage was consistent with the engine developing significant power at the time of impact. Airplane fueling information and published performance data indicated that the airplane had sufficient fuel onboard for a return flight to the airport of origin.

About 5 weeks before the accident, the pilot had completed a night flight in the accident airplane from his home airport to the accident airport and back, which indicated that he was at least somewhat familiar with the accident airport. The reason for the pilot's use of a right traffic pattern instead of the designated left traffic pattern for his departure could not be determined.

Although the pilot had documented color vision deficiencies, this condition likely did not contribute to the accident sequence. The pilot had relatively limited total and night flying experience, and the night and local terrain were very dark. Given the signatures of engine power and lack of mechanical anomalies found during postaccident examination, it is not likely that the accident was the result of a loss of engine power. Further, correlation of debris field information with the descent angle depicted in the surveillance imagery frames indicated that the descent path was too shallow to be consistent with an aerodynamic stall. Additionally, the airplane's impact attitude and the distribution of the wreckage were inconsistent with a loss of control due to spatial disorientation. It is possible that the pilot lost his situational awareness while maneuvering onto the right downwind leg which resulted in the airplane descending rapidly to ground impact.

Probable cause

The pilot's loss of situational awareness shortly after takeoff over a sparsely lit area in dark night conditions, which resulted in a rapid descent to ground impact.

Verbatim NTSB analysis and probable cause from the NTSB dataset

Sources

NTSB record WPR18FA035
Event ID
20171120X25221
Case number
WPR18FA035
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: local date, investigation status, coordinates. Values present in the bulk record are kept.
  • The date is the local date; the NTSB stores the UTC date 2017-11-20.
  • API snapshot SHA-256: 9d49281a05a0bf6808d322f5302cbb3839883870e954d991a4d4f31efe088b93; retrieved 2026-09-15T06:25:04.333Z.