Crash of an Embraer EMB-120RT Brasília in Lucapa

Date & Time: Feb 25, 2014 at 1000 LT
Type of aircraft:
Operator:
Registration:
D2-FFZ
Survivors:
Yes
Schedule:
Luanda – Lucapa
MSN:
120-212
YOM:
1990
Country:
Region:
Crew on board:
3
Crew fatalities:
Pax on board:
14
Pax fatalities:
Other fatalities:
Total fatalities:
0
Circumstances:
On final approach to Lucapa, the crew encountered technical problems and was forced to shut an engine down for unknown reason. After touchdown, the aircraft went out of control and veered off runway to the left. While contacting rough terrain, the aircraft lost its undercarriage and came to rest on its belly with severe damages to both wings, engines and fuselage. Three passengers were slightly injured.

Crash of a Beechcraft B100 King Air in Pearland: 1 killed

Date & Time: Feb 19, 2014 at 0845 LT
Type of aircraft:
Operator:
Registration:
N811BL
Flight Type:
Survivors:
No
Schedule:
Austin – Galveston
MSN:
BE-15
YOM:
1976
Location:
Crew on board:
1
Crew fatalities:
Pax on board:
0
Pax fatalities:
Other fatalities:
Total fatalities:
1
Captain / Total flying hours:
1281
Captain / Total hours on type:
192.00
Circumstances:
The non-instrument-rated pilot departed on a cross-country flight in a twin-engine turboprop airplane on an instrument flight plan. As the pilot neared his destination airport, he received heading and altitude vectors from air traffic control. The controller cleared the flight for the approach to the airport; shortly afterward, the pilot radioed that he was executing a missed approach. The controller then issued missed approach instructions, which the pilot acknowledged. There was no further communication with the pilot. The airplane collided with terrain in a near-vertical angle. About the time of the accident, the automated weather reporting station recorded a 300-foot overcast ceiling, and 5 miles visibility in mist. Examination of the wreckage did not reveal any anomalies that would have precluded normal operation. Additionally, both engines displayed signatures consistent with the production of power at the time of impact. The pilot's logbook indicated that he had a total of 1,281.6 flight hours, with 512.4 in multi-engine airplanes and 192.9 in the accident airplane. The logbook also revealed that he had 29.7 total hours of actual instrument time, with 15.6 of those hours in the accident airplane. Of the total instrument time, he received 1 hour of instrument instruction by a flight instructor, recorded about 3 years before the accident. The accident is consistent with a loss of control in instrument conditions.
Probable cause:
The noninstrument-rated pilot's loss of airplane control during a missed instrument approach. Contributing to the accident was the pilot's decision to file an instrument flight rules flight plan and to fly into known instrument meteorological conditions.
Final Report:

Crash of an Avro 748-371-2B in Rubkona: 1 killed

Date & Time: Feb 17, 2014 at 1445 LT
Type of aircraft:
Operator:
Registration:
5Y-HAJ
Flight Type:
Survivors:
Yes
Schedule:
Juba – Rubkona
MSN:
1776
YOM:
1980
Country:
Region:
Crew on board:
4
Crew fatalities:
Pax on board:
0
Pax fatalities:
Other fatalities:
Total fatalities:
1
Circumstances:
The crew was performing a humanitarian flight from Juba to Rubkona on behalf of the International Organisation for Migration, part of the UNMISS, the United Nations Mission in South Sudan. After landing, the aircraft was unstable and went out of control. It veered off runway, hit several cars and lost a wing before coming to rest partially upside down, bursting into flames. The flight engineer was killed while three other crew were seriously injured. The aircraft was destroyed.
Probable cause:
It is believed that the aircraft was approaching the airport at an excessive speed, too high and unstable.

Crash of a Cessna 501 Citation I/SP in Stella Maris

Date & Time: Feb 15, 2014 at 1640 LT
Type of aircraft:
Operator:
Registration:
C-GKPC
Survivors:
Yes
Schedule:
Fort Lauderdale - Stella Maris
MSN:
501-0253
YOM:
1983
Country:
Crew on board:
0
Crew fatalities:
Pax on board:
0
Pax fatalities:
Other fatalities:
Total fatalities:
0
Aircraft flight hours:
4579
Circumstances:
The aircraft belly landed at Stella Maris-Estate Airport, Bahamas. No one was hurt but the aircraft was damaged beyond repair. Apparently, the approach checklist was interrupted by the crew for unknown reason and the landing procedure was performed with the landing gear still retracted. The aircraft was owned by the private Canadian company Kelly Panteluk Construction and the airplane was inbound from Fort Lauderdale-Executive.

