Crash of a Beechcraft Beechjet 400A in Rome

Date & Time: Mar 14, 2016 at 1508 LT
Type of aircraft:
Operator:
Registration:
N465FL
Flight Type:
Survivors:
Yes
Schedule:
Jackson - Rome
MSN:
RK-426
YOM:
2005
Crew on board:
2
Crew fatalities:
Pax on board:
0
Pax fatalities:
Other fatalities:
Total fatalities:
0
Captain / Total flying hours:
10393
Captain / Total hours on type:
6174.00
Copilot / Total flying hours:
6036
Copilot / Total hours on type:
407
Aircraft flight hours:
7061
Circumstances:
The pilots of the business jet were conducting a cross-country positioning flight. According to the pilot flying (PF), the flight was uneventful until the landing. While completing the descent checklist and while passing through 18,000 ft mean sea level (msl), the pilot monitoring (PM), received the automated weather report from the destination airport and briefed the PF that the wind was variable at 6 knots, gusting to 17 knots. The PF then programmed the flight management system for a visual approach to runway 7 and briefed the reference speed (Vref) as 107 knots and the go-around speed as 129 knots based on an airplane weight. The PF further reported that he knew the runway was over 4,400 ft long (the runway was 4,495 ft long) and he thought that the airplane needed about 2,900 ft of runway to safely land. During the left descending turn to the base leg of the traffic pattern, the PF overshot the final approach and had to turn back toward the runway centerline as the airplane was being “pushed by the winds.” About 500 ft above ground level (agl), both pilots acknowledged that the approach was “stabilized” while the airspeed was fluctuating between 112 and 115 knots. About 200 ft agl, both pilots noticed that the airplane was beginning to descend and that the airspeed was starting to decrease. The PF added power to maintain the descent rate and airspeed. The PF stated that, after adding power and during the last 200 ft of the approach, the wind was “gusty,” that a left crosswind existed, that the ground speed seemed “very fast,” and that excessive power was required to maintain airspeed. When the airplane was between about 75 and 100 ft agl, the PF asked the PM for the wind information, and the PM responded that the wind was variable at 6 knots, gusting to 17 knots. Both pilots noted that the ground speed was “very fast” but decided to continue the approach. Neither pilot reported seeing the windsock located off the right side of the runway. Review of weather data recorded by the airport’s automated weather observation system revealed that about 3 minutes before the landing, the wind was from 240° at 16 knots, gusting to 26 knots, which would have resulted in a 3- to 5-knot crosswind and 16- to 26-knot tailwind. Assuming these conditions, the airplane’s landing distance would have been about 4,175 ft per the unfactored landing distance performance chart. Tire skid marks were found beginning about 1,000 feet from the approach end of runway 7. The PF stated that the airplane touched down “abruptly at Vref+5 and he applied the brakes while the PM applied the speed brakes. Neither pilot felt the airplane decelerating, so the PF applied harder pressure to the brakes with no effect and subsequently applied full braking pressure. When it was evident that the airplane was going to depart the end of the runway, the PM applied the emergency brakes, at which point he felt some deceleration; however, the airplane overran the end of the runway and travelled through grass and mud for about 370 feet before stopping. Examination of the airplane revealed that the nose landing gear (NLG) had collapsed, which resulted in the forward fuselage striking the ground and the airframe sustaining substantial damage. Although the pilots reported that they never felt the braking nor antiskid systems working and that they believed that they should have been able to stop the airplane before it departed the runway, postaccident testing of the brake and antiskid systems revealed no evidence of preaccident mechanical malfunctions or failures that would have precluded normal operation, and they functioned as designed. Given the tire skid marks observed on the runway following the accident, as well as the postaccident component examination and testing results, the brakes and antiskid system likely operated nominally during the landing. Based on the available evidence, the pilots failed to recognize performance cues and use available sources of wind information that would have indicated that they were landing in significant tailwind conditions and conduct a go-around. Landing under these conditions significantly increased the amount of runway needed to stop the airplane and resulted in the subsequent runway overrun and the collapse of the NLG.
Probable cause:
The pilots’ failure to use available sources of wind information before landing and recognize cues indicating the presence of the tailwind and conduct a go-around, which resulted in their landing with a significant tailwind and a subsequent runway overrun.
Final Report:

