WPR11CA077

NTSB accident investigation · Cessna 177 · Corona, CA · December 12, 2010

Accident · No injuriesData collectionFinal report
Date
December 11, 2010, 18:30 local (Dec 12, 2010, 02:30 UTC)
Place
Corona, CA
Injuries
2 uninjured
Damage
Substantial damage
Phase of flight
Landing
Aircraft
N2262YCessna 177
Defining event
Landing-flare/touchdown: Hard landing
Weather
Visual (VMC) · Night
Status
Completed · report May 16, 2011
Report
Approved by Office Director
NTSB office
Western Pacific Region
Parties
FAA FSDO
FAA report
20101211053589A
Case key
78003

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 pilot’s improper flare, which resulted in a hard landing.

Findings · 3

NTSB’s coded findings. Those marked are part of the probable cause; the rest are factors or other findings. Under each, the cases with the same finding.

Performance/control parameters: landing flareAircraft › Aircraft oper/perf/capability · Incorrect use/operationCessna 177: 8 casesAll aircraft: 1,285 casesProbable cause
Action: incorrect action performancePersonnel issues › Action/decision · PilotCessna 177: 7 casesAll aircraft: 1,386 casesProbable cause
Use of equip/info: aircraft controlPersonnel issues › Task performance · PilotCessna 177: 20 casesAll aircraft: 9,295 casesProbable cause

Sequence of events

The events NTSB coded, in order, by phase of flight. The defining event is the one that best describes the accident. Under each, the cases with the same event anywhere in their sequence.

Analysis

The pilot reported that during the first approach for landing the wind affected his alignment to the runway, and he performed a go-around. On the second attempt, the approach seemed normal until the pilot flared the airplane excessively, resulting in a stall and subsequent hard landing. Examination of the airplane revealed substantial damage to the firewall and wing.

Factual narrative

The pilot reported that on the first approach, the windy conditions affected his alignment to the runway, so he chose to perform a go-around. On the second attempt, the alignment was good, and the approach seemed normal until the flare. The pilot said that he flared the airplane a bit too much. He heard the stall horn sound, and slightly pushed the yoke forward. The airplane dropped fast for the last few feet and the touchdown was hard. He taxied to parking and tied the airplane down. It was dark and he did not expect or notice any damage. The next morning, his instructor called and asked him if he had experienced a hard landing. Examination revealed a buckled firewall, and sheet metal damage on top of the wing.

Aircraft

Registration
N2262Y
Reported as
Cessna 177
Category
Airplane
Serial number
17700062
Airframe hours
4,298
Engine
Lycoming O-360, 180 horsepower, reciprocating
Damage
Substantial damage
Flight
Personal · Part 91
Operator
James Powell
Registered owner
James Powell
Airworthiness certificate
Standard, Normal
Last inspection
Annual · November 19, 2010
Departed
HII · Lake Havasu, AZ
Destination
AJO · Corona, CA
Airport
AJO · Corona Municipal, runway 07, 3,200 × 60 ft, asphalt

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
Pilot
Age
42
Injuries
None
Certificate
Private
Airplane ratings
Single-engine land
Medical
Class 3, Without waivers/limitations
Last flight review
February 20, 2010
Seat
Left
Flight hours
119 total · 49 in this make and model · 74 as pilot in command · 22 in the last 90 days · 7 in the last 30 days · 3 in the last 24 hours

Weather

Conditions
Visual (VMC) · Night
Wind
150° at 6 knots
Visibility
10 statute miles
Lowest ceiling
None
Temperature
73 °F, dew point 39 °F
Altimeter
30.07 inHg
Observed at
KAJO

Docket · 1

The files NTSB released with the investigation on January 21, 2011, on NTSB’s docket system: statements, records, photos and specialists’ reports. 336 KB in all.

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 N2262Y · 1

Matched to the same aircraft by N-number and date.