Fact-checked by Grok 2 weeks ago

Task Force 20

Task Force 20 was a temporary (JSOC) task force established for operations during the 2003 U.S.-led invasion of Iraq, drawing primarily from elite Tier 1 units such as the Army's 1st Special Forces Operational Detachment-Delta () and the Navy's Naval Special Warfare Development Group (DEVGRU), with aviation support from the 160th Special Operations Aviation Regiment and augmentation by conventional forces including elements of the . Its core missions encompassed , sensitive site exploitation to uncover purported weapons of mass destruction (WMDs), and the capture or destruction of critical Iraqi military installations, particularly in the western desert region ahead of the main coalition ground offensive. Deployed covertly prior to the March 20, 2003, commencement of major combat operations, Task Force 20 executed high-risk raids such as a helicopter assault on a suspected WMD facility at Al Qadisiyah and an attempted precision airstrike targeting in , though the latter failed to confirm his elimination. After the rapid fall of on April 9, 2003, the task force pivoted to the pursuit of high-value targets (HVTs) from the Saddam regime, conducting numerous raids that disrupted Ba'athist leadership networks. A defining achievement came on July 22, 2003, when Task Force 20 operators, reinforced by the , assaulted a safehouse based on intelligence tips, resulting in the deaths of Saddam's sons Uday and along with two associates in intense . Task Force 20 later reorganized into , incorporating CIA elements to enhance intelligence-driven HVT captures, including the eventual apprehension of in December 2003 near , underscoring JSOC's adaptation to post-invasion demands amid the absence of large-scale WMD stockpiles.

Background and Formation

Origins within JSOC

(TF 20) originated as a specialized under the (JSOC), formed in early 2003 to support the impending invasion of . Drawing from JSOC's elite special mission units, it integrated assault squadrons from the Army's 1st Special Forces Operational Detachment-Delta () and the Navy's Naval Special Warfare Development Group (DEVGRU, formerly ), augmented by the Air Force's for combat control and pararescue capabilities, as well as all three battalions of the for and airfield seizure roles. This composition leveraged JSOC's established framework for tier-one , which had evolved since the command's activation on December 15, 1980, to conduct and missions requiring seamless inter-service coordination. Positioned initially in the western Iraqi desert, TF 20's formation emphasized rapid deployment and operational secrecy, incorporating supporting elements such as intelligence analysts, aviation assets, and from conventional forces to enable self-sustained operations. The task force was designed to execute , sensitive site exploitation—particularly searches for weapons of mass destruction—and the capture or neutralization of priority Iraqi leadership and infrastructure ahead of conventional ground forces crossing the border on , 2003. This pre-invasion posture built on JSOC's prior experience in operations like the 1991 , where similar ad hoc task forces had targeted launchers, but scaled up for the broader regime-change objectives of Operation Iraqi Freedom. The origins of TF 20 within JSOC underscored a doctrinal shift toward integrating special operations with intelligence-driven targeting, minimizing reliance on broader coalition commands for time-sensitive strikes. Commanded by senior JSOC officers, it operated with a flat hierarchy to facilitate quick decision-making, reflecting lessons from expansions in funding and authorities under the U.S. Special Operations Command (USSOCOM), established in 1987. While details of its exact activation date remain classified, declassified accounts confirm its assembly from JSOC's standing rotational forces, ensuring operational readiness without depleting other global commitments.

Initial Objectives and Mandate

Task Force 20, formed under the (JSOC) in early 2003, received an initial mandate to execute operations, sensitive site exploitation for potential weapons of mass destruction (WMD), and the seizure of key Iraqi military bases and installations in support of the impending invasion. These tasks aimed to gather actionable intelligence on regime assets, neutralize threats from prohibited weapons programs, and disrupt Iraqi command infrastructure ahead of conventional ground forces, thereby facilitating rapid regime decapitation and minimizing casualties. Central to the task force's objectives was the prioritization of (HVT) operations, specifically the location, capture, or elimination of and his sons, Uday and Qusay, to dismantle Ba'athist leadership and prevent organized resistance during the invasion phase beginning March 20, 2003. This directive leveraged JSOC's expertise in raids, integrating elite assault elements with aviation support for time-sensitive targeting, while emphasizing operational secrecy to exploit fleeting intelligence windows. The mandate reflected a strategic calculus prioritizing precision strikes over broad-area engagements, with Task Force 20 operating covertly to avoid compromising larger plans, though early WMD site searches produced scant verified yields amid contested intelligence assessments. Commanders, including figures like General , resolved inter-service debates by affirming JSOC's lead role in HVT hunts, underscoring the task force's alignment with national objectives for swift political-military resolution in .

Organizational Structure

Component Units and Personnel

