# NTSB LAX08CA156: Cessna 172P, N62348, Troutdale, OR, May 24, 2008 - Type: NTSB accident investigation - Classification: Accident · No injuries · Data collection · Final report - Date: May 24, 2008, 13:45 local (20:45 UTC) - Place: Troutdale, OR - Coordinates: 45.549446, -122.40139 - Nearby events: https://openairdocs.org/map.md?lat=45.5494&lon=-122.4014&mi=10 - Phase of flight: [Landing](https://openairdocs.org/ntsb-phases/550) (OpenAirDocs' grouping) - Defining event: [Landing-flare/touchdown: Hard landing](https://openairdocs.org/ntsb-events/092) - Highest injury: No injuries - Injuries: 1 uninjured - Status: Completed, report June 30, 2008 - Report: Approved by Office Director - Parties: Federal Aviation Administration - NTSB case key (mKey): 68096 - NTSB case page: https://web.ntsb.gov/investigations/?ntsbnumber=LAX08CA156 - NTSB report (PDF, downloads): https://data.ntsb.gov/carol-repgen/api/Aviation/ReportMain/GenerateNewestReport/68096/pdf - Page: https://openairdocs.org/ntsb/LAX08CA156 ## Probable cause The student pilot's failure to maintain directional control, which resulted in collision with a runway light. ## Findings NTSB's coded findings; those marked are part of the probable cause. - [Performance/control parameters: landing flare](https://openairdocs.org/ntsb-findings/01062041): Aircraft › Aircraft oper/perf/capability · Incorrect use/operation (probable cause); cases with it: [Cessna 172P, 38 cases](https://openairdocs.org/ntsb-findings/01062041/cases.md?model=2072436), [All aircraft, 1,285 cases](https://openairdocs.org/ntsb-findings/01062041/cases.md) - [Action: incorrect action performance](https://openairdocs.org/ntsb-findings/02041015): Personnel issues › Action/decision · Pilot (probable cause); cases with it: [Cessna 172P, 19 cases](https://openairdocs.org/ntsb-findings/02041015/cases.md?model=2072436), [All aircraft, 1,386 cases](https://openairdocs.org/ntsb-findings/02041015/cases.md) - [Performance/control parameters: directional control](https://openairdocs.org/ntsb-findings/01062020): Aircraft › Aircraft oper/perf/capability · Not attained/maintained (probable cause); cases with it: [Cessna 172P, 28 cases](https://openairdocs.org/ntsb-findings/01062020/cases.md?model=2072436), [All aircraft, 3,958 cases](https://openairdocs.org/ntsb-findings/01062020/cases.md) - [Airport facilities/design: runway lighting](https://openairdocs.org/ntsb-findings/03017015): Environmental issues › Operating environment · Not specified; cases with it: [Cessna 172P, 1 case](https://openairdocs.org/ntsb-findings/03017015/cases.md?model=2072436), [All aircraft, 18 cases](https://openairdocs.org/ntsb-findings/03017015/cases.md) ## Sequence of events The events NTSB coded, in order, by phase of flight. The defining event best describes what happened. - [Landing-flare/touchdown: Hard landing](https://openairdocs.org/ntsb-events/092) (defining event); cases with it: [Cessna 172P, 39 cases](https://openairdocs.org/ntsb-events/092/sequence.md?model=2072436), [All aircraft, 2,102 cases](https://openairdocs.org/ntsb-events/092/sequence.md) - [Landing: Loss of control on ground](https://openairdocs.org/ntsb-events/230); cases with it: [Cessna 172P, 37 cases](https://openairdocs.org/ntsb-events/230/sequence.md?model=2072436), [All aircraft, 4,585 cases](https://openairdocs.org/ntsb-events/230/sequence.md) - [Landing: Collision with terr/obj (non-CFIT) ](https://openairdocs.org/ntsb-events/470); cases with it: [Cessna 172P, 45 cases](https://openairdocs.org/ntsb-events/470/sequence.md?model=2072436), [All aircraft, 10,189 cases](https://openairdocs.org/ntsb-events/470/sequence.md) ## Analysis 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. ## Factual narrative The 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, 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. ## Aircraft - Registration: [N62348](https://openairdocs.org/aircraft/N62348), registered now, S/N 17275254, built 1981 (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: 17275254 - Engines: Lycoming O-320 reciprocating - Damage: Substantial damage - Flight: Instructional, Part 91 - Registered owner: Hillsboro Aviation - Airworthiness certificate: Standard, Utility; Standard, Normal - Departed: TTD, Troutdale, OR - Destination: TTD, PORTLAND, OR - Airport: TTD, Portland-Troutdale, runway 25, 5,399 × 150 ft, asphalt ## Flight crew As NTSB recorded them. NTSB leaves out names. - Student pilot; age 42; injuries: none; student; medical: class 2; seat: left; flight hours: 36 total, 36 in this make and model, 1 as pilot in command, 11 in the last 90 days, 7 in the last 30 days, 2 in the last 24 hours ## Weather - Conditions: Visual (VMC), Day - Wind: 260° at 5 knots - Visibility: 10 statute miles - Lowest ceiling: none - Temperature: 68 °F, dew point 52 °F - Altimeter: 29.73 inHg - Observed at: KTTD ## 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 20080524836049A](https://openairdocs.org/incident/20080524836049A), May 24, 2008: Cessna 172P, Portland, OR, Minor damage. (-23) A student pilot, was making a solo landing at Troutdale airport on may 24, 2008. The aircraft appears to have bounced once, came back down to the runway… 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.