NTSB Issues Probable Cause Report In Demopolis, AL Accident | Aero-News Network
Aero-News Network
RSS icon RSS feed
podcast icon MP3 podcast
Subscribe Aero-News e-mail Newsletter Subscribe

Airborne Unlimited -- Recent Daily Episodes

Episode Date

AMA Drone Report

Airborne-Monday

Airborne-Tuesday

Airborne-Wednesday

Airborne-Thursday

Airborne-Friday

Airborne On ANN

ADR 02.27.17

Airborne 02.27.17

Airborne 02.28.17

Airborne 02.22.17

Airborne 02.23.17

Airborne 02.24.17

Airborne-HD On YouTube

ADR 02.27.17

Airborne 02.27.17

Airborne 02.28.17

Airborne 02.22.17

Airborne 02.23.17

Airborne 02.24.17

Sat, Jan 19, 2013

NTSB Issues Probable Cause Report In Demopolis, AL Accident

Seven Members Of A Florida Family Fatally Injured When The Cessna 421 Went Down

The NTSB has released its probable cause report in an accident which resulted in seven members of a Florida family returning from a family reunion in St. Louis, MO. While the board said that the loss of an engine on the Cessna 421 contributed to the accident, it was the pilot's inability to control the airplane on a single engine that was the probable cause.

NTSB Identification: ERA11FA391
14 CFR Part 91: General Aviation
Accident occurred Saturday, July 09, 2011 in Demopolis, AL
Probable Cause Approval Date: 01/15/2013
Aircraft: CESSNA 421C, registration: N692TT
Injuries: 7 Fatal.

NTSB investigators either traveled in support of this investigation or conducted a significant amount of investigative work without any travel, and used data obtained from various sources to prepare this aircraft accident report.

The multi-engine airplane was in cruise flight at flight level 210 when the pilot declared an emergency due to a rough-running right engine and diverted to a non-towered airport about 10 miles from the airplane’s position. About 4 minutes later, the pilot reported that he had shut down the right engine. The pilot orbited around the diversion airport during the descent and reported to an air traffic controller that he did not believe he would require any assistance after landing. The airplane initially approached the airport while descending through about 17,000 feet mean sea level (msl) and circled above the airport before entering a left traffic pattern approach for runway 22. About 7,000 feet msl, the airplane was about 2.5 miles northeast of the airport. The airplane descended through 2,300 feet msl when it was abeam the runway threshold on the downwind leg of the traffic pattern. According to the airplane information manual, procedures for landing with an inoperative engine call for “excessive altitude;” however, the airplane's last radar return showed the airplane at an altitude of 700 feet msl (about 600 feet above ground level) and about 3 miles from the approach end of the runway.

The airplane was configured for a single-engine landing and was likely on or turning to the final approach course when it rolled and impacted trees. The airplane came to rest in a wooded area about 0.8 miles north of the runway threshold, inverted, in a flat attitude with no longitudinal deformation. A majority of the airplane, including the cockpit, main cabin, and left wing, were consumed by a postcrash fire. Search operations located the airplane about 6 hours after its expected arrival time. Due to the severity of the postcrash fire, occupant survivability after the impact could not be determined. Examination of the airframe, the left engine, and both propellers did not reveal any preaccident mechanical malfunctions or failures that would have precluded normal operation. The investigation revealed that the right engine failed when the camshaft stopped rotating after the camshaft gear experienced a fatigue fracture on one of its gear teeth. The remaining gear teeth were fractured in overstress and/or were crushed due to interference contact with the crankshaft gear. Spalling observed on an intact gear tooth suggested abnormal loading of the camshaft gear; however, the origin of the abnormal loading could not be determined.

The National Transportation Safety Board determines the probable cause(s) of this accident to be:

The pilot's failure to maintain airplane control during a single-engine approach and his failure to fly an appropriate traffic pattern for a single-engine landing. Contributing to the accident was a total loss of engine power on the right engine due to a fatigue failure of the right engine cam gear.

FMI: www.ntsb.gov

 


Advertisement

More News

Counting Down! ANN's Infamous April 1st Edition's Just Around The Corner!

Get Your Wacky Ideas In NOW! ANN E-I-C Note: Folks... we gotta warn you... our Annual April 1st Editions are LEGENDARY -- and this WILL be our best April 1st Edition yet. Based on >[...]

Airborne 02.24.17: RV-10 Suit Dismissed, 2016 GA Sales, Red Tail Legacy

Also: Falcon 9 Landing, TFR Busts, Denton Airshow, QF-16, Treasure Coast, 'Fly Safe' Campaign, Juno Mission When the news first came out, in 2015, that Van's Aircraft was sued for >[...]

Sun 'N Fun To Host Massive Gathering Of P-51 Mustangs

Expected To Be The Largest Assembly Of P-51s In A Decade Or More It is being billed as possibly the largest gathering of P-51 Mustangs in a decade or more ... on Wednesday, April 5>[...]

DJI Hints At A New Drone, Reveals Details Early

Industry WAS Speculating What The Drone Giant May Be Bringing To Market Next Generating buzz is good marketing, and DJI was doing so with a Tweet announcing new products for the Mo>[...]

Klyde Morris (02.27.17)

Klyde Is Amazed By All The Ways NASA Info Gets Interpreted FMI: www.klydemorris.com>[...]

blog comments powered by Disqus



Advertisement

Advertisement

Podcasts

Advertisement

© 2007 - 2017 Web Development & Design by Pauli Systems, LC