Metro Aviation Eurocopter Deutschland Gmbh MBB-BK 117 C-2 accident
Eurocopter Deutschland Gmbh MBB-BK 117 C-2 · Accident: part(s) separation from aircraft while taxiing
From an unrecorded airport to Monticello, IN
Event
- NTSB case
- CEN24LA128
- 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
- Charter & commuter
- 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
Eurocopter Deutschland Gmbh MBB-BK 117 C-2
- Aircraft type
- Eurocopter MBB-BK 117 C-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
- N191LL
- Operator
- Metro Aviation
- Onboard fatalities
- Unknown
- Route
- From not recordedTo Monticello, IN
- Aircraft age
- About 15 years (built 2009)
- 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 135: Air Taxi & Commuter
- 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
- Taxi · to runway
- 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
- Part(s) separation from aircraft
- 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 systems
- Personnel issues › Action/decision
- Personnel issues › Task performance
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 a hover taxi to accelerate for takeoff, he felt a force against his feet from the pedals and the helicopter began to yaw to the right. The pilot was unable to arrest the right yaw with pedal inputs. The helicopter landed hard, which resulted in substantial damage to the fuselage, tailboom, vertical fin, horizontal stabilizer, tail rotor assembly, and one main rotor blade. Postaccident examination revealed that the T-bolt and its attachment bolts, which connects the pitch change bellcrank to the pitch change slider, became disconnected during operation due to inadequate installation. Specifically, the T-bolt attachment bolts were installed but not torqued and safety wired to maintenance manual requirements, allowing them to back out during operation. Once the T-bolt attachment bolts backed out, the T-bolt also backed out and separated from the pitch change slider, resulting in a loss of tail rotor pitch control. The T-bolt likely impacted one of the tail rotor blades, resulting in the separation of the outboard portion of its leading edge and afterbody. The subsequent imbalance of the tail rotor, due to the damaged tail rotor blade, led to overload separation of the upper portion of the vertical fin. During maintenance of the accident helicopter in the days leading up to the accident, the T-bolt and its attachment bolts were removed by a mechanic at the direction of a lead mechanic to facilitate troubleshooting of adjacent components for the tail rotor control system. That mechanic assumed that the T-bolt’s removal was temporary and quick, so he did not follow established procedures by recording the removal in the discrepancy sheet for the work order. The T-bolt attachment bolts were subsequently temporarily installed “finger-tight” by another mechanic to assist a mechanic who was installing the tail rotor blade mounting forks and pitch change links. However, the first mechanic was tasked to another company helicopter shortly after, and while he stated he relayed to the other mechanics that the T-bolt attachment bolts were finger-tight, no one followed up on the installation of the T-bolt attachment bolts to ensure they were torqued correctly and safety wired. Additionally, no one from the maintenance team found that the safety wiring for the T-bolt attachment bolts was missing during final checks of the helicopter before it was released for an operational check flight. Since there was no maintenance discrepancy entry for the removal of the T-bolt, there was no formalized task for the maintenance team to track and verify the complete T-bolt installation, including torquing and safety wiring the T-bolt attachment bolts. Therefore, the lack of an entry in the work order discrepancy sheet for the T-bolt’s removal contributed to this accident.
Probable cause
The failure of maintenance personnel to properly install the tail rotor pitch change slider attachment hardware (T-bolt), which led to the disconnection of the pitch change slider, a loss of tail rotor control, and subsequent hard landing. Contributing to the accident was maintenance personnel’s failure to complete a maintenance discrepancy entry on the work order for the removal of the T-bolt.
Verbatim NTSB analysis and probable cause from the NTSB dataset
Sources
NTSB record CEN24LA128
- Event ID
- 20240307193891
- Case number
- CEN24LA128
- 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: local date, investigation status, coordinates, cause areas. Values present in the bulk record are kept.
- The date is the local date; the NTSB stores the UTC date 2024-03-07.
- API snapshot SHA-256: 48d61231caacbdf545ebc4926b22fb6fb4ec98e6f35235f6e44b96b2b4540d43; retrieved 2026-09-16T18:34:11.413Z.