# NTSB LAX96LA148: Cessna 172P, N9964L, Fullerton, CA, March 30, 1996 - Type: NTSB accident investigation - Classification: Accident · No injuries · Limited investigation · Final report - Date: March 30, 1996, 12:02 local (20:02 UTC) - Place: Fullerton, CA - Location: 33.8720° N, 117.9798° W: Placed by OpenAirDocs at FULLERTON MUNI (FUL), within about a mile (OpenAirDocs) - Nearby events: https://openairdocs.org/map.md?lat=33.8720&lon=-117.9798&mi=10 - Phase of flight: [Landing](https://openairdocs.org/ntsb-phases/550) (OpenAirDocs' grouping) - Highest injury: No injuries - Injuries: 1 uninjured - Status: Completed, report August 20, 1996 - Report: Approved by Office Director - NTSB case key (mKey): 29401 - NTSB case page: https://web.ntsb.gov/investigations/?ntsbnumber=LAX96LA148 - NTSB report (PDF, downloads): https://data.ntsb.gov/carol-repgen/api/Aviation/ReportMain/GenerateNewestReport/29401/pdf - Page: https://openairdocs.org/ntsb/LAX96LA148 ## Probable cause the student pilot's inadequate compensation for the encounter with wake turbulence from a preceding small aircraft, and his improper bounced landing recovery technique. ## Sequence of events In NTSB's coding before 2008 (https://www.ntsb.gov/GILS/Documents/codman.pdf). - Vortex turbulence encountered, landing - flare/touchdown - wake turbulence - encountered, pilot in command (contributing factor) - Loss of control - in flight, landing - flare/touchdown - remedial action - inadequate, pilot in command (cause) - Hard landing, landing - flare/touchdown - recovery from bounced landing - inadequate, pilot in command (cause) - In flight collision with terrain/water, go-around (vfr) ## Analysis The student reported that he was practicing full-stop landings on runway 24. The student stated his belief that on short final approach the aircraft encountered a wind gust in the landing flare which yawed the nose of the airplane to the left. The pilot attempted to correct the yaw with control inputs and the aircraft hit the runway hard and bounced toward the left side of the runway. The pilot attempted a rejected landing maneuver by adding full power; however, the left wing tip contacted the ground and the aircraft crashed in the median between the runway and taxiway. The pilot stated that there were no mechanical malfunctions or failures of the aircraft. A weather observation taken immediately after the accident by the air traffic control tower reported winds from 250 degrees at 4 knots. ## Factual narrative On March 30, 1996, at 1202 hours Pacific standard time, a Cessna 172P, N9964L, collided with the ground during an attempted rejected landing at Fullerton, California. The aircraft was operated by General Aviation Company, Inc., of Fullerton, and was rented by the student pilot for a local area solo instructional flight. Visual meteorological conditions prevailed and no flight plan was filed. The aircraft sustained substantial damage. The student pilot, the sole occupant, was not injured. The flight originated at Fullerton on the day of the accident at 1130. The student reported that he was practicing full-stop landings on runway 24. The student stated his belief that on short final approach the aircraft encountered a wind gust in the landing flare which yawed the nose of the airplane to the left. The pilot attempted to correct the yaw with control inputs and the aircraft hit the runway hard and bounced toward the left side of the runway. The pilot attempted a rejected landing maneuver by adding full power; however, the left wing tip contacted the ground and the aircraft crashed in the median between the runway and taxiway. The pilot stated that there were no mechanical malfunctions or failures of the aircraft. A weather observation taken immediately after the accident by the air traffic control tower reported winds from 250 degrees at 4 knots. ## Aircraft - Registration: [N9964L](https://openairdocs.org/aircraft/N9964L), registered now, S/N 17276652, built 1986 (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: 17276652 - Airframe hours: 3233 - Engines: Lycoming O-320-D2J 160 horsepower reciprocating - Damage: Substantial damage - Flight: Instructional, Part 91 - Operator: General Aviation Company, Inc. - Registered owner: John B. Denault III - Airworthiness certificate: Standard, Normal - Last inspection: Annual, January 16, 1995, 19 hours before - Departed: FUL - Airport: FUL, Fullerton Muni, runway 24, 3,121 × 75 ft, asphalt ## Flight crew As NTSB recorded them. NTSB leaves out names. - Pilot; age 54; student; medical: class 3, valid medical--w/ waivers/lim; seat: left; flight hours: 86 total, 86 in this make and model, 25 as pilot in command, 16 in the last 90 days, 5 in the last 30 days ## Weather - Conditions: Visual (VMC), Day - Wind: 250° at 4 knots - Visibility: 12 statute miles - Lowest ceiling: none - Temperature: 72 °F, dew point 39 °F - Altimeter: 30.00 inHg - Observed at: FUL ## 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 19960330005689A](https://openairdocs.org/incident/19960330005689A), Mar 30, 1996: Cessna 172P, Fullerton, CA, Substantial damage. Wind gust on flare. Yawed. Nose left hit hard bounced in yaw. Tried go around. Left wing hit. Cartwheeled. No gusts on March 30, 1996, at 1202 hours pacific… ## Other investigations on N9964L (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 GAA19CA203](https://openairdocs.org/ntsb/GAA19CA203), Apr 11, 2019: Cessna 172 (N9964L), Fullteron, CA, substantial damage. Probable cause: The student pilot's failure to maintain directional control during the landing roll, which resulted in a runway excursion and nose-over. 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.