- Date
- July 27, 2017, 13:30 local (20:30 UTC)
- Place
- San Andreas, CA
- Injuries
- 1 uninjured
- Damage
- Substantial damage
- Phase of flight
- Landing
- Aircraft
- N5596CCessna 170
- Defining event
- Landing: Hard landing
- Weather
- Visual (VMC) · Day
- Status
- Completed · report November 14, 2017
- Report
- Approved by Office Director
- NTSB office
- General Aviation Accidents
- Parties
- FAA
- FAA report
- 20170727010109A
- Case key
- 95682
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 landing flare during an aborted go-around in gusting wind conditions, which resulted in a hard landing.
Findings · 4
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.
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 of the tailwheel-equipped airplane reported that he landed on the main wheels, and while waiting for the tailwheel to drop, the "tailwheel jammed." He added that, when the tailwheel touched down, the airplane was difficult to control and veered to the left. He corrected for the veer, but the airplane veered to the right. He then conducted a go-around; however, once airborne, the airplane "did not appear to be producing proper power." He then aborted the go-around and opted to land on the remaining runway. About 25 ft above the runway, he set the airplane up for a wheel landing and descended. When the airplane was about 5 to 10 ft above the runway, the airplane "abruptly" sank and landed hard, and the main landing gear collapsed. Subsequently, the airplane came to rest nose down on the runway. The airplane sustained substantial damage to the fuselage. During a telephone interview, the pilot reported that he believed the tailwheel had jammed before touchdown and that he had previously redesigned and altered the tailwheel. Further, the airplane produced insufficient power during the go-around. He reported that the tailwheel was mechanically "okay" when examined after the accident. Additionally, an airframe and powerplants mechanic reported that he examined the tailwheel assembly after the accident and found no defects and no binding. The pilot reported that the weather at the accident airport, about the time of the accident, was wind from 320° at 10 knots, gusting to 12 knots. The pilot landed on runway 31. Photographs taken at the accident site showed torsional twisting of the propeller, consistent with the engine producing power at the time of impact. The National Transportation Safety Board did not examine the engine.
Factual narrative
The pilot of the tailwheel-equipped airplane reported that, he landed on the main wheels, and while waiting for the tailwheel to drop, the "tailwheel jammed." He added, that when the tailwheel touched down, the airplane was difficult to control, and veered to the left. He corrected for the veer, but the airplane veered to the right. He then did a go-around, however, once airborne the airplane "did not appear to be producing proper power." He then aborted the go-around, and opted to land on the remaining runway. About 25 ft. above the runway, he set the airplane up for a wheel landing and descended. When the airplane was about 5-10 ft. above the runway, the airplane "abruptly" sank, landed hard and collapsed the main landing gear. Subsequently, the airplane came to rest nose down on the runway. The airplane sustained substantial damage to the fuselage. During a telephone interview, the pilot reported that he believed the tailwheel had jammed prior to touchdown, and that he had previously re-designed and altered the tailwheel. Further, the airplane produced insufficient power during the go-around. He reported that, the tailwheel was mechanically "okay" when inspected after the accident. Additionally, an airframe and powerplant mechanic reported that he inspected the tailwheel assembly after the accident, and found no defects and no binding. The pilot reported the weather at the accident airport, about the time of the accident to be, wind from 320° at 10 knots, gusting to 12 knots. The pilot landed on runway 31. Photographs taken at the accident site showed torsional twisting of the propeller, consistent with the engine producing power at the time of impact. The National Transportation Safety Board did not examine the engine.
Aircraft
- Registration
- N5596C
- Reported as
- Cessna 170 (A)
- Category
- Airplane
- Serial number
- 19650
- Built
- 1950
- Airframe hours
- 4,200
- Engine
- Lycoming O-360-A1A, 180 horsepower, reciprocating
- Damage
- Substantial damage
- Flight
- Personal · Part 91
- Airworthiness certificate
- Standard, Normal
- Last inspection
- Annual · August 27, 2016
- Departed
- HWD · Hayward, CA
- Destination
- CPU · San Andreas, CA
- Airport
- CPU · Calaveras Co-Maury Rasmussen F, runway 31, 3,603 × 60 ft, asphalt
- Equipment
- Stall warning system, ADS-B
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
- 78
- Injuries
- None
- Certificate
- Commercial
- Airplane ratings
- Single-engine sea, Multi-engine sea, Single-engine land, Multi-engine land
- Instrument ratings
- Airplane
- Medical
- Class 3, With waivers/limitations
- Last flight review
- August 26, 2015
- Restraint
- 3-point
- Flight hours
- 28,842 total · 1,724 in this make and model · 11,847 as pilot in command · 6 in the last 90 days · 3 in the last 30 days · 1 in the last 24 hours
Weather
- Conditions
- Visual (VMC) · Day
- Wind
- 300° at 6 knots
- Visibility
- 10 statute miles
- Lowest ceiling
- None
- Temperature
- 99 °F, dew point 59 °F
- Altimeter
- 29.89 inHg
- Observed at
- KSCK, 31 nm away
Docket · 4
The files NTSB released with the investigation on October 19, 2017, on NTSB’s docket system: statements, records, photos and specialists’ reports. 2.1 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.
Other investigations on N5596C · 1
Matched to the same aircraft by N-number and date.