Crash of an Airbus A300B4-203F at Bagram AFB

Date & Time: Mar 1, 2010 at 1210 LT
Type of aircraft:
Operator:
Registration:
TC-ACB
Flight Type:
Survivors:
Yes
Schedule:
Bahrain - Bagram AFB
MSN:
121
YOM:
1980
Country:
Region:
Crew on board:
5
Crew fatalities:
Pax on board:
0
Pax fatalities:
Other fatalities:
Total fatalities:
0
Captain / Total flying hours:
12923
Captain / Total hours on type:
8000.00
Aircraft flight hours:
25300
Aircraft flight cycles:
46516
Circumstances:
While approaching Bagram AFB, the crew did not obtain the three green lights when the undercarriage were lowered. The left main gear signal appears to remain red. The captain obtained the authorization to make two low passes over the airport then ATC confirmed that all three gears were down. The final approach was completed at low speed and after touchdown, while braking, the left main gear collapsed. The aircraft veered off runway to the left and came to rest some 2 km past the runway threshold. All five crewmen were unhurt while the aircraft was damaged beyond repair.
Probable cause:
Cracks as result of fatigue caused the fracture of the hinge arm of the left main gear strut. The cracking most likely occurred as result of corrosion that remained undetected during the last maintenance inspection. The origin of pitting could not be identified, the investigation however identified deficiencies in the maintenance task conducted during last overhaul of the gear strut. Incomplete maintenance documentation and tools available during overhaul contributed to the accident.
Final Report:

Crash of a Boeing 747-209F in Brussels

Date & Time: May 25, 2008 at 1331 LT
Type of aircraft:
Operator:
Registration:
N704CK
Flight Phase:
Flight Type:
Survivors:
Yes
Schedule:
New York – Brussels – Bahrain
MSN:
22299/462
YOM:
1980
Flight number:
CKS207
Country:
Region:
Crew on board:
5
Crew fatalities:
Pax on board:
0
Pax fatalities:
Other fatalities:
Total fatalities:
0
Captain / Total flying hours:
15000
Captain / Total hours on type:
3000.00
Copilot / Total flying hours:
7000
Copilot / Total hours on type:
200
Aircraft flight hours:
108560
Aircraft flight cycles:
20599
Circumstances:
The flight crew arrived at Brussels the day before the accident, with a flight from Bahrain. The crew rested until the Sunday morning. The aircraft arrived at Brussels on Sunday with another crew; the two crews exchanged some information regarding the airplane. There were no mechanical problems reported. Runway 20 was in service for take-offs, while Runway 25L was mostly used for landings. The pilot performed the pre-flight inspection; he found only minor discrepancies (left inner tire check and E&E door latch down). The pre-flight briefing covered the standard departure call-outs, the runway incursion information, a discussion on the Runway 20 length, etc.. The crew also briefed about the engine failure procedures for an engine failure prior to V1, and they also briefed about an abort takeoff after V1 if there was a dangerous situation that would not allow the airplane to fly. After completing the flight documents, the crew requested an early departure, which they received. For the computation of the take-off parameters, the crew used the Kalitta Air On-board Performance System (OPS computer). The crew determined they needed the full length of the runway for take-off. The airplane taxied towards the B1 intersection for the Runway 20. After a few minutes, waiting for another airplane to land on Runway 25, they lined up on Runway 20, making a tight turn, in order to gain a few meters with respect to the usual departure position. The airplane was cleared for take-off at 11:29. The pilot pushed the throttles forward and checked the engines were stable. The Flight Engineers then set the engine power for take-off (setting “normal”, also known as “reduced thrust”). The aircraft started to accelerate. The standard call-out were made when the speed reached the determined value.
- “airspeed”
- 80 knots
- V1
A few seconds after reaching V1, the engine N°3 ingested a bird. Approximately 5 seconds after V1, the engine N°3 stalled and caused a loud “bang”, and a vibration felt in the cockpit. The pilot stated he had the feeling that the aircraft was no longer accelerating, and decided to abort the take-off. Two seconds after having heard the detonation, the thrust levers were brought back to idle, and braking action was initiated. The thrust reversers were not deployed. The FO called the tower, and notified the aircraft was going to the overrun. The pilot turned the aircraft a few degrees to the right, in order to avoid the approach lights at the end of the runway. The aircraft left the runway at a speed of approximately 72 Knots. The aircraft reached a first embankment, dropping from a height of 4 m, and broke in three parts. The aircraft came to a stop just above the top of the railroad embankment. The crew exited the airplane through the service door since the L1 door normally used was blocked due to deformation of the structure.
Probable cause:
The accident was caused by the decision to reject the takeoff 12 knots after passing V1 speed. The following factors contributed to the accident:
- Engine Nr 3 experienced a bird strike, causing it to stall. This phenomenon was accompanied by a loud bang, noticed by the crew.
- The aircraft line up at the B1 intersection although the take-off parameters were computed with the full length of the runway.
- The situational awareness of the crew,
- Less than maximum use of deceleration devices.
- Although the RESA conforms to the minimum ICAO requirement, it does not conform to the ICAO recommendation for length.
Final Report:

Crash of an Airbus A320-212 off Bahrain: 143 killed

Date & Time: Aug 23, 2000 at 1930 LT
Type of aircraft:
Operator:
Registration:
A4O-EK
Survivors:
No
Schedule:
Cairo - Bahrain - Muscat
MSN:
481
YOM:
1994
Flight number:
GF072
Country:
Region:
Crew on board:
8
Crew fatalities:
Pax on board:
135
Pax fatalities:
Other fatalities:
Total fatalities:
143
Captain / Total flying hours:
4416
Captain / Total hours on type:
1083.00
Copilot / Total flying hours:
608
Copilot / Total hours on type:
408
Aircraft flight hours:
17370
Aircraft flight cycles:
13990
Circumstances:
On 23 August 2000, at about 1930 local time, Gulf Air flight GF072, an Airbus A320-212, a Sultanate of Oman registered aircraft A4O-EK, crashed at sea at about 3 miles north-east of Bahrain International Airport. GF072 departed from Cairo International Airport, Egypt, with two pilots, six cabin crew and 135 passengers on board for Bahrain International Airport, Muharraq, Kingdom of Bahrain. GF072 was operating a regularly scheduled international passenger service flight under the Convention on International Civil Aviation and the provisions of the Sultanate of Oman Civil Aviation Regulations Part 121 and was on an instrument flight rules (IFR) flight plan. GF072 was cleared for a VOR/DME approach for Runway 12 at Bahrain. At about one nautical mile from the touch down and at an altitude of about 600 feet, the flight crew requested for a left hand orbit, which was approved by the air traffic control (ATC). Having flown the orbit beyond the extended centreline on a south-westerly heading, the captain decided to go-around. Observing the manoeuvre, the ATC offered the radar vectors, which the flight crew accepted. GF072 initiated a go-around, applied take-off/go-around thrust, and crossed the runway on a north-easterly heading with a shallow climb to about 1000 feet. As the aircraft rapidly accelerated, the master warning sounded for flap over-speed. A perceptual study, carried out as part of the investigation, indicated that during the go-around the flight crew probably experienced a form of spatial disorientation, which could have caused the captain to falsely perceive that the aircraft was ‘pitching up’. He responded by making a ‘nose-down’ input, and, as a result, the aircraft commenced to descend. The ground proximity warning system (GPWS) voice alarm sounded: “whoop, whoop pull-up …”. The GPWS warning was repeated every second for nine seconds, until the aircraft impacted the shallow sea. The aircraft was destroyed by impact forces, and all 143 persons on board were killed.
Probable cause:
The factors contributing to the above accident were identified as a combination of the individual and systemic issues. Any one of these factors, by itself, was insufficient to cause a breakdown of the safety system. Such factors may often remain undetected within a system for a considerable period of time. When these latent conditions combine with local events and environmental circumstances, such as individual factors contributed by “frontline” operators (e.g.: pilots or air traffic controllers) or environmental factors (e.g.: extreme weather conditions), a system failure, such as an accident, may occur.
The investigation showed that no single factor was responsible for the accident to GF072. The accident was the result of a fatal combination of many contributory factors, both at the individual and systemic levels. All of these factors must be addressed to prevent such an accident happening again.
(1) The individual factors particularly during the approach and final phases of the flight were:
(a) The captain did not adhere to a number of SOPs; such as: significantly higher than standard aircraft speeds during the descent and the first approach; not stabilising the approach on the correct approach path; performing an orbit, a non-standard manoeuvre, close to the runway at low altitude; not performing the correct go-around procedure; etc.
(b) In spite of a number of deviations from the standard flight parameters and profile, the first officer (PNF) did not call them out, or draw the attention of the captain to them, as required by SOP’s.
(c) A perceptual study indicated that during the go-around after the orbit, it appears that the flight crew experienced spatial disorientation, which could have caused the captain to perceive (falsely) that the aircraft was ‘pitching up’. He responded by making a ‘nose-down’ input, and as a result, the aircraft descended and flew into the shallow sea.
(d) Neither the captain nor the first officer perceived, or effectively responded to, the threat of increasing proximity to the ground, in spite of repeated hard GPWS warnings.
(2) The systemic factors, identified at the time of the above accident, which could have led to the above individual factors, were:
(a) Organisational factors (Gulf Air):
(i) A lack of training in CRM contributing to the flight crew not performing as an effective team in operating the aircraft.
(ii) Inadequacy in the airline's A320 training programmes, such as: adherence to SOPs, CFIT, and GPWS responses.
(iii) The airline’s flight data analysis system was not functioning satisfactorily, and the flight safety department had a number of deficiencies.
(iv) Cases of non-compliance, and inadequate or slow responses in taking corrective actions to rectify them, on the part of the airline in some critical regulatory areas, were identified during three years preceding the accident.
(b) Safety oversight factors:
A review of about three years preceding the accident indicated that despite intensive efforts, the DGCAM as a regulatory authority could not make the operator comply with some critical regulatory
requirements.
Final Report:

Crash of a Boeing 707-123B in Bahrain

Date & Time: Aug 19, 1979
Type of aircraft:
Operator:
Registration:
5B-DAM
Survivors:
Yes
Schedule:
Larnaca - Bahrain
MSN:
17628/7
YOM:
1958
Flight number:
CY402
Country:
Region:
Crew on board:
8
Crew fatalities:
Pax on board:
73
Pax fatalities:
Other fatalities:
Total fatalities:
0
Captain / Total hours on type:
93.00
Circumstances:
The four engine airplane landed hard on runway 30 at Bahrain-Muharraq Airport. It bounced then landed on its nose gear first. Upon touchdown, the nose gear collapsed and the airplane slid on its nose for few hundred meters then veered to the right and came to rest. All 81 occupants escaped uninjured while the aircraft was damaged beyond repair. It appears the aircraft was unstable during the last segment.

Crash of a Short SC.7 Skyvan 3 Variant 200 off Das Island

Date & Time: Nov 22, 1976
Type of aircraft:
Operator:
Registration:
A4O-SI
Flight Phase:
Flight Type:
Survivors:
Yes
Schedule:
Bahrain - Abu Dhabi
MSN:
1865
YOM:
1969
Region:
Crew on board:
2
Crew fatalities:
Pax on board:
0
Pax fatalities:
Other fatalities:
Total fatalities:
0
Circumstances:
While cruising over the Persian Gulf on a cargo flight from Bahrain to Abu Dhabi-Al Bateen Airport, the airplane suffered an engine failure. The crew reduced his altitude and ditched the aircraft off Das Island, about 160 km northwest of Abu Dhabi. Both occupants were rescued while the airplane sank and was lost.
Probable cause:
Engine failure for undetermined reasons.

Crash of a Pilatus PC-6/B1-H2 Turbo Porter in Bahrain

Date & Time: Dec 15, 1969
Operator:
Registration:
HB-FCY
Flight Type:
Survivors:
Yes
MSN:
650
YOM:
1967
Country:
Region:
Crew on board:
2
Crew fatalities:
Pax on board:
0
Pax fatalities:
Other fatalities:
Total fatalities:
0
Circumstances:
Crashed in unknown circumstances in Bahrain while on a delivery flight to the operator Borneo Skyways based in Indonesia. The aircraft was written off.

Crash of a Convair CV-340-68 in Dhahran: 11 killed

Date & Time: Jul 8, 1968
Type of aircraft:
Operator:
Registration:
HZ-AAZ
Survivors:
No
Schedule:
Bahrain – Dhahran
MSN:
219
YOM:
1955
Country:
Region:
Crew on board:
3
Crew fatalities:
Pax on board:
8
Pax fatalities:
Other fatalities:
Total fatalities:
11
Circumstances:
While approaching Dhahran Airport, the crew encountered poor weather conditions with sandstorm. Unable to locate the runway, the pilot initiated a go-around and followed a holding pattern. A second attempt to land was made few minutes later but again, the crew was forced to make a go-around due to poor visibility. During the third approach, the aircraft was too low and struck a sand dune located 5 km short of runway and crashed. All 11 occupants were killed.

Crash of a Bristol 253 Britannia C.1 in Aden

Date & Time: Oct 12, 1967
Type of aircraft:
Operator:
Registration:
XL638
Flight Type:
Survivors:
Yes
Schedule:
London - Bahrain - Aden
MSN:
13400
YOM:
1959
Country:
Region:
Crew on board:
0
Crew fatalities:
Pax on board:
0
Pax fatalities:
Other fatalities:
Total fatalities:
0
Circumstances:
After touchdown at Aden-Khormaksar Airport, the four engine airplane encountered difficulties to stop within the remaining distance and overran. It lost its undercarriage and came to rest in shallow water. There were no casualties but the aircraft was written off.
Probable cause:
Failure of the reverse systems after touchdown for undetermined reason.

Crash of an Avro 688 Super Trader 4B on Mt Süphan Dağı: 12 killed

Date & Time: Apr 23, 1959 at 0946 LT
Type of aircraft:
Operator:
Registration:
G-AGRH
Flight Phase:
Flight Type:
Survivors:
No
Site:
Schedule:
London – Ankara – Bahrain
MSN:
1256
YOM:
1945
Country:
Region:
Crew on board:
12
Crew fatalities:
Pax on board:
0
Pax fatalities:
Other fatalities:
Total fatalities:
12
Circumstances:
The four engine aircraft was performing a cargo flight from London to Bahrain with an intermediate stop at Ankara Airport, carrying a crew of 12 and various goods. At 0814LT, the airplane passed over Gemerek at an altitude of 11,500 feet then Elaziğ at 0859LT at 13,500 feet. The crew reported his position over Muş 27 minutes later and the contact was lost at 0946LT. SAR operations were conducted and the wreckage was found six days later on the slope of the Mt Süphan Dağı (4,158 metres high) located to the north of the Van Lake. The airplane disintegrated on impact and all 12 occupants were killed.
Probable cause:
The aircraft, flying on instruments, drifted north of its normal track because of strong winds and crashed into the mountain. Contributing factors were:
- The winds were stronger than forecast,
- An accurate bearing could not be obtained at Muş, and Van had not been checked,
- Sub-normal temperatures would result in a high indicated altimeter reading,
- Calculations on the flight and contacts with beacons were not coordinated and controlled.

Crash of a Beechcraft AT-11 Kansan near Tabriz

Date & Time: Jul 10, 1958
Type of aircraft:
Registration:
N54TA
Flight Phase:
Flight Type:
Site:
Schedule:
Bahrain – Karachi
MSN:
1342
YOM:
1942
Country:
Region:
Crew on board:
0
Crew fatalities:
Pax on board:
0
Pax fatalities:
Other fatalities:
Total fatalities:
0
Circumstances:
Crashed in a mountainous area located in the region of Tabriz while on a ferry flight from Bahrain to Karachi. The occupant's fate remains unknown.