||This article includes a list of references, related reading or external links, but its sources remain unclear because it lacks inline citations. (April 2009)|
|A DC-130H drone control aircraft passing over USS Chosin (CG-65), preparing to launch a pair of AQM-34 Firebee target drones from the aircraft during a test of the ship's Aegis anti-air warfare system.|
|Role||Drone control aircraft|
|National origin||United States|
|Primary users||United States Air Force
United States Navy
|Developed from||C-130 Hercules|
Origin of the design
Ever since World War I, many nations' air forces have investigated different means of remotely controlling aircraft. Spurred by the U-2 Crisis of 1960, the United States Air Force gained a renewed interest in using unmanned aerial vehicles, or drones, to gain intelligence on the SA-2 Guideline Surface-to-air missile system. Under the code names "Lightning Bug" and "Compass Cookie", Ryan 147A target drones were modified for reconnaissance. The drones were test flown over North Korea and China after the Gulf of Tonkin Incident in August, 1964.
While perfect for reconnaissance, the use of a mere radar van for command, track and control limit the combat ability of the drones. The team controlling the drones was limited to a single, stationary recovery area. In order to improve the range and recoverability of the drones, some C-130As were modified to carry the drones on pylons under the wings and were re-designated as GC-130, MC-130 or DC-130.
The DC-130H project was tested at Hill Air Force Base, Utah with the 6514th Test Squadron. The aircraft was designed to carry and deploy up to four drones. In addition to its ability to deploy four drones, it could also provide control for up to 16 drones simultaneously.
The Strategic Air Command (SAC) initially operated DC-130s assigned to its 100th Strategic Reconnaissance Wing (100 SRW) at Davis-Monthan AFB, Arizona from 1966 through 1976. In 1976, the 100th's DC-130s and drone assets were transferred to the 432nd Tactical Drone Group of Tactical Air Command (TAC) at Davis-Monthan AFB. Concurrent with this action, the 100 SRW's U-2 aircraft assets were transsferred to the 9th Strategic Reconnaissance Wing (9 SRW) and merged with the latter's SR-71 aircraft assets at Beale AFB, California. The 100 SRW was then re-designated as the 100th Air Refueling Wing (100 ARW) and relocated to Beale AFB, operating KC-135 Stratotanker aircraft, until its later reassignment to its current home of RAF Mildenhall, United Kingdom.
In the drone carrier role, target or strike (weapons carriers) drones were carried on two pylons located under each wing of the DC-130: one between the engines and one on the outboard of the engines. This allowed the DC-130 to carry and control four drones simultaneously. Strike drones were never deployed operationally and only reconnaissance and electric warfare drone types were used in the field.
DC-130s could launch, track and control the drones. The aircraft contained two launch stations (one for each drone) from which all systems on the drone were activated and checked. From those stations the engines were started, run through their checks and stabilized at the correct power setting for launch. A two-man station, just aft of the flight compartment, contained all the tracking and control functions. Instruments displayed all data transmitted from the drone—such as heading, speed, altitude, power setting and flight attitudes. Navigation and tracking data were fed to a system that plotted the current position of both the drone and DC-130 on a large map board in front of the operators. The planned track of the drone was drawn on the board, which enabled the crew to immediately detect any deviation in the drone's flight path. The drone controllers monitored and recorded video data from drones equipped with television cameras and recorded any other data collected by other special-purpose drones.
Reconnaissance drones were much larger and heavier, meaning the DC-130As could only carry one drone pylon under each wing. Each drone pylon was placed between the engines, replacing the auxiliary fuel tank on earlier models. When a select number of C-130E aircraft were converted to drone carriers as DC-130Es for USAF, they retained the underwing tanks and the drone pylons were installed outboard of the engines. This significantly increased the new DC-130s' capability and endurance. Concurrent with the USAF transition to the DC-130E model, the extant DC-130As were transferred to the US Navy for target drone carrier and control operations in the Navy's Southern California Operating Area (SOCAL OpArea), flying missions originally from NAS North Island in San Diego, California and later to NAS Point Mugu in Ventura County, California.
The Q-2C Firebee target drone was modified for the recon mission and designated the BQM-34A or 147A. Its size was increased to provide greater range and payload. For the low altitude mission, the wing span was increased to 15 feet (4.6 m) and later to 27 feet (8.2 m), but was most successful with the original 13 foot (4.0 m) wingspan. Wing spans of 27 and 33 feet (8.2 and 10.1 m) were used for the high altitude aircraft. The original 1700 pounds-force (7.6 kN) of thrust was increased to 1920 lbf (8.5 kN) and later to 2800 lbf (12.5 kN) for the special high altitude, long range drones. Some models were even equipped with wing-mounted fuel tanks to extend their range.
The drones had numerous navigation systems - including inertial, Doppler, and LORAN. They were equipped with an analogue computer which controlled speed, altitude, heading, engine settings, sensors and recovery systems. That system turned all sensors on and off and directed all turns, climbs, dives (as well as the rate of each) and engine power settings. Depending upon their mission, the equipment also included:
- Rivet Bounder - a system to jam the SAM's guidance signal
- TWT - a traveling wave tube to give it the return of a U-2 or even larger aircraft
- CRL - a system to suppress contrails to reduce visual detection
- HIDE - a system to reduce the aircraft's radar reflectivity
- HEMP - a system to detect interception by enemy fighters and initiate evasive actions
- HATRAC - a system for high altitude flights to detect intercept by either fighter aircraft or surface-to-air missiles and take evasive actions
Sensors included numerous cameras to satisfy the many different objectives of both low and high altitude sorties. The cameras may be fixed, turreted, or scanning horizon-to-horizon film cameras. Some provided fine detail of specific targets while others covered large areas. There were also TV cameras that could be zoomed and panned.
Numerous electronic receivers are also in place. They were designed to intercept communications of all sorts, radars, data links, etc. The intercepted data was then transmitted to other aircraft, ground sites or satellites. Some of the receivers could be tuned by an operator in another airplane or on the ground. The function of some receivers was strictly defensive. When they detected and identified a signal as a threat, they would trigger a jamming signal, dispense chaff and/or initiate defensive maneuvers.
For recovery, they have a recovery system and receivers that permitted overriding the program and flying it 'by hand'. The recovery sequence was triggered by the flight control computer at the preset position, unless overridden by the Drone Recovery Officer (DRO) in the control vehicle. Normally the drone was picked up by radar as it approached the recovery area and controlled by the DRO. Last minute course corrections were made as necessary and the recovery sequence triggered at the precise point to drop the drone on top of the waiting recovery helicopter. The on-board recovery system consisted of a servomechanism that shut down the engine, deployed a drag chute (to cause the drone to nose over) and opened the main parachute at a preset altitude. The recovery helicopter then flew over the main chute engaging a reinforced catch chute with a set of trailing hooks attached to an internal winch. The drone was then winched up to just below the recovery helicopter and flown back to base. An alternative method of recovery allowed the drone to reach the ground under the main chute. On ground impact a sensor operated a charge that severed the chute risers allowing the drone to be recovered. This method had a higher likelihood of damage and was not preferred.
The DC-130 program was eventually closed, as it was deemed too expensive to support. Launching a single drone required the maintenance and support for the DC-130, the drones, and the drone recovery helicopters (HH-3 and/or HH-53).
In the opening days of Operation Iraqi Freedom in 2003, a Navy-flown DC-130 dropped three Firebee target drones borrowed from the Air Force. Two others were ground-launched. The unmanned aircraft flew over Baghdad spooling out clouds of chaff until they too ran out of fuel and crashed. They led the flights of Tomahawk cruise missiles responsible for the "shock and awe" attacks into Baghdad.
- Crew: Air Force: 6 officers: pilot, co-pilot, navigator, remote control officer, and 2 launch control officers, and 2 enlisted: flight engineer and MCGS (microwave control guidance system) operator; eight Navy crew.
- Related development
- C-130 Hercules
- C-130J Super Hercules
- AC-130 Spectre/Spooky
- Lockheed EC-130
- Lockheed HC-130
- Lockheed LC-130
- Lockheed MC-130
- Lockheed WC-130
- Aircraft of comparable role, configuration and era
Media related to DC-130 Hercules drone control aircraft at Wikimedia Commons