LAX05CA238
2005-07-18 · Rio Vista, California, United States · None · 1 aircraft · Status: Completed
Airport O88
Current FAA registration · N68475
- Make / Model
- CESSNA 152
- Year of manufacture
- 1978 · 27 years old at event
- Engine
- LYCOMING 0-235 SERIES (115 hp)
- Seats / Engines
- 2 seats · 1 engine
- Last airworthiness date
- 19780809
- ADS-B equipped
- Yes — Mode-S A9157E
Source: FAA Aircraft Registry (releasable master file).
Aircraft involved
Probable cause & findings
the student pilot's inadequate recovery from a bounced landing and his failure to maintain directional control of the airplane during landing rollout. A contributing factor was the student's failure to divert to an airport with less severe crosswind conditions.
Factual narrative
On July 18, 2005, about 0910 Pacific daylight time, a Cessna 152, N68475, bounced upon touchdown at the Rio Vista Municipal Airport (O88), Rio Vista, California. During the subsequent rollout, the airplane veered off the side of the runway onto the grass and nosed over. California In Nice, Inc., was operating the airplane under the provisions of 14 CFR Part 91. The student pilot was not injured; the airplane sustained substantial damage. The initial solo cross-country flight departed Reid-Hillview Airport (RHV), San Jose, California, about 0830 with planned intermediate destinations of Rio Vista, the Oakdale Airport (O27), Oakdale, California, and a final destination of San Jose, California. Visual meteorological conditions prevailed, and a visual flight rules (VFR) flight plan had been filed. In a written statement, the student pilot stated that he obtained a standard weather briefing and filed a flight plan with the Flight Service Station (FSS) before the flight. From the briefing, he learned that there was a Notice To Airmen (NOTAM) issued for Rio Vista pertaining to the closing of runways 7 and 25. The student pilot reported that upon arrival to Rio Vista, he made a radio call in an attempt to obtain a traffic advisory; however, he did not receive a response. He then flew over the field at 2,200 feet to identify the wind direction by checking the windsock. He determined that the windsock was indicating a crosswind condition for runways 14 and 32, and decided to land on runway 32. While on approach to runway 32, he realized that the winds were very strong, which made it difficult to land, and decided to execute a go-around. On the second approach attempt, the student pilot decreased the airplane's airspeed to approximately 60 knots, and still found the winds to be very strong making the aircraft difficult to control. Shortly thereafter, the airplane made contact with the runway, bounced four times, and the student pilot lost control of the airplane. During the rollout, the airplane veered off the side of the runway onto the grass and nosed over. The resulting damage was to the nose wheel, propeller, engine, and firewall. In his statement, the student pilot also reported that he talked to an airport employee following the accident who notified him that runways 7 and 25 had reopened; therefore making the NOTAM he received in his weather briefing outdated. He felt that if he had received the correct information, he would have used the correct runway given the wind conditions, and the landing would have been successful. The student pilot stated that the airplane and engine had no mechanical failures or malfunctions during the flight. In a telephone conversation, the student pilot's certified flight instructor (CFI) reported that he gave the student pilot a preflight briefing. They discussed his planned route of flight, and the information that he received from the standard weather briefing. In the weather briefing, the student pilot was told that Rio Vista reported that the winds were calm, and that a NOTAM was issued pertaining to the closure of runways 7 and 25. During their discussion of the NOTAM, the CFI told the student pilot to divert to Oakdale if he could not make the landing into Rio Vista, California. The student pilot bounced the airplane during touchdown, lost direction control, veered off the runway, and nosed over. During the approach, the pilot realized that the crosswind was very strong, which made control difficult, and he decided to execute a go around. On the second approach attempt, he decreased the airplane's airspeed to approximately 60 knots, and still found the crosswind to be very strong, making the airplane difficult to control. Shortly thereafter, the airplane made contact with the runway and bounced four times. The student pilot lost directional control of the airplane and it veered off the side of the runway onto the grass median and nosed over. During the preflight briefing with his CFI, the instructor told the student pilot to divert to another airport if he could not make the landing into Rio Vista, California. The pilot stated that the airplane and engine had no mechanical failures or malfunctions during the flight. Source: NTSB Aviation Accident Database (Pre-2008 Archive) Retrieved: 2026-02-12
Verbatim from NTSB's published report. Source file
NTSB_2005_LAX05CA238.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…