2011 Afghanistan Boeing Chinook shootdown

From Infogalactic: the planetary knowledge core
Jump to: navigation, search
2011 Afghanistan Boeing Chinook shootdown
CH-47 Chinook in Bagram.jpg
A Boeing CH-47D Chinook helicopter in Bagram, Afghanistan, similar to the one that was shot down
Shootdown summary
Date 6 August 2011 (2011-08-06)
Summary Shot down by rocket-propelled grenade
Site Tangi Valley, Maidan Wardak Province, Afghanistan
Lua error in package.lua at line 80: module 'strict' not found.
Passengers 33
Crew 5
Fatalities 38
Survivors 0
Aircraft type Boeing CH-47D Chinook
Operator United States Army
Registration 84-24175

On 6 August 2011, a U.S. CH-47D Chinook military helicopter operating with the call sign Extortion 17 (pronounced "one-seven") was shot down while transporting a Quick Reaction Force attempting to reinforce a Joint Special Operations Command unit of the 75th Ranger Regiment in the Tangi Valley in Maidan Wardak province, southwest of Kabul, Afghanistan.[1][2][3][4]

The resulting crash killed all 38 people on board including 17 US Navy SEALs, two United States Air Force Pararescue, one United States Air Force Combat Control Team member, one pilot and two crewmen of the United States Army Reserve, one pilot and one crewman of the United States Army National Guard, seven members of the Afghan National Security Forces, and one Afghan interpreter.[1][5][6][7][8] At 30 American military personnel killed, the shootdown of Extortion 17 represents the greatest single-incident loss of American lives in Operation Enduring Freedom – Afghanistan, surpassing the 16 lost in the downing of Turbine 33, a 160th Special Operations Aviation Regiment (Airborne) MH-47 helicopter, during Operation Red Wings on 28 June 2005.[2]

Background

In March 2009, the U.S. 10th Mountain Division established a base in Tangi Valley after increased Taliban activity in the area. American, French and Afghan National Police forces carried out a three-day sweep of the area, and the area was then deemed secure. In April 2011, American forces turned over control of Combat Outpost Tangi to Afghan government forces. However, the Afghan government forces did not occupy the base, which was seized by the Taliban shortly after the departure of American forces.

American forces continued to carry out operations in the area (mostly via helicopter and using special forces), encountering resistance from Taliban fighters on several occasions. For example, on 8 June 2011 another Chinook helicopter was engaged from five to six locations (i.e., points of origin) with 14 rocket-propelled grenades, forcing the crew to abort their mission.[9][10]

Timeline

After American intelligence services discovered in 2011 that senior Taliban leader Qari Tahir was possibly in Tangi Valley, Wardak province, Afghanistan, local American forces launched a mission to apprehend or kill him.[11] At 22:37 (local time) on the night of 5 August, a platoon of 47 U.S. Army Rangers left a forward operating base in Logar Province via two CH-47D transport helicopters, one of which would later be involved in the accident.[9][10][11] After a 20-minute flight (around 23:00), the two Chinook helicopters landed near the compound ostensibly containing Tahir, offloaded the Ranger platoon and returned to base.[11]

The mission was deemed high risk; two AH-64 Apache helicopters, an AC-130 gunship, and other additional intelligence, surveillance and reconnaissance (ISR) aircraft supported the troop transports on their approach and remained with the ground forces afterwards.[11] Seventeen U.S. Navy SEALs remained in reserve at the forward operating base.[11][12]

As the Rangers approached the target compound, ISR aircraft observed several people leaving the compound. This group grew in number over the course of the night, but American forces were at first too preoccupied to engage. At 23:30, one of the Apache support helicopters engaged in a brief skirmish with a different group of eight Taliban fighters 400 m (440 yd) north of the compound, killing six.[11]

Separately, ISR aircraft continued to observe the unengaged group from the compound. Originally just two people, the group eventually swelled to a total of nine or ten fighters, and the special operations task force commander and the Immediate Reaction Force commander became concerned that it might include Tahir. At 01:00, they decided to engage the group with the SEAL reserves.[9][11]

Almost an hour later (01:50), the aviation brigade commander approved a new landing zone for infiltration of the SEAL team. The landing zone had been examined for a previous mission but had not yet been used.[11]

At 02:00, the special operations task force commander and the Immediate Reaction Force commander decided to add additional (non-SEAL) reinforcements, increasing the size of the team to 33. In order to speed disembarkation, all troops were loaded on a single CH-47D helicopter for transport; the other Chinook would approach the landing zone second as a decoy. Around 02:23, the two helicopters departed the forward base.[9][11]

Meanwhile, the group of Taliban fighters split in two. At 02:15, one group of three Taliban fighters took a position in a stand of trees; the remaining six or seven men entered a building located some 2 km (1.2 mi) from the target compound.[11] Going forward, the two AH-64 Apache helicopters would be engaged in tracking those two groups of Taliban, and hence unable to provide surveillance or fire support to the inbound helicopter carrying the SEAL team.[12][13]

Six minutes prior to reaching the landing zone, the empty CH-47D left the formation as planned. The helicopter carrying the SEALs proceeded to the landing zone alone, without external lighting. During the Ranger insertion earlier that night, the CH-47D had approached from the south; this time, it approached from the northwest. The helicopter made its last radio transmission stating that it was one minute away from the landing zone, then descended to an altitude of 100–150 ft (30–46 m) and slowed to a speed of 50 kn (58 mph; 93 km/h) as it approached the landing zone.[9][11]

Around 02:38, the helicopter was fired upon and shot down by a previously undetected group of Taliban fighters approximately 220 m (240 yd) south of the helicopter. The group fired two or three RPG rounds from a two-story building, the second striking one of the helicopter's three aft rotor blades. The resulting explosion destroyed the aft rotor assembly. In less than five seconds, the helicopter crashed, killing all occupants, and approximately 30 seconds later, one of the AH-64 Apache helicopters radioed in the crash.[9][11]

Six minutes later, the Rangers concluded securing the compound, detained several people and began to move on foot toward the crash site. They reached the site at 04:12 and found no survivors. Several minutes later, a 20-man Pathfinder team (specializing in downed-aircraft rescue and recovery) arrived at the site.[11]

By 16:25, all of the remains were taken from the crash site via ground convoy and transported to Combat Outpost Sayyid Abad. Recovery of wreckage from the crash site lasted until 9 August 2011.[11]

Victims

Casualties from the event included:[14]

The 30 American deaths represent the greatest loss of U.S. military lives in a single incident in the war in Afghanistan that began in 2001.[7][20][21]

Fifteen of the Navy SEALs that were killed were members of the Naval Special Warfare Development Group (DEVGRU),[5][22][20] while the other two Navy SEALs were from an unidentified West Coast-based unit. The five other Navy casualties were NSW (Naval Special Warfare) support personnel; in addition to these, three AFSOC operators, one Combat Controller and two Pararescuemen, all members of the 24th Special Tactics Squadron, died in the crash. Their deaths are the greatest single loss of life ever suffered by the U.S. Special Operations community in the 24-year history of the U.S. Special Operations Command.[5][22][15][23]

Aftermath

In the afternoon of 6 August, a flash flood swept through the area, washing away parts of the wreckage.

Early media reports suggested that the Army had been tardy to recover flight recorders from the downed Chinook, and, as a consequence, the recorders had been swept away by the flood.[11][24] These reports were erroneous; the CH-47D airframe does not contain flight recorders, although the MH-47 variant does have a flight data recorder and cockpit voice recorder.[25][original research?]

Four years after the downing of Extortion 17, there were many theories about a possible government coverup. The official statement from U.S. Central Command stated that a Taliban fighter scored a lucky shot with a rocket-propelled grenade. It was reported that the Taliban fighters had no information of the helicopter's flight path and that they had been in the right place at the right time. A Department of Defense official asserted that there were no leaks from the Afghans.[citation needed] Doubts about this story were raised by families and other concerned citizens despite the fact that the Navy SEAL team aboard Extortion 17 was a different squadron than that which had killed Osama bin Laden three months earlier. The theories suggest that Afghan forces leaked information to the Taliban about the mission.[26]

Response

The U.S. military helicopter carrying special operations forces to a night-raid in the Tangi Valley of Wardak Province, was most likely brought down by a rocket-propelled grenade, according to military officials.[22][20] Taliban spokesman Zabiullah Mujahid, confirmed that eight of the movement's fighters had been killed in the assault on the compound. He said: "They wanted to attack our Mujahideen who were in a house, but our Mujahideen resisted and destroyed a helicopter with a rocket-propelled grenade."[5]

Later accounts

Subsequent reports stated that on the night during which the helicopter had been delivering reinforcements to personnel of the 75th Ranger Regiment, another special operations unit engaged in a night raid on a compound to kill or capture a senior Taliban leader.[7][27][28] During the battle, American forces observed a small group of Taliban trying to flee the scene. The group probably contained the commander and a few of his bodyguards, while the remaining Taliban fighters offered resistance in an effort to buy the group enough time to escape. In order to prevent this, American forces called in for support.[29]

Other reports alleged that the Taliban had laid an elaborate trap for American special-operations forces, luring them in with false information. A senior Afghan government official, speaking anonymously, said that Taliban commander Qari Tahir had fed American forces false information about a meeting of insurgent leaders and fighters waited for the helicopter from both sides of a steep valley: "The Taliban knew which route the helicopter would take. That's the only route, so they took positions on either side of the valley on mountains and as the helicopter approached, they attacked it with rockets and other modern weapons. It was brought down by multiple shots."[30]

Reporting of event

Television

On 12 August 2011, Jim Lehrer of the PBS NewsHour announced that he would report the Honor Roll at the end of the program with names and photographs of all 30 men. He said, "And now, to our honor roll of American Service Personnel killed in the Iraq and Afghanistan conflicts. Yesterday, the Pentagon released the names of the 30 troops-- Navy SEALs, soldiers, and airmen, killed in the helicopter downed by Taliban fighters in eastern Afghanistan last weekend. Here, in silence, are the names and photographs of all 30 men."[31][32] NBC News reported that the Pentagon released the names of the 30 Americans killed.[33]

