DFW05LA252 · Bell 206B
Bell 206B · Accident: loss of control in flight while maneuvering
From Myu Heliport (LS97) to an unrecorded destination
Narrative check · The NTSB narrative appears to contradict this record's flight rules. Values are shown as recorded, not corrected; compare with the narrative.
Event
- NTSB case
- DFW05LA252
- 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
- Unknown
- 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
- 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
- N59539
- Operator
- Unknown
- Onboard fatalities
- Unknown
- Route
- From Myu Heliport (LS97), Luling, LATo 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 91: General Aviation Possible conflict
- 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
- Loss of control in flight
- 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
- Reason for occurrence undetermined
Approximate · Coordinates from the NTSB case API, which marks them as estimated or does not say; no uncertainty radius is established.
NTSB narrative
The private pilot was flying three passengers for hire along the Mississippi River, to inspect and look for missing barges following Hurricane Katrina, when he experienced a loss of tail rotor control. At an altitude about 200 feet above ground level (agl), the helicopter took a sudden right turn and climbed approximately 100 feet before it started spinning in a clockwise direction and descended. The helicopter continued to spin until it impacted a barge and fell into the river about 300 feet from the riverbank. The pilot and passengers were able to egress the sinking helicopter and swam to shore unassisted. A review of Federal Aviation Administration (FAA) airman records revealed the pilot held a private pilot certificate with ratings for airplane single-engine land and helicopter. Multiple attempts to obtain a completed Pilot/Operator Aircraft Accident Report (NTSB Form 6120.1/2) from the pilot were unsuccessful. As of January 23, 2006, the helicopter had not been located or recovered.
Probable cause
The pilot's loss of control in flight for undetermined reasons.
Verbatim NTSB analysis and probable cause from the NTSB dataset
Sources
NTSB record DFW05LA252
- Event ID
- 20051013X01646
- Case number
- DFW05LA252
- 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, coordinates. 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: 3255a28c0c1fe347cee89c1367665ed54f56f64ac98612cfc3793b0737962c79; retrieved 2026-09-21T18:54:53.582Z.