Crash of a Raytheon 390 Premier IA in New Delhi

Date & Time: Sep 22, 2012 at 1129 LT
Type of aircraft:
Operator:
Registration:
VT-UPN
Flight Type:
Survivors:
Yes
Schedule:
Lucknow - New Delhi
MSN:
RB-236
YOM:
2008
Country:
Region:
Crew on board:
3
Crew fatalities:
Pax on board:
3
Pax fatalities:
Other fatalities:
Total fatalities:
0
Circumstances:
The aircraft departed Lucknow Airport in the morning on a flight to New Delhi-Indira Gandhi Airport with a crew of three (two pilot and a cabin crew) and three passengers, among them Shivpal Yadav, Minister by the Uttar Pradesh Government. Following an uneventful flight, the crew completed the approach to runway 27. After touch down, the left main gear collapsed and the aircraft slid on runway for about one km when the right main gear collapsed as well. Out of control, the aircraft veered off runway to the right and came to rest in a grassy area. All six occupants escaped uninjured while the aircraft was damaged beyond repair.

Crash of a Beechcraft Beechjet 400A in Macon

Date & Time: Sep 18, 2012 at 1003 LT
Type of aircraft:
Operator:
Registration:
N428JD
Survivors:
Yes
Schedule:
Charleston - Macon
MSN:
RJ-13
YOM:
1986
Location:
Crew on board:
2
Crew fatalities:
Pax on board:
1
Pax fatalities:
Other fatalities:
Total fatalities:
0
Captain / Total flying hours:
7000
Captain / Total hours on type:
4000.00
Copilot / Total flying hours:
2500
Copilot / Total hours on type:
450
Aircraft flight hours:
5416
Circumstances:
The aircraft was substantially damaged when it overran runway 28 during landing at Macon Downtown Airport (MAC), Macon, Georgia. The airplane departed from Charleston Air Force Base/International Airport (CHS), Charleston, South Carolina, about 0930. Visual meteorological conditions prevailed and an instrument flight rules (IFR) flight plan was filed. Both Airline Transport Pilots (ATP) and one passenger sustained minor injuries. The airplane was owned by Dewberry, LLC and operated by The Aviation Department. The corporate flight was conducted under the provisions of Title 14 Code of Federal Regulations (CFR) Part 91. According to an interview with the pilots, they arrived at DeKalb-Peachtree Airport (PDK), Atlanta, Georgia, which was their home base airport, about 0400, and then drove about 4 1/2 hours to CHS for the 0930 flight. The flight departed on time, the airspeed index bug was set on the co-pilot's airspeed for a decision takeoff speed (V1) of about 102 knots and a single engine climb speed (V2) on the pilot's side of 115 knots. The flight climbed to 16,000 feet prior to beginning the descent into MAC. When the flight was about 11 miles from the airport the flight crew visually acquired the airport and cancelled their IFR clearance with the Macon Radar Approach controller and proceeded to the airport visually. The second-in-command activated the runway lights utilizing the common traffic advisory frequency for the airport. Both crew members reported that about 3 seconds following activation of the lights and the precision approach path indicator (PAPI) lights, the PAPI lights turned off and would not reactivate. During the approach, the calculated reference speed (Vref) was 108 knots and was set on both pilots' airspeed indicator utilizing the index bug that moved around the outside face of the airspeed instrument. The landing was within the first 1,000 feet of the runway and during the landing roll out the airplane began to "hydroplane" since there was visible standing water on the runway and the water was "funneling into the middle." Maximum reverse thrust, braking, and ground spoilers were deployed; however, both pilots reported a "pulsation" in the brake system. The airplane departed the end of the runway into the grass, went down an embankment, across a road, and into trees. They further added that the airplane "hit hard" at the bottom of the embankment. They also reported that there were no mechanical malfunctions with the airplane prior to the landing. According to an eyewitness statement, a few minutes prior to the airplane landing, the airport experienced a rain shower with a "heavy downpour." The witness reported observing the airplane on approach, heard the engine thrust reverse, and then observed the airplane "engulfed in a large ball of water vapor." However, he did not observe the airplane as it departed the end of the runway. Another witness was located in a hangar on the west side of the airport and heard the airplane, looked outside and then saw the airplane with the reverse thrusters deployed. He watched it depart the end of the runway and travel into the nearby woods.
Probable cause:
The pilot’s failure to maintain proper airspeed, which resulted in the airplane touching down too fast on the wet runway with inadequate runway remaining to stop and a subsequent runway overrun. Contributing to the landing overrun were the flight crew members’ failure to correctly use the appropriate performance chart to calculate the runway required to stop on a contaminated runway and their general lack of proper crew resource management.
Final Report:

