Crash of a Lockheed C-130H Hercules in Jolo: 52 killed

Date & Time: Jul 4, 2021 at 1130 LT
Type of aircraft:
Operator:
Registration:
5125
Flight Type:
Survivors:
Yes
Schedule:
Cagayan de Oro - Jolo
MSN:
5125
YOM:
1988
Country:
Region:
Crew on board:
8
Crew fatalities:
Pax on board:
88
Pax fatalities:
Other fatalities:
Total fatalities:
52
Circumstances:
The four engine aircraft departed Cagayan de Oro Airport to transfer troops to Jolo. On board were 88 passengers and a crew of 8, including three pilots. After landing on runway 09 at Jolo Airport, the aircraft was unable to stop within the remaining distance. It overran, collided with several house and came to rest in a wooded area, bursting into flames. At least 49 occupants were killed as well as three people on the ground. All others were injured.

Crash of a Lockheed C-130H3 Hercules at Al Taji AFB

Date & Time: Jun 8, 2020 at 2205 LT
Type of aircraft:
Operator:
Registration:
94-6706
Flight Type:
Survivors:
Yes
Schedule:
Ali Al Salem AFB - Al Taji AAF
MSN:
5398
YOM:
1995
Country:
Region:
Crew on board:
7
Crew fatalities:
Pax on board:
19
Pax fatalities:
Other fatalities:
Total fatalities:
0
Captain / Total hours on type:
1700.00
Copilot / Total hours on type:
506
Circumstances:
On 8 June 2020, at approximately 2205 hours local time (L), the mishap aircraft (MA), a C-130H (tail number (T/N) 94-6706), was involved in a mishap during a routine mobility airlift mission from Ali Al Salem Air Base, Kuwait, into Al Taji (Camp Taji), Iraq, when it failed to come to a stop during landing, overran the runway, and impacted a concrete barrier. All 26 mishap crew (MC) members and passengers survived the mishap, with relatively minor injuries to two of the individuals. The MA was damaged beyond repair, and was valued at $35,900,000. The MA was from the 165th Airlift Wing (165 AW), Georgia Air National Guard (ANG), was manned with Wyoming ANG crew members deployed from the 153d Airlift Wing (153 AW), in Cheyenne, Wyoming, and assigned to the 386th Air Expeditionary Wing (386 AEW) at Ali Al Salem Air Base, Kuwait. The mishap occurred at the end of the first planned leg of the MC’s mission on 8 June 2020. The MC departed Ali Al Salem Air Base, Kuwait, at approximately 2053L, with an uneventful start, taxi, takeoff, and cruise to Camp Taji. During descent into Camp Taji, the MC prepared the MA for a nighttime landing, using night vision devices. During this time, the MC turned the MA earlier than their planned turn point, did not descend to lower altitudes in accordance with their planned descent, and allowed the airspeed to exceed recommended maximum speeds for the configuration the plane was in. During the landing, the MA continued to be above the planned glideslope and maintained excessive airspeed, with a nose-down attitude until touchdown. The MA proceeded to “porpoise” or oscillate down the runway from the point of touchdown until the MA was slowed sufficiently by use of reverse thrust from the engines to allow the MA to settle onto the wheels, which in turn allowed for the brakes to engage. The MA, despite slowing somewhat, had less than 1,000 feet of runway remaining by that point, and thus overran the runway and did not come to a complete stop until it impacted a 12-foot-high concrete barrier, approximately 600 feet past the runway.
Probable cause:
The Accident Investigation Board (AIB) President found by a preponderance of the evidence that the causes of the mishap were the MA’s excess airspeed above recommended landing velocity, which caused the MA to maintain lift (flight) and did not provide sufficient weight on wheels (WOW) to allow braking action to occur. Additionally, the AIB President found, by a preponderance of the evidence, the MC’s failure to adequately assess risk, failure to follow proper procedures, and their poor communication were all substantially contributing factors to the mishap.
Final Report:

Crash of a Lockheed EC-130Q Hercules near Peak View: 3 killed

