Crash of a Grumman G-159 Gulfstream I in Kinshasa

Date & Time: Nov 1, 2015
Type of aircraft:
Operator:
Registration:
9Q-CNP
Survivors:
Yes
MSN:
164
YOM:
1965
Region:
Crew on board:
4
Crew fatalities:
Pax on board:
22
Pax fatalities:
Other fatalities:
Total fatalities:
0
Circumstances:
After takeoff from Kinshasa-Ndolo Airport, the crew reported technical problems with the undercarriage and was cleared to divert to Kinshasa-N'Djili Airport. A belly landing was completed on runway 24 and the aircraft slid for few dozen metres then veered off runway to the right and came to rest in a grassy area. All 26 occupants evacuated safely and the aircraft was damaged beyond repair. It is believed that the left main gear was torn off upon takeoff from Kinshasa-Ndolo Airport for unknown reasons.

Ground fire of a Boeing 767-269ER in Fort Lauderdale

Date & Time: Oct 29, 2015 at 1233 LT
Type of aircraft:
Operator:
Registration:
N251MY
Flight Phase:
Survivors:
Yes
Schedule:
Fort Lauderdale - Caracas
MSN:
23280/131
YOM:
1986
Flight number:
DYA405
Crew on board:
11
Crew fatalities:
Pax on board:
90
Pax fatalities:
Other fatalities:
Total fatalities:
0
Captain / Total flying hours:
15700
Copilot / Total flying hours:
4140
Aircraft flight hours:
30108
Aircraft flight cycles:
9986
Circumstances:
On October 29, 2015, about 12:33 pm eastern daylight time (EDT), Dynamic International Airways flight 405, a Boeing 767-200ER, N251MY, experienced a fuel leak and subsequent fire while taxiing for departure at the Fort Lauderdale-Hollywood International Airport, Florida (FLL). Of the 101 passengers and crew onboard, one passenger received serious injuries. The airplane sustained substantial damage from the fire. The flight was operating under the provisions of 14 Code of Federal Regulations Part 121 supplemental as a scheduled charter from FLL to Maiquetía Simón Bolívar International Airport (CCS), Caracas, Venezuela. A significant fuel leak and subsequent fire occurred in the left engine strut and nacelle during taxi, resulting in substantial damage to the airplane. The fuel leak was the result of a fuel line flexible coupling (Wiggins fitting) loosening and becoming disengaged due to the lack of a safety lockwire on the coupling as required by the maintenance manual. The leaking fuel contacted hot engine case surfaces which ignited the fire. Records indicate that maintenance was conducted on this fitting in October of 2012 at the 4C check prior to the airplane being prepared for storage. The area would also have been subject to a visual inspection when the airplane was brought out of storage in 2015. The same maintenance facility conducted both of these activities. About 240 flight hours were logged between the aircraft returning to service and the accident. The leak occurred after the coupling loosened due to the missing safety wire which was the result of an error by the third-party maintenance provider. The flight crew promptly shut down the left engine using the fire handle, and requested fire equipment. As the airplane stopped on the taxiway, passengers saw the fire and insisted that the cabin crew initiate an evacuation. One passenger opened an overwing exit on his own, and the slide did not deploy. The cabin crew initiated the evacuation without coordination with the flight crew. After the evacuation had already begun, the flight crew advised over the PA to evacuate out the right side of the airplane. The flight crew did not immediately shut down the right engine and an evacuating passenger ran behind the engine and was blown to the pavement resulting in serious injuries. The lack of coordination between the flight crew and cabin crew resulted in the evacuation initiating while the right engine was still running.
Probable cause:
The separation of the flexible fuel line coupling and subsequent fuel leak due to the failure of maintenance personnel to install the required safety lockwire. Contributing to the severity of the accident was the initiation of the evacuation before the right engine was shut down which led to the passenger's injury.
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 Boeing 737-3K2 in Cuzco

