NTSB CAROL · Event
Event DFW05LA019
Aircraft involved
Probable cause & findings
The loss of tail rotor drive as a result of a blanket coming in contact with the tail rotor blades, after the baggage compartment door unlatched during flight. A contributing factor was the "dusk" light condition that prevailed at the time of the accident.
Factual narrative
On November 9, 2004, at 1731 central standard time, a Bell 206L1 helicopter, N1075P, was substantially damaged when it impacted terrain following a loss of control while in cruise flight near Sapulpa, Oklahoma. The commercial pilot, a paramedic, and a flight nurse sustained minor injuries. The helicopter was owned and operated by Air Evac Life Team, Inc., of West Plains, Missouri, a Part 135 on-demand air ambulance operator. Visual meteorological conditions prevailed throughout the area for the 14 Code of Federal Regulations Part 91 positioning flight for which a company visual flight rules (VFR) flight plan was filed. The flight refueled at and departed from the Richard Lloyd Jones Jr. Airport (RVS), near Tulsa, Oklahoma, approximately 1720, with the Cushing Regional Hospital Heliport (OK65), near Cushing, Oklahoma, as its intended destination. In a written statement, the 2,000-hour pilot reported that after an uneventful departure from RVS, he switched to the company dispatch frequency to open his company flight plan. Shortly after, while at an altitude of approximately 500-800 feet and an airspeed of 90 knots, the pilot heard a loud "bang." Following this "bang," the "engine noise increased and the flight controls were stiff." The pilot also stated that "he had no pedal control, and there were no warning or caution lights." The helicopter then made an extremely fast, uncommanded left yaw, and tail rotor effectiveness was lost. The helicopter was then in a nose-down attitude, such that the pilot was looking at the ground through the top portion of the co-pilot's window. Subsequently, the pilot lowered the collective and manipulated the flight controls to level the helicopter and maintain controlled flight. The pilot reported that as the helicopter was descending rapidly, he spotted a field and guided the helicopter toward it. He added that it was dusk, and as he descended behind a tree line, it was difficult to determine his altitude for deceleration and cushion. The pilot reported that the helicopter did not yaw until just prior to the hard landing. Following touchdown, the pilot shut-off the fuel and battery and told the passengers to exit the aircraft. The helicopter came to rest on its left side, and there was no post-impact fire. Examination of the wreckage by the FAA inspector, who responded to the accident site, revealed that some of the fly-away items and some medical supplies, normally stored in the baggage compartment, were found scattered along the route of flight short of the main wreckage. Examination of the baggage compartment door revealed that both door latches were unlatched, and the door was partially open. Further examination of the tail rotor drive shaft revealed a torsional fracture of the tail rotor drive shaft. Frayed fibers and material consistent with clothing or a blanket were found throughout the tail rotor assembly and tail rotor hub. The baggage compartment door latches were examined and appeared to be undamaged and fully functional. The helicopter was released to the operator for recovery to a secure location. The pilot reported that prior to the flight's refueling stop at RVS, the helicopter had been at Tulsa Regional Medical Center, which was the last time that the baggage compartment door had been opened. The pilot recalled that when leaving Tulsa Regional Medical Center, all three crewmembers approached the helicopter on its left side and recalled that the baggage compartment door was closed at that time. The pilot added that there were two oxygen containers in the cargo compartment that were stacked on one another and reached approximately the same height as the latch release button on the interior side of the baggage compartment door. The 2,000-hour helicopter pilot reported that after an uneventful departure, and while at an altitude of approximately 500-800 feet and an airspeed of 90 knots, he heard a loud "bang." Following this "bang," tail rotor effectiveness was lost, and the helicopter was forced into a sideways, nose-down attitude The pilot performed an autorotation and made a hard landing into a field. A "dusk" light condition prevailed, and the helicopter came to rest on its left side. Examination of the wreckage by the FAA inspector, who responded to the accident site, revealed that some of the fly-away items and some medical supplies, normally stored in the baggage compartment, were found scattered along the route of flight short of the main wreckage. Examination of the baggage compartment door revealed that both door latches were unlatched, and the door was partially open. Further examination of the tail rotor drive shaft revealed a torsional fracture of the tail rotor drive shaft. Frayed fibers and material consistent with clothing or a blanket were found throughout the tail rotor assembly and tail rotor hub. The pilot reported that there were two oxygen containers in the cargo compartment that were stacked on one another and reached approximately the same height as the latch release button on the interior side of the baggage compartment door. Source: NTSB Aviation Accident Database (Pre-2008 Archive) Retrieved: 2026-02-12
Verbatim from NTSB's published report. Source file
NTSB_2004_DFW05LA019.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 ↗