Zone

Crash of a Boeing 737-4L7 in Johannesburg

Date & Time: Oct 26, 2015 at 1206 LT
Type of aircraft:
Operator:
Registration:
ZS-OAA
Survivors:
Yes
Schedule:
Port Elizabeth - Johannesburg
MSN:
26960/2483
YOM:
1993
Flight number:
BA6234
Country:
Region:
Crew on board:
6
Crew fatalities:
Pax on board:
94
Pax fatalities:
Other fatalities:
Total fatalities:
0
Captain / Total flying hours:
9186
Captain / Total hours on type:
2899.00
Copilot / Total flying hours:
5817
Copilot / Total hours on type:
480
Aircraft flight hours:
57543
Circumstances:
The aircraft Boeing 737-400, operated by Comair, flight number BA6234, was on a scheduled domestic flight operated under the provisions of Part 121 of the Civil Aviation Regulations (CARs). The aircraft was on the third leg for the day, after it had performed two uneventful legs. According to their recorded flight plan, the first leg departed from King Shaka International Airport (FALE) to O.R. Tambo International Airport (FAOR), the second leg was from FAOR to Port Elizabeth International Airport (FAPE) on the same day, during which the Captain was flying. During this third leg, the aircraft departed from FAPE at 0820Z on an instrument flight plan rule for FAOR. On board were six (6) crew members, ninety four (94) passengers and two (2) live animals. The departure from FAPE was uneventful, whereby the first officer (FO) was the flying pilot (FP) for this leg. During the approach to FAOR, the aircraft was cleared for landing on runway 03R. The accident occurred at approximately 1 km past the threshold. The crew stated that a few seconds after a successful touchdown, they felt the aircraft vibrating, during which they applied brakes and deployed the reverse thrust. The vibration was followed by the aircraft rolling slightly low to the left. It later came to a full stop slightly left of the runway centre line, resting on its right main landing gear and the number one engine, with the nose landing gear in the air. The crash alarm was activated by the FAOR Air Traffic Controller (ATC). The Airport Rescue and Fire Fighting (ARFF) personnel responded swiftly to the scene of the accident. The accident site was then secured with all relevant procedures put in place. The aircraft sustained substantial damage as the number one engine scraped along the runway surface when the landing gear detached from the fuselage. ARFF personnel had to prevent an engine fire in which they saw smoke as a result of runway contact. The occupants were allowed to disembark from the aircraft via the left aft door due to the attitude in which the aircraft came to rest. The accident occurred during daylight meteorological conditions on Runway 03R at O.R. Tambo International Airport (FAOR) located at GPS reading as: S 26°08’01.30” E 028°14’32.34” and the field elevation 5558 ft.
Probable cause:
Unstable approach whereby the aircraft was flared too high with high forward speed resulting with a low sink rate in which during touch down the left landing gear
experienced excessive vibration and failed due to shimmy events.
The following findings were identified:
- According to the FDR recordings, the aircraft flare was initiated earlier at 65ft than at 20ft as recommended by aircraft manufacture, which contributed to the low sink rate.
- The shimmy damper failed the post-accident lab-test and fluid was found in the thermal relief valve, which could have contributed to the shimmy damper failure.
- According to the lab results, significant wear was found on the upper torsion link bushing and flange, which could have contributed to undamped vibration
continuation.
- The aircraft had a tailwind component during landing, which could have prolonged the landing distance.
Final Report:

Ground accident of a Boeing 747-436 in Johannesburg