Date & Time: Jan 23, 2020 at 1315 LT
Type of aircraft:
Operator:
Registration:
N134CG
Flight Phase:
Flight Type:
Survivors:
No
Schedule:
Richmond - Richmond
MSN:
4904
YOM:
1981
Flight number:
Bomber 134
Country:
Region:
Crew on board:
3
Crew fatalities:
Pax on board:
0
Pax fatalities:
Other fatalities:
Total fatalities:
3
Captain / Total flying hours:
4010
Captain / Total hours on type:
3010.00
Copilot / Total flying hours:
1744
Copilot / Total hours on type:
1364
Aircraft flight hours:
11888
Circumstances:
At about 1205, while B137 was overhead the Adaminaby fire-ground, and about the same time the SAD logged the birddog rejection, B134 departed Richmond as initial attack. On board were the PIC, the copilot and flight engineer. In response to the draft report, the RFS provided excerpts from the state operations controller (SOC) log. An entry was written in the log by the SOC following the accident. The SOC noted having been advised that the birddog had indicated it was ‘not safe to fly’ and that B137 was not returning to the area until the conditions had eased. However, B134 would continue with the PIC to make the ‘decision of safety of bombing operations’. The RFS advised the ATSB that the SOC had the authority to cancel B134’s tasking, but instead allowed it to proceed, with the intention of gathering additional intelligence to assist in determining whether further aerial operations would proceed. The RFS further reported that this indicated an ongoing intelligence gathering and assessment process by the SOC. At about 1235, while returning to Richmond, the PIC of B137 heard the PIC of B134 on the Canberra approach frequency, and contacted them via their designated operating frequency. At that time, B134 was about 112 km north-east of Adaminaby, en route to the fire-ground. In this conversation, the PIC of B137 informed them of the actual conditions and that they would not be returning to Adaminaby. The PIC of B137 reported that they could not recall the specific details of the call, but that the conversation included that they were ‘getting crazy winds’ and ‘you can go take a look’ ’but I am not going back’. It was also noted that the PIC of B134 had asked several questions. It was reported by the majority of the operator’s pilots that, despite receiving information from another pilot, they would have also continued with the tasking under these circumstances, to assess the conditions themselves. At about 1242, the crew of B134 contacted air traffic control to advise them of the coordinates they would be working at, provide an ‘ops normal’ call time, and confirm there was no reported instrument flight rules aircraft in the area. About 5 minutes later, the Richmond ABM also attempted to contact the crew of B134 to confirm ‘ops normal’, firstly by radio, and then by text to the PIC’s mobile phone, but did not receive a response. The automatic dependent surveillance broadcast (ADS-B) data showed that, after arriving at the Adaminaby fire-ground at about 1251, the crew of B134 completed several circuits at about 2,000 ft AGL. At about 1255, the crew advised the Cooma ARO that it was too smoky and windy to complete a retardant drop at that location. The Cooma ARO then provided the crew with the approximate coordinates of the Good Good fire, about 58 km to the east of Adaminaby. The ARO further indicated that they had no specific requirements, but they could look for targets of opportunity, with the objective of conducting structure and property protection near Peak View. At about 1259, the crew of B134 contacted air traffic control to advise that they had been re-tasked to the Good Good fire-ground, and provided updated coordinates. At about the same time, the RFS ground firefighters at the Good Good fire-ground, near Feeney’s Road in Peak View, contacted the Cooma FCC and requested additional assets for property protection. They were advised that a LAT would be passing overhead in about 10 minutes. The firefighters acknowledged the intention of a LAT retardant drop and advised the Cooma FCC they would wait in open country on Feeney’s Road, clear of any properties targeted for protection. At about 1307, B134 arrived overhead the drop area. The drop area was located to the east of a ridgeline, with the fire on the western side of the ridgeline. The aircraft’s recorded track data (SkyTrac) showed that the crew conducted 3 left circuits, at about 1,500 ft, 500 ft and 1,000 ft AGL respectively, prior to commencing the drop circuit. At about 1312, after conducting about 2 circuits, they advised the Cooma ARO of their intention to complete multiple drops on the eastern side of the Good Good fire, and that they would advise the coordinates after the first delivery. At 1315:15, a partial retardant drop was conducted on a heading of about 190°, at about 190 ft AGL (3,600 ft above mean sea level). During the drop, about 1,200 US gallons (4,500 L) of fire retardant was released over a period of about 2 seconds. A ground speed of 144 kt was recorded at the time of the drop. A witness video taken by ground fire-fighters captured the drop and showed the aircraft immediately after the drop in an initial left turn with a positive rate of climb, before it became obscured by smoke. While being intermittently obscured by smoke, the aircraft climbed to about 330 ft AGL (3,770 ft above mean sea level). At about this time, ATSB analysis of the video showed that the aircraft was rolling from about 18° left angle of bank to about a 6° right angle of bank. Following this, the aircraft descended and about 17 seconds after the completion of the partial retardant drop, it was seen at a very low height above the ground, in a slight left bank. Video analysis and accident site examination showed there was no further (emergency) drop of retardant. Throughout this period, the recorded groundspeed increased slightly to a maximum of 151 kt. Shortly after, there was a significant left roll just prior to ground impact. At about 1315:37, the aircraft collided with terrain and a post-impact fuel-fed fire ensued. The 3 crew were fatally injured and the aircraft was destroyed. A review of the Airservices Australia audio recording of the applicable air traffic control frequency found no distress calls were received by controllers prior to the impact.
Probable cause:
The following contributing factors were identified:
- Hazardous weather conditions were forecast and present at the drop site near Peak View, which included strong gusting winds and mountain wave activity, producing turbulence. These
conditions were likely exacerbated by the fire and local terrain.
- The Rural Fire Service continued the B134 tasking to Adaminaby when they learned that no other aircraft would continue to operate due to the environmental conditions. In addition, they relied on the pilot in command to assess the appropriateness of the tasking to Adaminaby without providing them all the available information to make an informed decision on flight safety.
- The pilot in command of B134 accepted the Adaminaby fire-ground tasking, which was in an area of forecast mountain wave activity and severe turbulence. After assessing the conditions as unsuitable, the crew accepted an alternate tasking to continue to the Good Good (Peak View) fire-ground, which was subject to the same weather conditions. The acceptance of these taskings were consistent with company practices.
- Following the partial retardant drop and left turn, the aircraft was very likely subjected to hazardous environmental conditions including low-level windshear and an increased tailwind component, which degraded the aircraft’s climb performance.
- While at a low height and airspeed, it was likely the aircraft aerodynamically stalled, leading to a collision with terrain.
- Coulson Aviation's safety risk management processes did not adequately manage the risks associated with large air tanker operations. There were no operational risk assessments conducted or a risk register maintained. Further, as safety incident reports submitted were mainly related to maintenance issues, operational risks were less likely to be considered or monitored. Overall, this limited their ability to identify and implement mitigations to manage the risks associated with their aerial firefighting operations. (Safety issue)
- Coulson Aviation did not provide a pre-flight risk assessment for their firefighting large air tanker crews. This would provide predefined criteria to ensure consistent and objective decision-making with accepting or rejecting tasks, including factors relating to crew, environment, aircraft and external pressures. (Safety issue)
- The New South Wales Rural Fire Service had limited large air tanker policies and procedures for aerial supervision requirements and no procedures for deployment without aerial supervision.(Safety issue)
- The New South Wales Rural Fire Service did not have a policy or procedures in place to manage task rejections, nor to communicate this information internally or to other pilots working in the same area of operation. (Safety issue)

