Operation Anaconda was a joint operation. Even though it was a joint operation, this does not necessarily mean cohesive. This is especially true of the air operations. Poorly executed joint functions, primarily air operations, resulted in diminished close air support capabilities during Operation Anaconda due to confusion of control of aviation assets, lack of proper communication equipment, and available air coordination personnel were overwhelmed. Confusion of control of Aviation Assets The first reason for the diminished capabilities was that there was confusion on who had tactical control of some aviation assets. Without positive control of all available assets, problems were inevitable. Task Force Dagger, the Special Operation Force element, was part of Combined CJTF Mountain (CJTF), the overall command element. CJTF Mountain was not granted Tactical Control (TACON) of TF Dagger though. This also means that TF Dagger retained control of its aviation assets (Fleri, 2003). The aviation assets in question still assigned to TF Dagger were the AC-130 gunships. These aircraft are one of the most capable close air support assets that is available to the troops on the ground. This fixed wing aircraft is heavily armed. These armaments include a 25mm Gatlin gun, 40mm Bofors cannon, and a 105mm howitzer cannon (af.mil, 2016). This aircraft is one of the best close air support assets in the United States inventory. This also makes this it a high demand asset in
Six raids were conducted during the interval prior using similar tactics and patterns of maneuver. Minimal changes were made to the plan of operations from raid to raid. One of the drawbacks to performing several very similar operations was that Aideed’s forces used the intelligence collected during these raids to better prepare for a fight with the Ranger element. With each progressive raids, Aideed’s forces had identified the use of low circling helicopters and the lack of armored vehicles as the weaknesses of Joint Task Force Ranger. It became clear the week prior to the Battle of Mogadishu that Somalis were capable of shooting down helicopters with RPGS. MG Garrison added rockets to Blackhawks for added firepower. However, he but did not postpone operations while armor or heavier gunships were requested. He also failed to modify raid plans to keep helicopters out of the firing range of
The purpose of this paper is to identify the uses and application of mission command within Operation Anaconda. Operation Anaconda took place in the Shahikot Valley of eastern Afghanistan in early March of 2002. The ground commander selected to lead the operation was Major General (MG) Hagenbeck of the 10th Mountain Division, and for the purpose of this operation, Coalition and Joint Task Force (CJTF) Mountain. Due to the limited number of troops under his command currently available in Afghanistan, MG Hagenbeck was given command in addition to one of his own organic battalions, the 3rd Brigade, 101st Air Assault Division, some Special Operations Force (SOF) units, and Coalition Forces. This paper will identify MG Hagenbeck’s, his staff’s, and higher command’s use of the mission command principles during this operation. The principles of mission command are accept prudent risk, use mission orders, exercise disciplined initiative, provide a clear commander’s intent, create shared understanding, and lastly, build cohesive teams through mutual trust (Mission Command, 2014).
Training objectives must support the mission profile and meet the commanders desired end state. Prior to the 56TH train up at the National Training Center (NTC) the deployment location changed from Iraq to Afghanistan (case study). Changes to mission essential tasks were not identified prior to NTC, resulting in the BCT training on collective tasks and validated during MRE based on the Iraq mission profile. However, the shift to the Afghanistan mission profile created gaps in training not identified until units arrived at Bagram Air Field (BAF). i.e. the BCT had to establish an MRAP drivers training program at BAF extending the RSOI process. Training gaps were not limited to company level shortfalls as battalion and brigade staffs were not able to anticipate potential threats and capitalize on opportunities. (case study 2)
The mission command system is expressed as the placement of individuals within a unit conducting operations with a specific set of procedures and principles in place to optimize the use of its equipment. What does it mean to recognize or comprehend the art of Command and the science of Control? There are six key principles of mission command in developing a cohesive team that support all aspects of a mission. The following essay will discuss these principles and examine examples of how the famous Operation Anaconda both endured victories and inadequacies.
In the mountainous Shah-i-Khot region south of the city of Gardez in Eastern Afghanistan, Operation Anaconda took place early March 2002. Operation Anaconda, to this day, stands as the largest reported ground action in the Afghan war. This 17-day battle led to eight U.S. casualties and over 50 wounded. Operation Anaconda is viewed as a success due to coalition forces being able to kill and root out several hundred Taliban and al Qaeda fighters, which left U.S. and coalition forces in control of the Shah-i-Khot Valley. Originally intended to be a three-day battle with light resistance, a seven-day battle ensued with intense fighting and was finally
However; MG Hagenbeck was only given operational control of certain ground elements that were slated to be involved in the mission. He was not given command of the U.S air component from the Air Force, Navy or Marines, who were slated to support Anaconda ground operations. MG Hagenbeck also did not have command authority of the friendly Afghan forces who were to play a major role in the operation. Afghan forces coupled with U.S. Army Special Operations Forces were the “Hammer” that would drive al Qaeda and Taliban fighters toward the “Anvil” composed of U.S. forces and Afghan forces. Anaconda nearly became a crushing defeat for the U.S forces, because of the number of competing commands that were assigned major roles of responsibility in the operation.
10th Mountain Division’s Commander, General Hagenbeck became the Combined Joint Task Force Commander. CJTF Mountain would be operating out of Bagram Air Base in Afghanistan. Colonel Mulholland was the Special Forces Commander also located in Afghanistan. They both agreed that a cordon was needed around the valley and slowly tighten in on the Taliban forces. The mission was appropriately named Operation Anaconda.9
SOF were organized into five individual task forces with specific roles and responsibilities: Joint Special Operations Task Force-North (JSOTF-N), know as Task Force Dagger; Joint Special Operations Task Force-South (JSOTF-S), known as Task Force K-Bar; Task Force Sword; The Joint Inter Agency Task Force – Counter Terrorism (JIATF-CT), known as Task Force Bowie; and
In early January 2002, American intelligence received evidence of a large volume of enemy forces assembling in the Shahi Kot Valley in Eastern Afghanistan. Central Command (CENTCOM), led by General Tommy R. Franks, was directing combat operations in Afghanistan through the Coalition Forces Land Component Command (CFLCC) and Coalition Forces Air Component Command (CFACC). As the interest in assaulting the Shahi Kot Valley amplified, General Franks reached a conclusion that a U.S. tactical commander was a need in Afghanistan. The decision was to assign the 10th Mountain Division Commander, Major General (MG) Franklin Hagenbeck, as the tactical commander. In an effort to strengthen MG Hagenbeck’s command authority, CENTCOM named his headquarters Combined Joint Task Force (CJTF) Mountain and gave it command and control authority over Operation Anaconda. By having command and control authority, MG Hagenbeck would encounter challenges with the command structure. The challenges of command structure were due to CJTF Mountain not having tactical control (TACON) of multiple Special Operation Forces, the Joint Special Operations Air Component (JSOAC), and friendly Afghanistan forces. These misunderstandings were resolved during the execution phase, but rectifying the command relationships prior would have avoided lost time and resources needed on enemy forces and positions. In this paper, I will identify the challenges of command structure during Operation Anaconda.
The command structure of Operation Anaconda was multi-headed and lacked unity due to the U.S. military presence not being fully established prior to, or during, execution which adversely effected the operation. According to College of Aerospace Doctrine, combat operations were directed by CENTCOM under General Franks, based at MacDill AFB FL, with 2 subordinate commands, Coalition Forces Land Component Command (CFLCC) and Coalition Forces Air Component Command (CFACC). CFACC was led by U.S. Air Force Lt. Gen Michael Moseley & CFLCC was led by Army LTG Paul Mikolashek. CFLCC & CFACC were both based in the Persian Gulf where they directed Afghanistan force operations. MG Franklin Hagenbeck, commanded the 10th Mountain Division, Task Force Mountain, the forward headquarters for CENTCOM in Afghanistan. MG Hagenbeck answered to LTG Mikolashek directly, whom headed up all land forces in the theatre of operations. Combined Air Operations Center dire was headed by LTG Michael Moseley, based at Prince Sultan Air Base in Saudi Arabia. Special Operations Forces (SOF) Task Force (TF) Dagger headed by Col. John Mulholland, commanded Special Forces operations in Afghanistan. TF Rakkasan, 3rd Brigade of the 101st Air Assault Division was commanded by COL Frank Wiercinski based in Kandahar. Afghan forces supporting the operation were led by Zia Loden, a local warlord. TF-K Bar Joint Special Operations Task Force (JSOTF) South Kandahar, Afghanistan was headed by CPT Robert H
To understand how some of the soon to be discussed failures arose, all of the key commanders need to be identified. When Operation Enduring Freedom (OEF) began General Tommy Franks was the CENTCOM Combatant Commander in Tampa, Florida. Events on 9/11 lead to us having forces in Afghanistan soon after. From the beginning of the war Special Forces (SOF) were the primary assets utilized. As time went on conventional units were joining the forces in theatre. This caused the need for the Command and Control (C2) structure to adapt to the
Due to the sensitivity of the mission, the Department of Defense chose to bypass already established Joint Task Forces (JTF) that existed. Instead, an ad-hoc JTF was created specifically for Operation Eagle Claw. The newly created JTF encountered problems defining areas of responsibility and areas of focus. The JTF included three branches of the military in the operation the Navy, Army, and Air Force. The operation rehearsed for five months prior to its execution. The JTF never conducted a rehearsal during the five months. All elements conducted individual rehearsals only joining on the night of execution. Problems that were encountered on the night of Operation Eagle Claw were never identified prior which ultimately contributed to the failure of the mission.
The Joint Force Commander (JFC) utilizes command and control to exercise authority over assigned and attached forces within his or her command. Command provides direction and motivation to individuals and units, whereas control is the task of managing forces and the associated tasks required to accomplish the mission. Effective command and control successfully balances the art of command with the science of control and strengthens the commander’s ability to make and execute decisions. Mission command advances command and control
After taking 25 years to develop the F-22 Raptor from conception to operational certification, the United States Air Force (USAF) produced the world’s first 5th generation air superiority fighter. This revolutionary fighter plane leveraged its very low observable stealth (VLO), thrust-vectoring and digital fly-by wire capabilities, and other cutting edge technology to produce an extremely fast, agile and lethal air-to-air combatant. Less than five years after operational certification in 2009, Robert Gates, Secretary of Defense, (SECDEF) convinced the President (POTUS) and Congress to truncate the F22 program, leaving the USAF with fewer than 187 operational F-22 Raptors. This number was well short of the 381 aircraft the USAF’s
|Varying workforce size by |Avoids the costs of other |Hiring, layoff, and training |Used where size of labor pool |