LAX01LA021
2000-10-22 · HALF MOON BAY, California, United States · Minor · 1 aircraft · Status: Completed
Airport KHAF
N5226K has since been reassigned. It is now registered to a different aircraft (CESSNA T206H, built 2008), which was not involved in this event.
Aircraft involved
Probable cause & findings
A local windshear condition that exceeded the airplane's climb performance capability during landing approach and resulted in the runway overrun during an attempted go-around.
Factual narrative
On October 22, 2000, at 1140 hours Pacific daylight time, a Cessna 172P, N5226K, overran the runway during landing, and collided with a fence at the Half Moon Bay Airport, Half Moon Bay, California. The airplane sustained substantial damage, and the certificated commercial pilot and one of his two passengers received minor injuries. The second passenger was not injured. The airplane owner, d.b.a. Coast Flight, operated the sightseeing flight under the provisions of 14 CFR Part 91. The local flight had originated from the Half Moon Bay airport about 1030. Visual meteorological conditions prevailed at the time, and no flight plan was filed. The pilot reported that as he initiated his approach to runway 30 he noticed strong gusty winds and low-level shear conditions. To compensate, he increased his approach airspeed and left the flaps in their retracted position. While continuing over the approach end of the runway, he encountered an area with a high sink rate. He immediately added full power to stop his descent. With full power, and with the airplane's nose about 5 degrees above the horizon, the airplane began to climb slowly. At this point, the pilot encountered a strong, gusting, right quartering headwind that lifted the right wing and resulted in a loss of altitude. In response, as the airplane touched down beyond the departure end of the runway, the closed the throttle. The airplane rolled through a fence before coming to a stop. Winds at the closest weather reporting station San Francisco International Airport (SFO), were 360 at 18 knots gusting to 22 knots. The airplane collided with a fence during a forced landing. The pilot reported that as he initiated his approach to runway 30 he noticed strong gusty winds and low-level shear conditions. To compensate, he increased his approach airspeed and left the flaps in their retracted position. While continuing over the approach end of the runway, he encountered an area with a high sink rate. He immediately added full power to stop his descent. With full power, and with the airplane's nose about 5 degrees above the horizon, the airplane began to climb slowly. At this point, the pilot encountered a strong, gusting, right quartering headwind that lifted the right wing and resulted in a loss of altitude. In response, as the airplane touched down beyond the departure end of the runway, he closed the throttle. The airplane rolled through a fence before coming to a stop. Winds at the closest weather reporting station San Francisco International Airport (SFO), were 360 at 18 knots gusting to 22 knots. Source: NTSB Aviation Accident Database (Pre-2008 Archive) Retrieved: 2026-02-12
Verbatim from NTSB's published report. Source file
NTSB_2000_LAX01LA021.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…