Crash of a Cessna 402B in Little Whale Cay

Date & Time: Jun 17, 2003 at 1330 LT
Type of aircraft:
Registration:
N3748C
Survivors:
Yes
Schedule:
Chub Cay - Little Whale Cay
MSN:
402B-0606
YOM:
1974
Country:
Crew on board:
1
Crew fatalities:
Pax on board:
2
Pax fatalities:
Other fatalities:
Total fatalities:
0
Circumstances:
On June 17, 2003, about 1330 eastern daylight time, a Cessna 402B, N3748C, registered to Hamilton Development Company Ltd., operated by Execstar Aviation, Inc., collided with a seawall during the landing roll at a private airstrip located on Little Whale Cay, Bahamas. Visual meteorological conditions prevailed at the time and no flight plan was filed for the 14 CFR Part 135 non-scheduled, international, passenger/cargo flight. The airplane was substantially damaged and the commercial-rated pilot and two passengers were not injured. The flight originated about 10 minutes earlier from Chub Cay, Bahamas. The pilot stated that after takeoff the flight proceeded to the destination airport where he overflew the runway and set up for landing to the southeast on the 2,000 foot-long runway. While on final approach with the flaps fully extended, he maintained 95 knots which was just below blue line, then slowed to 88 knots when the runway was assured. He landed within the first 1/3 on the wet runway and reported inadequate braking and the airplane was possibly hydroplaning. Recognizing that he was unable to clear an approximately 4-foot-tall seawall near the end of the runway, he applied aft elevator control input. He further stated he believes the main landing gear contacted the seawall causing them to structurally separate. The airplane descended and impacted the water where he and the passengers exited the airplane using the emergency window and walked to the beach.

Crash of a Piper PA-31P Pressurized Navajo in Augusta: 2 killed

Date & Time: Jun 16, 2003 at 1302 LT
Type of aircraft:
Registration:
N577FS
Flight Phase:
Flight Type:
Survivors:
No
Schedule:
Augusta – Belmont
MSN:
31-7730008
YOM:
1977
Crew on board:
1
Crew fatalities:
Pax on board:
1
Pax fatalities:
Other fatalities:
Total fatalities:
2
Captain / Total flying hours:
8000
Aircraft flight hours:
4412
Circumstances:
A witness at the airport stated the airplane appeared to use half of the 8,000-foot runway on takeoff roll, and the climb out appeared "very flat." During climbout, the pilot reported to the tower controller the airplane "lost an engine," and he announced intentions to return to the runway. The controller stated he noticed the airplane continued straight out and appeared to be losing altitude. Witnesses north of the airport observed the airplane flying low and described its engine noises as "erratic," "skipping," "sputtering," and "some sort of backfire." One witness stated the airplane was moving slowly to the north with a high nose-up angle, and the airplane "appeared to stall" then dove vertically into the trees. Examination of the accident site revealed wreckage debris and broken trees were scattered approximately 120 feet. The airframe, engines, and the right propeller sustained fire damage. The left propeller, top forward portion of the left engine case, and the left propeller gear shaft and bearings were not located. Examination of recovered components revealed no evidence of mechanical malfunction could be determined. According to the Pilot's Operating Handbook for the Piper PA-31P, the stall speed for the airplane with the gear and flaps up is: "(7800 lbs) 80 KCAS, 81 KIAS."
Probable cause:
The pilot's failure to maintain airspeed while maneuvering on initial take off climb resulting in an inadvertent stall, loss of control, and subsequent in-flight collision with trees and a swamp. A factor in the accident was a reported loss of engine power for undetermined reasons.
Final Report:

Crash of a Fokker 50 in Adar Yeil

Date & Time: Jun 16, 2003 at 0630 LT
Type of aircraft:
Operator:
Registration:
ST-ARA
Survivors:
Yes
Schedule:
Khartoum - Adar Yeil
MSN:
20154
YOM:
1989
Country:
Region:
Crew on board:
3
Crew fatalities:
Pax on board:
42
Pax fatalities:
Other fatalities:
Total fatalities:
0
Circumstances:
After landing on a gravel runway at Adar Yeil Airport, the aircraft collided with a flock of birds, damaging the left engine. The aircraft went out of control and veered to the left, causing the left propeller to struck the ground. The propeller blades separated, punctured the fuselage and injured three passengers. The aircraft came to a halt and all occupants evacuated. The aircraft was damaged beyond repair.
Probable cause:
Loss of control after landing following a collision with a flock of birds.

