Crash of a Cessna 208B Grand Caravan in Yambio

Date & Time: May 2, 2012 at 1055 LT
Type of aircraft:
Operator:
Registration:
5Y-NGO
Flight Type:
Survivors:
Yes
Schedule:
Juba - Yambio
MSN:
208B-0322
YOM:
1992
Country:
Region:
Crew on board:
2
Crew fatalities:
Pax on board:
9
Pax fatalities:
Other fatalities:
Total fatalities:
0
Circumstances:
It was reported that the aircraft had taken-off from Juba for Yambio, Sothern Sudan with two crew members and nine passengers onboard. The flight was uneventful up to and until after touchdown, twenty metres after the threshold of runway 03, when it was noted that the aircraft steadily veered to the left. Efforts by the captain to prompt the pilot flying and intercession by taking control of the aircraft and initiating the necessary corrective measures by applying full right rudder yielded no positive results. The aircraft left wheel entered the trench at high speed, causing the aircraft to flip over and crash 200metrs from threshold of runway 03 and came rest in an inverted position. All persons exited safely on their own, except two passengers who were assisted by the captain to disembark. The captain used the portable fire extinguisher to put off the fire that flickered in the engine compartment. The flying pilot sustained injuries on his right foot, while the other passengers were reported to have hard minor injuries. The prevailing weather at the time of occurrence was reported as CAVOK (clear sky, and visibility better than 10Km) with calm North Easterly winds (030/05).
Final Report:

Crash of an Airbus A300B4-605R in Jeddah

Date & Time: May 1, 2012 at 1449 LT
Type of aircraft:
Operator:
Registration:
TC-OAG
Flight Type:
Survivors:
Yes
Schedule:
Madinah - Jeddah
MSN:
747
YOM:
1994
Flight number:
SV2865
Country:
Region:
Crew on board:
10
Crew fatalities:
Pax on board:
0
Pax fatalities:
Other fatalities:
Total fatalities:
0
Captain / Total flying hours:
9200
Copilot / Total flying hours:
15957
Aircraft flight hours:
54832
Aircraft flight cycles:
18308
Circumstances:
On 1 May 2012, aircraft TC-OAG, an Airbus A300-605R was performing a commercial flight for Saudi Arabian Airlines (SVA) as SVA2865. SVA 2865 departed from Prince Mohammed Bin Abdulaziz International Airport (PMAI) Madinah at 08h50 en-route to the King Abdulaziz International Airport (KAIA) Jeddah, Kingdom of Saudi Arabia. SVA 2865 was on a positioning flight with 10 crew members and no passengers. No discrepancies were noted on this aircraft prior to departure from Madinah. The visibility at Jeddah was good with a few clouds present. During the initial ILS approach to runway 16 Right (16R), while at 8 nautical miles (nm) and 2600 feet (ft), the landing gear handle was lowered. Both main landing gear extended and locked down and, the nose gear doors opened but the nose landing gear did not lower. The Captain who was then the Pilot Monitoring (PM) took over the controls and carried out a missed approach. The First Officer (FO) became the Pilot Monitoring (PM). SVA 2865 was then given an area to the northeast of Jeddah to carry out attempts at lowering the nose gear. The flight crew attempted to manually free fall the nose landing gear at least ten (10) times. The nose landing gear would not lower into the locked position, but the nose gear doors remained open during all those attempts. As a precautionary measure, SVA 2865 performed a fly-by of runway 16R at 500 ft. The air traffic controller confirmed that the nose landing gear (NLG) was not down. SVA 2865 was vectored over the Red Sea to lower the fuel load, thus reducing the landing weight. During this period, the Fire & Rescue Services (FRS) at Jeddah foamed a portion of runway 16 Left (16L) between taxiway Kilo 5 (K5) and K2. The majority of the FRS vehicles were standing by at the junction of taxiways K4 and K3. SVA 2865 was vectored for an instrument approach for Runway 16L. The Auto Pilot and the Auto Throttle Systems were OFF. The surface winds were from 220° at 12 knots (kt), gusting to 19 kt and the temperature was + 37 Celsius (°C). The flight crew used the "Landing with Nose Landing Gear Abnormal" checklist ensuring the aircraft was properly prepared and configured for the approach, the before landing, the flare and the touchdown sequences, including when the aircraft stopped and the necessary procedures to secure the aircraft before evacuation. The aircraft landed on its main landing gear 4000 ft past the threshold of runway 16L. The nose of the aircraft was slowly lowered to the runway with the nose landing gear doors touching the runway within the foamed area 4500 ft from the end of runway 16L. The front of the fuselage then touched the runway within the last portion of foam, 3500 ft from the end of runway 16L. The nose area of the aircraft slid on the runway, where sparks were present until the aircraft came to a full stop 1500 ft prior to the end of runway 16L. As soon as the aircraft passed by the position of the FRS vehicles, the FRS vehicles gave chase to the aircraft and reached it within 30 seconds after it came to a full stop. Although there was no post-crash fire, the FRS personnel applied water and foam to the nose area of the aircraft. All of the crew members were evacuated from the aircraft by ladder provided by the FRS. The crew was taken to the airport clinic as a precautionary measure. All were released the same day. The accident occurred at 14h49 on runway 16L at the KAIA - Jeddah, Kingdom of Saudi Arabia.
Probable cause:
Cause related findings:
- The NLG up-lock contained a spring, Part Number GA71102 that was broken as a result of fatigue initiated at the third coil of the spring.
- The spring had been broken for a prolonged period of time, as noted by the spring linear wear marks on the outside area of the spring coils.
- Damage observed on the NLG up-lock resulted from hard contact with the broken spring during normal NLG operation.
- The fracture process of the spring was initiated at the third coil level. At least 6000 cycles of fatigue (number of striations) have been estimated by fatigue striation measurements. The crack on the spring started on the internal surface of the spring which was not shot peened.
- The normal and free fall extensions of the NLG failed due to a mechanical blockage created by the broken spring jammed against the cam.
Final Report:

