CHI98LA242 · Brunnemer HMB-2
Brunnemer HMB-2 · Accident: total loss of engine power (mechanical failure) en route
From 71II · Franklin, IN to 4I7 · Greencastle, IN
Event
- NTSB case
- CHI98LA242
- 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
Brunnemer HMB-2
- Aircraft type
- Brunnemer HMB-2
- Category
- Gyroplane
- 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
- N9129F
- Operator
- Unknown
- Onboard fatalities
- Unknown
- Route
- From 71II · Franklin, INTo 4I7 · Greencastle, IN
- 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
- Ignition system, ignition coil › Fractured
Approximate · Coordinates as recorded by the NTSB; no uncertainty radius is established.
NTSB narrative
The pilot stated that approximately 10 minutes into the flight the engine loss complete power. The pilot was cruising at an approximate altitude of 700' above ground level (agl). The pilot completed a forced landing into a soybean field and upon touchdown the aircraft dug into the soft terrain. The front wheel contacted the terrain first, resulting in the aircraft to nose over and come to rest in an inverted position. The pilot stated that the area had received 1.5 inches of rain the night before, and that produced the 6 inches of mud that was present in the soybean field. Post accident investigation showed that the ignition coil had broken due to fatigue from operational vibrations. No other engine or aircraft anomalies were found.
Probable cause
A loss of engine power due to a fractured ignition coil. A factor to the accident was the soft terrain.
Verbatim NTSB analysis and probable cause from the NTSB dataset
Sources
NTSB record CHI98LA242
- Event ID
- 20001211X10496
- Case number
- CHI98LA242
- 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: 29f210af436c46f1f06002d5b8dff4aa0a357cbc4f4bb2856d833571b48da1ed; retrieved 2026-09-22T17:34:49.576Z.