Crash of an Antonov AN-24RV in Nueva Gerona

Date & Time: Jun 14, 2003 at 1605 LT
Type of aircraft:
Operator:
Registration:
CU-T1295
Survivors:
Yes
Schedule:
Nueva Gerona - Havana
MSN:
2 73 075 08
YOM:
1972
Country:
Crew on board:
4
Crew fatalities:
Pax on board:
48
Pax fatalities:
Other fatalities:
Total fatalities:
0
Circumstances:
After takeoff from Nueva Gerona-Rafael Cabrera Airport runway 23, the crew elected to climb to an altitude of 1,000 feet he encountered technical problems. He contacted ATC and was cleared for an immediate return. Following a 180 turn, the crew completed a flapless approach to runway 05. After landing, the aircraft rolled for about 2,500 metres then overran and came to rest in an artificial lake. All 52 occupants evacuated safely while the aircraft was damaged beyond repair.
Probable cause:
Failure of the hydraulic systems after takeoff for unknown reasons.

Crash of an Antonov AN-32B in Jaffna

Date & Time: Jun 14, 2003
Type of aircraft:
Operator:
Registration:
CR-866
Flight Type:
Survivors:
Yes
Schedule:
Colombo - Jaffna
MSN:
36 01
YOM:
1996
Country:
Region:
Crew on board:
5
Crew fatalities:
Pax on board:
50
Pax fatalities:
Other fatalities:
Total fatalities:
0
Circumstances:
After landing at Jaffna-Palaly Airport, the aircraft went out of control and veered off runway. It collided with a signpost, injured one soldier on the ground and came to rest. All 55 occupants escaped uninjured but the aircraft was damaged beyond repair.

Crash of an Embraer EMB-820C Navajo in Belo Horizonte: 4 killed

Date & Time: Jun 11, 2003 at 1600 LT
Registration:
PT-EHH
Survivors:
No
Schedule:
Belo Horizonte – Juiz de Fora
MSN:
820-044
YOM:
1977
Country:
Crew on board:
2
Crew fatalities:
Pax on board:
2
Pax fatalities:
Other fatalities:
Total fatalities:
4
Captain / Total flying hours:
180
Copilot / Total flying hours:
150
Circumstances:
The twin engine aircraft departed Belo Horizonte-Pampulha Airport at 1522LT on a taxi flight to Juiz de Fora, carrying two pilots, two passengers and a load of valuables. While cruising about 35 nm south of Belo Horizonte, the crew encountered technical problems with the engines and elected to return for an emergency landing. On approach to runway 13, the aircraft was too high and the crew was cleared to make a 360 turn to reduce his altitude. Doing so and after he completed 270° of this turn, the aircraft entered an uncontrolled descent and crashed 2 km short of runway, bursting into flames. The aircraft was totally destroyed by impact forces and a post crash fire and all four occupants were killed.
Probable cause:
The right engine suffered a oil leak in flight following the failure of a hose due to poor maintenance. The following contributing factors were identified:
- Both pilots did not have sufficient experience nor training on this type of aircraft,
- The copilot was flying for this operator for the first time,
- The operator was unable to provide any maintenance documentation nor crew training documentation to investigators,
- Both engines were running at impact but with limited power,
- The right propeller was feathered at impact.
Final Report:

Crash of a Piper PA-31-350 Navajo Chieftain in Christchurch: 8 killed