Ground accident of a Pilatus PC-12/47E in Savannah

Date & Time: Jan 6, 2016 at 0835 LT
Type of aircraft:
Operator:
Registration:
N978AF
Flight Phase:
Flight Type:
Survivors:
Yes
Schedule:
Savannah - Lexington
MSN:
1078
YOM:
2008
Flight number:
Cobalt Air 727
Crew on board:
2
Crew fatalities:
Pax on board:
0
Pax fatalities:
Other fatalities:
Total fatalities:
0
Captain / Total flying hours:
23141
Captain / Total hours on type:
534.00
Copilot / Total flying hours:
7900
Copilot / Total hours on type:
5100
Aircraft flight hours:
4209
Circumstances:
The aircraft collided with a ditch during a precautionary landing after takeoff from Savannah/Hilton Head International Airport (SAV), Savannah, Georgia. The pilot and copilot sustained minor injuries, and the airplane was substantially damaged. The airplane was registered to Upper Deck Holdings, Inc. and was being operated by PlaneSense, Inc,. as a Title 14 Code of Federal Regulations Part 91 positioning flight. Visual meteorological conditions prevailed, and an instrument flight rules flight plan was filed for the flight to Blue Grass Airport (LEX), Lexington, Kentucky. The pilot in the left seat was the pilot monitoring and the copilot in the right seat was the pilot flying. The crew had the full length of the runway 1 available (7,002 ft) for takeoff. The pilots reported that the acceleration and takeoff was normal and after establishing a positive rate of climb, the crew received an auditory annunciation and a red crew alerting system (CAS) torque warning. The engine torque indicated 5.3 pounds per square inch (psi); the nominal torque value for the conditions that day was reported by the crew to be 43.3 psi. With about 2,700 ft of runway remaining while at an altitude of 200 ft msl, the copilot elected to land immediately; the copilot pushed the nose down and executed a 90° left descending turn and subsequently landed in the grass. Although he applied "hard" braking in an attempt to stop, the airplane impacted a drainage ditch, resulting in substantial impact damage and a postimpact fire. The pilot reported that, after takeoff, he observed a low torque CAS message and the copilot told him to "declare an emergency and run the checklist." The pilot confirmed that the landing gear were extended and the copilot turned the airplane to the left toward open ground between the runways and the terminal. About 60 seconds elapsed from the start of the takeoff roll until the accident. The airport was equipped with security cameras that captured the airplane from its initial climb through the landing and collision. One camera, pointed toward the west-southwest, recorded the airplane's left descending turn and its landing in the grass, followed by impact and smoke. A second camera, mounted on the control tower, pointed toward the southeast and showed the airplane during the initial climb before it leveled off and entered a descending left turn; it also showed the airplane land and roll through the grass before colliding with the ditch.
Probable cause:
The pilots' failure to follow proper procedures in response to a crew alerting system warning for high engine torque values, which necessitated an off-runway emergency landing during which the airplane sustained substantial damage due to postimpact fire. Contributing to the accident was the erroneous engine torque indication for reasons that could not be determined.
Final Report:

Crash of a Beechcraft C90GTi King Air in Paraty: 2 killed

Date & Time: Jan 3, 2016 at 1430 LT
Type of aircraft:
Operator:
Registration:
PP-LMM
Flight Type:
Survivors:
No
Site:
Schedule:
Campo de Marte - Paraty
MSN:
LJ-1866
YOM:
2008
Country:
Crew on board:
2
Crew fatalities:
Pax on board:
0
Pax fatalities:
Other fatalities:
Total fatalities:
2
Captain / Total flying hours:
801
Captain / Total hours on type:
319.00
Copilot / Total flying hours:
159
Circumstances:
The twin engine aircraft departed Campo de Marte Airport at 1334LT on a positioning flight to Paraty, with an ETA at 1415LT. While descending to Paraty Airport, the crew encountered instrument meteorological conditions. On final, while approaching under VFR mode, the aircraft impacted trees and crashed in a dense wooded area located in hilly terrain few km short of runway. The aircraft was destroyed and both pilots were killed.
Probable cause:
Contributing factors:
- Attention - undetermined
Moments before the accident, another aircraft successfully completed the landing at the Paraty aerodrome. It is possible that the pilot's attention was focused on this information, which indicated the possibility of landing, despite the critical conditions faced, leading him to take high risks to make the landing in critical conditions.
Also, the presence of a copilot not qualified to operate the aircraft may have influenced the pilot's cognitive processes, causing deconcentration or deviation of attention from the pilot.
- Attitude - contributed
Recurring attempts to make the landing indicated an excess of self-confidence on the part of the pilot, leading him to continue the flight to the Paraty aerodrome, even in adverse weather conditions.
The bold operational profile of the pilot, his past experience and the rules and values ​​adopted informally in the group of pilots are possible factors that influenced the development of this attitude of excessive self-confidence.
- Adverse weather conditions - contributed
On the day of the accident, the weather conditions were not favorable for visual flight at the Paraty aerodrome.
- Culture of the working group - contributed
Among the pilots who operated in the Paraty region, competitive behavior had been installed, valued by the social recognition attributed to those who managed to operate in critical conditions. Above all, landing under conditions adverse weather conditions in the region was considered a manifestation of proficiency and professional competence. The values ​​shared by that group of pilots favored the weakening of the collective perception about the present operational risks. The presence of other pilots who were also trying to land in the region on the day of the occurrence, as well as the landing made by one of these aircraft, moments before the accident, and also the accomplishment of two failed attempts of the PP-LMM aircraft, translates clear evidence of that behavior.
- Pilot forgetfulness - undetermined
The fact that the landing gear was not retracted during the second launch in the air indicated a failure, fueled by the possible forgetfulness of the crew, to perform the planned procedure. Maintaining the landing gear in the lowered position affected the aircraft's performance during the ascent, which may have contributed to the aircraft not reaching the height required to clear obstacles.
- Pilotage Judgment - undetermined
The possible decision not to retract the landing gear during the launch affected the aircraft's performance during the climb, which may have contributed to the aircraft not reaching the height necessary to clear the obstacles.
- Motivation - undetermined
The successful landing by the pilot of another aircraft, even under unfavorable conditions, may have increased the motivation of the pilot of the PP-LMM aircraft to complete the landing, in order to demonstrate his proficiency and professional competence.
- Perception - contributed
The occurrence of a collision with the ground, in controlled flight, indicated that the crew had a low level of situational awareness at the time of the occurrence. This inaccurate perception of the circumstances of the flight made it impossible to adopt the possible measures that could prevent the collision.
- Decision making process - contributed
The pilot chose to make two landing attempts at the Paraty aerodrome, despite adverse weather conditions, indicating an inaccurate assessment of the risks involved in the operation. This evaluation process may have been adversely affected by the competition behavior installed among the pilots. In this context, it is possible that the pilot based his decision only on the successful landing of another aircraft, a fact that limited his scope of evaluation.
- Organizational processes - undetermined
The PP-LMM aircraft was operated by a group of pilots, mostly composed of freelance professionals, who were informally managed by a hired pilot. Therefore, there was no formal system used by the operator to recruit, select, monitor and evaluate the performance of professionals. The failures related to the management of this process, possibly, caused inadequacies in the selection of pilots, in the crew scale, in untimely activations and, as in the case in question, in the choice of crew member not qualified to exercise function on board.
Final Report:

Crash of a BAe 125-800SP in Palm Springs

Date & Time: Dec 4, 2015 at 1420 LT
Type of aircraft:
Registration:
N164WC
Flight Type:
Survivors:
Yes
Schedule:
Palm Springs – Boise
MSN:
258072
YOM:
1986
Crew on board:
2
Crew fatalities:
Pax on board:
0
Pax fatalities:
Other fatalities:
Total fatalities:
0
Aircraft flight hours:
2500
Circumstances:
After takeoff from Palm Springs Airport, while on a positioning flight to Boise, the crew encountered technical problems with the undercarriage. Following a holding circuit, the crew decided to return to Palm Springs and to complete a gear up landing. Upon touchdown, the aircraft slid on its belly for few dozen metres before coming to rest. Both pilots evacuated safely and the aircraft was damaged beyond repair.
Probable cause:
No investigations completed by the NTSB.

