# NTSB LAX90LA216: Cessna 172P, N216PB, Redding, CA, June 9, 1990

- Type: NTSB accident investigation
- Classification: Accident · No injuries · Limited investigation · Final report
- Date: June 9, 1990, 10:30 local (17:30 UTC)
- Place: Redding, CA
- Coordinates: 40.599811, -122.460739 (estimated)
- Nearby events: https://openairdocs.org/map.md?lat=40.5998&lon=-122.4607&mi=10
- Phase of flight: [Takeoff](https://openairdocs.org/ntsb-phases/300) (OpenAirDocs' grouping)
- Highest injury: No injuries
- Injuries: 4 uninjured
- Status: Completed, report September 15, 1992
- Report: Approved by Office Director
- NTSB case key (mKey): 26837
- NTSB case page: https://web.ntsb.gov/investigations/?ntsbnumber=LAX90LA216
- NTSB report (PDF, downloads): https://data.ntsb.gov/carol-repgen/api/Aviation/ReportMain/GenerateNewestReport/26837/pdf
- Page: https://openairdocs.org/ntsb/LAX90LA216

## Probable cause

THE FAILURE OF THE PILOT IN COMMAND TO MAINTAIN DIRECTION CONTROL. FACTORS IN THE ACCIDENT WERE THE PILOT IN COMMAND'S PREMATURE ROTATION DURING THE TAKEOFF AND THE FAILURE TO TAKE THE NECESSARY REMEDIAL ACTION.

## Sequence of events

In NTSB's coding before 2008 (https://www.ntsb.gov/GILS/Documents/codman.pdf).

- Loss of control - on ground/water, takeoff
  - rotation - premature, pilot in command (contributing factor)
  - directional control - not maintained, pilot in command (cause)
- On ground/water collision with object, takeoff
  - object - aircraft parked/standing

## Analysis

THE PILOT STATED THAT SHE PREMATURELY ROTATED THE AIRCRAFT AND THEN LOST CONTROL. THE AIRCRAFT THEN VEERED OFF THE RUNWAY AND STRUCK A PARKED AIRCRAFT. THE PILOT ALSO INDICATED THAT THERE WERE NO MECHANICAL FAILURES OR MALFUNCTIONS WITH THE AIRCRAFT BEFORE THE ACCIDENT.

## Aircraft

- Registration: [N216PB](https://openairdocs.org/deregistered/N216PB-2013-07-02), registration cancelled 2013-07-02, S/N 17274440, built 1980 (OpenAirDocs)
- Reported make and model: CESSNA 172P
- Registry model: [Cessna 172P](https://openairdocs.org/model/cessna-172p) (registry code 2072436) (OpenAirDocs)
- Registry engine: [Lycoming 0-320 series](https://openairdocs.org/engine/lycoming-0-320-series) (registry code 41508, reciprocating) (OpenAirDocs)
- Category: Airplane
- Serial number: 74440
- Airframe hours: 3474
- Engines: LYCOMING O-320-D2J 160 horsepower reciprocating
- Damage: Substantial damage
- Flight: Personal, Part 91
- Operator: Hillside Aviation
- Registered owner: Hillside Aviation
- Airworthiness certificate: Standard, Normal
- Last inspection: 100 hour, May 29, 1990, 26 hours before
- Destination: 086, TRINITY CENTER, CA
- Airport: O85, Benton Field, runway 33, 2,420 × 80 ft, asphalt

## Flight crew

As NTSB recorded them. NTSB leaves out names.

- Pilot; age 49; private; airplane ratings: single-engine land; medical: class 3, valid medical--w/ waivers/lim; flight hours: 252 total, 252 in this make and model, 250 as pilot in command, 33 in the last 90 days

## Weather

- Conditions: Visual (VMC), Day
- Wind: calm
- Visibility: 50 statute miles
- Lowest ceiling: none
- Temperature: 81 °F

## FAA reports on this event (1)

The FAA's own accident and incident reports, matched to the aircraft by N-number and date (OpenAirDocs).

- [Accident 19900609019919A](https://openairdocs.org/incident/19900609019919A), Jun 9, 1990: Cessna 172P, Redding, CA, Substantial damage. Rotated prematurly on takeoff. Lost control. Veered off runway and struck a parked aircraft.

## Other investigations on N216PB (1)

From the NTSB's public API. Aircraft are matched to registry aircraft by N-number and event date, checked against the reported serial number, make and model; the registry's history has gaps, so older matches can be wrong. Compare the reported make and model.

- [NTSB LAX00FA178](https://openairdocs.org/ntsb/LAX00FA178), Apr 28, 2000: Cessna 172P (N216PB), Chester, CA, destroyed, 4 fatal. Probable cause: The pilot's encounter with a wind shear at low altitude, which resulted in a loss of control and a stall/spin. Factors in the accident were the high density altitude and the pilot's lack of…

From the NTSB's public API. Aircraft are matched to registry aircraft by N-number and event date, checked against the reported serial number, make and model; the registry's history has gaps, so older matches can be wrong. Compare the reported make and model.

---
OpenAirDocs.org is an independent research project of [Contrail Labs](https://contraillabs.com/). It is not affiliated with the FAA or the NTSB. Source documents are U.S. government works in the public domain.