# NTSB GAA18CA076: Cessna 152, N417CB, Fullerton, CA, November 30, 2017

- Type: NTSB accident investigation
- Classification: Accident · No injuries · Data collection · Final report
- Date: November 30, 2017, 11:40 local (19:40 UTC)
- Place: Fullerton, CA
- Coordinates: 33.872501, -117.9775 (estimated)
- Nearby events: https://openairdocs.org/map.md?lat=33.8725&lon=-117.9775&mi=10
- Phase of flight: [Takeoff](https://openairdocs.org/ntsb-phases/300) (OpenAirDocs' grouping)
- Defining event: [Takeoff: Loss of control on ground](https://openairdocs.org/ntsb-events/230)
- Highest injury: No injuries
- Injuries: 1 uninjured
- Status: Completed, report March 14, 2018
- Report: Approved by Office Director
- NTSB office: General Aviation Accidents
- Parties: FAA
- NTSB case key (mKey): 96446
- NTSB case page: https://web.ntsb.gov/investigations/?ntsbnumber=GAA18CA076
- NTSB report (PDF, downloads): https://data.ntsb.gov/carol-repgen/api/Aviation/ReportMain/GenerateNewestReport/96446/pdf
- NTSB docket: https://data.ntsb.gov/Docket?ProjectID=96446
- Page: https://openairdocs.org/ntsb/GAA18CA076

## Probable cause

The student pilot’s failure to maintain directional control during takeoff.

## Findings

NTSB's coded findings; those marked are part of the probable cause.

- [Performance/control parameters: directional control](https://openairdocs.org/ntsb-findings/01062020): Aircraft › Aircraft oper/perf/capability · Not attained/maintained (probable cause); cases with it: [Cessna 152, 32 cases](https://openairdocs.org/ntsb-findings/01062020/cases.md?model=2071835), [All aircraft, 3,958 cases](https://openairdocs.org/ntsb-findings/01062020/cases.md)
- [Use of equip/info: aircraft control](https://openairdocs.org/ntsb-findings/02063040): Personnel issues › Task performance · Pilot (probable cause); cases with it: [Cessna 152, 115 cases](https://openairdocs.org/ntsb-findings/02063040/cases.md?model=2071835), [All aircraft, 9,295 cases](https://openairdocs.org/ntsb-findings/02063040/cases.md)

## Sequence of events

The events NTSB coded, in order, by phase of flight. The defining event best describes what happened.

- [Takeoff: Loss of control on ground](https://openairdocs.org/ntsb-events/230) (defining event); cases with it: [Cessna 152, 41 cases](https://openairdocs.org/ntsb-events/230/sequence.md?model=2071835), [All aircraft, 4,585 cases](https://openairdocs.org/ntsb-events/230/sequence.md)
- [Takeoff: Runway excursion](https://openairdocs.org/ntsb-events/300); cases with it: [Cessna 152, 38 cases](https://openairdocs.org/ntsb-events/300/sequence.md?model=2071835), [All aircraft, 3,643 cases](https://openairdocs.org/ntsb-events/300/sequence.md)
- [Takeoff: Collision with terr/obj (non-CFIT) ](https://openairdocs.org/ntsb-events/470); cases with it: [Cessna 152, 84 cases](https://openairdocs.org/ntsb-events/470/sequence.md?model=2071835), [All aircraft, 10,189 cases](https://openairdocs.org/ntsb-events/470/sequence.md)

## Analysis

The flight instructor reported that, during the student pilot's solo flight in the traffic pattern, after completing a series of takeoffs and landings, the student decided to practice a soft-field takeoff. During the takeoff, the student applied back pressure and full throttle; however, he did not add sufficient right rudder. Subsequently, the airplane veered off the runway to the left, struck the precision approach path indicator lights, and then came to rest. The airplane sustained substantial damage to the fuselage and engine mount. The flight instructor reported that there were no preaccident mechanical failures or malfunctions with the airplane that would have precluded normal operation.

## Factual narrative

The flight instructor reported that, during the student pilot's solo flight in the traffic pattern, after completing a series of takeoffs and landings, the student decided to practice a soft field takeoff. During the takeoff, the student applied back pressure and full throttle; however, he did not add sufficient right rudder. Subsequently, the airplane veered off the runway to the left, struck the Precision Approach Path Indicator lights, and came to rest off the runway. The airplane sustained substantial damage to the fuselage and engine mount. The flight instructor reported that there were no preaccident mechanical failures or malfunctions with the airplane that would have precluded normal operation.

## Aircraft

- Registration: [N417CB](https://openairdocs.org/aircraft/N417CB), registered now, S/N 15281010 (OpenAirDocs)
- Reported make and model: CESSNA 152 (NO SERIES)
- Registry model: [Cessna 152](https://openairdocs.org/model/cessna-152) (registry code 2071835) (OpenAirDocs)
- Registry engine: [Lycoming 0-235 series](https://openairdocs.org/engine/lycoming-0-235-series) (registry code 41505, 4 cycle) (OpenAirDocs)
- Category: Airplane
- Serial number: 15281010
- Year built: 1981
- Engines: LYCOMING O-235 SERIES reciprocating
- Damage: Substantial damage
- Flight: Instructional, Part 91
- Airworthiness certificate: Standard, Utility; Standard, Normal
- Departed: FUL, Fullerton, CA
- Destination: FUL, Fullerton, CA
- Airport: FUL, Fullerton Muni, runway 24, 3,121 × 75 ft, asphalt
- Equipment: Unknown

## Flight crew

As NTSB recorded them. NTSB leaves out names.

- Student pilot; age 24; injuries: none; student; medical: class 3, without waivers/limitations; seat: left; restraint: 3-point; flight hours: 35 total, 35 in this make and model

## Weather

- Conditions: Visual (VMC), Day
- Wind: calm
- Visibility: 10 statute miles
- Temperature: 72 °F, dew point 41 °F
- Altimeter: 30.01 inHg
- Observed at: KFUL

## 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 20171130022249A](https://openairdocs.org/incident/20171130022249A), Nov 30, 2017: Cessna 152, Fullerton, CA, Substantial damage. Student pilot was performing his second solo flight at his home airport (kful). Weather conditions at the time of the accident at approximately 11:40 PST was…

## Docket (2 files)

The files NTSB released with the investigation on February 1, 2018, on NTSB's docket system: https://data.ntsb.gov/Docket?ProjectID=96446. 1.6 MB in all.

- Pilot/Operator Aircraft Accident Report, NTSB Form 6120.1 (item 1, .PDF, 899 KB): https://data.ntsb.gov/Docket/Document/docBLOB?ID=40459736&FileExtension=.PDF&FileName=Pilot%2FOperator%20Aircraft%20Accident%20Report,%20NTSB%20Form%206120.1-Master.PDF
- Accident Pictures (item 2, .PDF, 740 KB): https://data.ntsb.gov/Docket/Document/docBLOB?ID=40459737&FileExtension=.PDF&FileName=Accident%20Pictures-Master.PDF

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.
