FLIGHT FINDINGSAVIATION OCCURRENCE MAP
Back to map

CHI02LA087 · Cessna 182H

8 Mar 2002 · West Plains, MO, United States

Cessna 182H · Accident: total loss of engine power (mechanical failure) en route

From West Plains Regional Airport (UNO) to Jonesboro Municipal Airport (JBR)

Report a problem

Event

NTSB case
CHI02LA087
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 182H

Aircraft type
Cessna 182
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
N64AE
Operator
Unknown
Onboard fatalities
Unknown
Route
From West Plains Regional Airport (UNO), West Plains, MOTo Jonesboro Municipal Airport (JBR), Jonesboro, AR
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, crankshaft › Failure
  • Engine assembly, crankshaft › Fatigue
  • Engine assembly, piston › Improper
  • Other maintenance personnel › Maintenance, installation, improper

Approximate · Coordinates as recorded by the NTSB; no uncertainty radius is established.

NTSB narrative

The airplane sustained substantial damage during a forced landing to a field after a total loss of engine power. The pilot reported he was cruising at 3,000 feet msl when he heard a loud bang from the engine, followed almost immediately by smoke from beneath the left side panel and excessive vibration from the engine. The engine lost power and the pilot executed a forced landing. During landing roll out, the nose wheel struck a rock and the nose gear collapsed. An inspection of the engine revealed that a connecting rod had punched a hole in the engine case. The number 2 piston rod, rod bearing, and rod journal were discolored and exhibited heat distress. The crankshaft was broken in two pieces at the number 2 cheek. A fatigue fracture was observed on the fracture surfaces of the number 2 cheek. The engine was originally a 230 horsepower Continental O-470-R that was converted to a 270 horsepower O-470-50, as a result of Supplemental Type Certificate (STC) #SE4985NM. This STC required the cylinders to be replaced with the same cylinders and pistons used on Continental O-520 engines. The crankshaft, forging number 539664, S/N S401, and heat code E99, referred to as a "wide-rod" crankshaft, was manufactured in the 1960's and was originally used on Continental Motors O-470 and IO-470 engines. The crankshaft had not been replaced since the STC conversion on December 23, 1994. It had accumulated 1,259.0 hours since the STC conversion. The engine teardown revealed that the pistons installed on the engine were 8.5 to 1 compression pistons used on normally aspirated Continental O-520 engines. The P. Ponk Aviation STC SE4985NM specifies that the 7.5 to 1 compression pistons are the proper pistons to use in the engine conversion. On September 24, 2002, P. PONK AVIATION, issued a Service Information Letter, SIL 002, that stated, "Use of the "wide-rod" crankshaft with any piston higher than the 7.5 to 1 compression ratio and a maximum rpm above 2700 is not authorized by our STC and could result in engine failure. Our testing did not exceed the above parameters, and we do not condone or support installation of the higher compression pistons." No logbook entries indicated any of the pistons had been changed since the engine was converted to an O-470-50, on December 23, 1994, and only the # 3 cylinder was changed on April 15, 2000, due to low compression. The engine build-up records that documented what parts were installed on the engine during the STC conversion no longer existed.

Probable cause

The engine failure due to the fatigue fracture of the crankshaft which resulted from the installation of improper pistons during an STC'd engine conversion by other maintenance personnel. Additional factors included the unsuitable terrain encountered by the pilot during the forced landing.

Verbatim NTSB analysis and probable cause from the NTSB dataset

Sources

NTSB record CHI02LA087
Event ID
20020312X00333
Case number
CHI02LA087
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. 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: 703f31307f7a03bb425eb77c8e8ec05e1a50d0ae0f860bbff8c6822302f7ca8f; retrieved 2026-09-22T11:04:52.534Z.