Task Force 20 primarily comprised elite counterterrorism units from the (JSOC), including assault elements from the Army's 1st Operational Detachment-Delta () and the Navy's Naval Special Warfare Development Group (DEVGRU). These core special mission units formed the nucleus for raids, , and sensitive site exploitation missions. The task force incorporated support from the , which provided platoon- and company-sized elements for perimeter security, quick reaction forces, and cordon operations during high-risk engagements. Aviation assets from the 160th Special Operations Aviation Regiment (SOAR), known as the Night Stalkers, supplied MH-60 Black Hawks, MH-47 Chinooks, and AH-6/MH-6 Little Birds for insertion, extraction, and . Additional enablers included combat controllers and pararescuemen from the 24th Special Tactics Squadron for airfield seizure and medical support. Personnel numbers remained classified, but the structure relied on small, specialized teams—typically 12-man or DEVGRU troops—for targeted operations, augmented by larger contingents and intelligence personnel from units like the . Commanded by Dell L. Dailey, TF 20 integrated conventional support, such as a battalion from the and tanks, for operations in western . Overall, the force emphasized JSOC's tier-one operators, with rotations of like Delta's B Squadron deploying for the 2003 invasion phase.

Command and Control

Task Force 20 operated under the direct command of the (JSOC), which exercised strategic oversight and operational control during the . JSOC's commander, Lieutenant General Dell Dailey, provided high-level direction, integrating Task Force 20's activities with broader U.S. Central Command (CENTCOM) objectives while maintaining operational independence for time-sensitive missions targeting high-value individuals and weapons of mass destruction sites. This structure emphasized decentralized execution, with tactical decisions delegated to on-scene leaders to enable rapid response in fluid combat environments. The task force's command hierarchy centered on a core leadership team drawn primarily from the 1st Special Forces Operational Detachment-Delta (), supplemented by officers from other JSOC elements such as the Naval Special Warfare Development Group (DEVGRU) and the 160th Aviation Regiment (SOAR). Squadron commanders from typically led individual raids and reconnaissance operations, coordinating with attached Ranger battalions from the for support and the 24th Special Tactics Squadron for airfield seizures and combat control. This joint manning facilitated seamless integration, with command posts established at forward locations like H-1 airfield to minimize response times. Control mechanisms relied on advanced real-time intelligence fusion from JSOC's (ISA), which provided targeting data via secure communications networks, enabling dynamic adjustments to mission parameters. Aviation assets under SOAR command handled insertions using MH-60 and MH-47 helicopters, with from attached AC-130 gunships and F-117 stealth fighters coordinated through joint terminal attack controllers embedded in assault teams. Ground elements maintained through embedded teams and liaison officers with conventional forces, such as , to deconflict operations and share battlefield intelligence. By April 2003, Task Force 20 had established a forward command post co-located with units near An-Nasiriyah, enhancing while preserving JSOC's compartmentalized operational security. This framework prioritized agility over rigid chains of command, allowing Task Force 20 to conduct over 100 raids in the invasion's opening weeks, though it occasionally led to friction with conventional commanders over and intelligence sharing. Empirical assessments from post-operation reviews highlight the effectiveness of JSOC's model in high-threat environments, where empirical success rates in exceeded 80% for priority targets, attributed to the fusion of expertise with technological enablers like GPS-guided munitions and encrypted data links.

Operations during the 2003 Invasion of Iraq

Pre-Invasion Preparations

Task Force 20, under Joint Special Operations Command (JSOC), initiated preparations for Operation Iraqi Freedom in late 2002, drawing on the structure of prior task forces like Task Force Sword from Afghanistan to focus on high-value target (HVT) raids and sensitive site exploitation (SSE). Units including Delta Force, SEAL Team Six, and the 160th Special Operations Aviation Regiment (SOAR) integrated at staging bases in Kuwait, Jordan, and Saudi Arabia, where they conducted mission planning and rehearsals emphasizing rapid infiltration, direct action, and weapons of mass destruction (WMD) searches. Intelligence fusion was central to preparations, with JSOC analysts collaborating with CIA and () teams to produce target dossiers on , his family, and Ba'athist leadership, incorporating , , and human sources to map potential safe houses and command nodes. Aviation assets, including MH-60 Black Hawks and MH-47 Chinooks from the 160th SOAR, underwent route familiarization flights and low-level navigation training to evade Iraqi air defenses. Ground teams practiced breaching techniques and SSE protocols, prioritizing forensic collection for WMD evidence and regime documents. By early 2003, TF20 elements had forward-deployed to border areas, establishing covert links with Kurdish Peshmerga in the north and conducting border reconnaissance to identify infiltration corridors through sand berms and wadis in western . On the evening of March 19, 2003, select teams infiltrated ahead of the coalition's main ground assault, setting up observation posts and preparing for immediate SSE at priority sites like suspected WMD facilities and leadership bunkers. These actions positioned TF20 to exploit the initial chaos of the commencing March 20.

Key Combat Engagements

Task Force 20's engagements during the invasion phase emphasized rapid, covert direct action raids rather than prolonged battles, focusing on disrupting Iraqi command structures, securing suspected weapons sites, and pursuing high-value targets amid the coalition's swift advance toward Baghdad. Operating from forward locations established via early infiltration, TF20 elements, including Delta Force and SEAL Team Six operators supported by the 160th Special Operations Aviation Regiment, conducted strikes to neutralize border defenses on March 19, 2003. Helicopter assaults using MH-60 DAP gunships and AH-6 Little Birds targeted Iraqi observation posts and watchtowers along southern and western borders, clearing paths for special reconnaissance teams to insert into the western desert without significant ground resistance. As coalition forces pushed northward, TF20 shifted to urban and site-specific operations around in late March and early April. Raids targeted facilities linked to Iraq's weapons programs, such as the Al Qadisiyah Research Center (Objective Beaver) on March 27, 2003, where operators faced sustained small-arms fire from defenders during site exploitation for chemical or biological agents; the facility was secured after brief but intense combat, yielding documents but no prohibited materials. Similar actions exploited other suspected WMD locations throughout April, often involving close-quarters fighting against holdouts, though many sites proved empty or yielded only conventional arms. A high-profile in Baghdad's , conducted to capture , resulted in the killing of five Iraqi civilians caught in with security elements, but the target evaded capture; the operation highlighted the challenges of time-sensitive in fluid urban environments. By mid-April, TF20 forces executed a low-combat seizure of leader Muhammad Abbas (Abu Abbas) in a Baghdad safehouse, advancing efforts to dismantle regime-linked networks without major firefights. These actions contributed to the disruption of Iraqi leadership but yielded limited decisive kills during the invasion's high-mobility phase, as regime forces fragmented rapidly.

Post-Invasion High-Value Target Operations

Shift to Counterinsurgency

Following the on December 13, 2003, Task Force 20 redirected its efforts from Ba'athist regime holdouts to combating the escalating , which featured improvised explosive devices, ambushes, and bombings increasingly coordinated by foreign jihadists. This pivot aligned with the broader U.S. recognition that post-invasion stability required disrupting insurgent leadership networks rather than solely regime remnants, incorporating more aggressive direct-action raids and to yield intelligence on bomb-making cells and facilitators. By early 2004, as attacks surged— with over 1,000 U.S. troop deaths recorded in the first year post-invasion—Task Force 20 intensified operations in volatile areas like the , targeting figures affiliated with Ansar al-Islam and emerging elements. The task force's adaptation emphasized kinetic strikes integrated with and signals intercepts, evolving from isolated HVT hunts to network-centric tactics that aimed to degrade operational tempo through repeated disruptions. In spring 2004, amid uprisings in and , Task Force 20 supported conventional forces by conducting precursor raids that captured mid-level operatives, yielding documents and electronics that informed larger maneuvers. This phase saw the incorporation of aviation assets for rapid insertion and the expansion of detainee protocols to accelerate tip-offs, reflecting a doctrinal shift toward "find, fix, finish" cycles tailored to asymmetric threats. By mid-2004, Task Force 20 reorganized into (also referenced as in some operations), prioritizing and his network amid the insurgency's shift toward spectacular attacks, including beheadings and marketplace bombings. This redesignation facilitated a surge in raid frequency—exceeding 300 high-risk missions monthly by late 2004—and enhanced interagency collaboration with CIA paramilitary units for targeting. Such measures contributed to the capture or elimination of dozens of facilitators, though critics later noted the approach's emphasis on raids over population-centric stabilization efforts limited broader gains.

Notable Raids and Captures

Task Force 20 conducted the raid that resulted in the deaths of Uday and , sons of deposed Iraqi leader , on July 22, 2003, in , . The operation was initiated following a tip from an identifying the brothers' location in a residential villa. Elements of Task Force 20, including operators, coordinated with soldiers from the , deploying over 200 troops supported by Apache helicopters and armored vehicles. The assault faced heavy resistance, with the targets firing from upper floors using AK-47s and a ; U.S. forces responded with fire, grenades, and TOW missiles to breach defenses. The firefight lasted approximately four hours, culminating in the deaths of Uday, Qusay, their 14-year-old brother , and two bodyguards. Post-raid exploitation confirmed identities through dental records and DNA testing against samples from family members. This operation represented a significant early success in Task Force 20's missions, disrupting potential Ba'athist leadership continuity amid ongoing efforts. No U.S. casualties were reported, though the intensity highlighted the risks of direct-action raids against fortified holdouts. Beyond eliminations, Task Force 20's raids yielded captures of mid-level Ba'athist officials and insurgent facilitators, contributing to intelligence gains on Saddam Hussein's network, though specific high-profile captures were limited compared to kills in initial phases. Operations often involved night raids on suspected safehouses in central , leveraging for precision targeting. These efforts transitioned into broader patterns but underscored Task Force 20's role in degrading regime remnants through targeted disruptions.

Achievements and Strategic Contributions

Intelligence and Site Exploitation Successes

Task Force 20 executed sensitive operations targeting suspected weapons of mass destruction facilities during the early stages of the 2003 invasion, securing sites to collect materials for forensic analysis and prevent evidence destruction. On March 26, 2003, TF 20 elements, including aviation from the 160th Special Operations Aviation Regiment and ground forces from the 75th Ranger Regiment's 2nd Battalion, conducted a assault on the Al Qadisiyah Research Center northwest of Hadithah, a facility suspected of chemical and biological weapons research. Despite encountering heavy resistance with armor-piercing fire that damaged multiple aircraft—including two MH-47 Chinooks and three MH-60 Black Hawks—and wounding two soldiers, the raid succeeded in collecting environmental samples and documents for subsequent laboratory examination. These efforts, part of broader preemptive raids such as those at on March 20 and a desert landing strip on March 24, allowed TF 20 to exploit sites hours before conventional units arrived, preserving potential intelligence on Iraq's weapons programs. Although no operational WMD stockpiles were uncovered in TF 20's exploitations—consistent with later comprehensive surveys—the operations generated actionable reports on regime infrastructure and capabilities, informing U.S. Central Command's assessments of Iraqi denial and deception tactics. TF 20's rapid site seizures, including the April 1 airborne capture of Hadithah Dam, yielded data on defensive preparations and local command networks, which were analyzed to refine targeting priorities. In the post-invasion shift to hunts, exploitation of raided compounds produced documents, electronics, and detainee interrogations that mapped Ba'athist evasion strategies and early insurgent linkages, contributing to the for subsequent captures despite initial challenges in evidence handling. These activities demonstrated TF 20's role in fusing tactical gains with strategic intelligence, disrupting regime remnants even as broader WMD objectives remained unfulfilled.

Impact on Insurgent Networks

Task Force 20's high-value target operations in post-invasion Iraq focused on decapitating Ba'athist loyalist structures, beginning with the July 22, 2003, raid in Mosul that killed Saddam Hussein's sons, Uday and Qusay. This action eliminated potential rallying figures for regime remnants, disrupting efforts to organize unified resistance and forcing surviving networks into decentralized, less effective operations. The raid's site exploitation yielded documents and materials that mapped connections within Hussein's inner circle, enabling follow-on captures of associates and financiers. As Task Force 20 transitioned into in October 2003 under General Stanley McChrystal, its raids extended to broader insurgent elements, including early jihadist cells. These operations captured or killed mid-level commanders and facilitators, fragmenting communication lines and sowing that hampered and . High-value targeting campaigns like those conducted by JSOC elements, including TF20/121, removed key nodes from networks, temporarily reducing the ' ability to execute complex, synchronized attacks. Analyses of such efforts indicate that while tactical disruptions were evident—evidenced by gains leading to cascading arrests—the strategic degradation of insurgent networks required integration with population-centric measures, as isolated HVT kills often prompted rapid leadership succession in adaptive groups like al-Qaeda in Iraq precursors. By late 2003, the himself on December 13, stemming from TF121 leads originating in TF20 operations, further eroded Ba'athist cohesion, contributing to a shift where foreign fighters assumed greater prominence in the .

Controversies and Criticisms

Allegations of Operational Overreach

Task Force 20, during its operations in , faced allegations of detainee mistreatment that suggested operations extended beyond authorized capture missions into unauthorized and practices. Reports from U.S. soldiers assigned to support TF20 detailed instances where detainees captured in raids were subjected to , including beatings with fists, knees, and rifle butts upon arrival at forward sites, as well as exposure to extreme cold via ice baths and stress positions. These practices were linked to , a temporary near operated by TF20 (later redesignated as part of TF121), where detainees were held for short-term before transfer, often to CIA custody. Specific soldier testimonies described TF20 personnel employing military working dogs to intimidate detainees by having them bark aggressively or snap at , alongside mock executions and prolonged , which contravened standard U.S. military interrogation protocols under the Army Field Manual. A reported facility slogan, "No Blood, No Foul," encapsulated an alleged tolerance for that left no visible marks, as recounted by members of the 377th Company who processed TF20 detainees showing signs of severe bruising and fractures. Declassified Army documents released via Freedom of Information Act requests corroborated detainee complaints of mistreatment during TF20 custody, including one case from April 2004 where a detainee reported shortly after capture by the . The integration of CIA operatives within TF20 units facilitated the rapid transfer of "high-value" detainees to undisclosed sites, raising concerns over accountability and adherence to the , as military personnel lacked oversight of subsequent renditions. Investigations into these allegations, prompted by early reports to senior commanders as of November 2003, revealed that TF20's methods prioritized rapid extraction over detainee welfare, with limited prosecutions despite documented incidents; for instance, a Army inquiry into TF20-related abuse at sites like resulted in no charges against members, contrasting with broader accountability efforts elsewhere in . Critics, including organizations, argued this reflected operational overreach by a JSOC-led unit venturing into roles typically reserved for agencies with different legal frameworks, potentially eroding designed for conventional forces. However, defenders within military circles contended that the high-threat environment of HVT hunts necessitated aggressive tactics to prevent detainee or , though from accounts indicates deviations from even those expedited standards.

Debates on Tactics and Civilian Impact

Task Force 20's operations, focused on raids, frequently involved dynamic entries, insertions, and temporary checkpoints to secure perimeters, which sparked debates over their proportionality and adherence to (ROE). In one documented incident on July 27, 2003, in Baghdad's , TF20 personnel fired on approaching vehicles perceived as threats during a post-raid operation, resulting in the deaths of at least three Iraqi civilians whose cars overshot a checkpoint. Local residents expressed outrage, describing the response as excessive and contributing to anti-coalition sentiment, with some reports claiming up to five fatalities from the gunfire. U.S. officials, including Lt. Gen. , later acknowledged civilian deaths in similar checkpoint engagements but attributed them to perceived imminent threats in a volatile urban environment where insurgents often used civilian vehicles for attacks. Human Rights Watch documented at least four additional civilian deaths in a separate TF20 in during 2003, highlighting patterns of rapid escalation to lethal force without clear positive identification of threats, as required under prevailing that mandated engagement only after confirming hostile intent. Critics, including organizations, contended that such tactics—prioritizing speed and over —disproportionately endangered noncombatants, potentially fueling recruitment by alienating the population and eroding legitimacy of efforts. Proponents within military circles argued the aggressive posture was essential for minimizing U.S. casualties during time-sensitive HVT hunts, where intelligence indicated high risks of ambushes or suicide bombings; data from broader JSOC operations showed these raids disrupted command structures despite occasional , with permitting force against vehicles failing to heed warnings in threat-heavy zones. Broader analyses of raids in , including those by TF20's successor units, revealed mixed empirical outcomes on civilian impact: while precise attribution to TF20 remains limited, aggregate studies indicated night and daytime raids correlated with localized spikes in civilian harm, averaging 1-5 deaths per high-profile in urban areas, often from or misidentified threats. Debates centered on causal trade-offs—raids yielding captures like key regime figures versus backlash effects, with some assessments linking perceived overreach to increased attacks and foreign fighter inflows, though direct causation was contested due to confounding dynamics. U.S. Central Command reviews emphasized iterative ROE refinements post- to incorporate non-lethal options, yet acknowledged persistent challenges in distinguishing civilians from hostiles amid poor and cultural barriers.

Dissolution and Legacy

Transition to Successor Units

Following the initial operations during the 2003 invasion, Task Force 20's designation was subsumed into an expanded structure, merging with elements from Task Force 5 (previously operating in ) to form by July 2003. This successor unit integrated JSOC tier-one operators, such as and , with CIA assets to intensify manhunting against regime remnants and emerging . Task Force 121 conducted the December 13, 2003, raid capturing near , leveraging intelligence from prior Task Force 20 site exploitations. As gained prominence under , the task force evolved through redesignations—first to , then to Task Force 145 by early 2004—to prioritize against foreign fighters and networks. These units expanded kinetic operations, averaging dozens of raids monthly, while incorporating advanced and drone overwatch for precision targeting. By 2006, 145 had grown to over 3,500 personnel, reflecting a shift from regime-hunting to sustained disruption, though it faced challenges from adaptive enemy tactics like suicide bombings. Successor iterations persisted until the 2011 U.S. transition to , handing off residual HVT roles to conventional forces and Iraqi counterparts, with JSOC elements redeploying for global priorities.

Long-Term Evaluations

Task Force 20's high-value targeting operations, including the December 13, 2003, in Operation , provided immediate intelligence gains from seized materials and interrogations, informing follow-on efforts against regime remnants. These actions disrupted centralized Ba'athist command elements, yielding documents that revealed internal regime dynamics and financial networks. However, post-capture insurgent activity escalated, as the decentralized nature of the emerging —fueled by grievances over and occupation—proved resilient to leadership decapitation. Longer-term analyses of the HVT paradigm TF20 helped establish indicate tactical efficacy in network degradation but strategic shortcomings without complementary measures. By 2009, successor JSOC task forces had seriously weakened through iterative targeting, reducing operational capacity via captured leaders and exploited sites. Yet, violence metrics from 2004–2006 show persistent escalation into sectarian conflict, underscoring HVT's limits in addressing ideological and vacuums. Critics argue early overemphasis on kinetic HVT, as practiced by TF20, delayed population-centric approaches, contributing to prolonged instability and the eventual rise of from residual insurgent elements. Proponents highlight its organizational innovations, such as interagency targeting teams, which enhanced U.S. adaptability in . Overall, TF20's legacy reflects HVT's utility for short-term disruption but necessity for integration with broader political-military strategies to achieve enduring stability.

References

  1. [1]
    Task Force 20 - United States Special Operations - Iraq
    Task Force 20 was tasked with special reconnaissance, sensitive site exploitations (hunting for WMDs) and seizing key iraqi bases and installations.
  2. [2]
    To Baghdad And Beyond: U.S. Army Special Operations Forces ...
    On 20 March 2003, a US-led coalition launched Operation IRAQI FREEDOM (OIF) to remove Iraqi President Saddam Hussein from power.
  3. [3]
    [PDF] The United States and Assassination Policy: Diluting the Absolute
    Al-Zaidan tipped off the Hussein brothers' location to U.S. forces, and on the morning of July 22, 2003, Task Force 20 arrived, backed up by elements of the ...
  4. [4]
    [PDF] Army History, No. 126, Winter 2023 - Kentucky
    A joint special operations task force and soldiers from the 101st Airborne Division located. Uday and Qusay Hussein on 22 July 2003 at a safe house in Mosul ...<|separator|>
  5. [5]
    JSOC: America's Joint Special Operations Command
    May 16, 2025 · Task Force 20 conducted hundreds of operations in Iraq. Their actions were crucial to the US's successful invasion of the country. After the ...
  6. [6]
    Covert Unit Hunted for Iraqi Arms - The Washington Post
    Jun 12, 2003 · Task Force 20 was also assigned to capture or kill "high-value targets," the U.S. military's euphemism for high-ranking wanted Iraqis. Some ...
  7. [7]
    Pentagon Says A Covert Force Hunts Hussein - The New York Times
    Nov 7, 2003 · ... Operations missions, Task Force 5 in Afghanistan and Task Force 20 in Iraq, officials said. Military officers say a broader, regional mission ...
  8. [8]
    Grange: Saddam 'paranoid' about capture - Jun. 23, 2003 - CNN
    Jun 23, 2003 · GRANGE: Well, what we can talk about on Task Force 20, it's a special operations force made up of several services that all bring different ...
  9. [9]
    JSOC: America's Joint Special Operations Command - Grey Dynamics
    4.1 Task Force 20. In preparation for the invasion of Iraq, JSOC established a new task force similar to the one they had used for the invasion of Afghanistan.Missing: personnel composition
  10. [10]
    Six little-known stories about secretive Joint Special Operations ...
    Task Force 20, comprising Delta operators and Army Rangers flying from the city of Mosul in helicopters — ran ...
  11. [11]
    [PDF] 11-L-0559/0SD/48866 - Executive Services Directorate
    ... Task Force 20, the predecessor to TF 121, said the task forces comprised several 12-man units that had targeted missions, ~uch as searching for Hussein ...
  12. [12]
    [PDF] Operation Northern Delay: The Evolution of Joint Forcible Entry - DTIC
    Jun 15, 2018 · On the western front, joint special operations Task Force 20 operated out of Saudi. Arabia. Major General Dell Dailey commanded TF 20 from an ...
  13. [13]
    B Squadron Deployment, Iraq, October 2003 - January 2004 - Reddit
    Jun 16, 2021 · the rangers were pretty much the muscle of task force 20 back then ... SEAL Team 6 operator alongside a Secret Service agent guarding ...
  14. [14]
    [PDF] All Roads Lead to Baghdad - ARSOF-History.org
    ... Iraq from the planning in late spring 2002 through June 2003. Te ... Task Force 20, another. SOF task force assigned to the west and the south. Te ...
  15. [15]
    https://www.rand.org/pubs/research_reports/RR1214.html
  16. [16]
    JSOC Operations - American Special Ops
    Once the dust had settled, Task Force 20 set up shop in Baghdad in order to fight a burgeoning insurgency. JSOC's mission in Iraq evolved into a highly kinetic ...
  17. [17]
    To Baghdad and Beyond: ARSOF in Operation Iraqi Freedom | Article
    Mar 20, 2023 · The invasion of Iraq began during the predawn hours of March 20, 2003. U.S. Army Special Forces Operational Detachments-Alpha from 5th ...Missing: pre- | Show results with:pre-
  18. [18]
    United States Special Operations - Iraq
    Formed from Delta, DEVGRU and other JSOC units, Task Force 20 was tasked with special reconnaissance, sensitive site exploitations (hunting for WMDs) and ...<|separator|>
  19. [19]
    Objective Beaver: The Search for the Elusive Smoking Gun in Iraq
    The Al Qadisiyah Research Center—also known as Objective Beaver—was the target of a 27 March 2003 raid by special operations forces. The site was a suspected ...
  20. [20]
    Mission Saddam: Inside TF 20 operations | News - Al Jazeera
    Jul 29, 2003 · Task Force 20 is said to be America's most elite military unit and has been working undercover – without much success – in Iraq prior to the March invasion.
  21. [21]
    [PDF] Counterinsurgency in Iraq (2003–2006) - RAND
    Apr 24, 2006 · During the invasion of Iraq, the U.S. deployed Army Special Forces and small con- ventional forces into Kurdish-controlled areas. Special Forces ...
  22. [22]
    Rapid and Radical Adaptation in Counterinsurgency: Task Force ...
    Sep 28, 2021 · The account of Task Force 714's innovations in Iraq from 2003 to 2005 provides valuable lessons for future conflicts. History has shown that ...
  23. [23]
    Killing the Wrong People in Afghanistan - CBS News
    Aug 20, 2010 · A sister organization set up in Iraq was called Task Force 20. The two were eventually combined into Task Force 121 by General John Abizaid ...
  24. [24]
    The Men in the Shadows -- Hunting al-Zarqawi - ABC News
    Jun 9, 2006 · Task Force 145 is a veritable all-star team of Special Forces. The Task Force has now been thrust into the spotlight after leading the way to Abu Musab al- ...Missing: becomes | Show results with:becomes<|separator|>
  25. [25]
    Pentagon: Saddam's sons killed in raid - Jul. 22, 2003 - CNN
    Jul 22, 2003 · The sons of ousted Iraqi leader Saddam Hussein were killed by US troops in the northern city of Mosul after a tipster betrayed their hideout.
  26. [26]
    Middle East | How the villa battle unfolded - BBC NEWS
    Jul 23, 2003 · Uday and Qusay Hussein were killed when more than 200 US soldiers stormed a villa where an informant had told them that the brothers were hiding.
  27. [27]
    Military Commander Details Mission That Killed Hussein's Sons
    Apr 7, 2025 · Officials went to great lengths to confirm that two of the bodies were those of Uday and Qusay. Sanchez said that four separate senior members ...
  28. [28]
    Operation RED DAWN nets Saddam Hussein | Article - Army.mil
    Dec 6, 2013 · Ten years ago this week, the US Army captured Iraqi dictator Saddam Hussein alive. The story of how he was located and captured is an intelligence success ...
  29. [29]
    AFTER THE WAR: BAGHDAD; 3 Iraqis Killed as G.I.'s Set Up Raid in ...
    Jul 28, 2003 · Hussein's sons Uday and Qusay, an increasing stream of tips from informants had moved them closer to capturing Mr. Hussein himself. On Thursday ...
  30. [30]
    [PDF] Operation IRAQI FREEDOM: Decisive War, Elusive Peace - DTIC
    This project set out to prepare an authoritative account of the planning and execution of combat and stability operations in Iraq and to identify key issues ...
  31. [31]
    [PDF] Secret Weapon: High-value Target Teams as an Organizational ...
    The Institute for National Strategic Studies (INSS) is National. Defense University's (NDU's) dedicated research arm. INSS includes.
  32. [32]
    [PDF] On Point II: transition to the new campaign - Army University Press
    May 1, 2003 · ... operation with Special. Forces Task Force 20 in Mosul that killed. Saddam's sons Uday and Qusay in late. July also seemed indicative of broader.
  33. [33]
    The ABCs of HVT: Key Lessons from High Value Targeting ...
    The use of high value targeting (HVT)—using military and police forces to kill or capture leaders of insurgent and terrorist groups—has increased ...
  34. [34]
    Moving Targets | The New Yorker
    Dec 8, 2003 · The Bush Administration has authorized a major escalation of the Special Forces covert war in Iraq. In interviews over the past month, ...
  35. [35]
    Soldiers' Accounts of Detainee Abuse in Iraq - Human Rights Watch
    Task Force 20/121/6-26/145 Camp Nama, Baghdad. Some of the most serious allegations of detainee abuse in Iraq since 2003 have concerned a special military ...<|control11|><|separator|>
  36. [36]
    Camp Nama: British personnel reveal horrors of secret US base in ...
    Apr 1, 2013 · ... Task Force 20, and had run a detention and interrogation facility at a remote location known as H1, in Iraq's western desert. At least one ...Missing: JSOC | Show results with:JSOC
  37. [37]
    U.S.: Soldiers Tell of Detainee Abuse in Iraq | Human Rights Watch
    Jul 22, 2006 · Some of the most serious abuses detailed in the report concern a special task force, which was called at various times Task Force 20, Task ...
  38. [38]
    Army Documents (released by the government12/30/2004 ... - ACLU
    Jan 24, 2005 · Detainee reported abuse on 4/29/04 or earlier. The file indicates that the woman was captured by Task Force 20, which an email describes as ...
  39. [39]
    [PDF] usa 'judge us by our actions' - Amnesty International
    Task Force 20 and then 121 and subsequently Task Force 145). “High-value” detainees were interrogated in a black, windowless room dubbed the Black Room ...
  40. [40]
    U.S. Generals in Iraq Were Told of Abuse Early, Inquiry Finds
    Nov 30, 2004 · A military source who participated in Task Force 20, the predecessor to TF 121, said the task forces comprised several 12-man units that had ...
  41. [41]
    U.S. generals told of detainee abuse early - NBC News
    Nov 30, 2004 · 4, 2003, a month before Herrington arrived for his review. 'Everyone knows about it' A military source who participated in Task Force 20, the ...
  42. [42]
    Iraq Prison Abuse Known Earlier - CBS News
    Dec 8, 2004 · The Post said the joint CIA-military team, known initially as Task Force 20 and later as Task Force 121, was investigated as a result of ...
  43. [43]
    Victims of trigger-happy Task Force 20 | World news | The Guardian
    Jul 28, 2003 · Victims of trigger-happy Task Force 20. This article is more than 22 years old. Rage triggered by US raid that claimed five lives. Jamie Wilson ...
  44. [44]
    Socialist Viewpoint
    At least three Iraqis were killed in west Baghdad's elite Mansour district July 27, when U.S. soldiers from Task Force 20 opened fire on cars that overshot a ...<|control11|><|separator|>
  45. [45]
    Iraqi civilians gunned down in US military raids - WSWS
    Aug 2, 2003 · Residents claim that up to 11 passersby were killed in the assault. Four days later, Lt. Gen. Ricardo Sanchez admitted at a Baghdad press ...
  46. [46]
    III. STATISTICAL ANALYSIS OF CIVILIAN DEATHS
    Oct 1, 2003 · Four civilians were killed in an operation by Task Force 20, a combined CIA-Army special forces team established to capture Iraq's former ...
  47. [47]
    [PDF] Current Issues in Occupation Law: 2003 Civilian Deaths in Baghdad
    Four civilians were killed in an operation by Task Force 20, a combined CIAiArmy special forces team established to capture Iraq s former rulers, but it is not ...
  48. [48]
    Appendix E: Rules of Engagement for U.S. Military Forces in Iraq
    Positive identification is required before engaging. Do not engage surrendered or wounded. Civilians and cultural sites are protected unless in self-defense. ...Missing: JSOC 20
  49. [49]
    Off Target: The Conduct of the War and Civilian Casualties in Iraq
    Dec 11, 2003 · Hundreds of civilian deaths in the U.S.-led invasion of Iraq could have been prevented by abandoning two misguided military tactics.
  50. [50]
    Task Force 121: The capture of Saddam Hussein - Combat Operators
    Apr 3, 2025 · Task Force 121 was already malfunctioning from similar units like Task Force 5, operating in Afghanistan, and Task Force 20, serving in Iraq.Missing: transition | Show results with:transition
  51. [51]
    [PDF] Army Times - ABC News
    May 8, 2006 · Zarqawi still on the loose, the JSOC force in Iraq has grown steadily and undergone several name changes. TF 121 and TF 626 were two previous ...
  52. [52]
    Zarqawi and Task Force 145 - FDD's Long War Journal
    Apr 29, 2006 · The Army Times' Sean Naylor has a fascinating article on Task Force 145, which has replaced Task Force 626 and 121, and the hunt for Abu Musab al-Zarqawi.Missing: successor | Show results with:successor
  53. [53]
    Task Force 145 (TF 145) - GlobalSecurity.org
    Dec 8, 2011 · Task Force 145 is a secretive collection of the US elite troops, operating under Joint Special Operations Command, which was tasked with hunting down Abu Musab ...Missing: 121 successor
  54. [54]
    The Surprising Interrogations That Led to Saddam Hussein's Capture
    Nov 8, 2018 · Operation Red Dawn: a bright spot in a murky war. Few moments in the Iraq War were as widely celebrated as the capture of Saddam Hussein. For ...
  55. [55]
    Captured Documents: What We Now Know about Saddam's Iraq
    Sep 22, 2010 · During a meeting with the president of Yemen, Saddam claimed that Iraq was ready to withstand a nuclear attack, referring to civil defense ...
  56. [56]
    An Evaluation of Counterterrorism Operations in Iraq - jstor
    The research underlying this article indicated a strong consensus that by the end of 2009 AQI had been seriously degraded by task force operations, and this was ...
  57. [57]
    The successes and problems of high-value targeting strategies ...
    Oct 19, 2022 · Senior Fellow Vanda Felbab-Brown breaks down how high-value targeting, when used in practice, is not the sole element of the counterinsurgency success.Missing: JSOC long-
  58. [58]
    Reconsidering the Theory and Practice of High Value Targeting - jstor
    Based on operations conducted in Iraq and Afghanistan from 2007 to 2013, this article argues that the discourse concerning HVT is mired with misunderstandings ...<|control11|><|separator|>