History of Unmanned Combat Air Vehicles
From Wikipedia, the free encyclopedia
The history of Unmanned Combat Air Vehicles (UCAV) describes the development and history of Unmanned Combat Air Vehicles (UCAV) and is closely tied to the general history of unmanned aerial vehicles (UAV) since UCAVs are a specialized development or offshoot of Unmanned Air Vehicles.
Contents |
[edit] UCAV origins
If UAVs could be used for reconnaissance, it was obvious that they could also be used for active combat missions, at least in principle. In practice, shooting at a specific target is much trickier than flying over an area and taking pictures, and it wasn't until the 1970s that the US Air Force seriously experimented with the concept. The objective was to study an attack system to perform the dangerous "suppression of enemy air defenses (SEAD)" mission, or in other words to destroy enemy anti-aircraft gun and SAM sites. The project was known as HAVE LEMON, a somewhat odd choice of name, since in US slang a "lemon" is a troublesome and worthless automobile, or similar unwanted machine.
HAVE LEMON involved a number of Ryan Firebees equipped with a weapons pylon under each wing, a forward-looking TV camera, and a datalink mounted in a pod on top of the vertical tailplane. These UAVs were given the designation "BGM-34A" and used beginning in late 1971 to perform remote-control strikes on simulated air-defense sites with Maverick missiles and HOBOS TV-guided glide bombs.
The results were good enough to permit follow-on development, resulting in the "BGM-34B", which featured an extended nose to accommodate an infrared imaging system (some sources say low-light-level TV) and laser target designator for targeting and control of laser-guided bombs. Tests performed with in 1973 and 1974 with the BGM-34B were also successful, and led Teledyne Ryan to develop a "BGM-34C" as a conversion of existing Lightning Bug airframes. The BGM-34C could be used for reconnaissance or strike missions by swapping out nose modules and other elements.
The concept proved to be a little too far ahead of its time. Nobody in the Air Force hierarchy stepped forward to take ownership of the issue, and the HAVE LEMON exercise faded away. The test squadron was disbanded in 1979 and its roughly 60 UAVs were put into storage. However, in the summer of 2003 a UAV "airshow" of sorts was conducted, in which a Firebee was displayed carrying two Hellfire anti-armor missiles, as well as a pod for dispensing remote battlefield sensors; apparently Northrop Grumman was running the idea up a flagpole to see if anyone would salute.
UAV advocates claim the Air Force abandoned UAVs for strike missions because of inclination of "hotshot flyboys" to keep the mission for themselves, but in fact the concept has always suffered from "command and control" problems, such as the vulnerability of communications links to jamming and spoofing, and the need to hit specific targets and not accidentally kill civilians or friendly troops.
Over the next two decades, more reliable communications links were developed, automated systems came into much wider use, and the military learned to be much more comfortable with such new technologies. In the late 1990s, the concept of using UAVs for performing actual combat, was revived in the form of various designs generally designated as "uninhabited combat air vehicles".
One of the initial concepts was to develop a UCAV on a fast track for "air occupation". The idea was to use unpiloted aircraft to fly continuous patrols over hostile territory, with some of the aircraft fitted with sophisticated sensors to identify enemy activities and target them, and other aircraft following up with attacks. The idea was obviously inspired by USAF air patrols over Iraq and the Balkans. Lockheed Martin suggested rebuilding old F-16A fighters as UAVs, fitting them with a wide wing to provide additional fuel, and also permit carriage of six or more air-to-surface weapons to provide the air-occupation strike element. The modified F-16As would have had endurance of 8 hours over a target area, and three sets of them could maintain 24-hour coverage.
The US Navy also began studies for UCAVs at about the same time. The Navy saw that UCAVs had a number of potential benefits. They promised to be cheaper than manned aircraft, with a lower purchase cost and much lower operating costs, since operators could be given much of their training through simulations. UCAVs would also be smaller and stealthier than manned aircraft, and could perform High-G maneuvers impossible with piloted aircraft, allowing them to dodge missiles and enemy fighters.
Indeed, since the Navy found themselves increasingly committed to the use of expensive cruise missiles to perform punitive strikes and other limited military operations, UCAVs offered a potentially cheaper alternative, a "reusable cruise missile". One UCAV could carry a number of smart GPS-guided munitions and hit multiple targets on a single sortie, and then return home to be used again. Even with a high combat attrition rate, the cost would be less than that of a barrage of cruise missiles.
Lockheed Martin performed studies that envisioned a number of different naval UCAV configurations, including "short takeoff and landing (STOVL)" aircraft that could be operated off of aircraft carriers, or "vertical attitude takeoff and landing (VTOL)" or "pogo" aircraft that could be operated off destroyers and other surface combat ships, or even submarines.
Piloted pogo aircraft were flight-tested in the 1950s and proved a technological dead end at the time, since they couldn't carry a useful payload and were extremely difficult to land even under benign conditions. The payload limitations can be addressed with lighter materials and RATO-boosted takeoff, and modern digital flight control systems can address the landing issue. The Navy has envisioned using pogo UCAVs to arm a guided-missile destroyer "unmanned air wing" with 20 pogo UCAVs for strike, and five pogo UAVs for reconnaissance.
The submarine launch concept was even more speculative, since recovery was a problem. The Lockheed Martin UCAV concepts were in the 4.5 tonne (10,000 pound) weight class and carried a warload of 450 kilograms (1,000 pounds). Weapons were carried internally to improve stealth and consisted of 45 kilogram (100 pound) and 115 kilogram (250 pound) small smart bombs, now under development.
Range would be about 1,100 kilometers (680 miles), with capability for probe-and-drogue aerial refueling. Top speed would be in the high subsonic range, and ceiling would be about 12.2 kilometers (40,000 feet). The UCAVs would be equipped with fairly simple radar or electro-optical sensors to give the operators imagery of the target. Long-range sensing would be provided by other platforms in air or space.
One Lockheed Martin UCAV concept was an arrowhead-shaped vehicle with no vertical surfaces and the air intake on top. A shaft-driven lift fan would exhaust through the nosewheel door for vertical landings, while the nose sensor array would pivot forward to expose the intakes for the lift fan. The UCAV would have a retractable refueling probe, communications antennas mounted on the aircraft's spine, and lights for navigation and refueling operations. Moveable wingtips and control surfaces along the sawtooth rear edge of the UCAV would eliminate the need for vertical stabilizers.
Another Lockheed-Martin UCAV concept envisioned a diamond-shaped tailless flying wing, with an engine buried down the centerline, and conformal weapons bays flanking the engine. For greater stealth, the UCAV would flip onto its featureless back and fly upside-down.
Such UCAVs could be available in several versions: one with an afterburning engine for maximum performance; one with a non-afterburning engine, but with a thrust-vectoring exhaust for better maneuverability; and one with a conventional non-afterburning engine for low cost.
UCAVs missions would be conducted by an operator in a ground vehicle, warship, or control aircraft over a high speed digital data link. The operator would not really be flying the UCAV directly, however, since the robot would be able to handle the details of flight operations by itself, leaving the operator in a supervisory role. The UCAV would be able to complete its mission autonomously if communications were cut.
[edit] USAF / Boeing X-45 UCAV
In March 1999, DARPA awarded a contract to Boeing for two "X-45A" UCAV technology demonstrators ahead of Northrop Grumman and Raytheon. Boeing rolled out the first prototype for public presentation at Saint Louis, Missouri, in September 2000. First flight was on 22 May 2002, from Edwards Air Force Base in California, and was followed a few months later by the second prototype.
The first demonstrator was built to a "Block 1" standard, with a UHF control link and an L-band telemetry link. The second demonstrator was built to "Block 2" standard, with an added UHF satellite communications link and a "Link 16" fighter data link, and the first machine was updated to that standard. The two demonstrators were then flown on cooperative test missions. The tests investigated operation of multiple UCAVs in military operations; integration of UCAVs with other military operations; and the feasibility of using reservists to fly the robot aircraft.
There has since been X-45B/C versions with greater fuel capacity and hence longer range.
[edit] US Navy / Northrop Grumman X-47A Pegasus UCAV
The US Navy did not commit to practical UCAV efforts until the summer of 2000, when the service awarded contracts of $2 million USD each to Boeing and Northrop Grumman for a 15-month concept-exploration program.
Design considerations for a naval UCAV included dealing with the corrosive salt-water environment, deck handling for launch and recovery, integration with command and control systems, and operation in a carrier's high electromagnetic interference environment. The Navy was also interested in using their UCAVs for reconnaissance missions, penetrating protected airspace to identify targets for the attack waves.
The Navy went on to give Northrop Grumman a contract for a naval UCAV demonstrator with the designation of "X-47A Pegasus", in early 2001. The Pegasus was rolled out on 30 July 2001 and performed its first flight on 23 February 2003 at the US Naval Air Warfare Center at China Lake, California.
[edit] US Joint Unmanned Combat Air System (J-UCAS)
Both the Air Force and the Navy had been developing plans for operational follow-ons to their respective demonstrator programs, but pressures rose for the two services to merge their efforts, resulting in the formation of the "Joint Unmanned Combat Air System (J-UCAS)" program in October 2003 under DARPA direction.
Of course, the candidates for the J-UCAS program include follow-ons to the X-45A and the X-47A. DARPA and Boeing had been working on the "X-45B", a scaled-up X-45A that was seen as the prototype for an operational machine that would reach service in 2008, and would carry a 1,590 kilogram (3,500 pound) load to a combat radius of 1,665 kilometers (900 nautical miles). Two were to be built, but before any metal could be bent for the two X-45B prototypes planned, the Air Force redirected the effort to an even more capable machine, the "X-45C".
The goal of the J-UCAS effort was to select a single contractor to provide from 10 to 12 machines for operational evaluation in the 2007:2008 time frame. Current plans are to obtain two X-45Cs and two X-47Bs to perform a comparative evaluation and then select a winner for development in the 2010 time frame.
The USAF envisioned that J-UCAS will feature:
- Stores pylons on the wings for external fuel tanks or additional munitions.
- Mid-air refueling capability.
- A narrow field-of-view SAR-MTI system for targeting and post-strike damage assessment.
The Navy is interested in many of the features on the Air Force wish list, though the Navy has put reconnaissance and jamming at the top of the list and strike at the bottom.
In the 2006 Quadrennial Defense Review it was stated that the J-UCAS program would be terminated and instead a new long-range strategic bomber program has been launched. [1]
[edit] USAF Hunter-Killer
This is the U.S. Air Force program for which several companies have developed vehicles. In the 2004, the U.S. Air Force, in need of a less expensive short-term UCAV solution with a focus on endurance, opened up a competition for a "Hunter-Killer" UCAV. Specifications include:
- An operating altitude of 10.7 to 15.25 kilometers (35,000 to 50,000 feet).
- Endurance from 16 to 30 hours or more carrying a load of 1,360 kilograms (3,000 pounds), in specific six 225 kilogram (500 pound) guided bombs.
- Fit of SAR/MTI or EO/IR sensors and laser target designator. Of course, the Hunter-Killer would be capable of performing surveillance or reconnaissance missions along with its active combat role.
The Air Force wants to field the Hunter-Killer by 2007 and may order up to 60 machines. The program seems on avoiding expensive custom made components ("gold plate"), instead preferring "off-the-shelf" avionics.
[edit] International UCAV development efforts
There is considerable interest in UCAVs elsewhere, but so far matters have not advanced as far as they have in the US. The British displayed a concept UCAV designated "Proteus", of no relation to the Scaled Composites Proteus. It was essentially a reusable cruise missile, with a long chisel-shaped fuselage with a hexagonal cross section, pop-out forward-swept wings, and triangular tailfins. It was apparently to be recovered by parachute and can carry a number of different warloads.
The Swedish government has worked with the SAAB company to perform studies for a UCAV designated "SHARC", for "Swedish Highly Advanced Research Configuration". The study project was initiated in the late 1990s, and nine different configurations were considered, leading to selection of a single design. Low-speed wind tunnel tests were conducted in 1999, and included drop tests of plausible munitions fits from the SHARC's internal weapons bays. This was followed by a secret flight test of a subscale demonstrator in early 2002.
The French Dassault firm has flown a subscale model of a stealthy UAV, designated the "Aeronef de Validation Experimentale (Experimental Air Vehicle / AVE", or "Petit DUC (Little Demonstrator UAV)". The AVE is intended to demonstrate Dassault's expertise in stealthy aircraft design, and could lead to UCAVs, reconnaissance UAVs, and high-speed expendable targets.
First flight of the Petit DUC was in July 2000. The Petit DUC is a manta-ray-like black diamond of an aircraft, with twin tails and an engine intake on the back of the aircraft. It has retractable tricycle landing gear and is powered by twin AMT engines. Wingspan and length are both 2.4 meters (7.9 feet), empty weight is 35 kilograms (77 pounds), loaded weight is 60 kilograms (132 pounds), operational radius is about 150 kilometers (93 miles), and top speed is about 600 km/h (350 mph).
The Petit Duc was to be followed by a "Moyen (Medium) DUC" demonstrator, and then a "Grand DUC" demonstrator. However, in late 2004 the direction of the effort changed somewhat. The French DGA defense procurement agency initiated a government effort to fly a UCAV demonstrator by 2008 and stated that a contract would be awarded to Dassault in early 2004. This led to interest from a number of European countries, including Italy, Belgium, Switzerland, Spain, Sweden, and Greece, in creating a joint effort with France to develop an operational UCAV, named "Neuron". Germany is interested but has not moved to sign up just yet.
[edit] Israel
Israel is interested in armed UAVs and it is believed that IDF drones have been used to perform precision strikes in Lebanon and the Gaza Strip. Israel has customized the Elbit Hermes 450 UAV to carry two Hellfire missiles and this UCAV has been fully operational for several years.
IAI recently rolled out the Eitan, a huge UCAV with anti-ballistic and assault capabilities. The Eitan has a wingspan of 26 meters and a takeoff weight of four tons, about four times the weight of the largest UAV now in the Israel Air Force. According to the Israeli Air Force, the aircraft has advanced avionics on a level similar to that of systems that operate on fighter-jets, operates with complete autonomy and allows the operator to focus more on performing the mission and less on flying the air platform. Industry sources have said that the Eitan would be a multi-purpose UCAV that could carry out reconnaissance and attack missions, including the ability to locate and destroy mobile ballistic missile launchers.
Israeli officials have for several years been interested in a large, piston-powered UCAV that would loiter at high altitude and dispense smart munitions as required by ground or other forces, acting basically as a flying fire-support base.
At present the Israelis are keeping very quiet about specifics. The Israelis are very enthusiastic about UAVs, seeing them as the way of the future, since they will permit Israel to perform surveillance, strike, and other missions with much less risk to personnel and at a fraction of the acquisition and operational cost of manned aircraft.
[edit] Other
In the spring of 2003, Alenia Aeronautica of Italy unveiled a non-flying ground-test prototype of a half-scale UCAV demonstrator, known as an "Integration Technology Vehicle (ITV)", with a flight prototype to follow. Other UCAV efforts have included the stealthy Seraph proposed by Kentron of South Africa; a number of UCAV design concepts proposed by the European Aerospace & Defense Systems (EADS) conglomerate, a merger of Matra-Aerospatiale of France, DaimlerChrysler of Germany, and CASA of Spain; and a number of vague proposals from the Russians.
[edit] External links
- Israel sets combat drones against missile launchers in Gaza, World Tribune, May 8, 2007
- Israel Starts Reexamining Military Missions and Technology, Aviation Week, August 20, 2006
[edit] References
This article contains material that originally came from the web article Unmanned Aerial Vehicles by Greg Goebel, which exists in the Public Domain.
