FLIGHT FINDINGSAVIATION OCCURRENCE MAP
Back to map

CEN15CA155 · Gaddis Michael EXEC 162 F

26 Feb 2015 · Plymouth, IN, United States

Gaddis Michael EXEC 162 F · Accident: powerplant system/component malfunction/failure en route

From Plymouth, IN to Plymouth Municipal Airport (C65)

Report a problem

Event

NTSB case
CEN15CA155
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

Gaddis Michael EXEC 162 F

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
N123XZ
Operator
Unknown
Onboard fatalities
Unknown
Route
From Plymouth, INTo Plymouth Municipal Airport (C65), Plymouth, IN
Aircraft age
About 17 years (built 1998)
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
Defining eventThe 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
Powerplant system/component malfunction/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

  • Aircraft › Aircraft propeller/rotor

Approximate · Coordinates from the NTSB case API, which marks them as estimated or does not say; no uncertainty radius is established.

NTSB narrative

The pilot reported that while in cruise flight the engine RPM of the helicopter suddenly increased to the point where the rev limiter activated. At this point the helicopter was about 700 ft above ground level and the pilot performed an autorotation to a baseball field. During the forced landing, the helicopter sustained substantial damage to its fuselage. Subsequent examination of the helicopter revealed that the main drive belt that transmitted engine power to the rotor system had failed.

Probable cause

The failure of the helicopter's main drive belt resulting in the pilot performing a forced landing, during which the helicopter's fuselage was substantially damage.

Verbatim NTSB analysis and probable cause from the NTSB dataset

Sources

NTSB record CEN15CA155
Event ID
20150227X93828
Case number
CEN15CA155
Dataset
full-current
Source SHA-256
5cf380f0061817c0331a6b2d8cc7e0ee3a79bea469a1001dc5c10e56f35f5ab3
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: 3420cc76b0bdb46ed62cb873e70b768656c0d96246287b7c368c2cf3d2749744; retrieved 2026-09-16T02:06:56.249Z.