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 Beechcraft C90A King Air in Mumbai: 5 killed

Date & Time: Jun 28, 2018 at 1315 LT
Type of aircraft:
Operator:
Registration:
VT-UPZ
Flight Type:
Survivors:
No
Site:
Schedule:
Juhu - Juhu
MSN:
LJ-1400
YOM:
1995
Country:
Region:
Crew on board:
2
Crew fatalities:
Pax on board:
2
Pax fatalities:
Other fatalities:
Total fatalities:
5
Circumstances:
Following a technical maintenance, a test flight was scheduled with two engineers and two pilots. The twin engine airplane departed Mumbai-Juhu Airport and the crew completed several manoeuvres over the city before returning. On approach in heavy rain falls, the aircraft went out of control and crashed at the bottom of a building under construction located in the Ghatkopar West district, some 3 km east from Mumbai Intl Airport, bursting into flames. The aircraft was destroyed by impact forces and a post crash fire and all four occupants were killed as well as one people on the ground.

Crash of a McDonnell Douglas MD-83 in Kiev

Date & Time: Jun 14, 2018 at 2040 LT
Type of aircraft:
Operator:
Registration:
UR-CPR
Survivors:
Yes
Schedule:
Antalya - Kiev
MSN:
49946/1898
YOM:
1991
Flight number:
BAY4406
Country:
Region:
Crew on board:
7
Crew fatalities:
Pax on board:
160
Pax fatalities:
Other fatalities:
Total fatalities:
0
Captain / Total flying hours:
11548
Captain / Total hours on type:
5580.00
Copilot / Total flying hours:
12514
Copilot / Total hours on type:
3580
Aircraft flight hours:
43105
Aircraft flight cycles:
46810
Circumstances:
On June 14, 2018, according to the flight assignment, BAY 4406 charter flight en-route Antalya - Kyiv (Zhulyany) on MD-83 aircraft, state and registration number UR-CPR of Bravo Airways, was operated by PIC, co-pilot and five flight attendants. According to PIC’s Statement, the flight was delayed by 6 hours (departure time - 03:30 pm.) The Investigation Team did not establish the departure time from Antalya Airport. According to the PIC, the crew arrived at the airport at 02:00 pm. The takeoff time was 03:41 pm. The airline said the flight was delayed because of the aircraft non-arrival. Bravo Airways is the aircraft operator responsible for the flight and technical operation of the aircraft, maintaining its airworthiness and ensuring the flight safety. The Pilot Flying duties were performed by the PIC, and the Pilot Monitoring was the co-pilot. In accordance with the flight assignment, the PIC cross checked the copilot. According to his Statement, the flight preparation of the crew was carried out one and a half hours before the actual departure at Antalya Airport (PIC received aeronautical and meteorological information from a representative of Turkish Ground Services), after which, the PIC took a decision to perform the flight. Climb and level flight were performed in a normal mode. Landing approach was carried out to RW08 in the conditions of thunderstorm activity with ILS system. At 05:40 pm, at landing on the aerodrome of the Kyiv International Airport (Zhulyany) (hereinafter – Kyiv (Zhulyany) Aerodrome), during the landing run, at the distance of 1260 m from the entrance threshold, the aircraft suffered a runway excursion to the left of the air strip and stopped outside the cleared and graded area of the air strip at the distance of 123 m from the runway center line (according to the tire footprints at the occurrence site.) As a result of the accident, the aircraft has sustained substantial damage, in particular, to the structural elements. None of passengers or crew members received serious injuries.
Probable cause:
The cause of the accident, i.e. runway excursion of MD-83 UR-CPR aircraft operated by Bravo Airways, which took place on June 14, 2018 at the Kyiv (Zhulyany) Aerodrome at performance of flight BAY 4406 en-route Antalya-Kyiv (Zhulyany) – was the PIC’s decision to continue the landing at the Kyiv (Zhulyany) Aerodrome in the thunderstorm conditions with the following main factors:
- non-stabilized approach for landing, starting from the height of 1,000 feet;
- spoiler non-deployment by the crew;
- incorrect crew actions in application of the reverse thrust on a wet runway (EPR>1.3).
Contributing Factors:
- Air traffic control service in the classified airspace of Ukraine, which is required by the Order of the Ministry of Transport of Ukraine dated April 16, 2003, No. 293, was not provided to the crew in full;
- Wind variable in strength and direction;
- Probably, the crew’s failure to listen to the latest ATIS reports for the Kyiv (Zhulyany) Aerodrome;
- Bravo Airways Operator's Manual does not contain landing approach procedures;
- Low-quality pre-flight preparation, pre-landing preparation, checklist reading and completion at all flight stages.
Final Report:

Crash of a Cessna 525 CitationJet CJ2+ in Saint-Tropez

Date & Time: Jun 6, 2018 at 1310 LT
Type of aircraft:
Operator:
Registration:
D-IULI
Flight Type:
Survivors:
Yes
Schedule:
Figari - Saint-Tropez
MSN:
525A-0514
YOM:
2013
Country:
Region:
Crew on board:
1
Crew fatalities:
Pax on board:
1
Pax fatalities:
Other fatalities:
Total fatalities:
0
Captain / Total flying hours:
2500
Captain / Total hours on type:
1234.00
Circumstances:
The aircraft departed Figari-Sud-Corse Airport on a positioning flight to Saint-Tropez-La Môle, carrying one passenger and one pilot. Weather conditions at destination were poor with ceiling at 1,800 feet and rain. The pilot contacted Nice Approach and was cleared to descend to 6,000 feet and to report over EM for an approach to La Môle Airport Runway 24. On final approach, the pilot was unable to establish a visual contact with the runway and initiated a go-around procedure. Few minutes later, he completed a second approach and landed the airplane 200 metres past the runway threshold at a speed of 136 knots. Spoilers were deployed but the airplane was unable to stop within the remaining distance. It veered slightly to the left, departed the end of the runway, crossed a river and came to rest against an embankment located about 100 metres past the runway end. The pilot escaped unhurt while the passenger was slighlty injured. The aircraft was damaged beyond repair.
Probable cause:
The landing distance of the airplane on a wet runway as defined in the Airplane Flight Manual (AFM) performance tables are not compatible with the length of runway available at La Môle Aaerodrome. When preparing the flight, the pilot used the flight record provided by the operator ProAir to determine landing performance. Landing distance on a wet runway presented in the file increased that on a dry runway by 15%. The 15% increase on a wet runway can only be used in conjunction with the increase of 60% imposed in commercial operation, otherwise it may be inappropriate. The value resulting from the calculation was, in this case, wrong and less than the value indicated in the aircraft flight manual. The pilot probably did not use the EFB application for the calculation of performance or the flight manual to verify this value. The pilot thus undertook the flight on the basis of erroneous performance values, without realizing that he could not land at this aerodrome if the runway was wet. In addition, during the final approach, the speed of the aircraft was greater than the speed approach reference and the approach slope was also greater than the nominal slope, which resulted in an increase in the landing distance. During the landing roll, the aircraft exited the runway longitudinally at a speed of 41 kt. The pilot failed to stop the aircraft until it does not violently collide with obstacles at the end of the track.
Contributing factors:
- The operator's use of the same operations manual for two different types of operations;
- The absence in the operations manual of a calculation method, coefficient and safety margin for the calculation of performance in non-commercial transport;
- Lack of knowledge by the pilot and the operator of the method of calculation of landing performance in non-commercial transport;
- The lack of indication in the operations manual that the landing performances at La Môle aerodrome are limiting in case of a wet or contaminated runway.
Final Report:

Crash of a Partenavia P.68B Victor on Endelave Island

