FTW98LA032
1997-10-25 · BOERNE, Texas, United States · Serious · 1 aircraft · Status: Completed
Airport 5C1
Aircraft involved
Probable cause & findings
the pilot's failure to maintain directional control of the airplane during the aborted landing. Factors relating to the accident were: the pilot's improper recovery from a bounced landing, which resulted in a porpoise; his lack of total experience in the Cessna 177; and the crosswind.
Factual narrative
On October 25. 1997, at 1021 central daylight time, a Cessna 177 airplane, N2971X, was destroyed by a post-crash fire following a collision with a parked front end loader during an aborted landing at Boerne Stage Field Airport, Boerne, Texas. The private pilot, the sole occupant, sustained serious injuries. The airplane was registered to a private individual and operated by the pilot under Title 14 CFR Part 91. No flight plan was filed and visual meteorological conditions prevailed for the personal local flight that departed the airport at 1000. During a telephone interview, conducted by the NTSB investigator-in-charge (IIC), and in the attached NTSB Pilot/Operator Aircraft Accident Report, the pilot stated that on the morning of the accident, the sky was overcast and the winds were from 200 degrees at 4 to 6 knots. He completed "two uneventful landings" on runway 17, and his third circuit of the traffic pattern was "uneventful" until on final approach, he noticed an increase in speed, possibly indicating the wind had shifted to a tailwind. He extended the flaps from 10 to 30 degrees and then to 40 degrees as the airplane crossed the runway threshold. The pilot reported that as he flared the airplane, it was "slammed" into the ground, bounced, then "slammed" down again, and bounced "5 to 6 feet into the air." He further reported that he initiated a go-around by adding power and raising the flaps to 10 degrees. According to the pilot, the airplane "would not climb," began "drifting left," and "would not respond to [his] control inputs." The pilot's next recollection was "hitting a front end loader parked 200 feet left of the runway." He stated that he "exited the aircraft unassisted" and received burns on his legs due to fuel that "poured on [him] from the left fuel tank." The pilot stated that he had made one previous flight in the airplane with the owner about 1 to 2 weeks prior to the accident flight. The flight with the owner had lasted less than an hour and, with the exception of the accident flight, was his only flight experience in a Cessna 177. The pilot commented that he may not have been "fully familiar with the stabilator tail" of the Cessna 177. According to the written statements of three witnesses, the airplane touched down on runway 17, bounced, and "started to porpoise." The pilot added power, and the airplane departed the left side of the runway. Two of the witnesses then lost sight of the airplane. The third witness momentarily lost sight of the airplane, went to the corner of his hangar, and observed the airplane at an altitude of "about 8 to 10 feet AGL" collide with a parked front end loader. The airplane then impacted the ground and "burst into flames." FAA inspectors who examined the accident site found a series of intermittent scrape marks and ground scars that began at a point on the runway approximately 856 feet from the threshold, departed the left side of the runway at the midfield taxiway (1056 feet from the threshold), and continued across a grassy area and the parallel taxiway before terminating near the airplane. The airplane came to rest approximately 120 feet east of the centerline of runway 17 and 1,584 feet south of the threshold. It was lying upright on a southerly heading adjacent to the front end loader, which was parked on the east side of the parallel taxiway. For further details refer to the attached wreckage diagram prepared by the FAA inspectors. According to the FAA inspectors, the post-crash fire consumed the left wing, instrument panel, cockpit, cabin, and aft fuselage of the airplane. The stabilator, vertical stabilizer, rudder, right wing, and engine were not consumed by the fire. A control continuity check was performed by the inspectors with no discrepancies noted. Review of the National Weather Service Surface Analysis Chart for 1000 on the day of the accident by an NTSB meteorologist revealed that a trough of low pressure, preceding a cold front, extended on a north-south line from the Dallas-Fort Worth area to east of San Antonio to Alice, Texas. The trough was moving eastward across Texas. Winds along the trough and ahead of the cold front were generally southerly with wind speeds of 10 knots or less. Behind the cold front, strong gusting west-northwesterly winds were reported. There were no surface weather observations taken at Boerne Stage Field Airport. At 1021 and 1056, the reported winds at San Antonio International Airport, located 17 nautical miles southeast of the accident site, were 210 degrees at 9 knots and 240 degrees at 7 knots, respectively. At 1008 and 1059, the reported winds at Hondo Municipal Airport, located 33 nautical miles southwest of the accident site, were 180 degrees at 3 knots and 260 degrees at 6 knots, respectively. At 0953 and 1053, the reported winds at Kimble County Airport, located 73 miles northwest of the accident site, were 300 degrees at 17 gusting to 23 knots and 300 degrees at 19 gusting to 23 knots, respectively. For further details refer to the Meteorological Factual Report. During a landing on runway 17, the Cessna 177 airplane touched down, bounced, and began to porpoise. The private pilot aborted the landing by adding power and raising the flaps from 40 to 10 degrees. The airplane departed the left side of the runway, crossed a grassy area and the parallel taxiway, became airborne, and collided with a parked front end loader. The airplane then impacted the ground and was destroyed by a postcrash fire. The pilot had less than 1 hour of flight time in the Cessna 177. Review of weather data indicated that during the time period of the accident flight, winds in the area were gradually changing from a southwesterly to a northwesterly direction, resulting in an increasing right crosswind component for landing on runway 17. At the time of the accident, winds were likely from the west at 10 to 15 knots. Source: NTSB Aviation Accident Database (Pre-2008 Archive) Retrieved: 2026-02-12
Verbatim from NTSB's published report. Source file
NTSB_1997_FTW98LA032.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…