Crash of a Beechcraft 65-A90-1 King Air in Slidell: 2 killed

Date & Time: Apr 19, 2016 at 2115 LT
Type of aircraft:
Operator:
Registration:
N7MC
Survivors:
No
Schedule:
Slidell - Slidell
MSN:
LM-106
YOM:
1968
Crew on board:
2
Crew fatalities:
Pax on board:
0
Pax fatalities:
Other fatalities:
Total fatalities:
2
Captain / Total flying hours:
18163
Captain / Total hours on type:
614.00
Copilot / Total flying hours:
7769
Copilot / Total hours on type:
22
Aircraft flight hours:
15208
Circumstances:
The airline transport pilot and commercial copilot were conducting a mosquito abatement application flight. Although flight controls were installed in both positions, the pilot typically operated the airplane. During a night, visual approach to landing at their home airfield, the airplane was on the left base leg and overshot the runway's extended centerline and collided with 80-ft-tall power transmission towers and then impacted terrain. Examination of the airplane did not reveal any preimpact anomalies that would have precluded normal operation. Both pilots were experienced with night operations, especially at their home airport. The pilot had conducted operations at the airport for 14 years and the copilot for 31 years, which might have led to crew complacency on the approach . Adequate visibility and moon disk illumination were available; however, the area preceding the runway is a marsh and lacks cultural lighting, which can result in black-hole conditions in which pilots may perceive the airplane to be higher than it actually is while conducting an approach visually. The circumstances of the accident are consistent with the pilot experiencing the black hole illusion which contributed to him flying an approach profile that was too low for the distance remaining to the runway. It is likely that the pilot did not maintain adequate crosscheck of his altimeter and radar altimeter during the approach and that the copilot did not monitor the airplane's progress; thus, the flight crew did not recognize that they were not maintaining a safe approach path. Further, it is likely that neither pilot used the visual glidepath indicator at the airport, which is intended to be a countermeasure against premature descent in visual conditions.
Probable cause:
The unstable approach in black-hole conditions, resulting in the airplane overshooting the runway extended centerline and descending well below a safe glidepath for the runway. Contributing to the accident was the lack of monitoring by the copilot allowing the pilot to fly well below a normal glidepath.
Final Report:

Crash of a Britten-Norman BN-2T Islander in Kiunga: 12 killed

Date & Time: Apr 13, 2016 at 1420 LT
Type of aircraft:
Operator:
Registration:
P2-SBC
Survivors:
No
Schedule:
Oksapmin – Kiunga
MSN:
3010
YOM:
1983
Region:
Crew on board:
1
Crew fatalities:
Pax on board:
11
Pax fatalities:
Other fatalities:
Total fatalities:
12
Captain / Total flying hours:
4705
Captain / Total hours on type:
254.00
Aircraft flight hours:
2407
Aircraft flight cycles:
2886
Circumstances:
On the afternoon of 13 April 2016, a Pilatus Britten Norman Turbine Islander (BN-2T) aircraft, registered P2-SBC, operated by Sunbird Aviation Ltd, departed from Tekin, West Sepik Province for Kiunga, Western Province, as a charter flight under the visual flight rules. On board were the pilot-in-command (PIC) and 11 passengers (eight adults and three children). The aircraft was also carrying vegetables. The pilot reported departing Oksapmin at 13:56. The pilot had flight planned, Kiunga to Oksapmin to Kiunga. However, the evidence revealed that without advising Air Traffic Services, the pilot flew from Oksapmin to Tekin. On departure from Tekin the pilot transmitted departure details to ATS, stating departure from Oksapmin. The recorded High Frequency radio transmissions were significantly affected by static and hash. The weather at Kiunga was reported to be fine. As the aircraft entered the Kiunga circuit area, the pilot cancelled SARWATCH with Air Traffic Services (ATS). The pilot did not report an emergency to indicate a safety concern. Witnesses reported that during its final approach, the aircraft suddenly pitched up almost to the vertical, the right wing dropped, and the aircraft rolled inverted and rapidly “fell to the ground”. It impacted the terrain about 1,200 metres west of the threshold of runway 07. The impact was vertical, with almost no forward motion. The aircraft was destroyed, and all occupants were fatally injured.
Probable cause:
The aircraft’s centre of gravity was significantly aft of the aft limit. When landing flap was set, full nose-down elevator and elevator trim was likely to have had no effect in lowering the nose of the aircraft. Unless the flaps had been retracted immediately, the nose-up pitch may also have resulted in tail plane stall, exacerbating the pitch up. The wings stalled, followed immediately by the right wing dropping. Recovery from the stall at such a low height was not considered possible.
Other factors:
Other factors is used for safety deficiencies or concerns that are identified during the course of the investigation, that while not causal to the accident, nevertheless should be addressed with the
aim of accident and serious incident prevention, and the safety of the travelling public.
a) Following the reweighing of SBC, the operator did not make adjustments to account for the shift of the moment arm as a result of the reweighing. Specifically, a reduction of allowable maximum weight in the baggage compartment.
b) The pilot, although signing the flight manifest on previous flights attesting that the aircraft was loaded within c of g limits, had not computed the c of g. No documentation was available to confirm that the pilot had computed the c of g for the accident flight, or any recent flights.
c) All of the High Frequency radio transmissions between Air Traffic Services and SBC were significantly affected by static interference and a lot of hash, making reception difficult, and many transmissions unclear and unreadable. This is a safety concern to be addressed to ensure that vital operational radio transmissions are not missed for the safety of aircraft operations, and the travelling public.
Final Report:

