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.

ROAD TO COMBAT TALON II<br />

slipped indefinitely due to continuing unsatisfactory<br />

progress of the aircraft’s radar. <strong>The</strong> USAF<br />

conducted a thorough program review during the<br />

latter half of 1988, which resulted in the program<br />

being restructured and having a more realistic<br />

IOC date established. During 1988 five more C-<br />

130H aircraft were delivered—88-0191, 88-0192,<br />

88-0193, 88-0194, and 88-0264—thus bringing the<br />

number of CT II identified airframes delivered to<br />

the USAF to 16 aircraft. <strong>The</strong> five aircraft were<br />

cycled through LAS Ontario’s Chino facility for<br />

initial modifications then put in long-term storage<br />

at Lockheed-Georgia, and at Rickenbacker AFB,<br />

Ohio, awaiting further modification at E-Systems.<br />

Flight testing at Edwards AFB and CT II modifi -<br />

cations at Greenville continued on the first 11 aircraft.<br />

For the 8th SOS the full impact of the slip<br />

of the Combat Talon II IOC date began to unfold<br />

during the fall of 1988.<br />

After assuming command and settling into the<br />

job, Thigpen focused on the number of aircraft<br />

available to the squadron for operational use.<br />

<strong>The</strong> Talon I test programs, along with PDM and<br />

modification schedules, steadily reduced the<br />

number of available aircraft to the 8th SOS<br />

throughout the fall of 1988, with an all-time low<br />

of one Talon I aircraft projected to be available in<br />

the spring of 1989. Without the Combat Talon II<br />

aircraft to offset the loss of the Talon Is, the<br />

squadron could not fulfill its commitments. With<br />

responsibility for the formal Combat Talon<br />

School and facing an ORI in January, the situation<br />

had to change. At the annual Combat Talon<br />

Management Review conference held at LAS Ontario<br />

in the fall of 1988, the problem was surfaced,<br />

and possible solutions were discussed. During<br />

follow-up actions spearheaded by the Twenty-Third<br />

AF, the modification schedule was adjusted by slipping<br />

several input dates. Agreements also were<br />

reached with SOCPAC and SOCEUR that essentially<br />

assured that the 8th SOS would not fall<br />

below four aircraft being assigned at any time.<br />

Four aircraft available at Hurlburt Field were<br />

the minimum required to keep the Combat Talon<br />

School functioning, keep assigned crews profi -<br />

cient, and support joint requirements with a twoaircraft<br />

package. <strong>The</strong> agreement would leave the<br />

1st and 7th SOS with only two Combat Talons<br />

much of the time, but each squadron was augmented<br />

with an assigned slick C-130E to provide<br />

additional pilot- and navigator-proficient sorties.<br />

<strong>The</strong> 8th SOS also was assigned a C-130E for basicproficiency<br />

flying.<br />

With a plan developed to ensure Talon I availability,<br />

the 8th SOS prepared for its upcoming<br />

ORI scheduled for January 1989. <strong>The</strong> 1st SOW<br />

had not been given an ORI since the December<br />

1985 Purple Duck evaluation at Biggs AAF. Since<br />

that time MAC had completely rewritten ORI criteria<br />

by which the wing would be evaluated. Using<br />

a building-block approach, the wing conducted<br />

limited recall and mobilization exercises and then<br />

put the parts together during a local ORE. By<br />

December a second ORE had been completed, and<br />

wing leadership felt that they were ready for the<br />

following month’s evaluation.<br />

1989: Project 46 Is Terminated<br />

Although Forward Look was still in the implementation<br />

phase in January 1989, the ORI of the<br />

1st SOW would be the first test of the Twenty-<br />

Third AF’s reorganization. With only one SOF<br />

wing in the numbered air force, the 1st SOW represented<br />

the majority of USAF’s SOF capability.<br />

<strong>The</strong> 1st SOW ORI, named Jaguar Bite, was conducted<br />

from 9 January to 17 February 1989. <strong>The</strong><br />

US Special Operations Command sponsored the<br />

exercise. It was the first JCS-coordinated, USSO-<br />

COM-sponsored exercise and had the largest participation<br />

of Air Force SOF assets in the history of<br />

Air Force SOF. Along with four Combat Talons<br />

from the 8th SOS, the 1st SOW deployed MH-<br />

53H Pave Low helicopters and AC-130H gunships<br />

to Fort Campbell, Kentucky, when alerted by the<br />

MAC IG team. Weather was a significant factor<br />

during the exercise, with wind-chill factors recorded<br />

at minus 70 degrees Fahrenheit in the<br />

Montana exercise area and minus 50 degrees in<br />

Michigan. 82 Elements of the USA’s 1st Special Operations<br />

Command provided most of the ground<br />

forces for the ORI. <strong>The</strong> 39th SOW at Eglin AFB<br />

also participated with its assigned HC-130 and<br />

MH-60 aircraft, but they were not part of the 1st<br />

SOW’s evaluation.<br />

<strong>The</strong> exercise was unprecedented in scope and<br />

duration, taking place over a 40-day period and<br />

encompassing operations based out of Hurlburt<br />

Field, Pope AFB, and Fort Campbell. Rotarywing<br />

operations were conducted as far north as<br />

the upper peninsula of Michigan. <strong>The</strong> western<br />

exercise area centered on Helena, Montana, and<br />

primarily involved the 8th SOS Combat Talons.<br />

Despite the weather and the extreme distances<br />

flown, the most grueling evaluation in SOF history<br />

resulted in an overall rating of excellent by<br />

the MAC IG. Some problems surfaced in command<br />

and control and in joint coordination, but<br />

311

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

Saved successfully!

Ooh no, something went wrong!