Crash of a Fokker 50 in Nairobi: 4 killed

Date & Time: Jul 2, 2014 at 0417 LT
Type of aircraft:
Operator:
Registration:
5Y-CET
Flight Phase:
Flight Type:
Survivors:
No
Site:
Schedule:
Nairobi - Mogadishu
MSN:
20262
YOM:
26
Country:
Region:
Crew on board:
2
Crew fatalities:
Pax on board:
2
Pax fatalities:
Other fatalities:
Total fatalities:
4
Captain / Total flying hours:
14531
Captain / Total hours on type:
6821.00
Copilot / Total flying hours:
823
Copilot / Total hours on type:
513
Aircraft flight hours:
27342
Aircraft flight cycles:
26358
Circumstances:
On 2 July 2014, about 01.14 UTC, 5Y-CET, a Fokker F50, an international cargo flight, operated by Skyward International, crashed shortly after takeoff from Jomo Kenyatta International Airport (JKIA), Nairobi, Kenya (JKIA). Instrument Meteorological Conditions prevailed at the time and the airplane was on an instrument flight plan. The four crewmembers were fatally injured. The airplane was destroyed and consumed by post-crash fire. The destination of the flight was Aden Adee International Airport, Mogadishu, Somalia. The airplane was repositioned from its home base at Wilson Airport in Nairobi, the day before. The accident captain (CAPT) and another first officer conducted the repositioning flight. (see Aircraft Information). At JKIA, the airplane was loaded with cargo in preparation for the accident flight. The accident crew consisted of the Capt and FO in addition to a maintenance engineer and loadmaster. According to air traffic control (ATC), the flight plan was filed for duration of 2.5 hours at an altitude of 19,000 feet along with 5 hours of fuel aboard. Based on flight recorder data, the Capt was the pilot-flying and the FO was the pilot-monitoring. The accident flight was reconstructed using data from air traffic control and flight recorder information. According to FDR data, engine start occurred at at 01.50.20. At about 01.10.59 the flight made initial contact with JKIA air traffic control tower and after routine communication, including the confirmation of the number of person and fuel endurance, the flight was cleared for takeoff at 0112.30. At 01.11.58, both engines accelerated to a high power setting with engine no. 1 stabilizing at 78% torque, 100% propeller speed and engine 2 stabilizing at 80% torque, 99% propeller speed. About six seconds later, the Capt indicates “power is set”. About 2 seconds afterwards the Capt indicated “the auto-feather is off, left” and then 5 seconds later, the FO calls out “seven eighty” (?). About 16 seconds after initial engine acceleration was applied, the first of a series of three chimes audio alerts occurred, and continued at 1 second interval throughout the CVR recording. Immediately after the initial chimes, the Capt said “you see” and “how much is that?”. The FO responded “okay niner”. The Capt then asked “it has gotten to?” The FO replied “thirty four thirty ninety two” and shortly afterward “the left one is thirty”. About 24 seconds after initial engine acceleration, engine 1 torque climbs over a period of 2 seconds to a recorded value of 119.9%, the maximum value the recorder is capable of recording. Simultaneously Engine 1 propeller speed falls from 100% to 57%. Other engine shaft speeds remain at approximately their original high power values. Airspeed at the point this change occurs was less than 30 knots. During this period, the FO called out “one twenty two now [pause] torque”. The Capt responded “it is rising eh? The FO then noted “torque one twenty six now”. About 31 seconds after initial engine acceleration, the FO called out “okay speed alive sixty”. About a second later the Capt asked “do we reduce or”? The FO responded “we can just cut”. The Capt inquired “do we abort or continue?” The FO responded, “okay one one twelve and nine four point three” and then “okay one sixteen [pause] ninety four.” The Capt acknowledged “yeah okay” About 47 seconds after initial engine acceleration, the Capt said twice “did I reduce it?”and the FO responded sequentially “yeah” and “okay”] About 52 seconds after initial engine acceleration, the Capt asked “how is it now?” and the FO replied “yeah one oh two [pause] ninety four”. About 7 seconds later the FO called out “okay, one sixteen ninety four”. About 1 minute after initial engine acceleration, the Capt inquired “Is it really going?” The FO replied “one oh one, ninety five”. The Capt acknowledged and shortly afterward he queried “is it going really, is the aircraft really moving”. The FO responded “okay, one oh one, ninety five”. About 4 seconds later, the Capt indicated “it is not giving power” About 1 minute 9 seconds after the initial engine acceleration the FO called out “okay speed has now reached about hundred”. The Capt responded “oh yeah” and immediately afterward the FO called out “okay one eleven, ninety five”. About 1 minute 18 seconds after the initial engine acceleration, the FO indicated “hundred now”. The Capt acknowledged. About 1 minute 26 seconds after the initial engine acceleration, the FO called out “V one V R rotate” About 1 minute 33 seconds after the initial engine acceleration a transition of the airplane from ground to air mode is recorded and the pressure altitude begins to climb along with the Capt immediately afterward expressing two exclamations. Following the transition to air mode there were 51 seconds of flight recorder data before the recording ended. During this time and over a period of about 3 seconds, the FO calls out “positive rate of climb” and the Capt responded “gear up”. About 3 second later, the Capt expressed “it doesn’t have power [pause] it’s on one side.” About 6 seconds afterward, the FO said “we can also turn back”. About 3 seconds later the first of seven “don’t sink” (GPWS aural warning alerts) begins over a period of 23 seconds. After the second GPWS alert the Capt queried “ok, we’re ok?” After the third GPWS alert, the FO said “we can turn back” and the Capt immediately responded “let’s just go”. The FO replied “okay”. After the fifth GPWS alert, the Capt indicated “and this one is showing one fourteen” and then queried? “we can turn back?”. About 2 seconds later, the FO called out “okay speed is one hundred” and the Capt responded “but this one has nothing” About 1 second later and about the time of the sixth GPW alert, JKIA control tower radioed “five yankee charlie echo tango contact radar one two three decimal three. Good morning.” After the seventh GPWS alert the recording ended about 13 seconds later. During this time, the controller called the aircraft again. The Capt expressed “tell him [pause] tell him we have no power”. The last CVR data indicates the FO radioed, “ah tower charlie echo” and the transmission abruptly ended along with simultaneous sounds of distress. According to FDR data, about 15 seconds after the airplane transitioned from ground to air mode the recorded altitude peaked about 5060 feet and accompanied by a maximum airspeed of 100 knots. Along with a variation of airspeed between 90 knots and 100 knots for the remainder of the recording, during the following 20 seconds the altitude decreased to about 5000 feet and then increased to 5050 feet over the next 10 seconds where it remained until the recording ended at 1.14.27. Witness Accounts (Air Traffic Controller Civilians). The aircraft crashed during the hours of darkness at geographical coordinates of 01° 17’16”S, 36° 57’5”E.
Probable cause:
The probable cause of the accident was the decision by the crew to conduct the flight with a known mechanical problem and their failure to abort or reject the takeoff after receiving twenty seven cautions.
The following findings were identified:
- A three chime alert occurred during the positioning flight from HKNW to HKJK,
- Crew continued with the flight with a known fault,
- No evidence that remedial maintenance action was taken after landing from that flight prior to the event flight,
- No evidence of the anomaly being captured in the aircraft technical log,
- At least one of the occupants during the event flight, possibly the PIC, had been present during the positioning flight and thus was aware of the three chime alert that had occurred then,
- Twenty seven sound of three chime alert event occurred during the take off roll on the accident flight,
- The aforementioned alert occurred well before V1,
- The left engine exhibited high torque values (in excess of 120%) while the left propeller speed was reduced to the range between 45% to 55% rpm for most of the flight,
- Crew continued with take of roll and subsequent rotation despite the twenty seven chime alert,
- When airborne, crew contemplated turning back but eventually elected to continue with the flight,
- Cargo weight exceeded what was indicated in the load sheet 36,
- There was no evidence of any maintenance having been conducted on the aircraft since its Certificate of Airworthiness issue two months previously (9th May 2014).
Final Report:

Crash of a Harbin Yunsunji Y-12-II in El Wak: 1 killed

Date & Time: May 12, 2014
Type of aircraft:
Operator:
Registration:
KAF124
Flight Phase:
Flight Type:
Survivors:
Yes
Schedule:
Mandera – El Wak – Garissa – Nairobi
MSN:
0095
YOM:
1997
Country:
Region:
Crew on board:
2
Crew fatalities:
Pax on board:
10
Pax fatalities:
Other fatalities:
Total fatalities:
1
Circumstances:
Shortly after takeoff from El Wak Airfield, bound for Garissa, the twin engine aircraft stalled and crashed. The copilot was killed while 11 other occupants were injured. The aircraft was destroyed.

Crash of a Let L-410UVP-E9 in Ngerende: 4 killed

Date & Time: Aug 22, 2012 at 1220 LT
Type of aircraft:
Operator:
Registration:
5Y-UVP
Flight Phase:
Survivors:
Yes
Schedule:
Amboseli – Ngerende – Mara North – Ukunda – Mombasa
MSN:
91 26 27
YOM:
1991
Country:
Region:
Crew on board:
2
Crew fatalities:
Pax on board:
11
Pax fatalities:
Other fatalities:
Total fatalities:
4
Captain / Total flying hours:
7480
Captain / Total hours on type:
1150.00
Copilot / Total flying hours:
312
Circumstances:
This was a commercial non scheduled flight which was being operated for air transport for local flights. The operator is based in Mombasa and mostly executes passenger flights to the Masai Mara and other game parks and reserves within the Republic of Kenya. On 22nd Aug 2012, the aircraft was scheduled to carry out a flight to the Masai Mara, do several sectors to pick and drop passengers and return to Moi international Airport via Ukunda Airport. The call sign was 5Y-UVP. The last point of departure was Ngerende Airstrip in the Masai Mara at 0917 with intention of onward flight to Mara North airstrip in the Masai Mara. The flight had earlier left Amboseli Airstrip with two crew, and 17 passengers for Ngerende Airstrip. 6 passengers had disembarked at Ngerende and the remaining 11 passengers were continuing to other destinations. No additional passengers or cargo was picked up from Ngerende airstrip. No refueling was done at the airstrip. The airfield is an unmanned airfield, with crew executing unmanned airfield communication procedures to execute approach and landings and also during takeoff. There is however a ground time keeper and a fueling bay at the airfield. Due to terrain and prevailing winds at the time of the flight, Runway 28 was in use. The crew was using unmanned airfield procedures and after the drop-off of 6 passengers, the aircraft lined up runway 28 and proceeded with the take off run. Ground staff at the airstrip reported a normal takeoff run and rotation. During the initial climb, the ground staff still had the aircraft in sight and reported to have seen the aircraft veer sharply to the left and then disappear behind terrain. Shortly afterwards, a loud sound was heard followed by dust in the air. Emergency SAR was initiated with the airport and hotel staff rushing to the accident site. The location of the accident was about 310 meters from the threshold of Runway 10, offset 30° to the left of the extended center line Runway 28. GPS coordinates (figure 1.2) 01.084189° S, 35.1781127° E, Ngerende airstrip. The accident occurred at 0917 UTC on 22nd Aug 2012, during daytime.
Probable cause:
The following findings were identified:
- The left engine was most probably not developing power at the time of impact,
- The left engine propeller was most probably in feather at the time of impact,
- Both CVR and FDR were unserviceable at the time of the accident,
- AAID was unable to determine origin of contaminant found in the left engine Fuel Control Unit,
- Sufficient oversight was not exercised over the Operator,
- High turnover of the Operator’s staff.
Final Report:

Crash of a Let L-410UVP-E9 in Kichwa Tembo

Date & Time: Jan 12, 2012 at 1955 LT
Type of aircraft:
Operator:
Registration:
5Y-BSA
Flight Phase:
Survivors:
Yes
Schedule:
Kichwa Tembo – Musiara
MSN:
89 23 23
YOM:
1989
Country:
Region:
Crew on board:
2
Crew fatalities:
Pax on board:
4
Pax fatalities:
Other fatalities:
Total fatalities:
0
Circumstances:
The twin engine aircraft was returning to Mombasa with a scheduled stop in Musiara to pickup 15 additional passengers. On departure from Kichwa Tembo, there were four passengers and two pilots on board. During the takeoff roll from runway 08, the aircraft hit a bump half way down the runway and bounced. The aircraft hit a second bump shortly later and as the crew heard the stall alarm, he decided to reject takeoff. Unable to stop within the remaining distance, the aircraft overran, lost its nose gear and came to rest 300 metres further. All six occupants escaped uninjured while the aircraft was damaged beyond repair.

Crash of a Cessna 401A near Nairobi: 2 killed

Date & Time: Oct 21, 2011 at 1523 LT
Type of aircraft:
Registration:
5Y-CAE
Survivors:
Yes
Schedule:
Nairobi - Marsabit - Lodwar - Nairobi
MSN:
401-0011
YOM:
1967
Country:
Region:
Crew on board:
1
Crew fatalities:
Pax on board:
2
Pax fatalities:
Other fatalities:
Total fatalities:
2
Circumstances:
The twin engine aircraft departed Nairobi-Wilson Airport in the morning for a flight to Marsabit and Lodwar, carrying exam documents. While returning to Wilson Airport in the afternoon, the airplane went out of control and crashed in an open field located about 15 km west of Wilson Airport. The pilot and a passenger were killed while the second passenger was seriously injured. The aircraft was destroyed.

Crash of a Fokker F27 Friendship 500CRF in Nairobi

Date & Time: Jan 27, 2011 at 1335 LT
Type of aircraft:
Operator:
Registration:
5X-FFD
Flight Phase:
Flight Type:
Survivors:
Yes
Schedule:
Nairobi - Nairobi
MSN:
10530
YOM:
1976
Country:
Region:
Crew on board:
2
Crew fatalities:
Pax on board:
2
Pax fatalities:
Other fatalities:
Total fatalities:
0
Circumstances:
The twin engine aircraft was engaged in a local post maintenance test flight from Nairobi-Wilson Airport. The crew consisted of two pilots and two engineers. During the takeoff roll from runway 07, the captain decided to abort. Unable to stop within the remaining distance, the aircraft overran, went through a fence, lost its nose gear and came to rest in a field. All four occupants escaped with minor injuries while the aircraft was damaged beyond repair.

Crash of a Beechcraft 1900D in Nairobi: 2 killed

Date & Time: Nov 9, 2009 at 0517 LT
Type of aircraft:
Operator:
Registration:
5Y-VVQ
Flight Type:
Survivors:
No
Schedule:
Nairobi – Guriceel
MSN:
UE-250
YOM:
1996
Country:
Region:
Crew on board:
2
Crew fatalities:
Pax on board:
0
Pax fatalities:
Other fatalities:
Total fatalities:
2
Aircraft flight hours:
15866
Aircraft flight cycles:
15941
Circumstances:
The airplane departed Wilson Airport at 03:39 hours, transporting a cargo of miraa to Guriceel Airstrip, Somalia. Taxi, take off and climb were uneventful. However, at 04:23 and flying at FL230 the crew contacted Nairobi Area Control Centre (ACC) and requested for a turn back to Wilson Airport due to a 'slight problem'. At about the same time, the aircraft made a right turn from a heading of 50° to 240° magnetic and commenced descent. The crew reported descending to FL220 and expressed intention to descend further to FL180. However, ACC informed the crew to initially maintain FL200 due to traffic moving in the opposite direction. At 04:28 the crew informed ACC that they were unable to maintain FL200 and requested to descend to FL180 having crossed the opposite traffic. At 04:29, the crew confirmed to Air Traffic Control (ATC) that they were heading to Wilson Airport and indicated that they did not require any assistance. The aircraft continued descending until FL120. The Nairobi Approach Radar established contact with the aircraft at 04:41 and indicated to the crew that they were 98 nautical miles North East of November Victor. The crew was then told to turn left to a heading of 225° and report when they were top of descent, which they did. The crew reported again that they had a 'slight problem' and as a safety measure they had to shut down one engine. They also expressed desire to route direct to Silos. At 04:42 5Y-VVQ aligned with the North East access lane via Ndula Marker. At 04:45, the crew confirmed to Nairobi Approach Radar that the malfunction was on the left engine and again acknowledged that they did not require any assistance. At 04:51, the crew requested for radar vectors for an ILS approach to runway 06 at Jomo Kenyatta International Airport with a long final to runway 32 of Wilson Airport. At 05:09, the aircraft descended to 8000ft heading 260°. At 05:14, the crew was given vectors for runway 32 Wilson Airport. At the same time, the aircraft turned right to a heading 310° as it continued to descend to 7000ft. The crew confirmed the vectors and at 05:15 stated that they were passing Visual Meteorological Conditions (VMC). They were also informed that the Wilson Airport runway 32 was 6.5 nautical miles away in the two o'clock direction. The aircraft continued to descend to 6000ft and at 05:16, the crew confirmed sight of runway 32. The crew was then transferred from the radar to the Wilson Tower frequency for landing. 5Y-VVQ was cleared for a straight-in approach to runway 32. Wilson Tower then communicated to the crew airfield QNH was 1022hPa and that winds were calm. The Tower controller had 5Y-VVQ visual and it was cleared to land on runway 32. At about the same time, the aircraft made a 5° right bank and again leveled off before making a steep left bank rising to 30° within 4 seconds. According to Tower and eyewitness information, the aircraft appeared high on approach and on short-final, it was observed to turn a bit to the right. This was followed by a steep left bank. The aircraft left wing hit the ground first approximately 100 meters outside the airport perimeter fence. The aircraft then flipped over, hitting and breaking the airport fence and coming to rest on the left of runway 32 approximately 100 meters from its threshold. The aircraft immediately caught fire upon the impact. Upon further investigations and interview of company personnel, it was established that the crew had made the decision to shut down the left engine following a low oil pressure warning. The flight crew did not declare an emergency.
Probable cause:
The investigation determined the probable cause of the accident as loss of aircraft control at low altitude occasioned by operation of the aircraft below VMCA during one engine inoperative approach.
Other significant contributory factors to this accident include:
- Inadequate pilot training on single engine operation and VMCA;
- inappropriate handling technique during one engine inoperative flight;
- inability of the pilot to monitor the degrading airspeed.

Crash of a Boeing 707-321C in Mombasa

Date & Time: Oct 13, 2009
Type of aircraft:
Registration:
J5-GGU
Flight Type:
Survivors:
Yes
MSN:
19372/655
YOM:
1967
Location:
Country:
Region:
Crew on board:
3
Crew fatalities:
Pax on board:
0
Pax fatalities:
Other fatalities:
Total fatalities:
0
Circumstances:
On final approach to Mombasa-Moi Airport, the aircraft was too low and collided with approach lights. The crew continued the approach and the aircraft landed safely. Few seconds later, while evacuating the runway to the taxiway, the right main gear collapsed. All three crew members escaped uninjured while the aircraft was damaged beyond repair.

Crash of a Cessna 404 Titan in Nairobi: 1 killed

Date & Time: Sep 14, 2009 at 1920 LT
Type of aircraft:
Operator:
Registration:
5Y-PAX
Flight Phase:
Flight Type:
Survivors:
Yes
Schedule:
Nairobi - Nairobi
MSN:
404-0104
YOM:
1977
Country:
Region:
Crew on board:
2
Crew fatalities:
Pax on board:
0
Pax fatalities:
Other fatalities:
Total fatalities:
1
Circumstances:
The crew was completing a local training at Nairobi-Wilson Airport. Shortly after takeoff, while in initial climb, the twin engine aircraft stalled and crashed, bursting into flames. One pilot was killed while the second one was seriously injured. The aircraft was destroyed.

Crash of a De Havilland DHC-5D Buffalo in Lokichoggio

Date & Time: Sep 29, 2008
Type of aircraft:
Registration:
5Y-OPL
Flight Type:
Survivors:
Yes
MSN:
84
YOM:
1978
Country:
Region:
Crew on board:
3
Crew fatalities:
Pax on board:
0
Pax fatalities:
Other fatalities:
Total fatalities:
0
Circumstances:
Upon landing at Lokichoggio Airport, the airplane banked right, causing the right propeller and the right wing to struck the runway surface. The aircraft slid for few dozen metres before coming to rest. There were no injuries while the aircraft was damaged beyond repair.
Probable cause:
It is believed that the right main gear was stuck in its wheel well because the door was blocked.