Crash of a BAe 125-700B in Moscow

Date & Time: Feb 12, 2014 at 1850 LT
Type of aircraft:
Operator:
Registration:
RA-02801
Flight Type:
Survivors:
Yes
Schedule:
Moscow - Moscow
MSN:
257097
YOM:
1980
Country:
Region:
Crew on board:
2
Crew fatalities:
Pax on board:
0
Pax fatalities:
Other fatalities:
Total fatalities:
0
Circumstances:
The crew departed Moscow-Sheremetyevo Airport on a positioning flight to Moscow-Vnukovo Airport. On approach by night, the crew configured the aircraft for landed when he realized that the right main gear remained stuck in its wheel well. The crew following a holding pattern and after the runway was covered with foam, he completed an emergency landing. After touchdown, the right wing contacted ground and the aircraft slid for few dozen metres before coming to rest. Both pilots escaped uninjured and the aircraft was damaged beyond repair.

Crash of a PAC Cresco 08-600 in Otane

Date & Time: Feb 4, 2014 at 0600 LT
Type of aircraft:
Operator:
Registration:
ZK-LTE
Survivors:
Yes
Schedule:
Otane - Otane
MSN:
029
YOM:
2001
Country:
Region:
Crew on board:
1
Crew fatalities:
Pax on board:
1
Pax fatalities:
Other fatalities:
Total fatalities:
0
Circumstances:
The pilot and the passenger were completing a top dressing mission in the region of Otane, south of Hastings, New Zealand. On final approach, the single engine aircraft seemed to be too low and hit tree tops before crashing nose down in a prairie. Both occupants were seriously injured and the aircraft was destroyed. It was dark at the time of the accident as the sunrise was computed at 0639LT.

Crash of a Cessna 525 CitationJet CJ1 in Elk City

Date & Time: Feb 3, 2014 at 2300 LT
Type of aircraft:
Operator:
Registration:
N61YP
Survivors:
Yes
Schedule:
Rapid City – Elk City
MSN:
525-0237
YOM:
1998
Crew on board:
1
Crew fatalities:
Pax on board:
6
Pax fatalities:
Other fatalities:
Total fatalities:
0
Captain / Total flying hours:
21550
Captain / Total hours on type:
592.00
Aircraft flight hours:
4798
Circumstances:
The airline transport pilot was conducting a business flight with six passengers on board. Radar data showed that, after crossing the final approach fix for an instrument approach at the destination airport, the airplane descended below the minimum descent altitude (MDA) of 2,480 ft mean sea level (msl); dark night, instrument meteorological conditions existed at that time. Subsequently, when the airplane was about 2 miles from the airport and about 2,070 ft msl, the airplane impacted a utility pole, which was 10 ft above ground level (agl). After impacting the pole, the pilot executed a missed approach, and about 40 minutes later, he landed the airplane without further incident at another airport. On-scene examination showed that the impact had scattered debris from the separated utility pole for about 200 ft into a snow-covered field. Examination of the airplane revealed that the impact resulted in substantial damage to the nose structure, lower and upper fuselage, and horizontal stabilizer. Further examinations of the airplane, including its static system, both altimeters, both vertical speed indicators, and the radar altimeter system revealed no evidence of preaccident mechanical malfunctions or failures that would have precluded normal operation. The pilot reported that he thought he had leveled the airplane at an altitude above the MDA and that at no time during the descent and approach did the airplane's radar altimeter sound an alert indicating that the airplane was below 400 ft agl radar altitude. He also reported that he never saw the terrain, any obstructions, nor the runway lights or airport environment. Despite the pilot's statement, given the radar data and the impact evidence, it is apparent that he descended the airplane below the MDA, which resulted in the subsequent impact with the utility pole. It could not be determined why the radar altimeter did not alert the pilot that the airplane was only 10 ft above the ground. The pilot's second-class medical certificate, which had been issued more than 20 months before the accident, had expired. The medical certificate limitation section in the expired certificate stated, "Not valid for night flying or by color signal control." There is no evidence that these restrictions contributed to the accident.
Probable cause:
The pilot's descent below the published minimum descent altitude for the instrument approach procedure, which resulted in impact with a utility pole.
Final Report:

Crash of a Beechcraft C90GTx King Air in Lanseria: 3 killed

Date & Time: Feb 3, 2014 at 0654 LT
Type of aircraft:
Operator:
Registration:
ZS-CLT
Survivors:
No
Schedule:
Johannesburg – Lanseria
MSN:
LJ-2011
YOM:
2011
Country:
Region:
Crew on board:
1
Crew fatalities:
Pax on board:
2
Pax fatalities:
Other fatalities:
Total fatalities:
3
Captain / Total flying hours:
1936
Captain / Total hours on type:
101.00
Aircraft flight hours:
500
Circumstances:
The pilot and two passengers were planning to fly from Rand Airport to Lanseria International Airport (FALA) in the early hours of the morning with the intention to clear customs. It was still dark and the weather forecast thunderstorms with rain for most areas of Gauteng. Rand Tower requested clearance from FAOR approach before departure. The aircraft took off from Runway 29 following the clearance given and proceeded in a westerly direction. At 6500 feet above mean sea level (AMSL), Rand handed the aircraft over to Approach for further clearances. Reported visibility at FALA was 600m and the cloud base was 600 feet AGL. The pilot then requested a VHF Omnidirectional range (VOR) Z approach for Runway 07. He started the approach at 8000 feet and approximately 14nm from LIV. At 12nm and established on Radial 245 Approach handed him over to FALA. Once in contact with FALA the pilot was advised of the heading to turn to at missed approach point (MAP). At MAP the pilot did not have the runway in sight and advised tower that they were going around. They turned left 360° and climbed to 8000 feet as instructed by FALA. FALA handed them back to Approach for repositioning for Radial 245. Approach advised the aircraft that visibility at Wonderboom was better but the pilot said if not successful they would route to Polokwane. At 12nm the aircraft was handed over to FALA. During the descent, the pilot started repeating messages more than twice. Close to MAP the pilot indicated that he had the field in sight. FALA gave them landing clearance. Soon after, the pilot said he did not have it in sight. When FALA instructed him to go around and route Polokwane, the pilot came back on frequency indicating that the aircraft was in distress. After that, the tower heard a loud bang accompanied by black smoke from behind a hangar.
Probable cause:
The accident was the consequence of a stall in adverse weather conditions after the pilot suffered a spatial disorientation during a missed approach procedure.
Final Report:

Crash of an Airbus A320-231 in Kulob

Date & Time: Feb 2, 2014 at 0736 LT
Type of aircraft:
Operator:
Registration:
EY-623
Survivors:
Yes
Schedule:
Moscow – Kulob
MSN:
428
YOM:
1994
Flight number:
ETJ704
Country:
Region:
Crew on board:
5
Crew fatalities:
Pax on board:
187
Pax fatalities:
Other fatalities:
Total fatalities:
0
Captain / Total flying hours:
18321
Captain / Total hours on type:
509.00
Copilot / Total flying hours:
2900
Copilot / Total hours on type:
1300
Aircraft flight hours:
54604
Aircraft flight cycles:
23974
Circumstances:
Following an uneventful flight from Moscow-Domodedovo Airport, the crew was cleared to land on runway 01 at Kulob Airport. In heavy snow falls, the aircraft landed 230 metres past the runway threshold at a speed of 255 km/h. After touchdown, the crew started the braking procedure when, after a course of 520 metres, the right main gear contacted a snow berm. Simultaneously, both engines impacted a snow berm (up to 95 cm high) and stopped due to the high quantity of snow ingested. The aircraft veered to the right, lost its nose gear and came to rest in snow, 20 metres to the right of the runway and 1,190 metres from its threshold. All 192 occupants evacuated safely and the aircraft was damaged beyond repair.
Probable cause:
The accident with A320-231 EY-623 aircraft was caused by the aircraft collision with snow parapet during landing on unprepared RWY that was cleared to 22 m in width (45 m RWY total width), and with 50-95 cm snow parapets along the cleared part that resulted in front gear leg destruction and engines flameout followed by aircraft runway overrun to the right. The accident was caused by the consequence of the following factors combination:
- flight operation officer decision for aircraft clearance on unprepared RWY,
- having unprepared RWY by the time of the aircraft arrival the aerodrome service didn't put temporary restrictions, didn't make the appropriate note in the "Aerodrome airworthiness log", didn't take any measures to prevent the aircraft landing on unprepared RWY.
Final Report:

