Crash of an Antonov AN-24B in Dire Dawa: 1 killed

Date & Time: Jul 23, 2007 at 1300 LT
Type of aircraft:
Operator:
Registration:
EX-030
Flight Phase:
Flight Type:
Survivors:
Yes
Schedule:
Dire Dawa - Djibouti City
MSN:
0 73 061 03
YOM:
1970
Country:
Region:
Crew on board:
3
Crew fatalities:
Pax on board:
6
Pax fatalities:
Other fatalities:
Total fatalities:
1
Circumstances:
Shortly after takeoff from Dire Dawa-Aba Tenna Dejazmach Yilma Airport, while climbing to an altitude of 3,500 feet, one of the engine failed. The captain decided to return for an emergency landing but the aircraft crashed in a desert area located near Shinile, about 5 km north of Dire Dawa Airport. Upon impact, the aircraft broke in three. A passenger was killed while 8 other occupants were injured. The aircraft was completing a cargo flight to Djibouti City on behalf of Djibouti Airlines, carrying a load of 6 tons of qat.
Probable cause:
Engine failure for unknown reasons.

Crash of a Cessna 208B Grand Caravan in Arekuna Camp

Date & Time: Jul 21, 2007 at 1655 LT
Type of aircraft:
Operator:
Registration:
YV1182
Flight Phase:
Flight Type:
Survivors:
Yes
MSN:
208B-0729
YOM:
1998
Country:
Crew on board:
2
Crew fatalities:
Pax on board:
0
Pax fatalities:
Other fatalities:
Total fatalities:
0
Circumstances:
Shortly after takeoff from Arekuna Camp Airstrip, while climbing to a height of about 200 feet, the engine lost power. The crew attempted an emergency landing when the aircraft collided with trees and came to rest upside down. Both pilots were injured and the aircraft was destroyed.
Probable cause:
Engine failure for unknown reasons.

Crash of a Learjet 25 in Saint Augustine

Date & Time: Jul 21, 2007 at 1410 LT
Type of aircraft:
Operator:
Registration:
N70SK
Flight Type:
Survivors:
Yes
Schedule:
Gainesville - Saint Augustine
MSN:
25-49
YOM:
1970
Crew on board:
2
Crew fatalities:
Pax on board:
0
Pax fatalities:
Other fatalities:
Total fatalities:
0
Captain / Total flying hours:
4620
Captain / Total hours on type:
250.00
Copilot / Total flying hours:
2453
Copilot / Total hours on type:
368
Aircraft flight hours:
15812
Circumstances:
About 5 miles from the destination airport, the flight was cleared by air traffic control to descend from its cruise altitude of 5,000 feet for a visual approach. As the first officer reduced engine power, both engines "quit." The captain attempted to restart both engines without success. He then took control of the airplane, and instructed the first officer to contact air traffic control and advise them that the airplane had experienced a "dual flameout." The captain configured the airplane by extending the landing gear and flaps and subsequently landed the airplane on the runway "hard," resulting in substantial damage to the airframe. Both engines were test run following the accident at full and idle power with no anomalies noted. Examination of the airplane revealed that it was equipped with an aftermarket throttle
quadrant, and that the power lever locking mechanism pins as well as the throttle quadrant idle stops for both engines were worn. The power lever locking mechanism internal springs for both the left and right power levers were worn and broken. Additionally, it was possible to repeatedly move the left engine's power lever directly into cutoff without first releasing its power lever locking mechanism; however, the right engine's power lever could not be moved to the cut off position without first releasing its associated locking mechanism. The right throttle thrust reverser solenoid installed on the airplane was found to be non-functional, but it is not believed that this component contributed to the accident. No explicit inspection or repair instructions were available for the throttle quadrant assembly. Other than the throttle quadrant issues, no other issues were identified with either the engines or airframe that could be contributed to both engines losing power simultaneously.
Probable cause:
A loss of power on both engines for an undetermined reason.
Final Report:

Crash of a Let L-410UVP in Bandundu

Date & Time: Jul 18, 2007
Type of aircraft:
Registration:
9Q-CIM
Flight Phase:
Survivors:
Yes
MSN:
83 09 35
YOM:
1983
Region:
Crew on board:
0
Crew fatalities:
Pax on board:
0
Pax fatalities:
Other fatalities:
Total fatalities:
0
Circumstances:
Shortly after takeoff from Bandundu Airport, while in initial climb, the twin engine aircraft collided with a flock of birds, stalled and crashed. There were no casualties but the aircraft was destroyed.
Probable cause:
Loss of control and subsequent crash on takeoff following a bird strike.

Crash of an Embraer ERJ-190-100 IGW in Santa Marta