Crash of an ATR72-500 in Dhaka

Date & Time: Apr 30, 2012 at 0851 LT
Type of aircraft:
Operator:
Registration:
60314
Flight Type:
Survivors:
Yes
Schedule:
Bangkok - Dhaka
MSN:
881
YOM:
2009
Flight number:
KAT304
Country:
Region:
Crew on board:
7
Crew fatalities:
Pax on board:
8
Pax fatalities:
Other fatalities:
Total fatalities:
0
Circumstances:
After landing at Dhaka-Hazrat Shahjalal Airport, the twin engine aircraft deviated to the right and veered off runway. It collided with an embankment, lost its undercarriage and came to rest against a concrete wall. All 15 occupants were rescued, among them two passengers were slightly injured.

Crash of an Antonov AN-24RV in Galkayo

Date & Time: Apr 28, 2012 at 1433 LT
Type of aircraft:
Operator:
Registration:
3X-GEB
Survivors:
Yes
Schedule:
Hargeisa - Galkayo
MSN:
3 73 084 03
YOM:
1973
Flight number:
6J711
Country:
Region:
Crew on board:
4
Crew fatalities:
Pax on board:
32
Pax fatalities:
Other fatalities:
Total fatalities:
0
Circumstances:
Following an uneventful flight from Hargeisa, the crew started the descent to Galkayo-Abdullahi Yusuf Airport runway 05L. On short final, at a height of about 5-7 feet, the captain spotted an animal crossing the runway from left to right. He attempted to extend the flare in order to avoid a collision but the aircraft subsequently touched down hard and bounced several times. Out of control, it veered off runway and came to rest with both wings partially detached. All 36 occupants evacuated safely while the aircraft was damaged beyond repair.

Crash of a Boeing 727-212 in Laguna Salada

