NTSB CAROL · Event
Event ERA12LA259
Aircraft involved
Probable cause & findings
The pilot's improper landing flare, which resulted in a hard landing.
Factual narrative
On March 24, 2012, about 1315 eastern daylight time, a Cessna 172P, N99087, was substantially damaged during a hard landing at Hernando County Airport (BKV), Brooksville, Florida. The commercial pilot and two passengers were not injured. The airplane was operated by the Civil Air Patrol (CAP) under the provisions of 14 Code of Federal Regulations Part 91, for the purpose of giving orientation flights to new cadets. The flight originated at Tampa Executive Airport (VDF), Tampa, Florida at 1245. Damage to the airplane was reported by a CAP pilot after it was discovered during a pre-flight inspection on the afternoon of March 24, 2012. CAP safety personnel initiated an internal investigation to determine who was flying the airplane when the damage occurred. Initially, no pilots that were contacted reported any abnormal activity or were aware of the damage. A ramp employee at BKV reported the following. He was driving a fuel truck on the ramp about 1315 on March 24, 2012 and observed the accident airplane on final approach for runway 21. Since he was also a pilot, he pulled over and stopped the truck to watch the airplane land. He observed the airplane "porpoise" three times and he saw and heard the tail strike the runway. The pilot then added full power and commenced a go-around. The ramp employee also watched the airplane taxi to the ramp after the flight. He stated that the pilot did not perform an exterior walk-around inspection to check for any damage. The ramp employee proceeded into the fixed base operator's office to report the event. An inspector with the Federal Aviation Administration obtained copies of flight log entries for the accident airplane. He then interviewed the pilot that was flying the airplane at the time reported by the ramp employee at BKV. The pilot reported that he was performing an approach to runway 21 for a touch-and-go landing. He recalled the winds from the southwest at 8 knots with gusts to 13 knots. During the landing, the airplane bounced at first, then settled back down to the runway. He executed a full power takeoff and remained in the traffic pattern for a full stop landing. He stated that he performed a post-flight inspection and noted no discrepancies. He flew the airplane back to VDF without further incident. The pilot reported that he did not land lard or experience a tail strike. The FAA inspector examined the airplane and noted buckling damage to the cabin floor, the engine firewall, and a bent tail strike bar. Weather, reported at BKV at 1253, included surface winds from 230 degrees at 12 knots with gusts to 18 knots. An airport ramp employee reported observing the airplane "porpoise" three times during the landing, followed by a tail strike, which he saw and heard. The pilot performed a go-around and remained in the traffic pattern for a full stop landing. The ramp employee observed the pilot and his passengers leave the airplane without performing an external inspection. During postaccident interviews, the pilot who was flying the airplane reported that he was performing a touch-and-go landing and bounced once during the initial touchdown. He stated that he did not land hard or experience a tail strike. The damage to the cabin floor, the engine firewall, and the tail strike bar was discovered later in the day by another pilot preparing to fly the airplane. Source: NTSB Aviation Accident Database Retrieved: 2026-02-12
NTSB Findings
Hierarchical cause / factor breakdown from the FAA bulk avdata database. Each finding tagged C (Cause) or F (Factor).
- C Aircraft-Aircraft oper/perf/capability-Performance/control parameters-Landing flare-Not attained/maintained - C
- C Personnel issues-Task performance-Use of equip/info-Aircraft control-Pilot - C
Verbatim from NTSB's published report. Source file
NTSB_2012_ERA12LA259.txt.
Findings + structured fields enriched from FAA avall.mdb.
Full investigation docket on
data.ntsb.gov ↗.
Beyond the agency record
Search this event elsewhere.
Pre-filled searches into the sources where news + community discussion of aviation events lives. External sources are reported, not agency. Treat them as signal that something happened, not as fact about what happened.
Entity-clustered aviation events in the press — last 24 hr + 30-day archive.
Official agency record + docket.
Investigative docket: factual reports, photos, transcripts.
Long-running aviation incident database (Flight Safety Foundation).
Community NTSB synthesis blog — often has photos and witness reports.
Gold-standard aviation incident blog.
Aviation industry news search.
GA pilot forum — informed but rumor-prone.
GA pilot subreddit search.
Tail-number page — flight history (free tier limited).
AOPA Air Safety Institute search.
Mainstream press coverage. Recent events only.
Privacy-preserving news search.
External links open in a new tab. We don't ingest their content; we deep-link search queries.
Related research
What the literature says.
Academic papers and agency reports matching this event's aircraft type or causal vocabulary (go-around). Sourced from NASA NTRS, NTSB Safety Studies, FAA CAMI, AOPA Air Safety Institute, Embry-Riddle Scholarly Commons, arXiv, and the Semantic Scholar academic graph.
- 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…
Browse the full corpus — academia portal ↗