Date & Time: Jul 17, 2007 at 1519 LT
Type of aircraft:
Operator:
Registration:
HK-4455
Survivors:
Yes
Schedule:
Cali - Santa Marta
MSN:
190-00076
YOM:
2007
Flight number:
RPB7330
Country:
Crew on board:
6
Crew fatalities:
Pax on board:
54
Pax fatalities:
Other fatalities:
Total fatalities:
0
Captain / Total flying hours:
13737
Captain / Total hours on type:
238.00
Copilot / Total flying hours:
2148
Copilot / Total hours on type:
233
Aircraft flight hours:
998
Circumstances:
Following an uneventful flight from Cali, the crew started the approach to Santa Marta-Simón Bolívar Airport runway 01. On final approach, the crew encountered poor weather conditions with heavy rain falls, turbulences and windshear. As the aircraft was unstable, the captain decided to abandon the approach and initiated a go-around procedure. Few minutes later, the crew started a second approach. Still unstable, the aircraft landed too far down the wet runway 01 at an excessive speed, about 490 metres from the runway end. Unable to stop within the remaining distance, the aircraft overran, went through a fence, collided with pylons, went down a concrete embankment and came to rest with the cockpit in the sea. All 60 occupants evacuated safely while the aircraft was damaged beyond repair.
Probable cause:
 Continuation of the approach and landing without being stabilized on finals with an excessive speed caused the aircraft to cross the threshold of the runway with an additional 41 knots during a low angle approach, which caused the aircraft wheels to touch down positively when there were only 490 meters of runway available, an insufficient distance to stop the aircraft within the runway.
The following contributing factors were identified:
- Lack of situational awareness regarding the approach and landing speed, after having disconnected the automated systems of the aircraft.
- Omission of call outs by the Pilot Monitoring to warn the pilot in control of speeding in order to persuade him to execute a missed approach.
- The delay in initiating a missed approach procedure / interrupted landing in circumstances that indicated the desirability to take such a measure during a destabilized approach.
- Misperception to believe that the aircraft could be stopped within the limited remaining available runway without analyzing the status and distance without having positive contact due to speeding.
Final Report:

Crash of an ATR42-300 in São Paulo

Date & Time: Jul 16, 2007 at 1242 LT
Type of aircraft:
Operator:
Registration:
PT-MFK
Survivors:
Yes
Schedule:
Araçatuba – Bauru – São Paulo
MSN:
225
YOM:
1991
Flight number:
PTN4763
Country:
Crew on board:
4
Crew fatalities:
Pax on board:
21
Pax fatalities:
Other fatalities:
Total fatalities:
0
Captain / Total flying hours:
7420
Captain / Total hours on type:
4993.00
Copilot / Total flying hours:
947
Copilot / Total hours on type:
797
Circumstances:
The aircraft departed Araçatuba on a flight to São Paulo with an intermediate stop in Bauru, carrying 21 passengers and a crew of four. After touchdown on wet runway 17R at Congonhas Airport, the crew started the braking procedure when the aircraft deviated to the left and veered off runway. While contacting soft ground, the aircraft collided with a concrete block housing the electrical device supplying the runway light system. On impact, the nose gear was torn off and the aircraft came to rest. All 25 occupants evacuated safely while the aircraft was damaged beyond repair.
Probable cause:
Loss of control upon landing after the aircraft suffered aquaplaning. The following contributing factors were identified:
- A light rain caused the presence of water on the runway, enabling the occurrence of hydroplaning.
- The accumulation of water on the surface of the runway, as a result of inadequate drainage, lack of "grooving", enabled the hydroplaning.
- The pilot applied full pressure on the right pedal, generating a force to the left that contributed to the departure off the runway.
- During hydroplaning, the pilot should not apply pedal to the opposite side to which the aircraft slides; this fact was not covered during the instruction of the pilot.
- In the face of hydroplaning, the pilot applied the right pedal, aggravating the departure of the aircraft to the left.
Final Report:

Crash of a Piper PA-31-350 Navajo Chieftain in Orlando