Crash of a Learjet 60 in Zihuatanejo

Date & Time: Nov 16, 2015 at 1622 LT
Type of aircraft:
Operator:
Registration:
XA-UQP
Flight Type:
Survivors:
Yes
Schedule:
Toluca - Zihuatanejo
MSN:
60-202
YOM:
2001
Country:
Crew on board:
2
Crew fatalities:
Pax on board:
0
Pax fatalities:
Other fatalities:
Total fatalities:
0
Captain / Total flying hours:
7673
Captain / Total hours on type:
1360.00
Copilot / Total flying hours:
9592
Copilot / Total hours on type:
3100
Aircraft flight hours:
3676
Circumstances:
The crew departed Toluca Airport on a positioning flight to Zihuatanejo. Following an uneventful flight, the crew was cleared for a VOR approach to runway 26. Due to the formation of clouds in the vicinity of the airport, ATC changed the clearance and instructed the crew for a VOR/DME approach to runway 08. Following an unstabilized approach, the aircraft landed on a wet runway. After touchdown, the aircraft skidded and veered off runway to the left. In a grassy area, the left main gear impacted a concrete block hosting the electrical system for the runway and was torn off. Then the aircraft slid for few dozen metres before coming to rest. Both pilots evacuated safely and the aircraft was damaged beyond repair.
Probable cause:
Runway excursion due to loss of directional control of the aircraft during the landing run on an unstabilized approach.
The following contributing factors were identified:
a) Unstabilized approach,
b) Adverse atmospheric conditions in the "W" area of the airport,
c) Change of designation of runway in use for landing,
d) Lack of adherence to standard operating procedures "SOPS",
e) Lack of adherence to the concepts of "CRM" resource management in the cockpit,
f) Decreased situational awareness on the part of the commander of the aircraft,
g) Flying the approach and descent visually, following an IFR descent within IMC conditions (Instrument Meteorological Conditions),
h) Wet track,
i) Lack of crew coordination,
j) Poor judgement and incorrect decision,
k) Existence of a concrete marker with a level of 10cms protruding above the road surface in the runway safety zone.
Final Report:

Crash of a Learjet 35A in San Fernando

Date & Time: Oct 19, 2015 at 0640 LT
Type of aircraft:
Registration:
LV-ZSZ
Flight Phase:
Flight Type:
Survivors:
Yes
Schedule:
San Fernando - Rio Gallegos
MSN:
35A-235
YOM:
1979
Country:
Crew on board:
2
Crew fatalities:
Pax on board:
0
Pax fatalities:
Other fatalities:
Total fatalities:
0
Captain / Total flying hours:
9851
Captain / Total hours on type:
6200.00
Copilot / Total flying hours:
1100
Copilot / Total hours on type:
39
Aircraft flight hours:
12190
Aircraft flight cycles:
9517
Circumstances:
The aircraft departed Buenos Aires-San Fernando Airport on a positioning flight to Río Gallegos, carrying two pilots. During the takeoff roll, the copilot (pilot-in-command) noticed that the left engine N1 reached a value of 101% instead of 95% like the right engine. At that point the aircraft had already traveled 380 metres. As the aircraft started to veer to the right, the copilot decided to abandon the takeoff procedure without informing the captain. The power levers were brought back to idle and the copilot started to brake. After a course of about 980 metres, the right engine N1 value dropped to 30-40% while the left engine remained at 101%. Then the captain took over control, deployed briefly the thrust reverser system when the aircraft departed the runway to the right. While rolling in a grassy area, it struck a drainage ditch located 80 metres from the runway, lost its undercarriage then slid for few dozen metres before coming to rest, bursting into flames. Both pilots evacuated safely while the aircraft was destroyed by a post crash fire.
Probable cause:
The most likely cause of the uncommanded acceleration and subsequent overspeed condition was a contamination of retained particles present within the fuel control unit (FCU). The contamination was a short-lived random condition, as evidenced by the fact that after about 30 seconds the power lever regained control of the left engine. On a general aviation flight, during the take-off run, the LJ35 LV-ZSZ suffered a runway excursion on the right side, and a subsequent aircraft fire.
The accident was due to the combination of the following factors:
- The uncommanded acceleration of the left engine at the start of the take-off run,
- The initial lack of response of the left engine to the requests of the corresponding power lever,
- The difficulties of the crew in managing an unusual condition of the aircraft in accordance with guidelines established in the AFM,
- The ambivalence in the existing regulations for the authorization of a co-pilot in an aircraft that require two pilots for certification,
- The duality in the application of safety standards allowed by the existing normative regulations.
Although unrelated, the state of the runway 05/23 protection zone at the San Fernando Aerodrome contributed to the severity of the accident.
Final Report:

Crash of a Beechcraft B200 Super King Air in Chigwell: 2 killed

Date & Time: Oct 3, 2015 at 1020 LT
Operator:
Registration:
G-BYCP
Flight Phase:
Flight Type:
Survivors:
No
Schedule:
Stapleford - Brize Norton
MSN:
BB-966
YOM:
1982
Region:
Crew on board:
1
Crew fatalities:
Pax on board:
1
Pax fatalities:
Other fatalities:
Total fatalities:
2
Captain / Total flying hours:
1941
Captain / Total hours on type:
162.00
Aircraft flight hours:
14493
Aircraft flight cycles:
12222
Circumstances:
G-BYCP was planned to operate a non-commercial flight from Stapleford Aerodrome to RAF Brize Norton with two company employees on board (including the pilot) to pick up two passengers for onward travel. The pilot (the aircraft commander) held a Commercial Pilot’s Licence (CPL) and occupied the left seat and another pilot, who held an Airline Transport Pilot’s Licence (ATPL), occupied the right. The second occupant worked for the operator of G-BYCP but his licence was valid on Bombardier Challenger 300 and Embraer ERJ 135/145 aircraft and not on the King Air. The pilot reported for work at approximately 0715 hrs for a planned departure at 0815 hrs but he delayed the flight because of poor meteorological visibility. The general weather conditions were fog and low cloud with a calm wind. At approximately 0850 hrs the visibility was judged to be approximately 600 m, based on the known distance from the operations room to a feature on the aerodrome. At approximately 0915 hrs, trees were visible just beyond the end of Runway 22L, indicating that visibility was at least 1,000 m and the pilot decided that conditions were suitable for departure. At 0908 hrs, the pilot called the en-route Air Navigation Service Provider (ANSP) on his mobile phone to ask for a departure clearance. He was instructed to remain clear of controlled airspace when airborne and call London Tactical Control Northeast (TCNE) on 118.825 MHz. The planned departure was to turn right after takeoff and intercept the 128° radial from Brookman’s Park VOR (BPK) heading towards the beacon, and climb to a maximum altitude of 2,400 ft amsl to remain below the London TMA which has a lower limit of 2,500 ft amsl. The aircraft took off at 0921 hrs and was observed climbing in a wings level attitude until it faded from view shortly after takeoff. After takeoff, the aircraft climbed on a track of approximately 205°M and, when passing approximately 750 ft amsl (565 ft aal), began to turn right. The aircraft continued to climb in the turn until it reached 875 ft amsl (690 ft aal) when it began to descend. The descent continued until the aircraft struck some trees at the edge of a field approximately 1.8 nm southwest of the aerodrome. The pilot and passenger were both fatally injured in the accident, which was not survivable. A secondary radar return, thought to be G-BYCP, was observed briefly near Stapleford Aerodrome by London ATC but no radio transmission was received from the aircraft. A witness was walking approximately 30 m north-east of where the aircraft struck the trees. She suddenly heard the aircraft, turned towards the sound and saw the aircraft in a nose‑down attitude fly into the trees. Although she saw the aircraft only briefly, she saw clearly that the right wing was slightly low, and that the aircraft appeared to be intact and was not on fire. She also stated that the aircraft was “not falling” but flew “full pelt” into the ground.
Probable cause:
Examination of the powerplants showed that they were probably producing medium to high power at impact. There was contradictory evidence as to whether or not the left inboard flap was fully extended at impact but it was concluded that the aircraft would have been controllable even if there had been a flap asymmetry. The possibility of a preaccident control restriction could not be discounted, although the late change of aircraft attitude showed that, had there been a restriction, it cleared itself. The evidence available suggested a loss of aircraft control while in IMC followed by an unsuccessful attempt to recover the aircraft to safe flight. It is possible that the pilot lost control through a lack of skill but this seemed highly unlikely given that he was properly licensed and had just completed an extensive period of supervised training. Incapacitation of the pilot, followed by an attempted recovery by the additional crew member, was a possibility consistent with the evidence and supported by the post-mortem report. Without direct evidence from within the cockpit, it could not be stated unequivocally that the pilot became incapacitated. Likewise, loss of control due to a lack of skill, control restriction or distraction due to flap asymmetry could not be excluded entirely. On the balance of probabilities, however, it was likely that the pilot lost control of the aircraft due to medical incapacitation and the additional crew member was unable to recover the aircraft in the height available.
Final Report:

Crash of a Cessna 550 Citation Bravo in Lismore

Date & Time: Sep 25, 2015 at 1300 LT
Type of aircraft:
Operator:
Registration:
VH-FGK
Flight Phase:
Flight Type:
Survivors:
Yes
Schedule:
Lismore - Baryulgil
MSN:
550-0852
YOM:
1998
Country:
Region:
Crew on board:
2
Crew fatalities:
Pax on board:
0
Pax fatalities:
Other fatalities:
Total fatalities:
0
Captain / Total flying hours:
5937
Copilot / Total flying hours:
377
Aircraft flight hours:
2768
Circumstances:
On the morning of 25 September 2015, the captain and copilot of a Cessna 550 aircraft (Citation Bravo), registered VH-FGK, prepared to conduct a private flight from Lismore Airport to Baryulgil, about 40 NM south-west of Lismore, New South Wales. The aircraft had been parked at the northern end of the airport overnight, with engine covers and control locks on. After arriving at the airport, the flight crew conducted a pre-flight inspection, with no abnormalities identified. They then commenced the normal pre-start checks, which included the disengagement of the flight control locks. The crew elected to use runway 15 for take-off, and used the Cessna simplified take-off performance criteria (see Take-off performance simplified criteria) to determine the thrust settings and take-off reference speeds. The resultant reference speeds were 105 kt for the decision speed (V1) and 108 kt for the rotation speed (VR). At about 1300 Eastern Standard Time, the flight crew started the engines and performed the associated checks, with all indications normal. The crew reported that they completed the after start checks, and the captain then taxied the aircraft to the holding point for runway 15, less than 200 m from where the aircraft was parked. While stopped at the holding point, the crew completed the taxi and pre-take-off checks, the copilot broadcast the standard calls on the common traffic advisory frequency, and the captain communicated with air traffic control (ATC). The captain taxied the aircraft onto the runway, and turned left onto the runway centreline to commence the take-off run from the intersection. While rolling along the runway, the captain advanced the thrust levers to the approximate take-off setting. The captain then called ‘set thrust’, and the copilot set the thrust levers to the more precise position needed to achieve the planned engine thrust for the take-off. As the aircraft accelerated, the copilot called ‘80 knots’ and crosschecked the two airspeed indicators were in agreement and reading 80 kt. The copilot called ‘V1’ and the captain moved their hands from the thrust levers to the control column in accordance with the operator’s normal procedure. A few seconds later, the copilot called ‘rotate’ and the captain initiated a normal rotate action on the control column. The crew reported that the aircraft did not rotate and that they did not feel any indication that the aircraft would lift off. The copilot looked outside and did not detect any change in the aircraft’s attitude as would normally occur at that stage. The captain stated to the copilot that the aircraft would not rotate, and pulled back harder on the control column. The copilot looked across and saw the captain had pulled the control column firmly into their stomach. Although the aircraft’s speed was then about 112 kt, and above VR, the crew did not detect any movement of the attitude director indicator or the nose wheel lifting off the ground, so the captain rejected the take-off; applied full brakes, and set the thrust levers to idle and then into reverse thrust. The aircraft continued to the end of the sealed runway and onto the grass in the runway end safety area (RESA), coming to rest slightly left of the extended centreline, about 100 m beyond the end of the runway. The aircraft sustained substantial damage and the flight crew, who were the only occupants of the aircraft, were uninjured. The nose landing gear separated from the aircraft during the overrun, and there was significant structural damage to the fuselage and wings. The right wheel tyre had deflated due to an apparent wheel lockup and flat spot, which had progressed to a point that a large hole had been worn in the tyre.
Probable cause:
Contributing factors:
- There was probably residual braking pressure in the wheel brakes during the take-off run.
- The aircraft’s parking brake was probably applied while at the holding point and not disengaged before taxing onto the runway for take-off.
- The Citation aircraft did not have an annunciator light to show that the parking brake is engaged, and the manufacturer’s before take-off checklist did not include a check to ensure the parking brake is disengaged.
- The aircraft experienced a retarded acceleration during the take-off run, and did not rotate as normal when the appropriate rotate speed was reached, resulting in a critical rejected take-off
and a runway overrun.
Final Report:

Crash of a PZL-Mielec AN-2R near Bratsk

Date & Time: Sep 16, 2015 at 1115 LT
Type of aircraft:
Registration:
RA-35141
Flight Phase:
Flight Type:
Survivors:
Yes
Schedule:
Zhelenogorsk-Ilimsky – Taseyovo – Achinsk
MSN:
1G112-23
YOM:
1969
Country:
Region:
Crew on board:
2
Crew fatalities:
Pax on board:
1
Pax fatalities:
Other fatalities:
Total fatalities:
0
Captain / Total flying hours:
5116
Captain / Total hours on type:
4683.00
Copilot / Total flying hours:
1283
Copilot / Total hours on type:
1283
Aircraft flight hours:
14512
Aircraft flight cycles:
19970
Circumstances:
The single engine airplane departed Zhelenogorsk-Ilimsky Airport on a flight to Achinsk with an intermediate stop in Taseyovo, carrying one passenger and two pilots. After 43 minutes into the flight, while cruising at an altitude of about 1,200 metres, the engine lost power and the oil temperature increased from 70° to 150° C. The aircraft lost height, forcing the crew to attempt an emergency landing. The aircraft hit tree tops and eventually crash landed in a wooded area located 60 km northeast of Bratsk. The aircraft was damaged beyond repair and all three occupants escaped unarmed.
Probable cause:
The crash of An-2 RA-35141 aircraft occurred during the emergency landing on a forest firebreak. The landing was urged due to in-flight engine power loss as a result of the destruction of the 62.06.02 bronze hub pouring of the master rod big end of the crank mechanism. Most probably the destruction of the bronze hub pouring was caused by a manufacturing flaw consisting in a lack of bronze friction with the steel base on a part of its surface.
Final Report:

Crash of a Cessna 750 Citation X in Toluca

Date & Time: Aug 27, 2015 at 0015 LT
Type of aircraft:
Operator:
Registration:
XA-KYE
Flight Type:
Survivors:
Yes
MSN:
750-0204
YOM:
2002
Location:
Country:
Crew on board:
2
Crew fatalities:
Pax on board:
0
Pax fatalities:
Other fatalities:
Total fatalities:
0
Circumstances:
The crew was apparently completing a positioning flight to Toluca Airport. Following a night landing on runway 15, the crew started the braking procedure when the aircraft deviated to the left. The crew applied full brake but the aircraft veered off runway. While contacting soft ground, the nose gear collapsed and the aircraft came to rest about 2,700 metres from the runway threshold. Both pilots escaped uninjured and the aircraft was damaged beyond repair.