Operation Anaconda Command Structure

874 Words4 Pages

Introduction Operation Anaconda was the largest battle in the initial invasion of Afghanistan. The planning of the operation proved to be complex, especially in dealing with multi-unit joint operations. Despite the limited time for planning, limited multi-unit interoperability, and lack of resources, Organizational Management functions played an essential role in the successful execution of Operation Anaconda.
Planning and Organizing Joint Special Operations Task Force North (JSOTF-N) started the initial planning of Operation Anaconda. Forward Combined Forces Land Component Commander (CFLCC-FWD) finalized the plan for Operation Anaconda on February 13, 2002, in Bagram Airfield. On February 17, 2002, Central Command (CENTCOM) and CFLCC gave command authority of the operation to MG Franklin L. “Buster” Hagenback, commander of the 10th Mountain Division and Combined Joint Task Force (CJTF) Mountain. At this time, CJTF Mountain had a little over a week to take over an operation in which originally was tasked to Special Operations Forces (SOF).
Complex Command Structure CJTF Mountain had command authority over 3rd Brigade (BDE), 101st Air Assault Division, Task …show more content…

The attack on Shahi Kot valley was broken down into two phases. The first phase codenamed “Hammer”, comprised of the Afghan Forces supported by the SOF teams, would attack from the south and the north. In theory this would worse the enemy would force the enemy to retreat towards the entrance in to the valley in Serhkkhankel, where the U.S. Forces codenamed “Anvil” would be waiting for them. In the first few days, casualties occurred when a U.S. Navy SEAL fell off a chinook helicopter after the helicopter took fire, and had no choice but to land to a farther landing zone. This resulted in a rescue attempt by another chinook to insert a Quick Reactionary Force (QRF) of Rangers in which they also suffered casualties in the successful extraction of the U.S. Navy