Other factors that increased risk:
- The B134 crew were very likely not aware that the 'birddog' pilot had declined the tasking to Adaminaby fire-ground, and the smaller fire-control aircraft had ceased operations in the area, due to the hazardous environmental conditions
- In the limited time available, the remainder of the fire-retardant load was not jettisoned prior to the aircraft stalling.
- Coulson Aviation did not include a windshear recovery procedure or scenario in their C-130 Airplane Flight Manual and annual simulator training respectively, to ensure that crews consistently and correctly responded to a windshear encounter with minimal delay. (Safety issue)
- Coulson Aviation fleet of C-130 aircraft were not fitted with a windshear detection system, which increased the risk of a windshear encounter and/or delayed response to a windshear encounter during low level operations. (Safety issue)
- The New South Wales Rural Fire Service procedures allowed operators to determine when pilots were initial attack capable. However, they intended for the pilot in command to be certified by the United States Department of Agriculture Forest Service certification process. (Safety issue)

Other findings:
- The aircraft's cockpit voice recorder did not record the accident flight, which resulted in a valuable source of safety information not being available. This limited the extent to which potential factors contributing to the accident could be identified.
Final Report:

Crash of a Lockheed C-130BZ Hercules in Goma

Date & Time: Jan 9, 2020
Type of aircraft:
Operator:
Registration:
403
Flight Type:
Survivors:
Yes
Schedule:
Beni - Goma
MSN:
3750
YOM:
1962
Location:
Region:
Crew on board:
8
Crew fatalities:
Pax on board:
59
Pax fatalities:
Other fatalities:
Total fatalities:
0
Circumstances:
The four engine airplane was completing a flight from Beni to Goma, carrying 59 South African troops and eight crew members from the 28th Squadron on behalf of the MONUSCO (Mission de l’Organisation des Nations unies pour la stabilisation en République Démocratique du Congo). The approach and landing were completed in heavy rain falls. After touchdown, the airplane veered off runway to the left and came to rest in a grassy area with the left wing broken in two and the n°1 engine on fire. All 67 occupants escaped uninjured and the fire was quickly contained. However, the aircraft seems to be damaged beyond repair.

