FLIGHT FINDINGSAVIATION OCCURRENCE MAP
Back to map

ERA Helicopters Eurocopter AS350 accident

12 Jan 2009 · Vermillion 229, United States

Eurocopter AS350 · Accident: collision during takeoff/landing

From V299 · Vermillion 229, GM to Cameron, LA

Report a problem

Event

NTSB case
CEN09CA127
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

Eurocopter AS350

Aircraft type
Eurocopter AS350
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
N193EH
Onboard fatalities
Unknown
Route
From V299 · Vermillion 229, GMTo Cameron, 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
Takeoff
Defining eventThe 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
Collision during takeoff/landing
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
Pole
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

  • Personnel issues › Psychological

Approximate · Coordinates as recorded by the NTSB; no uncertainty radius is established.

NTSB narrative

According to the pilot, he was departing the heliport at the oil rig platform and had brought the helicopter into a low hover. While in the hover, the tail rotor struck a two-foot vertical lightning rod attached to the platform edge causing damage to the tail rotor blades and horizontal stabilizer, wrinkling the tail boom, and displacing the tail rotor gear box. The pilot reported no mechanical anomalies with the helicopter prior to impact. The pilot stated that he had observed the lightning rod placement during previous landings on the platform as well as during the current operation.

Probable cause

The pilot's failure to maintain clearance from a known obstruction. Contributing to the accident was the location/placement of lightning rods in the landing zone.

Verbatim NTSB analysis and probable cause from the NTSB dataset

Sources

NTSB record CEN09CA127
Event ID
20090112X90757
Case number
CEN09CA127
Dataset
full-current
Source SHA-256
5cf380f0061817c0331a6b2d8cc7e0ee3a79bea469a1001dc5c10e56f35f5ab3
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: 4d05ab6a15b586f46e87ebcce16c4425dd45a9c971a30f69c720c869a2f5af96; retrieved 2026-09-15T10:41:03.006Z.