Date & Time: Apr 27, 2012 at 1000 LT
Type of aircraft:
Operator:
Registration:
XB-MNP
Flight Type:
Survivors:
Yes
Site:
MSN:
21348/1287
YOM:
1977
Country:
Crew on board:
0
Crew fatalities:
Pax on board:
0
Pax fatalities:
Other fatalities:
Total fatalities:
0
Circumstances:
The aircraft departed Mexicali Airport with one pilot on board. The goal of the flight was a test experiment on behalf of the Mexican Civil Aviation Authority and various agencies to crash deliberately the aircraft in the Laguna Salada for a television program organized by British, German, Mexican and American Producers. While approaching the desert along the Mexican 5 Highway, about 30 km southwest of Mexicali, the pilot bailed out and the aircraft continued for few seconds in a slightly flat attitude. In a flaps down and gear down configuration, the aircraft touched down hard in a sandy area, lost its undercarriage, crashed and came to rest, broken in two.

Crash of a Curtiss C-46F-1-CU Commando in Santa Cruz: 3 killed

Date & Time: Apr 21, 2012 at 0813 LT
Type of aircraft:
Operator:
Registration:
CP-1319
Flight Type:
Survivors:
Yes
Schedule:
Santa Cruz - Cobija
MSN:
22428
YOM:
1945
Country:
Crew on board:
3
Crew fatalities:
Pax on board:
1
Pax fatalities:
Other fatalities:
Total fatalities:
3
Captain / Total flying hours:
12500
Copilot / Total flying hours:
3219
Aircraft flight hours:
29080
Circumstances:
The crew departed Santa Cruz-Viru Viru Airport at 0807LT on a cargo flight to Cobija-E. Beltram Airport. Shortly after takeoff from runway 16, the crew informed ATC he was returning but did not give any details about his situation. On final approach, the aircraft adopted a high-nose attitude, climbed then stalled and crashed 200 metres short of runway, bursting into flames. The passenger was seriously injured and all three crew members were killed. The aircraft was totally destroyed by a post crash fire.
Probable cause:
The cause of the accident was that the aircraft, while on short finals and cleared to land, made an unusual flight maneuver by climbing almost vertically until a wing stall and plunging violently against the terrain, bursting into flames within the security area of the runway.
Final Report:

Crash of a Beechcraft G18S in Cornelia

Date & Time: Apr 21, 2012
Type of aircraft:
Registration:
N6B
Flight Type:
Survivors:
Yes
Schedule:
Miami - Dickson
MSN:
BA-573
YOM:
1961
Crew on board:
1
Crew fatalities:
Pax on board:
0
Pax fatalities:
Other fatalities:
Total fatalities:
0
Circumstances:
The twin engine aircraft departed Miami on a flight to Dickson, Tennessee. By night, the pilot decided to land at Cornelia Fort Airpak which is closed to traffic at this time. In unclear circumstances, the aircraft belly landed in a grassy area along the left side of runway 22 and came to rest. The pilot escaped uninjured and the aircraft was damaged beyond repair.
Probable cause:
No investigations were completed by the NTSB.

Crash of a Boeing 737-236 in Islamabad: 127 killed

Date & Time: Apr 20, 2012 at 1840 LT
Type of aircraft:
Operator:
Registration:
AP-BKC
Survivors:
No
Schedule:
Karachi - Islamabad
MSN:
23167/1074
YOM:
1984
Flight number:
BHO213
Country:
Region:
Crew on board:
6
Crew fatalities:
Pax on board:
121
Pax fatalities:
Other fatalities:
Total fatalities:
127
Captain / Total flying hours:
10158
Captain / Total hours on type:
2027.00
Copilot / Total flying hours:
2832
Copilot / Total hours on type:
750
Aircraft flight hours:
46933
Aircraft flight cycles:
37824
Circumstances:
On 20th April, 2012, M/s Bhoja Air Boeing 737-236A Reg # AP-BKC was scheduled to fly domestic Flight BHO-213 from Jinnah International Airport (JIAP) Karachi to Benazir Bhutto International Airport (BBIAP) Islamabad. The aircraft had 127 souls onboard including 06 flight crew members. The Mishap Aircraft (MA) took off for Islamabad at 1705 hrs Pakistan Standard Time (PST) from Karachi. The reported weather at Islamabad was thunderstorm with gusty winds. During approach for landing at BBIAP, Islamabad (OPRN), Flight BHO-213 was cleared by Islamabad Approach Radar for an Instrument Landing System (ILS) approach for Runway 30. The MA, while established on ILS (aligned with Runway 30 at prescribed altitude), at 6 miles to touchdown was asked by the Approach Radar to change over to Air Traffic Control (ATC) Tower frequency for final landing clearance. The cockpit crew came on ATC Tower frequency and flight was cleared to land at BBIAP, Islamabad, but the cockpit crew did not respond to the landing clearance call. The ATC Tower repeated the clearance but there was no response. After a few minutes, a call from a local resident was received in ATC Tower, stating that an aircraft had crashed close to Hussain Abad (A population around 4 nm short of runway 30 BBIAP, Islamabad). It was later confirmed that Flight BHO-213 had crashed and all 127 souls onboard (121 passengers + 6 flight crew) had sustained fatal injuries along with complete destruction of aircraft.
Probable cause:
Factors Leading to the Accident:
- The aircraft accident took place as a result of combination of various factors which directly and indirectly contributed towards the causation of accident. The primary causes of accident include, ineffective management of the basic flight parameters such as airspeed, altitude, descent rate attitude, as well as thrust management. The contributory factors include the crew’s decision to continue the flight through significant changing winds associated with the prevailing weather conditions and the lack of experience of the crew to the airplane’s automated flight deck.
- The reasons of ineffective management of the automated flight deck also include Bhoja Air’s incorrect induction of cockpit crew having experience of semi automated aircraft, inadequate cockpit crew simulator training and absence of organizational cockpit crew professional competence and monitoring system.
- The incorrect decision to continue for the destination and not diverting to the alternate aerodrome despite the presence of squall line and very small gaps observed by the Captain between the active weather cells is also considered a contributory factor in causation of the accident.
- The operator’s Ops Manual (CAA Pakistan approved) clearly states to avoid active weather cells by 5 to 10 nm which was violated by the cockpit crew is also considered a contributory factor in causation of the accident.
- FO possessed average professional competence level and was due for his six monthly recurrent simulator training for Boeing 737-200 aircraft (equipped with a semi-automated flight deck). Bhoja Air requested an extension for his recurrent simulator training on 07th March, 2012. As per the existing laid down procedures of CAA Pakistan, two months extension was granted for recurrent simulator training on 09th March, 2012. The extension was granted for Boeing 737-200 aircraft, whereas the newly inducted Boeing 737-236A aircraft was equipped with automated flight deck. It is important to note that Bhoja Air did not know this vital piece of information till their cockpit crew went for simulator training to South Africa. This critical information regarding automation of the newly inducted Boeing 737-236A was not available with Flight Standard Directorate CAA, Pakistan as the information was not provided by the Bhoja Air Management.
- Therefore it is observed that due to the ignorance of Bhoja Air Management and CAA Pakistan, the said extension in respect of FO for simulator training was initially requested by former and subsequently approved by the latter. This resulted in absence of variance type training conformance of FO because of which he did not contribute positively in recovering the aircraft out of unsafe set of conditions primarily due to lack of automation knowledge, proper training and relying on captain to take remedial actions. This is also considered as one of the contributory factors in causation of accident.
- The Captain’s airline flying experience on semi automated flight deck aircraft and his selection for automated aircraft without subsequent training and monitoring to enhance his professional competence and skill, is one of the factors in causation of the accident.
- None of the cockpit crew member challenged the decision of each other to continue for the destination despite violation of Ops Manual instructions which is against the essence of CRM training.
- After experiencing the extremely adverse weather conditions, the cockpit crew neither knew nor carried out the Boeing recommended QRH and FCOM / Ops Manual procedures to handle the abnormal set of conditions / situations due to non availability of customized Boeing documents for Boeing 737-236A (advanced version of Boeing 737-200 series).

Finalization:
- The ineffective automated flight deck management in extreme adverse weather conditions by cockpit crew caused the accident. The ineffective automated flight deck management was due to various factors including; incorrect selection of cockpit crew on account of their inadequate flying experience, training and competence level for Boeing 737-236A (advanced version of Boeing 737-200 series), absence of formal simulator training in respect of FO for handling an automated flight deck, non-existence of cockpit crew professional competence / skill level monitoring system at operator level (Bhoja Air).
- The cockpit crew incorrect decision to continue the flight for destination and non- adherence to Boeing recommended QRH and FCOM remedial actions / procedures due to non-availability of customized aircraft documents (at Bhoja Air) for Boeing 737-236A (advanced version of Boeing 737-200 series) contributed towards the causation of accident. The inability of CAA Pakistan to ensure automated flight deck variance type training and monitoring requirements primarily due to incorrect information provided by the Bhoja Air Management was also a contributory factor in causation of the accident.
Final Report:

Crash of a Beechcraft C90B King Air in Jundiaí: 1 killed

Date & Time: Apr 20, 2012 at 1430 LT
Type of aircraft:
Registration:
PP-WCA
Flight Type:
Survivors:
No
Schedule:
Jundiaí - Jundiaí
MSN:
LJ-1676
YOM:
2002
Country:
Crew on board:
1
Crew fatalities:
Pax on board:
0
Pax fatalities:
Other fatalities:
Total fatalities:
1
Circumstances:
The pilot, sole aboard, was completing a local flight from Jundiaí-Comandante Rolim Adolfo Amaro Airport. Shortly after takeoff from runway 36, the pilot reported to ATC that the engine lost power and that he was not able to maintain a safe altitude. He was cleared for an immediate return and completed a circuit. On final approach to runway 18, he lost control of the airplane that crashed 180 metres short of runway and came to rest upside down, bursting into flames. The aircraft was totally destroyed and the pilot was killed.
Probable cause:
The following factors were identified:
- Upon intercepting the final leg for landing, the aircraft crossed the approach axis, and the pilot, in an attempt to make the aircraft join the approach axis again, may have depressed the rudder pedal in an inadequate manner, inadvertently making the aircraft enter a Cross Control Stall.
- The pilot, intentionally, violated a number of aeronautical regulations in force in order to fly an aircraft for which he had no training and was not qualified.
- The short experience of the pilot in the aircraft model hindered the correct identification of the situation and the adoption of the necessary corrective measures.
- The DCERTA’s vulnerability allowed a non-qualified pilot to file a flight notification by making use of the code of a qualified pilot. Thus, the last barrier capable of preventing the accident flight to be initiated was easily thrown down, by making it difficult to implement a more effective supervisory action.
Final Report:

Crash of a Fokker F27 Friendship 500 in Yida

Date & Time: Apr 15, 2012 at 1321 LT
Type of aircraft:
Operator:
Registration:
5Y-SRJ
Flight Type:
Survivors:
Yes
Schedule:
Lokichogio - Yida
MSN:
10372
YOM:
1968
Country:
Region:
Crew on board:
3
Crew fatalities:
Pax on board:
0
Pax fatalities:
Other fatalities:
Total fatalities:
0
Circumstances:
The aircraft departed Lokichoggio Airport at 1103LT on a cargo flight to Yida, carrying three crew members and a load consisting of food. En route, while cruising at an altitude of 16,000 feet, the right engine failed. The crew was able to restart it but it failed again few minutes later. The crew started the approach on one engine and landed uneventfully. While decelerating, the nose gear collapsed and the aircraft came to rest. All three crew members escaped uninjured while the aircraft was damaged beyond repair. Both engines accumulated about 20 hours since the last overhaul and it is believed that the nose gear failed due to fatigue cracks.