MIA00LA214
2000-03-10 · BEAUFORT, North Carolina, United States · None · 1 aircraft · Status: Completed
Airport MRH
Current FAA registration · N3875Q
- Make / Model
- CESSNA 172L
- Year of manufacture
- 1971 · 29 years old at event
- Engine
- LYCOMING 0-320 SERIES (180 hp)
- Seats / Engines
- 4 seats · 1 engine
- Last airworthiness date
- 19710816
- ADS-B equipped
- Yes — Mode-S A47861
Source: FAA Aircraft Registry (releasable master file).
Aircraft involved
Probable cause & findings
The failure of the pilot to initiate a go-around after the airplane began to porpoise, resulting in a hard landing and structural damage to the airplane.
Factual narrative
On March 10, 2000, about 1130 eastern standard time, a Cessna 172L, N3875Q, registered to a private individual, experienced a hard landing at the Michael J. Smith Field Airport, Beaufort, North Carolina. Visual meteorological conditions prevailed at the time and no flight plan was filed for the 14 CFR Part 91 personal flight. The airplane was substantially damaged and the private-rated pilot, the sole occupant, was not injured. The flight originated about 36 minutes earlier. The registered owner failed to report the accident to the NTSB or the FAA. According to the FAA inspector who reported the accident to the NTSB on July 12, 2000, during routine surveillance on June 15, 2000, at the facility where the airplane was being repaired, he observed the airplane in the hangar and inquired about the damage. The pilot did not return the NTSB 6120.1/2 Pilot/Operator Aircraft Accident Report form; the registered owner completed information on the form applicable to the airplane. Several attempts were made to the talk with the pilot but were unsuccessful. According to a transcription of recorded statement provided by the insurance adjuster who interviewed the pilot, the pilot stated that no discrepancies were noted during the preflight or engine run-up before takeoff. He stated that after departure the flight remained in the airport traffic pattern where he performed touch-and-go landings. During the flare of the accident landing, the flight was fast and the airplane began to porpoise resulting in a propeller strike. He further stated that he should have initiated a go-around but "at the time I never experienced the porpoising during the flare. It happened so quickly that I didn't even finish it." Postaccident examination of the airplane revealed the firewall and propeller were damaged. Several attempts were made to the talk with the pilot but were unsuccessful. The pilot stated during an interview with the insurance adjuster that there were no discrepancies noted during the preflight or engine run-up before takeoff. He stated that after departure the flight remained in the airport traffic pattern where he performed touch-and-go landings. During the flare of the accident landing, the flight was fast and the airplane began to porpoise resulting in a propeller strike. He further stated that he should have initiated a go-around but 'at the time I never experienced the porpoising during the flare. It happened so quickly that I didn't even finish it.' Postaccident examination of the airplane revealed the firewall and propeller were damaged. Source: NTSB Aviation Accident Database (Pre-2008 Archive) Retrieved: 2026-02-12
Verbatim from NTSB's published report. Source file
NTSB_2000_MIA00LA214.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…