What’s all the fuss about President Obama’s “kill list”? If there is a list of terrorists to be killed with drone strikes on the soil of a country where we’re not officially at war, shouldn’t it be the president who decides to pull the trigger? For such an extraordinary occasion, ripe with moral issues and potential diplomatic consequences, it is properly the president’s call, not the CIA director’s or the nearest four-star general’s.

This has long been the case. When the United States fired cruise missiles at Osama Bin Laden’s training camp in 1998, it was President Bill Clinton who gave the order. When a team of SEALs raided Bin Laden’s compound in Pakistan in 2011, few challenged that President Obama held the power to decide whether or not to go in. Why should this be the case for killing Bin Laden but not for killing the No. 2 or No. 3 al-Qaida leader in Yemen or Somalia?



The New York Times article that revealed Obama’s “secret ‘kill list,’” written by the highly scrupulous team of Jo Becker and Scott Shane, noted that the president started taking an active role early in his term, after the first drone strike he approved killed several civilians. From then on, Obama would meet with a dozen senior officials in the White House Situation Room to discuss the latest candidates nominated for death. According to the article, Obama “signs off on every strike in Yemen and Somalia and also on the more complex and risky strikes in Pakistan—about a third of the total.”

Stipulating that the United States needs to do this now and then (more about which, later), isn’t it a good thing that the president is taking responsibility for these borderline cases, that he’s not leaving it up to the spymasters or the generals, whose purview on such matters is narrower and whose tolerance for risk might be looser?

The real objections to Obama’s direct involvement in this business seem to be about tangential matters.

First, there is the matter of Obama himself. These grisly discussions in the Situation Room seem at odds with the image of this liberal president who came to office pledging to step away from the seamier side of President Bush’s war on terror and who, a few months later, won the Nobel Peace Prize. The Times’ headline put the concern neatly: “A Measure of Change—Secret ‘Kill List’ Proves a Test of Obama’s Principles and Will.”



Yet the only dissonance here is with a stereotype of Obama. During the 2008 campaign, he spoke out against the Iraq war, torture, and unjustified detention. But he also openly called for escalating the war in Afghanistan and stepping up the war against al-Qaida, even to the point of saying that he would bomb high-level terrorists hiding out in Pakistan, whether or not the Pakistani leaders approved (a position that his opponents in the election derided at the time). The Nobel Peace Prize was always an oddity, more an expression of the jury’s hopes than a reward for any deeds. But go back and read Obama’s speech at the ceremony, which is no less strange, an eloquent defense of a nation’s right to use force.

Second, there is a widespread discomfort over drones—the small, pilotless planes armed with video cameras and smart bombs, controlled by video-game-style joysticks, that rain death on unsuspecting targets from half-a-world away. As Jon Stewart put it (with some deliberate hyperbole), “The president’s killing people with flying robots!” P.W. Singer, a defense analyst at the Brookings Institution, has said the same thing with a straight face, calling drones “deadly robots” and likening them to the A.I. trading programs that occasionally wreak havoc with the stock market.



It’s conceivable that someday drones will be autonomous, just as conceivably nuclear missiles might be wired to a radar network so that they’re launched automatically upon the earliest warning (whether true or false) of an attack. But nobody has done this yet, and the trends run in the opposite direction.

The official name for drones is “unmanned aerial vehicles,” but the only thing unmanned in the program is the vehicles. Each drone flying over Afghanistan, Pakistan, Yemen, or wherever is backed by 43 military personnel rotating in three shifts. They include seven joystick pilots, seven system operators, and five mission coordinators—backed by an intelligence unit, usually at CIA headquarters in Langley, Va., consisting of (again, for each drone up in the sky) 66 people, including 34 video crew members, and 18 intelligence analysts. (These numbers come from Air Force public affairs.)



According to a recent Air Force report, unearthed by Wired magazine’s Danger Room website, the military is nearly 600 personnel short of what it needs to man the ever-expanding drone arsenal. If Singer’s fears were on the mark, the Pentagon’s managers might be expected to shave the manpower requirements—especially in times of tight budgets—and make the “robots” more autonomous. In fact, though, they’re recruiting more people to fill the slots.

In this sense, the disclosure of Obama’s “kill list” should be assuring. Not only are people—trained, authorized personnel—very much in control of what the drones do; in the most sensitive cases, the ultimate decision is made, in a very deliberate fashion, by the president of the United States.