Crash of a Piper PA-31-310 Navajo C in Aldinga

Date & Time: Jan 29, 2014 at 1132 LT
Type of aircraft:
Operator:
Registration:
VH-OFF
Flight Phase:
Flight Type:
Survivors:
Yes
Schedule:
Aldinga - Kangaroo Island
MSN:
31-7812064
YOM:
1978
Country:
Region:
Crew on board:
1
Crew fatalities:
Pax on board:
1
Pax fatalities:
Other fatalities:
Total fatalities:
0
Circumstances:
On 29 January 2014, at about 1100 Central Daylight-savings Time, the pilot prepared a Piper PA-31 aircraft, registered VHOFF, for a private flight from Aldinga aeroplane landing area (ALA) to Kangaroo Island, South Australia. To check fuel quantities, the pilot entered the cockpit, turned on the master switch and placed the left and right fuel selectors onto the main tank (inboard) position. The gauge for each tank showed just under half full. He then placed each fuel selector onto the auxiliary (outboard) tank position, where the gauge indicated the right and left auxiliary tanks were each about a quarter full. He did not return the selectors to the main tanks. He estimated that refuelling the main tanks would allow sufficient fuel for the flight with over an hour in reserve. He exited the aircraft while it was refuelled and continued preparing for the flight. Once refuelling was completed, the pilot conducted a pre-flight inspection, and finished loading the aircraft. The pilot and passenger then boarded. The pilot was familiar with Aldinga ALA, which is a non-controlled airport. At uncontrolled airports, unless a restriction or preference is listed for a certain runway in either the Airservices en route supplement Australia (ERSA), or other relevant publications, selection of the runway is the responsibility of the pilot. Operational considerations such as wind direction, other traffic, runway surface and length, performance requirements for the aircraft on that day, and suitable emergency landing areas in the event of an aircraft malfunction are all taken into consideration. On this day, the pilot assessed the wind to be favoring runway 14, which already had an aircraft in the circuit intending to land. However, he decided to use runway 03 due to the availability of a landing area in case of an emergency. He then completed a full run-up check of the engines, propellers and magnetos prior to lining up for departure. The pilot reported that all of the pre-take-off checks were normal. Once the aircraft landing on runway 14 was clear of the runway, the pilot went through his usual memory checklist prior to take-off. He scanned and crosschecked the flight and panel instruments, power quadrant settings and trims, but did not complete his usual final check, which was to reach down with his right hand and confirm that the fuel selector levers were on the main tanks. After broadcasting on the common traffic advisory frequency (CTAF) he commenced the take-off. At the appropriate speed, he rotated the aircraft as it passed the intersection of the 14 and 03 runways. Almost immediately both engines began surging, there was a loss of power, the power gauges fluctuated and the aircraft yawed from side to side. Due to the surging, fluctuating gauges and aircraft yaw, the pilot found it difficult to identify what he thought was a non-performing engine. He reported there were no warning lights so he retracted the landing gear, with the intent of getting the aircraft to attain a positive rate of climb, so he could trouble shoot further at a safe altitude. When a little over 50 ft above ground level (AGL), he realized the aircraft was not performing sufficiently, so he selected a suitable landing area. He focused on maintaining a safe airspeed and landed straight ahead. The aircraft touched down and slid about another 75-100 metres before coming to rest. The impact marks of the propellers suggest the aircraft touched the ground facing north-easterly and rotated to the north-west prior to stopping. The pilot turned off the master switch and both he and the passenger exited the aircraft. After a few minutes he re-entered the cockpit and completed the shutdown. Police and fire service attended shortly after the accident.
Probable cause:
Engine malfunction due to fuel starvation.
Final Report: