11.11.2014 Views

HQ$History - United States Special Operations Command

HQ$History - United States Special Operations Command

HQ$History - United States Special Operations Command

SHOW MORE
SHOW LESS

You also want an ePaper? Increase the reach of your titles

YUMPU automatically turns print PDFs into web optimized ePapers that Google loves.

During 2003, however, Afghanistan saw a<br />

surge in politically related violence and criminal<br />

activity. Combined Forces <strong>Command</strong> –<br />

Afghanistan (CFC-A), which was created to<br />

oversee both ISAF and CJTF operations, subsequently<br />

requested an increase in U.S. forces to<br />

secure the interior of Afghanistan. Concerned<br />

with the internal security situation, CFC-A had<br />

to bolster the Karzai government and to prepare<br />

the country for projected transition to ISAF (or<br />

NATO) sponsorship in 2005. CFC’s request<br />

prompted an increase in the number of U.S. conventional<br />

forces, raising troop levels in<br />

Afghanistan from a low of 7,500 in January 2003<br />

to a high of 18,000 exactly one year later. The<br />

increase in forces created command, control, and<br />

battlespace synchronization issues largely<br />

absent prior to 2004. SOF, previously able to<br />

conduct missions as they saw fit, now had to<br />

obtain mission approval at numerous levels to<br />

conduct operations. Additionally, SOF would<br />

soon see its most significant change of mission<br />

since initiating the Afghanistan campaign in<br />

2001.<br />

Evolution of Roles and<br />

Missions: February 2004 to<br />

Present<br />

112<br />

The CJSOTF’s mission and battlespace orientation<br />

changed very little in the broad sense<br />

during its first two years in Afghanistan. Minus<br />

its initial training of the Afghan Army, its chief<br />

role remained the capture or destruction of key<br />

personalities within the ACM network in<br />

Afghanistan. Arguably, this mission focus prevented<br />

SOF from maximizing its FID capabilities,<br />

the chief of which was training, advising,<br />

and employing government forces to enhance<br />

security. A number of constraints existed on<br />

both SOF and conventional forces, chiefly a U.S.<br />

troop-to-task ratio insufficient to secure large<br />

swaths of the country and a corresponding lack<br />

of AMF to fill the gap. SF lacked sufficient,<br />

“legitimate” Afghan forces with whom it could<br />

work. During the years from 2004 – 2006, however,<br />

both of these factors began to change.<br />

Subsequently, the role of SOF changed as well.<br />

In March 2004, the U.S. Army’s 25th<br />

Infantry Division (ID) assumed command of<br />

CJTF-180. To capture the historic significance<br />

of parliamentary and national elections scheduled<br />

for that year, it changed the designation of<br />

the CJTF to CJTF-76 and instituted several<br />

major changes.<br />

In April 2004, the CJTF tasked CJSOTF-A to<br />

focus primarily on border security operations in<br />

both Regional <strong>Command</strong>s South and East. The<br />

CJTF intended to halt the flow of ACM and their<br />

supplies from Pakistan. In part, the CJTF wanted<br />

to align missions based on geography. ODAs<br />

occupied the several firebases along the<br />

Pakistani border in RC East: Bari Kowt,<br />

Asadabad, and Chapman. Even in RC South,<br />

the CJSOTF had ODAs positioned in the farthermost<br />

firebases, including Qalat, Gereshk,<br />

and Gecko. Furthermore, CJTF-76 intended for<br />

conventional forces to concentrate on stability<br />

and support operations (SOSO) within the interior<br />

of the CJOA. Provincial Reconstruction<br />

Teams (PRTs), composed primarily of CA personnel,<br />

assumed even greater emphasis under<br />

CJTF-76, and the headquarters wanted secure<br />

conditions to facilitate reconstruction and the<br />

fall elections.<br />

The chief challenge for the CJSOTF was its<br />

lack of access to ANA forces for employment in<br />

combat. In the spring of 2004, the CJSOTF had<br />

only two ANA Kandaks (battalions) under its<br />

OPCON: the <strong>Command</strong>o Kandak (SF trained),<br />

operating in RC East, and 2nd Kandak 201st<br />

Corps. ODAs did employ relatively large numbers<br />

of Afghan Security Forces (ASF) to provide<br />

local security at their firebases; however, these<br />

security elements could not legally conduct operations<br />

beyond 10 to 15 kilometers of the firebase,<br />

and these missions had to be directly related to<br />

the firebase defense. Additionally, the GOA and<br />

CFC-A both wanted to demobilize the ASF. The<br />

GOA viewed the ASF as a militia and wanted to<br />

rid the country of all forces that did not belong to<br />

the army or police. To place a meaningful dent<br />

in the flow of ACM forces and supplies from<br />

Pakistan, the CJSOTF clearly needed access to a<br />

far larger number of Afghan government troops.<br />

Additionally, the directive from the CJTF<br />

ignored the CJSOTF’s need for access to the<br />

interior to maximize its collection of intelligence<br />

concerning the insurgency. The occupation of<br />

firebases in the interior population centers, such<br />

as Jalalabad, Gardez, Zormat, Deh Rawood,<br />

Tarin Khowt, and Deh Chopan, remained essential<br />

for ODAs to gather information on the flow

Hooray! Your file is uploaded and ready to be published.

Saved successfully!

Ooh no, something went wrong!