Crash of a Convair CV-580 in Kasba Lake

Date & Time: Aug 3, 2011 at 1100 LT
Type of aircraft:
Operator:
Registration:
C-GKFP
Survivors:
Yes
Schedule:
Winnipeg – Kasba Lake
MSN:
446
YOM:
1956
Country:
Crew on board:
0
Crew fatalities:
Pax on board:
0
Pax fatalities:
Other fatalities:
Total fatalities:
0
Circumstances:
Following an uneventful flight from Winnipeg, the crew completed the landing on runway 02/20, a 1,876 metres long clay/gravel runway. During the landing roll, the nose gear collapsed. The aircraft slid on its nose for few dozen metres before coming to rest. All occupants evacuated safely and the aircraft was damaged beyond repair. At the time of the accident, the runway surface was irregular with potholes and water gouges due to the recent rains.

Crash of a Boeing 737-8BK in Georgetown

Date & Time: Jul 30, 2011 at 0132 LT
Type of aircraft:
Operator:
Registration:
9Y-PBM
Survivors:
Yes
Schedule:
New York - Port of Spain - Georgetown
MSN:
29635/2326
YOM:
2007
Flight number:
BW523
Country:
Crew on board:
6
Crew fatalities:
Pax on board:
157
Pax fatalities:
Other fatalities:
Total fatalities:
0
Captain / Total flying hours:
9600
Captain / Total hours on type:
5000.00
Copilot / Total flying hours:
1400
Copilot / Total hours on type:
350
Aircraft flight hours:
14861
Circumstances:
The flight originated in New York as BW 523, and made a passenger and fuel stop in Port-of-Spain, Trinidad where there was also a change of crew comprising two pilots and four flight attendants before proceeding to Georgetown, Guyana. The flight departed Piarco at 04:36UTC. The aircraft proceeded to Georgetown from Port of Spain at Flight Level (FL) 330, was given descent clearance and was cleared for an RNAV (GPS) approach to RWY 06, landing at 05:32 UTC. There were no reported anomalies in the en-route profile, although during the transition from cruise to approach to RWY 06 the aircraft deviated to avoid some thunderstorm cells north and east of the Airport. The reported visibility was 9,000m. Light rain was encountered during the approach. The pilot reported that after visual contact was made and after crossing the Final Approach Fix (FAF), he disengaged the auto pilot and configured the aircraft for landing. The Flight Data Recorder (FDR) indicated that the flight was normal until the aircraft was approaching the runway. Even before the aircraft was over the threshold, the captain commented that he was not landing here. As the flight continued over the runway, comments on the Cockpit Voice Recorder (CVR), revealed that the captain indicated to the First Officer (FO) that the aircraft was not touching down. A go-around call was made by the Captain and acknowledged by the First Officer, however three seconds elapsed and the aircraft subsequently touched down approximately 4700ft from the threshold of RWY06, leaving just over 2700 feet of runway surface remaining. Upon touchdown, brake pressure was gradually increased and maximum brake pressure of 3000psi was not achieved until the aircraft was 250ft from the end of the runway or 450ft from the end of the paved area. The ground spoilers were extended on touchdown. The thrust reversers were partially deployed after touchdown. The aircraft did not stop and overran the runway. It then assumed a downward trajectory followed by a loud impact.
Probable cause:
The probable cause of the accident was that the aircraft touched down approximately 4,700 feet beyond the runway threshold, some 2,700 feet from the end of the runway, as a result of the Captain maintaining excess power during the flare, and upon touching down, failure to utilize the aircraft’s full deceleration capability, resulted in the aircraft overrunning the remaining runway and fracturing the fuselage.
Contributory Factors:
The Flight Crew’s indecision as to the execution of a go-around, failure to execute a go-around after the aircraft floated some distance down the runway and their diminished situational awareness contributed to the accident.
Final Report:

Ground fire of a Boeing 777-266ER in Cairo

Date & Time: Jul 29, 2011 at 0911 LT
Type of aircraft:
Operator:
Registration:
SU-GBP
Flight Phase:
Survivors:
Yes
Schedule:
Cairo - Jeddah
MSN:
28423/71
YOM:
1997
Flight number:
MS667
Country:
Region:
Crew on board:
10
Crew fatalities:
Pax on board:
307
Pax fatalities:
Other fatalities:
Total fatalities:
0
Captain / Total flying hours:
16982
Captain / Total hours on type:
5314.00
Copilot / Total flying hours:
2247
Copilot / Total hours on type:
198
Aircraft flight hours:
48281
Aircraft flight cycles:
11448
Circumstances:
On July 29, 2011, the said Boeing 777-200, Egyptian registration SU-GBP, operated by EgyptAir, arrived from Madina, Saudi Arabia (Flight No 678) and stopped at Gate F7, terminal 3, Cairo international airport almost at 0500 UTC time. Necessary maintenance actions (After Landing Check ALC, Transit Check) have been performed by EgyptAir engineers and technicians, to prepare the aircraft for the following scheduled flight (Cairo/Jeddah, scheduled at 0730 UTC, same day 29 July 2011, flight number 667). The cockpit crew (Captain and F/O) for the event flight (Cairo/Jeddah), started the cockpit preparation including checking the cockpit crew oxygen system as per normal procedures. The F/O reported that the oxygen pressure was within normal range (730 psi). At almost 0711 UTC, and while waiting for the last passengers to board the aircraft, the F/O officer reported that a pop, hissing sound originating from the right side of his seat was heard, associated with fire and smoke coming from the right side console area below F/O window #3 (right hand lower portion of the cockpit area) [The aircraft was still preparing for departure at Gate F7, Terminal 3 at Cairo Airport at the time the crew detected the fire]. The Captain requested the F/O to leave the cockpit immediately and notify for cockpit fire. The captain used the cockpit fire extinguisher bottle located behind his seat in attempt to fight and extinguish the fire. The attempt was unsuccessful, the fire continued in the cockpit. The F/O left the cockpit, he asked the cabin crew to deplane all the passengers and crew from the aircraft, based on captain’s order. He moved to the stairs and then underneath the aircraft in attempt to find anyone with a radio unit but he could not. He returned to the service road in front of the aircraft and stopped one car and asked the person in the car to notify the fire department that the aircraft is burning on the stand F7 using his radio unit. The cabin crew deplaned the passengers using the two doors 1L and 2L. The passenger bridge was still connected to the entry doors that were used for deplaning. The first fire brigade arrived to the aircraft after three minutes. The fire was extinguished. Extinguishing actions and cooling of the aircraft were terminated at 0845 UTC (1045 Cairo local time). The aircraft experienced major damage resulting from the fire and smoke. Passengers deplaned safely, some (passengers, employees) suffered mild asphyxia caused by smoke inhalation. Passengers and crew were as follows: Passengers 307, Cockpit Crew 2, Cabin Crew 8.
Probable cause:
Probable causes for the accident can be reached through:
- Accurate and thorough reviewing of the factual information and the analysis sections
- Excluding the irrelevant probable causes included in the analysis section
Examination of the aircraft revealed that the fire originated near the first officer's oxygen mask supply tubing, which is located underneath the side console below the no. 3 right hand flight deck window. Oxygen from the flight crew oxygen system is suspected to have contributed to the fire's intensity and speed.
The cause of the fire could not be conclusively determined. It is not yet known whether the oxygen system breach occurred first, providing a flammable environment or whether the oxygen system breach occurred as a result of the fire.
Accident could be related to the following probable causes:
1. Electrical fault or short circuit resulted in electrical heating of flexible hoses in the flight crew oxygen system. (Electrical Short Circuits; contact between aircraft wiring and oxygen system components may be possible if multiple wire clamps are missing or fractured or if wires are incorrectly installed).
2. Exposure to Electrical Current
Final Report:

Crash of a Piper PA-46-350P Malibu Mirage in Rantoul: 3 killed

Date & Time: Jul 24, 2011 at 0920 LT
Operator:
Registration:
N46TW
Flight Phase:
Flight Type:
Survivors:
No
Schedule:
Rantoul – Sarasota
MSN:
46-22071
YOM:
1989
Crew on board:
1
Crew fatalities:
Pax on board:
2
Pax fatalities:
Other fatalities:
Total fatalities:
3
Captain / Total flying hours:
1850
Aircraft flight hours:
2560
Circumstances:
On July 24, 2011, about 0920 central daylight time, a Piper PA-46-350P, N46TW, owned and operated by a private pilot, sustained substantial damage when it impacted powerlines and terrain during takeoff from runway 27 at the Rantoul National Aviation Center Airport-Frank Elliott Field (TIP), near Rantoul, Illinois. A post impact ground fire occurred. The personal flight was operating under 14 Code of Federal Regulations Part 91. Visual meteorological conditions prevailed at the time of the accident. An instrument flight rules (IFR) flight plan was on file. The pilot and two passengers sustained fatal injuries. The flight was originating from TIP at the time of the accident and was destined for Sarasota/Bradenton International Airport (SRQ), near Sarasota, Florida. A witness, who worked at the fixed base operator, stated that the pilot performed the preflight inspection of the airplane in a hangar. An estimated 80 pounds. of luggage was loaded behind the airplane's rear seat. The witness said that the pilot's wife told the pilot that she had to use the restroom. The pilot reportedly replied to her to "hurry because a storm front was coming." The witness said that the engine start was normal and that both passengers were sitting in the rear forward-facing seats when the airplane taxied out. A witness at the airport, who was a commercial pilot, reported that he observed the airplane takeoff from runway 27 and then it started to turn to the south. He indicated that the landing gear was up when the airplane was about 500 feet above the ground. The witness stated that a weather front was arriving at the airport and that the strong winds from the northwest appeared to "push the tail of the plane up and the nose down." The airplane descended and impacted powerlines and terrain where the airplane subsequently caught on fire. The witness indicated that the airplane's engine was producing power until impact.
Probable cause:
The pilot did not maintain airplane control during takeoff with approaching thunderstorms. Contributing to the accident was the pilot's decision to depart into adverse weather conditions.
Final Report:

Crash of a Cessna 208 Caravan I in Kei Mouth

Date & Time: Jul 23, 2011
Type of aircraft:
Operator:
Registration:
3009
Flight Type:
Survivors:
Yes
Schedule:
Swartkop AFB - Kei Mouth
MSN:
208-0159
YOM:
1989
Country:
Region:
Crew on board:
2
Crew fatalities:
Pax on board:
0
Pax fatalities:
Other fatalities:
Total fatalities:
0
Circumstances:
On final approach to Kei Mouth Airport in the Eastern Cape Province, the single engine aircraft crashed in unknown circumstances. While both occupants were uninjured, the aircraft was damaged beyond repair. The crew was completing a positioning flight from Swartkop AFB.

Crash of an ATR72-212 in Shannon

Date & Time: Jul 17, 2011 at 1021 LT
Type of aircraft:
Operator:
Registration:
EI-SLM
Survivors:
Yes
Schedule:
Manchester - Shannon
MSN:
413
YOM:
1994
Flight number:
EI3601
Location:
Country:
Region:
Crew on board:
4
Crew fatalities:
Pax on board:
21
Pax fatalities:
Other fatalities:
Total fatalities:
0
Captain / Total flying hours:
2882
Captain / Total hours on type:
2444.00
Copilot / Total flying hours:
1678
Copilot / Total hours on type:
1351
Aircraft flight hours:
32617
Aircraft flight cycles:
37149
Circumstances:
The aircraft and crew commenced operations in EINN that morning, departing at 05.52 hrs and arriving at EGCC at 07.13 hrs. During the turnaround, fuel was uplifted and 21 passengers boarded. Using the flight number and call sign EI-3601 the scheduled passenger service departed EGCC at 07.47 hrs for EINN with an estimated flight time of one hour and nine minutes. En-route operations were normal and, in consultation with ATC, the aircraft descended and was cleared to self-position to DERAG2 for an Instrument Landing System (ILS) approach to RWY 24. At 09.08 hrs the aircraft commenced an approach to RWY 24 in strong and gusty crosswind conditions. Following a turbulent approach difficulty was experienced in landing the aircraft, which contacted the runway in a nose-down attitude and bounced. A go-around was performed and the aircraft was vectored for a second approach. During this second approach landing turbulence was again experienced. Following bounces the aircraft pitched nose down and contacted the runway heavily in a nose down attitude. The nose gear collapsed and the aircraft nose descended onto the runway. The aircraft sustained damage with directional control being lost. The aircraft came to rest at the junction of the runway and a taxiway. Following engine shutdown the forward Cabin Crew Member (CCM) advised the cockpit that there was no smoke and that the doors could be opened following which, an evacuation was commenced. Airport fire crews arrived on scene promptly and assisted passengers disembarking the aircraft. There were no injuries.
Probable cause:
Probable Cause:
1. Excessive approach speed and inadequate control of aircraft pitch during a crosswind landing in very blustery conditions.
Contributory Factors:
1. Confusing wording in the FCOM that led the crew to compute an excessive wind factor in the determination of Vapp.
2. Incorrect power handling technique while landing.
3. Inexperience of the pilot in command.
4. Inadequate information provided to flight crew regarding crosswind landing techniques.
Final Report:

Ground collision of an ATR72-202 in Warsaw

Date & Time: Jul 14, 2011 at 2230 LT
Type of aircraft:
Operator:
Registration:
SP-LFH
Flight Phase:
Survivors:
Yes
Schedule:
Wrocław – Warsaw
MSN:
478
YOM:
1995
Flight number:
ELO3850
Country:
Region:
Crew on board:
4
Crew fatalities:
Pax on board:
33
Pax fatalities:
Other fatalities:
Total fatalities:
0
Circumstances:
On 14 July, 2011 ATR 72 flight crew after landing at EPWA aerodrome received the clearance for taxiing to parking stand 41 via taxiways: "S", "O" and "M". When the airplane was on taxiway "M2", "Mulag" type tractor was moving by the service road, passing perpendicularly to taxiway “M2”. The tractor driver did not give the right of way to ATR 72 and the tractor collided with the airplane. As a result, the airplane and the tractor sustained substantial damages. The flight crew stopped the airplane and shut down the engines. Airport Fire Brigade and an ambulance were called. The tractor operator suffered some injuries and was taken to hospital. the airplane passengers and the flight crew did not suffer any injuries. The impact caused a fuel leakage from the airplane of 200 m2 in area, which was removed along with other elements of the damaged aircraft by the Airport Fire Brigade. The airplane and the "Mulag" tractor were withdrawn from the further service. During the accident there were adverse weather conditions at the airport - heavy rain and lightning which caused reduction in visibility.
Probable cause:
Inadequate observation of the Ground Movement Area by the “Mulag” tractor operator.
Contributing factors:
1. Heavy rain and lightning.
2. Light reflections on the aerodrome surface which hindered observation from the tractor cab.
3. Construction of the "Mulag” tractor cab, left side of which could partially or completely obscure silhouette of the airplane.
4. Short distance between a service road and taxiway "O2".
Final Report:

Crash of a Cessna 560XL Citation XLS in Port Harcourt

Date & Time: Jul 14, 2011 at 1953 LT
Operator:
Registration:
5N-BMM
Survivors:
Yes
Schedule:
Lagos – Port Harcourt
MSN:
560-5830
YOM:
2008
Country:
Region:
Crew on board:
2
Crew fatalities:
Pax on board:
4
Pax fatalities:
Other fatalities:
Total fatalities:
0
Captain / Total flying hours:
11751
Captain / Total hours on type:
684.00
Copilot / Total flying hours:
13302
Copilot / Total hours on type:
612
Aircraft flight hours:
982
Circumstances:
5N-BMM departed Lagos at 1856 hrs for Port Harcourt on an Instrument Flight Rules (IFR) and estimated Port Harcourt at 1940 hrs. The aircraft was cleared to maintain FL330. The aircraft’s first contact with Port Harcourt was at 1914 hrs. The pilot reported maintaining FL330 with six souls onboard, four hours fuel endurance and estimating POT VOR at 1940hrs. The aircraft was cleared to POT, to maintain FL330 with no delay expected for ILS Approach Runway 21, QNH 1011 and to report when released by Lagos. At 1921 hrs the pilot reported 100 NM to POT and requested for descent. The aircraft was cleared to descend to FL150. At 1927 hrs the pilot requested for further descent and was cleared to 3,300 feet on QNH 1011 but the pilot acknowledged 3500 feet. At 1931 hrs the aircraft was re-cleared to FL090 initially due to departing traffic on Runway 03. At 1934 hrs 5N-BMM reported maintaining FL090 and was re-cleared to FL050. The aircraft was re-cleared to 2,000 feet on QNH 1011 at 1936 hrs and cleared for the straight-in ILS Approach Runway 21 and to report on the localizer. At 1947 hrs the pilot reported final for Runway 21 and was asked to contact Tower on 119.2 and the Tower asked 5N-BMM to report on glide slope Runway 21. At 1950 hrs the Tower asked 5N-BMM to confirm on the glide slope and the crew confirmed “Charlie, we have three miles to run”. The Tower cleared 5N-BMM to land with surface wind calm but to exercise caution since the Runway surface was wet and 5N-BMM responded “wind calm”. At 1952:26 hrs the auto voice callout "minimums minimums” alerted the crew. At 1952:40 hrs the pilot flying (PF) said "I am not on the centerline". At 1952:48 hrs he said "I can't see down". At 1952:55 hrs the pilot monitoring (PM) said to the pilot flying; " I am telling you to go down" and the pilot flying said " I will go down", five seconds later the aircraft crashed. The crew exited the aircraft without accomplishing the Emergency Evacuation Checklist and therefore left the right engine running for about 28 minutes after the crash. The Fire Service eventually used their water hose to shutdown the running engine. At 19:54 hrs the Tower called 5N-BMM to pass on the landing time as 19:53 hrs, but no response from 5N-BMM. There was no indication that the aircraft was taxing on the Runway because it was dark and no light was visible hence the need to alert the Fire personnel. The watch room was asked to give the Tower information, which they could not give since they do not have a two – way contact with the Fire trucks. The Tower could not raise the Fire truck since there was no two - way communication between them; however, the Fire truck was later cleared to proceed to the Runway as the Tower could not ascertain the position of the aircraft. The aircraft was actually turned 90° because of the big culvert that held the right wing and made the aircraft spin and turned 90o facing the runway, two meters from the active runway, the culvert was uprooted due to the aircraft impact forces. The wheel broke off because of the gully that runs parallel to the runway.
Probable cause:
The decision of the pilot to continue the approach without the required visual references.
Contributory Factors:
- Poor crew coordination (CRM),
- Pairing two captains together,
- The weather was marginal.
Final Report:

Crash of a Let L-410UVP-E20 in Recife: 16 killed

Date & Time: Jul 13, 2011 at 0654 LT
Type of aircraft:
Operator:
Registration:
PR-NOB
Flight Phase:
Survivors:
No
Schedule:
Recife - Natal - Mossoró
MSN:
92 27 22
YOM:
1992
Flight number:
NRA4896
Country:
Crew on board:
2
Crew fatalities:
Pax on board:
14
Pax fatalities:
Other fatalities:
Total fatalities:
16
Captain / Total flying hours:
15457
Captain / Total hours on type:
957.00
Copilot / Total flying hours:
2404
Copilot / Total hours on type:
404
Aircraft flight hours:
2126
Aircraft flight cycles:
3033
Circumstances:
At 0650 local time, the aircraft departed from Recife-Guararapes Airport runway 18, destined for Natal, carrying 14passengers and two crewmembers on a regular public transportation flight. During the takeoff, after the aircraft passed over the departure end of the runway, the copilot informed that they would return for landing, preferably on runway 36, and requested a clear runway. The aircraft made a deviation to the left, out of the trajectory, passed over the coastline, and, then, at an altitude of approximately 400ft, started a turn to the right over the sea. After about 90º of turn, upon getting close to the coast line, the aircraft reverted the turn to the left, going farther away from the coast line. After a turn of approximately 270º, it leveled the wings and headed for the airport area. The copilot informed, while the aircraft was still over the sea, that they would make an emergency landing on the beach. Witnesses reported that, as the aircraft was crossing over the coast line, the left propeller seemed to be feathered and turning loosely. At 0654 local time, the aircraft crashed into the ground in an area without buildings, between Boa Viagem Avenue and Visconde de Jequitinhonha Avenue, at a distance of 1,740 meters from the runway 36 threshold. A raging post-impact fire occurred and all 16 occupants were killed.
Probable cause:
Human Factors
Medical Aspect
- Anxiety
The perception of danger especially by the first officer affected the communication between the pilots and may have inhibited a more assertive attitude, which could have led to an emergency landing on the beach, minimizing the consequences of the accident.
Psychological Aspect
- Attitude
Operational decisions during the emergency may have resulted from the high confidence level, that the captain had acquired in years of flying and experience in aviation, as well as the captain's resistance to accept opinions different to his own.
- Emotional state
According to CVR recordings there was a high level of anxiety and tension even before the abnormal situation. These components may have influenced the judgment of conditions affecting the operation of the aircraft.
- Decision making
The persistence to land on runway 36 during the emergency, even though the first officer recognized the conditions no longer permitted to reach the airport, reflects misjudgment of operational information present at the time.
- Signs of stress
The unexpected emergency at takeoff and the lack of preparation for dealing with it may have invoked a level of stress with the crew, that negatively affected the operational response.
Psychosocial Information
- Interpersonal relations
The historical differences between the two pilots possibly hindered the exchange of information and created a barrier to deal with the adverse situation.
- Dynamic team
The present diverging intentions of how to proceed clearly show cooperation and management issues in the cockpit. This prevented the choice of best alternative to achieve a safe emergency landing when there were no options left to reach the airport.
- Company Culture
The company was informally divided into two groups, whose interaction was impaired. It is possible that this problem of interaction continued into the cockpit management during the in flight emergency, with one pilot belonging to one and the other to the other group.
Organizational Information
- Education and Training
Deficiencies of training provided by the operator affected the performance of the crew, who had not been sufficiently prepared for the safe conduct of flight in case of emergency.
- Organizational culture
The actions taken by the company indicate informality, which resulted in incomplete operational training and attitudes that endangered the safety.
Operational Aspects
According to data from the flight recorder the rudder pedal inputs were inadequate to provide sufficient rudder deflection in order to compensate for asymmetric engine power.
The values of side slip reached as result of inadequate rudder pedal inputs penalized the performance of the aircraft preventing further climb or even maintaining altitude.
In the final phase of the flight, despite the airspeed decaying below Vmca, despite continuous stall warnings and despite calls by the first officer to not hold the nose up in order to not stall the captain continued pitch up control inputs until the aircraft reached 18 degrees nose up attitude and entered stall.
- Crew Coordination
The delay in retracting the landing gear after the first instruction by the captain, the instruction of the captain to feather the propeller when the propeller had already been feathered as well as the first officer's request the captain should initiate the turn back when the aircraft was already turning are indicative that the crew tasks and actions were not coordinated.
Emergency procedures provided in checklists were not executed and there was no consensus in the final moments of the flight, whether the best choice (least critical option) was to return to the runway or land on the beach.
- Oblivion
It is possible in response to the emergency and influenced by anxiety, that the crew may have forgotten to continue into the 3rd segment of the procedure provided for engine failure on takeoff at or above V1 while trying to return to the airfield shortly after completion of the 2nd segment while at 400ft.
- Pilot training
The lack of training of engine failures on takeoff at or above V1, similar as is recommended in the training program, led to an inadequate pilot response to the emergency. The pilots did not follow the recommended flight profile and did execute the checklist items to be carried out above 400 feet.
- Pilot decisions
The pilots assessed that the priority was to return to land in opposite direction of departure and began the turn back at 400 feet, which added to the difficulty of flying the aircraft. At 400 feet the aircraft maintained straight flight and a positive rate of climb requiring minor flight control inputs only, which would have favored the completion of the emergency check list items in accordance with recommendations by the training program.
After starting the turn the crew would needed to adjust all flight controls to maintain intended flight trajectory in addition to working the checklists, the turn thus increased workload. It is noteworthy that the remaining engine developed sufficient power to sustain flight.
- Supervision by Management
The supervision by management did not identify that the training program provided to pilots failed to address engine failure above V1 while still on the ground and airborne.
It was not identified that the software adopted by the company to dispatch aircraft used the maximum structural weight (6,600 kg) as maximum takeoff weight for departures from Recife.
On the day of the accident the aircraft was limited in takeoff weight due to ambient temperature. Due to the software error the aircraft took off with more than the maximum allowable takeoff weight degrading climb performance.
Mechanical Aspects
- Aircraft
Following the hypothesis that the fatigue process had already started when the turbine blade was still attached to the Russia made engine, the method used by the engine manufacturer for assessment to continue use of turbine blades was not able to ensure sufficient quality of the blade, that had been mounted into position 27 of the left hand engine's Gas Generator Turbine's disk.
- Aircraft Documentation
The documentation of the aircraft by the aircraft manufacturer translated into the English language did not support proper operation by having confusing texts with different content for the same items in separate documents as well as translation errors. This makes the documentation difficult to understand, which may have contributed to the failure to properly implement the engine failure checklists on takeoff after V1.
An especially concerning item is the "shutdown ABC (Auto Bank Control)", to be held at 200 feet height, the difference between handling instructed by the checklist and provided by the flight crew manual may have contributed to the non-performance by the pilots, aggravating performance of the aircraft.
Final Report:

Crash of a Cessna 421C Golden Eagle III in Demopolis: 7 killed

Date & Time: Jul 9, 2011 at 1740 LT
Registration:
N692TT
Flight Type:
Survivors:
No
Schedule:
Creve Cœur – Destin
MSN:
421C-0616
YOM:
1979
Crew on board:
1
Crew fatalities:
Pax on board:
6
Pax fatalities:
Other fatalities:
Total fatalities:
7
Captain / Total flying hours:
1000
Captain / Total hours on type:
340.00
Aircraft flight hours:
7800
Circumstances:
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.
Probable cause:
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.
Final Report: