Drone strikes against targets associated with al Qaeda or affiliated groups became the common feature of these wars and a source of power for military and intelligence officials. The Air Force owned the drones and conducted strikes in Afghanistan, but the CIA carried them out covertly in Pakistan, and the CIA and the military competed for control over the strikes in Yemen.
The early experience with drone strikes against "high-value targets" was an unmitigated disaster. From 2004 through 2007, the CIA carried out 12 strikes in Pakistan, aimed at high-value targets of al Qaeda and its affiliates. But they killed only three identifiable al Qaeda or Pakistani Taliban figures, along with 121 civilians, based on analysis of news reports of the strikes.
But on the urging of CIA Director Michael Hayden, in mid-2008 President Bush agreed to allow "signature strikes" based merely on analysts' judgment that a "pattern of life" on the ground indicated an al Qaeda or affiliated target. Eventually it became a tool for killing mostly suspected rank-and-file Afghan Taliban fighters in both Pakistan and Afghanistan, particularly during the Obama administration, which had less stomach and political capital for outright war and came to depend on the covert drone campaign. This war was largely secret and less accountable publicly. And it allowed him the preferable optics of withdrawing troops and ending official ground operations in places like Iraq.
Altogether in its eight years in office, the Obama administration carried out a total of nearly 5,000 drone strikes--mostly in Afghanistan--according to figures collected by the Bureau of Investigative Journalism.
But between 2009 and 2013, the best informed officials in the U.S. government raised alarms about the pace and lethality of this new warfare on the grounds that it systematically undermined the U.S. effort to quell terrorism by creating more support for al Qaeda rather than weakening it. Some mid-level CIA officers opposed the strikes in Pakistan as early as 2009, because of what they had learned from intelligence gathered from intercepts of electronic communications in areas where the strikes were taking place: they were infuriating Muslim males and making them more willing to join al Qaeda.
In a secret May 2009 assessment leaked to the Washington Post, General David Petraeus, then commander of the Central Command, wrote, "Anti-U.S. sentiment has already been increasing in Pakistan"especially in regard to cross-border and reported drone strikes, which Pakistanis perceive to cause unacceptable civilian casualties."
More evidence of that effect came from Yemen. A 2013 report on drone war policy for the Council on Foreign Relations found that membership in al Qaeda in the Arabian Peninsula in Yemen grew from several hundred in 2010 to a few thousand members in 2012, just as the number of drone strikes in the country was increasing dramatically--along with popular anger toward the United States.
Drone strikes are easy for a president to support. They demonstrate to the public that he is doing something concrete about terrorism, thus providing political cover in case of another successful terrorist attack on U.S. soil. Donald Trump has shown no interest in scaling back the drone wars, despite openly questioning the stationing of troops across the Middle East and Africa. In 2017 he approved a 100 percent increase in drone strikes in Yemen and a 30 percent increase in Somalia above the totals of the final year of the Obama administration. And Trump has approved a major increase in drone strikes in Afghanistan, and has eliminated rules aimed at reducing civilian casualties from such strikes.
Even if Obama and Trump had listened to dissenting voices on the serious risks of drone wars to U.S. interests, however, another political reality would have prevented the United States from ending the drone wars: the role of the private defense contractors and their friends on Capitol Hill in maintaining the status quo.
Unlike conventional bombing missions, drone strikes require a team to watch the video feeds, interpret them, and pass on their conclusions to their mission coordinators and pilots. By 2007 that required more specialists than the Air Force had available. Since then, the Air Force has been working with military and intelligence contractors to analyze full-motion videos transmitted by drones to guide targeting decisions. BAE, the third-ranking Pentagon contractor according to defense revenues, claims that it is the "leading provider" of analysis of drone video intelligence, but in the early years the list of major companies with contracts for such work also included Booz Allen Hamilton, L-3 Communications, and SAIC (now Leidos).
These analysts were fully integrated into the "kill chain" that resulted, in many cases, in civilian casualties. In the now-famous case of the strike in February 2010 that killed at least 15 Afghan civilians, including children, the "primary screener" for the team of six video analysts in Florida communicating via a chat system with the drone pilot in Nevada was a contract employee with SAIC. That company had a $49 million multi-year contract with the Air Force to analyze drone video feeds and other intelligence from Afghanistan.
The pace of drone strikes in Afghanistan accelerated sharply after U.S. combat ended formally in 2014. And that same year, the air war against ISIS began in Iraq and Syria. The Air Force then began running armed drones around the clock in those countries as well. The Air Force needed 1,281 drone pilots to handle as many "combat air patrols" per day in multiple countries. But it was several hundred pilots short of that objective.
To fulfill that requirement the Air Force turned to General Atomics--maker of the first armed drone, the Predator, and a larger follow-on, the MQ-9 Reaper--which had already been hired to provide support services for drone operations on a two-year contract worth $700 million. But in April 2015 the Air Force signed a contract with the company to lease one of its Reapers with its own ground control station for a year. In addition, the contractor was to provide the pilots, sensor operators, and other crew members to fly it and maintain it.
The pilots, who still worked directly for General Atomics, did everything Air Force drone pilots did except actually fire the missiles. The result of that contract was a complete blurring of the lines between the official military and the contractors hired to work alongside them. The Air Force denied any such blurring, arguing that the planning and execution of each mission would still be in the hands of an Air Force officer. But the Air Force Judge Advocate General's Office had published an article in its law review in 2010 warning that even the analysis of video feeds risked violating international law prohibiting civilian participation in direct hostilities.
A second contract with a smaller company, Aviation Unlimited, was for the provision of pilots and sensor operators and referred to "recent increased terrorist activities," suggesting that it was for anti-ISIS operations.
The process of integrating drone contractors into the kill chain in multiple countries thus marked a new stage in the process of privatizing war in what had become a permanent war complex. After 9/11, the military became dependent on the private sector for everything from food, water, and housing to security and refueling in Iraq and Afghanistan. By 2009 contractors began outnumbering U.S. troops in Afghanistan and eventually became critical for continuing the war as well.
(Note: You can view every article as one long page if you sign up as an Advocate Member, or higher).
2
1
1