Crash of a De Havilland DHC-6 Twin Otter 100 in Fentress

Date & Time: Apr 9, 2016 at 1700 LT
Operator:
Registration:
N122PM
Survivors:
Yes
Schedule:
Fentress - Fentress
MSN:
15
YOM:
1966
Location:
Crew on board:
2
Crew fatalities:
Pax on board:
0
Pax fatalities:
Other fatalities:
Total fatalities:
0
Captain / Total flying hours:
6000
Captain / Total hours on type:
1000.00
Aircraft flight hours:
53624
Circumstances:
The pilot reported that he was landing in gusty crosswind conditions following a parachute jump flight, and that the gusty conditions had persisted for the previous 10 skydiving flights that day. The pilot further reported that during the landing roll, when the nose wheel touched down, the airplane became "unstable" and veered to the left. He reported that he applied right rudder and added power to abort the landing, but the airplane departed the runway to the left and the left wing impacted a tree. The airplane spun 180 degrees to the left and came to rest after the impact with the tree. The left wing was substantially damaged. The pilot did not report any mechanical malfunctions or failures with the airplane that would have precluded normal operation.
Probable cause:
The pilot's failure to maintain directional control during the aborted landing in gusty crosswind conditions, which resulted in a runway excursion and a collision with a tree.
Final Report:

Crash of a BAe U-125 at Kanoya AFB: 6 killed

Date & Time: Apr 6, 2016 at 1435 LT
Type of aircraft:
Operator:
Registration:
49-3043
Flight Type:
Survivors:
No
Site:
Schedule:
Kanoya - Kanoya
MSN:
258242
YOM:
1993
Country:
Region:
Crew on board:
6
Crew fatalities:
Pax on board:
0
Pax fatalities:
Other fatalities:
Total fatalities:
6
Circumstances:
The aircraft departed Kanoya AFB at 1315LT on a calibration flight with six people on board. After he complete a counter clockwise arc, the crew started the descent to Kanoya AFB Runway 08R. The visibility was poor due to low clouds. On approach, at an altitude of 3,000 feet, the aircraft entered clouds when the GPWS alarm sounded. Two second later, the crew deactivated the alarm and continued the approach. Ten seconds later, the aircraft impacted trees and crashed on the slope of Mt Takakuma (1,182 metres high) located 10 km north of the airbase. The wreckage was found a day later and all six crew members were killed.
Probable cause:
Controlled flight into terrain after the crew continued the approach in poor visibility without visual contact with the environment. Misidentification of the environment on part of the crew was a contributing factor, as well as the fact that the crew deactivated the GPWS alarm and failed to initiate corrective maneuver.

Crash of a Mitsubishi MU-2B-60 Marquise in Le Havre-aux-Maisons: 7 killed

