MKC82FCA08 · Bell 47G-4
North American Bell 47G-4 · Accident: total loss of engine power (mechanical failure) en route
From Jackson, MO to ST CLAIRE, MO
Event
- NTSB case
- MKC82FCA08
- 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
Bell 47G-4
- Aircraft type
- Bell 47
- Category
- Helicopter
- 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
- N87623
- Operator
- North American
- Onboard fatalities
- Unknown
- Route
- From Jackson, MOTo ST CLAIRE, MO
- 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)
- Also codedOther events the NTSB coded in the sequence, such as a wire strike after a loss of power. Flight Findings uses them for its kinds of event. Glossary
- Tree(s)
- 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 › Undetermined
Not plotted · Location withheld: coordinates are missing, conflicting, invalid, or have no accepted acquisition method. No substitute location has been invented.
NTSB narrative
THE PILOT REPORTED THAT ABOUT 40 MINUTES AFTER TAKEOFF, THERE WAS A DROP IN OIL PRESSURE FOLLOWED ALMOST IMMEDIATELY BY AN ENGINE FAILURE. THE ENGINE FAILURE OCCURRED OVER A WOODED AREA. THE PILOT ATTEMPTED AN EMERGENCY LANDING IN A SMALL CLEARING, BUT THE HELICOPTER STRUCK TREES SHORT OF THE OPENING. AN INVESTIGATION REVEALED THAT THE NO. 5 CONNECTING ROD HAD FAILED AT THE CRANKSHAFT END. IT WAS NOTED THAT A ROD CAP BOLT HAD BROKEN, THE CAP HAD STRAIGHTENED OUT, AND THE ROD HAD SEPARATED FROM THE CRANKSHAFT. A LARGE HOLE WAS FOUND IN THE CRANKCASE AND THE OIL TANK WAS EMPTY. HOWEVER, OIL WAS NOTED INSIDE THE ENGINE AND ON ALL BEARINGS AND JOURNALS EXCEPT THE NO. 5 CONNECTING ROD. ALSO, ALL MAIN BEARINGS AND ALL ROD BEARINGS AND JOURNALS, EXCEPT NO. 5, WERE NORMAL.
Verbatim NTSB analysis from the NTSB dataset
Sources
NTSB record MKC82FCA08
- Event ID
- 20020917X02472
- Case number
- MKC82FCA08
- 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: b74b7b6a7fc3b0737f125fc4f9811d08a2bebd4f4ad50ed1a3e43694de29740c; retrieved 2026-09-21T18:17:11.964Z.