Date & Time: Jun 6, 2003 at 1907 LT
Registration:
ZK-NCA
Survivors:
Yes
Schedule:
Palmerston North – Christchurch
MSN:
31-7405203
YOM:
1974
Country:
Region:
Crew on board:
1
Crew fatalities:
Pax on board:
9
Pax fatalities:
Other fatalities:
Total fatalities:
8
Captain / Total flying hours:
4325
Captain / Total hours on type:
820.00
Aircraft flight hours:
13175
Circumstances:
The aircraft was on an air transport charter flight from Palmerston North to Christchurch with one pilot and 9 passengers. At 1907 it was on an instrument approach to Christchurch Aerodrome at
night in instrument meteorological conditions when it descended below minimum altitude, in a position where reduced visibility prevented runway or approach lights from being seen, to collide with trees and terrain 1.2 nm short of the runway. The pilot and 7 passengers were killed, and 2 passengers received serious injury. The aircraft was destroyed. The accident probably resulted from the pilot becoming distracted from monitoring his altitude at a critical stage of the approach. The possibility of pilot incapacitation is considered unlikely, but cannot be ruled out.
Probable cause:
Findings:
- The pilot was appropriately licensed and rated for the flight.
- The pilotís previously unknown heart disease probably would not have made him unfit to hold his class 1 medical certificate.
- The pilotís ability to control the aircraft was probably not affected by the onset of any incapacitation associated with his heart condition.
- Although the pilot was experienced on the PA 31 type on VFR operations, his experience of IFR operations was limited.
- The pilot had completed a recent IFR competency assessment, which met regulatory requirements for recent instrument flight time.
- The aircraft had a valid Certificate of Airworthiness, and the scheduled maintenance which had been recorded met its airworthiness requirements.
- The return of the cabin heater to service by the operator, after the maintenance engineer had disabled it pending a required test, was not appropriate but was not a factor in the accident.
- The cabin heater was a practical necessity for IFR operations in winter, and the required test should have been given priority to enable its safe use.
- The 3 unserviceable avionics instruments in the aircraft did not comply with Rule part 135, and indicated a less than optimum status of avionics maintenance. However there was sufficient
serviceable equipment for the IFR flight.
- The use of cellphones and computers permitted by the pilot on the flight had the potential to cause electronic interference to the aircraftís avionics, and was unsafe.
- The pilotís own cellphone was operating during the last 3 minutes of the flight, and could have interfered with his glide slope indication on the ILS approach.
- The aircraftís continued descent below the minimum altitude could not have resulted from electronic interference of any kind.
- The pilotís altimeter was correctly set and displayed correct altitude information throughout the approach.
- There was no aircraft defect to cause its continued descent to the ground.
- The aircraftís descent which began before reaching the glide slope, and continued below the glide slope, resulted either from a faulty glide slope indication or from the pilot flying a localiser approach instead of an ILS approach.
- When the aircraft descended below the minimum altitude for either approach it was too far away for the pilot to be able to see the runway and approach lights ahead in the reduced visibility at the time.
- The pilot allowed the aircraft to continue descending when he should have either commenced a missed approach or stopped the aircraftís descent.
- The pilotís actions or technique in flying a high-speed unstabilised instrument approach; reverting to hand-flying the aircraft at a late stage; not using the autopilot to fly a coupled approach and, if intentional, his cellphone call, would have caused him a high workload and possibly overload and distraction.
- The pilotís failure to stop the descent probably arose from distraction or overload, which led to his not monitoring the altimeter as the aircraft approached minimum altitude.
- The possibility that the pilot suffered some late incapacity which reduced his ability to fly the aircraft is unlikely, but cannot be ruled out.
- If TAWS equipment had been installed in this aircraft, it would have given warning in time for the pilot to avert the collision with terrain.
- While some miscommunication of geographical coordinates caused an erroneous expansion of the search area, the search for the aircraft was probably completed as expeditiously as possible in difficult circumstances.
Final Report:

Crash of a De Havilland DHC-2 Beaver in Anchorage

Date & Time: Jun 6, 2003 at 1705 LT
Type of aircraft:
Registration:
N343WB
Flight Type:
Survivors:
Yes
Schedule:
Beluga - Anchorage
MSN:
999
YOM:
1956
Crew on board:
1
Crew fatalities:
Pax on board:
0
Pax fatalities:
Other fatalities:
Total fatalities:
0
Captain / Total flying hours:
6860
Captain / Total hours on type:
1711.00
Aircraft flight hours:
5698
Circumstances:
The float-equipped airplane was in the traffic pattern to land at a seaplane base when the engine lost all power, and the pilot made an emergency landing in the backyard of a private residence. During the forced landing, the airplane struck trees and a railing on the deck of the residence, sustaining structural damage to the left wing. The pilot reported that he had the right wing fuel tank selected, and thought the tank was about 1/4 full. He indicated that when the engine lost power, he was too low and didn't have sufficient time or altitude to switch to the belly tank and restore power. Postaccident draining of the fuel tanks disclosed about 18 gallons of fuel in the belly tank, and about one quart in the right wing tank.
Probable cause:
The pilot's incorrect positioning of the fuel tank selector to a nearly empty tank, which resulted in a loss of engine power due to fuel starvation, and subsequent emergency landing at an off airport site.
Final Report:

Crash of a Learjet 45 in Milan: 2 killed

