Plane crash map Locate crash sites, wreckage and more

N2526S accident description

California map... California list
Crash location 37.506944°N, 122.243055°W
Nearest city San Carlos, CA
37.507159°N, 122.260522°W
1.0 miles away
Tail number N2526S
Accident date 20 Aug 2006
Aircraft type Cessna TR182
Additional details: None

NTSB Factual Report

On August 20, 2006, at 1258 Pacific daylight time, a Cessna TR182, N2526S, impacted a runway sign during the takeoff roll on runway 30, following an aborted landing, at San Carlos Airport (SQL), San Carlos, California. The private pilot/owner was operating the airplane under the provisions of 14 Code of Federal Regulations Part 91 as a personal flight. The airplane sustained substantial damage. The pilot and one passenger were not injured. Visual meteorological conditions prevailed for the cross-country flight that departed the Jackpot Airport/Hayden Field (06U), Jackpot, Nevada, at 1030 mountain daylight time. No flight plan had been filed.

The National Transportation Safety Board investigator interviewed the pilot. The pilot reported that several days before the accident he had flown the airplane from SQL to 06U, and on to Kalispell, Montana. He then flew from Kalispell to 06U, and was returning to his home airport when the accident occurred. There were no discrepancies noted with the airplane during any of the flights or landings.

In the pilot's written statement he reported that the approach seemed normal, and over the numbers with 20 degrees of flaps and an airspeed of 65 knots. He landed centerline for runway 30. The pilot stated that a couple of hundred feet down the runway the airplane suddenly veered to the left. Aileron and rudder inputs were ineffective and he decided to go around. He applied full power and retracted 10 degrees of flaps, and the airplane became airborne. The airplane struck a sign during the go-around. He reported to tower personnel that he was having a problem. The tower controller asked him what his intentions were, and he replied that he wanted to return for landing. The controller said that they wanted him to do a low pass to look at the landing gear. After the flyby, tower personnel reported to the pilot that the landing gear appeared to be okay. The pilot stated that the landing gear light was illuminated green. He flew the pattern, and the controller called his base. The controller then cleared him to land. The pilot stated that he again landed on runway centerline, and about 3/4 of the way down the runway he began to apply the brakes. The airplane veered right off the runway and struck a taxiway sign. He was able to stop the airplane, shut it down normally, and exit the airplane. He thought a sudden strong gust of wind struck the airplane on landing. The pilot stated that there were no mechanical problems with the airplane.

The passenger stated that on the first landing the airplane started to veer to the left. She observed the pilot pushing the right rudder in, but the airplane would not correct back to centerline. The pilot informed her that they were going too fast to stop and it would be best to go around and try again. As they took off, the passenger reported hitting something. As they were coming back to land, the pilot stated that something was wrong, but he did not know what. She thought a "huge gust of wind" had blown them off the runway. On the second landing the airplane veered slight to the left, but the pilot was able to correct back to runway centerline. Towards the end of the runway the airplane started to turn to the right. The pilot reported that there was no left brake and that only the right brake was working. The airplane finally came to a stop in front of transient parking.

One witness heard the airplane hit the guidance sign, and as it took off again, he saw it hit a light pole.

Another witness stated that he saw the airplane strike the light pole, and then watched it land the second time.

Airport operations personnel interviewed the pilot. The pilot reported that there was a relatively light crosswind on landing. After landing on the runway centerline, the airplane immediately went to the left side onto the grass. There was enough airspeed, and the pilot decided to go around. The stabilizer struck a light pole. After performing a low approach so that tower personnel could check the landing gear, he landed a second time with no brakes. About 3/4 of the way down the runway he applied the brakes, but stated that he did not "have any." The airplane went off the right side of runway and hit a guidance sign.

Reported winds at SQL were from 360 degrees at 14 knots. No gusts were reported.

NTSB Probable Cause

The pilot's inadequate compensation for the crosswind condition and failure to maintain directional control during the landing roll.

© 2009-2020 Lee C. Baker / Crosswind Software, LLC. For informational purposes only.