Date & Time: Mar 29, 2016 at 1230 LT
Type of aircraft:
Operator:
Registration:
N246W
Survivors:
No
Schedule:
Montreal - Le Havre-aux-Maisons
MSN:
1552
YOM:
1982
Country:
Crew on board:
1
Crew fatalities:
Pax on board:
6
Pax fatalities:
Other fatalities:
Total fatalities:
7
Captain / Total flying hours:
2500
Captain / Total hours on type:
125.00
Aircraft flight hours:
11758
Circumstances:
The twin engine aircraft left Montreal-Saint-Hubert Airport at 0930LT for a two hours flight to Le Havre-aux-Maisons, on Magdalen Islands. Upon arrival, weather conditions were marginal with low ceiling, visibility up to two miles, rain and wind gusting to 30 knots. During the final approach to Runway 07, when the aircraft was 1.4 nautical miles west-southwest of the airport, it deviated south of the approach path. At approximately 1230 Atlantic Daylight Time, aircraft control was lost, resulting in the aircraft striking the ground in a near-level attitude. The aircraft was destroyed and all seven occupants were killed, among them Jean Lapierre, political commentator and former Liberal federal cabinet minister of Transport. All passengers were flying to Magdalen Islands to the funeral of Lapierre's father, who died last Friday. The captain, Pascal Gosselin, was the founder and owner of Aéro Teknic.
Crew:
Pascal Gosselin, pilot.
Passengers:
Fabrice Labourel, acting as a copilot,
Jean Lapierre,
Nicole Beaulieu, Jean Lapierre's wife,
Martine Lapierre, Jean Lapierre's sister,
Marc Lapierre, Jean Lapierre's brother,
Louis Lapierre, Jean Lapierre's brother.
Probable cause:
Findings as to causes and contributing factors:
1. The pilot’s inability to effectively manage the aircraft’s energy condition led to an unstable approach.
2. The pilot “got behind” the aircraft by allowing events to control his actions, and cognitive biases led him to continue the unstable approach.
3. A loss of control occurred when the pilot rapidly added full power at low airspeed while at low altitude, which caused a power-induced upset and resulted in the aircraft rolling sharply to the right and descending rapidly.
4. It is likely that the pilot was not prepared for the resulting power-induced upset and, although he managed to level the wings, the aircraft was too low to recover before striking the ground.
5. The pilot’s high workload and reduced time available resulted in a task-saturated condition, which decreased his situational awareness and impaired his decision making.
6. It is unlikely that the pilot’s flight skills and procedures were sufficiently practised to ensure his proficiency as the pilot-in-command for single-pilot operation on the MU2B for the conditions experienced during the occurrence flight.

Findings as to risk:
1. If the weight of an aircraft exceeds the certified maximum take-off weight, there is a risk of aircraft performance being degraded, which may jeopardize the safety of the flight.
2. If pilots engage in non-essential communication during critical phases of flight, there is an increased risk that they will be distracted, which reduces the time available to complete cockpit activities and increases their workload.
3. If flight, cockpit, or image/video data recordings are not available to an investigation, the identification and communication of safety deficiencies to advance transportation safety may be precluded.
4. If pilots do not recognize that changing circumstances require a new plan, then plan continuation bias may lead them to continue with their original plan even though it may not be safe to do so.
5. If pilots do not apply stable-approach criteria, there is a risk that they will continue an unstable approach to a landing, which can lead to an approach-and-landing accident.
6. If pilots are not prepared to conduct a go-around on every approach, they risk not responding appropriately to situations that require one.
7. If a flight plan does not contain search-and-rescue supplementary information, and if that information is not transmitted or readily available, there is a risk that first responders will not have the information they need to respond adequately.

Other findings:
1. Transport Canada does not monitor or track the number of days foreign-registered aircraft are in Canada during a given 12-month period.
2. Turbulence and icing were not considered factors in this occurrence.
3. Transport Canada considers that the discretionary installation of an angle-of-attack system on normal-category, type-certificated, Canadian-registered aircraft is a major modification that requires a supplemental type certificate approval.
4. Although the aircraft was not in compliance with Airworthiness Directive 2006-17-05 at the time of the occurrence, there was no indication that it was operating outside of the directive’s specifications.
5. Although not required by regulation, the installation and use of a lightweight flight recording system during the occurrence flight, as well as the successful retrieval of its data during the investigation, permitted a greater understanding of this accident.
Final Report:

Crash of a Fokker 100 in Astana

Date & Time: Mar 27, 2016 at 1037 LT
Type of aircraft:
Operator:
Registration:
UP-F1012
Survivors:
Yes
Schedule:
Kyzylorda – Astana
MSN:
11426
YOM:
1992
Flight number:
Z92041
Location:
Country:
Region:
Crew on board:
5
Crew fatalities:
Pax on board:
116
Pax fatalities:
Other fatalities:
Total fatalities:
0
Circumstances:
Following an uneventful flight from Kyzylorda, the crew initiated the descent to Astana Airport and configured the aircraft for landing. After the crew lowered the landing gear, he realized that the nose gear remained stuck in its wheel well. The captain abandoned the approach and initiated a go-around. During the holding circuit, the crew elected to lower the gear manually, without success. After a 50 minutes circuit, the crew decided to land without the nose gear. After touchdown on runway 22, the aircraft slid for few dozen metres before coming to rest. All 121 occupants evacuated safely and the aircraft was damaged beyond repair.

Crash of a Boeing 737-8KN in Rostov-on-Don: 62 killed