Date & Time: Jun 1, 2003 at 1526 LT
Type of aircraft:
Operator:
Registration:
I-ERJC
Flight Phase:
Flight Type:
Survivors:
No
Schedule:
Milan - Genoa - Amsterdam
MSN:
45-093
YOM:
2000
Flight number:
ERJ1570
Country:
Region:
Crew on board:
2
Crew fatalities:
Pax on board:
0
Pax fatalities:
Other fatalities:
Total fatalities:
2
Captain / Total flying hours:
1031
Captain / Total hours on type:
544.00
Copilot / Total flying hours:
500
Copilot / Total hours on type:
14
Aircraft flight hours:
931
Aircraft flight cycles:
890
Circumstances:
The aircraft departed Milan-Linate Airport on a positioning flight to Genoa to pick up passengers for Amsterdam. Shortly after takeoff from runway 36R, while in initial climb, the aircraft collided with a flock of pigeons that struck both engines. The crew declared an emergency and reported technical problems without giving any other details. He was cleared for an immediate return and initiated a turn to the east. One minute and 25 seconds after takeoff, the aircraft entered an uncontrolled descent and crashed on a factory located 750 metres southeast from the runway 36R threshold. The aircraft was totally destroyed by impact forces and a post crash fire and both pilots were killed.
Probable cause:
The event, triggered by a multiple impact with birds during take-off, was caused by the loss of control in flight of the aircraft, due to an aerodynamic stall during the return to the departure airport, which could not be recovered due to the reduced altitude available.
The following factors contributed to the event:
- The non-implementation of the procedure provided for in the Flight Manual for engine failure after V1, with particular reference to configuration control (undercarriage and flaps), thrust lever management, definition and achievement of safety altitude, maintenance of expected speeds,
- The lack of CRM, already detectable in the ground procedures phase, but significantly worsened as a result of the emergency,
- The lack of experience of FO, on its first flight of line training on the type of aircraft,
- The inadequacy of the measures and of the bird control activity in the manoeuvring area.
Final Report:

Crash of a Rockwell Aero Commander 500B in Grand Canyon

Date & Time: May 28, 2003 at 1720 LT
Registration:
N64TS
Flight Phase:
Flight Type:
Survivors:
Yes
Schedule:
Grand Canyon - Rialto
MSN:
500-1442-156
YOM:
1964
Crew on board:
1
Crew fatalities:
Pax on board:
3
Pax fatalities:
Other fatalities:
Total fatalities:
0
Captain / Total flying hours:
26110
Captain / Total hours on type:
850.00
Aircraft flight hours:
4587
Circumstances:
The airplane did not gain altitude after takeoff and collided with trees and terrain off the departure end of the runway. Prior to takeoff the pilot received a computerized weather briefing that showed generally good conditions. The tower controller cleared the pilot to taxi to the active runway (runway 21) and issued winds, which were 300 degrees at 10 knots, a direct crosswind. During the initial climb after liftoff, the pilot saw that the airplane had stopped climbing and he asked for and received the wind information again. With the airplane not climbing and headed directly for some trees, the pilot maneuvered the airplane towards a clearing but the left wing hit a tree and the airplane descended into the ground. The pilot reported no mechanical problems with the airframe and engines. The density altitude was calculated to be 9,481 feet. The aircraft's gross weight at the time of takeoff was 6,000 pounds. Review of the Airplane Flight Manual climb performance charts for that aircraft weight at the pressure altitude and reported outside air temperature discloses that the airplane should have had a positive rate of climb of about 1,100 feet per minute. The airport was equipped with a wind information recording system, which had four sensors. Three sensors recorded wind information at ground level only. They were placed, one each, at the approach, middle, and departure ends of the runway. Wind data was recorded every 10 seconds. The system does not have the capability to predict or warn of wind shear events. During the aircraft's departure, the approach end sensor recorded winds at 068 degrees at 1 knot; the middle sensor recorded winds at 293 degrees at 5 knots; and the departure sensor recorded winds at 302 degrees at 2 knots. At the next data sampling (10 seconds later), the departure end sensor recorded a wind increase of 10 knots, and the approach end recorded a wind shift from a headwind to a tailwind at 10 knots. A full analysis of the weather conditions indicated that due to developing convection over the runway the airplane likely encountered a wind shear (increasing tailwind) event that seriously degraded the takeoff and climb performance.
Probable cause:
The pilot's encounter with a wind shear just after liftoff.
Final Report: