MIA96LA200 · Bell 206B III
Bell 206B III · Accident: in flight collision with object en route
Event
- NTSB case
- MIA96LA200
- 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
- 1 · 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 206B III
- Aircraft type
- Bell 206
- 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
- N5015T
- Operator
- Unknown
- Onboard fatalities
- Unknown
- Route
- From not recordedTo 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
- 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
- In flight collision with object
- 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
- Wire, transmission
- DamageDestroyed: beyond practical repair. Substantial: damage that affects the structure, performance or handling and normally needs major repair. Minor: less than that. Glossary
- Destroyed
Cause areas
- Pilot in command › Altitude/clearance, not maintained
- Pilot in command › Visual lookout, not attained
Approximate · Coordinates as recorded by the NTSB; no uncertainty radius is established.
NTSB narrative
According to the operator of the helicopter, the purpose of the flight was to defoliate an area of vegetation near power lines by spraying chemicals. The loader of the chemicals indicated that when the flight was due to return for refueling, he observed smoke near where the helicopter was spraying. He then called 911 and reported the crash. Investigation revealed that one of the main rotor blades had contacted a power line that was 97 feet above ground level. The helicopter then descended and impact the ground nose low and rolled onto its right side where it came to rest. Impact damage to the cockpit from the main rotor blades was noted. Examination of the airframe and engine revealed no evidence of preimpact failure or malfunction. There were no known witnesses to the accident.
Probable cause
failure of the pilot to see-and/or-avoid the obstruction (unmarked power line), while en route between the area that was being treated and the refueling location. The power line and lack of visual cues at dusk were related factors.
Verbatim NTSB analysis and probable cause from the NTSB dataset
Sources
NTSB record MIA96LA200
- Event ID
- 20001208X06572
- Case number
- MIA96LA200
- 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: local date, investigation status. Values present in the bulk record are kept.
- The date is the local date; the NTSB stores the UTC date 1996-08-04.
- API snapshot SHA-256: 3491c4b4d0bb5fc4de0664d58cae09647ef623b293fb6ce6d6cd06c13544f209; retrieved 2026-09-20T23:14:35.646Z.