20100407031439A

Accident · Substantial damage

FAA accident report · Cessna 170B · Columbia, CA · April 7, 2010

Date
April 7, 2010 · 15:30 local
Place
Columbia, CA
Airport
Columbia
Phase of flight
Landing: Rollout
Operating rules
General operating rules (Part 91)
Damage
Substantial damage
Aircraft
N2629D
NTSB investigation
NTSBWPR10LA194
Reported as
Cessna 170B
Reported engine
Lycoming 0-360
People aboard
3
Fatal injuries
0
Other injuries
0
Pilot’s certificates
Commercial pilot, flight instructor
Pilot’s flight hours
8,446 total92 in this make and model60 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.

Parapharsed pilot statementon April 7th, 2010 a Cessna 170 N-2629D departed Columbia, CA and flew the aircraft to a local practice area and demonstrated various flight characteristics of the Cessna 170. Thelocal AWOS had reported the winds at 160 at 6 knts. Skies clear. The pilot then flew the aircraft back to the Columbia Airport and made a standard pattern andapproach to runway 17 and executed a three point landing with no adverse results. The pilot then taxied back to the departure end of runway 17 to demonstrate the 170'S climb performance. The aircraft remained in the pattern for another landing on 17. Carburetor heat was applied and airspeed was established at 70 mph and 20 degrees of flaps. Upon reaching the touchdown area I transitioned the aircraft into a three point landing configuration while maintaining runway heading. On the rollout the airplane started a slight turn to the left and the pilot applied a bit of right rudder for correction and at that point the aircraft continued to turn to the right. The pilot then immediately applied full power and left rudder with no result from either input. The aircraft continued to turn to theright and the left wingtip contacted the runway surface. The left wingtip then contacted the soft soil off the right side of the runway and forced the aircraft up on to its nose. At this point there was little momentum but enough for the plane to spill over onto its back.

As the FAA filed it

PARAPHARSED PILOT STATEMENTON APRIL 7TH, 2010 A CESSNA 170 N-2629D DEPARTED COLUMBIA, CA AND FLEW THE AIRCRAFT TO A LOCAL PRACTICE AREA AND DEMONSTRATED VARIOUS FLIGHT CHARACTERISTICS OF THE CESSNA 170. THELOCAL AWOS HAD REPORTED THE WINDS AT 160 AT 6 KNTS. SKIES CLEAR. THE PILOT THEN FLEW THE AIRCRAFT BACK TO THE COLUMBIA AIRPORT AND MADE A STANDARD PATTERN ANDAPPROACH TO RUNWAY 17 AND EXECUTED A THREE POINT LANDING WITH NO ADVERSE RESULTS. THE PILOT THEN TAXIED BACK TO THE DEPARTURE END OF RUNWAY 17 TO DEMONSTRATE THE 170'S CLIMB PERFORMANCE. THE AIRCRAFT REMAINED IN THE PATTERN FOR ANOTHER LANDING ON 17. CARBURETOR HEAT WAS APPLIED AND AIRSPEED WAS ESTABLISHED AT 70 MPH AND 20 DEGREES OF FLAPS. UPON REACHING THE TOUCHDOWN AREA I TRANSITIONED THE AIRCRAFT INTO A THREE POINT LANDING CONFIGURATION WHILE MAINTAINING RUNWAY HEADING. ON THE ROLLOUT THE AIRPLANE STARTED A SLIGHT TURN TO THE LEFT AND THE PILOT APPLIED A BIT OF RIGHT RUDDER FOR CORRECTION AND AT THAT POINT THE AIRCRAFT CONTINUED TO TURN TO THE RIGHT. THE PILOT THEN IMMEDIATELY APPLIED FULL POWER AND LEFT RUDDER WITH NO RESULT FROM EITHER INPUT. THE AIRCRAFT CONTINUED TO TURN TO THERIGHT AND THE LEFT WINGTIP CONTACTED THE RUNWAY SURFACE. THE LEFT WINGTIP THEN CONTACTED THE SOFT SOIL OFF THE RIGHT SIDE OF THE RUNWAY AND FORCED THE AIRCRAFT UP ON TO ITS NOSE. AT THIS POINT THERE WAS LITTLE MOMENTUM BUT ENOUGH FOR THE PLANE TO SPILL OVER ONTO ITS BACK.

NTSB investigation

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

Other reports on N2629D · 1

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