Fact-checked by Grok 2 weeks ago

Task Force 11

Task Force 11 was a United States Navy aircraft carrier task force active in the Pacific theater during World War II, initially formed to conduct offensive operations against Japanese forces following the attack on Pearl Harbor.^[1]^[2]
Under Rear Admiral Frank Jack Fletcher's command, Task Force 11, centered on the carrier USS Saratoga (CV-3), departed Pearl Harbor on December 16, 1941, as part of efforts to reinforce Wake Island but was recalled on December 22 due to risks from potential Japanese carrier presence, arriving too late after the island's fall on December 23.^[1]
Reorganized subsequently around USS Lexington (CV-2) under Vice Admiral Wilson Brown, the task force executed air raids on Japanese bases in the Marshall and Gilbert Islands in early February 1942 and on Rabaul later that month, disrupting enemy expansion while developing fast carrier strike tactics.^[3]^[4]
USS Saratoga rejoined as the core carrier after repairs from a January 11, 1942, submarine torpedo hit, enabling Task Force 11's participation in the Battle of the Eastern Solomons in August 1942, where it provided crucial air support during the Guadalcanal campaign despite Saratoga's subsequent torpedoing by Japanese aircraft.^[5]^[6]
These operations highlighted Task Force 11's role in early carrier warfare innovations, though the Wake recall drew postwar criticism for prioritizing fleet preservation over aggressive relief, reflecting cautious command decisions amid incomplete intelligence on Japanese dispositions.^[1]^[7]

World War II

Formation and Initial Deployment

Task Force 11 was formed in the immediate aftermath of the Japanese attack on Pearl Harbor on December 7, 1941, as part of the U.S. Pacific Fleet's reorganization into carrier-centered task forces to conduct offensive operations against Japanese-held territories. Centered on the aircraft carrier USS Lexington (CV-2) as flagship, the task force was placed under the command of Vice Admiral Wilson E. Brown Jr., who flew his flag aboard Lexington.^[8]^[9] This structure reflected the U.S. Navy's shift toward mobile, carrier-based strike groups to counter Japanese expansion in the Pacific, prioritizing rapid deployment over fixed defenses.^[8] The task force's initial deployment commenced on December 14, 1941, after weather delays, as a diversionary element to support Rear Admiral Frank Jack Fletcher's Task Force 14 relief expedition to Wake Island. TF 11 sailed from Pearl Harbor toward the Marshall Islands, specifically targeting a raid on Jaluit Atoll to draw Japanese attention away from Wake.^[8]^[9] However, upon learning of Wake Island's fall to Japanese forces on January 23, 1942, Brown canceled the planned strike, and TF 11 returned to Pearl Harbor on January 22.^[8] During this transit, Lexington patrolled the Oahu-Johnston-Palmyra triangle to interdict potential Japanese raids.^[8] Following refit and preparation, TF 11 conducted its next operation in February 1942, steaming toward Rabaul on New Britain for a carrier strike against Japanese airfields and shipping. Departing Pearl Harbor on February 14, the force approached the target on February 20 but aborted the raid after Lexington was detected by Japanese reconnaissance aircraft, which prompted a damaging air counterattack that inflicted minor casualties and aircraft losses but no ship sinkings.^[10] TF 11 then withdrew to the South Pacific, setting the stage for its role in subsequent engagements like the Battle of the Coral Sea in May 1942.^[8]

Composition and Command Structure

Task Force 11 was commanded by Vice Admiral Wilson Brown Jr., who exercised overall authority from his flagship, the heavy cruiser USS Indianapolis (CA-35).^[11] The task force followed standard U.S. Navy doctrine for carrier striking forces, with Brown directing subordinate commanders for the carrier division, cruiser division, and destroyer squadron, enabling coordinated screening, air operations, and logistics.^[12] The core of TF 11 centered on a single fleet aircraft carrier, initially USS Lexington (CV-2) under Captain Frederick C. Sherman, carrying approximately 70-80 aircraft including Douglas SBD Dauntless dive bombers, Grumman F4F Wildcat fighters, and Douglas TBD Devastator torpedo bombers.^[8]^[13] This was screened by three heavy cruisers—USS Minneapolis (CA-36), USS San Francisco (CA-38), and USS Indianapolis (CA-35)—providing anti-aircraft defense and gunfire support, augmented in some operations by light cruisers such as USS St. Louis (CL-49) and USS Helena (CL-50).^[13] Nine destroyers from Destroyer Squadron 1 or attached units, including USS Dewey (DD-349), USS Farragut (DD-348), USS Aylwin (DD-355), USS Monaghan (DD-354), USS Dale (DD-353), USS Phelps (DD-360), USS Worden (DD-352), USS Hull (DD-350), and USS Lamson (DD-367), formed the inner anti-submarine and torpedo screen.^[13]^[11] Logistical sustainment was handled by the oiler USS Neosho (AO-23), which refueled the force at sea during extended operations in the South Pacific.^[11] Following the loss of Lexington on May 8, 1942, during the Battle of the Coral Sea, TF 11 was reorganized around USS Saratoga (CV-3) as the primary carrier, retaining a similar cruiser-destroyer screen while Brown transitioned command responsibilities amid fleet reallocations.^[14]^[8]

Pacific Theater Operations

Task Force 11, commanded by Vice Admiral Wilson Brown and centered on aircraft carrier USS Lexington (CV-2), executed the U.S. Navy's initial carrier-based offensive in the Pacific on 1 February 1942. Departing Pearl Harbor on 31 January, the task force launched 33 aircraft against Japanese targets in the Marshall and Gilbert Islands, striking airfields at Taroa (Jaluit Atoll), Makin, and nearby installations. The raid destroyed or damaged seaplane hangars, fuel dumps, anti-aircraft batteries, and several aircraft on the ground, with U.S. losses limited to two planes and their crews.^[8]^[15] Prior to this action, TF 11 had faced setbacks during efforts to relieve Wake Island. USS Saratoga (CV-3), operating with the task force, was torpedoed by Japanese submarine I-16 on 11 January 1942, approximately 500 miles west of Oahu, while transporting Marine fighter aircraft; the carrier sustained heavy damage but reached Pearl Harbor for repairs, delaying her return to operations until June.^[8] Lexington then assumed the flagship role for the Marshalls operation, marking the first U.S. counterstrike following Pearl Harbor.^[16] On 20 February 1942, TF 11, comprising Lexington, heavy cruisers Minneapolis, Indianapolis, Pensacola, San Francisco, and ten destroyers, approached Rabaul, New Britain, for a planned carrier strike to disrupt Japanese advances. Detected by Japanese reconnaissance, the force repelled an attack by 27 land-based bombers in two waves; U.S. fighters, led by Lieutenant Edward H. O'Hare, downed 15 enemy aircraft, earning O'Hare the Medal of Honor. No ships were damaged, but two fighters were lost; the raid was aborted due to compromised surprise and fuel constraints, with TF 11 withdrawing successfully.^[16]^[15] In early March 1942, TF 11 rendezvoused with Task Force 17 (Yorktown) south of the Louisiade Archipelago. On 10 March, 104 aircraft from both carriers conducted a coordinated strike on Japanese invasion forces at Lae and Salamaua, New Guinea, sinking four transports, one destroyer, and damaging other vessels, while destroying aircraft and shore facilities; one U.S. plane was lost. This operation demonstrated effective inter-task force carrier coordination but failed to prevent Japanese entrenchment in the region.^[15] TF 11's operations culminated in the Battle of the Coral Sea (3–8 May 1942). Departing for the southwest Pacific in late April, the task force linked with TF 17 on 1 May under Rear Admiral Frank J. Fletcher's overall command. On 4 May, TF 11 aircraft bombed Tulagi, sinking several Japanese ships. During subsequent engagements on 7–8 May, Lexington endured multiple bomb and torpedo hits from Japanese carrier aircraft, leading to uncontrollable fires and explosions; the carrier was scuttled that evening, with 216 crewmen killed and 2,735 rescued. The battle marked the first carrier-versus-carrier clash, halting Japanese advances on Port Moresby, though TF 11 suffered the loss of its primary carrier. Brown was relieved of command on 26 May due to health issues.^[17]^[18]

Strategic Impact and Transition

The engagements involving Task Force 11, particularly its role in the Battle of the Coral Sea from May 1–8, 1942, marked a pivotal shift in Pacific Theater dynamics by halting the Japanese Imperial Navy's southward expansion toward Port Moresby, New Guinea, thereby protecting Allied supply lines to Australia.^[17] Although tactical outcomes included the loss of USS Lexington (CV-2) on May 8 and damage to USS Yorktown (CV-5), the operation sank the light carrier Shōhō and severely damaged heavy carrier Shōkaku, compelling Japan to abandon its invasion convoy and redirect resources to the Guadalcanal campaign.^[19] This demonstrated the efficacy of carrier-based air strikes in denying enemy amphibious objectives without direct fleet engagement, influencing subsequent U.S. Navy doctrine emphasizing dispersed, reconnaissance-led carrier operations over concentrated battleship formations.^[20] Task Force 11's contributions extended U.S. naval air power's reach, forcing Japanese planners to operate within contested airspace and expend carriers prematurely, which eroded their qualitative edge in aviation. Rear Admiral Aubrey Fitch's command of TF 11 during Coral Sea, coordinating with Vice Admiral Frank Jack Fletcher's overall force, preserved operational aircraft and fueled intelligence gains from decrypted Japanese signals, enabling proactive interdiction.^[13] Critics, including some postwar analyses, noted Fletcher's cautious fuel management and withdrawal decisions as overly conservative, potentially forgoing pursuit opportunities, yet these preserved Yorktown for rapid repairs at Pearl Harbor, completed in 72 hours by May 25, 1942.^[21] ![USS Saratoga (CV-3)][float-right] Following Coral Sea, TF 11 transitioned from independent raiding to integrated fleet support, reforming around USS Saratoga (CV-3) after her January 1942 torpedo repairs; by July 7, 1942, she departed Pearl Harbor with heavy cruisers Astoria, New Orleans, Minneapolis, and Vincennes, plus destroyers, to reinforce Southwest Pacific operations.^[5] This shift aligned TF 11 with Admiral Ernest King's emphasis on fast carrier task forces for multi-threat environments, merging temporarily into Task Force 61 alongside TF 16 for the Guadalcanal campaign, culminating in the Battle of the Eastern Solomons on August 23–25, 1942, where Saratoga's aircraft repelled a Japanese carrier strike, sinking cruiser Ryūjō despite her subsequent torpedoing.^[22] By late 1942, TF 11's nucleus supported amphibious landings and convoy protection, evolving into the flexible, multi-carrier groups that dominated later offensives, with Saratoga logging over 120,000 miles and 16,000 landings by war's end.^[5]

Global War on Terrorism

Establishment and Mandate

Task Force 11 was formed in the immediate aftermath of the September 11, 2001, terrorist attacks as the initial Joint Special Operations Command (JSOC) composite task force dedicated to high-value target operations in Afghanistan under Operation Enduring Freedom.^[23] Commanded by U.S. Air Force Brigadier General Gregory Trebon, it integrated elite units from across U.S. special operations forces, including elements from the Army's Delta Force and the Navy's SEAL Team Six, to execute time-sensitive missions.^[24] The task force established its forward headquarters at Bagram Airfield, with a joint operations center at Masirah Island, Oman, to facilitate rapid deployment and command and control.^[25] The mandate of Task Force 11 centered on the capture or elimination of high-value targets (HVTs) within Al-Qaeda and Taliban networks, emphasizing direct action raids, special reconnaissance, and sensitive site exploitation to disrupt terrorist leadership and infrastructure.^[23] This included conducting unilateral operations independent of broader conventional forces, often in coordination with allied special operations elements such as British SAS and SBS units integrated under JSOC oversight.^[26] Unlike conventional task forces, TF 11 reported directly to U.S. Central Command's General Tommy Franks, bypassing intermediate conventional command structures to enable swift, intelligence-driven responses unencumbered by bureaucratic delays.^[24] In addition to kinetic operations, the task force was tasked with synchronizing interagency efforts, incorporating intelligence from the CIA's Special Activities Division and the Defense Intelligence Agency to refine targeting and exploit captured materials for follow-on missions.^[23] This structure prioritized operational secrecy and agility, reflecting JSOC's evolution into a primary instrument for counterterrorism in the Global War on Terrorism, though it later transitioned into successor designations like Task Force 20 for Iraq operations.

Primary Operations and Tactics

Task Force 11, operating under the Joint Special Operations Command (JSOC), focused its primary efforts on intelligence-gathering and direct action missions to neutralize high-value targets (HVTs) within al-Qaeda and Taliban networks during the initial phases of Operation Enduring Freedom in Afghanistan. Established shortly after the September 11, 2001, attacks, the task force prioritized the elimination of terrorist leadership through targeted raids, special reconnaissance, and disruption of command structures, drawing on elite units such as special mission units for rapid-response operations. These activities emphasized integration of human intelligence (HUMINT), signals intelligence (SIGINT), and real-time aerial surveillance to identify and strike individual threats, often in austere mountainous terrain.^[23]^[27] A core tactic involved "quick strike" retaliatory operations, characterized by helicopter insertions under cover of darkness, minimal ground footprints to maintain operational secrecy, and coordination with close air support for precision-guided munitions to suppress enemy defenses. TF-11 teams typically conducted hit-and-run raids to capture or kill HVTs, minimizing prolonged engagements and relying on advanced force operations (AFO) for pre-mission reconnaissance to validate targets and assess risks. This approach allowed for high mobility and deniability but faced limitations in border regions, where porous terrain enabled escapes, as evidenced by the need for interagency collaboration with CIA paramilitary elements for enhanced targeting.^[23]^[28] In the Battle of Tora Bora from December 6–17, 2001, TF-11 supported encirclement efforts against Osama bin Laden and approximately 1,000 al-Qaeda fighters in cave complexes near the Pakistan border, employing small-team insertions, B-52 airstrikes delivering over 700,000 pounds of ordnance, and ground assaults to seal escape routes. Tactics included the use of local Afghan militias for blocking positions supplemented by U.S. special operators for direct assaults, though incomplete border sealing and militia unreliability contributed to bin Laden's evasion into Pakistan.^[29] (Note: Facebook post links to official Army History content) During Operation Anaconda in the Shah-i-Kot Valley from March 2–18, 2002, TF-11 elements executed advanced force reconnaissance and direct action to disrupt al-Qaeda concentrations estimated at 200–300 fighters, inserting teams via MH-47 Chinooks to occupy high ground and interdict exfiltration routes amid harsh weather and enemy anti-aircraft fire. The operation highlighted adaptive tactics such as dynamic targeting with AC-130 gunships and F-15E strikes—totaling over 6,700 joint fires sorties—but revealed vulnerabilities in initial underestimation of enemy strength and coordination challenges with conventional forces, resulting in eight U.S. fatalities, including seven from TF-11-related actions on Takur Ghar.^[25]^[30]

Key Engagements and Outcomes

Task Force 11, operating as Task Force Sword, executed its initial major engagement on October 19, 2001, during Operation Enduring Freedom with the assault on Objective Rhino, a remote airstrip in Helmand Province, Afghanistan. Launched from USS Kitty Hawk using MH-47 Chinook and MH-60 Black Hawk helicopters, approximately 200 JSOC operators from Delta Force and DEVGRU secured the site in a heliborne raid, marking the first U.S. ground combat operation in Afghanistan post-9/11. The operation succeeded in capturing the airfield without resistance, enabling its use as a forward operating base for subsequent special operations and disrupting Taliban control in southern Afghanistan.^[31]^[23] In December 2001, Task Force 11 supported operations at Tora Bora, providing special operations forces alongside Afghan militias and conventional units to target al-Qaeda remnants, including Osama bin Laden. TF 11 elements conducted reconnaissance, direct action raids, and close air support coordination, capturing or killing dozens of fighters and mid-level high-value targets (HVTs) while gathering intelligence on cave complexes. However, bin Laden's escape highlighted limitations in interagency coordination and reliance on local proxies, as U.S. commanders declined committing larger conventional forces, allowing key al-Qaeda leadership to evade capture.^[32]^[23] During Operation Anaconda in March 2002, Task Force 11 focused on advanced force operations, including reconnaissance, HVT strikes, and seizure of key terrain in the Shah-i-Kot Valley, Shahikot Mountains. JSOC teams under TF 11 inserted via helicopter to target al-Qaeda and Taliban holdouts, conducting raids that neutralized command nodes and facilitated the overall coalition effort to clear the area, resulting in hundreds of enemy casualties and the capture of significant intelligence materials. The task force's independent command structure from Combined Joint Task Force Mountain enabled rapid execution but exposed tensions in joint operations, contributing to tactical successes amid broader challenges like enemy reinforcements. Outcomes included the degradation of al-Qaeda's regrouping efforts, though incomplete enemy elimination prolonged instability in eastern Afghanistan.^[23] By mid-2003, elements of Task Force 11 transitioned to Iraq under evolving JSOC designations, integrating into high-value target networks for raids against regime remnants and insurgents. Operations focused on urban manhunts in Baghdad and Tikrit, yielding captures of former Ba'athist officials and early insurgent leaders, which provided actionable intelligence for subsequent task forces like TF 121. While specific TF 11-attributed captures remain classified, the shift enhanced JSOC's adaptation to counterinsurgency, with outcomes including disrupted networks but persistent challenges from adaptive threats and limited strategic impact on overall violence levels.^[23]

