Air Logistics Bell 206-L1 accident
Bell 206-L1 · Accident: loss of control in flight on approach
From Creole, LA (no airport) to WC 173, GM (no airport)
Event
- NTSB case
- FTW01LA172
- 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
- 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
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
- N2755N
- Operator
- Air Logistics
- Onboard fatalities
- Unknown
- Route
- From Creole, LA (no airport)To WC 173, GM (no airport)
- 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
- Approach · VFR pattern final
- 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
- Pilot in command › Tail rotor/anti-torque control, not maintained
Approximate · Coordinates from the NTSB case API, which marks them as estimated or does not say; no uncertainty radius is established.
NTSB narrative
After an uneventful flight, the pilot initiated an approach to an offshore platform into the wind, when the helicopter made an "uncontrolled, un-induced yaw to the right." He then attempted to turn to the right to stop the yaw and to maneuver away from the platform. As he increased power, the aircraft "went into an uncontrollable and rapid spin to the right." The pilot then closed the throttle and reduced power, which "slowed but did not stop the spin." Just as the pilot "pulled" collective, the aircraft impacted the water, rolled over, and sank. Flight control continuity checks were performed after the helicopter was recovered from the water. No anomalies were found within the tail rotor drive or flight control systems that could not be attributed to impact or recovery damage.
Probable cause
the pilot's failure to maintain yaw control of the helicopter during approach.
Verbatim NTSB analysis and probable cause from the NTSB dataset
Sources
NTSB record FTW01LA172
- Event ID
- 20010817X01718
- Case number
- FTW01LA172
- Dataset
- historical-pre2008
- Source SHA-256
- 89e2df6d848e7ab3b42e7d7c7a03ff403303057a26ca04c95b3ea67201c3ce74
Source notes (5)
- 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: 37c624c098c7d78cd1f7ff30f4a8dbcbdb6cdc0be396eee4d8e40df6b0a4f350; retrieved 2026-09-18T16:10:51.804Z.
- The NTSB's operator name is blank for N2755N; the operator shown is the name the NTSB records it doing business as.