NTSB CAROL · Event
Event LAX96LA296
Aircraft involved
Probable cause & findings
the pilot's failure to initiate a go-around when a landing overshoot became apparent. Factors which contributed to the accident were: the pilot's excessive airspeed and misjudged distance during landing, his lack of flying experience in the Cessna, and overconfidence in his personal ability.
Factual narrative
HISTORY OF FLIGHT
On August 4, 1996, at 1620 hours Pacific daylight time, a Cessna 421C, N6209V, operated by the pilot, overran the departure end of runway 22 during landing rollout at the (uncontrolled) Catalina Airport, Avalon, California. The airplane went down an embankment, collided with rough terrain, and came to rest approximately 120 feet southwest of the runway's end. The airplane was substantially damaged. The private pilot and three passengers were seriously injured, and three additional passengers received minor injuries. Visual meteorological conditions prevailed at the time of the personal flight, and no flight plan was filed. The flight originated from the John Wayne Airport, Santa Ana, California, about 1500. According to the Federal Aviation Administration (FAA), after departing from Santa Ana the pilot proceeded to the Santa Monica Municipal Airport, Santa Monica, California, and arrived there at 1529. The on-duty air traffic controller reported that when the pilot requested landing instructions, he gave him instructions to overfly the airport above 2,000 feet for right traffic to runway 21, and to report abeam the tower on the north side of the airport. The controller stated that the pilot did not comply with his instructions. The pilot descended on the south side of the airport and entered the left-hand traffic pattern. The controller further reported that the pilot landed on runway 21, but he touched down long. The runway's length is 4,987 feet, and the airplane touched down at approximately the 1,000 foot distance remaining marker. After passengers boarded the airplane, the pilot departed for Catalina at 1553. The controller reported that he instructed the pilot to make a right climbing 270-degree turn at the shoreline during climbout. The controller stated that, once again, the pilot did not comply with his instructions. Upon departure, the pilot made a left turn. No further contact was made with the airplane until it approached the Catalina Airport. A pilot-witness, who was standing on the ramp at the Catalina Airport, reported observing the airplane's final approach. The witness stated it appeared that the pilot was flying at a fast airspeed, and he opined that the pilot would be unable to completely decelerate before reaching the runway's end. He stated that as the airplane passed the midfield location, its nose wheel had not been lowered to the pavement. As the airplane neared the departure end of the runway, no evidence of engine power application was heard. Another witness, the acting tower manager, reported that the Cessna's approach "looked good" but it was "a lot faster than most twin-engine airplanes." The airplane "appeared to float," and it did not touchdown until reaching midfield on the 3,240-foot-long runway. An officer from the Los Angeles Country Sheriff's Department responded to the accident site and interviewed the pilot. According to the officer, the pilot reported that he touched down about midfield, and the brakes felt like they were working. When he saw that the airplane was nearing the runway's end, all he could do was to keep applying the brakes because he would not be able to build up enough speed to take off prior to reaching the runway's end. The airplane rolled off the runway's end, floated about 50 feet down an embankment, and slid to a stop.
WRECKAGE EXAMINATION
The FAA and a participant from the Cessna Aircraft Corporation inspected the accident site, the runway, and the airplane. Evidence of tire (rubber transfer) marks was observed on the runway surface which corresponded with the airplane's left and right main landing gear tires. The marks were nearly symmetrical in appearance (length and density). The marks were noted over an approximate 70-yard-long distance from near the runway's end to the southwestern edge of the airport, where the terrain elevation suddenly lowered by about 40 feet. No evidence of malfunctions was found during the examination of the tires, wheels, or brake assemblies.
PERSONNEL INFORMATION
The private pilot's flight time (hours) recorded in the Flight Time Matrix boxes in this factual report were obtained from FAA Form 8710-1, entitled Airman Certificate and/or Rating Application. The hours were reported by the pilot on April 26, 1996, upon his second application for the addition of a multiengine class rating. As indicated on the application form, the pilot reported that his total multiengine flight time (experience) was 23 hours, and the hours were all obtained during dual flight instruction. The flight test was conducted in a Piper PA-34-200 airplane. On May 5, 1996, the pilot was issued a multiengine class rating. The National Transportation Safety Board was not able to determine the pilot's experience level (flight hours) in the Cessna 421C airplane.
ADDITIONAL INFORMATION
On August 8, 1996, the Safety Board mailed the pilot a letter requesting that he complete the required "Pilot/Operator Aircraft Accident Report" NTSB Form 6120.1/2. On October 22, 1996, the Safety Board requested to speak with the pilot via telephone and left a message at his residence. On October 30, 1996, the FAA mailed the pilot a letter requesting that he make his flight records available for examination. As of March 1997, the pilot has not responded to either the NTSB or the FAA's requests. According to the airport's acting tower manager, the airplane's landing approach 'looked good' but was 'a lot faster than most twin-engine airplanes.' The airplane 'appeared to float,' and it did not touchdown until reaching midfield on the 3,240-foot-long runway. A pilot-witness who was standing on the ramp similarly reported that the airplane's approach speed was fast, and also noted that as the airplane passed midfield its nose wheel had not been lowered to the pavement. The pilot report that after touchdown he applied brakes, and although the airplane slowed he was unable to stop before exiting off the runway's departure end. The airplane went down an embankment, collided with rough terrain, and came to rest approximately 120 feet southwest of the runway's end. The pilot previously had landed at the Santa Monica Municipal Airport. According to the FAA, at Santa Monica the airplane touched down about 1,000 feet prior to the end of that 4,987-foot-long runway. Three months earlier, the pilot received a multiengine class rating. At that time, he indicated his total multiengine flying experience was 23 hours of dual instruction. Source: NTSB Aviation Accident Database (Pre-2008 Archive) Retrieved: 2026-02-12
Verbatim from NTSB's published report. Source file
NTSB_1996_LAX96LA296.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 ↗