Stanley, ID, USA
N6353U
CESSNA T210R
The pilot stated that after an uneventful flight he decided to land to the south. He was unable to maintain a stable approach and performed a go-around immediately after touching down. He then made an approach to land to the north. The airplane touched down about 1/3 down the runway with about a 5-knot tailwind. With about 2,300 feet of runway remaining, the pilot immediately applied heavy braking and retracted the wing flaps. The brakes did not respond, and he attempted to rapidly depress and release (pump) them several times. Despite his attempts, the brakes did not function adequately, and he was unable to stop the airplane. The airplane continued off the end of the runway, went down a hill, and collided with trees. A postaccident examination of the brake system revealed no evidence of pre-impact mechanical malfunction or failure. There were no skid marks on the runway surface or flat spots on the tire. There were no signs of hydraulic leaks, and the brake master cylinder had adequate fluid. The right brake was non-operational due to damage to the brake line at the caliper as a result of it striking rocks at the runway's end; the left brake operated normally.
On July 07, 2022, about 1440 Mountain daylight time, a Cessna T210R, N6353U, was substantially damaged when it was involved in an accident near Stanley, Idaho. The pilot and three passengers were not injured. The airplane was operated as a Title 14 Code of Federal Regulations Part 135 on-demand air taxi flight. The pilot stated that after an uneventful flight he entered the proximity of the destination airport about 1,500 ft above ground level. He noted that the airport’s north windsock indicated a direct crosswind, and the south windsock indicated the wind was from the southwest at 10-15 mph. He decided to land on runway 17 and maneuvered the airplane to enter the downwind leg of the traffic pattern around midfield. During the landing phase, he was unable to maintain a stable approach and performed a go-around immediately after touching down. He then made an approach to runway 35 and touched down on the runway surface just past the south windsock (located about 1/3 down the runway). With about 2,300 ft of runway remaining, the pilot immediately applied heavy braking and retracted the wing flaps. The brakes did not respond, and he attempted to rapidly depress and release them (pump) several times. Despite his attempts, the brakes did not function, and he was unable to stop the airplane. The airplane continued off the end of the runway, went down a hill, and collided with trees. The airplane had undergone an annual inspection on July 01, 2022, or 6 days before the accident. Since that maintenance, he had flown the airplane on three flights. Investigators from the Federal Aviation Administration responded to the accident site. One stated there was no evidence of skid marks on the runway and no flat spots on the tires. Their examination of the brake system revealed no signs of hydraulic leaks and the brake master cylinder was approximately two-thirds full. The right brake was non-operational due to damage to the brake line at the caliper as a result of it striking rocks at the runway's end. The left brake appeared to function correctly. The inspectors physically engaged the brakes by pressing the pedals with their feet. One inspector stated that while the brakes weren't exceptionally firm, it was a common characteristic in this make and model airplane. A weather station located 12 miles east of the airport recorded that at the time of the accident, the wind was from the southwest at 8 knots, equating to a tailwind of about 5 knots. The pilot reported the wind was from the southwest at 10-15 knots.
The pilot’s failure to provide adequate braking during a tailwind landing, which resulted in a runway excursion.
Source: NTSB Aviation Accident Database
Aviation Accidents App
In-Depth Access to Aviation Accident Reports