Finally, there is the broader concern of whether the president even has the right to engage in “targeted killing.” The issue, as Katrina vanden Heuvel argued in a Washington Post op-ed, is “the assertion of a presidential prerogative that the administration can target for death people it decides are terrorists—even American citizens—anywhere in the world, at any time, on secret evidence with no review.” She calls on Congress to “reassert its constitutional authority” to declare war.

The questions she raises are troubling but also muddled. Congress passed a joint resolution in September 2001, authorizing the president to use “all necessary and appropriate force” against al-Qaida. For better or worse or both, Presidents Bush and Obama have invoked that authority with very wide latitude, as was intended. Congress has no further “constitutional authority” to choose or deny targets.

As for the probity of targeted killing, regardless of which branch of government approves it, it is worth noting that President Gerald Ford issued an executive order in 1975, stating, “No employee of the United States government shall engage in, or conspire to engage in, political assassination.” This order came in the wake of hearings held by Sen. Frank Church’s committee, revealing a vast dark landscape of CIA activities in the previous decades, including many attempted assassinations.

Legal scholars have disputed whether Ford’s executive order applied only to the killing of foreign government leaders (it didn’t define “assassination”). In any case, the controversy was rendered moot in 1998, when President Clinton revised the order to allow for the death of such leaders if it resulted from a counterterrorism operation. Clinton’s aides also took to invoking Article 51 of the United Nations charter, which allows nations fairly free rein in the pursuit of self-defense. Those caveats, bolstered by the Authorization to Use Military Force, passed by Congress in 2001, leaves little doubt as to the drone strikes’ legality.



However, questions do remain about the strikes’ wisdom—and here, Congress does have a proper role to play.

First is the simple practice of oversight. I have tacitly assumed in this column that the targets on the “kill list” are appropriate and urgent targets—i.e., that they do pose a direct threat to the United States. I don’t know that, of course; nor do I expect to be briefed on the intelligence informing this judgment. But the congressional intelligence committees should expect to be. They are, by law, notified whenever the president issues a “finding”—a classified action involving intelligence agencies. Are they similarly notified when the president approves a “kill list” candidate? And can they ask for a briefing on the intel that put the target on the list? If not, they should be.



Second is the broader question of the policy behind the strikes. Are they having an effect on the war against al-Qaida? Does killing the No. 2 in Yemen degrade the organization, or does it just mean the ascension of an equally competent No. 3? Have the killings to date triggered a backlash? Ibrahim Mothana, co-founder of the Watan party, writes in an op-ed in today’s New York Times, “Drones strikes are causing more and more Yemenis to hate America and join radical militants.” Is this true? I don’t know, but it’s a question worth investigating.

David Petraeus, as CIA director, is no doubt sensitive to this dilemma. In 2006, back when he was a three-star general, he wrote in the Army’s counterinsurgency field manual, “An operation that kills five insurgents is counterproductive if collateral damage leads to the recruitment of fifty more insurgents.” Sometimes, as the manual acknowledged, it’s so important to kill those five insurgents, the risk of siring more is worth taking. Still, the gamble should be acknowledged and weighed—and not just by those tossing the dice.



Finally, what is U.S. policy in Yemen these days? According to a study released this week by Peter Bergen and Jennifer Rowland at the New America Foundation, the Obama administration has launched 20 drone strikes in Yemen just in the last three months—two more than in the previous two years. All told, drone and conventional air strikes have killed between 531 and 779 people in Yemen, 96 percent of them militants.

There is reason for this intensity: Al-Qaida in the Arabian Peninsula, which operates out of Yemen, is now seen as the center of the most dangerous operations, the locus of several attempted attacks against the United States. AQAP’s ranks are said to have swelled to more than 1,000 fighters (up from 200 to 300 just three years ago), and they control significant parts of southern Yemen. But what is the U.S. aim: to stave off attacks against the United States, or to help stabilize the Yemeni government? Obviously the two are related, and there is a contingent of U.S. Special Forces conducting counterterrorist and counterinsurgency operations. But are we getting sucked into an internal conflict in Yemen, and what are the implications—the dangers and opportunities—if we are?



After the Times published its story about Obama’s kill list, many members of Congress had only one question: Who leaked the information? It’s a legitimate question, but here’s the one they should be asking: Where is all this leading us?