Date & Time: Jul 11, 2007 at 1215 LT
Operator:
Registration:
N105GC
Flight Type:
Survivors:
Yes
Schedule:
Melbourne - Orlando
MSN:
31-7652130
YOM:
1976
Crew on board:
1
Crew fatalities:
Pax on board:
0
Pax fatalities:
Other fatalities:
Total fatalities:
0
Captain / Total flying hours:
13000
Captain / Total hours on type:
200.00
Circumstances:
The airplane had undergone routine maintenance, and was returned to service on the day prior to the incident flight. The mechanics who performed the maintenance did not secure the right engine cowling using the procedure outlined in the airplane's maintenance manual. The mechanic who had been working on the outboard side of the right engine could not remember if he had fastened the three primary outboard cowl fasteners before returning the airplane to service. During the first flight following the maintenance, the right engine's top cowling departed the airplane. The pilot secured the right engine, but the airplane was unable to maintain altitude, so he then identified a forced landing site. The airplane did not have a sufficient glidepath to clear a tree line and buildings, so he landed the airplane in a clear area about 1,500 yards short of the intended landing area. The airplane came to rest in a field of scrub brush, and about 5 minutes after the pilot deplaned, the grass under the left engine ignited. The subsequent brush fire consumed the airplane. Examination of the right engine cowling revealed that the outboard latching fasteners were set to the "open" position. When asked about the security of the cowling during the preflight inspection, the pilot stated that he "just missed it."
Probable cause:
The mechanic's failure to secure the right engine cowling fasteners. Contributing to the incident was the pilot's inadequate preflight inspection.
Final Report:

Crash of a De Havilland DHC-6 Twin Otter 100 in Muncho Lake: 1 killed

Date & Time: Jul 8, 2007 at 1235 LT
Operator:
Registration:
C-FAWC
Flight Phase:
Survivors:
Yes
Schedule:
Muncho Lake – Prince George
MSN:
108
YOM:
1968
Country:
Crew on board:
2
Crew fatalities:
Pax on board:
3
Pax fatalities:
Other fatalities:
Total fatalities:
1
Captain / Total flying hours:
22000
Captain / Total hours on type:
6000.00
Copilot / Total flying hours:
10800
Copilot / Total hours on type:
105
Circumstances:
At approximately 1235 Pacific daylight time, the Liard Air Limited de Havilland DHC-6-100 Twin Otter (registration C-FAWC, serial number 108) was taking off from a gravel airstrip near the Northern Rockies Lodge at Muncho Lake on a visual flight rules flight to Prince George, British Columbia. After becoming airborne, the aircraft entered a right turn and the right outboard flap hanger contacted the Alaska Highway. The aircraft subsequently struck a telephone pole and a telephone cable, impacted the edge of the highway a second time, and crashed onto a rocky embankment adjacent to a dry creek channel. The aircraft came to rest upright approximately 600 feet from the departure end of the airstrip. An intense post-impact fire ensued and the aircraft was destroyed. One passenger suffered fatal burn injuries, one pilot was seriously burned, the other pilot sustained serious impact injuries, and the other two passengers received minor injuries.
Probable cause:
Findings as to Causes and Contributing Factors:
1. The take-off was attempted at an aircraft weight that did not meet the performance capabilities of the aircraft to clear an obstacle and, as a result, the aircraft struck a telephone pole and a telephone cable during the initial climb.
2. A take-off and climb to 50 feet performance calculation was not completed prior to take-off; therefore, the flight crew was unaware of the distance required to clear the telephone cable.
3. The southeast end of the airstrip was not clearly marked; as a result, the take-off was initiated with approximately 86 feet of usable airstrip behind the aircraft.
4. The take-off was attempted in an upslope direction and in light tailwind, both of which increased the distance necessary to clear the existing obstacles.
Findings as to Risk:
1. Operational control within the company was insufficient to reduce the risks associated with take-offs from the lodge airstrip.
2. The take-off weight limits for lodge airstrip operations were not effectively communicated to the flight crew.
3. Maximum performance short take-off and landing (MPS) techniques may have been necessary in order to accomplish higher weight Twin Otter take-offs from the lodge airstrip; however, neither the aircraft nor the company were approved for MPS operations.
4. The first officer’s shoulder harness assembly had been weakened by age and ultraviolet (UV) light exposure; as a result, it failed within the design limits at impact.
5. The SeeGeeTM calculator operating index (OI) values being used by Liard Air Twin Otter pilots was between 0.5 and 1.0 units greater than the correct SeeGeeTM OI values; therefore, whenever the SeeGeeTM calculator was used for flight planning, the actual centre of gravity (c of g) of the aircraft would have been forward of the calculated CofG.
6. There are no airworthiness standards specifically intended to contain fuel and/or to prevent fuel ignition in crash conditions in fixed-gear United States Civil Aviation Regulation 3 and United States Federal Aviation Regulation 23 aircraft.
Final Report:

Crash of a Cessna 208B Grand Caravan in Aerfort na Minna (Aran Island): 2 killed

