NTSB CAROL · Event
Event NYC06LA175
Aircraft involved
Probable cause & findings
A partial failure of the override clutch assembly. A contributing factor to the accident was the manufacturer's inadequate inspection procedures of the override clutch assembly following a tail rotor strike.
Factual narrative
On July 15, 2006, about 0915 eastern daylight time, an Enstrom 280C, N5691B, was substantially damaged during a precautionary landing in Danville, West Virginia. The certificated commercial pilot sustained minor injuries. Visual meteorological conditions prevailed and no flight plan was filed for the flight that departed the Logan County Airport (6L4), Logan, West Virginia, destined for the Greater Portsmouth Regional Airport, Portsmouth (PMH), Ohio. The solo cross-country instructional flight was conducted under 14 Code of Federal Regulations Part 91. According to his written statement, the pilot said he heard a "loud snap" and experienced a 5 to 10 degree right yaw, approximately 7 minutes after takeoff. Approximately 5 to 8 seconds later, he heard a second snapping sound, and again experienced a 5 to 10 degree right yaw. The pilot declared an emergency and elected to perform a precautionary landing at a strip mine. During the approach, he experienced a third snap sound and yaw movement. The helicopter was at an airspeed below 20 knots, and about 8 to 10 feet above the ground, when the pilot heard a bang, and felt ground contact. The helicopter rolled to the left, and the main rotor blades contacted the ground. Examination of the helicopter was conducted by a Federal Aviation Administration (FAA) inspector and representatives from Enstrom Helicopter. Drive train continuity was confirmed to the main and tail rotor drive shafts. A ground scar, consistent with tail rotor ground contact, was observed about 60 feet from the main wreckage. The tail rotor gear box, drive shaft and blade assembly were located about 250 feet from the main wreckage. The tail rotor assembly, 90-degree gearbox and the override clutch assembly were retained for further examination. Examination of the tail rotor gearbox and adjacent components at the National Transportation Safety Board Materials Laboratory, Washington DC, did not reveal any preexisting damage or failures. In addition, the examination did not reveal any indications of rotational damage. The override clutch assembly, which drove both the main transmission and the tail rotor system, was removed and examined at its manufacturer, under the supervision of an FAA inspector. According to the manufacturer's teardown report, damage was found in the clutch assembly that was consistent with impact damage sustained during the accident; however, damage was also found that was consistent with preexisting damage that occurred at an undeterminable time prior to the accident. The override clutch assembly had accumulated approximately 1,804.6 hours since new, and had a time between overhaul (TBO) interval of 2,400 hours. The accident helicopter was involved in a previous hard landing accident on August 12, 2005, during which, it experienced a tail rotor strike, and a fractured tail rotor drive shaft. According to maintenance records, the override clutch assembly was not removed for inspection after that accident. Review of the helicopter's maintenance manual did not reveal any information calling for an inspection of the override clutch assembly after a tail rotor blade strike. Enstrom service information letter (SIL) No. 0088, "Special Inspection for Sudden Stoppage, Main and/or Tail Rotor Blade Strikes" was in effect at the time of the accident; however, the SIL required that the override clutch assembly be inspected only during main rotor strikes and or sudden stoppage. According to the maintenance manual, SIL's were to be considered part of the maintenance manual, and were used to transmit information, recommendations, and general service instructions to the customer. The clutch assembly would not have been disassembled and inspected during routine 100-hour and annual inspection maintenance intervals. The helicopter had been operated approximately 87 hours since the previous accident. The override clutch assembly teardown report further stated that because the clutch assembly was not disassembled and inspected after the tail strike in August 2005, it was not possible to determine the amount of internal damage that the clutch assembly sustained at the time of that event, and may have accumulated during the subsequent hours of operation. The pilot held a commercial pilot certificate, with ratings for single and multiengine land airplanes, and was training for a rotorcraft rating with private pilot privileges. He reported 1,060 hours of total flight experience, which included about 30 hours in helicopters. Approximately 7 minutes after takeoff, the pilot of the helicopter heard a "loud snap," and experienced a 5 to 10 degree right yaw. This occurred a second time, 5 to 8 seconds later. The pilot declared an emergency and elected to make a precautionary landing. During the approach, he experienced a third snap sound and yaw movement. The helicopter was at an airspeed below 20 knots, and about 8 to 10 feet above the ground, when the pilot heard a bang, and felt ground contact. The helicopter rolled to the left, and the main rotor blades contacted the ground. Examination of the helicopter confirmed drive train continuity to the main and tail rotor drive shafts. A ground scar, consistent with tail rotor ground contact, was observed about 60 feet from the main wreckage. The tail rotor gear box, drive shaft and blade assembly were located about 250 feet from the main wreckage. Examination of the tail rotor gearbox and adjacent components did not reveal any preexisting damage; however, it also did not reveal any indications of rotational damage. Examination of the override clutch assembly, which drove both the main transmission and the tail rotor system, revealed preexisting damage that occurred at an undeterminable time prior to the accident. The accident helicopter was involved in a previous hard landing accident about 13 months, and 87 hours of operation prior, during which, it had a tail rotor strike, and a fractured tail rotor drive shaft. The override clutch assembly was not removed for inspection after that accident; nor was it specifically required to be removed and inspected per the manufacturer's maintenance guidelines for "Special Inspection for Sudden Stoppage, Main and/or Tail Rotor Blade Strikes." Source: NTSB Aviation Accident Database (Pre-2008 Archive) Retrieved: 2026-02-12
Verbatim from NTSB's published report. Source file
NTSB_2006_NYC06LA175.txt.
Findings + structured fields enriched from FAA avall.mdb.
Full investigation docket on
data.ntsb.gov ↗.
Beyond the agency record
Search this event elsewhere.
Pre-filled searches into the sources where news + community discussion of aviation events lives. External sources are reported, not agency. Treat them as signal that something happened, not as fact about what happened.
Entity-clustered aviation events in the press — last 24 hr + 30-day archive.
Official agency record + docket.
Investigative docket: factual reports, photos, transcripts.
Long-running aviation incident database (Flight Safety Foundation).
Community NTSB synthesis blog — often has photos and witness reports.
Gold-standard aviation incident blog.
Aviation industry news search.
GA pilot forum — informed but rumor-prone.
GA pilot subreddit search.
Tail-number page — flight history (free tier limited).
AOPA Air Safety Institute search.
Mainstream press coverage. Recent events only.
Privacy-preserving news search.
External links open in a new tab. We don't ingest their content; we deep-link search queries.
Related research
What the literature says.
Academic papers and agency reports matching this event's aircraft type or causal vocabulary (maintenance). Sourced from NASA NTRS, NTSB Safety Studies, FAA CAMI, AOPA Air Safety Institute, Embry-Riddle Scholarly Commons, arXiv, and the Semantic Scholar academic graph.
- Embry-Riddle Scholarly Commons 2026 · Journal article (IJAAA)
From Reactive to Predictive: A hybrid Trust-Mediated Adoption Framework for Data-Driven Maintenance in Distributed-Authority Aviation Environments
Modern aviation maintenance operates within increasingly data-intensive technological environments, yet the operational integration of predictive maintenance into routine decision-making remains incon…
- Semantic Scholar 2025 · Article (Applied Sciences)
Decision-Making Framework for Aviation Safety in Predictive Maintenance Strategies
The implementation of predictive maintenance (PM) in aviation presents unique challenges due to strict safety requirements, complex operational environments, and regulatory constraints.
- Embry-Riddle Scholarly Commons 2024 · Journal article (JAAER)
Low-Resource Automatic Speech Recognition Domain Adaptation – A Case-Study in Aviation Maintenance
With timeliness and efficiency being critical in the aviation maintenance industry, the need has been growing for smart technological solutions that optimize and streamline the different underlying ta…
- Embry-Riddle Scholarly Commons 2024 · Journal article (JAAER)
A New Trajectory in UAV Safety: Leveraging Reinforcement Learning for Distance Maintenance Under Wind Variations
In the field of aviation, safety is a critical cornerstone, and the operation of Unmanned Aerial Vehicle (UAV) systems is deeply connected with this principle.
- Embry-Riddle Scholarly Commons 2024 · Journal article (IJAAA)
Just Culture in Aviation: A Metaphorical Study on Aircraft Maintenance Students
Just Culture, a sub-dimension of safety culture, has been a prominent and debated topic in aviation safety in recent years.
- Embry-Riddle Scholarly Commons 2024 · Journal article (IJAAA)
Performance PRISM: A Comprehensive Framework For Performance Measurement In Aircraft Maintenance
Aircraft maintenance is governed by rigorous safety requirements and high operational complexity, demanding robust performance measurement frameworks to ensure optimal maintenance practices.
Browse the full corpus — academia portal ↗