FLIGHT FINDINGSAVIATION OCCURRENCE MAP
Back to map

CEN11CA232 · Bell 230

17 Mar 2011 · Gulf of Mexico, LA, United States

Republic Helicopters Bell 230 · Accident: collision during takeoff/landing

From Republic Helicopters Heliport (2TE1) to Gulf of Mexico, LA (private airstrip)

Report a problem

Narrative check · The NTSB narrative appears to contradict this record's departure or destination. Values are shown as recorded, not corrected; compare with the narrative.

Event

NTSB case
CEN11CA232
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 230

Aircraft type
Bell 230
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
N974RH
Onboard fatalities
Unknown
Route Narrative disagrees
From Republic Helicopters Heliport (2TE1), Santa Fe, TXTo Gulf of Mexico, LA (private airstrip)
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
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
Landing
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
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 › Action/decision

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

NTSB narrative

The pilot was asked to reposition the helicopter on the helideck in an effort to clear a space for a helicopter that was coming in to land. During the repositioning landing, the pilot felt a high frequency vibration and the helicopter began to shudder. The pilot landed and after egressing the helicopter, discovered that a piece of tail rotor skin was lodged in the skirting; the tailrotor had impacted the safety skirting. The helicopter's tailboom sustained substantial damage. The pilot reported that there were no preimpact mechanical malfunctions with the helicopter.

Probable cause

The pilot's failure to maintain adequate clearance from the safety skirting during the repositioning landing.

Verbatim NTSB analysis and probable cause from the NTSB dataset

Sources

NTSB record CEN11CA232
Event ID
20110317X02351
Case number
CEN11CA232
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: 2012bde8364b04c406b9dc3e516753d2dc3a866df484a6acfb69e8303021984d; retrieved 2026-09-15T15:55:09.196Z.