# NTSB MIA00LA214: Cessna 172L, N3875Q, Beaufort, NC, March 10, 2000 - Type: NTSB accident investigation - Classification: Accident · No injuries · Limited investigation · Final report - Date: March 10, 2000, 11:30 local (16:30 UTC) - Place: Beaufort, NC - Coordinates: 34.720397, -76.650413 (estimated) - Nearby events: https://openairdocs.org/map.md?lat=34.7204&lon=-76.6504&mi=10 - Phase of flight: [Landing](https://openairdocs.org/ntsb-phases/550) (OpenAirDocs' grouping) - Highest injury: No injuries - Injuries: 1 uninjured - Status: Completed, report April 25, 2001 - Report: Approved by Office Director - NTSB case key (mKey): 49681 - NTSB case page: https://web.ntsb.gov/investigations/?ntsbnumber=MIA00LA214 - NTSB report (PDF, downloads): https://data.ntsb.gov/carol-repgen/api/Aviation/ReportMain/GenerateNewestReport/49681/pdf - Page: https://openairdocs.org/ntsb/MIA00LA214 ## Probable cause 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. ## Sequence of events In NTSB's coding before 2008 (https://www.ntsb.gov/GILS/Documents/codman.pdf). - Hard landing, landing - porpoise/pilot-induced oscillation - encountered, pilot in command - go-around - not performed, pilot in command (cause) ## Analysis 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. ## 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. ## Aircraft - Registration: [N3875Q](https://openairdocs.org/aircraft/N3875Q), registered now, S/N 17259975, built 1971 (OpenAirDocs) - Reported make and model: Cessna 172L - Registry model: [Cessna 172L](https://openairdocs.org/model/cessna-172l) (registry code 2072432) (OpenAirDocs) - Registry engine: [Lycoming 0-320 series](https://openairdocs.org/engine/lycoming-0-320-series) (registry code 41508, reciprocating) (OpenAirDocs) - Category: Airplane - Serial number: 17259975 - Airframe hours: 3256 - Engines: Lycoming O-320-E2D 150 horsepower reciprocating - Damage: Substantial damage - Flight: Personal, Part 91 - Registered owner: Jeff L. Wood - Airworthiness certificate: Standard, Normal; Standard, Utility - Last inspection: Annual, March 29, 1999, 165 hours before - Departed: MRH - Airport: MRH, Michael J. Smith Field ## Flight crew As NTSB recorded them. NTSB leaves out names. - Pilot; age 30; private; airplane ratings: single-engine land; medical: class 3, valid medical--no waivers/lim.; flight hours: 80 total ## Weather - Conditions: Visual (VMC), Day - Wind: calm - Visibility: 10 statute miles - Lowest ceiling: none - Temperature: 81 °F, dew point 55 °F - Altimeter: 30.00 inHg - Observed at: EWN, 28 nm away ## FAA reports on this event (1) The FAA's own accident and incident reports, matched to the aircraft by N-number and date (OpenAirDocs). - [Accident 20000310040979A](https://openairdocs.org/incident/20000310040979A), Mar 10, 2000: Cessna 172L, Beaufort, NC, Substantial damage. (.4) 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… ## Other investigations on N3875Q (1) From the NTSB's public API. Aircraft are matched to registry aircraft by N-number and event date, checked against the reported serial number, make and model; the registry's history has gaps, so older matches can be wrong. Compare the reported make and model. - [NTSB MIA00LA215](https://openairdocs.org/ntsb/MIA00LA215), Jul 10, 2000: Cessna 172L (N3875Q), Beaufort, NC, substantial damage. Probable cause: A loss of engine power due to failure of the No. 4 cylinder connecting rod during the first flight following engine overhaul for undetermined reasons. Contributing to the accident was unsuitable… From the NTSB's public API. Aircraft are matched to registry aircraft by N-number and event date, checked against the reported serial number, make and model; the registry's history has gaps, so older matches can be wrong. Compare the reported make and model. --- OpenAirDocs.org is an independent research project of [Contrail Labs](https://contraillabs.com/). It is not affiliated with the FAA or the NTSB. Source documents are U.S. government works in the public domain.