ERA21FA195 · Bell Helicopter Textron Canada 429
Duke Energy Business Services Bell Helicopter Textron Canada 429 · Accident: part(s) separation from aircraft while maneuvering
From Danville Regional Airport (DAN) to Burlington Alamance Regional Airport (BUY)
Event
- NTSB case
- ERA21FA195
- 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
- Visual 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
- N53DE
- Operator
- Duke Energy Business Services
- Onboard fatalities
- Unknown
- Route
- From Danville Regional Airport (DAN), Danville, VATo Burlington Alamance Regional Airport (BUY), Burlington, NC
- Aircraft age
- About 2 years (built 2019)
- 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
- Maneuvering · low-altitude flying
- 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
- Part(s) separation from aircraft
- 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
- Aircraft › Aircraft oper/perf/capability
- Aircraft › Aircraft propeller/rotor
Approximate · Coordinates as recorded by the NTSB; no uncertainty radius is established.
NTSB narrative
The helicopter departed and flew cross-country to begin a powerline patrol, which included flying adjacent to powerlines at an altitude of about 100 ft above ground level and with the helicopter gaining altitude during turns and when flying between line inspections. During the final minutes of flight, the helicopter was traveling at an airspeed between 50 and 60 kts along powerlines at an altitude between 700 and 775 ft above mean sea level (msl). As the helicopter flew south, near the end of the north-south powerline’s right of way, the helicopter began a climbing right turn towards the west. A utility lineman in the helicopter’s front left seat recalled that the pilot was reversing course and the helicopter was in a banking turn to the right when he heard a very loud noise, “almost cannon-like, very deep, within a second or two we were heading into the trees.” Onboard data recovered from the helicopter showed rotor speed suddenly increased to 107% about 1.5 seconds before the end of recorded data. Examination of the wreckage showed evidence the main rotor blades impacted the tail rotor drive system. Therefore, it is likely the loud noise heard by the onboard lineman was caused by the main rotor blades impacting the tail rotor drive system, resulting in a severance of the tail rotor drive shaft and subsequently a loss of directional control. Successful recovery of the helicopter after the loss directional control at a low altitude was unlikely and resulted in impact with terrain. Based on analysis of flight data and a scan of the local terrain, it is unlikely the helicopter impacted powerlines or nearby trees at the time the main rotor blades impacted the tail rotor drive system. The loss of clearance between the main rotor and the tail of the helicopter can be caused by sudden aft cyclic control inputs, usually in conjunction with a reduction in collective pitch that would reduce main rotor thrust and increase downward flapping of the blade. The lack of flight control parametric data precluded analysis of flight control inputs at the time the main rotor blade contacted the tail boom. However, it is likely the pilot was not maneuvering to avoid trees based on the increasing distance between the accident helicopter and treetops near the end of the accident flight. Examinations of the helicopter wreckage found no evidence of any preimpact anomalies or malfunctions that would have precluded normal operation of the helicopter.
Probable cause
The impact of the main rotor blades with the tail boom during low-altitude maneuvers, which severed the tail rotor drive shaft and resulted in a loss of control and impact with terrain.
Verbatim NTSB analysis and probable cause from the NTSB dataset
Sources
NTSB record ERA21FA195
- Event ID
- 20210428102994
- Case number
- ERA21FA195
- 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, 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: 681ffd90fe17b0c9ae443f4bc8a5ee48f495b7991f59c5699da7db4273ca5993; retrieved 2026-09-15T07:27:50.732Z.