LAX06LA232 · Cessna R172K II
Cessna R172K II · Accident: total loss of engine power (mechanical failure) during initial climb
From Antonio B. Won Pat International Airport (GUM) to Antonio B. Won Pat International Airport (GUM)
Event
- NTSB case
- LAX06LA232
- Event typeAccident: someone killed or seriously injured, or the aircraft substantially damaged (NTSB definition). Incident: an occurrence that affected or could have affected safety, short of that. Glossary
- Accident
- InvestigationHow far the investigation had got when the record was published: preliminary, ongoing, final or completed. Unknown where the source does not say. Glossary
- Completed
- API-reported fatalities
- 0 · all aircraft and ground
- Ground fatalities
- Unknown
- OperationWhat kind of flying it was, grouped by the rules it flew under: airline (US Part 121), air taxi and commuter (Part 135), general aviation (Part 91 and similar), military or government. Glossary
- General aviation
- WeatherVisual meteorological conditions (VMC): good enough to fly by looking outside. Instrument conditions (IMC): cloud or low visibility, flying by instruments. Glossary
- Visual Meteorological Cond
Cessna R172K II
- Aircraft type
- Cessna 172
- Category
- Airplane
- RegistrationThe aircraft's tail number, such as N12345 or G-ABCD. Registrations are reissued, so the same one years apart can be a different aircraft. Glossary
- N1209V
- Operator
- Unknown
- Onboard fatalities
- Unknown
- Route
- From Antonio B. Won Pat International Airport (GUM), HagatnaTo Antonio B. Won Pat International Airport (GUM), Hatagna
- Aircraft age
- Not recorded
- Flight rulesThe regulations the flight operated under: in the US, Part 91 (general aviation), Part 121 (airlines), Part 135 (air taxi and commuter) and others; for flights abroad, the NTSB's coarser commercial or non-commercial code. Glossary
- Part 91: General Aviation
- Phase of flightThe stage of the flight when things started to go wrong: standing, taxi, takeoff, initial climb, en route, maneuvering, approach or landing. Glossary
- Initial climb
- First occurrenceThe single coded event the NTSB judges best describes what happened (records from 2008 on). Older records name the first occurrence in the sequence instead. Glossary
- Total loss of engine power (mechanical failure)
- DamageDestroyed: beyond practical repair. Substantial: damage that affects the structure, performance or handling and normally needs major repair. Minor: less than that. Glossary
- Substantial
Cause areas
- Engine assembly, connecting rod › Separation
Approximate · Coordinates from the NTSB case API, which marks them as estimated or does not say; no uncertainty radius is established.
NTSB narrative
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.
Probable cause
The failure of the number four connecting rod during takeoff-initial climb.
Verbatim NTSB analysis and probable cause from the NTSB dataset
Sources
NTSB record LAX06LA232
- Event ID
- 20061025X01556
- Case number
- LAX06LA232
- Dataset
- historical-pre2008
- Source SHA-256
- 89e2df6d848e7ab3b42e7d7c7a03ff403303057a26ca04c95b3ea67201c3ce74
Source notes (4)
- Unreviewed is an editorial label, not an investigation status. API-sourced is not report-checked or human-reviewed. Explicit event totals are used without summing aircraft injury tables; onboard allocation is withheld. Unknown values remain unknown. The operation category is mapped from the NTSB-reported FAR part and has not been reviewed.
- Filled from the NTSB case API where the bulk record had no value: investigation status, coordinates. Values present in the bulk record are kept.
- The date is the local date, which is the same as the UTC date the NTSB stores.
- API snapshot SHA-256: 4ade557c590cd44801b541a14beb3cd9fa50f6c6da089c1ac2e4f070d39fa3f1; retrieved 2026-09-21T18:43:32.416Z.