Crash of a Learjet 24D in Rønne

Date & Time: Sep 15, 2012 at 1340 LT
Type of aircraft:
Operator:
Registration:
D-CMMM
Flight Type:
Survivors:
Yes
Schedule:
Strausberg - Rønne
MSN:
24-328
YOM:
1976
Country:
Region:
Crew on board:
2
Crew fatalities:
Pax on board:
0
Pax fatalities:
Other fatalities:
Total fatalities:
0
Circumstances:
The accident occurred during a private IFR flight from Strausberg Airport (EDAY), Germany, to Bornholm Airport (EKRN), Denmark. Before the flight, an ATS flight plan was filed. Before takeoff at EDAY, the aircraft was refueled with 200 liters of jet fuel. According to the ATS flight plan, the pilot stated the total endurance to be 01:30 hrs and the Estimated Elapsed Time (EET) to be 00:30 hrs. The pilot informed the AIB DK that the estimated total endurance before takeoff at EDAY was approximately 01:00 hrs. The aircraft departed EDAY at 10:58. Enroute, the pilot observed a low fuel quantity warning light. Otherwise, the flight was uneventful until the approach to EKRN. At 11:32:00 hrs and at a distance of approximately18 nm southwest of EKRN, the pilot cancelled the IFR flight plan and continued VFR for a visual approach to runway 29. While descending inbound EKRN, the airspeed was decreasing. At 11:37:08 hrs, the pilot reported to Roenne Tower that the aircraft was turning final for runway 29. The aircraft was cleared to land. The wind conditions were reported to be 280° 19 knots maximum 29 knots. The aircraft was configured for landing (the landing gear was down and the flaps extended to 40°). On a left base to runway 29, both engines suffered from fuel starvation. At 11:39:18 hrs, the pilot three times declared an emergency. The aircraft entered a stall and impacted terrain in a field of sweet corn. A search and rescue mission was immediately initiated.
Probable cause:
CONCLUSION:
Inadequate en route fuel management resulted in fuel starvation of both engines, while the aircraft was flying at low altitude and the airspeed was decreasing. The dual engine flame out and the subsequent aircraft speed control led to an unrecoverable stall and consequently caused the accident.
FINDINGS:
On board the aircraft in the pilot’s personal belongings, the AIB DK found 2 Airline Transport Pilot Licenses (ATPL) issued by the US Federal Aviation Administration (FAA). The 2 US ATPL licenses had the same FAA license number but the names of the license holders were different. The names of the license holders were inconsistent with the pilot’s Iranian identity.
The BFU informed the AIB DK that the pilot was neither in possession of a valid German pilot license nor a German validation of an US license, which was required to operate a German registered aircraft.
The NTSB informed the AIB DK that the pilot was not in possession of a valid US pilot license.
It has not been possible for the AIB DK to determine whether or not the pilot was in possession of valid pilot license issued by another state.
The BFU informed the AIB DK that the certificate of aircraft registration was cancelled in 2009. Later on in the investigation, the BFU corrected this information. On February 2nd , 2012 and due to a missing airworthiness certificate, the Luftfahrt-Bundesamt (CAA - Germany) revoked the certificate of aircraft registration.
The latest valid airworthiness certificate was issued on the 8th of March 2004 and expired on the 31st of March 2005.
At the time of the accident, the aircraft was not recorded to be maintained by a JAR 145 maintenance organization, a maintenance program or a Continuing Airworthiness Management Organization (CAMO).
Final Report:

Crash of a PZL-Mielec AN-28 in Palana: 10 killed

Date & Time: Sep 12, 2012 at 1220 LT
Type of aircraft:
Operator:
Registration:
RA-28715
Survivors:
Yes
Schedule:
Petropavlovsk-Kamchatsky - Palana
MSN:
1AJ006-25
YOM:
1989
Flight number:
PTK251
Country:
Region:
Crew on board:
2
Crew fatalities:
Pax on board:
12
Pax fatalities:
Other fatalities:
Total fatalities:
10
Captain / Total flying hours:
8955
Captain / Total hours on type:
7732.00
Copilot / Total flying hours:
6543
Copilot / Total hours on type:
6347
Aircraft flight hours:
11947
Aircraft flight cycles:
8891
Circumstances:
Following an uneventful flight from Petropavlovsk-Kamchatsky, the crew started the descent to Palana Airport Runway 11 from the south. In marginal weather conditions, the twin engine aircraft descended too low, impacted trees and crashed in a wooded area located on Mt Pyatibratka. The wreckage was found at a height of 216 meters some 10 km south of the airport. Both pilots and 8 passengers were killed while four other passengers were seriously injured. Thea aircraft was destroyed by impact forces.
Probable cause:
The fatal accident with An-28 RA-28715 aircraft was caused by violation of specified approach pattern in Palan Airport resulted in outbound track and premature descending up to unauthorized low altitude performing flight in mountainous terrain in weather conditions excluding sustained visual reference with ground references resulted in aircraft collision with mountain slope, its destruction and crew and passengers fatality. Alcohol was detected in blood of both crew members.
Contributing factors were:
- Low level of discipline of personnel in Petropavlovsk-Kamchatsky Air Enterprise and inadequate flight methodical work in enterprises in a part of crew preflight training and approach patterns monitoring.
- Crew inaction when the radio altimeter altitude alert was actuated.
- Ground Proximity Warning System at An-28 aircraft could probably prevent the accident.
Final Report:

Crash of a Beechcraft King Air 90 in Lohegaon

Date & Time: Sep 7, 2012 at 2000 LT
Type of aircraft:
Operator:
Registration:
VT-KPC
Flight Type:
Survivors:
Yes
Schedule:
Lohegaon - Lohegaon
MSN:
LJ-1696
YOM:
2005
Country:
Region:
Crew on board:
3
Crew fatalities:
Pax on board:
0
Pax fatalities:
Other fatalities:
Total fatalities:
0
Circumstances:
The crew was completing a local training mission at Lohegaon Airport. On final approach to runway 28, the aircraft impacted ground, teared off several runway lights and came to rest. All three occupants escaped uninjured while the aircraft was damaged beyond repair.

Crash of a Cessna 402B in Rome: 2 killed

Date & Time: Sep 7, 2012 at 1300 LT
Type of aircraft:
Operator:
Registration:
I-ERJA
Flight Phase:
Flight Type:
Survivors:
No
Schedule:
Rome - Brescia
MSN:
402B-0918
YOM:
1975
Country:
Region:
Crew on board:
2
Crew fatalities:
Pax on board:
0
Pax fatalities:
Other fatalities:
Total fatalities:
2
Circumstances:
Shortly after takeoff from Rome-Ciampino Airport, while in initial climb, the twin engine aircraft went out of control and crashed in a car demolition, bursting into flames. The aircraft was totally destroyed by impact forces and a post impact fire as well as more than 30 cars. Both crew were killed.

Crash of a Cessna 421B Golden Eagle II in Fort Worth

Date & Time: Sep 5, 2012 at 0949 LT
Operator:
Registration:
N69924
Flight Phase:
Flight Type:
Survivors:
Yes
Schedule:
Fort Worth - San Antonio
MSN:
421B-0553
YOM:
1973
Crew on board:
2
Crew fatalities:
Pax on board:
0
Pax fatalities:
Other fatalities:
Total fatalities:
0
Captain / Total flying hours:
3800
Captain / Total hours on type:
897.00
Aircraft flight hours:
10056
Circumstances:
The commercial pilot was distracted by the nose cargo door popping open during takeoff; the airplane stalled and collided with trees off the end of the runway. The pilot said there were no mechanical problems with the airplane or engines and that he was fixated on the cargo door and lost control of the airplane. He also said that due to stress, he was not mentally prepared to handle the emergency situation.
Probable cause:
The pilot's failure to maintain airplane control on takeoff, which resulted in an inadvertent stall. Contributing to the accident were the unlatched nose cargo door, the pilot’s diverted attention, and the pilot's mental ability to handle the emergency situation.
Final Report:

Crash of an ATR42-500 in Lahore

Date & Time: Aug 31, 2012 at 1510 LT
Type of aircraft:
Operator:
Registration:
AP-BHJ
Survivors:
Yes
Schedule:
Islamabad - Lahore
MSN:
657
YOM:
2006
Flight number:
PK653
Country:
Region:
Crew on board:
4
Crew fatalities:
Pax on board:
42
Pax fatalities:
Other fatalities:
Total fatalities:
0
Circumstances:
Following an uneventful flight from Islamabad, the crew started the descent to runway 36R in marginal weather conditions. Upon touchdown on a wet runway, the right main gear collapsed. The aircraft slid for about 1,700 feet before exiting the runway to the right and coming to rest 60 feet further on. All 46 occupants were unhurt while the aircraft was considered as damaged beyond repair. Five minutes after the accident, the weather briefing was as follow: OPLA 311015Z 16009KT 3000 RA BKN040 OVC100 29/24 Q1003. But ten minutes prior to the crash, the weather briefing was as follow: OPLA 311000Z 33008KT 4000 -RA SCT040 BKN100 32/24 Q1002 TEMPO 31030KT 2000 TSRA FEW030CB. Thus, the conditions were considered as marginal with turbulences, wind to 30 knots and CB's at 3,000 feet. On 11SEP2012, the French BEA reported that the aircraft touched down just at the beginning of the paved surface (undershoot area) to the right of the extended runway 36R centerline, causing the right main gear to collapse. It was reported that the aircraft was unstable on short final and that the crew failed to initiate a go-around procedure while the aircraft was too low on the glide.

Crash of a Cessna 421A Golden Eagle I at Annino AFB: 2 killed

Date & Time: Aug 22, 2012 at 1517 LT
Type of aircraft:
Operator:
Registration:
RA-0879G
Flight Phase:
Flight Type:
Survivors:
No
Schedule:
Annino - Annino
MSN:
421A-0075
YOM:
1968
Country:
Region:
Crew on board:
2
Crew fatalities:
Pax on board:
0
Pax fatalities:
Other fatalities:
Total fatalities:
2
Circumstances:
In the afternoon, the crew departed Annino AFB (Gorelovo) to complete a local training mission consisting of touch-and-go maneuvers. After two circuits, the aircraft landed normally and the crew took off and started the rotation without informing ATC. After liftoff, at a height of about 10-15 metres, the aircraft rolled to the right to an angle of 70° then stalled and crashed in a kindergarten located one km from the airport, bursting into flames. The aircraft was destroyed and both pilots were killed.
Probable cause:
Most probably the accident with С-421 (FVSP) RA-0879G aircraft was caused by right and then left engine flameout during touch-and-go landing, flight speed decrease and aircraft stall entry resulted in aircraft ground impact with bank angle over 70°. Most probably engines flameout midair was caused by fuel-air mixture depletion due to low level of fuel in aircraft tanks that in combination with its inadequate quality resulted in engines trouble.
Combination of the following factors could contribute to the accident:
- Flight operation with low level of fuel on board.
- Inadequate fuel quality.
- Inadequate crew training for forthcoming flight.
- Inadequate maintenance prior to aircraft familiarization flight after its long-term parking.
- Touch-and-go landing and continued takeoff with engines trouble during run operation.
- Non-feathering of switched-off engine propeller midair (non compliance with requirement of clause "2" of subsection 3 of «ENGINE INOPERATIVE PROCEDURE» section aircraft FOM).
- Possible on position failure of fuel booster pump switches by crew before aircraft take-off.
- Inadequate flight operation management, aircraft maintenance and efficiency discipline in "Aviator" Airclub" LLC, weak monitoring from senior staff over maintenance operation on accident prevention.
- The flight was performed by crew on aircraft without airworthiness certificate (violation of clause 1 article 35 of Air Code of RF and clause 1 of FAR-118).

