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 />

fall of 1976, unit aircrews were being qualified on<br />

the HSLLADS airdrop capability. <strong>The</strong> system had<br />

been tested and certified in 1973, but budget reductions<br />

throughout SOF and the additional requirement<br />

for US Army certification had prevented<br />

earlier employment of the system<br />

throughout the Talon community. 36<br />

<strong>The</strong> long-anticipated tasking for Commando<br />

Talon operations came in October, and the<br />

squadron deployed to Osan AB during three<br />

weeklong periods beginning on 16 October 1975.<br />

<strong>The</strong> 1st SOS flew successful missions nightly<br />

from 16 to 22 October, 16 to 23 November, and<br />

10 to 17 December. 37 By year’s end the 1st SOS<br />

had become an active participant in the defense<br />

of the ROK.<br />

<strong>The</strong> squadron also participated in Specwarex<br />

1-77 from 4 to 14 November in the Philippines.<br />

During the exercise several small-unit counterterrorism<br />

field problems were executed, with the<br />

climax of the exercise designed around a hostage<br />

rescue mission on 12 November. For this mission<br />

participants included USA Special Forces sol -<br />

diers, USAF Combat Control Team (CCT) members,<br />

and an aggressor force made up of US Navy<br />

SEALs. <strong>The</strong> 1st SOS began the exercise by onloading<br />

11 Special Forces, seven CCT personnel,<br />

and one jeep with a driver and a gunner, and<br />

then departing the airfield for a two-hour lowlevel<br />

infiltration route. <strong>The</strong> scenario called for<br />

airdrop of the paratroopers, who were tasked with<br />

freeing the hostages and securing the landing/<br />

extraction zone. Within 10 minutes of the drop,<br />

CCT had marked the landing zone, and the Special<br />

Forces team had moved into position to free<br />

the hostages. <strong>The</strong> Combat Talon landed and offloaded<br />

the gun jeep, which was used to assist in<br />

the hostage rescue operation. After 11 minutes<br />

on the ground, 35 “hostages” were successfully<br />

freed from their captors, and the aircraft departed<br />

the airfield with everyone on board. <strong>The</strong><br />

total elapsed time from airdrop to final departure<br />

was 20 minutes. <strong>The</strong> operation was considered<br />

a success, but additional procedures were<br />

needed to decrease ground time for the aircraft.<br />

38 Although this rescue operation was rudimentary<br />

compared to later exercises, it marked<br />

the first time that a hostage rescue scenario<br />

was included in an SOF exercise with Combat<br />

Talon participation. With the coming storm of international<br />

terrorism, it certainly would not be<br />

the last.<br />

<strong>The</strong> 8th SOS Becomes<br />

a Talon Test Squadron<br />

At the 8th SOS 1976 marked an upsurge in<br />

Combat Talon system testing by the squadron.<br />

Early in the year, from 18 to 19 February, an<br />

HSLLADS orientation conference was held at<br />

Hurlburt Field that was hosted by the TAWC and<br />

attended by Aeronautical System Division (ASD)<br />

representatives and members of the joint community<br />

that would employ the system. <strong>The</strong> conference<br />

was to standardize rigging and loading procedures<br />

and to resolve any questions potential<br />

users might have of ASD. At the conclusion of the<br />

conference, a forward restraint system was identified<br />

as a system deficiency, and TAWC agreed to<br />

provide preliminary engineering studies to ASD<br />

for action. <strong>The</strong> conference was a success, resulting<br />

in an improved HSLLADS capability. 39<br />

On 28 February one aircraft and crew deployed<br />

to Nellis AFB, Nevada, to participate in TAC Project<br />

75T-902, code-named Seabear. <strong>The</strong> test project<br />

was to evaluate the Combat Talon terrainfollowing<br />

and mapping radar systems in a<br />

simulated combat environment. Sorties were<br />

flown on 2, 3, and 4 March, with redeployment to<br />

Hurlburt Field on 5 March 1976. During the test,<br />

a problem with the AN/APQ-122(V)8 radar was<br />

noted. <strong>The</strong> 4 March flight was planned to fly over<br />

a sand dune ridge located in the Nellis AFB<br />

range. <strong>The</strong> area had been identified by F-111 pilots<br />

as hazardous because their radar did not<br />

“paint” the dunes and provide a command to fly<br />

over them. When the Talon passed over the<br />

dunes, its TF/TA radar did not provide a climb<br />

command either, thus bringing the crew to the<br />

conclusion that the system might not detect some<br />

terrain in arid, sandy environments. 40 A warning<br />

was later placed in the Lockheed Technical Manual<br />

to alert operators to the hazard of flying in the<br />

TF mode over deep sand or snow.<br />

<strong>The</strong> primary purpose of the Seabear test was to<br />

determine if certain enemy ECM equipment affected<br />

the Talon radar. Also, chaff and radar decoys<br />

were tested against the radar to determine if<br />

there was any interference. <strong>The</strong> test determined<br />

that the chaff had little effect on the KA band<br />

mapping radar, but it did create interference<br />

when operating in the terrain-following mode.<br />

<strong>The</strong> radar decoys had no effect on the Talon’s radar.<br />

Two enemy jamming systems were also<br />

tested against the AN/APQ-122(V)8, with mixed<br />

results. In general there was some degradation of<br />

the Talon radar, but the system continued to<br />

function while in the low-level mode. 41<br />

166

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

Saved successfully!

Ooh no, something went wrong!