CHI01LA187
2001-06-24 · Brooklyn, Michigan, United States · None · 1 aircraft · Status: Completed
Airport 6G8
Current FAA registration · N8210Z
- Make / Model
- PIPER PA-28-181
- Year of manufacture
- 1982 · 19 years old at event
- Engine
- LYCOMING O&VO-360 SER (180 hp)
- Seats / Engines
- 4 seats · 1 engine
- Last airworthiness date
- 19820427
- ADS-B equipped
- Yes — Mode-S AB3702
Source: FAA Aircraft Registry (releasable master file).
Aircraft involved
Probable cause & findings
The proper touchdown point exceeded, all of the available runway not used, and aircraft control not being maintained by the pilot during the landing. Factors to the accident were the pilot mistaking the taxiway for the runway, the pilot not performing a go-around after identifying the runway on final approach, and the ditch.
Factual narrative
On June 24, 2001, at 1258 eastern daylight time, a Piper PA-28-181, N8210Z, piloted by a private pilot, was substantially damaged when the pilot landed long and the airplane overran the end of runway 01 (2,822 feet by 100 feet, dry/turf) at the Shamrock Field Airport, Brooklyn, Michigan. Visual meteorological conditions prevailed at the time of the accident. The personal flight was operating under the provisions of 14 CFR Part 91 and was on an instrument flight rules (IFR) flight plan. The pilot and his single passenger were not injured. The flight departed the MBS International Airport, Saginaw, Michigan at 1145. According to the pilot's written statement, he had initially mistaken the taxiway, located to the left side of the runway, for runway 01 and had identified the correct runway while on final approach. The pilot reported that once he had identified runway 01 he executed a steep approach to the runway, touching down with approximately one half of the useable runway remaining. The pilot stated that, "Approached too high[,] I believe this was where I screwed up big time!" The pilot reported that he was unable to stop the airplane prior to the end of the runway, and the airplane impacted a ditch off to the right side of the end of the runway. The pilot reported that the accident could have been prevented by, "...Stabilized [approach], low speed to soft field to the threshold rather than further infield...Vigilance for threshold confusion in turf fields...Prefer paved fields if never landed on grass before." The airplane was substantially damaged when the pilot landed long and the airplane overran the end of runway, striking some trees. The pilot reported that he had initially mistaken the taxiway, located to the left side of the runway, for runway 01 and had identified the correct runway while on final approach. The pilot stated that once he had identified runway 01 he executed a steep approach to the runway, touching down with approximately one half of the useable runway remaining. The pilot reported that, "Approached too high[,] I believe this was where I screwed up big time!" The pilot reported that he was unable to stop the airplane prior to the end of the runway, and the airplane impacted a ditch off to the right side of the end of the runway. The pilot reported that the accident could have been prevented by, "...Stabilized [approach], low speed to soft field at the threshold rather than further infield...Vigilance for threshold confusion in turf fields...Prefer paved fields if never landed on grass before." Source: NTSB Aviation Accident Database (Pre-2008 Archive) Retrieved: 2026-02-12
Verbatim from NTSB's published report. Source file
NTSB_2001_CHI01LA187.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…