NTSB CAROL · Event
Event LAX96LA182
Aircraft involved
Probable cause & findings
the pilot's inadequate compensation for the wind conditions, his use of an overly excessive approach speed, and his misjudged distance/altitude relationship to the runway. The wind was a factor.
Factual narrative
On April 11, 1996, at 1605 hours mountain standard time, a Cessna 402C, N172VB, overran runway 32 while landing at the St. Johns Industrial Airpark, St. Johns, Arizona, and collided with the terrain. The airplane was substantially damaged and the airline transport rated pilot was not injured. The airplane was operated as a business flight by Bank One Arizona, Phoenix, Arizona, under 14 CFR Part 91. The flight originated from the Deer Valley Airport in Phoenix about 1500. Visual meteorological conditions prevailed at the time. The airplane was dispatched on a company visual flight rules (VFR) flight plan. The pilot indicated the St. Johns UNICOM operator reported the surface winds were from 260 to 280 degrees with gusty winds at 30 to 40 knots. He decided to increase his final approach speed by 15 knots to compensate for the gust spread and crosswind. He descended on final approach using the VASI system as a glide path reference. After touchdown the airplane bounced and floated, and touched down again in the middle 1/3 of the runway. The pilot was concentrating on maintaining runway alignment on the centerline and did not notice how much runway was remaining. After clearing a slight rise, he saw the departure end of the runway and realized there was insufficient runway remaining to stop or execute a go-around. The departure end of runway 32 drops off about 9.5 feet. When the airplane reached the departure end it became airborne and cleared the airport perimeter fence, which is lower than the runway, and landed in a uneven field about 80 feet from the runway end. The airplane traveled another 160 feet, at which time the nose gear collapsed. The airplane continued to move on the nose and main landing gear for another 152 feet before coming to rest. The St. Johns AWOS recorded winds 50 minutes after the accident were from 260 degrees at 33 knots gusting to 45 knots. The pilot decided to increase his final approach speed by 15 knots to compensate for the gust spread and crosswind. He descended on final approach using the VASI system as a glide path reference. After touchdown the airplane bounced and floated, and touched down again in the middle 1/3 of the 5,323-foot runway. The pilot did not notice how much runway was remaining. After clearing a slight rise, he saw the departure end of the runway and realized there was insufficient runway remaining to stop or execute a go-around. The airplane ran off the end of the runway. The AWOS recorded winds from 260 degrees at 33 knots gusting to 45 knots. Source: NTSB Aviation Accident Database (Pre-2008 Archive) Retrieved: 2026-02-12
Verbatim from NTSB's published report. Source file
NTSB_1996_LAX96LA182.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 ↗