FLIGHT FINDINGSAVIATION OCCURRENCE MAP
Back to map

CEN13FA003 · Bell 407

5 Oct 2012 · Intracoastal City, LA, United States

Bristow US Bell 407 · Accident: VFR encounter with IMC during initial climb

From Central Industries Airport (2LA0) to Central Industries Airport (2LA0)

Report a problem

Event

NTSB case
CEN13FA003
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
1 · 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
Instrument Meteorological Cond

Bell 407

Aircraft type
Bell 407
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
N406AL
Operator
Bristow US
Onboard fatalities
Unknown
Route
From Central Industries Airport (2LA0), Intracoastal City, LATo Central Industries Airport (2LA0), Intracoastal City, LA
Aircraft age
About 11 years (built 2001)
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
Initial climb
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
VFR encounter with IMC
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

  • Aircraft › Aircraft oper/perf/capability
  • Environmental issues › Conditions/weather/phenomena
  • Personnel issues › Action/decision
  • Personnel issues › Task performance

Approximate · Coordinates from the NTSB case API, not marked as estimated; no uncertainty radius is established.

NTSB narrative

According to the operator, the pilot was performing a local postmaintenance flight following a routine phase check that had been completed the previous evening. Several witnesses reported seeing the helicopter start up and enter a low altitude hover before it hover-taxied toward the runway. One witness reported that she saw the helicopter depart on the runway heading and disappear into fog or a low cloud ceiling. Another witness, who also was a pilot employed by the operator, reported that there was mist, fog, and a low cloud ceiling when the helicopter departed.

Recovered flight data indicated that, about 20 seconds after takeoff, the helicopter reached a maximum altitude of 255 feet and ground speed of 51 knots while still on the runway heading. The helicopter then entered a left descending turn, during which, it reached a maximum bank angle of 38 degrees to the left and a 20-degree nose-down pitch angle. The helicopter also achieved a 1,600 ft per minute descent during the turn. After turning about 200 degrees from the original departure heading, the helicopter descended into trees and terrain in a nose-low, left-skid-low attitude.

The postaccident examination of the helicopter revealed no evidence of a preimpact failure or malfunction that would have precluded normal operation. Additionally, the engine exhibited damage consistent with it operating at the time of impact. The witness accounts of the helicopter climbing into a low cloud ceiling during initial climb and the subsequent descending left turn shown by the recovered flight data were consistent with the pilot inadvertently encountering instrument meteorological conditions and then attempting a course reversal. Additionally, the helicopter's descent rate and pitch and bank angles during the course reversal were consistent with the pilot lacking a discernible horizon or ground reference to maintain control of the helicopter. Although the helicopter was equipped with basic attitude instrumentation and avionics, it was not certified for flight under instrument flight rules (IFR). Additionally, although he held an instrument rating for helicopters, the pilot was not current for IFR operations nor was it required for his employment as a pilot of helicopters limited to visual flight rules operations.

Probable cause

The pilot’s decision to attempt a local flight in marginal visual meteorological conditions and his subsequent loss of control following an inadvertent encounter with instrument metrological conditions shortly after takeoff.

Verbatim NTSB analysis and probable cause from the NTSB dataset

Sources

NTSB record CEN13FA003
Event ID
20121005X04242
Case number
CEN13FA003
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, 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: bbd813217b3fd672de4defbf0b5f8c1b337012421efab9fcee87e768557c2b83; retrieved 2026-09-14T15:45:35.517Z.