Date & Time: Jun 3, 2018 at 1422 LT
Type of aircraft:
Operator:
Registration:
D-GATA
Flight Type:
Survivors:
Yes
Schedule:
Rendsburg - Endelave Island
MSN:
82
YOM:
1977
Country:
Region:
Crew on board:
1
Crew fatalities:
Pax on board:
3
Pax fatalities:
Other fatalities:
Total fatalities:
0
Captain / Total flying hours:
950
Captain / Total hours on type:
70.00
Aircraft flight hours:
3260
Circumstances:
The accident occurred during a private VFR flight from EDXR (Rendsburg-Schachtholm) to Endelave (EKEL). When arriving overhead EKEL, the pilot made a visual inspection of the airstrip conditions. Upon a low approach at a shallow angle to runway 29 at EKEL, the pilot on short final reduced engine power and initiated the flare. Approximately 10 meters in front of the beginning of runway 29, the aircraft landed in a wheat field, and the main landing gear touched down at and collided with an upslope roadside next to a road crossing perpendicularly to the beginning of runway 29. When colliding with the upslope roadside, the left main landing gear collapsed. The aircraft started veering uncontrollably to the left and ran off the side of the airstrip. In the grass parking area next to the airstrip, the left wing of the aircraft collided with the nose landing gear of a parked aircraft. The aircraft continued veering to the left, impacted with a tree and a farm building, and came to rest. After impact with the tree and the farm building, the aircraft caught an explosive fire. Witnesses observing the landing and the impact with the tree and the farm building initiated a rescue mission. The aircraft was totally destroyed by a post crash fire and all four occupants were injured.
Probable cause:
An undershoot landing and touchdown at an upslope roadside next to a road crossing perpendicularly to the beginning of runway 29 resulted in a left main landing gear collapse. The aircraft uncontrollably veered to the left, ran off the side of the airstrip, collided with a parked aircraft, and impacted with a tree and a farm building. The aircraft caught an explosive fire. The resolute actions by witnesses and the local community in combination with an effective rescue mission were the difference between fatal and serious injuries.
Final Report:

Crash of a Lockheed C-130H Hercules in Biskra: 1 killed

Date & Time: Jun 3, 2018
Type of aircraft:
Operator:
Registration:
7T-WHT
Survivors:
Yes
Schedule:
Biskra - Biskra
MSN:
4911
YOM:
1981
Location:
Country:
Region:
Crew on board:
9
Crew fatalities:
Pax on board:
0
Pax fatalities:
Other fatalities:
Total fatalities:
1
Circumstances:
Following an uneventful paratroopers mission over the area of Biskra, the crew was returning to Biskra-Mohamed Khider Airport. On final approach, the airplane stalled and crashed few hundre metres short of runway, coming to rest broken in two. All nine crew members were injured and the aircraft was destroyed. A day later, one of the survivor died from his injuries.

Crash of a Piper PA-31-350 Navajo Chieftain off Amagansett: 4 killed

Date & Time: Jun 2, 2018 at 1433 LT
Registration:
N41173
Flight Type:
Survivors:
No
Schedule:
Newport – East Hampton
MSN:
31-8452017
YOM:
1984
Crew on board:
1
Crew fatalities:
Pax on board:
3
Pax fatalities:
Other fatalities:
Total fatalities:
4
Captain / Total flying hours:
3000
Aircraft flight hours:
5776
Circumstances:
The commercial pilot of the multiengine airplane was the first of a flight of two airplanes to depart on the cross-country flight, most of which was over the Atlantic Ocean. The pilot of the second airplane stated that he and the accident pilot reviewed the weather for the route and the destination before departing; however, there was no record of the accident pilot receiving an official weather briefing and the information the pilots accessed before the flight could not be determined. The second pilot departed and contacted air traffic control, which advised him of thunderstorms near the destination; he subsequently altered his route of flight and landed uneventfully at the destination. The second pilot stated that he did not hear the accident pilot on the en route air traffic control frequency. Two inflight weather advisories were issued for the route and the area of the destination about 42 and 15 minutes before the accident flight departed, respectively, and warned of heavy to extreme precipitation associated with thunderstorms. It could not be determined whether the accident pilot received these advisories. Review of air traffic control communications and radar data revealed that, about 5 miles from the destination airport, the pilot of the accident airplane reported to the tower controller that he was flying at 700 ft and "coming in below" the thunderstorm. There were no further communications from the pilot. The airplane's last radar target indicated 532 ft about 2 miles south of the shoreline. The airplane was found in about 50 ft of water and was fragmented in several pieces. Postaccident examination revealed no preimpact anomalies with the airplane or engines that would have precluded normal operation. A local resident about 1/2 mile from the accident site took several photos of the approaching thunderstorm, which documented a shelf cloud and cumulus mammatus clouds along the leading edge of the storm, indicative of potential severe turbulence. Review of weather imagery and the airplane's flight path showed that the airplane entered the leading edge of "extreme" intensity echoes with tops near 48,000 ft. Imagery also depicted heavy to extreme intensity radar echoes over the accident site extending to the destination airport. It is likely that the pilot encountered gusting winds, turbulence, restricted visibility in heavy rain, and low cloud ceilings in the vicinity of the accident site and experienced an in-flight loss of control at low altitude. Such conditions are conducive to the development of spatial disorientation; however, the reason for the pilot's loss of control could not be determined based on the available information.
Probable cause:
The pilot's decision to fly under a thunderstorm and a subsequent encounter with turbulence and restricted visibility in heavy rain, which resulted in a loss of control.
Final Report:

Crash of a Piper PA-46-310P Malibu in Prescott

Date & Time: May 29, 2018 at 2115 LT
Registration:
N148ME
Flight Type:
Survivors:
Yes
Site:
Schedule:
Santa Ana – Prescott
MSN:
46-8608009
YOM:
1986
Crew on board:
1
Crew fatalities:
Pax on board:
2
Pax fatalities:
Other fatalities:
Total fatalities:
0
Captain / Total flying hours:
3100
Captain / Total hours on type:
3.00
Circumstances:
According to the pilot, about 15 minutes before reaching the destination airport during descent, the engine lost power. The pilot switched fuel tanks, and the engine power was momentarily restored, but the engine stopped producing power even though he thought it "was still running all the way to impact." The pilot conducted a forced landed on a highway at night, and the right wing struck an object and separated from the airplane. The airplane came to rest inverted. According to the Federal Aviation Administration (FAA) aviation safety inspector (ASI) that performed the postaccident airplane examination, the fuel lines to the fuel manifold were dry, and the fuel manifold valves were dry. He reported that the fuel strainer, the diaphragm, and the fuel filter in the duel manifold were unremarkable. Fuel was found in the gascolator. The FAA ASI reported that, during his interview with the pilot, "the pilot changed his story from fuel exhaustion, to fuel contamination." The inspector reported that there were no signs of fuel contamination during the examination of the fuel system. According to the fixed-base operator (FBO) at the departure airport, the pilot requested 20 gallons of fuel. He then canceled his fuel request and walked out of the FBO.
Probable cause:
The pilot's improper fuel planning, which resulted in fuel exhaustion and the subsequent total loss of engine power.
Final Report:

Crash of a Swearingen SA227AC Metro III in Saltillo

Date & Time: May 24, 2018
Type of aircraft:
Operator:
Registration:
XA-UPP
Flight Type:
Survivors:
Yes
Schedule:
Saltillo - Saltillo
MSN:
AC-736
YOM:
1989
Country:
Crew on board:
3
Crew fatalities:
Pax on board:
0
Pax fatalities:
Other fatalities:
Total fatalities:
0
Circumstances:
The crew was completing a training flight at Saltillo-Plan de Guadalupe Airport. After touchdown on runway 17, the airplane veered off runway to the left, lost its right main gear and came to rest about 600 metres from the runway threshold. All three crew members evacuated safely and the aircraft was damaged beyond repair.

Crash of a Gulfstream G200 in Tegucigalpa

Date & Time: May 22, 2018 at 1119 LT
Type of aircraft:
Operator:
Registration:
N813WM
Survivors:
Yes
Schedule:
Austin – Tegucigalpa
MSN:
54
YOM:
2001
Country:
Crew on board:
2
Crew fatalities:
Pax on board:
4
Pax fatalities:
Other fatalities:
Total fatalities:
0
Captain / Total flying hours:
5400
Aircraft flight hours:
5299
Circumstances:
On final approach to runway 02, the copilot informed the captain about the fact that the approach speed was too high by 20 knots to the reference speed. The captain replied he would correct this but the airplane landed too far down runway 02, about 993 metres before the end of the runway which is 2,010 metres long but with a displaced threshold, giving a landing distance available of 1,700 metres. Upon touchdown, the aircraft's speed was 142 knots, about 14 knots above the speed reference according to existing conditions and weight and balance. Unable to stop within the remaining distance, the airplane overran, went down an embankment, crossed a road and came to rest against a second embankment, broken in two. All six occupants were slightly injured and the aircraft was destroyed. Owned by TVPX, it was operated by Silver Air.
Probable cause:
The accident was the consequence of the followings:
- The crew completed an approach at a speed higher than the reference speed for weight and balance specified in the aircraft checklist,
- Lack of specific information on the length of the runway at Toncontín International Airport by the crew for the approach to runway 02, when landing almost halfway down the runway leaving little distance for effective braking of the systems,
- A late activation of the thrust reverser systems about 0:13 seconds after touchdown was considered as a contributing factor,
- Existing weather conditions were not considered as a contributing factor.
Final Report: