CHI05CA075
2005-02-26 · Portage, Wisconsin, United States · Serious · 1 aircraft · Status: Completed
Airport C47
Aircraft involved
Probable cause & findings
The pilot's failure to maintain adequate airspeed during the aborted landing, which resulted in an inadvertent stall at a low altitude. Factors to the accident were the pilot's lack of experience flying from the right pilot station and his failure to maintain directional control during landing rollout.
Factual narrative
On February 26, 2005, at 1620 central standard time, a Cessna 172K, N7325G, piloted by a private pilot, was substantially damaged during an in-flight collision with the terrain during an aborted landing from runway 17 (3,775 feet by 60 feet, dry asphalt) at the Portage Municipal Airport (C47), Portage, Wisconsin. Visual meteorological conditions prevailed at the time of the accident. The personal flight was operating under the provisions of 14 CFR Part 91 without a flight plan. The pilot reported serious injuries and the passenger reported minor injuries. The local flight departed C47 at an unconfirmed time. The pilot reported that the accident flight was with a prospective new flying club member. The pilot stated that the club required new members complete a check-out flight with a current member. The prospective new member (passenger) held a student pilot certificate and had flown solo prior to the accident flight. The pilot held a private pilot certificate and had accumulated 73 hours as pilot-in-command (PIC). The pilot was not a flight instructor and was acting as PIC for the entire flight. The pilot was seated at the right pilot station and the passenger was seated at the left pilot station. The pilot reported that he had "never piloted from the right position before." The pilot reported that the passenger flew three landing approaches and each attempt terminated in a go-around maneuver. After the third landing attempt, the passenger asked the pilot to "demonstrate a landing." The pilot stated that he assumed aircraft control during the downwind leg for runway 17. He reported his final approach was flown with full flaps and an uneventful touchdown was made on the runway. He stated that during rollout the airplane "started to veer toward the right" and that he "incorrectly applied the right rudder instead of left." The pilot decided to perform an aborted landing in order to "demonstrate a better landing." The pilot reported he applied full engine power and "lifted the flaps briefly (but not fully)." He stated that he thought the flaps were "up more" and that he became "flustered" as the airplane "pitched up." He reported that the airplane "stalled" about 30-50 feet above the ground, and that he was "able to pull the nose up so that we landed hard on the [landing] gear." The airplane stalled and impacted the runway during an aborted landing. The pilot reported that the accident flight was with a prospective new flying club member. The pilot stated that the club required new members complete a check-out flight with a current member. The prospective new member (passenger) held a student pilot certificate and had flown solo prior to the accident flight. The pilot held a private pilot certificate and had accumulated 73 hours as pilot-in-command (PIC). The pilot was not a flight instructor and was acting as PIC for the entire flight. The pilot was seated at the right pilot station and the passenger was seated at the left pilot station. The pilot reported that he had "never piloted from the right position before." The pilot reported that the passenger flew three landing approaches and each attempt terminated in a go-around maneuver. After the third landing attempt, the passenger asked the pilot to "demonstrate a landing." The pilot stated that he assumed aircraft control during the downwind leg for runway 17. He reported his final approach was flown with full flaps and an uneventful touchdown was made on the runway. He stated that during rollout the airplane "started to veer toward the right" and that he "incorrectly applied the right rudder instead of left." The pilot decided to perform an aborted landing in order to "demonstrate a better landing." The pilot reported he applied full engine power and "lifted the flaps briefly (but not fully)." He stated that he thought the flaps were "up more" and that he became "flustered" as the airplane "pitched up." He reported that the airplane "stalled" about 30-50 feet above the ground, and that he was "able to pull the nose up so that we landed hard on the [landing] gear." Source: NTSB Aviation Accident Database (Pre-2008 Archive) Retrieved: 2026-02-12
Verbatim from NTSB's published report. Source file
NTSB_2005_CHI05CA075.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 (stall, go-around). All research papers
- NASA NTRS 2026 · Conference Paper Computational Analysis of Steady State Aerodynamics of Transonic Truss-Braced Wing Configuration in Deep Stall
This study presents a computational investigation of steady state aerodynamics of the Subsonic Ultra-Green Aircraft Research (SUGAR) Transonic Truss-Braced Wing (TTBW) configuration over a wide range …
- 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…
- arXiv 2023 · arXiv preprint Automating Bird Diverter Installation through Multi-Aerial Robots and Signal Temporal Logic Specifications
This paper tackles the task assignment and trajectory generation problem for bird diverter installation using a fleet of multi-rotors.
- arXiv 2023 · arXiv preprint Variation of Critical Crystallization Pressure for the Formation of Square Ice in Graphene Nanocapillaries
Two-dimensional square ice in graphene nanocapillaries at room temperature is a fascinating phenomenon and has been confirmed experimentally.
- arXiv 2023 · arXiv preprint Polycrystallinity enhances stress build-up around ice
Damage caused by freezing wet, porous materials is a widespread problem, but is hard to predict or control. Here, we show that polycrystallinity makes a great difference to the stress build-up process…