NTSB CAROL · Event
Event MIA99LA133
Aircraft involved
Probable cause & findings
An in-flight loss of control caused by the main rotor severing the tail rotor drive shaft as a result of the pilot's cyclic pull-up into a tailwind for his second approach and landing. The loss of the tail rotor caused an uncontrollable descent and tree strike with the main rotor and in-flight collision with terrain. Contributing to the accident was the pilot's improper decision to make a downwind approach and landing.
Factual narrative
On April 19, 1999, about 0730 central daylight time, a Bell 47-G3B, N32PH, registered to Provine Helicopter Service, Inc., operating as a 14 CFR Part 137 aerial application flight, crashed while attempting a liftoff from a truck mounted platform near Thomastown, Mississippi. Visual meteorological conditions prevailed and no flight plan was filed. The helicopter sustained substantial damage and the commercially-rated pilot and a passenger reported no injuries. The flight originated about 30 minutes before the accident. The pilot stated he departed with the land owner for an orientation flight over the tract to be sprayed. Upon completion of the orientation flight, he returned to the "nurse truck" and made an approach to deplane the land owner. He was not content with his landing skid placement on the platform and pulled up for a second approach, when the helicopter started an uncommanded yaw, followed by an uncontrolled rotation. He stated he thought the passenger had stepped on the right anti-torque pedal. He maneuvered the helicopter away from the truck, but the main rotor blades collided with a small tree, the right landing skid hit the terrain hard enough to collapse, and the aircraft came to rest on its right side. According to the two-man ground crew, as the helicopter was lifting off the platform for better positioning on the platform, they heard a "loud bang similar to a shotgun blast". They saw a piece of the aircraft fly away and the tail rotor stopped turning. The helicopter performed multiple rotations, tilted toward its right side, and impacted a stand of small trees with its main rotor blades. The helicopter came to rest on its right side within the trees. Subsequent examination of the accident site and interview of the pilot, ground crew, and land owner by Federal Aviation Administration (FAA) inspectors, revealed that the pilot was making a downwind approach to the platform in order to position the passenger near the ladder to expedite his exit off the platform. The wreckage revealed the throttle was fully open and the right anti-torque pedal was full forward. A 16-inch section of tail rotor drive shaft located in the plane of the main rotor tips was missing and the tail boom truss had sustained a main rotor blade strike. One of the main rotor blade tips (outer 4-6 inches) had witness marks that would be consistent with striking the tail rotor shaft. Except for the aforementioned, the inspectors could find no mechanical malfunctions of the pilot's flight or engine controls, the engine or its components, or the transmission or drive train to the main or tail rotor systems. The FAA operations inspector stated, "It appears that the pilot through cyclic and collective control input caused the rotor blades to make contact with the tailboom and tailrotor drive shaft". The pilot stated he was pulling up the aerial spray rigged helicopter from the platform of the 'nurse truck' in order to reposition for a better placement on the platform, when he experienced uncommanded rotation. His ground crew stated, as he pulled up, a piece of the aircraft flew off and the tail rotor began to spin down. The aircraft went into an uncontrollable rotation, and the main rotor blades collided with an adjacent small tree stand. The helicopter impacted the terrain, the right landing skid collapsed, and the helicopter rolled over on its right side. Subsequent examination of the wreckage and interviews of the pilot, passenger, and ground crew revealed the approach and pull up for the second approach were into downwind conditions. The piece of the aircraft that flew off was a section of the tail rotor drive shaft. Except for the missing piece of shaft, no mechanical abnormalities could be found in the pilot controls, engine, or drive train. Source: NTSB Aviation Accident Database (Pre-2008 Archive) Retrieved: 2026-02-12
Verbatim from NTSB's published report. Source file
NTSB_1999_MIA99LA133.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 ↗