MIA00LA215
2000-07-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
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 terrain.
Factual narrative
On July 10, 2000, about 1030 eastern daylight time, a Cessna 172L, N3875Q, registered to a private individual, collided with a fence during a forced landing at the Micheal 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 maintenance test flight. The airplane was substantially damaged and the commercial-rated pilot and one passenger were not injured. The flight was originating at the time of the occurrence. The pilot stated that she was asked to fly the airplane on a 30-minute test flight prior to returning the airplane to the owner following repairs. The passenger was the Director of Maintenance (DOM) for the facility that had performed the repairs, which included disassembly and overhaul of the engine following a propeller strike which occurred on March 10, 2000. The pilot further reported that no discrepancies were noted during the engine run-up, and all engine instruments were indicating in the green arcs after applying full power to takeoff. While climbing about 100 feet above ground level (agl), the "entire aircraft began to shake violently and the power dropped to 1,000 rpm. The rpm then advanced slightly to 1,400 rpm, and dropped off as the engine quit." She landed the airplane with only 180 feet remaining on the departure runway and applied heavy brakes. The airplane departed the end of the runway, rolled onto wet grass, and unable to stop the airplane, collided with a chain link fence. The pilot and the DOM notified the Greensboro FAA Flight Standards District Office (FSDO) within approximately 1.5 - 2.0 hours from the time of the accident. FAA FSDO personnel made the determination based on the described damage that the airplane sustained minor damage. FAA personnel also informed the DOM of the facility that had overhauled the engine to photograph it and to disassemble the damaged engine taking photographs during various stages of disassembly. The engine was disassembled per the instructions from the FAA without government oversight, before NTSB notification. Following NTSB notification, arrangements were made with a local airframe and powerplant mechanic with inspection authorization (IA) to inspect the airplane and report his findings. The inspection revealed damage to two leading edge ribs in the right wing and to one leading edge rib in the left wing. The NTSB classified the occurrence as an accident. A copy of the statement from the IA is an attachment to this report. According to the DOM, the No. 4 cylinder connecting rod bolts were fractured, and the connecting rod cap was straight. The camshaft was fractured, and a connecting rod bearing was found in the oil sump. Review of digital photographs taken by the IA who inspected the airplane revealed the No. 4 cylinder skirt was damaged; crankcase material was missing beneath the No. 4 cylinder area. Due to the lack of government oversight during the examination of the failed engine, no components of the engine were examined or retained. Review of the maintenance records revealed an entry dated July 5, 2000, indicates that the engine was overhauled "...per Lycoming Overhaul Manual (60294-7)." The entry also indicates that the engine was test run, and "All pressures and temps [sic] within manufacturer specifications...." A copy of the maintenance record entry is an attachment to this report. The flight was a maintenance test flight following engine overhaul due to a propeller strike on March 10, 2000. No discrepancies were noted by the pilot during the engine run-up or after applying full power to takeoff. While climbing about 100 feet above ground level (agl), the engine experienced a loss of power then quit. The pilot landed the airplane with only 180 feet remaining on the departure runway and applied heavy brakes. The airplane departed the end of the runway, rolled onto wet grass, and unable to stop the airplane, collided with a chain link fence. The engine was disassembled with FAA approval by the facility that overhauled it without government oversight, before NTSB notification. The No. 4 cylinder connecting rod bolts were fractured, and the connecting rod cap was straight. Due to the lack of government oversight during the examination of the failed engine, no components of the engine were examined or retained. An entry in the maintenance records dated July 5, 2000, indicates that the engine was overhauled '...per Lycoming Overhaul Manual (60294-7).' The entry also indicates that the engine was test run, and 'All pressures and temps [sic] within manufacturer specifications....' Source: NTSB Aviation Accident Database (Pre-2008 Archive) Retrieved: 2026-02-12
Verbatim from NTSB's published report. Source file
NTSB_2000_MIA00LA215.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 (maintenance). All research papers
- Embry-Riddle Scholarly Commons 2026 · Journal article (IJAAA) From Reactive to Predictive: A hybrid Trust-Mediated Adoption Framework for Data-Driven Maintenance in Distributed-Authority Aviation Environments
Modern aviation maintenance operates within increasingly data-intensive technological environments, yet the operational integration of predictive maintenance into routine decision-making remains incon…
- Semantic Scholar 2026 · Article (Reliability Engineering & System Safety) Understanding human error in military aviation maintenance: The role of Performance shaping factors, cognitive workload and error orientation
- Semantic Scholar 2025 · Article (Applied Sciences) Decision-Making Framework for Aviation Safety in Predictive Maintenance Strategies
The implementation of predictive maintenance (PM) in aviation presents unique challenges due to strict safety requirements, complex operational environments, and regulatory constraints.
- Semantic Scholar 2024 · Article (Defence Science Journal) Modelling of Human Factors in Aviation Maintenance Using HFACS ME Human Factors Analysis and Classification System Maintenance Extension and Bayesian Network
Aircraft maintenance is a complex task involving a skilled human workforce, spare parts, and various other resources. Human factors are an inherent element of the human workforce.
- Embry-Riddle Scholarly Commons 2024 · Journal article (JAAER) A New Trajectory in UAV Safety: Leveraging Reinforcement Learning for Distance Maintenance Under Wind Variations
In the field of aviation, safety is a critical cornerstone, and the operation of Unmanned Aerial Vehicle (UAV) systems is deeply connected with this principle.
- Embry-Riddle Scholarly Commons 2024 · Journal article (JAAER) Low-Resource Automatic Speech Recognition Domain Adaptation – A Case-Study in Aviation Maintenance
With timeliness and efficiency being critical in the aviation maintenance industry, the need has been growing for smart technological solutions that optimize and streamline the different underlying ta…