20100725055579A

Accident · Substantial damage

FAA accident report · Cessna 172S · Santa Maria, CA · July 25, 2010

Date
July 25, 2010 · 13:00 local
Place
Santa Maria, CA
Phase of flight
Landing: Touchdown
Operating rules
General operating rules (Part 91)
Damage
Substantial damage
Aircraft
N172CY
NTSB investigation
NTSBWPR10CA475
Reported as
Cessna 172S
Reported engine
Lycoming I0360 SER A&C
People aboard
1
Fatal injuries
0
Other injuries
0
Pilot’s certificate
Student
Pilot’s flight hours
35 total29 in this make and model0 in the last 90 days

From the FAA’s Accident/Incident Data System (AIDS), through its Aviation Safety Information Portal, as reported. The NTSB investigates accidents separately, and its record of an accident is the fuller one. The aircraft is matched to the registry by N-number and event date, checked against the reported make and model; the registry’s history has gaps, so older matches can be wrong. Compare the reported make and model.

What happened

The FAA’s narrative, in sentence case. The FAA writes it in capitals and removes private details.

NTSB did not notify FAA of accident. FAA unaware of accident until 2/9/2011.NTSB report states, "the solo student pilot reported that he made a 40 minute flight to the destination airport in order to meet a family member for lunch. In order to initiate the landing flare, he pulled back on the control yoke, but the airplane's nose pitched up more than he expected. The pilot stated that he corrected for the higher than expected pitch attitude by pushing forward on the yoke, resulting in the airplane's nose wheel being "dropped" onto the runway surface. After contacting the runway surface, the nose wheel porpoised (bounced) one time before contacting the surface a final time. The pilot was ultimately able to stabilize the airplane by applying back pressure to the control yoke. Although he did not become aware of it until he returned to his initial point of departure, the airplane's nose wheel hadstruck the runway surface with sufficient force to buckle the lower part of the firewall and the forward portion of the floorboard. Thepropeller had also come in contact with the runway surface. The pilot reported no mechanical failures or malfunctions with the airplaneat the time of the accident."

As the FAA filed it

NTSB DID NOT NOTIFY FAA OF ACCIDENT. FAA UNAWARE OF ACCIDENT UNTIL 2/9/2011.NTSB REPORT STATES, "THE SOLO STUDENT PILOT REPORTED THAT HE MADE A 40 MINUTE FLIGHT TO THE DESTINATION AIRPORT IN ORDER TO MEET A FAMILY MEMBER FOR LUNCH. IN ORDER TO INITIATE THE LANDING FLARE, HE PULLED BACK ON THE CONTROL YOKE, BUT THE AIRPLANE'S NOSE PITCHED UP MORE THAN HE EXPECTED. THE PILOT STATED THAT HE CORRECTED FOR THE HIGHER THAN EXPECTED PITCH ATTITUDE BY PUSHING FORWARD ON THE YOKE, RESULTING IN THE AIRPLANE'S NOSE WHEEL BEING "DROPPED" ONTO THE RUNWAY SURFACE. AFTER CONTACTING THE RUNWAY SURFACE, THE NOSE WHEEL PORPOISED (BOUNCED) ONE TIME BEFORE CONTACTING THE SURFACE A FINAL TIME. THE PILOT WAS ULTIMATELY ABLE TO STABILIZE THE AIRPLANE BY APPLYING BACK PRESSURE TO THE CONTROL YOKE. ALTHOUGH HE DID NOT BECOME AWARE OF IT UNTIL HE RETURNED TO HIS INITIAL POINT OF DEPARTURE, THE AIRPLANE'S NOSE WHEEL HADSTRUCK THE RUNWAY SURFACE WITH SUFFICIENT FORCE TO BUCKLE THE LOWER PART OF THE FIREWALL AND THE FORWARD PORTION OF THE FLOORBOARD. THEPROPELLER HAD ALSO COME IN CONTACT WITH THE RUNWAY SURFACE. THE PILOT REPORTED NO MECHANICAL FAILURES OR MALFUNCTIONS WITH THE AIRPLANEAT THE TIME OF THE ACCIDENT."

NTSB investigation

The NTSB’s investigation of this event, with its probable cause and findings. Matched to this report by N-number and date.