Crash of a Lockheed C-130H Hercules in the Drake Passage: 38 killed

Date & Time: Dec 9, 2019 at 1813 LT
Type of aircraft:
Operator:
Registration:
990
Flight Phase:
Flight Type:
Survivors:
No
Schedule:
Punta Arenas - Teniente Marsh
MSN:
4776
YOM:
1978
Country:
Region:
Crew on board:
17
Crew fatalities:
Pax on board:
21
Pax fatalities:
Other fatalities:
Total fatalities:
38
Circumstances:
The four engine airplane departed Santiago de Chile at 1021LT and landed at Punta Arenas for a technical stop at 1444LT. It took off at 1653LT on a leg to Teniente Rodolfo Marsh-Presidente Eduardo Frei Montalva Airport located on King George Island, Antarctica, carrying 21 passengers and 17 crew members. After flying a distance of about 390 NM, while in cruising altitude, the radar contact was lost, vertical to the Drake Passage. SAR operations were initiated jointly by the Chilean, Uruguay and Argentine Air Forces which dispatched several aircraft over the area. Two days later, debris were found floating on water. It seems that none of the 38 occupants survived the crash.

Crash of a Lockheed KC-130J Hercules in the Pacific Ocean: 5 killed

Date & Time: Dec 6, 2018 at 0200 LT
Type of aircraft:
Operator:
Registration:
167981
Flight Phase:
Flight Type:
Survivors:
No
Schedule:
Iwakuni - Iwakuni
MSN:
5617
YOM:
2009
Flight number:
Sumo 41
Country:
Region:
Crew on board:
5
Crew fatalities:
Pax on board:
0
Pax fatalities:
Other fatalities:
Total fatalities:
5
Circumstances:
The crew departed Iwakuni Airport on a refuelling mission over the Pacific Ocean under callsign 'Sumo 41'. Following a night refuelling operation, the four engine airplane collided with a McDonnell Douglas F/A-18 Hornet. Both aircraft went out of control and crashed into the ocean some 200 miles off Muroto Cape, Japan. The United States Marine Corps confirms that two Marines have been found. One is in fair condition and the other has been declared deceased by competent medical personnel. All five crew members from the Hercules are still missing after two days of SAR operations and presumed dead. The KC-130 Hercules was assigned to Marine Aerial Refueler Transport Squadron 152 (the Sumos), 1st Marine Aircraft Wing.
Probable cause:
The CDA-RB’s report determined four interconnected causal factors led to the 6 December 2018 mishap. First, the flight lead (F/A-18 call sign, Profane 11) requested, and received approval for, an un-briefed, non-standard departure from the C-130 tanker (call sign, Sumo 41). This departure placed the mishap pilot (F/A-18 call sign, Profane 12) on the left side of the tanker. A standard departure would have placed both F/A-18s on the right side of the tanker. Second, Profane 11 chose an authorized, but not optimized, lighting configuration. After tanking, Profane 11 placed his external lights in a brightly lit overt setting, while the C-130’s lights remained in a dimly lit covert setting. These circumstances set the conditions for Profane 12 to focus on the overtly lit Profane 11 aircraft, instead of the dimly lit tanker. Third, Profane 12 lost sight of the C-130 and lost situational awareness of his position relative to the tanker resulting in a drift over the top of the C-130 from left to right. Fourth, Profane 12 was unable to overcome these difficult and compounding challenges created by the first three factors. As a result, when Profane 12 maneuvered his aircraft away from Profane 11, he moved from right to left and impacted the right side of the tanker’s tail section. It must be noted, this specific set of circumstances would have been incredibly difficult for any pilot, let alone a junior, or less proficient pilot to overcome.
The CDA-RB determined the previous 2018 mishap command investigation did not capture a completely accurate picture of the event. The CDA-RB determined portions of the investigation contained a number of inaccuracies. Specifically, the 2018 command investigation incorrectly concluded medication may have been a causal factor in the mishap, the mishap pilot was not qualified to fly the mission, AN/AVS-11 night vision devices contributed to the mishap, and the previously mentioned mishap in 2016 had not been properly investigated. These conclusions are not supported by the evidence, and are addressed in detail in the CDA-RB report. While the 2018 CI contains a few inaccuracies, the CDA-RB does confirm the command investigation’s conclusions related to organizational culture and command climate as contributing factors to the mishap.
The CDA-RB made 42 recommendations to address institutional and organizational contributing factors. As a result, the Assistant Commandant directed 11 actions to address manpower management, training, operations, and medical policies. The Director of the Marine Corps Staff will lead the coordination of all required actions to ensure proper tracking and accomplishment.