# NTSB LAX06LA269: Cessna TR182, N2526S, San Carlos, CA, August 20, 2006 - Type: NTSB accident investigation - Classification: Accident · No injuries · Limited investigation · Final report - Date: August 20, 2006, 12:58 local (19:58 UTC) - Place: San Carlos, CA - Coordinates: 37.506942, -122.243057 - Nearby events: https://openairdocs.org/map.md?lat=37.5069&lon=-122.2431&mi=10 - Phase of flight: [Landing](https://openairdocs.org/ntsb-phases/550) (OpenAirDocs' grouping) - Highest injury: No injuries - Injuries: 2 uninjured - Status: Completed, report February 28, 2008 - Report: Approved by Office Director - Parties: Federal Aviation Administration - NTSB case key (mKey): 64369 - NTSB case page: https://web.ntsb.gov/investigations/?ntsbnumber=LAX06LA269 - NTSB report (PDF, downloads): https://data.ntsb.gov/carol-repgen/api/Aviation/ReportMain/GenerateNewestReport/64369/pdf - Page: https://openairdocs.org/ntsb/LAX06LA269 ## Probable cause The pilot's inadequate compensation for the crosswind condition and failure to maintain directional control during the landing roll. ## Sequence of events In NTSB's coding before 2008 (https://www.ntsb.gov/GILS/Documents/codman.pdf). - Loss of control - on ground/water, landing - roll - compensation for wind conditions - inadequate, pilot in command (cause) - weather condition - crosswind - directional control - not maintained, pilot in command (cause) - In flight collision with object, landing - aborted - aborted landing - performed, pilot in command - object - airport sign/marker (contributing factor) ## Analysis The pilot landed on the runway 30 centerline with 20 degrees of flaps and an airspeed of 65 knots. After a ground roll of 100 feet 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 then struck a sign during the climb out. After a flyby to check the landing gear position, the pilot again landed on runway centerline, and about 3/4 of the way down the runway he began to apply the brakes. The pilot discovered that the brakes were not working and the airplane veered off the right side of the runway and struck a taxiway sign. The airplane finally came to a stop in front of transient parking. Reported winds were from 360 degrees at 14 knots. No gusts were reported. ## Factual narrative 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. ## Aircraft - Registration: [N2526S](https://openairdocs.org/aircraft/N2526S), registered now, S/N R18201347, built 1979 (OpenAirDocs) - Reported make and model: Cessna TR182 - Registry model: [Cessna TR182](https://openairdocs.org/model/cessna-tr182) (registry code 2072735) (OpenAirDocs) - Registry engine: [Lycoming 0-540 series](https://openairdocs.org/engine/lycoming-0-540-series) (registry code 41532, reciprocating) (OpenAirDocs) - Category: Airplane - Serial number: R18201347 - Airframe hours: 3071.2 - Engines: Lycoming O-540-L3 235 horsepower reciprocating - Damage: Substantial damage - Flight: Personal, Part 91 - Airworthiness certificate: Standard, Normal - Last inspection: Annual, September 1, 2005 - Departed: 06U, JACKPOT, NV - Destination: SQL, SAN CARLOS, CA - Airport: SQL, San Carlos, runway 30, 2,600 × 75 ft, asphalt ## Flight crew As NTSB recorded them. NTSB leaves out names. - Pilot; age 49; injuries: none; private; airplane ratings: single-engine land; medical: class 3, without waivers/limitations; last flight review October 1, 2005; seat: left; flight hours: 737 total, 349 in this make and model, 682 as pilot in command, 41 in the last 90 days, 15 in the last 30 days, 7 in the last 24 hours ## Weather - Conditions: Visual (VMC), Day - Wind: 360° at 14 knots - Visibility: 10 statute miles - Temperature: 66 °F, dew point 57 °F - Altimeter: 29.97 inHg - Observed at: SQL ## FAA reports on this event (1) The FAA's own accident and incident reports, matched to the aircraft by N-number and date (OpenAirDocs). - [Accident 20060820018759A](https://openairdocs.org/incident/20060820018759A), Aug 20, 2006: Cessna TR182, San Carlos, CA, Substantial damage. (-23) The pilot lost control during the landing flare due to a gusting crosswind condition. The aircraft struck a taxiway sign, and the pilot elected to abort… From the NTSB's public API. Aircraft are matched to registry aircraft by N-number and event date, checked against the reported serial number, make and model; the registry's history has gaps, so older matches can be wrong. Compare the reported make and model. --- OpenAirDocs.org is an independent research project of [Contrail Labs](https://contraillabs.com/). It is not affiliated with the FAA or the NTSB. Source documents are U.S. government works in the public domain.