CHI95LA130 · Brantly Helicopter B-2B
Brantly Helicopter B-2B · Accident: airframe, component or system failure en route
From Strother Field (WLD) to RLA · CEMENT CITY, OK
Event
- NTSB case
- CHI95LA130
- 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
Brantly Helicopter B-2B
- Aircraft type
- Brantly B-2
- 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
- N2198U
- Operator
- Unknown
- Onboard fatalities
- Unknown
- Route
- From Strother Field (WLD), STROTHER, KSTo RLA · CEMENT CITY, OK
- 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
- Airframe, component or system 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
- Rotor drive system, clutch assembly › Failure, total
- Rotor drive system, clutch assembly › Worn
Approximate · Coordinates as recorded by the NTSB; no uncertainty radius is established.
NTSB narrative
THE PILOT STATED THE HELICOPTER WAS IN CRUISE FLIGHT AT ABOUT 500 FEET AGL WHEN THE ENGINE RPM '...SUDDENLY AND RAPIDLY INCREASED AS IF THE ENGINE WAS ABRUPTLY UNLOADED...'. THE PILOT SAID HE AUTOROTATED TO A LANDING THAT WAS '...QUITE SMOOTH.' AFTER TOUCHING DOWN THE HELICOPTER SLID AND ROLLED OVER ON ITS RIGHT SIDE. THE PILOT SAID THE TOUCH DOWN FIELD WAS VERY MUDDY. AN EYE WITNESS SAID HE SAW THE HELICOPTER DESCEND VERY RAPIDLY THEN BOUNCE INTO THE AIR. AFTER TOUCHING DOWN A SECOND TIME IT ROLLED OVER ON ITS RIGHT SIDE. THE ON-SCENE INVESTIGATION REVEALED THAT THE HELICOPTER'S OVER-RUNNING CLUTCH HAD FAILED. EXAMINATION OF THE CLUTCH ASSEMBLY REVEALED ITS SPRAGS AND THE INNER AND OUTER RACES WERE WORN BEYOND THE MANUFACTURER'S DESIGN LIMITATIONS. THE WORN PARTS ALLOWED THE CLUTCH TO GO OVER CENTER AND BECOME DISENGAGED.
Probable cause
The total failure of the rotor drive system clutch assembly due to excessive wear of the clutch assembly. A factor in this accident was the soft ground in the emergency landing area.
Verbatim NTSB analysis and probable cause from the NTSB dataset
Sources
NTSB record CHI95LA130
- Event ID
- 20001207X03263
- Case number
- CHI95LA130
- 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: 05c778bf62e92fec918520a3439241e6baa995d88158ee28d5e556efe73e4b1b; retrieved 2026-09-23T00:01:52.240Z.