1 - The Black Vault
1 - The Black Vault
1 - The Black Vault
Create successful ePaper yourself
Turn your PDF publications into a flip-book with our unique Google optimized e-Paper software.
to MAC’s newly formed Twenty-Third Air Force,<br />
which was responsible for all special operations<br />
and SAR forces. <strong>The</strong> Twenty-Third Air Force was<br />
located at Scott AFB, Illinois, and was made up<br />
primarily of rescue personnel that had been assigned<br />
to the deactivated Air Rescue Service.*<br />
<strong>The</strong> immediate result of the reorganization for the<br />
1st SOS was felt in the maintenance area. Since<br />
coming to Clark AB as part of the 3d TFW, the<br />
squadron had developed an excellent and dedicated<br />
maintenance capability for Combat Talon<br />
unique systems. When the squadron was transferred<br />
to MAC, the 3d TFW retained many of the<br />
squadron’s specialized maintenance personnel in<br />
its wing, with the remainder transferred to the<br />
374th TAW. <strong>The</strong> 374th TAW then assigned the<br />
specialists throughout its maintenance shops,<br />
thus resulting in a huge decrease in maintenance<br />
capability for the 1st SOS. 63 <strong>The</strong> decreased maintenance<br />
capability would affect the squadron for<br />
the remainder of the year.<br />
A few days after the reorganization, the 1st<br />
SOS deployed two aircraft and a CAFSOB support<br />
package to Korea for Team Spirit 83 and<br />
operated out of Kimhae AB from 5 to 22 March.<br />
Some of the former 3d TFW dedicated maintenance<br />
personnel already had been committed to<br />
the exercise before the conversion to MAC, resulting<br />
in smooth maintenance operations during<br />
the exercise. Aircraft and personnel from the<br />
374th TAW and the 317th TAW (located at Pope<br />
AFB) also deployed for the exercise, each with a<br />
“MAC mission commander” designated to command<br />
its respective element. <strong>The</strong> resulting confusion<br />
had an impact on the exercise, with CAF-<br />
SOB planners from the 1st SOS questioned by<br />
other MAC-committed units as to command and<br />
control arrangements. During the exercise 66<br />
missions were successfully completed out of a<br />
tasked 95, with weather being responsible for 16<br />
cancellations. Overall, the exercise was a success<br />
due to the commitment of all exercise partici -<br />
pants. 64<br />
Concerned with decreasing maintenance indicators<br />
since the transfer to MAC, Colonel Cox visited<br />
Clark AB and the 1st SOS from 18 to 20<br />
April. What Cox saw so concerned him that he<br />
sent an immediate message to the commander of<br />
Twenty-Third Air Force, relaying the problems<br />
FROM DESERT ONE TO POINT SALINES<br />
faced by the squadron. Since consolidation under<br />
MAC, 1st SOS aircraft had deteriorated to a point<br />
that the specialized subsystems installed on the<br />
aircraft were marginally operational. One assigned<br />
aircraft had 67 delayed discrepancies, and<br />
the aircraft suffered from low-maintenance priority<br />
within the 374th TAW. Documents revealed<br />
that the host wing did not work the Combat Talons<br />
until they appeared on the flying schedule—<br />
and only then were systems critical for flight repaired.<br />
<strong>The</strong> sophisticated radar and ECM equipment<br />
were rarely in fully mission-capable status.<br />
With the reorganization the 374th TAW had not<br />
maintained the capability to repair the radar, the<br />
inertial navigation system, the electronic countermeasures<br />
system, or the aerial refueling system<br />
installed on the Combat Talon. After returning to<br />
Hurlburt Field, Cox sent a report to Twenty-Third<br />
Air Force outlining the problems he found at<br />
Clark AB. 65 Some improvements were seen locally<br />
for the squadron after Cox’s visit, but little increase<br />
in maintenance capability was seen until<br />
after the end of the calendar year.<br />
* * * * * *<br />
<strong>The</strong> year of 1982 had been extremely busy for<br />
the 8th SOS, and 1983 promised to be the same,<br />
with traditional exercises scheduled along with<br />
quarterly joint events. In addition, weekly training<br />
was scheduled to keep joint components ready<br />
to respond to the growing worldwide terrorist<br />
threat to the United States.<br />
Throughout the latter part of January, 1st<br />
SOW forces participated in the Alaskan Exercise<br />
Brim Frost 83, with the 8th SOS deploying one<br />
aircraft and crew. Hobson was designated the AF-<br />
SOB commander for the exercise. <strong>The</strong> Combat<br />
Talon flew two air defense exercises on 24 and 25<br />
January as a slow-moving airborne penetrator.<br />
On 31 January the 8th SOS flew an infiltration<br />
mission and, on 1 February, exfiltrated two Special<br />
Forces teams from Fort Wainwright. <strong>The</strong><br />
Combat Talon flew nine sorties and 50.5 hours<br />
during the exercise. 66<br />
Beginning on 1 February, the 1st SOW was<br />
alerted for a no-notice quarterly exercise named<br />
Prairie Runner. For the next 48 hours, the wing<br />
mobilized and prepared to launch forces to Patrick<br />
AFB, Florida. On 4 February one Combat<br />
__________<br />
*When Air Rescue Service was deactivated, the facilities that it occupied at Scott AFB, along with most of its personnel, were transferred to the<br />
newly established Twenty-Third Air Force. <strong>The</strong> primary emphasis of the headquarters (as perceived by Combat Talon operators) heavily leaned<br />
towards improving combat rescue capabilities rather than those of special operations. Over succeeding years resentment grew between the two<br />
factions, with career special operations personnel being forced into assignments at Scott AFB when volunteers were not available. Promotions<br />
suffered for SOF personnel assigned to the headquarters, as MAC and Twenty-Third Air Force looked out for their career officers who had grown<br />
up in the MAC system, or at least that was the perception within the Combat Talon community.<br />
265