Crash of an Embraer EMB-120 Brasilía in Moscow

Date & Time: Jul 31, 2015 at 1810 LT
Type of aircraft:
Operator:
Registration:
VQ-BBX
Survivors:
Yes
Schedule:
Ulyanovsk - Moscow
MSN:
120-205
YOM:
1990
Flight number:
7R226
Country:
Region:
Crew on board:
3
Crew fatalities:
Pax on board:
28
Pax fatalities:
Other fatalities:
Total fatalities:
0
Circumstances:
Following an uneventful flight from Ulyanovsk, the crew started the descent to Moscow-Domodedovo Airport. While following the approach checklist, the crew realized that the nose gear failed to deploy and remained stuck in its wheel well. Several attempts to lower the gear manually failed and the crew eventually decided to carry out a nose gear-up landing on runway 32L. After a holding circuit of about 45 minutes, the aircraft landed then slid on its nose for few dozen metres before coming to rest. All 31 occupants evacuated safely and the aircraft was damaged beyond repair.

Crash of an Embraer EMB-505 Phenom 300 in Blackbushe: 4 killed

Date & Time: Jul 31, 2015 at 1508 LT
Type of aircraft:
Registration:
HZ-IBN
Flight Type:
Survivors:
No
Schedule:
Milan - Blackbushe
MSN:
505-00040
YOM:
2010
Region:
Crew on board:
1
Crew fatalities:
Pax on board:
3
Pax fatalities:
Other fatalities:
Total fatalities:
4
Captain / Total flying hours:
11000
Captain / Total hours on type:
1180.00
Aircraft flight hours:
2409
Aircraft flight cycles:
1377
Circumstances:
The aircraft had positioned to Milan earlier in the day, flown by the same pilot, and was returning to Blackbushe with the pilot and three passengers on board. After descending through the London Terminal Manoeuvring Area (TMA) it was handed over from London Control to Farnborough Approach. Its descent continued towards Blackbushe and, having reported that he had the airfield in sight, the pilot was instructed to descend at his own discretion. When the aircraft was approximately four miles south of its destination, he was instructed to contact Blackbushe Information. The weather at Blackbushe was fine with light and variable winds, visibility in excess of ten kilometres, and no low cloud. HZ-IBN entered the left-hand circuit for Runway 25 via the crosswind leg. Towards the end of the downwind leg, it overtook an Ikarus C42 microlight aircraft, climbing to pass ahead of and above that aircraft. As the climb began, at approximately 1,000 ft aal, the TCAS of HZ-IBN generated a ‘descend’ RA alert to resolve a conflict with the microlight. The TCAS RA changed to ‘maintain vertical speed’ and then ‘adjust vertical speed’, possibly to resolve a second conflict with a light aircraft which was above HZ-IBN and to the east of the aerodrome. Neither the microlight nor the light aircraft was equipped with TCAS. Following this climb, HZ-IBN then flew a curving base leg, descending at up to 3,000 feet per minute towards the threshold of Runway 25. The aircraft’s TCAS annunciated ‘clear of conflict’ when HZ-IBN was 1.1 nm from the runway threshold, at 1,200 ft aal, and at a speed of 146 KIAS, with the landing gear down and flap 3 selected. The aircraft continued its approach at approximately 150 KIAS. Between 1,200 and 500 ft aal the rate of descent averaged approximately 3,000 fpm, and at 500 ft aal the descent rate was 2,500 fpm. The aircraft’s TAWS generated six ‘pull up’ warnings on final approach. The aircraft crossed the Runway 25 threshold at approximately 50 ft aal at 151 KIAS. The aircraft manufacturer calculated that the appropriate target threshold speed for the aircraft’s mass and configuration was 108 KIAS. The AFISO initiated a full emergency as the aircraft touched down, because “it was clear at this time that the aircraft was not going to stop”. Tyre marks made by the aircraft at touchdown indicated that it landed 710 m beyond the Runway 25 threshold. The Runway 25 declared Landing Distance Available (LDA) was 1,059 m; therefore the aircraft touched down 349 m before the end of the declared LDA. The paved runway surface extended 89 m beyond the end of the LDA. The aircraft continued along the runway, decelerating, but departed the end of the paved surface at a groundspeed of 83 kt (84 KIAS airspeed) and struck an earth bank, which caused the aircraft to become airborne again. It then struck cars in a car park, part of a large commercial site adjacent to the aerodrome. The wing separated from the fuselage, and the fuselage rolled left through 350° before coming to rest on top of the detached wing, on a heading of 064°(M), 30° right side down and in an approximately level pitch attitude. A fire broke out in the underside of the aft fuselage and burned with increasing intensity. The aerodrome’s RFFS responded to the crash alarm but their path to the accident site was blocked by a locked gate between the aerodrome and commercial site. The first two RFFS vehicles arrived at the gate 1 minute and 34 seconds after the aircraft left the runway end. The third RFFS vehicle, which carried a key for the gate, arrived approximately one minute later, and the three RFFS vehicles proceeded through the gate 2 minutes and 46 seconds after the aircraft left the runway. As the aircraft was located in an area of the car park surrounded by a 2.4 m tall wire mesh fence, the RFFS vehicles had to drive approximately 400 m to gain access to the accident site. Despite applying all their available media, the RFFS was unable to bring the fire under control. The intensity of the fire meant that it was not possible to approach the aircraft to save life. All four occupants of the aircraft survived the impact and subsequently died from the effects of fire. Subsequently, local authority fire appliances arrived and the fire was extinguished.
Probable cause:
The pilot was appropriately licensed and experienced, and had operated into Blackbushe Aerodrome on 15 previous occasions. He was reported to be physically and mentally well. The aircraft was certified for single-pilot operations and the pilot was qualified to conduct them. The engineering investigation of the accident aircraft did not find evidence of any pre‑existing technical defect that caused or contributed to the accident. The meteorological conditions were suitable for the approach and landing and, at the actual landing weight and appropriate speed, a successful landing at Blackbushe was possible. HZ-IBN joined the circuit at a speed and height which would have been consistent with the pilot’s stated plan to extend downwind in order that the microlight could land first. The subsequent positioning of HZ-IBN and the microlight involved HZ-IBN manoeuvring across the microlight’s path, in the course of which the first of several TCAS warnings was generated. After manoeuvring to cross the microlight’s path, HZ-IBN arrived on the final approach significantly above the normal profile but appropriately configured for landing. In the ensuing steep descent, the pilot selected the speed brakes out but they remained stowed because they are inhibited when the flaps are deployed. The aircraft’s speed increased and it crossed the threshold at the appropriate height, but 43 KIAS above the applicable target threshold speed. The excessive speed contributed to a touchdown 710 m beyond the threshold, with only 438 m of paved surface remaining. From touchdown, at 134 KIAS, it was no longer possible for the aircraft to stop within the remaining runway length. The brakes were applied almost immediately after touchdown and the aircraft’s subsequent deceleration slightly exceeded the value used in the aircraft manufacturer’s landing performance model. The aircraft departed the paved surface at the end of Runway 25 at a groundspeed of 83 kt. The aircraft collided with an earth bank and cars in a car park beyond it, causing the wing to separate and a fire to start. Although the aircraft occupants survived these impacts, they died from the effects of fire. Towards the end of the flight, a number of factors came together to create a very high workload situation for the pilot, to the extent that his mental capacity could have become saturated. His ability to take on new and critical information, and adapt his situational awareness, would have been impeded. In conjunction with audio overload and the mental stressors this can invoke, this may have lead him to become fixated on continuing the approach towards a short runway.
Final Report:

Crash of a Socata TBM-700 in Milwaukee: 2 killed

Date & Time: Jul 29, 2015 at 1810 LT
Type of aircraft:
Registration:
N425KJ
Flight Type:
Survivors:
No
Schedule:
Beverly - Milwaukee
MSN:
518
YOM:
2009
Crew on board:
1
Crew fatalities:
Pax on board:
1
Pax fatalities:
Other fatalities:
Total fatalities:
2
Captain / Total flying hours:
1875
Captain / Total hours on type:
721.00
Aircraft flight hours:
656
Circumstances:
The airline transport pilot was landing at the destination airport after a cross-country flight in visual meteorological conditions. The tower controller stated that the airplane's landing gear appeared to be extended during final approach and that the airplane landed within the runway's touchdown zone. The tower controller stated that, although the airplane made a normal landing, he heard a squealing noise that continued longer than what he believed was typical. The pilot subsequently transmitted "go-around." The tower controller acknowledged the go-around and cleared the pilot to enter a left traffic pattern. The tower controller stated that he heard the engine speed accelerate while the airplane maintained a level attitude over the runway until it passed midfield. He then saw the airplane pitch up and enter a climbing left turn. The tower controller stated that the airplane appeared to enter an aerodynamic stall before it descended into terrain in a left-wing-down attitude. Another witness reported that he saw the airplane, with its landing gear extended, in a steep left turn before it descended rapidly into terrain. A postaccident examination did not reveal any evidence of flight control, landing gear, or engine malfunction. An examination of the runway revealed numerous propeller slash marks that began about 215 ft past the runway's touchdown zone; however, there was no evidence that any portion of the airframe had impacted the runway during the landing. Additionally, measurement of the landing gear actuators confirmed that all three landing gear were fully extended at the accident site. Therefore, the pilot likely did not adequately control the airplane's pitch during the landing, which allowed the propeller to contact the runway. Due to the propeller strikes, the propeller was likely damaged and unable to provide adequate thrust during the go-around. Further, based on the witness accounts, the pilot likely did not maintain adequate airspeed during the climbing left turn, which resulted in the airplane exceeding its critical angle of attack and experiencing an aerodynamic stall at a low altitude.
Probable cause:
The pilot's improper pitch control during the landing, which resulted in the propeller striking the runway, and his failure to maintain adequate airspeed during the subsequent go-around, which resulted in the airplane exceeding its critical angle of attack and experiencing an aerodynamic stall at a low altitude.
Final Report:

Crash of an ATR72-212 in Yangon

Date & Time: Jul 24, 2015 at 1854 LT
Type of aircraft:
Operator:
Registration:
XY-AIH
Survivors:
Yes
Schedule:
Mandalay – Yangon
MSN:
469
YOM:
1995
Flight number:
JAB424
Country:
Region:
Crew on board:
5
Crew fatalities:
Pax on board:
49
Pax fatalities:
Other fatalities:
Total fatalities:
0
Captain / Total flying hours:
6603
Captain / Total hours on type:
513.00
Copilot / Total flying hours:
2650
Copilot / Total hours on type:
2650
Aircraft flight hours:
40827
Circumstances:
The route of the aircraft on that day was MDL- MYT- PBU- MYT- MDL- RGN. From Mandalay (MDL) on the way back to Yangon International Airport, the plane took off at 17:20.On the way the weather was not significant. For weather reason, seat belt sign was turned on the way to Yangon International Airport only one time. From Mandalay Airport up to landing phase to Yangon International Airport, first officer took control of the aircraft. At 1730 visibility was 6Km as per ATC verbal information. About 4 Km to Mingaladon Tower, clearance was obtained "Air Bagan 424 ,wind calm ,runway 21,clear to land, caution landing Runway wet, after landed vacate via Charlie" At decision height (250ft), runway was insight, runway lightings were able to be seen so the aircraft continued though there was light rain. At about 50 ft, more rain was falling suddenly consequently visibility became poor. So the pilot took over control of the aircraft. A few seconds later the aircraft made hard landing and skidded and veered off the left side of the runway to the muddy strip, came to rest about 2800ft from the threshold and 75ft from the runway edge.
Probable cause:
Primary cause:
During the final landing phase, the pilot was reluctant to perform a go-around while the plane was unstable and of bounce landing in low visibility condition.
Contributing factors:
a) The visibility was very low and the runway centerline lightings were not able to be seen intermittently.
b) The runway was wet and it was raining heavily.
c) The pilot in command took over the control of the plane from the copilot (14) seconds just before the first impact.
Final Report:

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

Date & Time: Jul 22, 2015 at 0744 LT
Registration:
N4BP
Flight Type:
Survivors:
Yes
Schedule:
Benton Harbor – Oshkosh
MSN:
46-8408065
YOM:
1984
Crew on board:
1
Crew fatalities:
Pax on board:
4
Pax fatalities:
Other fatalities:
Total fatalities:
0
Captain / Total flying hours:
934
Captain / Total hours on type:
130.00
Aircraft flight hours:
5792
Circumstances:
The pilot was landing at a large fly-in/airshow and following the airshow arrival procedures that were in use. While descending on the downwind leg for runway 27, the pilot was cleared by a controller to turn right onto the base leg abeam the runway numbers and to land on the green dot (located about 2,500 ft from the runway's displaced threshold). About the time the pilot turned onto the base leg, he observed an airplane taxi onto the runway and start its takeoff roll. The controller instructed the pilot to continue the approach and land on the orange dot (located about 1,000 ft from the runway's displaced threshold) instead of the green dot. The pilot reported that he considered performing a go-around but decided to continue the approach. As the pilot reduced power, the airplane entered a stall and impacted the runway in a right-wing-low, nose-down attitude. Witnesses estimated that the bank angle before impact was greater than 60 degrees. A postaccident examination of the airframe and engine revealed no evidence of mechanical malfunctions or failures that would have precluded normal operation.
Analysis of a video recording of the accident showed that the airplane was about 180 ft above ground level (agl) when the turn onto the base leg began, and it descended to about 140 ft agl during the turn. The airplane's total inertial speed (the calculated vector sums of the airplane's ground speeds and vertical speeds) decreased from 98 knots (kts) to 80 kts during the turn. During the last 8 seconds of flight, the speed decreased below 70 kts, and the airplane descended from about 130 ft agl to ground impact. The wings-level stall speed of the airplane at maximum gross weight with landing gear and flaps down was 59 kts. In the same configuration at 60 degrees of bank, the stall speed was 86 kts and would have been higher at a bank angle greater than 60 degrees. Reduced runway separation standards for airplanes were in effect due to the airshow. When the accident airplane reached the runway threshold, the minimum distance required by the standards between the arriving accident airplane and the departing airplane was 1,500 ft. The video analysis indicated that it was likely that a minimum of 1,500 ft of separation was maintained during the accident sequence. Although the pilot was familiar with the procedures for flying into the airshow, the departing airplane
and the modified landing clearance during a period of typically high workload likely interfered with the pilot's ability to adequately monitor his airspeed and altitude. As a result, the airplane entered an accelerated stall when the pilot turned the airplane at a steep bank angle and a low airspeed in an attempt to make the landing spot, which resulted in the airplane exceeding its critical angle of attack. At such a low altitude, recovery from the stall was not possible. Although the airshow arrival procedures stated that pilots have the option to go around if necessary, and the pilot considered going around, he instead continued the unstable landing approach and lost control of the airplane.
Probable cause:
The pilot's failure to perform a go-around after receiving a modified landing clearance and his failure to maintain adequate airspeed while maneuvering to land, which resulted in the airplane exceeding its critical angle of attack in a steep bank and entering an accelerated stall at a low altitude.
Final Report:

Crash of a Learjet 35A in Panama City

Date & Time: Jul 19, 2015
Type of aircraft:
Operator:
Registration:
YV543T
Flight Type:
Survivors:
Yes
MSN:
35-246
YOM:
1979
Country:
Crew on board:
2
Crew fatalities:
Pax on board:
0
Pax fatalities:
Other fatalities:
Total fatalities:
0
Circumstances:
For unknown reasons, the aircraft completed a belly landing at Panana City-Tocument Airport. Both occupants evacuated safely and the aircraft was damaged beyond repair.

Crash of a De Havilland DHC-6 Twin Otter 300 off Kuredu Island

Date & Time: Jul 2, 2015 at 1733 LT
Operator:
Registration:
8Q-MAN
Survivors:
Yes
Schedule:
Male - Kuredu Island
MSN:
435
YOM:
1974
Region:
Crew on board:
3
Crew fatalities:
Pax on board:
11
Pax fatalities:
Other fatalities:
Total fatalities:
0
Captain / Total flying hours:
5075
Captain / Total hours on type:
4200.00
Copilot / Total flying hours:
988
Copilot / Total hours on type:
705
Aircraft flight hours:
24132
Circumstances:
Flight FLT371301, a Viking Air (De Havilland) DHC-6-300 aircraft with registration mark 8Q-MAN, crashed into the sea approximately 3 km southeast of Kuredu (KUR) at 1733 hrs on 2 July 2015. The aircraft was flying under visual flight rules (VFR) on a charter flight, carrying 11 passengers from Komandoo (KOM) to Kuredu (KUR). According to the operating crew, the aircraft was on final approach, northwest bound, to land at KUR. At approximately 400 feet, on selection of flaps to the fully down position, the aircraft pitched up and the aircraft was vibrating. The pilot flying (PF) could not control the aircraft and asked the PIC to take over the controls. The aircraft was in a nose-high attitude when the PIC took over the controls. The stall warning light illuminated. The PIC applied full left rudder, moved the control column forward and put the power levers to idle to recover the aircraft. The aircraft, however, did not respond to these actions. Flaps were then moved to the fully up position. The PIC was gaining some control at this stage but the aircraft continued turning right, losing height and impacted the sea before he could regain full control of the aircraft. On initial impact the left float detached. The aircraft then bounced and landed on the right float causing the right float to also detach from the aircraft. The right float was, however, trapped between the airframe and the engine for several minutes. With both floats detached from the aircraft and the right float still trapped between the airframe and engine, the aircraft stayed afloat until all passengers and crew evacuated. At the same time the aircraft started tilting left causing water to rush inside and started sinking. All 11 passengers and three crew were able to evacuate the aircraft without injury, before the aircraft completely sank. The accident was notified to the Aircraft Accident Investigation Committee (AICC) at 1750 hrs. Investigation began on the same day. Inspectors arrived at the scene at 2300 hrs, about five and a half hours after the accident occurred.
Probable cause:
The investigation identified the following causes:
a. The aircraft was operated outside the centre of gravity limitations on the sector in which the accident occurred.
b. The load distribution errors went undetected because the mass and balance calculations were not carried out in accordance with the approved procedures, prior to the accident flight.
c. The co-pilot (PF) was not alerted to the impending stall as she neither saw the stall warning light illuminated nor heard the aural stall warning.
d. The PIC was not able to gain control of aircraft as developing stall was not recognized and incorrect recovery procedures were applied.
Final Report:

Crash of a Hawker 800XP in Port Harcourt

Date & Time: Jun 8, 2015 at 1916 LT
Type of aircraft:
Registration:
N497AG
Survivors:
Yes
Schedule:
Abuja – Port Harcourt
MSN:
258439
YOM:
1999
Country:
Region:
Crew on board:
3
Crew fatalities:
Pax on board:
2
Pax fatalities:
Other fatalities:
Total fatalities:
0
Captain / Total flying hours:
4180
Captain / Total hours on type:
2752.00
Copilot / Total flying hours:
16744
Copilot / Total hours on type:
147
Aircraft flight hours:
8447
Aircraft flight cycles:
6831
Circumstances:
On 11th June, 2015, at about 18:25 h, an HS-125-800XP aircraft with nationality and registration marks N497AG, operated by SWAT Technology Limited departed Nnamdi Azikiwe International Airport, Abuja (DNAA) for Port Harcourt International Airport (DNPO) as a charter flight on an Instrument Flight Rule (IFR) flight plan. There were five persons on board inclusive of three flight crew and two passengers. The Captain was the Pilot Flying while the Co-pilot was the Pilot Monitoring. At 18:48 h, N497AG established contact with Lagos and Port Harcourt Air Traffic Control (ATC) units cruising at Flight Level (FL) 280. At 18:55 h, the aircraft was released by Lagos to continue with Port Harcourt. Port Harcourt cleared N497AG for descent to FL210. At 19:13 h, the crew reported field in sight at 6 nautical miles to touch down to the Tower Controller (TC). TC then cleared the aircraft to land with caution “runway surface wet”. The crew experienced light rain at about 1.3 nautical miles to touch down with runway lights ON for the ILS approach. At about 1,000 ft after the extension of landing gears, the PM remarked ‘Okay...I got a little rain on the windshield’ and the PF responded, ‘We don’t have wipers sir... (Laugh) Na wa o (Na wa o – local parlance, - pidgin, for expression of surprise). From the CVR, at Decision Height, the PM called out ‘minimums’ while the PF called back ‘landing’ as his intention. The PM reported that the runway edge lights were visible on the left side. On the right side, it was missing to a large extent and only appeared for about a quarter of the way from the runway 03 end. The PM observed that the aircraft was slightly to the left of the “centreline” and pointed out “right, right, more right.” The PM further stated that at 50 ft, the PF retarded power and turned to the left. At 40 ft, the PM cautioned the PF to ‘keep light in sight don’t go to the left’. At 20 ft, the PM again said, ‘keep on the right’. PF replied, ‘Are you sure that’s not the centre line?’. At 19:16 h, the aircraft touched down with left main wheel in the grass and the right main wheel on the runway but was steered back onto the runway. The PF stated, “...but just on touchdown the right-hand lights were out, and in a bid to line up with the lights we veered off the runway to the left”. The nose wheel landing gear collapsed, and the aircraft stopped on the runway. The engines were shut down and all persons on board disembarked without any injury. From the CVR recordings, the PF told the PM that he mistook the brightly illuminated left runway edge lights for the runway centreline and apologized for the error of judgement for which the PM responded ‘I told you’. The aircraft was towed out of the runway and parked at GAT Apron at 21:50 h. The accident occurred at night in light rain.
Probable cause:
The accident was the consequence of a black hole effect disorientation causing low-level manoeuvre into grass verge.
The following contributing factors were identified:
- Most of the runway 21 right edge lights were unserviceable at landing time.
- Inadequate Crew Resource Management during approach.
Final Report:

Crash of a Piper PA-31T Cheyenne II off Barcelona

Date & Time: May 30, 2015 at 1635 LT
Type of aircraft:
Registration:
YV2761
Flight Type:
Survivors:
Yes
Schedule:
Charallave – Barcelona
MSN:
31-8120055
YOM:
1981
Country:
Crew on board:
1
Crew fatalities:
Pax on board:
3
Pax fatalities:
Other fatalities:
Total fatalities:
0
Circumstances:
Following an uneventful flight from Charallave, the pilot initiated the descent to Barcelona-Jose Antonio Anzoátegui Airport in poor weather conditions. On final, in a flat attitude, the twin engine aircraft impacted the water surface and came to rest some 3,7 km short of runway 15. All four occupants evacuated the cabin and took place in a lifeboat. Slightly injured, they were rescued two hours later. The aircraft sank and was lost.

Crash of a Cessna 208B Caravan I in Mandeng

Date & Time: May 19, 2015
Type of aircraft:
Operator:
Registration:
5Y-NKV
Survivors:
Yes
Schedule:
Juba - Mandeng
MSN:
208B-0387
YOM:
1994
Country:
Region:
Crew on board:
0
Crew fatalities:
Pax on board:
0
Pax fatalities:
Other fatalities:
Total fatalities:
0
Circumstances:
The single engine airplane suffered an accident upon landing at Mandeng Airfield. The undercarriage were torn off and the aircraft was severely damaged. There were no casualties.