SEA95LA155 · Cessna 172P
Cessna 172P · Accident: total loss of engine power (mechanical failure) en route
From King County International Airport - Boeing Field (BFI) to an unrecorded destination
Event
- NTSB case
- SEA95LA155
- 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
- 0
- 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 172P
- 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
- N52139
- Operator
- Wings Aloft
- Onboard fatalities
- Unknown
- Route
- From King County International Airport - Boeing Field (BFI), Seattle, WATo not recorded
- 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
- En route · cruise
- 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 bolt › Overload
Approximate · Coordinates as recorded by the NTSB; no uncertainty radius is established.
NTSB narrative
WHILE IN CRUISE FLIGHT, THE ENGINE SUDDENLY MADE A LOUD SOUND, BEGAN TO SHAKE, THEN LOST POWER. THE PILOT INITIATED A FORCED LANDING TO AN OPEN FIELD. THE AIRPLANE TOUCHED DOWN, BOUNCED AND BECAME AIRBORNE BEFORE TOUCHING DOWN THE SECOND TIME. THE NOSE GEAR COLLAPSED AND THE AIRPLANE SLID TO A STOP. POST CRASH EXAMINATION REVEALED HOLES IN THE CRANKCASE. A TEARDOWN OF THE ENGINE FOUND THAT THE NUMBER THREE AND FOUR CONNECTING ROD CAP BOLTS SEPARATED. A METALLURGICAL EXAMINATION OF THE FRACTURED BOLTS REVEALED FEATURES CHARACTERISTIC OF A PROGRESSIVE OVERSTRESS. THE METALLURGICAL SPECIALIST REPORTED THAT THE SEPARATION MOST LIKELY OCCURRED DUE TO AN INADEQUATELY TORQUED NUT OR LOSS OF PRESTRESS OVER A PERIOD OF TIME.
Probable cause
THE LOSS OF ENGINE POWER DUE TO CONNECTING ROD BOLT OVERLOAD FAILURE. THE ROUGH, UNEVEN TERRAIN IN THE EMERGENCY LANDING AREA WAS A FACTOR.
Verbatim NTSB analysis and probable cause from the NTSB dataset
Sources
NTSB record SEA95LA155
- Event ID
- 20001207X04099
- Case number
- SEA95LA155
- 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: local date, investigation status. Values present in the bulk record are kept.
- The date is the local date; the NTSB stores the UTC date 1995-07-13.
- API snapshot SHA-256: 3908b83df0b5bc564928cd01573107735ebd2a8051e399b711dd4a34a2f8f981; retrieved 2026-09-22T23:37:52.548Z.