Crash of a Let L-410UVP-E9 in Ngerende: 4 killed

Date & Time: Aug 22, 2012 at 1220 LT
Type of aircraft:
Operator:
Registration:
5Y-UVP
Flight Phase:
Survivors:
Yes
Schedule:
Amboseli – Ngerende – Mara North – Ukunda – Mombasa
MSN:
91 26 27
YOM:
1991
Country:
Region:
Crew on board:
2
Crew fatalities:
Pax on board:
11
Pax fatalities:
Other fatalities:
Total fatalities:
4
Captain / Total flying hours:
7480
Captain / Total hours on type:
1150.00
Copilot / Total flying hours:
312
Circumstances:
This was a commercial non scheduled flight which was being operated for air transport for local flights. The operator is based in Mombasa and mostly executes passenger flights to the Masai Mara and other game parks and reserves within the Republic of Kenya. On 22nd Aug 2012, the aircraft was scheduled to carry out a flight to the Masai Mara, do several sectors to pick and drop passengers and return to Moi international Airport via Ukunda Airport. The call sign was 5Y-UVP. The last point of departure was Ngerende Airstrip in the Masai Mara at 0917 with intention of onward flight to Mara North airstrip in the Masai Mara. The flight had earlier left Amboseli Airstrip with two crew, and 17 passengers for Ngerende Airstrip. 6 passengers had disembarked at Ngerende and the remaining 11 passengers were continuing to other destinations. No additional passengers or cargo was picked up from Ngerende airstrip. No refueling was done at the airstrip. The airfield is an unmanned airfield, with crew executing unmanned airfield communication procedures to execute approach and landings and also during takeoff. There is however a ground time keeper and a fueling bay at the airfield. Due to terrain and prevailing winds at the time of the flight, Runway 28 was in use. The crew was using unmanned airfield procedures and after the drop-off of 6 passengers, the aircraft lined up runway 28 and proceeded with the take off run. Ground staff at the airstrip reported a normal takeoff run and rotation. During the initial climb, the ground staff still had the aircraft in sight and reported to have seen the aircraft veer sharply to the left and then disappear behind terrain. Shortly afterwards, a loud sound was heard followed by dust in the air. Emergency SAR was initiated with the airport and hotel staff rushing to the accident site. The location of the accident was about 310 meters from the threshold of Runway 10, offset 30° to the left of the extended center line Runway 28. GPS coordinates (figure 1.2) 01.084189° S, 35.1781127° E, Ngerende airstrip. The accident occurred at 0917 UTC on 22nd Aug 2012, during daytime.
Probable cause:
The following findings were identified:
- The left engine was most probably not developing power at the time of impact,
- The left engine propeller was most probably in feather at the time of impact,
- Both CVR and FDR were unserviceable at the time of the accident,
- AAID was unable to determine origin of contaminant found in the left engine Fuel Control Unit,
- Sufficient oversight was not exercised over the Operator,
- High turnover of the Operator’s staff.
Final Report: