2021 Philippine Air Force C-130 crash

From Infogalactic: the planetary knowledge core
Jump to: navigation, search
2021 Philippine Air Force C-130 crash
File:C-130H 5125.jpg
5125, the C-130H of the Philippine Air Force involved in the crash, photographed in March 2021
Accident summary
Date July 4, 2021 (2021-07-04)
Summary Failed go-around attempt, resulting in loss of control; under investigation
Site Patikul, near Jolo Airport, Sulu, Philippines
Lua error in package.lua at line 80: module 'strict' not found.
Passengers 96
Crew 8
Injuries (non-fatal) 46
Fatalities 50
Survivors 54
Aircraft type Lockheed C-130H Hercules
Operator  Philippines Air Force
Registration 5125
Flight origin Villamor Air Base, Pasay, Philippines
Stopover Lumbia Airfield, Cagayan de Oro, Philippines
Destination Jolo Airport, Sulu, Philippines

On July 4, 2021, a Lockheed C-130 Hercules aircraft of the Philippine Air Force (PAF) crashed after an attempted landing at Jolo Airport in Sulu, Philippines.[1] With 53 deaths, of which 50 people were on the aircraft and 3 on the ground, the incident is the deadliest aviation accident in Philippine military history, the fourth deadliest on Philippine soil, and the second deadliest to occur in 2021, behind Sriwijaya Air Flight 182.[2]

Background

Aircraft

The aircraft involved in the incident is a Lockheed C-130H Hercules operated by the Philippine Air Force (PAF) with the tail number 5125.[3] A former United States Air Force aircraft in service since February 1988, it was acquired by the PAF through a grant by the United States government's Defense Security Cooperation Agency in January 2021.[4][5] The Philippine military has maintained that the aircraft was in good condition and had 11,000 flying hours left before its next maintenance was due.[6] The PAF has three other C-130s in its inventory prior to the crash; two C-130s undergoing maintenance and repair in Portugal and one C-130 operational.[7]

Passengers and crew

At the time of the crash, there were 104 military personnel on board; including 3 pilots and 5 other aircrew.[8] 50 of the personnel came from the Philippine Army's 4th Infantry Division training unit of Malaybalay, Bukidnon.[9] Five military vehicles were also on board.[10] The soldiers on board were meant to augment the Jolo-based 11th Infantry Division which is after the Abu Sayyaf group operating in the area.[11][12]

Accident

Syntax error
<maplink zoom="12" latitude="<strong class="error"><span class="scribunto-error" id="mw-scribunto-error-2">Lua error in package.lua at line 80: module 'strict' not found.</span></strong>" longitude="<strong class="error"><span class="scribunto-error" id="mw-scribunto-error-3">Lua error in package.lua at line 80: module 'strict' not found.</span></strong>" text="[Full screen]">

[


{"type": "FeatureCollection",

 "features": [


{ "type": "Feature",

  "geometry": {"type": "Point", "coordinates": [Lua error in package.lua at line 80: module 'strict' not found.,Lua error in package.lua at line 80: module 'strict' not found.] },
  "properties": {
   "title": "Lumbia Airfield", 
   "description": "",
   "marker-symbol": "-number", "marker-size": "medium", "marker-color": "#B80000" }
}

, { "type": "Feature",

  "geometry": {"type": "Point", "coordinates": [Lua error in package.lua at line 80: module 'strict' not found.,Lua error in package.lua at line 80: module 'strict' not found.] },
  "properties": {
   "title": "Crash site", 
   "description": "",
   "marker-symbol": "-number", "marker-size": "medium", "marker-color": "#B80000" }
}





























] }

]</maplink>

On July 4, 2021, the aircraft took off from Villamor Air Base in Pasay and headed to Lumbia Airfield in Cagayan de Oro. From Cagayan de Oro, the aircraft transported personnel to Jolo, Sulu.[13] At 11:30 a.m. Philippine Time (UTC+08:00), the plane crashed after attempting to land at Jolo Airport.[1][14][15] The aircraft overshot the runway, crashed in the nearby municipality of Patikul, and caught fire.[16][17]

Fifty military personnel on board, including the pilot in command, and 3 civilians on the ground died, while 46 occupants on board and 4 civilians on the ground were injured.[18][19][20] The 3 civilian deaths involved quarry workers.[21][22] The crash is the Philippine Air Force's deadliest aviation accident in history, surpassing the 1971 Douglas C-47 Skytrain crash in Floridablanca, Pampanga which killed 40 people.[23][24]

Response

The Joint Task Force Sulu (JTF Sulu) of the Philippine military conducted a search and rescue operation to retrieve the bodies of the dead and assist survivors.[25] Tausug civilians as well as members of the Citizens Armed Forces Geographical Unit (CAFGU) militia also reportedly helped extract survivors of the burning crash site.[26] The Armed Forces of the Philippines (AFP), the Philippine National Police's Police Regional Office Bangsamoro Autonomous Region (PRO BAR), and the Sulu provincial government promised assistance to the military and affected civilians on the ground.[13][27][28] The United States sent an emergency medical services unit to provide support to the survivors of the crash.[29][30]

