No fatalities

24 May 2008: Cessna 172P — Hillsboro Aviation — Troutdale, OR

Troutdale, OR, United States

On 24 May 2008, a Cessna 172P operated by Hillsboro Aviation was involved in an aviation accident near Troutdale, OR. No fatalities were reported. Investigators recorded the probable cause as: The student pilot's failure to maintain directional control, which resulted in collision with a runway light. This summary draws on records from NTSB; 12 related events involving the same aircraft type or operator are linked below.

SourcesNTSBPrimary reportUpdated 1778583330Data APIEditorial standards

During a first supervised solo traffic pattern flight, a student pilot bounced the fourth landing, yawed left, drifted to the runway edge, initiated a rejected landing, and later damaged the aircraft's horizontal stabilizer after striking a runway light.

Accident Details

A student pilot was performing a first supervised solo traffic pattern flight on runway 25 at Portland-Troutdale Airport (KTTD). After completing three touch-and-go landings, the pilot flared prematurely and bounced the fourth landing, subsequently landing hard. According to the student pilot, the aircraft yawed to the left due to the impact and a low crosswind condition.

Student Pilot's Account

During 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. 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.

CFI Observations

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. 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.

Aftermath

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.

Contributing factors

Causes

Directional control — Not attained/maintained

Other contributing factors

Incorrect use/operationPilotRunway lighting