NTSB CAROL · Event
Event LAX06LA269
Registry · N2526S
FAA Aircraft Registry record.
Make / Model
CESSNA TR182
Year of manufacture
1979 · 27 years old at event
Engine
LYCOMING 0-540 SERIES (250 hp)
Seats / Engines
4 seats · 1 engine
Last airworthiness date
19791112
ADS-B equipped
Yes — Mode-S A26227
Registrant of record
PLANE NUTZ LLC
Source: FAA Aircraft Registry (releasable master file).
Aircraft involved
Probable cause & findings
The pilot's inadequate compensation for the crosswind condition and failure to maintain directional control during the landing roll.
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. 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. Source: NTSB Aviation Accident Database (Pre-2008 Archive) Retrieved: 2026-02-12
Verbatim from NTSB's published report. Source file
NTSB_2006_LAX06LA269.txt.
Findings + structured fields enriched from FAA avall.mdb.
Full investigation docket on
data.ntsb.gov ↗.
Beyond the agency record
Search this event elsewhere.
Pre-filled searches into the sources where news + community discussion of aviation events lives. External sources are reported, not agency. Treat them as signal that something happened, not as fact about what happened.
Entity-clustered aviation events in the press — last 24 hr + 30-day archive.
Official agency record + docket.
Investigative docket: factual reports, photos, transcripts.
Long-running aviation incident database (Flight Safety Foundation).
Community NTSB synthesis blog — often has photos and witness reports.
Gold-standard aviation incident blog.
Aviation industry news search.
GA pilot forum — informed but rumor-prone.
GA pilot subreddit search.
Tail-number page — flight history (free tier limited).
AOPA Air Safety Institute search.
Mainstream press coverage. Recent events only.
Privacy-preserving news search.
External links open in a new tab. We don't ingest their content; we deep-link search queries.
Related research
What the literature says.
Academic papers and agency reports matching this event's aircraft type or causal vocabulary (go-around). Sourced from NASA NTRS, NTSB Safety Studies, FAA CAMI, AOPA Air Safety Institute, Embry-Riddle Scholarly Commons, arXiv, and the Semantic Scholar academic graph.
- NASA NTRS 2025 · Conference Paper
A Training Study to Improve Monitoring During A Go-Around
As part of an FAA program to improve go-around (GA) safety, we were asked to determine if we could improve the performance of the Pilot Monitoring (PM) during a GA maneuver.
- Flight Safety Foundation 2024 · FSF / AeroSafety World
Go-Around Safety Forum Findings
Foundation Go-Around Safety Forum technical findings — examines why pilots fail to execute go-arounds when criteria are met (stabilized approach gate not met, energy state out of envelope, traffic con…
- Semantic Scholar 2022 · Article (Journal of Safety Research)
Go-around accidents and general aviation safety.
INTRODUCTION Changes in General Aviation (GA) accident rates, specifically in the go-around phase, are examined by comparing the number of accidents, the proportion of fatal accidents, and the proport…
- Semantic Scholar 2021 · Article (Aerospace)
Classification and Analysis of Go-Arounds in Commercial Aviation Using ADS-B Data
Go-arounds are a necessary aspect of commercial aviation and are conducted after a landing attempt has been aborted. It is necessary to conduct go-arounds in the safest possible manner, as go-arounds …
- NASA NTRS 2021 · Accepted Manuscript (Version with final changes)
Go-Around Criteria Refinement for Transport Category Aircraft
Presently, airline pilots are trained to go around if, when lower than 500 ft above the ground, they are outside of a handful of parameters such as airspeed, position, and rate of descent.
- NASA NTRS 2019 · Conference Paper
Validation of Proposed Go-Around Criteria Under Various Environmental Conditions
This paper evaluates the effects of environmental conditions on touchdown performance under varying approach states and validates proposed go-around criteria developed using data from a previously con…
Browse the full corpus — academia portal ↗