Newspapers

The New York Post reported that the Pentagon released 30 names from the crash.[34] Kevin Sieff and Greg Jaffe of The Washington Post reported that U.S. officials confirmed the deaths, including 22 SEALs.[35] The Seattle Times and The New York Times also reported this information.[36][37]

Subsequent events

After the shootdown of Extortion 17, the insurgent responsible used a two-way radio to brag to others about the act. American signals intelligence aircraft intercepted these transmissions and subsequently tracked the individual and his accomplice. American intelligence officials identified this individual as "OBJECTIVE GINOSA." On the night of 8 August 2011, an F-16 dropped four GBU-54 "Laser JDAM" bombs on the man, his accomplice and four associates in the Chak Valley, which lies to the west of the Tangi Valley. Monitored and controlled by a Joint Terminal Attack Controller at Forward Operating Base Shank via a General Atomics MQ-1 Predator unmanned aerial vehicle, all six were positively confirmed killed by the bomb strike and subsequent attacks by a Lockheed AC-130 gunship and two Boeing AH-64 Apache helicopter gunships.[2][38]

On 10 August 2011, the U.S. military stated that the insurgent who fired the rocket-propelled grenade had been killed only two days afterward in an F-16 airstrike, saying only that intelligence gained on the ground provided "a high degree of confidence" that the person was among those killed in the airstrike from two days earlier, but providing no other details.[39]

During the same Pentagon news conference in which he announced that the F-16 airstrike had incapacitated "less than 10" of the insurgents involved, International Security Assistance Force (ISAF) commander in Afghanistan John R. Allen said that the military investigation would also review whether small-arms fire or other causes might have contributed to the downing.[39]

Following the withdrawal of U.S. forces in April 2011, Tangi valley became a major staging area for attacks on Kabul (located just 60 miles away). Tangi valley remained under Taliban control until April 2013, when more than 1,000 Afghan security forces personnel launched an offensive in an effort to clear the area of Taliban fighters.[40]

In October 2011, U.S. Central Command (CENTCOM) announced that an investigation following the shootdown concluded "that all operational decisions, linked to the incident, were deemed tactically sound." The article stated that the helicopter crashed after an RPG round impacted the aft rotor assembly.[11]

In 2013, Congressman Jason Chaffetz said that he would hold an investigation of the United States House Oversight Subcommittee on National Security into the matter.[41] At the subsequent hearing in February 2014, Pentagon representative Garry Reid defended the decision to undertake the mission and denied that the Taliban had any advance knowledge of it. He said that insurgents had assumed a strong tactical position without knowledge of the helicopter's flight path.[42]

In 2017, Air Force captain Joni Marquez, the firing officer on an AC-130 gunship that had accompanied Extortion 17 on the final flight, made a similar claim. Ranger assault helicopters had already engaged the enemy and killed six of eight Taliban fighters, causing the other two to retreat. In her first interview about the incident, Marquez said: "I had the sensor operators immediately shift to the eight insurgents the helicopters had taken out. Two were still alive." Captain Marquez claims that had the AC-130 been allowed to fire on the remaining enemy insurgents, Extortion 17 would not have been shot down. Warnings from her crew to turn the Chinook back or cancel their mission went unheeded.[43][44]

American rules of engagement were tightened by Gen. Stanley McChrystal in 2009 in order to improve American counterinsurgency strategy.[45] McChrystal cited a previous "overreliance on firepower and force protection" and the need to reduce civilian casualties and win the cooperation of the local population.[43][45]

See also

References

  1. ↑ 1.0 1.1 Lua error in package.lua at line 80: module 'strict' not found.
  2. ↑ 2.0 2.1 2.2 Lua error in package.lua at line 80: module 'strict' not found.
  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. ↑ 5.0 5.1 5.2 5.3 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 7.2 Lua error in package.lua at line 80: module 'strict' not found.
  8. ↑ Lua error in package.lua at line 80: module 'strict' not found.
  9. ↑ 9.0 9.1 9.2 9.3 9.4 9.5 Lua error in package.lua at line 80: module 'strict' not found.
  10. ↑ 10.0 10.1 Lua error in package.lua at line 80: module 'strict' not found.
  11. ↑ 11.00 11.01 11.02 11.03 11.04 11.05 11.06 11.07 11.08 11.09 11.10 11.11 11.12 11.13 11.14 11.15 Lua error in package.lua at line 80: module 'strict' not found.
  12. ↑ 12.0 12.1 Lua error in package.lua at line 80: module 'strict' not found.
  13. ↑ 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. ↑ 15.0 15.1 15.2 15.3 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. ↑ 20.0 20.1 20.2 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. ↑ 22.0 22.1 22.2 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. ↑ 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. ↑ 39.0 39.1 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. ↑ 43.0 43.1 Lua error in package.lua at line 80: module 'strict' not found.
  44. ↑ Lua error in package.lua at line 80: module 'strict' not found.
  45. ↑ 45.0 45.1 Lua error in package.lua at line 80: module 'strict' not found.
Retrieved from "https://infogalactic.com/w/index.php?title=2011_Afghanistan_Boeing_Chinook_shootdown&oldid=726748089"