Date & Time: Mar 19, 2016 at 0342 LT
Type of aircraft:
Operator:
Registration:
A6-FDN
Survivors:
No
Schedule:
Dubai - Rostov-on-Don
MSN:
40241/3517
YOM:
2010
Flight number:
FZ981
Country:
Region:
Crew on board:
7
Crew fatalities:
Pax on board:
55
Pax fatalities:
Other fatalities:
Total fatalities:
62
Captain / Total flying hours:
5961
Captain / Total hours on type:
4682.00
Copilot / Total flying hours:
5767
Copilot / Total hours on type:
1100
Aircraft flight hours:
21257
Aircraft flight cycles:
9421
Circumstances:
At the overnight into 19.03.2016 the Flydubai airline flight crew, consisting of the PIC and F/O, was performing the round-trip international scheduled passenger flight FDB 981/982 on route
Dubai (OMDB) – Rostov-on-Don (URRR) – Dubai (OMDB) on the B737-8KN A6-FDN aircraft. At 18:37 on 18.03.2016 the aircraft took off from the Dubai airport. The flight had been performed in IFR. At 18:59:30 FL360 was reached. The further flight has been performed on this very FL. The descent from FL has been initiated at 22:17. Before starting the descent, the crew contacted the ATC on the Rostov-on-Don airport actual weather and the active RWY data. In progress of the glide path descent to perform landing with magnetic heading 218° (RWY22) the crew relayed the presence of “windshear” on final to the ATC (as per the aboard windshear warning system activation). At 22:42:05 from the altitude of 1080 ft (330 m) above runway level performed go-around. Further on the flight was proceeded at the holding area, first on FL080, then on FL150. At 00:23 on 19.03.2016, the crew requested descent for another approach. It was an ILS approach. The A/P was disengaged by the crew at the altitude of 2165 ft QNH (575 m QFE), and the A/T at the altitude of 1960 ft QNH (510 m QFE). . In the progress of another approach the crew made the decision to initiate go-around and at 00:40:50, from the altitude of 830 ft (253 m) above the runway level, started the maneuver. After the reach of the altitude of 3350 ft (1020 m) above the runway level the aircraft transitioned to a steep descent and at 00:41:49 impacted the ground (it collided the surface of the artificial runway at the distance of about 120 m off the RWY22 threshold) with the nose-down pitch of about 50⁰ and IAS about 340 kt (630 km/h). The aircraft disintegrated on impact and all 62 occupants were killed.
Probable cause:
The fatal air accident to the Boeing 737-8KN A6-FDN aircraft occurred during the second go around, due to an incorrect aircraft configuration and crew piloting, the subsequent loss of PIC’s situational awareness in nighttime in IMC. This resulted in a loss of control of the aircraft and its impact with the ground. The accident is classified as Loss of Control In-Flight (LOC-I) occurrence.
Most probably, the contributing factors to the accident were:
- The presence of turbulence and gusty wind with the parameters, classified as a moderate to-strong "windshear" that resulted in the need to perform two go-arounds;
- The lack of psychological readiness (not go-around minded) of the PIC to perform the second go-around as he had the dominant mindset on the landing performance exactly at the destination aerodrome, having formed out of the "emotional distress" after the first unsuccessful approach (despite the RWY had been in sight and the aircraft stabilized on the glide path, the PIC had been forced to initiate go-around due to the windshear warning activation), concern on the potential exceedance of the duty time to perform the return flight and the recommendation of the airline on the priority of landing at the destination aerodrome;
- The loss of the PIC’s leadership in the crew after the initiation of go-around and his "confusion" that led to the impossibility of the on-time transition of the flight mental mode from "approach with landing" into "go-around";
- The absence of the instructions of the maneuver type specification at the go-around callout in the aircraft manufacturer documentation and the airline OM;
- The crew’s uncoordinated actions during the second go-around: on the low weight aircraft the crew was performing the standard go-around procedure (with the retraction of landing gear and flaps), but with the maximum available thrust, consistent with the Windshear Escape Maneuver procedure that led to the generation of the substantial excessive nose-up moment and significant (up to 50 lb/23 kg) "pushing" forces on the control column to counteract it;
- The failure of the PIC within a long time to create the pitch, required to perform go around and maintain the required climb profile while piloting aircraft unbalanced in forces;
- The PIC’s insufficient knowledge and skills on the stabilizer manual trim operation, which led to the long-time (for 12 sec) continuous stabilizer nose-down trim with the subsequent substantial imbalance of the aircraft and its upset encounter with the generation of the negative G, which the crew had not been prepared to. The potential impact of the somatogravic "pitch-up illusion" on the PIC might have contributed to the long keeping the stabilizer trim switches pressed;
- The psychological incapacitation of the PIC that resulted in his total spatial disorientation, did not allow him to respond to the correct prompts of the F/O;
- The absence of the criteria of the psychological incapacitation in the airline OM, which prevented the F/O from the in-time recognition of the situation and undertaking more decisive actions;
- The possible operational tiredness of the crew: by the time of the accident the crew had been proceeding the flight for 6 hours, of which 2 hours under intense workload that implied the need to make non-standard decisions; in this context the fatal accident occurred at the worst possible time in terms of the circadian rhythms, when the human performance is severely degraded and is at its lower level along with the increase of the risk of errors.
The lack of the objective information on the HUD operation (there were no flight tests of the unit carried out into the entire range of the operational G, including the negative ones; the impossibility to reproduce the real HUD readings in the progress of the accident flight, that is the image the pilot was watching with the consideration of his posture in the seat trough the stream video or at the FFS) did not allow making conclusion on its possible impact on the flight outcome. At the same time the investigation team is of the opinion that the specific features of the HUD indication and display in conditions existed during final phase of the accident flight (severe turbulence, the aircraft upset encounter with the resulting negative G, the significant difference between the actual and the target flight path) that generally do not occur under conditions of the standard simulator sessions, could have affected the situational awareness of the PIC, having been in the highly stressed state.
Final Report:

