06.03.2015 Views

1 - The Black Vault

1 - The Black Vault

1 - The Black Vault

SHOW MORE
SHOW LESS

You also want an ePaper? Increase the reach of your titles

YUMPU automatically turns print PDFs into web optimized ePapers that Google loves.

PRAETORIAN STARSHIP<br />

radome had experienced structural failure. Inspection<br />

of the Combat Talon II fleet identified<br />

several other radomes with cracks and soft spots<br />

that severely impacted the operational readiness<br />

of the weapons system. 144<br />

<strong>The</strong> following month one 7th SOS Combat<br />

Talon deployed to Norway for Exercise Arctic Express.<br />

<strong>The</strong> squadron provided almost all of the personnel<br />

for the exercise since most of the 352d SOG<br />

was still heavily committed in Brindisi, Italy.<br />

Colonel Scott served as the Joint Special Opera -<br />

tions Air Component Command (JSOACC) commander<br />

and established his base of operations at<br />

Bardufoss, Norway. In addition to the 7th SOS<br />

Combat Talon II, the 160th Special Operations<br />

Aviation Regiment from Fort Campbell, Kentucky,<br />

deployed a contingent of CH-47D aircraft for the<br />

duration of the exercise. <strong>The</strong> exercise consisted of<br />

insertion, extraction, and resupply of special forces<br />

ground units. While on the ground the units executed<br />

special reconnaissance of strategic points<br />

(beach heads, fjord inlets, airports, and transportation<br />

routes), and direct action missions and were<br />

prepared to execute personnel recovery missions<br />

as required. Although the Combat Talon was hampered<br />

by the loss of a transformer rectifier early in<br />

the exercise, most exercise objectives were accomplished<br />

by the squadron. 145<br />

<strong>The</strong> 352d had not received an ORI for several<br />

years, and one was scheduled in the spring of<br />

1994. Continued tasking for Operation Provide<br />

Promise II/Deny Flight had prevented an earlier<br />

inspection. To allow the group the opportunity to<br />

complete its ORI, Headquarters AFSOC agreed to<br />

assume the Brindisi commitment with other a s-<br />

signed forces and temporarily to release the 352d<br />

SOG. Elements from the 16th SOW, including two<br />

8th SOS Combat Talon Is, assumed the SAR alert<br />

duty on 1 March. <strong>The</strong> last of the 352d SOGs personnel<br />

departed Brindisi on 4 April. <strong>The</strong> 16th<br />

SOW remained at Brindisi until 17 June, when<br />

the 352d returned to assume the alert duties. 146<br />

During March and April the group conducted<br />

two operational readiness exercises (ORE) to help<br />

prepare for the ORI scheduled for May. <strong>The</strong> AF-<br />

SOC IG team originally wanted the group to deploy<br />

to Italy for the inspection, but when Italian<br />

officials denied permission due to the saturated<br />

airspace caused by the Balkan operation, they<br />

had to look elsewhere. Locations in Spain, Germany,<br />

and the United Kingdom were considered,<br />

but in the end the only viable location turned out<br />

to be home station. <strong>The</strong> scenario for the exercise<br />

included a terrorist event in a Middle Eastern<br />

country controlled by religious fundamentalists.<br />

For the 7th SOS the unit committed all three of<br />

its Combat Talon IIs to the ORE. Five days after<br />

completion of the second ORE, SOCEUR issued<br />

an exercise warning order to the group, which put<br />

into motion Phase I of the ORI. On 27 April a<br />

SOCEUR exercise execute order was issued, and<br />

the initial deployment phase of the inspection began.<br />

After marshaling cargo and generating all<br />

participating aircraft, the deployment phase was<br />

complete after 36 hours. On 4 May Phase I employment<br />

operations began and continued until 11<br />

May. During Phase I of the ORI, crews completed<br />

100 percent of tasked missions, flying 44 sorties<br />

and 145.4 hours. After completion of the first<br />

phase, the group stood down for 48 hours to reconstitute<br />

before Phase II. Between 18 and 24<br />

May, group assets deployed to RAF Macrihanish<br />

and executed a complex exercise scenario, with<br />

two 7th SOS Combat Talon IIs participating. At<br />

the completion of Phase II, the deployed assets<br />

returned to RAF Alconbury for ORI termination.<br />

Overall, the group received a grade of excellent,<br />

having received an outstanding for initial response,<br />

a satisfactory for unit employment, and<br />

an excellent for combat support. <strong>The</strong> manner in<br />

which the group and the 7th SOS performed validated<br />

its combat capability. 147<br />

With the ORI successfully behind them, group<br />

personnel redeployed to Brindisi to assume once<br />

again SAR alert duties in support of Operation<br />

Provide Promise/Deny Flight. By midmonth elements<br />

of the 21st SOS, 67th SOS, and the 321st<br />

STS were in position at Brindisi. For the 7th SOS<br />

preparations were under way for a change of command<br />

for the squadron. On 1 July 1994 Colonel<br />

Scott assumed command of the squadron from<br />

Lauderdale. Scott had been the operations officer<br />

before taking command, and he continued to emphasize<br />

training and support of the group’s exercise<br />

and JCET program.<br />

Throughout the spring and summer, a civil<br />

war had raged in the Central African country of<br />

Rwanda. By July the situation had deteriorated<br />

to such a degree that the US government publicly<br />

committed itself to providing humanitarian relief<br />

to the besieged people living there. As a result of<br />

this commitment, SOCEUR was tasked by<br />

USEUCOM to provide air and ground support,<br />

and on 22 July it issued a warning order for the<br />

352d SOG to be prepared to deploy all available<br />

7th SOS Combat Talon IIs in support of Operation<br />

Support Hope. Four hours later the group<br />

404

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

Saved successfully!

Ooh no, something went wrong!