FLIGHT FINDINGSAVIATION OCCURRENCE MAP
Back to map

ENG23LA045 · Bell 407

21 Sept 2023 · Linden, NJ, United States

Helicopter Flight Services Bell 407 · Incident

Report a problem

Event

NTSB case
ENG23LA045
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
Incident
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
Event fatalities
Unknown
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
Unknown
WeatherVisual meteorological conditions (VMC): good enough to fly by looking outside. Instrument conditions (IMC): cloud or low visibility, flying by instruments. Glossary
Unknown

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
N406TD
Onboard fatalities
Unknown
Route
From not recordedTo not recorded
Aircraft age
About 17 years (built 2006)
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
Unknown
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
Unknown
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
Unknown or undetermined
DamageDestroyed: beyond practical repair. Substantial: damage that affects the structure, performance or handling and normally needs major repair. Minor: less than that. Glossary
None

Cause areas

  • Aircraft › Aircraft structures

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

NTSB narrative

The upper-left tail boom attachment bolt failed due to fatigue fracture and subsequent overload. Fatigue cracking initiated on the upper-left tail boom attachment bolt due to abnormal loading of the bolt shank caused by the presence of a gap and misalignment between the aft fuselage upper-left longeron and the tail boom. The gap and misalignment were likely introduced during installation of a new upper-left longeron in 2014, about 3,858.9 flight hours prior to discovery of the fractured upper-left attachment bolt. After the upper-left attachment bolt fractured, the load normally carried by the upper-left attachment fitting was redistributed to the remaining three tail boom attachment fittings. As a result, multiple-origin fatigue cracking initiated on the lower-left longeron fitting. This incident was the third known occurrence involving a fractured upper-left tail boom attachment bolt due to a gap and misalignment of the upper-left longeron. (In NTSB investigation ANC22FA041, one of the three occurrences, the upper-left tail boom attachment bolt was not found, but the upper-left tail boom attachment bolt likely fractured based on the available information.) In the three occurrences, each involving a different repair facility, the upper-left longeron was installed in accordance with Bell Technical Bulletin (TB) 407-12-96. Bell TB 407-12-96 did not contain steps to verify the absence of gaps and misalignment between the upper-left longeron and the aft fuselage bulkhead at the end of their installation instructions. The lack of these verification steps was a factor in the nondetection of the gap and misalignment that were introduced during the upper-left longeron installation for these three occurrences. On June 8, 2022, a Bell 407 helicopter, N402SH, experienced an inflight separation of its tail boom (NTSB investigation ANC22FA041). During the N402SH investigation, the NTSB issued safety recommendations A-22-29 and A-22-31 to the Federal Aviation Administration (FAA) and Transport Canada Civil Aviation (TCCA), respectively, to require subsequent torque checks of the tail boom attachment hardware be performed at a more stringent interval until the causal factors of the N402SH accident could be determined and corrective actions enacted. The FAA and TCCA did not take the recommended action and the tail boom attachment hardware torque check interval remained unchanged at 300-hours. As a result, the incident operator did not discover the fractured upper-left attachment bolt until a scheduled 300-hour inspection, by which time a fatigue crack on the lower-left tail boom attachment fitting had already initiated and grew. The combination of a loss of the upper-left tail boom attachment load path and fatigue crack growth on the lower-left longeron fitting substantially increased the risk of an inflight tail boom separation. Had the FAA and TCCA adopted the NTSB’s previously recommended action, the operator of this incident would have had more opportunities to detect the fractured upper-left attachment bolt, mitigating the risk of an inflight tail boom separation.

Probable cause

The fracture of the upper-left tail boom attachment bolt due to abnormal loading of the bolt caused by a gap and misalignment between the upper-left longeron and the tail boom. Contributing to this incident was the lack of a check to verify the absence of gaps or misalignments at the conclusion of installation for the upper-left longeron.

Verbatim NTSB analysis and probable cause from the NTSB dataset

Sources

NTSB record ENG23LA045
Event ID
20240117193675
Case number
ENG23LA045
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, damage. 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: 180588e736eb7eb1a7edabf3d5b313440fa2ac0879554593d0ece9d90ba4aecf; retrieved 2026-09-16T18:26:42.398Z.