06.03.2015 Views

1 - The Black Vault

1 - The Black Vault

1 - The Black Vault

SHOW MORE
SHOW LESS

Create successful ePaper yourself

Turn your PDF publications into a flip-book with our unique Google optimized e-Paper software.

FROM DESERT ONE TO POINT SALINES<br />

through Phase III objectives had been met. Phase<br />

IV, which included the establishment of a civilian<br />

government in Grenada, would continue throughout<br />

the remainder of the year.<br />

Lessons Learned<br />

Operation Urgent Fury was a success, having<br />

attained its military objectives during the period<br />

from 25 October to 2 November. For special operations<br />

and the entire military community, how -<br />

ever, weaknesses in command and control were<br />

highlighted. CJTF-120 was made up of four sepa -<br />

rate task forces, and these task forces were not<br />

colocated and could not readily communicate<br />

among each other nor with CJTF-120. Airlift and<br />

tanker forces were not OPCON to the CJTF but<br />

rather responded to tasking through JCS. Each<br />

TF had aircraft committed to it, but no single air<br />

manager was designated. <strong>The</strong> CJTF arrangement<br />

resulted in piecemeal control of forces and uncertainties<br />

as to specific areas of responsibility. From<br />

an Air Force perspective, the constant flux in<br />

force composition caused significant difficulties<br />

for air planners in determining requirements and<br />

assessing employment capabilities and options.<br />

Operation Urgent Fury also did not use an existing<br />

plan as the basis of the operation. If it had<br />

used an existing plan, it might have avoided some<br />

of the confusion. A contingency plan was in existence,<br />

which covered the type of operation faced in<br />

Grenada, and it had been practiced in joint exercises<br />

before Operation Urgent Fury. <strong>The</strong> decision<br />

was made not to use the plan, which effectively<br />

meant that the operation started from a no-plan<br />

status. Command difficulties also were experienced<br />

on the ground, with General Schwarzkopf<br />

acting in an advisory role during the first two<br />

days of the operation. He eventually was designated<br />

as Vice Admiral Metcalf’s deputy commander,<br />

which cleared up some confusion in the<br />

chain of command.<br />

<strong>The</strong> short notice of the operation did not allow<br />

Combat Talon sufficient time to plan and “what if”<br />

the plan before execution. Because of the need to<br />

react quickly and decisively to the threat, a rehearsal<br />

of the airfield seizure operation was not<br />

possible. Had a rehearsal been conducted, weaknesses<br />

in the plan (i.e., an abort en route or systems<br />

failure that precluded planned drop sequencing)<br />

could have been more thoroughly addressed<br />

and provisions made for rapid adjustments. <strong>The</strong>re<br />

were also not enough Combat Talons to perform<br />

the mission. Only five aircraft were available at<br />

Hurlburt Field from the 8th SOS, and all five were<br />

committed to the Point Salines airfield assault. A<br />

sixth Combat Talon was hastily deployed from<br />

Europe to serve as a spare for the mission. Additional<br />

SOLL II C-130s were used in combination<br />

with the Talons so that adequate numbers of special<br />

operations forces could be infiltrated on to the<br />

airfield. In all, five Combat Talons and seven<br />

SOLL II C-130s transported rangers into Point Salines.<br />

Had there been sufficient numbers of Talons<br />

to support the mission, there would not have been<br />

a requirement for SOLL II augmentation. As had<br />

been the case three years earlier at Desert One,<br />

the weather played a major part in the success of<br />

the assault. Postmission analysis pointed to the<br />

fact that the ability to forecast accurate weather<br />

information was critical to mission success.<br />

<strong>The</strong> weaknesses in executing a joint operation<br />

did not go unnoticed by Congress. Within three<br />

years, in the Goldwater–Nichols Defense Reorganization<br />

Act of 1986, Congress created the US Special<br />

Operations Command (USSOCOM), which was<br />

tasked to organize and train a special operations<br />

force made up of soldiers, airmen, and sailors from<br />

the three services. USSOCOM would trace its roots<br />

back to the OSS of World War II, and Combat Talon<br />

would become a key player in the new command.<br />

Notes<br />

1. History, 7th Special Operations Squadron, 1 April–30<br />

June 1980, USAF HRA, Maxwell AFB, Ala., supporting document<br />

11, 5.<br />

2. Ibid ., 3 .<br />

3. Ibid., iv.<br />

4. Ibid., 8.<br />

5. History, 7th Special Operations Squadron, 1 October–31<br />

December 1980, 18.<br />

6. History, 8th Special Operations Squadron, 1 October–31<br />

December 1980, 16th Special Operations Wing historian file,<br />

Hurlburt Field, Fla.<br />

7. History, 7th Special Operations Squadron, 1 April–30<br />

June 1981, 1–2.<br />

8. History, 8th Special Operations Squadron, 1 January–<br />

31 March 1981.<br />

9. History, 7th Special Operations Squadron, 1 April–30<br />

June 1981, 13, 21.<br />

10. History, 1st Special Operations Wing, 1 April–30 June<br />

1981, 16th Special Operations Wing historian file, Hurlburt<br />

Field, Fla., vol. 1, II-37 to II-39.<br />

11. History, 1st Special Operations Squadron, 1 April–30<br />

June 1981, Combat Talon Archive, HQ AFSOC/HO, Hurlburt<br />

Field, Fla., supporting document 4, D4-3 to D4-5.<br />

12. Ibid., 11.<br />

13. History, 1st Special Operations Squadron, 1 July–30<br />

September 1981, 11.<br />

287

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

Saved successfully!

Ooh no, something went wrong!