Date & Time: Oct 23, 2015 at 1115 LT
Type of aircraft:
Operator:
Registration:
OB-2040-P
Survivors:
Yes
Schedule:
Lima - Cuzco
MSN:
24329/1858
YOM:
1990
Flight number:
P9216
Country:
Crew on board:
6
Crew fatalities:
Pax on board:
133
Pax fatalities:
Other fatalities:
Total fatalities:
0
Captain / Total flying hours:
6352
Captain / Total hours on type:
1971.00
Copilot / Total flying hours:
1455
Copilot / Total hours on type:
1219
Aircraft flight hours:
74018
Aircraft flight cycles:
42389
Circumstances:
Following an uneventful flight from Lima, the crew started the descent to Cuzco-Alejandro Velasco Astete Airport Runway 28. On approach, the aircraft was configured for landing and flaps were deployed to 15°. Following a smooth landing, the crew started the braking procedure when, eight seconds after touchdown, he noticed vibrations coming from the left main gear. At a speed of 100 knots, the right main gear collapsed. The aircraft rolled for few hundred metres then came to a halt on the runway. All 139 occupants evacuated safely and the aircraft was damaged beyond repair.
Probable cause:
Unstable approach and inadequate landing technique for high altitude fields, which resulted in increased landing speed, the start of the flare manoeuvre at higher altitude, and low descent speed, which made the OB-2040-P aircraft make soft contact with the runway, causing inefficiency in operation of the shimmy damper, which did not prevent uncontrolled oscillation of the shock absorbers.
Contributing factors:
- Lack of instruction and training in simulators that include techniques and maneuvers of landing at high altitude fields, with emphasis on speed control at landing.
- Lack of a performance analysis process, through the use of flight recorders or other installed data recording equipment and flight parameters, by the operating company, to enable supervision, control and corrective measures in the operational use of its aircraft.
Final Report:

Crash of a BAe 146-300 in Tamale

Date & Time: Oct 6, 2015 at 0831 LT
Type of aircraft:
Operator:
Registration:
9G-SBB
Survivors:
Yes
Schedule:
Accra – Tamale
MSN:
E.3123
YOM:
1989
Flight number:
IKM110
Location:
Country:
Region:
Crew on board:
5
Crew fatalities:
Pax on board:
71
Pax fatalities:
Other fatalities:
Total fatalities:
0
Circumstances:
After landing on runway 23 at Tamale Airport, the four engine aircraft failed to stop within the remaining distance. It went through a fence that was delimiting a work area as the runway was subject to an extension. Upon impact, the nose gear was torn off and the aircraft slid for few dozen metres before coming to rest. All 76 occupants escaped uninjured but the aircraft was damaged beyond repair. It was specified in a NOTAM that the runway 23 length was reduced to 1,860 meters and that works were in progress to extend runway 23, with the presence of men and equipment. So, caution was advised during landing and takeoff procedures.

Crash of a De Havilland DHC-6 Twin Otter 300 on Mt Bajaja: 10 killed

