Region

Crash of a Pilatus PC-6/B2-H4 Turbo Porter in Johannesburg: 5 killed

Date & Time: Aug 30, 2022 at 1400 LT
Operator:
Registration:
ZS-NIT
Flight Phase:
Survivors:
Yes
Schedule:
Johannesburg - Johannesburg
MSN:
896
YOM:
1993
Country:
Region:
Crew on board:
1
Crew fatalities:
Pax on board:
5
Pax fatalities:
Other fatalities:
Total fatalities:
5
Circumstances:
Crashed shortly after liftoff from Johannesburg-Rand Airport. All five passengers were killed and the pilot was injured.

Crash of a Cessna S550 Citation S/II in Friemersheim: 3 killed

Date & Time: Jan 23, 2020 at 1050 LT
Type of aircraft:
Operator:
Registration:
ZS-CAR
Flight Phase:
Flight Type:
Survivors:
No
Site:
Schedule:
George - George
MSN:
S550-0078
YOM:
1985
Country:
Region:
Crew on board:
3
Crew fatalities:
Pax on board:
0
Pax fatalities:
Other fatalities:
Total fatalities:
3
Captain / Total flying hours:
5215
Captain / Total hours on type:
1315.00
Copilot / Total flying hours:
1061
Copilot / Total hours on type:
265
Aircraft flight hours:
10106
Circumstances:
A Cessna S550 Citation S/II of the South African Civil Aviation Authority crashed into the Outeniqua mountains, near the town of Friemersheim. The three occupants were killed and the aircraft was destroyed. The Citation departed Port Elizabeth Airport (FAPE) on a positioning flight to George Airport (FAGG). On approach to FAGG, the flying crew requested to carry out a calibration flight for the very high frequency omnidirectional range (VOR) beacon at FAGG. Due to inclement weather conditions at the time, they were not cleared to conduct VOR calibration. As a result, they decided to land and refuel the aircraft before commencing with the calibration of the Instrument Landing System (ILS) on runway 11 at FAGG. The flying crew requested take-off from runway 11 and an early right turn to intercept radial 250°, 17 nautical miles (nm) DME arc to radial 330° at 3000 feet (ft) climbing to 4,000 feet. The air traffic control (ATC) granted their request. Radar data indicated that at 10:42, the aircraft took off from runway 11 and, once airborne, made a right-hand turn to intercept radial 250° using the George VOR (GRV VOR). The aircraft climbed to 3000ft. Once the aircraft reached 17 nm on the DME from the GRV VOR (DME is co-located with the VOR), it commenced with a right-hand turn to intercept radial 330° while maintaining 17nm DME arc. At 10:46, the ATC at FAGG advised the flying crew that they were now exiting controlled airspace and were advised to broadcast on the special rules frequency. The crew acknowledged the advisory to change frequency and there was no further communication. The aircraft was still being monitored by ATC using secondary surveillance radar. At 10:50, radar data showed the aircraft crossing radial 310° and entered a climb from 3000ft, reaching 3,900 feet. As the aircraft levelled off at 3,900 feet, a rapid descent occurred, and the aircraft lost 1500ft in approximately 9 seconds. Three seconds prior to impact, the aircraft nose pitched up before impacting a ridge at 2,192 feet. The aircraft was destroyed and all three occupants were killed.
Probable cause:
The crew lost control of the aircraft which resulted in significant loss of altitude; as they attempted to recover, they collided with the mountain. According to the SAWS report, there was significant cloud coverage below 1,500 feet above ground level at the time of the accident as observed in the METARs. Mountain tops were obscured as seen on the webcam. The aircraft route which is 17 NM arc passes over the obscured mountains. From the limited FDR reading the aircraft attitude drastically changed into an unusual attitude when approaching the mountain area. This indicates that most probably, the pilot has entered an unusual attitude during transition from VFR to IFR flight without preparation. The accident flight plan was VFR.
The following contributing factor were identified:
- The presence of low clouds at about 1,500 feet above ground and obscured mountains with clouds,
- The incapability of the crew to recover from unusual attitude,
- Lack of supervision and disregard of the Civil Aviation Regulations requirements by the FIU (operator),
- Overbanked and steep dive maneuver, unable to gain the required altitude before impact,
- Lack of upset prevention and recovery technique (UPRT).
Final Report:

Crash of a Convair CV-340 in Pretoria: 1 killed

Date & Time: Jul 10, 2018 at 1639 LT
Type of aircraft:
Operator:
Registration:
ZS-BRV
Flight Type:
Survivors:
Yes
Schedule:
Pretoria - Sun City
MSN:
215
YOM:
1954
Country:
Region:
Crew on board:
3
Crew fatalities:
Pax on board:
17
Pax fatalities:
Other fatalities:
Total fatalities:
1
Captain / Total flying hours:
18240
Captain / Total hours on type:
63.00
Copilot / Total flying hours:
19616
Aircraft flight hours:
18115
Circumstances:
On Tuesday 10 July 2018, at approximately 1439Z, two crew members and 17 passengers took off on a ZS-BRV aircraft for a scenic flight from Wonderboom Aerodrome (FAWB) destined for Pilanesberg Aerodrome (FAPN) when the accident occurred. During take-off, the left engine caught fire, however, the crew continued with the flight. They declared an emergency by broadcasting ‘MAYDAY’ and requesting to return to the departure aerodrome. The crew turned to the right with the intention of returning to the aerodrome. However, the left engine fire intensified, causing severe damage to the left wing rear spar and left aileron system, resulting in the aircraft losing height and the crew losing control of the aircraft and colliding with power lines, prior to crashing into a factory building. The footage taken by one of the passengers using their cellphone showed flames coming from the front top side of the left engine cowling and exhaust area after take-off. The air traffic control (ATC) on duty at the time of the accident confirmed that the left engine had caught fire during take-off and that the crew had requested clearance to return to the aerodrome. The ATC then activated the crash alarm and the aircraft was prioritized for landing. During the accident sequence that followed, one passenger (engineer) occupying the jump seat in the cockpit was fatally injured and 18 others sustained injuries. The investigation revealed that during take-off, the left engine had caught fire and the crew had continued with the flight without securing the left engine as prescribed in the aircraft flight manual (AFM). The crew had then declared an emergency and attempted to return to the aerodrome, however, they lost control of the aircraft and collided with power lines prior to crashing into a factory building. Owned by Rovos Air (part of the South African Rovos Rail Group), the aircraft was donated to the Dutch Museum Aviodrome based in Lelystad and has to be transferred to Europe with a delivery date on 23 July 2018. For this occasion, the aircraft was repaint with full Martin's Air Charter colorscheme. Part of the convoy program to Europe, the airplane was subject to several test flights, carrying engineers, technicians, pilots and also members of the Aviodrome Museum.
Probable cause:
During take-off, the left engine caught fire and the crew continued with the flight without securing the left engine as prescribed in the aircraft flight manual (AFM). The crew declared an emergency and attempted to return to the aerodrome, however, they lost control of the aircraft and collided with power lines prior to crashing into a factory building. The following contributing factors were reported:
- Pre-existing damage to the cylinder No 13 piston and ring pack deformation and, most probably, the cylinder No 7’s fractured exhaust valve head that were not detected during maintenance of the aircraft,
- Substandard maintenance for failing to conduct compression tests on all cylinders during the scheduled maintenance prior to the accident,
- Misdiagnosis of the left engine manifold pressure defect as it was reported twice prior to the accident,
- The crew not aborting take-off at 50 knots prior to reaching V1; manifold pressure fluctuation was observed by the crew at 50 knots and that should have resulted in an aborted take-off,
- Lack of crew resource management; this was evident as the crew ignored using the emergency checklist to respond to the in-flight left engine fire,
- Lack of recency training for both the PF and PM, as well as the LAME,
- Non-compliance to Civil Aviation Regulations by both the crew and the maintenance organisation.
Final Report:

Crash of a Raytheon 390 Premier I in Johannesburg

Date & Time: Nov 22, 2017 at 1623 LT
Type of aircraft:
Registration:
ZS-CBI
Flight Type:
Survivors:
Yes
Schedule:
Cape Town - Johannesburg
MSN:
RB-214
YOM:
2007
Country:
Region:
Crew on board:
2
Crew fatalities:
Pax on board:
0
Pax fatalities:
Other fatalities:
Total fatalities:
0
Captain / Total flying hours:
3048
Captain / Total hours on type:
649.00
Copilot / Total flying hours:
4718
Copilot / Total hours on type:
305
Aircraft flight hours:
963
Circumstances:
On 22 November 2017, the pilot-in-command (PIC) accompanied by the first officer (FO) took off from the Cape Town International Airport (FACT) on a private flight to the Rand Airport (FAGM). The flight was conducted under instrument flight rules (IFR) by day and the approach was conducted under visual flight rules (VFR). The PIC was the pilot flying (PF) and was seated on the left seat and the FO was occupying the right seat. The air traffic controller (ATC) on duty at FAGM tower stated that the FO reported in-bound for a fullstop landing at FAGM. The last wind direction data for Runway 29 was transmitted to the FO as 230°/11 knots (kts) and Query Nautical Height (QNH): 1021. The FO acknowledged the transmission and the crew elected to land on Runway 11. The PIC stated that the approach for landing was stable and that the touchdown was near the first taxiway exit point. According to the FO, the aircraft floated for a while before touchdown. This was confirmed during the investigation. During the landing rollout, the PIC applied the brakes and the brakes responded for a short while, however, the aircraft continued to roll without slowing down. At approximately 300 metres (m) beyond the intersection of Runway 35 and Runway 11, the PIC requested the FO to apply emergency brakes. The FO applied the emergency brakes gradually and the aircraft continued to roll before the brakes locked and the tyres burst. The aircraft skidded on the main wheels and continued for approximately 180m until it overshot the runway. The undercarriage went over a ditch of approximately 200 millimetres in depth at the end of the runway into the soft ground and the aircraft came to a stop approximately 10m from the threshold facing slightly left off the extended centre line Runway 11. The aircraft was substantially damaged during the impact sequence and none of the occupants sustained injuries. The crash alarm was activated by the tower and the fire services responded to the scene.
Probable cause:
The investigation revealed that the aircraft was unstable on approach (hot and high), resulting in deep landing, probably near the second exit point, leading to a runway excursion. Contributing factors were attributed to the lift dumps not being deployed and the incorrect application of the emergency brakes.
Final Report:

Crash of a Cessna (DMI) Falcon 402 in Lanseria

Date & Time: Dec 13, 2016 at 1530 LT
Type of aircraft:
Registration:
ZU-TVB
Flight Type:
Survivors:
Yes
Schedule:
Lanseria - Bazaruto Island
MSN:
402B-1008
YOM:
1975
Country:
Region:
Crew on board:
1
Crew fatalities:
Pax on board:
2
Pax fatalities:
Other fatalities:
Total fatalities:
0
Circumstances:
Shortly after takeoff from Lanseria Airport Runway 07, en route to Bazaruto Island in Mozambique, the pilot encountered engine problems. He contacted ATC and was cleared for an immediate return and landing on runway 25. On short final, the single engine airplane hit the perimeter fence and crashed near the runway threshold, bursting into flames. All three occupants were injured and the aircraft was destroyed by a post crash fire. Built in 1975, this Cessna 402B was equipped with a new turbo engine and redesigned as a single engine Cessna (DMI) Falcon 402 (the C402 is usually a twin engine aircraft).

Crash of a Cessna 208 Caravan I at Langebaanweg AFB

Date & Time: Mar 3, 2016
Type of aircraft:
Operator:
Registration:
3004
Flight Phase:
Flight Type:
Survivors:
Yes
Schedule:
Langebaanweg - Langebaanweg
MSN:
208-0130
YOM:
1988
Country:
Region:
Crew on board:
2
Crew fatalities:
Pax on board:
0
Pax fatalities:
Other fatalities:
Total fatalities:
0
Circumstances:
The crew was completing a local night training exercice at Langebaanweg AFB. While completing various manoeuvres, the airplane went out of control and crashed in an open field located near airbase, coming to rest upside down. The aircraft was destroyed and both pilots were injured.

Crash of an Eclipse EA500 near Swellendam: 1 killed

Date & Time: Dec 7, 2015 at 1057 LT
Type of aircraft:
Registration:
ZS-DKS
Flight Phase:
Flight Type:
Survivors:
No
Schedule:
Lanseria - Cape Town
MSN:
142
YOM:
2008
Country:
Region:
Crew on board:
1
Crew fatalities:
Pax on board:
0
Pax fatalities:
Other fatalities:
Total fatalities:
1
Captain / Total flying hours:
2977
Captain / Total hours on type:
506.00
Aircraft flight hours:
714
Circumstances:
The aircraft had taken off on a private flight with the pilot being the sole occupant on board. The pilot had filed an IFR flight plan and had informed air traffic control (ATC) at FALA that the aircraft had a fuel endurance of 4 hours and his estimated flying time to FACT was approximately 2 hours and 30 minutes. After take-off the aircraft climbed to its cruising altitude of 36 000 feet (FL360) as was seen on the radar recordings. The pilot maintained communication with ATC until overhead Kimberley. Shortly thereafter the aircraft was observed to change course, turning slightly left before the town of Douglas. The aircraft remained at FL360 and was observed to fly south towards the waypoint OKTED, which was a substantial distance to the east of FACT. FACT could not get communication with the aircraft and the aeronautical rescue co-ordination centre (ARCC) was advised of the situation. The aircraft was kept under constant radar surveillance. The ARCC requested assistance from the South African Air Force (SAAF) and a Gripen (military jet) from Air Force Base Overberg (FAOB) was dispatched to intercept the aircraft. The pilot of the Gripen intercepted the aircraft approximately 3 minutes before it impacted the terrain. The Gripen pilot was unable to get close enough to the aircraft as it was flying very erratically, and he could therefore not see whether the pilot was conscious or not. The aircraft was observed entering a left spiral and continue spiraling down until it impacted the ground. The pilot was fatally injured and the aircraft was destroyed during the impact sequence.
Probable cause:
The investigation revealed no anomalies on the part of the aircraft and all damage was attributed to the impact with the ground. The fatal injuries sustained by the pilot made it impossible to determine if the pilot was incapacitated or not. It was observed that the aircraft performed a series of unexplainable as well as erratic flying manoeuvres, which resulted in a loss of control and the aircraft to enter into a spiral dive, which was observed by the Gripen pilot before colliding with the ground.
Final Report:

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:

Crash of a Cessna 441 Conquest II in Cape Town: 5 killed

Date & Time: Aug 16, 2015 at 0629 LT
Type of aircraft:
Operator:
Registration:
V5-NRS
Flight Type:
Survivors:
No
Site:
Schedule:
Oranjemund - Cape Town
MSN:
441-0288
YOM:
1983
Country:
Region:
Crew on board:
2
Crew fatalities:
Pax on board:
3
Pax fatalities:
Other fatalities:
Total fatalities:
5
Captain / Total flying hours:
6353
Captain / Total hours on type:
1357.00
Copilot / Total flying hours:
1394
Copilot / Total hours on type:
1
Aircraft flight hours:
7605
Circumstances:
On 15 August 2015 at 2351Z a Cessna 441 aeroplane, with two crew and a paramedic on board took off from Eros Airport (FYWE) on a medical evacuation flight with their intended final destination Cape Town International Airport (FACT). The aircraft landed at Oranjemund (FYOG) to pick up a male patient and his daughter. At 0206Z the aircraft departed from FYOG on a mercy flight to FACT. At 0343Z the aircraft made the first contact with FACT area and the aircraft was put under radar control. At 0355Z, area control advised the crew that there was a complete radar failure. The aircraft was on a descent to 6500 ft when approach advised them to prepare for a VOR approach for runway 19. At 0429Z, while on approach for landing at FACT, all contact was lost with the aircraft. At approximately 0556Z the aircraft’s wreckage was located approximately 8 nm to the north of FACT. All five occupants on board were fatally injured and the aircraft was destroyed by impact and post impact fire. The investigation revealed the aircraft collided with terrain during instrument meteorological condition (IMC) conditions while on the VOR approach for Runway 19 at FACT. At the time the ILS was working, however the approach controller offered a VOR approach for separation with an outbound aircraft as the radar was unserviceable.
Probable cause:
The aircraft collided with terrain during instrument meteorological flight conditions while on the VOR approach Runway 19.
Final Report:

Crash of a Cessna 208 Caravan I Near Lydenburg: 3 killed

Date & Time: Jun 17, 2014 at 1030 LT
Type of aircraft:
Operator:
Registration:
3006
Flight Phase:
Flight Type:
Survivors:
Yes
Site:
Schedule:
Sabi Sabi - Lydenburg
MSN:
208-00136
YOM:
1988
Country:
Region:
Crew on board:
2
Crew fatalities:
Pax on board:
3
Pax fatalities:
Other fatalities:
Total fatalities:
3
Circumstances:
The single engine aircraft was completing a training flight from Sabi Sabi to Lydenburg on behalf of the 41st Squadron. While descending to Lydenburg, the aircraft crashed in a mountainous area near the Long Tom Pass. Two passengers were seriously injured while three other occupants were killed.