CHI03LA183 · Enstrom 280C
Enstrom 280C · Accident: loss of engine power during initial climb
From West Branch, MI (private airstrip) to MidMichigan Health Park Heliport (1MI7)
Event
- NTSB case
- CHI03LA183
- 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
Enstrom 280C
- Aircraft type
- Enstrom 280
- 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
- N5695D
- Operator
- Unknown
- Onboard fatalities
- Unknown
- Route
- From West Branch, MI (private airstrip)To MidMichigan Health Park Heliport (1MI7), Selkirk, MI
- 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
- Loss of engine power
- 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 › Failure
- Engine assembly, connecting rod › Fatigue
Approximate · Coordinates from the NTSB case API, which marks them as estimated or does not say; no uncertainty radius is established.
NTSB narrative
The helicopter impacted water during an autorotation following a loss of engine power. The pilot reported he lost engine power during initial climb and the helicopter landed upright about 75 feet off the shore in about 2-1/2 feet of water. An inspection of the helicopter confirmed flight control continuity. Both fuel tanks contained 25 gallons of fuel and the engine contained 8 quarts of oil. The main and tail rotors showed drivetrain continuity. A large hole was found in the crankcase, near the number one engine cylinder, and the number one connecting rod was protruding from the hole. Examination of the broken connecting rod cap revealed fracture features that were consistent with a fatigue-type failure. Additionally, the material encompassing the fatigue initiation point was galled along with several other areas of the bearing interface.
Probable cause
The loss of engine power due to the fatigue failure of the connecting rod cap. A related factor was the unsuitable terrain the pilot encountered.
Verbatim NTSB analysis and probable cause from the NTSB dataset
Sources
NTSB record CHI03LA183
- Event ID
- 20030626X00964
- Case number
- CHI03LA183
- 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: c99ee480d0addf4016c3492998d72336b7c324de0aa2d3abe6474b0dd29b8fd7; retrieved 2026-09-21T09:27:23.616Z.