CEN22FA073 · Bell Helicopter Textron Canada 407
RC Smith Aviation Bell Helicopter Textron Canada 407 · Accident: collision with terrain/object (non-CFIT) en route
From Baton Rouge, LA to Lakefront Airport (KNEW)
Event
- NTSB case
- CEN22FA073
- 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
- 0
- 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 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
- N150AS
- Operator
- RC Smith Aviation
- Onboard fatalities
- Unknown
- Route
- From Baton Rouge, LATo Lakefront Airport (KNEW), New Orleans, LA
- Aircraft age
- About 5 years (built 2016)
- 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
- Collision with terrain/object (non-CFIT)
- DamageDestroyed: beyond practical repair. Substantial: damage that affects the structure, performance or handling and normally needs major repair. Minor: less than that. Glossary
- Destroyed
Cause areas
- Personnel issues › Action/decision
Approximate · Coordinates from the NTSB case API, which marks them as estimated or does not say; no uncertainty radius is established.
NTSB narrative
The pilot was operating the helicopter in an area of low cloud ceilings, fog, and mist. Flight data showed that the helicopter’s altitude varied and that the maximum altitude reached was 175 ft above ground level. The last recorded altitude was 75 ft. The helicopter subsequently collided with a guy wire suspended between two transmission line trusses and impacted the highway below. A postimpact fire ensued and destroyed the helicopter. Postaccident examination of the airframe and engine revealed no anomalies that would have precluded normal operation of the helicopter. The pilot did not receive an official weather briefing before the flight. After the accident, a US Coast Guard pilot was deployed to the accident area. The Coast Guard pilot stated that a “wall of clouds” extended from the power lines westward to the accident area. Thus, the accident pilot likely could not see the power lines due to the reduced visibilities in mist and clouds at the accident time.
Probable cause
The pilot’s failure to maintain clearance from power lines. Contributing to the accident was the pilot’s decision to fly in instrument conditions.
Verbatim NTSB analysis and probable cause from the NTSB dataset
Sources
NTSB record CEN22FA073
- Event ID
- 20211214104406
- Case number
- CEN22FA073
- 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, cause areas. 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: ea16b41ab9ec1d20b5f53e1f546bd8095412e0cf378d14a875530e470f0b4555; retrieved 2026-09-15T07:39:06.435Z.