Date & Time: Jul 5, 2007 at 1449 LT
Type of aircraft:
Registration:
N208EC
Flight Type:
Survivors:
Yes
Schedule:
Inis Meáin - Aerfort na Minna
MSN:
208B-1153
YOM:
2005
Country:
Region:
Crew on board:
1
Crew fatalities:
Pax on board:
8
Pax fatalities:
Other fatalities:
Total fatalities:
2
Captain / Total flying hours:
9001
Captain / Total hours on type:
476.00
Aircraft flight hours:
320
Aircraft flight cycles:
275
Circumstances:
The purpose of the flight was a demonstration of an aircraft to a group of potential investors and interested parties associated with a proposed airport at Clifden, Co. Galway, some 25 nm to the northwest of EICA. The flight was organised by one of this group who requested the aircraft, a Cessna Caravan registration N208EC, through an Aircraft Services Intermediary (ASI) from the aircraft’s beneficial owner. The owner agreed to loan his aircraft and the pilot, to fly the group from EICA to EIMN, (a distance of 9 nm) and back. The aircraft departed from Weston (EIWT) aerodrome, near Dublin, at 08.20 hrs on the day of the accident. It over flew Galway (EICM) to EICA where it landed and shutdown. There were two persons on board, the Pilot and an Aircraft Maintenance Specialist (AMS). After a short discussion with ground staff, the Pilot and AMS flew a familiarisation flight to EIMN where the aircraft landed and taxied to the terminal. It did not stop or shut down but turned on the ramp and flew back to EICA where it shut down and parked while awaiting the arrival of the group. The group assembled at EICA, but as there were too many passengers to be accommodated on one aircraft, two flights were proposed with the aircraft returning to pick up the remainder. The aircraft then departed with the first part of the group. On arrival at EIMN, the Pilot contacted those remaining and informed them that he would not be returning for them. This did not cause a problem because an Aer Arran Islander aircraft, with its pilot, was available at EICA to fly the remainder of the group across to EIMN. Following lunch in a local hotel the AMS made a presentation on behalf of the ASI on the Cessna Caravan, its operation and costing. The Pilot assisted him, answering questions of an operational nature. During the presentation two members of the group, who had a meeting to attend on the mainland, travelled back on the Islander aircraft to EICA. The Islander aircraft subsequently returned to EIMN to assist in transporting the remainder of the group back to EICA. The aircraft was returning on a short flight from Inis Meáin (EIMN), one of the Aran Islands in Galway Bay, to Connemara Airport (EICA), in marginal weather conditions when the accident occurred. There had been a significant wind shift, since the time the aircraft had departed earlier from EICA that morning, of which the Pilot appeared to be unaware. As a result a landing was attempted downwind. At a late stage, a go-around was initiated, at a very low speed and high power setting. The aircraft turned to the left, did not gain altitude and maintained a horizontal trajectory. It hit a mound, left wing first and cartwheeled. The Pilot and one of the passengers were fatally injured. The remaining seven passengers were seriously injured. The aircraft was destroyed but there was no fire. The emergency fire service from the airport quickly attended. Later an ambulance, a local doctor and then the Galway Fire Services arrived. A Coastguard Search and Rescue helicopter joined in transporting the injured to hospital. The Gardaí Síochána secured the site pending the arrival of the AAIU Inspectors.
Probable cause:
The Pilot attempted to land downwind in marginal weather conditions. This resulted in a late go-around during which control was lost due to inadequate airspeed.
Contributory Factors:
1. Communications were not established between the Pilot and EICA thus denying the Pilot the opportunity of being informed of the changed wind conditions and the runway in use.
2. The aircraft was over maximum landing weight.
3. The altimeters were under-reading due to incorrect QNH settings.
4. The additional stress on the Pilot associated with the conduct of a demonstration flight.
Final Report:

Crash of a Rockwell Sabreliner 40R in Culiacán Rosales: 10 killed

Date & Time: Jul 5, 2007 at 0930 LT
Type of aircraft:
Operator:
Registration:
XA-TFL
Flight Phase:
Flight Type:
Survivors:
No
Schedule:
Culiacán Rosales – La Paz
MSN:
265-48
YOM:
1962
Flight number:
1100
Country:
Crew on board:
3
Crew fatalities:
Pax on board:
0
Pax fatalities:
Other fatalities:
Total fatalities:
10
Circumstances:
During the takeoff roll from runway 02, at a speed of about 100 km/h, the aircraft became unstable. The pilot-in-command elected to takeoff twice but the aircraft failed to respond. Twelve seconds later, the captain decided to abandon the takeoff procedure but this decision was taken too late as the remaining distance was 300 metres only. Unable to stop, the aircraft crossed the boundary fence then a motorway where it collided with several vehicles before coming to rest, bursting into flames. All three crew members were killed as well as seven people on the ground. Ten other people on the ground were seriously injured.
Probable cause:
Wrong takeoff configuration on part of the crew. The following contributing factors were identified:
- Lack of crew training,
- Poor crew resources management,
- Pressure on the crew due to the imminent closure of the airport because of presidential visit,
- The crew failed to follow the published procedures,
- A possible failure of the stabilizers,
- Poor operations supervision on part of the operator,
- Late decision of the crew to reject takeoff.