FLIGHT FINDINGSAVIATION OCCURRENCE MAP
Back to map

CEN17FA103 · Bell Helicopter Textron Canada 429

15 Feb 2017 · Shreveport, LA, United States

Bell Helicopter Textron Canada 429 · Accident: VFR encounter with IMC en route

From Bossier City, LA to Center Municipal Airport (F17)

Report a problem

Event

NTSB case
CEN17FA103
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
2 · 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 Helicopter Textron Canada 429

Aircraft type
Bell 429
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
N598PB
Operator
Unknown
Onboard fatalities
Unknown
Route
From Bossier City, LATo Center Municipal Airport (F17), Center, TX
Aircraft age
About 3 years (built 2014)
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
En route · cruise
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

  • Environmental issues › Conditions/weather/phenomena
  • Personnel issues › Psychological

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

NTSB narrative

While performing a dark night, cross-country flight, the helicopter cruised towards its destination. The helicopter impacted a marshy area of a lake. Impact signatures were consistent with the helicopter colliding with trees and terrain in a nose low attitude. Weather information for the time of the accident showed that the helicopter was operating in an area favorable for instrument flight rules (IFR) conditions due to precipitation and mist, cloud ceilings between 1,000 to 1,600 ft above ground level, and possible moderate turbulence. Due to cloud cover, it is likely that the Moon was not visible. There is no evidence that the pilot obtained a weather briefing prior to takeoff. The pilot's log books were not recovered during the investigation and the pilot's total time, and night experience is not known. While the pilot held a rating for instrument airplane, it is not known how much training the pilot obtained, if any, for an instrument helicopter rating. It is likely that the pilot had no more than 30 hours in make and model.

Data downloaded from onboard avionics found that the flight was uneventful until 4 minutes before the accident when the helicopter made a right turn and began flying to the southwest. As the helicopter tracked southwest, the altitude dropped to about 600 ft msl (500 ft above ground level [agl]). A minute later, the helicopter turned left turn and descended in the turn to about 420 ft agl before it pitched up to 40° nose high, resulting in a 2,500 ft per minute (fpm) climb. The helicopter momentarily stabilized on a 55° heading. At this time, the pilot armed the airspeed hold mode but did not turned on the force trim, so the autopilot would not engage. It is likely that the pilot expected the autopilot to engage, and when the helicopter began a left bank, he turned on the force trim but did not re-engage the autopilot. Shortly thereafter, the helicopter exceeded a 45° left bank and the pitch exceeded 40° nose low. The helicopter rapidly descended and impacted terrain. An examination of the avionics data, airframe, and engine did not identify any preimpact anomalies. While several substances were found in the pilot's toxicology, their use did not appear to contribute to the accident. The circumstances of the accident are consistent with the pilot's inadvertent encounter with instrument meteorological conditions, which resulted in in spatial disorientation, loss of control, and subsequent impact with terrain.

Probable cause

The pilot's inadvertent encounter with instrument meteorological conditions resulting in spatial disorientation, loss of control, and subsequent impact with terrain.

Verbatim NTSB analysis and probable cause from the NTSB dataset

Sources

NTSB record CEN17FA103
Event ID
20170215X50149
Case number
CEN17FA103
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: d920b663f35745656cdd9bc6d92a5d5587c4d9ff32e67d795dd58f074019b4ca; retrieved 2026-09-15T05:58:40.401Z.