NTSB CAROL · Event
Event IAD05LA122
Aircraft involved
Probable cause & findings
The pilot's inadequate remedial action following a loss of control during the landing approach.
Factual narrative
On August 12, 2005, about 1330 eastern daylight time, an Enstrom 280C, N5691B, received substantial damage when it impacted terrain near Saulsville, West Virginia. The certificated commercial pilot was not injured, and the passenger received serious injuries. Visual meteorological conditions prevailed, and no flight plan was filed for the business flight, which originated at Logan County Airport (6L4), Logan, West Virginia, about 1300, and was conducted under 14 CFR Part 91. According to the pilot, the purpose of the flight was to drop off a package at a local community college. While on approach to the landing area, the pilot did not see a windsock, and based his estimation of the wind direction by watching leaves on the trees. During the final approach, he adjusted the flight controls to decelerate and maintain the approach angle to the touchdown point, while maintaining the rotor rpm at 2,900. The helicopter approached the intended landing area at a "normal to steep angle." Without any further control inputs, and while stabilized at approximately 40 knots indicated airspeed, about 100 feet above the ground, the helicopter began a slow, un-commanded yaw to the right. The pilot responded by applying left anti-torque pedal; however, the helicopter continued to yaw to the right. As the helicopter turned beyond about 90 degrees from the original flight path, the pilot realized that he would not be able to land the helicopter in the intended landing area. He then checked the rotor and engine rpm and noted that they were "out of the green and decreasing." The pilot felt that he could not enter an autorotation due to a power line that was below, and instead increased the throttle to stabilize rotor rpm and maintain altitude in order to fly to a more suitable area for landing. The helicopter "did not respond," and continued yawing to the right. About 10 feet above the ground, and after about 270 degrees of yaw from the original direction of flight, the helicopter descended rapidly and impacted the ground. The pilot held a commercial pilot certificate with a rating for rotorcraft-helicopter and a flight instructor certificate with a rating for rotorcraft-helicopter. He reported 297 total hours of flight experience, 15 hours of which were in the accident helicopter make and model. The helicopter was examined following the accident. The left skid was broken, and the tail rotor sustained damage to both blades consistent with impact. Additionally, the tail rotor drive shaft was fractured at the coupling hub. The coupling hub, flex pack, coupling flange, drive shaft, and associated components were forwarded to the Safety Board Materials Laboratory for further examination. Examination of the fractured portions of the coupling hub revealed that the fracture regions on both sides of the taper pin hole displayed light circumferential smearing and distinct circumferential surface lines that were consistent with torsional overload. There was no discoloration or severe mechanical damage observed on the fracture faces to indicate that the mating fracture faces had rubbed together while the system was transmitting power. Displaced material, oriented counter to the direction of rotation, was found on the sides of the exposed taper pin hole, consistent with a torsional event. The weather reported at Raleigh County Memorial Airport (BKW), Beckley, West Virginia, about 17 nautical miles east, at 1351, included calm winds, scattered clouds at 4,400 feet, 4 statute miles visibility in haze, temperature 82 degrees Fahrenheit, dewpoint 64 degrees Fahrenheit, and an altimeter setting of 30.10 inches of mercury. The elevation in the area of the accident site was about 2,000 feet, and the density altitude was calculated to be about 3,900 feet around the time of the accident. According to the Enstrom 280C Flight Manual, steep approach procedures are used to clear obstacles in the flight path when landing in a confined area, and require precision power control. The airspeed of a steep approach should be between 30 and 35 mph, and the rate of descent should be as low as possible for the desired angle of descent. A relatively high amount of power is required to control the rate of descent. According to Federal Aviation Administration Advisory Circular (AC) 90-95, Unanticipated Right Yaw in Helicopters, loss of tail rotor effectiveness (LTE) events typically occur in a low airspeed flight regime while maneuvering, on final approach to landing, or during low-level flying. Any maneuver that requires the pilot to operate at high-power, at low airspeed, and with a left crosswind or tailwind, creates an environment where unanticipated right yaw may occur. Additional factors that can influence the severity of the onset of LTE include increases in gross weight and density altitude, low indicated airspeeds, and "power droop," or a decrease in rotor rpm that causes a corresponding decrease in tail rotor thrust. The AC also provided guidance regarding recovery techniques following an LTE event. If a sudden unanticipated right yaw occurs, the pilot should apply full left pedal, while simultaneously moving the cyclic forward to increase speed, and altitude permitting, reduce power. Following the recovery, the controls should be adjusted for normal forward flight. A collective pitch reduction will aid in arresting the yaw rate, but may cause an increase in the rate of descent. Any large, rapid increase in collective pitch to prevent ground or obstacle contact may further increase the yaw rate, and decrease rotor rpm. While on approach to the landing area, the pilot could not see a windsock, and based his estimation of the wind by watching leaves on the trees. As he approached the landing area at a "normal to steep angle," and while stabilized at approximately 40 knots indicated airspeed, about 100 feet above the ground, the helicopter began a slow, un-commanded yaw to the right. The pilot responded by applying left anti-torque pedal; however, the helicopter continued to yaw to the right. The pilot observed that the engine and rotor rpm were "out of the green," but felt that he could not enter an autorotation due to a power line that was below. He instead increased the throttle, and the helicopter continued to yaw to the right. About 10 feet above the ground, and after about 270 degrees of yaw, the helicopter descended rapidly and impacted the ground, seriously injuring the passenger. Examination of the helicopter following the accident revealed that the tail rotor had sustained impact damage to both blades, and that the tail rotor drive shaft was fractured at the coupling hub. Examination of the fractured portions of the coupling hub revealed signatures consistent with a torsional event, such as a tail rotor strike, and no evidence that the fracture surfaces were rubbing against each other under power. According to Federal Aviation Administration Advisory Circular 90-95, loss of tail rotor effectiveness (LTE) events typically occur in a low airspeed flight regime while maneuvering, such as on final approach to landing. Any maneuver that requires the pilot to operate at high-power, at low airspeed, and with a left crosswind or tailwind, creates an environment where unanticipated right yaw may occur. Additional factors that can influence the severity of the onset of LTE include increases in gross weight and density altitude, low indicated airspeeds, and power droop. Recovery from an LTE event should include the application of full left pedal, while simultaneously moving the cyclic forward to increase speed, and altitude permitting, a reduction in power. Source: NTSB Aviation Accident Database (Pre-2008 Archive) Retrieved: 2026-02-12
Verbatim from NTSB's published report. Source file
NTSB_2005_IAD05LA122.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 (loss of control). 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 2025 · Journal article (JAAER)
A Scoping Review of Aviation Loss of Control Inflight Research
Loss of control – inflight (LOC-I) contributes to aircraft accidents at unacceptably high rates. Significant industry efforts and research have aimed to improve LOC-I prevention, detection, and recove…
- SKYbrary (Eurocontrol) 2024 · SKYbrary article
Loss of Control In-Flight (LOC-I) — SKYbrary Knowledge Base
SKYbrary comprehensive knowledge-base entry on Loss of Control In-Flight — definitions, contributing factors, accident case studies (Air France 447, Colgan 3407), and prevention strategies.
- NTSB Aircraft Accident Reports 2022 · Accident report
Loss of Control on Takeoff in Icing Conditions — Citation 560XL
Cessna Citation 560XL fatal takeoff icing accident, March 2018. Investigation of a Citation 560XL loss-of-control takeoff accident in icing conditions.
- Semantic Scholar 2021 · Article (Aviation)
ANALYSIS OF GENERAL AVIATION FIXED-WING AIRCRAFT ACCIDENTS INVOLVING INFLIGHT LOSS OF CONTROL USING A STATE-BASED APPROACH
Inflight loss of control (LOC-I) is a significant cause of General Aviation (GA) fixed-wing aircraft accidents. The United States National Transportation Safety Board’s database provides a rich source…
- NASA NTRS 2021 · Presentation
Use of Design of Experiments in Determining Neural Network Architectures for Loss of Control Detection
Abstract—We describe empirical methods for selecting a neural network architecture to implement belief state inference on generic commercial transport aircraft.
- NASA NTRS 2021 · Conference Paper
Use of Design of Experiments in Determining Neural Network Architectures for Loss of Control Detection
We describe empirical methods for selecting a neural network architecture to implement belief state inference on generic commercial transport aircraft.
Browse the full corpus — academia portal ↗