Reviews, Controversies, and Effectiveness

Task Force 11 demonstrated tactical proficiency in high-value target raids and special reconnaissance during early Global War on Terrorism operations in Afghanistan, contributing to the disruption of al-Qaeda networks following the 2001 invasion, though strategic successes were limited by the escape of key leaders like Osama bin Laden into Pakistan.^[23] In Operation Anaconda (March 2002), TF 11 elements, including Delta Force and 160th Special Operations Aviation Regiment units, conducted advanced force operations and supported blocking positions, resulting in the confirmed deaths of approximately 100-200 al-Qaeda and Taliban fighters, but the operation failed to encircle and eliminate the main enemy force due to incomplete intelligence and escape routes to Pakistan.^[33] Controversies surrounding TF 11 primarily stemmed from command and control frictions during Operation Anaconda, where the task force reported directly to U.S. Central Command (CENTCOM) General Tommy Franks rather than the tactical commander, Combined Joint Task Force Mountain under Lieutenant General Franklin Hagenbeck, creating a parallel structure that hindered coordination between special operations and conventional forces.^[24] TF 11 commander Brigadier General Gregory Trebon and subordinates, such as Delta Force commander Lieutenant Colonel Pete Blaber, advocated for ground insertions by special operators into the Shah-i-Kot Valley for reconnaissance, arguing that air-centric plans ignored terrain realities and SOF expertise; however, CENTCOM overruled these recommendations, leading to the ill-fated Razor 03 helicopter insertion on Takur Ghar peak on March 4, 2002, which resulted in the deaths of seven U.S. personnel, including SEAL Neil Roberts, and exposed vulnerabilities in real-time decision-making from remote headquarters.^[33] Critics within special operations circles, including Blaber, attributed these outcomes to micromanagement and a lack of deference to on-scene commanders, though CENTCOM defended the structure as necessary for synchronizing joint fires and intelligence.^[34] Assessments of TF 11's effectiveness highlight its role in pioneering JSOC's hunter-killer model, which evolved into subsequent task forces like TF 121 in Iraq, achieving high operational tempos—such as 300 raids per month by 2005—but early Afghanistan missions revealed limitations in integrating with broader joint forces and preventing enemy exfiltration.^[35] Military analysts note that while TF 11's direct action yielded tactical kills and captures, the task force's secretive operations and command autonomy sometimes exacerbated inter-service tensions, prompting post-Anaconda reforms like unified chains under Combined Joint Special Operations Task Force-Afghanistan to improve unity of effort.^[28] Overall, TF 11's contributions laid groundwork for JSOC's later successes, with kill/capture rates exceeding 80% in evolved iterations, but its Anaconda performance underscored the challenges of adapting special operations paradigms to conventional-heavy battlespaces.^[35]

References

[1]
The Forsaken Defenders of Wake Island
Jul 8, 2019 · Task Force 11 (TF 11), built around the aircraft carrier Saratoga (CV-3), with Rear Admiral Frank Jack Fletcher in command, as well as Task ...
[2]
Task Force 11 | Military Wiki | Fandom
During World War II, Task Force 11 was a United States Navy aircraft carrier task force in the Pacific theater. After the attack on Pearl Harbor in December ...
[3]
Carrier Operations in World War II - GlobalSecurity.org
Task Force 11 (TF 11) (Lexington, CV-2) carried out raids on Rabaul in February which helped delay Japanese landings on Lae and Salamaua in New Guinea. Then ...
[4]
Task Force 11 - Naval War in Pacific 1941-45
42/06/08, arrived Midway area ; 42/06/10, meet TF 16 - transferred replacement planes to Enterprise and Hornet ; 42/06/11, departed for P.H. ; 42/06/13, entered ...
[5]
Saratoga V (CV-3) - Naval History and Heritage Command
Light carriers like Independence had proved too small for safe night operations, and Saratoga was rushed out of Pearl Harbor on 29 January 1945 to form a night ...
[6]
World War II Battle Action and Operational Reports, 1941-1945
Report of Action of Task Force 11 with Japanese aircraft on February 20, 1942 submitted by Commander Task Force 11, February 24, 1942. Box 1 Folder 2. Report ...<|separator|>
[7]
Market Street Commandos | Naval History Magazine
We surmised that Task Force One had been ordered by Nimitz to rendezvous with Task Force 11, the group built around the carrier Saratoga (CV-3), near ...Missing: composition | Show results with:composition
[8]
USS Lexington (CV-2) - Naval History and Heritage Command
Jan 11, 2022 · To block possible enemy raids, Lexington patrolled the Oahu-Johnston-Palmyra triangle until 11 January 1942. ... Task Force 11 (TF 11). While ...
[9]
The Relief of Wake Island 1941 - War History
Dec 13, 2024 · ”) Lexington (Task Force 11, Vice Admiral Wilson Brown, Jr.) would conduct a diversionary raid on the enemy airfield on Jaluit in the ...
[10]
In Contact | Naval History Magazine - October 2011 Volume 25 ...
Brown was relieved from carrier task force command on 28 March 1942 to take charge of the newly formed Amphibious Force, Pacific Fleet. His background in ...<|separator|>
[11]
USS Lexington: A Lady to the End - Warfare History Network
On the 14th, she joined Vice Admiral Wilson Brown Jr.'s Task Force 11, also comprising three heavy cruisers, nine destroyers, and the fleet oiler Neosho (AO ...
[12]
Composition of US Forces - Naval History and Heritage Command
Feb 14, 2018 · The Battles of Cape Esperance 11 October 1942 and Santa Cruz Islands 26 October 1942 ... Composition of Joint Task Force One · Target Ships ...
[13]
Defending the USS Lexington: Action Off Bougainville
Task Force 11 comprised the carrier Lexington (CV-2, affectionately called The Lady Lex and commanded by Captain Frederick C. Sherman), the heavy cruisers ...
[14]
What other ships were with USS Saratoga when it was hit by a ...
May 26, 2022 · TF–14 consisted of the fleet carrier Saratoga, the fleet oiler Neches, the seaplane tender Tangier, three heavy cruisers (Astoria, Minneapolis, ...
[15]
Early Raids in the Pacific Ocean
The first offensive operation by Task Forces of the United States Pacific Fleet in the current war took place just 8 weeks after Japan's attack of December 7, ...
[16]
Early Naval Raids - Naval History and Heritage Command
... Navy carrier battle groups (Lexington and Yorktown) operated on a coordinated operation. Lae-Salamaua strike, 10 March 1942. NH 95437. Douglas SBD-3 dive ...
[17]
H-005-3 Coral Sea - Naval History and Heritage Command
May 7, 2019 · USS Yorktown (CV-5) Bombing Squadron 5 (VB-5) SBD-3 aircraft spotted forward on the flight deck, during operations in the Coral Sea, April 1942.
[18]
1942 - Battle of the Coral Sea - Naval History and Heritage Command
The Japanese Imperial Navy sank USS Lexington (CV-2), USS Sims (DD-409), and USS Neosho (AO-23), and damaged Yorktown. The Japanese only lost one small carrier ...
[19]
The Carrier Task Force in World War II | Proceedings
The task force serves, most importantly, as a strategic screen for the more vulnerable craft—transports, supply ships, landing craft, escort carriers, command ...
[20]
How the Navy's Fast Carrier Task Force Swept the Pacific - HistoryNet
Apr 19, 2022 · The first combat-ready F6Fs reached the Pacific Fleet in February 1943. It proved the best carrier-based fighter of the war. Grumman also ...<|separator|>
[21]
Trial by fire in the Coral Sea - Navy Times
May 3, 2019 · Fletcher did not protest. Thirty-six aircraft went down with Lexington, leaving Fletcher's task force with 39 operational planes. Fitch had ...
[22]
Give Credit Where It's Due | Naval History Magazine
On 6 March, the USS Lexington (CV-2) with its Task Force 11 rendezvoused with Task Force 17 for operations that were to include a strike on shipping at Rabaul ...
[23]
Task Force 11 (TF 11) / "Task Force Sword" - GlobalSecurity.org
In addition, TF 11 was tasked with coordinating the interagency effort in Afghanistan to include organizations like the CIA and Defense Intelligence Agency. TF ...Missing: mandate | Show results with:mandate
[24]
[PDF] EXPERIENCING THE FOG OF WAR
Instead, the so-called “Task Force 11,” commanded by Air Force. Brigadier General Gregory Trebon, reported directly to General Franks. These units were also a.<|separator|>
[25]
[PDF] Not A Good Day To Die: The Untold Story of Operation Anaconda
Army Special Operators would later say that to the folks at Bagram and at Masirah. Island, where the Task Force 11 joint operations center was located. The ...
[26]
UKSF: The United Kingdom Special Forces - Grey Dynamics
The main participant was the SBS, integrated into Task Force Sword (later renamed Task Force 11) under the direct command of JSOC. This unit acted as a ...
[27]
Joint Special Operations Command Task Force in the Iraq War
In preparation for the 2003 invasion of Iraq, Task Force 20 was formed based on Task Force 11 ... Global War on Terrorism), CreateSpace Independent Publishing ...
[28]
Joint Special Operations Command - SourceWatch
May 7, 2012 · "Much of the hunting for senior Taliban and al Qaeda members in Afghanistan is being conducted by a unit called Task Force 11, composed mostly ...
[29]
A Decade of Tactical, Operational, and Strategic Effects - Minsky DTIC
forces in Afghanistan (with the exception of Task Force 11), but Mikolashek waited a week before officially giving the order.45 This delay wasted precious ...
[30]
TORA BORA REVISITED: HOW WE FAILED TO GET BIN LADEN ...
[Senate Prints 111-35] [From the U.S. Government Publishing Office] 111th Congress S. Prt. 1st Session COMMITTEE PRINT 111-35 ...
[31]
[PDF] Operation Anaconda - NDU Press
The U.S. battle plan for Anaconda employed forces, tactics, and procedures that reflected earlier successful experiences in Afghanistan. The early stages of the ...
[32]
SECNAV Names Future America-class Amphibious Assault Ship ...
May 2, 2024 · 19, 2001, helicopters launched from USS Kitty Hawk (CV 63) lifted Task Force Sword (FT-11) to Objective Rhino, a remote airstrip in Helmand ...<|separator|>
[33]
[PDF] Operation Enduring Freedom, September 2001-March 2002 - GovInfo
but Task Force 11 troops now had permission to fight alongside them.147. U.S. and Afghan militia forces encountered substantial challenges at Tora. Bora ...
[34]
[PDF] Operation Anaconda in Afghanistan: A Case Study of Adaptation in ...
But General. Hagenbeck did not have command over Task Force 11, a key SOF unit for advanced force operations, such as reconnaissance and strikes against high ...
[35]
[DOC] Background
What is your view of the command structures for Task Force 11 and for Operation Anaconda? ... global war on terrorism,” its independence and influence have ...
[36]
'Top Secret America': A look at the military's Joint Special Operations ...
Sep 2, 2011 · They have hidden behind various nicknames: the Secret Army of Northern Virginia, Task Force Green, Task Force 11, Task Force 121. JSOC leaders ...