Cessna 172P N62348

Summary

On 24 May 2008 at about 20:45 local time, a Cessna 172P registered N62348 was involved in an accident near Troutdale, Oregon, United States. One person was on board and nobody was injured. The aircraft was substantially damaged. The NTSB has published a probable cause for this accident; it is quoted in full below.

Date

24 May 2008 at 20:45

Classification

Accident

Location

Troutdale, Oregon, United States

Nearest airport

Portland-Troutdale (TTD)

Coordinates

45.5494, -122.4014

Aircraft

Cessna 172P

Registration

N62348

Category

Airplane

Engines

1

Operator

Not recorded

Operating rule

Part 91: General Aviation

Purpose of flight

Instructional

Phase of flight

Not recorded

Route

Troutdale → Portland

Aircraft damage

Substantial

Weather

VMC

Light

Day

NTSB number

LAX08CA156

Nobody was injured.

The student pilot's failure to maintain directional control, which resulted in collision with a runway light.

Quoted verbatim from the NTSB record. This site does not paraphrase or interpret it.

Read the full NTSB narrative

The student pilot was performing a first supervised solo traffic pattern flight on runway 25. After completing three touch-and-go landings, he flared prematurely and bounced the fourth landing and subsequently landed hard. According to the student pilot, the aircraft yawed to the left due to the impact and a low crosswind condition. In a subsequent discussion after the accident, the student pilot reported to his Certified Flight Instructor (CFI) that he was focused on the cockpit instruments during the initial bounced landing recovery efforts, and by the time he looked out again, the airplane had drifted to the left edge of the runway. He initiated a rejected landing, resulting in a climb-out heading 50 degrees to the left of the runway heading. This was followed by a traffic pattern with a full stop landing. The student pilot and CFI reported that earlier in the day they had completed 1 hour of dual instruction. The dual flight consisted of airwork and seven touch-and-go landings in the pattern. The CFI observed the solo flight from the ramp but did not witness the rejected landing because he had turned to walk back to the FBO facility. Later that day, a dispatcher observed damage to the aircraft and notified the student pilot and CFI. The damage looked like the horizontal stabilizer had been grazed by a pole-like object on the bottom side. An FAA inspector confirmed structural damage to the right horizontal stabilizer. The CFI requested to examine the runway and found a damaged runway light, with a ground track mark in the grass leading up to and away from it. The CFI stated that the airplane had no mechanical malfunctions or irregularities with the control system during their dual flight, and the student did not claim any.

Quoted verbatim from the NTSB record.