LAX96LA176
1996-04-23 · TUCSON, Arizona, United States · None · 1 aircraft · Status: Completed
Airport E14
Current FAA registration · N333JS
- Make / Model
- BELLANCA 7KCAB
- Year of manufacture
- 1977 · 19 years old at event
- Engine
- LYCOMING AEIO-320 SER (160 hp)
- Seats / Engines
- 2 seats · 1 engine
- Last airworthiness date
- 19770525
- ADS-B equipped
- Yes — Mode-S A3A1CD
Source: FAA Aircraft Registry (releasable master file).
Aircraft involved
Probable cause & findings
failure of the pilot to adequately compensate for gusting crosswind conditions and to maintain directional control. A factor in the accident was unattended construction equipment parked in close proximity to the runway edge.
Factual narrative
On April 23, 1996, at 0825 hours mountain standard time, a Bellanca 7KCAB, N333JS, collided with a back hoe after landing on runway 12 at the Avra Valley airport, Tucson, Arizona. The airplane sustained substantial damage and the certificated private pilot and passenger were not injured. The airplane was being operated as a personal flight. The flight originated from the La Cholla Airpark in Tucson about 0755 hours. Visual meteorological conditions prevailed at the time. The pilot indicated he entered the downwind leg of the airport traffic pattern and noted the windsock was indicating calm winds. He completed the normal rectangular traffic pattern with no indications of the wind conditions changing. He also stated that a gust of wind from the west raised the right wing, allowing the airplane to drift left as it touched down. The pilot immediately applied right aileron and rudder. The wings returned to level and the airplane continued to drift left towards the left shoulder of the runway. He added power and then removed it when he saw a back hoe adjacent to the runway in his path. He was attempting to steer the airplane clear with the rudder pedals when the left wing collided with the back hoe. The pilot stated that the back hoe was parked with the engine running unattended about 20 to 30 feet from the runway's edge. The pilot remained with the airplane for several hours after the accident. During that period he noted the windsock would indicate calm winds with periodic shifting gusts above 15 miles per hour. The pilot entered the downwind leg of the traffic pattern and noted that the windsock was indicating calm winds. He completed the normal rectangular traffic pattern with no indications of the wind conditions changing. During touchdown a gust of wind from the west raised the right wing, allowing the airplane to drift left. The pilot unsuccessfully attempted to correct the drift and then attempted a go-around. The pilot aborted the go-around when he saw a back hoe in his path. The airplane's left wing then collided with the back hoe, which was parked unattended about 20 to 30 feet from the runway's edge. After the accident, the winds were noted to shift periodically with gusts above 15 miles per hour. Source: NTSB Aviation Accident Database (Pre-2008 Archive) Retrieved: 2026-02-12
Verbatim from NTSB's published report. Source file
NTSB_1996_LAX96LA176.txt.
Findings + structured fields enriched from FAA avall.mdb.
Full investigation docket on
data.ntsb.gov ↗.
Search this event elsewhere
External sources are reported, not agency: signal that something happened, not fact about what happened.
- TallyAero Live Wire Aviation press
- NTSB CAROL Agency ↗
- NTSB Docket Agency ↗
- Aviation Safety Network Aviation press ↗
- Kathryn's Report Aviation press ↗
- Aviation Herald Aviation press ↗
- AVweb Aviation press ↗
- Pilots of America Community ↗
- Reddit /r/flying Community ↗
- FlightAware Aviation press ↗
- AOPA accident database Aviation press ↗
- Google News News ↗
- DuckDuckGo News ↗
Related research
Matched on aircraft type or causal vocabulary (go-around). All research papers
- 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…