- Date
- April 12, 2004, 17:50 local (Apr 13, 2004, 00:50 UTC)
- Place
- Long Beach, CA
- Injuries
- 1 uninjured
- Damage
- Substantial damage
- Phase of flight
- Landing
- Aircraft
- N669SPCessna 172S
- Weather
- Visual (VMC) · Day
- Status
- Completed · report June 30, 2004
- Report
- Approved by Office Director
- Parties
- Federal Aviation Administration
- FAA report
- 20040412006489A
- Case key
- 59074
From the NTSB’s public API. By law, NTSB reports can’t be used as evidence in lawsuits over the accident.
On this page
Probable cause
the student pilot's inadequate flare, which resulted in a hard landing and porpoise.
Sequence of events
NTSB’s coding before 2008: each occurrence and phase of flight, and the causes and factors under it. The codes are defined in NTSB’s coding manual.
Analysis
The airplane experienced a hard landing. The student pilot was attempting to land, but did not flare before touchdown. One propeller blade collided with the runway during touchdown, and the nose wheel impacted the runway surface hard, pushing it into the firewall. This resulted in the firewall bending and the elevator controls jamming, becoming inoperative. The airplane porpoised down the runway, and the student applied brake pressure. The student taxied to the ramp area uneventfully. The student pilot reported no preimpact mechanical malfunctions or failures with the airplane.
Factual narrative
On April 12, 2004, about 1750 Pacific daylight time, a Cessna 172S, N669SP, experienced a hard landing at Long Beach Airport, Long Beach, California. California Flight Center 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. Visual meteorological conditions prevailed, and a flight plan had not been filed. The local student solo instructional flight originated in Long Beach about 1630.
In a written statement, the student pilot reported that he was attempting to land on runway 25L. While the airplane was over the runway identifying numbers, he started the flare. The yoke control froze and he could not properly operate it. The airplane touched down, and bounced down the runway. He reported no preimpact mechanical malfunctions or failures with the airplane.
During a telephone interview with the National Transportation Safety Board, the owner of the flight school that was operating the airplane stated that the student pilot had about 4.7 hours of solo time. After interviewing the student, and looking at the damage, he assessed that the student did not flare before touchdown. He thought the nose wheel impacted the runway hard, pushing it into the cowling. This resulted in the firewall bending and the elevator controls jamming, becoming inoperative. The airplane porpoised down the runway, and the student applied brake pressure. The student taxied to the ramp area uneventfully. The flight school owner noted that one propeller blade collided with the runway during touchdown, leading him to believe that the student attempted to touchdown at a 40- to 45-degree angle. Examination of the airplane revealed no discrepancies with the control system.
Aircraft
- Registration
- N669SP
- Reported as
- Cessna 172S
- Category
- Airplane
- Serial number
- 172S8622
- Engine
- Lycoming IO-360, reciprocating
- Damage
- Substantial damage
- Flight
- Instructional · Part 91
- Operator
- California Flight Center
- Registered owner
- Timothy Snee
- Airworthiness certificate
- Standard, Utility; Standard, Normal
- Departed
- LGB · Long Beach, CA
- Destination
- LGB · Long Beach, CA
- Airport
- LGB · Long Beach Airport, runway 25L
Matched to the registry by N-number and the event date; the registry’s history has gaps, so older matches can be wrong. Compare the reported make and model.
Flight crew
As NTSB recorded them. NTSB leaves out names.
- Role
- Student pilot
- Age
- 41
- Certificate
- Student
- Medical
- Class 3
- Flight hours
- 30 total · 30 in this make and model · 3 in the last 90 days · 3 in the last 30 days
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.
Other investigations on N669SP · 1
Matched to the same aircraft by N-number and date.