Date & Time: Oct 2, 2015 at 1451 LT
Operator:
Registration:
PK-BRM
Flight Phase:
Survivors:
No
Site:
Schedule:
Masamba – Makassar
MSN:
741
YOM:
1981
Flight number:
VIT7503
Country:
Region:
Crew on board:
2
Crew fatalities:
Pax on board:
8
Pax fatalities:
Other fatalities:
Total fatalities:
10
Captain / Total flying hours:
2911
Captain / Total hours on type:
2911.00
Copilot / Total flying hours:
4035
Copilot / Total hours on type:
4035
Aircraft flight hours:
45242
Aircraft flight cycles:
75241
Circumstances:
On 2 October 2015, a DHC-6 Twin Otter, registered PK-BRM, was being operated by PT. Aviastar Mandiri as a scheduled passenger flight with flight number MV 7503. The aircraft departed from Andi Jemma Airport, Masamba (WAFM)1 with the intended destination of Sultan Hasanuddin International Airport, Makassar (WAAA) South Sulawesi, Indonesia. On board the flight were 10 persons consisting of two pilots and eight passengers, including one company engineer. The previous flights were from Makassar – Tana Toraja – Makassar – Masamba – Seko - Masamba and the accident flight was from Masamba to Makassar which was the 6th sector of the day. The aircraft departed from Masamba at 1425 LT (0625 UTC2 ) with an estimated time of arrival at Makassar of 0739 UTC. The Pilot in Command (PIC) acted as Pilot Flying (PF) while the Second in Command (SIC) acted as Pilot Monitoring (PM). The flight was conducted under the Visual Flight Rules (VFR) and cruised at an altitude of 8,000 feet. At 0630 UTC, the pilot reported to Ujung Pandang Information officer that the aircraft passed an altitude of 4,500 feet and was climbing to 8,000 feet. The Ujung Pandang Information officer requested the pilot of the estimate time of aircraft position at 60 Nm out from MKS VOR/DME. At 0632 UTC, the pilot discussed about the calculation of estimate time to reach 60 Nm out from MKS and afterward the pilot informed Ujung Pandang Information officer that the estimate at 60 Nm was at 0715 UTC. At 0633 UTC, the Ujung Pandang Information officer informed the pilot to call when reaching 8,000 feet and was acknowledged by the pilot. At 0636 UTC, the pilot informed the Ujung Pandang Information officer that the aircraft had reached 8,000 feet and requested the squawk number (ATC transponder code). The Ujung Pandang Information officer acknowledged and gave the squawk number of A5616, which was acknowledged by the pilot. At 0637 UTC, the pilots discussed to fly direct to BARRU. BARRU is a town located at about 45 Nm north of Makassar. Both pilots agreed to fly direct and the SIC explained the experience of flying direct on the flight before. At 0651 UTC, the PIC told the SIC that he wanted to climb and one second later the CVR recorded the sound of impact.
Probable cause:
The following findings were identified:
1. The aircraft had valid Certificate of Airworthiness prior to the accident and was operated within the weight and balance envelope.
2. Both pilots had valid licenses and medical certificates.
3. The accident flight from Masamba (WAFM) to Makassar (WAAA) was the 6th sector for the aircraft and the crew that day. The PIC acted as Pilot Flying and the
SIC acted as Pilot Monitoring.
4. The satellite image published by BMKG at 0700 UTC showed that there were cloud formations at the accident area. The local villagers stated that the weather
on the accident area was cloudy at the time of the accident.
5. The aircraft departed Masamba at 0625 UTC (1425 LT), conducted under VFR with cruising altitude of 8,000 feet and estimated time of arrival Makassar at 0739 UTC.
6. After reached cruising altitude, at about 22 Nm from Masamba, the flight deviated from the operator visual route and directed to BARRU on heading 200° toward the area with high terrain and cloud formation based on the BMKG satellite image
7. The pilots decision making process did not show any evidence that they were concerned to the environment conditions ahead which had more risks and required correct flight judgment.
8. The CVR did not record EGPWS aural caution and warning prior to the impact. The investigation could not determine the reason of the absence of the EGPWS.
9. The CVR data and cut on the trees indicated that the aircraft was on straight and level flight and there was no indication of avoid action by climb or turn.
10. The SAR Agency did not receive any crashed signal from the aircraft ELT most likely due to the ELT antenna detached during the impact.
11. Regarding to the operation of the EGPWS for the flight crew, a special briefing was performed however there was no special training.
12. The operational test of TAWS system was not included in the pilot checklist.
13. The investigation could not determine the installation and the last revision of TAWS terrain database.
14. The investigation could not find the functional test result document after the installation of the TAWS.
15. Some of the DHC-6 pilots have not been briefed for the operation of the TAWS and EGPWS.

Contributing Factors:
Deviation from the company visual route without properly considering the elevated risks of cruising altitude lower than the highest terrain and instrument meteorological condition in addition with the absence of the EGPWS warning resulted in the omission of avoidance actions.
Final Report:

Crash of a De Havilland DHC-8-Q402 in Saarbrücken

