Wednesday, August 3, 2016

Cessna 152, Hillsboro Aero Academy LLC, N49276: Accident occurred August 01, 2016 in Scappoose, Columbia County, Oregon

HILLSBORO AERO ACADEMY LLC:   http://registry.faa.gov/N49276

FAA Flight Standards District Office: FAA Portland FSDO-09


NTSB Identification: GAA16CA407

NTSB Identification: GAA16CA407
14 CFR Part 91: General Aviation
Accident occurred Monday, August 01, 2016 in Scappoose, OR
Probable Cause Approval Date: 09/22/2016
Aircraft: CESSNA 152, registration: N49276
Injuries: 1 Uninjured.

NTSB investigators used data provided by various entities, including, but not limited to, the Federal Aviation Administration and/or the operator and did not travel in support of this investigation to prepare this aircraft accident report.

The solo student pilot reported that during the third landing of his first solo, the airplane was a "little high" on final approach. He further reported that during the landing flare, the right wing was lifted by a crosswind and the airplane bounced nose wheel first on the runway. Subsequently, the nose wheel partially collapsed, the propeller struck the runway, and the airplane skidded to a stop on the runway.

The firewall sustained substantial damage.

The student pilot did not report any mechanical malfunctions or failures with the airplane that would have precluded normal operation. 

The automated weather observing system (AWOS) at the airport about 7 minutes before the accident recorded the wind at 020 degrees true at 11 knots, gusting to 15 knots. The AWOS at the airport about 53 minutes after the accident recorded the wind at 330 degrees true at 8 knots. The student pilot reported that the landing was on runway 33.

The National Transportation Safety Board determines the probable cause(s) of this accident as follows:
The student pilot's failure to maintain pitch control during the landing flare in gusty crosswind conditions, which resulted in a hard landing/abnormal runway contact, a partial nose wheel collapse and substantial damage to the firewall.

No comments: