Cape Town - Johannesburg
Flight / Schedule
Cape Town - Johannesburg
Aircraft
Raytheon 390 Premier IRegistration
ZS-CBI
MSN
RB-214
Year of Manufacture
2007
Operator
Multimanaged InvestmentsDate
November 22, 2017 at 04:23 PM
Type
CRASHFlight Type
Private
Flight Phase
Landing (descent or approach)
Crash Site
Airport (less than 10 km from airport)
Crash Location
Johannesburg-Rand Gauteng
Region
Africa • South Africa
Coordinates
-26.3492°, 27.7731°
Crash Cause
Human factor
Narrative Report
On November 22, 2017 at 04:23 PM, Cape Town - Johannesburg experienced a crash involving Raytheon 390 Premier I, operated by Multimanaged Investments, with the event recorded near Johannesburg-Rand Gauteng.
The flight was categorized as private and the reported phase was landing (descent or approach) at a airport (less than 10 km from airport) crash site.
2 people were known to be on board, 0 fatalities were recorded, 2 survivors were identified or estimated. This corresponds to an estimated fatality rate of 0.0%.
Crew on board: 2, crew fatalities: 0, passengers on board: 0, passenger fatalities: 0, other fatalities: 0.
The listed crash cause is human factor. 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.
Aircraft reference details include registration ZS-CBI, MSN RB-214, year of manufacture 2007.
Geospatial coordinates for this crash are approximately -26.3492°, 27.7731°.
Fatalities
Total
0
Crew
0
Passengers
0
Other
0
Crash Summary
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.
Cause: Human factor
Occupants & Outcome
Crew On Board
2
Passengers On Board
0
Estimated Survivors
2
Fatality Rate
0.0%
Known people on board: 2
Operational Details
Schedule / Flight
Cape Town - Johannesburg
Operator
Multimanaged InvestmentsFlight Type
Private
Flight Phase
Landing (descent or approach)
Crash Site
Airport (less than 10 km from airport)
Region / Country
Africa • South Africa
