NTSB CAROL · Event
Event LAX06LA232
Aircraft involved
Probable cause & findings
The failure of the number four connecting rod during takeoff-initial climb.
Factual narrative
On July 15, 2006, about 1810 coordinated universal time, a pilot ditched a Cessna R172K II, N1209V, near Hagatna, Guam. Micronesia Aviation Systems, Inc., was operating the airplane under the provisions of 14 Code of Federal Regulations (CFR) Part 91. The certificated commercial pilot and two passengers sustained minor injuries; the airplane sustained substantial damage to the firewall. The local sight seeing flight departed Guam International Airport in Hagatna about 1805. Visual meteorological conditions prevailed, and no flight plan had been filed. The pilot reported to the Federal Aviation Administration that the airplane was climbing through 1,500 feet. The engine began to run rough, and he tried to smooth it out using the mixture. It began sputtering as he tried to return to the airport for a landing on runway 06L. However, it's condition worsened, and then the engine quit producing power. He ditched in a nearby bay. A Federal Aviation Inspector supervised examination of the airframe and engine. The airplane sustained damage to the firewall where the engine cradle attaches to the airframe. The cradle tweaked to the right, wrinkling the airframe just a little aft of the firewall. He observed a hole in the top of the case at the number four cylinder. He noted that the number four connecting rod fractured and separated. After being in the salt water, he reported that the engine had corroded and could not be further disassembled. The engine had been flown 1,500 hours past the manufacturer's recommended time between overhaul. The airplane was climbing through 1,500 feet when the engine began to run rough. The pilot tried to smooth it out using the mixture; however, its condition worsened, and it stopped producing power altogether. The pilot could not glide to shore, and he ditched in a nearby bay. Examination of the engine revealed a hole in the top of the case at the number four cylinder. The number four connecting rod fractured and separated. After being in the salt water, the engine had corroded and could not be further disassembled. Moreover, the corrosion obscured the connecting rod fracture faces. Review of the maintenance records found that the engine had flown 1,500 hours past the manufacturer's recommended time between overhaul. Source: NTSB Aviation Accident Database (Pre-2008 Archive) Retrieved: 2026-02-12
Verbatim from NTSB's published report. Source file
NTSB_2006_LAX06LA232.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 (maintenance). Sourced from NASA NTRS, NTSB Safety Studies, FAA CAMI, AOPA Air Safety Institute, Embry-Riddle Scholarly Commons, arXiv, and the Semantic Scholar academic graph.
- 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 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.
- 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…
- 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 (IJAAA)
Just Culture in Aviation: A Metaphorical Study on Aircraft Maintenance Students
Just Culture, a sub-dimension of safety culture, has been a prominent and debated topic in aviation safety in recent years.
- Embry-Riddle Scholarly Commons 2024 · Journal article (IJAAA)
Performance PRISM: A Comprehensive Framework For Performance Measurement In Aircraft Maintenance
Aircraft maintenance is governed by rigorous safety requirements and high operational complexity, demanding robust performance measurement frameworks to ensure optimal maintenance practices.
Browse the full corpus — academia portal ↗