Most people who died from the crash were burned beyond recognition and their identities had to be determined through various means including DNA testing and relying on surviving clothing and accessories and body marks.[31]

On July 5, President Rodrigo Duterte travelled to the Western Mindanao Command of the AFP in Zamboanga City to pay his respects to the families of the military personnel who were killed in the crash.[32] The AFP also declared a six-day mourning period, ordering that all flags in camps and military installation across the country be flown at half-mast.[8] Several countries sent condolences to the Philippines following the crash.[33]

Due to the crash, the first air-to-air bilateral training of the Japan Air Self-Defense Force (JSDF) and the Philippine Air Force at the Clark Air Base in Pampanga was modified. In-flight training was cancelled with the exercise focusing on on-ground training; including load or offload training and simulated emergency procedure which involved a lone C-130 of the JSDF.[34]

The modernization program has also been a subject of discussion in the Congress of the Philippines, both in the House of Representatives and the Senate. The policy of acquiring second-hand military assets through foreign loans was also questioned.[7]

The crash was captured on camera, and a video of the incident later circulated on social media.[35]

Investigation

The Department of National Defense and the military has urged the public to refrain from spreading "highly speculative statements" about the incident and assured that an investigation on the crash is already being done.[36][37]

The military has ruled out the possibility that the crash was caused by an attack against the aircraft.[38] Among the angles being considered are the condition of the aircraft, the runway, if there was a human error, and if the plane was overloaded.[36] An investigating team from the AFP arrived at the crash site on July 5.[39] The aircraft's flight recorder and voice cockpit recorder were both recovered. Both were sent to the United States so that the recorded data from the devices could be retrieved.[40][41]

The military disclosed to the public in September 2021 that there is no single attributable cause for the crash in Sulu. The report said that the accident was "most probably due to actual or perceived material factors and induced human factors which were aggravated by local and environmental conditions.” It added that the “aircraft component, environmental condition and aircrew response led to unrecoverable stall in a critical phase of the aircraft operation".[42]

Aftermath

The first flight of a C-130 since the July crash by the Philippine military would be successfully made on December 11, 2021.[43]

See also

References

  1. 1.0 1.1 Lua error in package.lua at line 80: module 'strict' not found.
  2. ASN Aviation Safety Database Retrieved August 28, 2022.
  3. Lua error in package.lua at line 80: module 'strict' not found.
  4. Lua error in package.lua at line 80: module 'strict' not found.
  5. Lua error in package.lua at line 80: module 'strict' not found.
  6. Lua error in package.lua at line 80: module 'strict' not found.
  7. 7.0 7.1 Lua error in package.lua at line 80: module 'strict' not found.
  8. 8.0 8.1 Lua error in package.lua at line 80: module 'strict' not found.
  9. Lua error in package.lua at line 80: module 'strict' not found.
  10. Lua error in package.lua at line 80: module 'strict' not found.
  11. Lua error in package.lua at line 80: module 'strict' not found.
  12. Lua error in package.lua at line 80: module 'strict' not found.
  13. 13.0 13.1 Lua error in package.lua at line 80: module 'strict' not found.
  14. Lua error in package.lua at line 80: module 'strict' not found.
  15. Lua error in package.lua at line 80: module 'strict' not found.
  16. Lua error in package.lua at line 80: module 'strict' not found.
  17. Lua error in package.lua at line 80: module 'strict' not found.
  18. Lua error in package.lua at line 80: module 'strict' not found.
  19. Lua error in package.lua at line 80: module 'strict' not found.
  20. Lua error in package.lua at line 80: module 'strict' not found.
  21. Lua error in package.lua at line 80: module 'strict' not found.
  22. Lua error in package.lua at line 80: module 'strict' not found.
  23. Lua error in package.lua at line 80: module 'strict' not found.
  24. Lua error in package.lua at line 80: module 'strict' not found.
  25. Lua error in package.lua at line 80: module 'strict' not found.
  26. Lua error in package.lua at line 80: module 'strict' not found.
  27. Lua error in package.lua at line 80: module 'strict' not found.
  28. Lua error in package.lua at line 80: module 'strict' not found.
  29. Lua error in package.lua at line 80: module 'strict' not found.
  30. Lua error in package.lua at line 80: module 'strict' not found.
  31. Lua error in package.lua at line 80: module 'strict' not found.
  32. Lua error in package.lua at line 80: module 'strict' not found.
  33. Lua error in package.lua at line 80: module 'strict' not found.
  34. Lua error in package.lua at line 80: module 'strict' not found.
  35. Lua error in package.lua at line 80: module 'strict' not found.
  36. 36.0 36.1 Lua error in package.lua at line 80: module 'strict' not found.
  37. Lua error in package.lua at line 80: module 'strict' not found.
  38. Lua error in package.lua at line 80: module 'strict' not found.
  39. Lua error in package.lua at line 80: module 'strict' not found.
  40. Lua error in package.lua at line 80: module 'strict' not found.
  41. Lua error in package.lua at line 80: module 'strict' not found.
  42. Lua error in package.lua at line 80: module 'strict' not found.
  43. Lua error in package.lua at line 80: module 'strict' not found.