# NTSB LAX05CA017: Cessna 152, N4734B, Imperial, CA, October 26, 2004 - Type: NTSB accident investigation - Classification: Accident · No injuries · Data collection · Final report - Date: October 25, 2004, 17:40 local (Oct 26, 2004, 00:40 UTC) - Place: Imperial, CA - Coordinates: 32.834167, -115.578613 - Nearby events: https://openairdocs.org/map.md?lat=32.8342&lon=-115.5786&mi=10 - Phase of flight: [Landing](https://openairdocs.org/ntsb-phases/550) (OpenAirDocs' grouping) - Highest injury: No injuries - Injuries: 1 uninjured - Status: Completed, report January 24, 2005 - Report: Approved by Office Director - Parties: Federal Aviation Administration - NTSB case key (mKey): 60426 - NTSB case page: https://web.ntsb.gov/investigations/?ntsbnumber=LAX05CA017 - NTSB report (PDF, downloads): https://data.ntsb.gov/carol-repgen/api/Aviation/ReportMain/GenerateNewestReport/60426/pdf - Page: https://openairdocs.org/ntsb/LAX05CA017 ## Probable cause the student pilot's failure to maintain directional control during the landing rollout, which resulted in the airplane veering off of the runway surface and nosing over. ## Sequence of events In NTSB's coding before 2008 (https://www.ntsb.gov/GILS/Documents/codman.pdf). - Loss of control - on ground/water, landing - roll - directional control - not maintained, pilot in command (cause) - On ground/water encounter with terrain/water, landing - roll - terrain condition - soft - Nose over, landing - roll ## Analysis The airplane veered off the runway during the landing rollout and nosed over. As the student pilot initiated a landing on his first solo flight, the airplane touched down on the main landing gear first, with the nose landing gear following. Shortly after the nose landing gear touched down, the airplane began to veer to the left and continued off the runway surface. The main landing gear impacted soft dirt, and the airplane nosed over, coming to rest inverted. The student pilot stated that after touchdown, he lost focus and could not maintain control of the airplane. The operator reported no preimpact mechanical malfunctions or failures with the airplane. ## Factual narrative On October 25, 2004, about 1740 Pacific daylight time, a Cessna 152, N4734B, veered off the runway during the landing rollout and nosed over at Imperial County Airport, Imperial, California. Flite Co. LLC was operating the airplane under the provisions of 14 CFR Part 91. The student pilot, the sole occupant, was not injured; the airplane sustained substantial damage. The local instructional flight originated from Imperial about 1730. Visual meteorological conditions prevailed, and a flight plan had not been filed. In a written statement, the student pilot's certified flight instructor (CFI) reported that earlier in the day he and the student pilot performed touch-and-go practice takeoffs and landings for about 0.9 hours. During that flight, the student pilot executed seven landings, six of which were unassisted. The landing in which the CFI assisted, the second landing of the flight, the student pilot configured the airplane in a flare too high above the runway surface, and the CFI applied engine power in an effort to cushion the airplane's touchdown. After finishing the flight, the CFI determined that the student pilot was ready to fly the airplane without his assistance, and made the appropriate endorsements, enabling the student pilot to fly his first solo flight. The CFI further stated that the student pilot opted to fly his first solo flight almost immediately after their flight terminated. The instructor was to observe the flight while remaining in contact via a handheld radio device. He observed the student pilot depart runway 32 and maneuver the airplane in a traffic pattern, configuring it with fully extended wing flaps while on the final approach leg. Upon touchdown, the main landing gear contacted the runway surface first, with the nose landing gear following. Shortly after the nose landing gear touched down, the airplane began to veer to the left. The airplane continued to the left and departed the runway surface. About 100 feet off the runway, the main landing gear impacted soft dirt, and the airplane nosed over, coming to rest inverted. The CFI added, that after the accident the student pilot communicated to him that after the airplane touched down he lost focus and could not maintain control of the airplane. The airplane incurred damage to both wings and the rudder. The operator reported no preimpact mechanical malfunctions or failures with the airplane. ## Aircraft - Registration: [N4734B](https://openairdocs.org/deregistered/N4734B-2007-10-16), registration cancelled 2007-10-16, S/N 15283606, built 1979 (OpenAirDocs) - Reported make and model: Cessna 152 - 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: 15283606 - Engines: Lycoming O-235 reciprocating - Damage: Substantial damage - Flight: Instructional, Part 91 - Registered owner: Flight Co. LLC - Airworthiness certificate: Standard, Utility; Standard, Normal - Departed: IPL, Imperial, CA - Destination: IPL, Imperial, CA - Airport: IPL, Imperial County Airport, runway 32 ## Flight crew As NTSB recorded them. NTSB leaves out names. - Student pilot; age 29; student; airplane ratings: single-engine land; medical: class 2, with waivers/limitations; flight hours: 21 total, 21 in this make and model, 21 in the last 90 days, 13 in the last 30 days, 1 in the last 24 hours ## Weather - Conditions: Visual (VMC), Day ## 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 20041025033009A](https://openairdocs.org/incident/20041025033009A), Oct 25, 2004: Cessna 152, Imperial, CA, Substantial damage. (-23) The student pilot was performing his first solo flight, following a series of touch and go landings with a flight instructor. The instructor then… 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.