Ground collision with an ATR42-600 in Jakarta

Date & Time: Apr 4, 2016 at 1957 LT
Type of aircraft:
Operator:
Registration:
PK-TNJ
Flight Phase:
Survivors:
Yes
MSN:
1015
YOM:
2014
Country:
Region:
Crew on board:
2
Crew fatalities:
Pax on board:
0
Pax fatalities:
Other fatalities:
Total fatalities:
0
Aircraft flight hours:
2073
Aircraft flight cycles:
1038
Circumstances:
On 4 April 2016, Boeing 737-800 registration PK-LBS was being operated by Batik Air as scheduled passenger flight with flight number ID 7703 from Halim Perdanakusuma Airport with intended destination Sultan Hasanuddin International Airport, Makassar. An ATR 42-600 aircraft, registration PK-TNJ operated by TransNusa Aviation Mandiri was being repositioned from north to south apron of Halim Perdanakusuma Airport by a ground handling agent PT. Jasa Angkasa Semesta (PT. JAS). The aircraft was towed without aircraft electrical power fed to the system including the radio communication and aircraft lighting system. At the time of occurrence, the ID7703 pilot communicated to Halim Tower controller on frequency 118.6 MHz while the towing car driver communicated using handheld radio on frequency 152.73 KHz and was handled by assistant controller. At 1948 LT (1248 UTC), ID7703 pilot received taxi clearance from Halim Tower controller and after the ID7703 taxi, the towing car driver received clearance for towing and to report when on taxiway C. Afterward the towing car driver was instructed to expedite and to follow ID7703. While the ID7703 backtracking runway 24, the towed aircraft entered the runway intended to cross and to enter taxiway G. At 1256 UTC, ID7703 pilot received takeoff clearance and initiated the takeoff while the towed aircraft was still on the runway. The towing car driver and the pilots took action to avoid the collision. The decision of the pilot and the towing car driver to move away from the centerline runway had made the aircraft collision on the centerline runway (head to head) avoided, however the wings collision was unavoidable. At 1257 UTC, the ID7703 collided with the towed aircraft. The ID7703 pilot rejected the takeoff and stopped approximately 400 meters from the collision point while the towed aircraft stopped on the right of the centerline runway 24. No one injured at this occurrence and both aircraft severely damaged.
Probable cause:
The collision was the result of a poor coordination by ATC staff at Jakarta Airport. The following factors were reported:
- Handling of two movements in the same area with different controllers on separate frequencies without proper coordination resulted in the lack of awareness to the controllers, pilots and towing car driver,
- The communication misunderstanding of the instruction to follow ID 7703 most likely contributed the towed aircraft enter the runway,
- The lighting environments in the tower cab and turning pad area of runway 24 might have diminished the capability to the controllers and pilots to recognize the towed aircraft that was installed with insufficient lightings.
Final Report:

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:

Ground fire of an Antonov AN-26RT in Rostov-on-Don

Date & Time: Mar 29, 2016
Type of aircraft:
Operator:
Registration:
09 blue
Flight Phase:
Flight Type:
Survivors:
Yes
MSN:
122 02
YOM:
1982
Country:
Region:
Crew on board:
0
Crew fatalities:
Pax on board:
0
Pax fatalities:
Other fatalities:
Total fatalities:
0
Circumstances:
During the takeoff roll, the right engine caught fire. The crew aborted the takeoff procedure and was able to stop the aircraft on the runway. Unfortunately, he was unable to extinguish the fire that destroyed the right engine. All occupants evacuated safely and the aircraft was partially destroyed by fire.
Probable cause:
The right engine caught fire during takeoff for unknown reasons.

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 Cessna 340A in Tampa: 2 killed

Date & Time: Mar 18, 2016 at 1130 LT
Type of aircraft:
Operator:
Registration:
N6239X
Flight Phase:
Flight Type:
Survivors:
No
Schedule:
Tampa – Pensacola
MSN:
340A-0436
YOM:
1978
Crew on board:
1
Crew fatalities:
Pax on board:
1
Pax fatalities:
Other fatalities:
Total fatalities:
2
Captain / Total flying hours:
5195
Aircraft flight hours:
3963
Circumstances:
The airline transport pilot and pilot-rated passenger were departing on an instrument flight rules (IFR) cross country flight from runway 4 in a Cessna 340A about the same time that a private pilot and pilot rated passenger were departing on a visual flight rules repositioning flight from runway 36 in a Cessna 172M. Visual meteorological conditions prevailed at the airport. The runways at the nontowered airport converged and intersected near their departure ends. According to a witness, both airplanes had announced their takeoff intentions on the airport's common traffic advisory frequency (CTAF), which was not recorded; the Cessna 340A pilot's transmission occurred about 10 to 15 seconds before the Cessna 172M pilot's transmission. However, the witness stated that the Cessna 172M pilot's transmission was not clear, but he was distracted at the time. Both occupants of the Cessna 172M later reported that they were constantly monitoring the CTAF but did not hear the transmission from the Cessna 340A pilot nor did they see any inbound or outbound aircraft. Airport video that captured the takeoffs revealed that the Cessna 172M had just lifted off and was over runway 36 approaching the intersection with runway 4, when the Cessna 340A was just above runway 4 in a wings level attitude with the landing gear extended and approaching the intersection with runway 36. Almost immediately, the Cessna 340A then began a climbing left turn with an increasing bank angle while the Cessna 172M continued straight ahead. The Cessna 340A then rolled inverted and impacted the ground in a nose-low and left-wing-low attitude. The Cessna 172M, which was not damaged, continued to its destination and landed uneventfully. The Cessna 340A was likely being flown at the published takeoff and climb speed of 93 knots indicated airspeed (KIAS). The published stall speed for the airplane in a 40° bank was 93 KIAS, and, when the airplane reached that bank angle, it likely exceeded the critical angle of attack and entered an aerodynamic stall. Examination of the Cessna 340A wreckage did not reveal any preimpact mechanical malfunctions that would have precluded normal operation. Because of a postcrash fire, no determination could be made as to how the radios and audio panel were configured for transmitting and receiving or what frequencies were selected. There were no reported discrepancies with the radios of the Cessna 172M, and there were no reported difficulties with the communication between the Cessna 340A and the Federal Aviation Administration facility that issued the airplane's IFR clearance. Additionally, there were no known issues related to the CTAF at the airport. Toxicological testing detected unquantified amounts of atorvastatin, diphenhydramine, and naproxen in the Cessna 340A pilot's liver. The Cessna 340A pilot's use of atorvastatin or naproxen would not have impaired his ability to hear the radio announcements, see the other airplane taking off on the converging runway, or affected his performance once the threat had been detected. Without an available blood level of diphenhydramine, it could not be determined whether the drug was impairing or contributed to the circumstances of the accident.
Probable cause:
The intentional low altitude maneuvering during takeoff in response to a near-miss with an airplane departing from a converging runway, which resulted in an exceedance of the airplane's critical angle of attack and a subsequent aerodynamic stall.
Final Report:

Crash of a Beechcraft 1900D in Karachi

Date & Time: Mar 18, 2016 at 0820 LT
Type of aircraft:
Operator:
Registration:
AP-BII
Flight Phase:
Survivors:
Yes
Schedule:
Karachi – Sui
MSN:
UE-45
YOM:
1993
Country:
Region:
Crew on board:
3
Crew fatalities:
Pax on board:
18
Pax fatalities:
Other fatalities:
Total fatalities:
0
Captain / Total flying hours:
2885
Captain / Total hours on type:
717.00
Copilot / Total flying hours:
3614
Copilot / Total hours on type:
245
Aircraft flight hours:
19574
Aircraft flight cycles:
30623
Circumstances:
The Aircraft Sales and Services (Private) Limited (ASSL) aircraft Beechcraft-1900D Registration No. AP-BII was scheduled for a chartered flight on 18th March, 2016 from Karachi to Sui. Just after takeoff from runway 25L at 0820 hrs local time, the crew observed power loss of right engine and made a gear up landing on the remaining runway on the right side of centreline. After touchdown, the aircraft went off the runway towards right side and then came back on the runway before coming to a final stop 1,050 feet short from the end of runway. The Captain and one passenger received serious injuries due to hard impact of the aircraft with ground. All other passengers and technician remained unhurt.
Probable cause:
The investigation therefore, concludes that:
- Some internal malfunction of the Propeller Governor Part No. 8210-410 Serial No. 2490719 was the cause of experienced uncommanded auto feather. However, exact cause of the occurrence could not be determined.
- Continuing take off below V1 speed (104kts) after encountering engine malfunction and after takeoff raising flaps below recommended height (400ft AGL) lead to decrease in lift and unsustainability of flight.
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 Cessna 208 Caravan I at Langebaanweg AFB

Date & Time: Mar 3, 2016
Type of aircraft:
Operator:
Registration:
3004
Flight Phase:
Flight Type:
Survivors:
Yes
Schedule:
Langebaanweg - Langebaanweg
MSN:
208-0130
YOM:
1988
Country:
Region:
Crew on board:
2
Crew fatalities:
Pax on board:
0
Pax fatalities:
Other fatalities:
Total fatalities:
0
Circumstances:
The crew was completing a local night training exercice at Langebaanweg AFB. While completing various manoeuvres, the airplane went out of control and crashed in an open field located near airbase, coming to rest upside down. The aircraft was destroyed and both pilots were injured.