MIA96LA144 · Bell UH1B
Bell UH1B · Accident: airframe, component or system failure while maneuvering
From No airport to an unrecorded destination
Event
- NTSB case
- MIA96LA144
- 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
Bell UH1B
- Aircraft type
- Bell UH1
- 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
- N3880A
- Operator
- Unknown
- Onboard fatalities
- Unknown
- Route
- From No airportTo not recorded
- 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 137: Agricultural
- 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
- Maneuvering
- 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
- Also codedOther events the NTSB coded in the sequence, such as a wire strike after a loss of power. Flight Findings uses them for its kinds of event. Glossary
- Tree(s)
- 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, tail rotor drive shaft › Failure
- Rotorcraft flight control, tail rotor cable › Loose part/bolt/nut/clamp/etc
Approximate · Coordinates as recorded by the NTSB; no uncertainty radius is established.
NTSB narrative
While refueling the helicopter the pilot and his crew saw smoke coming from the 'hell hole' on the bottom of the helicopter. They could not determine where the smoke was coming from, so the pilot elected to reposition the helicopter away from the fuel pad. After lift-off, there was a 'loud pop' and the helicopter immediately started rotating to the right. In an effort to avoid striking the fuel tank the pilot added power, and the wind carried the helicopter across the top of the tank. The spinning rotation increased, and after crossing the fuel tank the pilot reduced power. As the helicopter started to come around and get closer to the ground, it went backwards and struck a tree. After impact with the ground the helicopter rolled on its left side. Examination of the helicopter revealed that the tail rotor cable retaining pin came loose, and had rubbed against the tail rotor shaft, subsequently causing the drive shaft to fail.
Probable cause
the failure of the tail rotor drive shaft which resulted in a loss of tail rotor control.
Verbatim NTSB analysis and probable cause from the NTSB dataset
Sources
NTSB record MIA96LA144
- Event ID
- 20001208X05836
- Case number
- MIA96LA144
- 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: f619d1ba9b5b51be966891a689c743b5ce79a13a9308021cdce68d7124938818; retrieved 2026-09-22T22:24:56.056Z.