NTSB CAROL · Event
Event LAX06CA128
Registry · N8141L
FAA Aircraft Registry record.
Make / Model
CIRRUS DESIGN SR22
Year of manufacture
2003 · 3 years old at event
TCDS
A00009CH · CIRRUS DESIGN CORP
Engine
CONT MOTOR IO-550 SERIES (300 hp)
Seats / Engines
4 seats · 1 engine
Last airworthiness date
20030902
ADS-B equipped
Yes — Mode-S AB1ABE
Registrant of record
LAND AERIAL SERVICES LLC
Source: FAA Aircraft Registry (releasable master file).
Aircraft involved
Probable cause & findings
the pilot's inadequate compensation for the wind conditions and failure to maintain directional control.
Factual narrative
On March 9, 2006, at 2130 mountain standard time, a Cirrus SR22, N8141L, veered off the runway during landing and collided with a taxiway light and a runway sign at Scottsdale Airport, Scottsdale, Arizona. The commercial pilot, who was also the registered owner of the airplane, was operating it as a personal flight under the provisions of 14 CFR Part 91. The airplane sustained substantial damage; the pilot, the sole occupant, was not injured. The pilot departed from Lubbock Preston Smith International Airport, Lubbock, Texas, on an instrument flight rules (IFR) flight plan and was landing at his destination when the accident occurred. Visual meteorological conditions prevailed in the vicinity of the Scottsdale area where the pilot canceled his IFR flight plan and landed at Scottsdale under visual flight rules. The pilot stated that upon canceling his IFR flight plan, he entered the right downwind for a visual approach to runway 21 at Scottsdale. As he attempted to bring the airplane to a stop, it began to veer to the left side of the runway in the gusting winds. The gusts exceeded the limitations of the airplane, and as the airplane slowed, the pilot could not maintain effective rudder control. The airplane departed the runway surface and collided with a taxiway light and a runway sign. The pilot suggested that the accident could have been prevented if he had executed a balked landing and had gone around for another approach. By the time he realized that he was not going to be able to stop the airplane on the runway, it was too late to execute a go-around procedure. The pilot reported that there were no mechanical malfunctions or failures with the airplane. Post accident examination of the airplane showed that a 1-foot by 1-foot area on the lower, inboard portion of the left wing was punctured during the accident sequence. Airport personnel reported that the winds were from 250 at 9 knots, gusting to 15 at the accident location. At 2153, an aviation routine weather report (METAR) at Scottsdale reported the following wind conditions: 250 degrees at 8 knots. Airport personnel stated that this weather-recording device is located on the opposite end of the airport from the location of the accident site. The aircraft has a fully castering nose wheel and directional control is maintained by differential braking and rudder. The airplane veered off the runway during landing and collided with a taxiway light and a runway sign. The aircraft has a fully castering nose wheel and directional control is maintained by differential braking and rudder. The pilot said that as he attempted to bring the airplane to a stop after touchdown it began to veer to the left side of the runway in the gusting crosswinds. As the airplane slowed, the pilot could not maintain effective rudder control. The airplane departed the runway surface and collided with a taxiway light and a runway sign, resulting in a 1-foot by 1-foot puncture damage on the lower inboard portion of the left wing. The pilot suggested that the accident could have been prevented if he had executed a balked landing and had gone around for another approach. By the time he realized that he was not going to be able to stop the airplane on the runway, it was too late to execute a go-around procedure. The pilot reported that there were no mechanical malfunctions or failures with the airplane. The winds were from 250 degrees at 8 knots, gusting to 15 knots, at the time of the accident. Source: NTSB Aviation Accident Database (Pre-2008 Archive) Retrieved: 2026-02-12
Verbatim from NTSB's published report. Source file
NTSB_2006_LAX06CA128.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 ↗