WPR14CA351

NTSB accident investigation · Cessna 172S · Santa Ynez, CA · August 16, 2014

Accident · No injuriesData collectionFinal report
Date
August 16, 2014, 16:00 local (23:00 UTC)
Place
Santa Ynez, CA
Injuries
1 uninjured
Damage
Substantial damage
Phase of flight
Landing
Aircraft
N10033Cessna 172S
Defining event
Landing-flare/touchdown: Abnormal runway contact
Weather
Visual (VMC) · Day
Status
Completed · report October 27, 2014
Report
Approved by Office Director
NTSB office
Western Pacific Region
Parties
FAA FSDO
FAA report
20140816015549A
Case key
89928

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 student pilot's inadequate flare and loss of aircraft control during landing, which resulted in multiple bounces.

Findings · 2

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 · Not attained/maintainedCessna 172S: 99 casesAll aircraft: 1,285 casesProbable cause
Use of equip/info: aircraft controlPersonnel issues › Task performance · Student/instructed pilotCessna 172S: 206 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 student pilot was conducting his final required solo cross-country flight. The flight to the first destination was uneventful, and the pilot entered the left-hand traffic pattern for the runway at the non-towered airport. The pilot reported that his base-to-final turn was slightly "wide," which placed the airplane to the right of the extended runway centerline. He also reported that he was "a little high" on the final approach. He corrected his flight path, and was satisfied that the airplane was positioned for a normal landing. The pilot used full flaps for this landing, as was his normal habit pattern. The airplane landed slightly beyond where the pilot had planned, but not far enough down the runway to cause him any concern. The touchdown was "hard," the airplane bounced, and the pilot "re-flared" to correct the situation. The airplane began "porpoising" and bounced at least two more times before the pilot was able to regain control and keep it on the ground. During the bounces, the pilot did not adjust the power or consider aborting the landing attempt. Although he had learned about porpoising in his ground training, he had never experienced it prior to this event, and did not immediately recall or implement the flight school's recommended corrective action, which was a go-around. The pilot taxied the airplane to a parking spot, and discovered that the airplane was substantially damaged. The firewall, cockpit floor, and several fuselage skins were buckled, and elevator travel was restricted. The pilot reported no preimpact mechanical malfunctions or failures with the airplane that would have precluded normal operation.

Factual narrative

The student pilot was conducting his final required solo cross-country flight. The flight to the first destination was uneventful, and the pilot entered the left-hand traffic pattern for the runway at the non-towered airport. The pilot reported that his base-to-final turn was slightly "wide," which placed the airplane to the right of the extended runway centerline. He also reported that he was "a little high" on the final approach. He corrected his flight path, and was satisfied that the airplane was positioned for a normal landing. The pilot used full flaps for this landing, as was his normal habit pattern. The airplane landed slightly beyond where the pilot had planned, but not far enough down the runway to cause him any concern. The touchdown was "hard," the airplane bounced, and the pilot "re-flared" to correct the situation. The airplane began "porpoising" and bounced at least two more times before the pilot was able to regain control and keep it on the ground. During the bounces, the pilot did not adjust the power or consider aborting the landing attempt. Although he had learned about porpoising in his ground training, he had never experienced it prior to this event, and did not immediately recall or implement the flight school's recommended corrective action, which was a go-around. The pilot taxied the airplane to a parking spot, and discovered that the airplane was substantially damaged. The firewall, cockpit floor, and several fuselage skins were buckled, and elevator travel was restricted. The pilot reported no preimpact mechanical malfunctions or failures with the airplane that would have precluded normal operation.

Aircraft

Registration
N10033
Reported as
Cessna 172S
Category
Airplane
Serial number
172S9797
Built
2005
Airframe hours
3,637
Engine
Lycoming IO-360-L2A, reciprocating
Damage
Substantial damage
Flight
Instructional · Part 91
Operator
Channel Islands Aviation
Registered owner
Adventure Air
Airworthiness certificate
Standard, Normal
Last inspection
Continuous airworthiness · August 8, 2014 · 14 hours before
Departed
CMR · Camarillo, CA
Destination
IZA · Santa Ynez, CA
Airport
IZA · Santa Ynez, runway 26, 2,803 × 75 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
Student pilot
Age
59
Injuries
None
Certificate
Student
Medical
Class 1, Without waivers/limitations
Seat
Left
Restraint
3-point
Flight hours
99 total · 99 in this make and model · 10 as pilot in command · 25 in the last 90 days · 5 in the last 30 days · 1 in the last 24 hours

Weather

Conditions
Visual (VMC) · Day
Wind
260° at 13 knots, gusting 16
Visibility
10 statute miles
Lowest ceiling
None
Temperature
90 °F, dew point 50 °F
Altimeter
29.96 inHg
Observed at
iza

Docket · 5

The files NTSB released with the investigation on October 16, 2014, on NTSB’s docket system: statements, records, photos and specialists’ reports. 2.5 MB 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.