Date & Time: Sep 30, 2015 at 1016 LT
Operator:
Registration:
LX-LGH
Flight Phase:
Survivors:
Yes
Schedule:
Hamburg - Saarbrücken - Luxembourg
MSN:
4420
YOM:
2012
Flight number:
LG9562
Country:
Region:
Crew on board:
4
Crew fatalities:
Pax on board:
16
Pax fatalities:
Other fatalities:
Total fatalities:
0
Captain / Total flying hours:
11927
Captain / Total hours on type:
3649.00
Copilot / Total flying hours:
3295
Copilot / Total hours on type:
1483
Aircraft flight hours:
7131
Circumstances:
On the day of the accident, the crew of four was deployed for flights from Luxembourg (LUX) via Saarbrucken (SCN) to Hamburg (HAM) and back again via Saarbrucken to Luxembourg with a Bombardier DHC-8-402. The crew stated that they had met at about 0530 hrs for pre-flight preparations. The flights up until the take-off in Saarbrucken had occurred without incident. All in all the working atmosphere had been good and relaxed and they had been ahead of schedule. Saarbrucken was the destination airport for 14 passengers. The remaining 16 passengers’ destination airport was Luxembourg. According to the Cockpit Voice Recorder (CVR), the Flight Data Recorder (FDR), and the radio communication recordings, the engine start-up clearance was issued at 1009:47 hrs approximately 25 minutes ahead of schedule. At 1015:03 hrs while taxiing on taxiway C take-off clearance was issued. The Into Position Check was conducted at 1015:33 hrs on runway 09. The Pilot in Command (PIC) was Pilot Flying (PF) and the co-pilot Pilot Non Flying (PNF). The plan was to conduct take-off with reduced engine thrust (81%). During take-off the following callouts were made:
1016:24 PF take off, my controls
1016:25 PNF your controls
1016:27 PNF spoiler is closed
1016:30 PNF autofeather armed
1016:33 PF looks like spring
1016:35 PNF yeah, power is checked
1016:36 PNF 80 knots
1016:37 PF checked
1016:40 PNF V1, rotate
1016:42 Background click sound, probably gear lever UP
1016:43 PNF upps, sorry
During the rotation phase with approximately 127 KIAS and a nose-up attitude of approximately 5°, the landing gear retracted. At 1016:44 hrs the airplane’s tail had the first ground contact (tail strike). The tail strike warning light illuminated. Approximately 875 m after the initial ground contact the airplane came to a stop after it had bounced three times and skidded on the fuselage. The cabin crew stated that due to smoke and fume development in the cabin the airplane was evacuated right away. All passengers and the crew were uninjured and left the severely damaged airplane without help.
Probable cause:
The air accident was the result of an early retraction of the retractable landing gear during take-off, which was not prevented by the landing gear selector lever and the retracting control logic.
Contributory factors:
- Reduced concentration level,
- A break in the callout process / task sequence on the part of the PNF,
- Actuation of the landing gear lever to the UP Position too early,
- Control logic design allows retraction of the landing gear with one wheel airborne.
Final Report:

Crash of a Piper PA-31-350 Navajo Chieftain in Thompson

Date & Time: Sep 15, 2015 at 1821 LT
Operator:
Registration:
C-FXLO
Flight Phase:
Survivors:
Yes
Schedule:
Thompson – Winnipeg
MSN:
31-8052022
YOM:
1980
Flight number:
KEE208
Country:
Crew on board:
2
Crew fatalities:
Pax on board:
6
Pax fatalities:
Other fatalities:
Total fatalities:
0
Captain / Total flying hours:
2000
Captain / Total hours on type:
1000.00
Copilot / Total flying hours:
446
Copilot / Total hours on type:
120
Circumstances:
At 1817 Central Daylight Time, the Keystone Air Service Ltd. Piper PA-31-350 (registration C-FXLO, serial number 31-8052022) departed Runway 06 at Thompson Airport, Manitoba, on an instrument flight rules flight to Winnipeg/James Armstrong Richardson International Airport, Manitoba, with 2 pilots and 6 passengers on board. Shortly after rotation, both engines began to lose power. The crew attempted to return to the airport, but the aircraft was unable to maintain altitude. The landing gear was extended in preparation for a forced landing on a highway southwest of the airport. Due to oncoming traffic, the forced landing was conducted in a forested area adjacent to the highway, approximately 700 metres south of the threshold of Runway 06. The occupants sustained varying serious injuries but were able to assist each other and exit the aircraft. The emergency locator transmitter activated, and there was no fire. Emergency services were activated by a 911 call and by the Thompson flight service station. Initial assistance was provided by sheriffs of the Manitoba Department of Justice after a crew member flagged down their vehicle on the highway.
Probable cause:
Findings as to causes and contributing factors:
1. Delivery of the incorrect type of aircraft fuel caused loss of power from both engines, necessitating a forced landing.
2. The fueling operation was not adequately supervised by the flight crew.
3. A reduced-diameter spout was installed that enabled the delivery of Jet-A1 fuel into the AVGAS fuel filler openings.
4. The fuel slip indicating that Jet-A1 fuel had been delivered was not available for scrutiny by the crew.

Findings as to risk:
1. If administrative and physical defences against errors in aviation fuel operations are circumvented or disabled, there is a risk that the incorrect type of fuel will be delivered.
2. If a reduced-diameter spout is available to accommodate non-standard fuel filler openings, there is an increased risk that Jet-A1 fuel can be dispensed into an aircraft that requires AVGAS.

Other findings:
1. Aircraft that were manufactured prior to the current airworthiness standards, or that have been modified by the installation of turbine engines, may have fuel filler openings that do not meet the dimension requirements.
2. The airworthiness standards for rotorcraft do not specify the size of fuel filler openings.
3. The use of all of the available restraint systems in the aircraft contributed to the survival of the occupants.
4. There was no post-crash fire, likely due to the separation of the battery from the aircraft and to the rain-saturated crash site.
5. The absence of a post-impact fire contributed to the survival of all of the aircraft's occupants.
Final Report:

Crash of an ATR42-300 near Oksibil: 54 killed

Date & Time: Aug 16, 2015 at 1455 LT
Type of aircraft:
Operator:
Registration:
PK-YRN
Flight Phase:
Survivors:
No
Site:
Schedule:
Jayapura - Oksibil
MSN:
102
YOM:
1988
Flight number:
TGN267
Country:
Region:
Crew on board:
4
Crew fatalities:
Pax on board:
50
Pax fatalities:
Other fatalities:
Total fatalities:
54
Captain / Total flying hours:
25287
Captain / Total hours on type:
7340.00
Copilot / Total flying hours:
3818
Copilot / Total hours on type:
2640
Aircraft flight hours:
50133
Aircraft flight cycles:
55663
Circumstances:
An ATR 42-300 aircraft registered PK-YRN was being operated by PT Trigana Air Service on 16 August 2015 as scheduled passenger flight with flight number IL267 from Sentani to Oksibil. On board of this flight were 54 persons. This flight was the fifth flight of the day and the second flight from Sentani to Oksibil. The aircraft departed Sentani at 0522 UTC and estimated time of arrival Oksibil was at 0604 UTC. The Second in Command (SIC) acted as Pilot Flying while the Pilot in Command (PIC) acted as Pilot Monitoring. The weather at Oksibil reported that the cloud was broken (more than half area of the sky covered by cloud) and the cloud base was 8,000 feet (4,000 feet above airport elevation) and the visibility was 4 up to 5 km. The area of final approach path was covered by clouds. The flight cruising at 11,500 feet and at 0555 UTC, the pilot made first contact with Oksibil Aerodrome Flight Information Services (AFIS) officer, reported on descent at position Abmisibil and intended to direct left base leg runway 11. At 0600 UTC, Oksibil AFIS officer expected the aircraft would have been on final but the pilot had not reported, the AFIS officer contacted the pilot but did not reply. The AFIS officer informed Trigana in Sentani that they had lost contact with IL267. The aircraft wreckage was found on a ridge of Tanggo Mountain, Okbape District, Oksibil at approximately 8,300 feet AMSL at coordinates of 04°49’17.34” S, 140°29’51.18” E, approximately 10 NM from Oksibil Aerodrome on bearing of 306°. All occupants were fatally injured and the aircraft was destroyed by impact force and post impact fire. The Flight Data Recorder (FDR) and Cockpit Voice Recorder were recovered and transported to KNKT recorder facility. The recovery of FDR data was unsuccessful while the recovery of CVR data successfully retrieved accident flight data. The CVR did not record any crew briefing, checklist reading not EGPWS warning prior to impact. The CVR also did not record EGPWS altitude call out on two previous flights. The investigation concluded that the EGPWS was probably not functioning.
Probable cause:
The following findings were identified:
1. The aircraft had valid Certificate of Airworthiness and was operated within the weight and balance envelope.
2. All crew had valid licenses and medical certificates.
3. The flight plan form was filed with intention to fly under Instrument Flight Rule (IFR), at flight level 155, with route from Sentani to MELAM via airways W66 then to Oksibil. The MORA of W66 between Sentani to MELAM was 18,500 feet.
4. The flight was the 5th flight of the day for the crew with the same aircraft and the second flight on the same route of Sentani to Oksibil.
5. The CVR data revealed that the previous flight from Sentani to Oksibil the flight cruised at altitude of 11,500 feet and the approach was conducted by direct to left base runway 11.
6. The CVR data also revealed that on the accident flight, the flight cruised at altitude 11,500 feet and intended to direct left base leg runway 11 which was deviate from the operator visual guidance approach that described the procedure to fly overhead the airport prior to approach to runway 11.
7. The witness stated that most of the time, the flight crew deviated from the operator visual approach guidance. The deviation did not identify by the aircraft operator.
8. The downloading process to retrieve data from the FDR was unsuccessful due to the damage of the FDR unit that most likely did not record data during the accident flight. The repetition problems of the FDR unit showed that the aircraft operator surveillance to the repair station was not effective.
9. The CVR did not record any crew briefing, checklist reading and EGPWS altitude callout prior to land on two previous flights nor the EGPWS caution and warning prior to impact.
10. The spectrum analysis of the CVR determined that both engines were operating prior to the impact.
11. Several pilots, had behavior of pulling the EGPWS CB to eliminate the nuisance of EGPWS warning. The pilots stated that the reason for pulling the EGPWS CB was due to the pilots considered this warning activation was not appropriate for the flight conditions. The correction to this behavior was not performed prior to the accident.
12. The investigation could not determine the actual EGPWS CB position during the accident flight.
13. The installation of EGPWS by the aircraft operator was not conducted according to the Service Bulletin issued by the aircraft manufacturer.
14. The terrain data base installed in the EGPWS of PK-YRN was the version MK_VIII_Worldwide_Ver_471 that was released in 2014. The Oksibil Airport was not included in the high-resolution update in this version of terrain database.
15. The information for Oksibil published in AIP volume IV (Aerodrome for Light Aircraft/ALA) did not include approach guidance. The operator issued visual guidance of circling approach runway 11 for internal use.
16. The visual approach guidance chart stated that the minimum safe altitude was 8,000 feet while the aircraft impacted with terrain at approximately 8,300 feet. This indicated an incorrect information in the chart. The investigation considered that the pattern on the approach guidance chart was not easy to fly, as many altitudes and heading changes.
17. Several maintenance records such as component status installed on the aircraft and installation of EGPWS was not well documented. This indicated that the maintenance management was not well performed.
18. The investigation could not find any regulation that describes the pilot training requirement for any addition or modification of aircraft system which affect to the aircraft operation.
19. There was no information related to the status of ZX NDB published on NOTAM prior to the accident.
20. Several safety issues indicated that the organization oversight of the aircraft operator by the regulator was not well implemented.
Contributing Factors:
1. The deviation from the visual approach guidance in visual flight rules without considering the weather and terrain condition, with no or limited visual reference to the terrain resulted in the aircraft flew to terrain.
2. The absence of EGPWS warning to alert the crew of the immediate hazardous situation led to the crew did not aware of the situation.
Final Report:

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.