Date & Time: Dec 22, 2013 at 2243 LT
Type of aircraft:
Operator:
Registration:
G-BNLL
Flight Phase:
Survivors:
Yes
Schedule:
Johannesburg – London
MSN:
24054/794
YOM:
1990
Flight number:
BA034
Country:
Region:
Crew on board:
17
Crew fatalities:
Pax on board:
185
Pax fatalities:
Other fatalities:
Total fatalities:
0
Captain / Total flying hours:
20050
Captain / Total hours on type:
12500.00
Copilot / Total flying hours:
5700
Copilot / Total hours on type:
1400
Aircraft flight hours:
110578
Aircraft flight cycles:
12832
Circumstances:
The British Airways aircraft B747-400, flight number BA034 with registration G-BNLL, was going to embark on a commercial international air transportation long haul flight from FAOR to EGLL. The ATC gave the crew instructions to push back, start and face south, then taxi using taxiway Bravo to the Category 2 holding point for Runway 03L. During the taxi, instead of turning to the left to follow Bravo, the crew continued straight ahead, crossing the intersection of taxiway Bravo and aircraft stand taxilane Mike. After crossing the intersection, still being on Mike, the aircraft collided with a building. An investigation was conducted and several causal factors were determined. Amongst others, it was determined that the crew erred in thinking they were still taxiing on Bravo while in fact they were taxiing on Mike. This mistake, coupled with other contributory factors such as the briefing information, taxi information, ground movement visual aids, confusion and loss of situational awareness led to the collision. All 202 occupants evacuated safely while four people in the building were injured. The aircraft was damaged beyond repair.
Probable cause:
The loss of situational awareness caused the crew to taxi straight ahead on the wrong path, crossing the intersection/junction of Bravo and Mike instead of following Bravo where it turns off to the right and leads to the Category 2 holding point. Following aircraft stand taxilane Mike; they collided with a building on the right-hand side of Mike.
Contributory Factors:
- Failure of the crew to carry out a briefing after they had received instruction from ATC that the taxi route would be taxiway Bravo.
- The lack of appropriate knowledge about the taxiway Bravo layout and relevant information (caution notes) on threats or risks to look out for while taxiing on taxiway Bravo en route to the Cat 2 holding point.
- The aerodrome infrastructure problems (i.e. ground movement navigation aids anomalies), which created a sense of confusion during the taxi.
- Loss of situation awareness inside the cockpit causing the crew not to detect critical cues of events as they were gradually unfolding in front of them.
- Failure of the other crew members to respond adequately when the Co-pilot was commenting on the cues (i.e. narrowness and proximity to the building).
- The intersection/junction of Bravo and Mike not being identified as a hotspot area on the charts.
Final Report:

Ground accident of a Boeing 737-2T5 at Hoedspruit AFB

Date & Time: Jan 10, 2011 at 2050 LT
Type of aircraft:
Operator:
Registration:
ZS-SGX
Flight Phase:
Flight Type:
Survivors:
Yes
Schedule:
Hoedspruit - Johannesburg
MSN:
22396/730
YOM:
1981
Country:
Region:
Crew on board:
3
Crew fatalities:
Pax on board:
0
Pax fatalities:
Other fatalities:
Total fatalities:
0
Captain / Total flying hours:
26512
Copilot / Total flying hours:
1300
Copilot / Total hours on type:
1100
Aircraft flight hours:
70094
Circumstances:
The aircraft was flown on a non-scheduled charter flight from O. R. Tambo International Airport to Hoedspruit military aerodrome, where it landed safely and all 97 passengers disembarked. The crew then prepared to return to O. R. Tambo International Airport with no passengers on board. Whilst taxiing to the cleared holding point for takeoff, the pilot switched off the landing lights to avoid blinding an approaching aircraft. As a result, he overshot the turning point in the darkness and found himself at the end of the taxiway with insufficient space to turn around. According to him, he decided to manoeuvre the aircraft out of the "dead end" by turning into the last taxiway, which led to military hangars, and then reversing the aircraft to carry out a 180° turn. This was to be done without external guidance. Whilst reversing the aircraft, the pilot failed to stop it in time, the main wheels rolled off the edge of the taxiway and the aircraft slipped down a steep embankment, coming to rest with the nose-wheel still on the taxiway. The aeroplane was substantially damaged, but no-one was injured.
Probable cause:
Inappropriate decision by the captain to reverse the aircraft at night without external guidance.
Final Report:

Crash of an Airbus A330-202 in Tripoli: 103 killed

Date & Time: May 12, 2010 at 0601 LT
Type of aircraft:
Operator:
Registration:
5A-ONG
Survivors:
Yes
Schedule:
Johannesburg - Tripoli - London
MSN:
1024
YOM:
2009
Flight number:
AAW771
Country:
Region:
Crew on board:
11
Crew fatalities:
Pax on board:
93
Pax fatalities:
Other fatalities:
Total fatalities:
103
Captain / Total flying hours:
17016
Captain / Total hours on type:
516.00
Copilot / Total flying hours:
4216
Copilot / Total hours on type:
516
Aircraft flight hours:
2175
Aircraft flight cycles:
572
Circumstances:
The aircraft was on a schedule flight from O. R. Tambo International Airport - Johannesburg (South Africa) to London, with an intermediate stop at Tripoli international Airport, Libya. The Aircraft took off on May 11th 2010 at 19:25 UTC as flight number 8U771/AAW771. There were three cockpit crew, eight cabin crew, and 93 passengers on board, with fifty thousand kg of fuel during takeoff role and the Aircraft mass was 187,501 kg. During final approach towards runway 09 at Tripoli international Airport, the crew announced go-around and initiated the miss approach procedure with the knowledge and confirmation of Tripoli tower. During the missed approach phase, the Aircraft responded to the crew’s inputs, velocity and altitude increased above the MDA, then the aircraft descended dramatically until collided with the ground about 1,200 meters from the threshold of the runway 09 and 150 meters to the right of its centerline, impact and post impact fire caused complete destruction to the Aircraft. A boy aged 8 was injured while 103 other occupants were killed.
Probable cause:
A final approach carried out in common managed guidance mode should have relieved the crew of their tasks. The limited coordination and cooperation between the two crew members, especially the change into vertical selected guidance mode by the PF, probably led to a lack of a common action plan. The lack of feedback from the 28 April 2010 flight, flown by the same crew on the same aircraft, did not allow them to anticipate the potential risks associated with managing non-precision approaches. The pilots’ performance was likely impaired because of fatigue, but the extent of their impairment and the degree to which it contributed to the performance deficiencies that occurred during the flight cannot be conclusively determined. During the go-around, the crew was surprised not to acquire visual references. On one hand the crew feared exceeding the aircraft’s speed limits in relation to its configuration, and on the other hand they were feeling the effects of somatogravic illusion due to the aircraft acceleration. This probably explains the aircraft handling inputs, mainly nose-down inputs, applied during the go-around. These inputs were not consistent with what is expected in this flight phase. The degraded CRM did not make it possible for either crew member to identify and recover from the situation before the collision with the ground, even when the TAWS warnings were activated close to the ground.
Based on elements from the investigation, the accident resulted from:
- The lack of common action plan during the approach and a final approach continued below the MDA, without ground visual reference acquired.
- The inappropriate application of flight control inputs during a go- around and on the activation of TAWS warnings,
- The lack of monitoring and controlling of the flight path.
These events can be explained by the following factors:
- Limited CRM on approach that degraded during the missed approach. This degradation was probably amplified by numerous radio-communications during the final approach and the crew’s state of fatigue,
- Aircraft control inputs typical in the occurrence of somatogravic perceptual illusions,
- Inappropriate systematic analysis of flight data and feedback mechanism within the AFRIQIYAH Airways.
- Non adherence to the company operation manual, SOP and standard terminology.
In addition, the investigation committee found the following as contributing factors to the accident:
- Weather available to the crew did not reflect the actual weather situation in the final approach segment at Tripoli International Airport.
- In adequacy of training received by the crew.
- Occupancy of tower frequency by both air and ground movements control.
Final Report:

Crash of a Boeing 707-366C in Kinshasa

Date & Time: Apr 26, 2002
Type of aircraft:
Operator:
Registration:
9Q-CKB
Flight Type:
Survivors:
Yes
Schedule:
Johannesburg - Kinshasa
MSN:
19844
YOM:
1968
Region:
Crew on board:
3
Crew fatalities:
Pax on board:
0
Pax fatalities:
Other fatalities:
Total fatalities:
0
Circumstances:
After landing on runway 24 at Kinshasa-N'Djili Airport in poor weather conditions, the aircraft went out of control, veered off runway to the right, lost its right main gear and came to rest few dozen metres further. All three crew members escaped with minor injuries while the aircraft was damaged beyond repair. Weather was poor at the time of the accident with heavy rain falls and crosswinds.

Crash of a Cessna F406 Caravan II in Johannesburg: 3 killed

Date & Time: Nov 2, 2001 at 0320 LT
Type of aircraft:
Registration:
ZS-OIG
Flight Phase:
Flight Type:
Survivors:
No
Schedule:
Johannesburg - Windhoek
MSN:
406-0041
YOM:
1989
Country:
Region:
Crew on board:
2
Crew fatalities:
Pax on board:
1
Pax fatalities:
Other fatalities:
Total fatalities:
3
Captain / Total flying hours:
1956
Captain / Total hours on type:
1001.00
Circumstances:
The aircraft departed Johannesburg International Airport at 0119Z on an international cargo flight to Eros, an aerodrome located on the outskirts of Windhoek the capital of Namibia. There were two pilots and a passenger onboard the aircraft as well a substantial amount of cargo, consisting mainly of express freight parcels and two heavy steel bars approximately 3 metres in length each. The aircraft crashed approximately 106 seconds after commencing its take-off roll, impacting the ground in a left wing low attitude approximately 700 metres South of the threshold of runway 03R at Johannesburg International Airport in a marshy area. All three occupants onboard were fatally injured and the aircraft was destroyed.
Probable cause:
The accident resulted due to a loss of control (aircraft becoming uncontrollable in the pitch and roll axis), which occurred approximately 35 to 40 seconds after lift-off/rotation. It was induced and aggravated by a 16% overload condition as well as the exceedance of the certified aft CG limitation of the aircraft. The investigation revealed that the aircraft was overloaded by approximately 16% 699.6kg). The cargo was not secured, nor was there a seat or a restraining device in the aircraft for the passenger that was onboard the ill-fated flight. The last Mandatory Periodic Inspection prior to the accident was certified on 30 May 2001 at 4 353.1 airframe hours, by AMO No. 273. Since the inspection was certified a further 96.6 hours were flown. The Certificate of Airworthiness for the aircraft was invalid at the time of the accident, as both engines have exceeded their TBO (time between overhaul) by approximately 185 hours.
Final Report:

Crash of an Ilyushin II-18V in Johannesburg

Date & Time: Dec 17, 1997 at 0620 LT
Type of aircraft:
Operator:
Registration:
RA-75554
Flight Phase:
Flight Type:
Survivors:
Yes
Schedule:
Johannesburg - Bujumbura
MSN:
185 0084 04
YOM:
1965
Flight number:
RMY202
Country:
Region:
Crew on board:
3
Crew fatalities:
Pax on board:
1
Pax fatalities:
Other fatalities:
Total fatalities:
0
Aircraft flight hours:
18766
Aircraft flight cycles:
7040
Circumstances:
During the takeoff roll un runway 03L at Johannesburg-Jan Smuts Airport, the pilot-in-command started the rotation but the aircraft failed to respond. The captain decided to reject takeoff and initiated an emergency braking procedure. Unable to stop within the remaining distance, the aircraft overran, struck a concrete block, rolled for 200 metres then lost its left main gear and engine n°1 before coming to rest. All four occupants escaped uninjured while the aircraft was damaged beyond repair.
Probable cause:
It was determined that the total weight of the aircraft was five tons above MTOW while the CofG was too far forward, out of the envelope. In such conditions, the aircraft was not properly configured and a takeoff was impossible.

Crash of a Piaggio P.166S Albatross in Johannesburg

Date & Time: Mar 1, 1997
Type of aircraft:
Registration:
ZS-NJR
Flight Phase:
Flight Type:
Survivors:
Yes
Schedule:
Johannesburg - Port Elizabeth
MSN:
455
YOM:
1973
Country:
Region:
Crew on board:
1
Crew fatalities:
Pax on board:
0
Pax fatalities:
Other fatalities:
Total fatalities:
0
Circumstances:
Shortly after liftoff, while in initial climb, the twin engine aircraft stalled and crashed near the runway end. The pilot was injured and the aircraft was destroyed.
Probable cause:
Loss of control during initial following an engine failure for unknown reasons.

Crash of a Douglas DC-8-55F in Harare

Date & Time: Jan 28, 1996
Type of aircraft:
Operator:
Registration:
Z-WSB
Flight Type:
Survivors:
Yes
Schedule:
Johannesburg - Harare
MSN:
45805
YOM:
1965
Country:
Region:
Crew on board:
5
Crew fatalities:
Pax on board:
0
Pax fatalities:
Other fatalities:
Total fatalities:
0
Circumstances:
Following an uneventful cargo flight from Johannesburg, the crew started the approach to Harare Airport in poor weather conditions with heavy rain falls. After landing on runway 05, the aircraft encountered difficulties and was unable to stop within the remaining distance (runway 05 is 4,750 metres long). It overran, lost its nose gear and came to rest. All five crew members escaped uninjured and the aircraft was damaged beyond repair.
Probable cause:
The following findings were reported:
- Poor weather conditions with heavy rain falls,
- Limited visibility,
- The runway 05 was wet and the braking action was reduced,
- The aircraft suffered aquaplaning,
- The reverse thrust systems were unserviceable on engine n°2 and 4,
- The crew completed the landing without the spoilers being armed,
- The aircraft was not airworthy,
- The crew failed to follow the approach checklist.

Crash of a Piper PA-31-350 Navajo Chieftain in Johannesburg: 2 killed

Date & Time: Jan 26, 1996
Operator:
Registration:
ZS-KBY
Flight Phase:
Flight Type:
Survivors:
No
MSN:
31-7852067
YOM:
1978
Country:
Region:
Crew on board:
2
Crew fatalities:
Pax on board:
0
Pax fatalities:
Other fatalities:
Total fatalities:
2
Circumstances:
Shortly after takeoff from Johannesburg-Oliver Reginald Tambo Airport, while climbing, the twin engine aircraft went out of control and crashed near Boksburg, about 5 km south of the airport. Both occupants were killed.