Crash of a Beechcraft C90 King Air in Oeiras

Date & Time: Mar 18, 2016 at 1630 LT
Type of aircraft:
Registration:
PP-JBL
Survivors:
Yes
Schedule:
Teresina - Oeiras
MSN:
LJ-861
YOM:
1979
Location:
Country:
Crew on board:
1
Crew fatalities:
Pax on board:
7
Pax fatalities:
Other fatalities:
Total fatalities:
0
Circumstances:
The twin engine airplane departed Teresina on a business flight to Floriano, carrying seven passengers and one pilot, among them Ciro Nogueira, Senator of the State of Piauí and Margarete Coelho, Vice-Governor of the State of Piauí. En route to Floriano, the pilot was informed about the deterioration of the weather conditions at destination and decided to divert to Oeiras Airfield. After touchdown on runway 11 that was wet due to recent rain falls, the aircraft started to skid. Control was lost and the aircraft veered off runway to the left and came to rest in a wooded area, some 10 metres from the runway. All eight occupants were rescued, among them one passenger was slightly injured. The aircraft was damaged beyond repair.
Probable cause:
Contributing factors:
- Application of commands - undetermined
It is possible that the pilot has not acted properly in the controls after touchdown to avoid a runway excursion.
- Flight indiscipline - contributed
Having landed on a non-approved runway, without justifiable reason, the crew member did not comply with the provisions of civil aviation regulations.
- Influence of the environment - undetermined
The wet and puddled runway may have affected directional control and aircraft braking performances during the landing roll.
- Pilot judgment - contributed
The crew member had not correctly assessed the risks involved in the operation in an unapproved runway, without justifiable reason. In addition, the pilot had no considering that the wet and puddle conditions of the runway could affect the directional control and braking performances of the aircraft.
- Decision-making process - contributed
The decision to land at an unapproved aerodrome, as well as having used a wet runway and the presence of puddles denoted an inadequate assessment of the risks present in the context. Failures related to decisions assumed by the pilot contributed to the occurrence insofar as they resulted in the entry of the aircraft into a critical condition, affecting its control.
Final Report:

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:

Crash of a Rockwell Sabreliner 75A in Santiago de Querétaro

Date & Time: Jan 30, 2016 at 0738 LT
Type of aircraft:
Operator:
Registration:
N380CF
Flight Type:
Survivors:
Yes
Schedule:
Celaya - Santiago de Querétaro
MSN:
380-51
YOM:
1977
Country:
Crew on board:
0
Crew fatalities:
Pax on board:
0
Pax fatalities:
Other fatalities:
Total fatalities:
0
Aircraft flight hours:
10195
Circumstances:
The aircraft, a Rockwell Sabreliner 75A (NA-265-80 version) departed Celaya-Capitán Rogelio Castillo Airport shortly before 0700LT on a short flight to Santiago de Querétaro without any flight plan and with an unknown number of people on board. At 0731LT, the crew contacted the destination airport and elected to land about seven minutes later. After landing on runway 27, the crew was instructed to vacate via taxiway for the apron but the aircraft continued, veered off runway after a distance 800 metres, impacted a rocky wall, lost its nose gear and came to rest. When the rescuers arrived on the scene, there was nobody as the occupants left the airplane and disappeared. It appears the flight was illegal and it is believed that the aircraft was stolen at Celaya Airport.