Recent from talks
Nothing was collected or created yet.
Forward Operating Base Shank
View on Wikipedia
Forward Operating Base Shank (IATA: OAA, ICAO: OASH, also known as Rocket City) was a forward operating base of the U.S. military, located in Logar Province of eastern Afghanistan, about 12 km south-east of the city of Baraki Barak. During Operation Enduring freedom, FOB Shank was one of the most heavily rocketed forward operating bases in Afghanistan.[1] In 2014, the base was turned over to Afghan National Army, who established Camp Maiwand at the northern end of the FOB. American forces later returned and reoccupied the southern portion of the FOB, under the name Camp Dahlke.
Key Information
History
[edit]In 2008 FOB Shank was built by Alpha Company of the 508th Special Troops Battalion of the 82nd Airborne Division with assistance from the 555th Engineer Battalion. The FOB was dedicated after SSG Michael A. Shank, who was killed in the Logar Province in 2006. International Security Assistance Force (ISAF) used the base to train the Afghan National Police (ANP). The Police Academy, led by a U.S. Police Mentoring Training team, cooperated daily with the Czech Provincial Reconstruction Team Logar, composed of 200 Czech Soldiers and about 10 civilians.
These efforts were focused on training the Afghanistan National Auxiliary Police to become members of the ANP.
As of 8 July 2008, Czech and Afghan instructors were teaching the fourth group of cadets at the academy. Each group attended a three-week cycle which included first-aid treatment, tactics, patrolling, weapons training, vehicle-check-point procedures and many other police-related subjects. The practical part of the training also included scenarios where cadets were ambushed by simulated oppositional forces.[citation needed]
During 2014 the base was downsized partly by 663 Engineer Company (cbt hvy)and was turned over to the ANA.[2] The ANA utilized the northern portion of the base only, which they renamed Camp Maiwand.[3]
The last few convoys containing equipment from FOB Shank back to Bagram Airbase were completed during October 2014 by the 730th Transportation Company, 419th Combat Sustainment Support Battalion, 4th Resolute Support Sustainment Brigade.[4]
Following the shutdown of FOB Shank, a new American base was established at the southern end of the perimeter, called FOB Dahlke or Camp Dahlke. Camp Dahlke was expanded in 2018 to support the deployment of the 1st Security Force Assistance Brigade. Camp Dahlke had facilities to house 1200 personnel.[5]
Deployed units
[edit]This section needs additional citations for verification. (April 2020) |
Aviation
- October 2008-October 2009
- 101st Airborne 159th Aviation Brigade "Task Force Thunder" under Col. Ronald Lewis / 4-101 "Task Force Wings" under Lt. Col James Benson.
- October 2009–October 2010
- 3rd Infantry Division 4-3 AVN Battalion "BRAWLER" under Lt. Col Ault
- December 2008-December 2009
- 710BSB 3RD IBCT 10th MTN
2010–2010 10th Mountain
- April 2011
- 10th Combat Aviation Brigade
- Company F, 2nd Battalion (Aviation Support)
- 10th Combat Aviation Brigade
- August 2011–August 2012
- 82nd Combat Aviation Brigade (TF Corsair)
- Unknown Company, 3rd Battalion
- All Companies, 2nd Battalion, 82nd Aviation Regiment (UH-60M)
- Company B, 3rd Battalion, 82nd Aviation Regiment (CH-47F)
- Company B, 2nd Battalion, 135th Aviation Regiment (CH-47)
- Company F, 1st Attack Battalion, 1st Air Combat Brigade, 227th Aviation Regiment, 1st Cavalry Division (Gray Eagle) (3/2012 – 03/2013) – first unit to operate Gray Eagle at Shank. This company was deployed as a standalone company and attached to the 82nd Airborne Division upon arrival to Shank. After TF Corsair left, F 227 was attached to the incoming unit until its tour of duty was completed.
- Elements of 122nd Aviation Support Battalion
- 82nd Combat Aviation Brigade (TF Corsair)
- August 2012-January 2013
- 173rd ABCT (TF Bayonet)
- June – December 2013
- 10th Combat Aviation Brigade (TF Knighthawk)
- Headquarters and Headquarters Company, 2nd Assault Battalion, 10th Aviation Regiment
- Company C, 2nd Assault Battalion, 10th Aviation Regiment (UH-60M)
- Company E, 2nd Assault Battalion, 10th Aviation Regiment (Aviation Support)
- Company A, 2nd Assault Battalion, 10th Aviation Regiment (AH-64)
- Company B, 3rd General Support Aviation Battalion, 10th Aviation Regiment (CH-47F)
- Company C, 3rd General Support Aviation Battalion, 10th Aviation Regiment (HH-60M)
- 10th Combat Aviation Brigade (TF Knighthawk)
- December 2013–August 2014
Taskforce Wings 4-101 Aviation Regiment
- Taskforce Lift
- Company C (DUSTOFF), 7-101 General Support Aviation Battalion, 159th Combat Aviation Brigade, 101 Airborne Division
- 6-101 Aviation Battalion, 159th Combat Aviation Brigade, 101 Airborne Division
- Taskforce Lift
- 2014
- 82nd Combat Aviation Brigade (TF Pegasus)[6]
- Company E, 1st Attack Reconnaissance Battalion, 82nd Aviation Regiment (UH-60)
- Company F, 2nd Attack Helicopter Battalion, 82nd Aviation Regiment
- Company B, 3rd General Support Helicopter Battalion, 82nd Aviation Regiment using the Boeing CH-47F Chinook
- Company B, 122nd Aviation Support Battalion
- 82nd Combat Aviation Brigade (TF Pegasus)[6]
- October 2014
- Company B, 1st General Support Aviation Battalion, 169th Aviation Regiment (CH-47)
- May 2016 – Unknown
- 40th Combat Aviation Brigade[7]
- Company C, 1st Battalion, 104th Aviation Regiment (DUSTOFF)
- Company F, 2nd Battalion, 238th Aviation Regiment (UH-60)
- Company B, 1st Battalion, 140th Aviation Regiment
- 1st Battalion, 10th Aviation Regiment (AH-64)
- 40th Combat Aviation Brigade[7]
- 2018
- 101st Combat Aviation Brigade (TF Eagle Assault)
- 5th Battalion, 101st Aviation Regiment (CH-47, UH-60, AH-64E)
- Company B, 3rd General Support Battalion, 25th Aviation Regiment (CH47F)
- 101st Combat Aviation Brigade (TF Eagle Assault)
- 2019
- 1st Armored Division, Combat Aviation Brigade (TF Apocalypse)
- 3rd Battalion (UH-60)
- 16th Combat Aviation Brigade, B Company (CH-47) "Sugarbears"
- 1st Combat Aviation Brigade, 1-1 Attack Battalion, Bravo Company (AH-64E) "Wolf Pack" "LUOFY"
- 2-10 Combat Aviation Brigade, 10th Mountain Division
- 1st Armored Division, Combat Aviation Brigade (TF Apocalypse)
Ground forces
- A, B and C Companies, 710th Brigade Support Battalion, 3rd Brigade Combat Team, 10th Mountain Division between December 2008 and 2009[8] and December 2009.
- Alpha Battery, 4th Battalion, 319th Airborne Field Artillery Regiment, 173rd Airborne Brigade Combat Team during July 2012.
- Elements of 919th ICTC, 103rd Sustainment Command from 2010-2011
- 2nd Battalion - 30th Infantry Regiment, 4th Brigade Combat Team, 10th Mountain Division from October of 2010 to October of 2011.
- A Co, 1st Battalion – 41st Infantry Regiment, 3rd Infantry Brigade Combat Team, 1st Armored Division during 2011–2012.
- 3rd Infantry Brigade Combat Team, 1st Armored Division from Fort Bliss, Tx, from 2011 to 2012.
- 628th Forward Surgical Team, from San Antonio, Tx, 2011–2012
- Elements of 427th BSB (NY ARNG) attached to 401st AFSB during 2011–2012
- 1st Squadron (Airborne) 91st Cavalry, 173rd Airborne Brigade Combat Team, June 2012–March 2013.
- 102nd Sapper Company, 307th Engineer Battalion, June 2012- March 2013
- Naval Mobile Construction Battalion 14 Detachment 2, August 2012-February 2013
- 6th Squadron, 8th Cavalry Regiment, 4th Infantry Brigade Combat Team, 3rd Infantry Division, March 2013–November 2013.
- Bravo Company "Mongoose Bravo" 1st Battalion, 5th Cavalry Regiment, 2nd Brigade Combat Team, August 2013–March 2014
- 710th Brigade Support Battalion and 2nd Battalion, 87th Infantry Regiment, 3rd Brigade Combat Team, 10th Mountain Division between October 2013 and July 2014[9]
- 388th Clearance Company, January 2014–October 2014.
- B CO, 1st Battalion – 502nd Infantry Regiment, 2nd Brigade Combat Team, 101st Airborne (Air Assault) Division during January 2014–October 2014.
- 2nd Squadron 3rd Cavalry Regiment between June 2014 to October 2014.
- 1982nd Forward Surgical Team during 2015.
- Alpha Battery 1st Battalion 265th ADA Regiment; 164th ADA Brigade Florida Army National Guard, June 2015–February 2016 ADA[10]
- 389th Engineer Company, 2016-2017
- 207th Engineer Construction Company, Over The Horizon, 2017
- 136th Combat Sustainment Support Battalion during October 2017.
- 2-174 ADA C-RAM (Ohio National Guard) 2017–2018
- 659th Engineer Construction Company, Over The Horizon, 2017–2018
- 2nd Squadron 1st Cavalry Regiment, Fort Carson 2018–2019
- Elements of 495th Combat Sustainment Support Battalion 2018–2019.
- 3rd Platoon, Alpha Company, 1-38 Infantry Battalion, 1st SBCT, 4th ID. 2018–2019
- Elements of the 329th Combat Sustainment Support Battalion, TF Viking 2019–2020
- 801st Engineering Company, Over The Horizon, 2019
- 829 Engineering Company, TF Over The Horizon, 2020
- Bravo and Delta Co and Headquarters Elements of the 1st Battalion 178 Infantry Regiment (Illinois National Guard) TF Southeast, September 2019–January 2020.
- Elements of Bravo Company and HHC 1st Battalion 508th Parachute Infantry Regiment, 3BCT, 82ND ABN DIV (TF FURY), October 2019–January 2020
- 10th Mountain 1-32 Infantry
See also
[edit]References
[edit]- ^ ""Rocket City," Afghanistan: Army thinks outside the box to protect troops at front-line base". CBS News.
- ^ "Afghanistan: April 2014". The Atlantic. 10 May 2016.
- ^ "Welcome to 'Zombieland': A former US Army base rots in the hands of overwhelmed Afghans". Stars and Stripes. Retrieved 14 December 2019.
- ^ "Ruffians close down FOB Shank". DVIDS. 9 August 2016.
- ^ "An austere base in Afghanistan rapidly expands for more US troops". Stars and Stripes. Retrieved 14 December 2019.
- ^ Brooks, Drew. "With the Troops: Afghanistan remains dangerous as drawdown leaves fewer soldiers at war". The Fayetteville Observer.
- ^ "40th CAB joins the fight at FOB Dahlke".
- ^ "710 BSB bolster security around FOB Shank". United States Army. Retrieved 9 August 2016.
- ^ "10th Mountain Division soldiers prepare to go out on patrol from FOB Shank". World Armies. Retrieved 2 April 2014.
- ^ "Dr. Swanson retires from Army Reserve". 5 May 2016.
External links
[edit]
Media related to Forward Operating Base Shank at Wikimedia Commons
- "Rocket City," Afghanistan: Army thinks outside the box to protect troops at front-line base
- Just Another Day in Rocket City
- US soldiers increase base defense measures on FOB Shank
- Truck bomb injures U.S. soldiers at Afghan base
- In Opinion: Addicted to war—learning to deal with the highs and lows
- "Camp Shank/Forward Operating Base Shank". GlobalSecurity.org. Retrieved 21 March 2007.
Forward Operating Base Shank
View on GrokipediaGeography and Location
Terrain and Strategic Positioning
Forward Operating Base Shank occupies a site in Logar Province, eastern Afghanistan, within the relatively flat river valley terrain of the province's northern and central regions, adjacent to the Logar River.[1] The base sits at an elevation of approximately 2,050 meters (6,700 feet) above sea level, with coordinates around 33°55′N 69°05′E.[6] [7] This lowland positioning provided logistical advantages through proximity to provincial routes but left the installation exposed to the encircling rugged highlands and mountainous features characteristic of Logar Province.[1] The surrounding terrain, including elevated ridges and open approaches, enabled insurgent forces to establish observation posts and launch indirect fire from high ground, complicating defensive efforts against rocket and mortar threats.[3] This vulnerability to frequent attacks from afar contributed to the base's informal designation as "Rocket City" by U.S. personnel, reflecting the persistent hazard posed by the landscape's tactical disadvantages.[8] Strategically, Shank's location in a Taliban-influenced area facilitated coalition support for stability operations across Logar and adjacent provinces, functioning as a key node for troop movements, supplies, and rapid response within Regional Command East.[9] [10] Its valley setting supported airfield operations and ground access to critical highways linking Kabul southward, enhancing its role despite the inherent risks from proximate highlands.[9]Establishment and Early Development
Founding and Naming
Forward Operating Base (FOB) Shank was established in 2008 in Baraki Barak District, Logar Province, eastern Afghanistan, during Operation Enduring Freedom, as part of U.S. and coalition efforts to counter a Taliban resurgence that had intensified following increased insurgent activity after 2006.[11][10] The base was constructed by Alpha Company, 508th Special Troops Battalion, 82nd Airborne Division, with support from the 555th Engineer Company, to provide a forward hub amid rising threats in a province strategically positioned near key supply routes and close to Kabul.[12] Its initial role focused on enabling patrols and operations to secure Logar Province, where Taliban forces exploited rugged terrain and local sympathies to launch attacks and disrupt governance.[10] The base was named in honor of U.S. Army Staff Sergeant Michael A. Shank, a 31-year-old soldier from Bonham, Texas, who died on November 28, 2006, from injuries sustained when his vehicle struck an improvised explosive device during combat operations in Logar Province.[13][14] This naming followed U.S. military tradition of commemorating fallen service members by dedicating installations in areas of their sacrifice, underscoring the base's origins tied to the human cost of early counterinsurgency operations in the region.[14] By July 2008, FOB Shank housed International Security Assistance Force (ISAF) personnel primarily tasked with training the Afghan National Police to build local security capacity against insurgent incursions.[10]Initial Construction
The initial construction of Forward Operating Base Shank commenced in 2008 in Logar Province, eastern Afghanistan, under the leadership of Alpha Company, 508th Special Troops Battalion, 82nd Airborne Division, with engineering support from the 555th Engineer Company.[12] This effort prioritized rapid establishment of a defensible outpost capable of supporting initial troop deployments amid the region's rugged terrain, which includes elevations around 1,800 meters and proximity to the Logar River, necessitating adaptations for soil stability and flood risk mitigation.[1] Engineers focused on core defensive elements, including perimeter fencing, guard towers, and HESCO barrier walls to create secure boundaries against environmental and access challenges.[15] To enable quick scalability for logistics and personnel influx, construction incorporated prefabricated modular units for barracks, command posts, and storage facilities, a standard approach in austere Afghan environments to minimize on-site labor and material dependencies.[15] Basic infrastructure integrated early sustainment systems, such as fuel storage tanks and provisional water purification via tactical units, to reduce reliance on extended supply convoys from bases like Bagram, where dust storms and elevation-related logistics strains complicated heavy equipment transport.[16] These adaptations addressed local conditions, including fine silty soils prone to erosion and wind-blown particulates, by employing gravel stabilization and covered assembly methods for durable foundations.[1] By late 2008, the base achieved operational readiness for small-unit sustainment, though major expansions like the airfield runway remained pending until 2009-2010 to handle increased airlift demands.[17] [9] This phase underscored engineering imperatives for self-reliance in a remote, elevation-challenged area, with initial layouts emphasizing modular expandability over permanent fixtures to align with fluid mission requirements.[18]Operational History
Peak Usage (2008-2014)
Following the U.S. announcement of a troop surge in December 2009, which added approximately 30,000 personnel to counter Taliban resurgence, Forward Operating Base Shank underwent rapid expansion to accommodate heightened coalition activity in Logar Province.[3] The base, positioned along critical supply routes such as Highway 7 linking Pakistan to Kabul, functioned as a primary staging area for disrupting insurgent logistics and incursions from eastern safe havens. Infrastructure upgrades, including a $12 million runway completed in June 2010, enabled intensified air operations and logistical sustainment amid the surge's focus on clearing and holding contested districts.[19] The period from 2010 to 2012 marked the apex of operational intensity at FOB Shank, with peak personnel exceeding 18,000 troops, contractors, and support staff. Coalition forces conducted frequent dismounted patrols and partnered training with Afghan National Army units to build local capacity, while helicopter and fixed-wing sorties targeted Taliban positions in Logar's rugged terrain. This era coincided with escalating insurgent violence, as the base—nicknamed "Rocket City"—faced near-daily indirect fire attacks from Taliban rocket positions in surrounding villages, establishing it as one of Afghanistan's most besieged forward operating bases since active combat operations commenced there in 2008.[20] By 2013–2014, alignment with U.S. policy emphasizing transition to Afghan security responsibility prompted a phased coalition drawdown at Shank, reducing troop levels and shifting emphasis from offensive operations to advisory roles. Enhanced base defenses, including counter-rocket systems deployed in 2013, mitigated ongoing threats during this contraction, which mirrored the broader end of major U.S. combat missions by late 2014. The base's handover to Afghan forces reflected strategic recalibration toward sustainable partner-led stability, though persistent attacks underscored unresolved insurgent capabilities in Logar.[3][21]Key Military Activities
From Forward Operating Base Shank, coalition aviation units conducted reconnaissance and security missions using AH-64 Apache helicopters, targeting insurgent threats along key routes in Logar Province. On August 14, 2012, an Apache Longbow completed a night mission before landing at the base's flightline, supporting ground forces by providing close air support and disrupting enemy movements.[22] In March 2011, Task Force Knighthawk established a forward arming and refueling point at Shank, allowing the first Apache to refuel on-site and extend operational range for such missions against Taliban positions and improvised explosive device networks.[23] The base facilitated training programs for the Afghan National Army, focusing on counterinsurgency skills to enable independent operations. Afghan soldiers practiced five- and 25-meter checks for improvised explosive device detection during a dedicated course on May 20, 2013, enhancing their ability to secure routes previously vulnerable to Taliban ambushes.[24] Howitzer live-fire exercises were also conducted on July 26, 2012, improving ANA artillery proficiency for offensive support in regional engagements.[25] Shank's aviation assets underpinned logistical resupply to outlying posts, with units like the 3rd Combat Aviation Brigade adapting rotary-wing operations to deliver sustainment amid contested terrain from 2010 onward. These efforts sustained coalition maneuvers by ensuring ammunition and supplies reached forward positions, contributing to sustained pressure on insurgent supply lines.[26]Facilities and Infrastructure
Core Installations
The core installations at Forward Operating Base Shank included barracks constructed from containerized housing units designed to accommodate approximately 4,500 military personnel, featuring blast-resistant structures to withstand indirect fire threats prevalent in the region.[19] Dining facilities, known as DFACs, provided continuous meals for troops despite frequent disruptions from rocket attacks, with food service specialists responsible for maintenance and operations to ensure operational readiness.[27] Medical infrastructure centered on the 8th Forward Surgical Team (FST), the U.S. Army's busiest trauma center at the base, equipped to handle casualties from U.S. troops and Afghan National forces through rapid surgical interventions.[28] Command centers, including the Tactical Operations Center (TOC), supported operational coordination with elevated radio antennas for communication and oversight of brigade activities. Aviation facilities encompassed maintenance hangars for aircraft and a tarmac used for assembling and launching Grey Eagle unmanned aerial vehicles (UAVs), enabling intelligence, surveillance, and reconnaissance (ISR) missions.[29] Helicopter landing pads facilitated close air support and logistics for combat aviation brigades operating in the area. Perimeter defenses integrated the Counter Rocket, Artillery, and Mortar (C-RAM) system, utilizing radar and cameras for early threat detection, paired with the land-based Phalanx Weapons System (LPWS) that fired 20mm self-detonating rounds to intercept incoming projectiles and provide trajectory data for counterfire responses.[3]Expansion and Sustainment
Expansion of Forward Operating Base Shank transformed it from an initial austere outpost into a major logistical hub capable of housing nearly 5,200 personnel at its peak during U.S. operations.[30] Infrastructure enhancements included contracts for roads, utilities, and a dedicated water distribution system to support increased sustainment demands.[18] In November 2011, the U.S. Army Corps of Engineers awarded a $5.4 million contract to construct an aerated lagoon wastewater treatment plant with a daily capacity of 1,900,000 liters, incorporating pump stations, electrical generation upgrades, sanitary sewers, and drainage systems to manage waste from expanded facilities.[31] Sustainment operations depended on contracted Afghan labor for construction and maintenance, which introduced vulnerabilities such as potential supply chain interruptions and insider threats, as evidenced by rising attacks by Afghan security forces and affiliates on coalition personnel across bases in the region.[32] These efforts prioritized modular utilities and power improvements to ensure operational continuity amid high occupancy. Environmental adaptations addressed prevalent hazards like airborne dust, with Department of Defense monitoring documenting elevated PM10 levels averaging 204 μg/m³ from 2007 to 2012, linked to acute respiratory irritation.[1] Mitigation measures included restricting strenuous outdoor activities and sealing living quarters during dust events, alongside routine health surveillance to track exposures without formal post-deployment follow-up requirements.[1]Deployed Units
US and Coalition Deployments
The primary U.S. deployments to Forward Operating Base Shank consisted of rotational brigade combat teams and supporting elements from the U.S. Army, particularly during the 2009–2012 surge period when troop levels in Regional Command East expanded to enable force projection across Logar and adjacent provinces. The 3rd Brigade Combat Team, 10th Mountain Division, maintained a significant presence at the base, conducting advisory and kinetic operations in coordination with Afghan partners. Artillery units, such as elements of the Patriot Battalion, deployed to Shank in March 2013 to provide fire support, including relocating M119 howitzers via helicopter to nearby outposts. Engineering detachments like the 102nd Sapper Company operated from the base to clear routes and counter improvised explosive devices in the vicinity. Aviation rotations were central to Shank's role as a hub for air operations, with combat aviation brigades providing helicopter assault, attack, and reconnaissance capabilities. The 82nd Combat Aviation Brigade rotated through Shank from August 2011 to August 2012 as Task Force Viper, supporting ground maneuvers with UH-60 Black Hawks and AH-64 Apaches. Subsequent rotations included elements of the 10th Combat Aviation Brigade in April 2011, focusing on aviation support battalions for logistics and maintenance. By late 2014, the 82nd CAB again contributed to retrograde operations prior to the base's handover, conducting flight missions amid ongoing threats. Special operations elements, including aviation and ground task forces, integrated into these rotations for targeted strikes and advisory missions, enhancing rapid response in eastern Afghanistan. Coalition contributions under ISAF emphasized niche support roles, with NATO allies augmenting U.S. logistics, engineering, and training efforts at Shank. Turkish engineers partnered with U.S. forces to expand the airfield in a multi-year project completed on March 10, 2010, increasing capacity for fixed-wing and rotary aircraft refueling and arming. Other allied personnel from ISAF nations provided base defense and sustainment, sharing the facility with U.S. troops amid persistent indirect fire risks, though specific non-Turkish unit rotations at Shank were limited compared to U.S. dominance. These deployments peaked during the surge, aligning with broader ISAF expansions to over 130,000 personnel by 2011, bolstering coalition force projection before drawdowns began in 2012.Afghan and Partner Forces
Afghan National Security Forces (ANSF), including the Afghan National Army (ANA) and Afghan National Police (ANP), maintained a growing presence at Forward Operating Base Shank to support joint operations and build capacity for independent control of Logar Province security. As part of transition efforts, ANSF units partnered with coalition mentors for patrols and base defense, with advisory teams embedding to advise on tactics, logistics, and counterinsurgency operations against Taliban forces. A police mentoring and training team operated on-site, cooperating with the Czech Provincial Reconstruction Team to deliver daily instruction to ANP personnel.[10][33] Training facilities at Shank facilitated ANSF development, hosting basic recruit courses for ANP as early as April 2008 under International Security Assistance Force (ISAF) oversight, focusing on foundational skills like weapons handling and patrol procedures. Partner nation contributions included multinational advisory elements within ISAF, which embedded with ANSF to enhance operational coordination and prepare for base handover, emphasizing sovereignty through localized command structures. By 2013, Security Force Advise and Assist Teams, such as those from U.S. units at Fort Hood, integrated directly with ANSF counterparts to refine joint fire support and sustainment protocols.[33][34][35] Interoperability challenges persisted due to equipment discrepancies, with ANSF relying on mismatched NATO-standard gear that complicated joint maneuvers and maintenance. Sustainment issues were exacerbated by systemic corruption within ANSF ranks, including fuel diversion and procurement fraud, which eroded logistical reliability and unit cohesion despite advisory interventions. These factors delayed full operational independence, as evidenced by ongoing reliance on partner logistics during the 2014 base transfer to ANA control, where the northern perimeter became Camp Maiwand.[36][37][38]Security Challenges
Indirect Fire Threats
Forward Operating Base Shank earned the nickname "Rocket City" among U.S. and coalition troops due to the high volume of indirect fire attacks, primarily rockets and mortars, launched by Taliban insurgents starting in 2008.[39][20] These attacks occurred with such regularity—often daily during peak periods—that they defined operational routines, with surrounding elevated terrain in Logar Province providing insurgents elevated vantage points for unhindered observation and targeting of the base's expansive layout.[40] Insurgents exploited the base's visibility and predictable defensive responses to constrain coalition forces, channeling significant manpower and resources into perimeter security and counter-battery operations rather than enabling proactive offensive actions.[20] This approach aligned with broader Taliban tactics of attrition through harassment, leveraging the base's role as a logistics hub to impose sustained psychological and material strain without requiring direct assaults.[39] Coalition countermeasures included dismounted patrols by cavalry scouts to locate and disrupt launch sites in adjacent ravines and rocky areas, counter-battery radar for rapid target acquisition, and artillery responses from units like the 2nd Battalion, 17th Field Artillery.[35][41] Additionally, adaptations such as the Navy-derived Phalanx CIWS (Counter-Rocket, Artillery, and Mortar system) were deployed to intercept incoming projectiles via bursts of 20mm rounds, while experimental systems like aerostat balloons and the Israeli "Storm" anti-artillery were tested for enhanced detection and neutralization.[3] These efforts achieved partial interception rates but yielded mixed results overall, as insurgents adjusted firing positions and volumes, maintaining pressure through persistent, low-cost volleys into 2014.[39][35]Notable Attacks and Responses
On April 23, 2013, a Taliban rocket attack struck Forward Operating Base Shank, killing two U.S. Army helicopter pilots, Chief Warrant Officer 2 Thomas J. Blanchard and Chief Warrant Officer 2 Brent L. Hess, who were part of Task Force Palehorse.[42] The incident underscored the persistent indirect fire threat, with insurgents employing unguided rockets to target personnel and infrastructure despite coalition countermeasures.[39] In a separate incident on July 18, 2013, Taliban militants kidnapped and executed eight Afghan civilian laborers en route to the base in Logar Province, shooting each in the head after stopping their vehicle; the attack was part of a broader insurgent intimidation campaign against locals supporting coalition operations.[43] This event highlighted vulnerabilities in supply chain logistics, as the victims were day workers essential for base sustainment, demonstrating insurgents' tactical shift to asymmetric targeting of Afghan collaborators to disrupt coalition sustainment without direct confrontation.[44] Indirect fire attack rates on FOB Shank escalated during the U.S. troop surge years of 2009–2012, with the base earning the nickname "Rocket City" due to near-daily barrages from nearby hills, reflecting Taliban adaptation to fixed coalition positions by prioritizing volume over precision to inflict attrition.[20] In response, coalition forces deployed Counter-Rocket, Artillery, and Mortar (C-RAM) systems in 2013 to intercept incoming projectiles, enhancing base defense layers alongside aviation assets for rapid post-impact hunts of launch sites.[3] These measures, including expanded sensor networks and quick-reaction air patrols, reduced some impacts but could not eliminate the threat, as insurgents exploited terrain advantages for repeated firings.[21]Strategic Role and Impact
Contributions to Counterinsurgency
Forward Operating Base Shank served as a primary launch point for coalition clearance operations in Logar Province, disrupting Taliban freedom of movement through targeted raids and captures. On September 22, 2010, Afghan and coalition forces operating from bases including Shank detained a Taliban commander responsible for orchestrating indirect fire attacks, improvised explosive device placements, and small arms assaults against Afghan and international targets in the region.[45] Such operations, supported by Shank's aviation and logistics assets, contributed to the neutralization of insurgent networks and the seizure of weapons caches, though specific tallies of captured arms from Shank-launched missions remain operationally aggregated in regional reports.[46] The base hosted dedicated training programs that bolstered Afghan National Security Forces (ANSF) capabilities, enabling them to conduct independent patrols and secure key districts temporarily. In April 2008, International Security Assistance Force (ISAF) personnel initiated basic training for Afghan National Police recruits at Shank, focusing on foundational skills for countering insurgent threats in Logar.[33] By May 2013, Afghan National Army soldiers underwent counter-IED instruction on-site, practicing detection and response techniques such as five- and 25-meter checks to mitigate roadside threats.[24] Additionally, the establishment of a Counterinsurgency (COIN) Academy at Shank in April 2010 trained coalition aviators and ground forces on tactics tailored to population-centric operations, enhancing ANSF mentorship and joint mission effectiveness in the province.[46] As a logistical hub for eastern Afghanistan, Shank sustained broader counterinsurgency efforts by facilitating supply lines and rapid response to frontline needs, preventing insurgent breakthroughs along critical routes. Housing up to 18,000 troops during peak surge periods from 2006 to 2014, the base supported aviation brigades and sustainment units that delivered munitions, fuel, and reinforcements to operations in Logar and adjacent provinces, maintaining pressure on Taliban supply networks.[47] This infrastructure role underpinned temporary stabilization, as evidenced by reduced insurgent operational tempo in cleared areas during ISAF surges.[10]Effectiveness and Outcomes
FOB Shank facilitated short-term successes in force projection and partner enablement through its aviation and intelligence, surveillance, and reconnaissance (ISR) capabilities, supporting operations that disrupted Taliban networks in Logar Province. Task Force Brawler of the 3rd Combat Aviation Brigade demonstrated adaptability by conducting both aerial and ground missions, contributing to local counterinsurgency efforts including captures of key insurgents responsible for indirect fire and IED attacks.[26][45] The base hosted a COIN Academy to train coalition forces in population-centric tactics, enhancing coordination with Afghan partners and enabling patrols that built local trust via counterinsurgency techniques.[46][48] However, these gains yielded limited long-term suppression of Taliban activity, as external sanctuaries allowed insurgent resurgence and adaptation, evidenced by persistent indirect fire attacks on the base dubbed "Rocket City" since 2008.[20] Despite ISR-driven intelligence enabling targeted operations, attack data reflected enemy resilience, with FOB Shank enduring heavy rocketing that strained defenses and indicated incomplete control over surrounding areas.[39] In the broader drawdown strategy, FOB Shank played a role in transitioning combat responsibilities to Afghan forces, culminating in its handover to the Afghan National Army on October 23, 2014, as part of reduced U.S. presence from over 4,000 troops to minimal advisory elements.[30][49] This shift aimed to bolster ANA readiness through training and sustainment support, yet outcomes were mixed, with Afghan units facing challenges in maintaining operational tempo amid ongoing insurgent pressure.[50]Transition and Legacy
Handover to Afghan Control
The handover of Forward Operating Base Shank to Afghan National Security Forces occurred on October 23, 2014, during a transfer of authority ceremony conducted by the U.S. 3rd Cavalry Regiment to the Afghan National Army (ANA).[51] This event aligned with NATO's Inteqal transition framework, which progressively shifted security responsibilities from International Security Assistance Force (ISAF) troops to Afghan forces, culminating in the completion of ISAF's combat mission by the end of 2014.[52] Infrastructure, including barracks, runways, and support facilities developed during the U.S.-led expansion, was transferred intact for ANA use amid the broader American military drawdown from Afghanistan.[50] Following the handover, the ANA established Camp Maiwand at the northern end of the former FOB Shank site in Logar Province, repurposing it as a forward operating base for regional operations.[36] U.S. advisory elements maintained a presence on the base immediately afterward, embedding with Afghan partners to provide logistical and operational support during the initial phase of independent ANA control.[36] This advisory role facilitated monitoring of early Afghan-led activities, though reports from the period highlighted broader challenges in ANSF sustainment capabilities, such as equipment maintenance and supply chain management, which advisors worked to address through on-site training and oversight.[53]Post-Withdrawal Status and Deterioration
Following the 2014 handover of Forward Operating Base Shank to Afghan National Security Forces (ANSF), the facility underwent rapid physical decline attributable to chronic maintenance shortfalls, fuel scarcity, and insufficient personnel capable of operating complex infrastructure. By March 2019, the base—once supporting up to 18,000 troops—had deteriorated into what observers termed "Zombieland," featuring collapsed tents requiring nightly 80 gallons of fuel for climate control under prior U.S. operations, now rotting amid uncollected waste and crumbling concrete structures unable to withstand Logar Province's harsh conditions.[5] ANSF commanders cited overwhelming logistical burdens and high attrition rates as primary causes, with basic utilities like electricity and water systems failing due to absent technical expertise previously provided by coalition partners.[5] A residual U.S. contingent of approximately 300 personnel vacated the base in early 2021 ahead of the broader coalition drawdown mandated by the U.S.-Taliban agreement.[54] This left the site fully under ANSF administration amid escalating Taliban advances in Logar Province, where insurgent control over surrounding districts had already intensified by 2019.[55] The Afghan government's collapse accelerated the base's fate; on August 13, 2021, Taliban fighters seized Pul-e-Alam, Logar Province's capital roughly 12 kilometers northwest of Shank, completing their hold on the region and placing the facility under insurgent authority without recorded resistance.[56] In the ensuing months, FOB Shank joined a pattern of former ANSF installations that were stripped of equipment, vehicles, and salvageable materials by locals and fighters, transforming the expansive compound into an abandoned husk amid broader post-withdrawal scavenging reported across Afghanistan.[57] As of 2025, the site persists as a derelict symbol of the failed transition to Afghan self-reliance, inaccessible to international verification under Taliban governance and showing no evidence of sustained redevelopment or foreign military utility.[54]Controversies and Criticisms
Vulnerabilities and Tactical Debates
Critics of the Forward Operating Base (FOB) strategy in Afghanistan contended that large installations like FOB Shank functioned as static targets, attracting indirect fire (IDF) attacks and necessitating the allocation of substantial personnel to perimeter defense rather than offensive maneuvers or population-centric counterinsurgency (COIN) efforts.[20] This defensive posture, they argued, diverted troops from patrolling villages and engaging insurgents, fostering what some termed an "illusion of war" where base security overshadowed broader operational tempo. Military analyst Bing West, in his critique of U.S. strategy, emphasized that consolidating forces on expansive bases reduced agility and encouraged a reactive mindset, advocating instead for smaller, dispersed units to better integrate with Afghan forces and disrupt enemy safe havens.[58] Proponents of FOB-centric basing countered that such hubs were indispensable for power projection in contested regions like Logar Province, where Shank's aviation assets, logistics infrastructure, and command facilities enabled support for remote combat outposts (COPs) and rapid response operations.[3] They attributed Shank's persistent vulnerabilities not to the large-base concept itself but to extrinsic factors, including the surrounding mountainous terrain that facilitated rocket launches from concealed positions and restrictive rules of engagement (ROE) that hampered preemptive strikes on firing points.[21] These defenders maintained that without centralized FOBs, sustaining sustained presence in Taliban-denied areas would have been logistically untenable, as smaller outposts alone lacked the sustainment capacity to project force effectively. Empirical patterns at Shank underscored the tactical trade-offs: the base endured near-constant IDF since 2008, often exceeding attacks on other FOBs, prompting investments in systems like Counter-Rocket, Artillery, and Mortar (C-RAM) defenses and Patriot batteries for rapid counter-battery fire.[20] [59] [35] While these measures mitigated some risks, the resource intensity—encompassing personnel rotations for base security and materiel for countermeasures—highlighted debates over whether FOB reliance aligned with COIN doctrine's emphasis on mobility and local protection, or inadvertently prioritized asset defense over adaptive enemy pursuit.Costs Versus Benefits
The construction and sustainment of Forward Operating Base Shank imposed significant fiscal burdens, exemplified by a nearly $12 million runway extension completed in June 2010 to support expanded air operations and a $10 million command-and-control facility planned for regional coordination.[19][19] Fuel infrastructure upgrades at the base, estimated at $10 to $25 million, further escalated costs to ensure logistical resilience amid supply chain vulnerabilities, contributing to the broader U.S. investment exceeding $80 billion in Afghan military infrastructure from 2001 to 2018.[19][5] These expenditures yielded proximate operational advantages, such as enhanced force projection into Logar Province, but represented a fraction of the $825 billion total U.S. military outlay in Afghanistan through December 2020, much of which sustained forward bases like Shank without commensurate long-term territorial gains.[60] Human costs at Shank were acutely tied to its exposure to indirect fire, with the base enduring hundreds of rocket and mortar attacks annually—more than most Afghan outposts—resulting in fatalities such as Staff Sgt. Roberto Loeza, killed on May 25, 2012, and a Provincial Reconstruction Team soldier on October 1, 2008.[61] This persistent threat, peaking after 2008 with Taliban targeting of coalition hubs, eroded morale through mandatory sheltering protocols and psychological strain, diverting resources to defensive countermeasures rather than offensive maneuvers.[39][20] Strategically, Shank enabled disruptions of Taliban supply lines and training for Afghan National Security Forces via embedded Provincial Reconstruction Teams, fostering temporary stability in eastern approaches to Kabul through joint patrols that neutralized improvised explosive device threats.[62] Yet these benefits hinged on continuous U.S. logistical support, as evidenced by Afghan forces' post-2014 struggles to maintain base functionality amid corruption and sustainment shortfalls, underscoring a dependency that amplified costs without building self-reliant capacities.[5] Analysts have debated whether such forward bases prolonged engagements by facilitating political timelines—such as the 2011 surge drawdown—for withdrawal that overlooked persistent insurgent resilience, effectively subsidizing operational presence at the expense of decisive outcomes.[63][64]References
- https://handwiki.org/wiki/Engineering:Forward_Operating_Base_Shank