CHI04CA165
2004-06-26 · Fishers, Indiana, United States · None · 1 aircraft · Status: Completed
Airport UMP
Current FAA registration · N229ME
- Make / Model
- CESSNA 172S
- Year of manufacture
- 2000 · 4 years old at event
- Engine
- LYCOMING I0360 SER (180 hp)
- Seats / Engines
- 4 seats · 1 engine
- Last airworthiness date
- 20000523
- ADS-B equipped
- Yes — Mode-S A20388
Source: FAA Aircraft Registry (releasable master file).
Aircraft involved
Probable cause & findings
The pilot's inadequate remedial actions after an inadequate landing flare and subsequent hard landing. Additional causes were the pilot-induced porpoise and the collapse of the nose landing gear.
Factual narrative
On June 26, 2004, at 1150 eastern standard time, a Cessna 172S, N229ME, piloted by a student pilot, sustained substantial damage when the nose landing gear collapsed during a landing attempt on runway 33 (3,850 feet by 100 feet, asphalt) at the Indianapolis Metropolitan Airport (UMP), near Fishers, Indiana. Visual meteorological conditions prevailed at the time of the accident. The solo instructional flight was operating under the provisions of 14 CFR Part 91 without a flight plan. The pilot was not injured. The local flight departed UMP at 1000. The student pilot reported that he had practiced maneuvers in the local area prior to returning to the airport to practice short-field landings. The pilot stated the accident occurred during the third landing attempt. The pilot reported he crossed the runway threshold approximately 100 feet above ground level, and then reduced engine power to idle to initiate the descent to the runway. The pilot stated that during the landing flare the airplane touched down with a "mild impact," which was followed by the airplane bouncing back into the air. The pilot reported he continued to flare, with no addition of engine power, and the second touchdown was "harder than the first." The pilot stated, "No correction action attempted and third touchdown broke nose wheel, prop hit pavement and plane came to stop." The pilot reported the accident could have been prevented if he had performed a go-around after experiencing the initial hard touchdown and subsequent bounce. The airplane experienced a hard landing, which was followed by a pilot-induced porpoise and the collapse of the nose landing gear. The student pilot was flying solo at the time of the accident. The pilot reported he crossed the runway threshold approximately 100 feet above ground level, and then reduced engine power to idle to initiate the descent to the runway. The pilot stated that during the landing flare the airplane touched down with a "mild impact," which was followed by the airplane bouncing back into the air. The pilot reported he continued to flare, with no addition of engine power, and the second touchdown was "harder than the first." The pilot stated, "No correction action attempted and third touchdown broke nose wheel, prop hit pavement and plane came to stop." He reported the accident could have been prevented if he had performed a go-around after experiencing the initial hard touchdown and subsequent bounce. Source: NTSB Aviation Accident Database (Pre-2008 Archive) Retrieved: 2026-02-12
Verbatim from NTSB's published report. Source file
NTSB_2004_CHI04CA165.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…