ASN logo
ASN Wikibase Occurrence # 44174
Last updated: 10 August 2019
This information is added by users of ASN. Neither ASN nor the Flight Safety Foundation are responsible for the completeness or correctness of this information. If you feel this information is incomplete or incorrect, you can submit corrected information.

Type:Silhouette image of generic PA34 model; specific model in this crash may look slightly different
Piper PA-34-200T
Registration: N21RR
C/n / msn: 34-7770405
Fatalities:Fatalities: 4 / Occupants: 4
Aircraft damage: Written off (damaged beyond repair)
Location:Branson, MO -   United States of America
Phase: Manoeuvring (airshow, firefighting, ag.ops.)
Departure airport:Branson, MO (PLK)
Destination airport:Lubbock, TX (LBB)
Investigating agency: NTSB
The airplane impacted a transmission wire, single-story storage building, and terrain, while attempting to return to the departure airport after takeoff. Instrument meteorological conditions prevailed at the time of the accident. The airport manager reported that the accident airplane's takeoff appeared to be normal. After departure, the accident pilot was unable to establish radio communication with air traffic control (ATC). The controller described the airplane's transmissions as "weak and unreadable." Communications were subsequently relayed through a second aircraft on the ground at the departure airport waiting for a takeoff clearance. The accident pilot declared an emergency approximately 3 minutes after takeoff; however, he did not stated the nature of the emergency. Witnesses in the vicinity of the airport reported seeing the airplane in-flight prior to the accident. Two witnesses stated that they saw the airplane exit the clouds at a high rate of descent before it leveled off. One of them noted that the airplane's flight path was steady. Both of the witnesses lost sight of the airplane behind a ridgeline. Another witness reported the airplane flew past her residence, located on a ridge south of the airport at an "exceptionally low" altitude. She added that the engines were at a "very, very high throttle" setting. Regarding weather conditions at the time, the witness reported that it "was just like a big cloud over Branson," and that she could not see the city at the time. An off-duty airport firefighter, reported that he saw the airplane shortly before the accident. He stated that it appeared to be in normal flight, with the exception that it was low. He added that he didn't hear anything unusual and the propellers were turning. He reported that it was approximately 50 feet above ground level (agl) when it appeared to "stop in mid air," the airplane's tail "spun around" and then it "dropped straight down." He responded to the accident site but was unable to assist the occupants. A post accident fire subsequently consumed most of the aircraft and the storage building. The post accident airframe and engine examinations did not reveal any anomalies associated with a pre impact failure. Both engine propeller assemblies had separated from their respective engine crankshafts, and were located at the accident site. The fracture surfaces exhibited 45-degree shear planes consistent with torsional overload failures. The post accident fire consumed the left vacuum pump. The right vacuum pump exhibited thermal damage, however, upon disassembly, the rotor and vanes were intact. Ceilings at the accident airport were estimated at 400 - 800 feet agl, with the surface visibilities at 1 - 3 miles. Routine weather observations were not available for the accident airport.
Probable Cause: The pilot's failure to maintain sufficient airspeed, which resulted in an inadvertent stall/spin while maneuvering to return to the departure airport for landing after declaring an emergency for unspecified reasons. Additional factors were the low cloud ceiling (instrument conditions), the low altitude at the time of the inadvertent stall, the residential power transmission wire and the storage building.



Revision history:

28-Oct-2008 00:45 ASN archive Added
21-Dec-2016 19:24 ASN Update Bot Updated [Time, Damage, Category, Investigating agency]
05-Dec-2017 09:04 ASN Update Bot Updated [Operator, Other fatalities, Source, Narrative]

Corrections or additions? ... Edit this accident description