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.

ROAD TO COMBAT TALON II<br />

proposal. <strong>The</strong> details of the reorganization plan<br />

were not officially released until August 1986. At<br />

that time General Patterson signed out a letter<br />

with an attachment titled, “<strong>The</strong> Basis of Forward<br />

Look, Reorganizing the Twenty-Third AF.” Although<br />

Patterson’s letter served as the official announcement,<br />

it did not provide details of the timetable<br />

for implementation. 47 For the three Combat<br />

Talon squadrons, the reorganization provided the<br />

possibility of greater support (especially in the<br />

overseas units), with emphasis on command and<br />

control and the maintenance area.<br />

While MAC and the Twenty-Third AF developed<br />

Forward Look, Congress continued to debate<br />

the reorganization of SOF. By May 1986 Senator<br />

Cohen, with cosponsorship by Sen. Sam Nunn,<br />

introduced Senate bill S. 2453, and the following<br />

month Daniel introduced House bill H. R. 5109.<br />

Many of the key provisions of those two bills later<br />

would form the basis for the defense authoriza -<br />

tion bill that was signed into law on 14 October<br />

1986. <strong>The</strong> final bill passed in October directed the<br />

formation of a unified command for SOF (the US<br />

Special Operations Command), created the Office<br />

of the Assistant Secretary of Defense for Special<br />

Operations and Low-Intensity Conflict, and established<br />

a coordinating board for low-intensity conflict<br />

within the National Security Council. 48<br />

Perhaps the most far-reaching provision of the<br />

October legislation was the creation of Major<br />

Force Program (MFP) 11. Before this legislation,<br />

there were only 10 MFPs, and SOF funding was<br />

provided by the services from those funds. All<br />

three services had a poor record of accomplishment<br />

for funding SOF. <strong>The</strong> acquisition of the<br />

Combat Talon II was an example of how the Air<br />

Force ignored an SOF program that was desired by<br />

Congress while funding conventional core requirements<br />

instead. Representative Daniel had made<br />

his case for separate SOF funding in his article<br />

the previous August proposing a sixth service. In<br />

defense of the services, SOF programs were<br />

funded throughout each service’s POM, and the<br />

relatively small expenditures for SOF had often<br />

been lumped with larger programs within each<br />

service. It was extremely difficult for the services<br />

to manage SOF funding with this disjointed (for<br />

SOF) system in place. Consolidation under MFP<br />

11 made funds visible to both Congress and to the<br />

services, and it provided a measure of protection<br />

against spending SOF dollars for non-SOF items.<br />

With the passage of the defense authorization bill,<br />

Congress passed into law the requirement to reorganize<br />

SOF. It would take another two years,<br />

however, before the new US Special Operations<br />

Command would be established and operational<br />

at MacDill AFB, Florida. 49<br />

With congressional action directing SOF reorganization<br />

signed into law, MAC’s Forward Look<br />

initiative put the command on track to fulfill Congress’s<br />

mandate within the Air Force. A Headquarters<br />

MAC/XPP point paper, dated 31 December<br />

1986, reviewed the reorganization and listed<br />

the reasons MAC supported the initiative. Forward<br />

Look would reduce command layers below<br />

the Twenty-Third AF by inactivating the 2d AD<br />

at Hurlburt Field, and it would establish in-thea -<br />

ter wings in Europe and in the Pacific. It would<br />

also align combat units by location rather than by<br />

mission and by region where they were expected<br />

to be employed. <strong>The</strong> paper concluded that Forward<br />

Look created a command structure that<br />

could absorb future growth, including the Combat<br />

Talon II. In early January 1987 final Air Staff approval<br />

of Forward Look was received, and a public<br />

announcement was made shortly afterwards. On<br />

20 January 1987 Special Order GA-49 was published,<br />

thus putting Forward Look into motion.<br />

<strong>The</strong> 2d AD was inactivated, the USAF Special Operations<br />

School was reassigned from 2d AD to the<br />

Twenty-Third AF, the 1st SOS was reassigned<br />

from 2d AD to the Twenty-Third AF, the 7th SOS<br />

was reassigned from 2d AD to the 39th ARRW at<br />

Eglin AFB, and the 1st SOW (including the 8th<br />

SOS) was reassigned from 2d AD to the Twenty-<br />

Third AF; all effective on 1 February 1987. 50<br />

Included in the January announcement were<br />

plans to move the Headquarters Twenty-Third<br />

AF, from Scott AFB, Illinois, to Hurlburt Field<br />

and to colocate with the 1st SOW. <strong>The</strong> headquarters<br />

would transfer 177 military and 29 civilian<br />

positions. On 1 April 1987 USSOCOM was activated<br />

at MacDill AFB, Florida, with General<br />

Lindsay, USA, commander in chief. On 30 July<br />

1987 General Patterson issued a statement concerning<br />

his understanding of the new relationships<br />

among MAC, USSOCOM, the other unified<br />

commands, and Headquarters, Twenty-Third AF.<br />

In the statement Patterson unofficially designated<br />

the Twenty-Third AF as the Air Force Special<br />

Operations Command and recognized its<br />

status as the air component of USSOCOM. On 1<br />

August 1987 the Twenty-Third AF officially<br />

moved to Hurlburt Field, and a flag-raising ceremony<br />

was held marking the establishment of the<br />

new organization in the heart of USAF special<br />

operations. 51 * * * * * *<br />

303

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

Saved successfully!

Ooh no, something went wrong!