CHI06LA124 · Hughes 269B
Hughes 269B · Accident: airframe, component or system failure en route
From Sullivan, OH (private airstrip) to an unrecorded destination
Event
- NTSB case
- CHI06LA124
- 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
- 0 · 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
- Visual Meteorological Cond
Hughes 269B
- Aircraft type
- Hughes 269
- 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
- N9471F
- Operator
- Unknown
- Onboard fatalities
- Unknown
- Route
- From Sullivan, OH (private airstrip)To not recorded
- Aircraft age
- Not recorded
- 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
- First occurrenceThe 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
- Airframe, component or system failure
- 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
- Fuselage, attachment › Fatigue
- Other maintenance personnel › Maintenance, compliance with ad, not complied with
- Rotor drive system, tail rotor drive shaft › Failure
Approximate · Coordinates from the NTSB case API, which marks them as estimated or does not say; no uncertainty radius is established.
NTSB narrative
The helicopter was substantially damaged when a tail boom support fitting failed during cruise flight, which resulted in a secondary failure of the tail rotor drive shaft. The pilot initiated an autorotation and encountered a ditch during touchdown, causing the right skid to collapse. The pilot reported that the helicopter was in cruise flight when he heard a "very loud" bang. He stated that the aircraft began to yaw and he subsequently determined the aircraft had no tail rotor authority. He set up for a run-on landing to a field; however, he subsequently heard a "metal grinding sound" and a "high pitched squealing noise." He initiated an autorotation at that time. The pilot reported a "sensation of the tail boom swinging left [and] right, up [and] down." The helicopter encountered a ditch during touchdown, which collapsed the right skid. Upon exiting the helicopter, the pilot noticed that the left main tail boom support (cluster) fitting had broken loose from the frame. The tail rotor drive shaft and cluster fitting were examined by the National Transportation Safety Board Materials Laboratory. Damage to the tail rotor drive shaft was consistent with an overstress failure and appeared to be caused by rotational contact between the drive shaft and the forward tail boom closure fitting. The cluster fitting exhibited fracture markings indicative of fatigue. Fracture features on both lugs indicated localized fatigue origin areas on the outer surfaces of each lug. Federal Aviation Administration (FAA) Airworthiness Directive (AD) 2003-13-15 R1, which became effective August 10, 2004, was applicable to the accident aircraft. The AD noted that compliance was required in order "to prevent failure of a tailboom support strut or lug on a cluster fitting." The AD required modification or replacement of the original cluster fittings, part numbers 269A2234 and 269A2235, within 6 months or 150 hours time-in-service (TIS). The AD required dye penetrant inspections of the lugs within 10 hours TIS, and thereafter at intervals not to exceed 50 hours TIS, until the lugs were modified or replaced. Nominal measured lug thickness was 0.076 inch, which was consistent with the original cluster fitting configuration. The failed lug did not appear to have been modified and did not appear to be in compliance with the AD. Review of the aircraft logbook revealed that a 100 hour / annual inspection was completed on May 23, 2005. The inspection entry noted AD 2003-13-15 R1. In addition, the airworthiness compliance record noted that the AD had been complied with by performing a dye penetrant inspection without finding any cracks. The entry also stated that the modification kit was not installed at that time.
Probable cause
Fatigue failure of the fuselage-to-tail boom cluster fitting, and the secondary failure of the tail rotor drive shaft. An additional cause was the incomplete compliance with an applicable Airworthiness Directive. A factor was the ditch.
Verbatim NTSB analysis and probable cause from the NTSB dataset
Sources
NTSB record CHI06LA124
- Event ID
- 20060511X00548
- Case number
- CHI06LA124
- Dataset
- historical-pre2008
- Source SHA-256
- 89e2df6d848e7ab3b42e7d7c7a03ff403303057a26ca04c95b3ea67201c3ce74
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: 13748ab5cf0d3a208467ac28fcb8e09ccd0ab86158186da388b8707212402244; retrieved 2026-09-22T04:56:57.103Z.