FLIGHT FINDINGSAVIATION OCCURRENCE MAP
Back to map

American Helicopters Bell 206-L1 accident

24 Jun 2004 · Vermillion Bay, LA, United States

Bell 206-L1 · Accident: in flight encounter with weather en route

From EI-349, GM (no airport) to 0R3 · Abbeville, LA

Report a problem

Event

NTSB case
FTW04FA168
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
3 · 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
Charter & commuter
WeatherVisual meteorological conditions (VMC): good enough to fly by looking outside. Instrument conditions (IMC): cloud or low visibility, flying by instruments. Glossary
Instrument Meteorological Cond

Bell 206-L1

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
N5006F
Onboard fatalities
Unknown
Route
From EI-349, GM (no airport)To 0R3 · Abbeville, LA
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 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
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 encounter with weather
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 › Aircraft control, not maintained
  • Pilot in command › Flight into adverse weather, continued
  • Pilot in command › In-flight planning/decision, improper

Approximate · Coordinates from the NTSB case API, which marks them as estimated or does not say; no uncertainty radius is established.

NTSB narrative

The 6,562-hour commercial rated helicopter pilot encountered adverse weather while on a 114-nautical mile over water cross-country flight. The pilot contacted his company's flight following with a normal position report and reported inbound on a Gulf of Mexico operation. Approximately eight minutes later, the accident pilot contacted his company's flight following and changed his destination to another heliport, but did not give a reason for the change of destination. He also reported his estimated time of arrival and that he was 45 miles out. At the helicopters approximate time of arrival, another helicopter pilot monitoring a common VHF radio frequency, overheard a mayday distress call. He then replied by asking for the accident pilot's location, but received no response. A moment later, another mayday distress call was heard followed by, "going in the water." There were no further communications or reported distress calls, and no reported eyewitnesses. A Convective SIGMET advisory was valid at the time of the accident. The SIGMET warned of embedded thunderstorms moving from 220 degrees at 25 knots, with tops above 45,000 feet. This advisory encompassed the area of the accident site. There was no report of the pilot obtaining any formal preflight weather briefing (from a company, flight service station, DUATS or WSI weather program) prior to departure or en route.

Probable cause

The pilot's continued flight into adverse weather conditions resulting in a loss of control. Contributing factors were the prevailing thunderstorms and the pilot's inadequate in flight preparation and planning.

Verbatim NTSB analysis and probable cause from the NTSB dataset

Sources

NTSB record FTW04FA168
Event ID
20040713X00966
Case number
FTW04FA168
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: ede32165b75c4577fa218a20e3de02310579f0de13ad4378fda001e1f83d1f88; retrieved 2026-09-18T13:00:33.401Z.