Are Afghan Lives Worth Anything?

This story first appeared on the TomDispatch website.

It was a blast. I'm talking about my daughter's wedding. You don't often see a child of yours quite that happy. I'm no party animal, but I danced my 64-year-old legs off. And I can't claim that, as I walked my daughter to the ceremony, or ate, or talked with friends, or simply sat back and watched the young and energetic enjoy themselves, I thought about those Afghan wedding celebrations where the "blast" isn't metaphorical, where the bride, the groom, the partygoers in the midst of revelry die.

In the two weeks since, however, that's been on my mind — or rather the lack of interest our world shows in dead civilians from a distant imperial war — and all because of a passage I stumbled upon in a striking article by journalist Anand Gopal. In "Uprooting an Afghan Village" in the June issue of the Progressive magazine, he writes about Garloch, an Afghan village he visited in the eastern province of Laghman. After destructive American raids, Gopal tells us, many of its desperate inhabitants simply packed up and left for exile in Afghan or Pakistani refugee camps.

• Photo Essay: The Hidden Half

  Behind the veils.

• MoJo Interview: Khaled Hosseini, Kabul's Splendid Son

  The Kite Runner author Khaled Hosseini talks about homecomings and Taliban-censored flamingos. With audio.

• Obama's Great Afghanistan Gamble

  17,000 more troops can't win the war in Afghanistan. So what's the exit strategy?

One early dawn in August 2008, writes Gopal, American helicopters first descended on Garloch for a six-hour raid:

"The Americans claim there were gunshots as they left. The villagers deny it. Regardless, American bombers swooped by the village just after the soldiers left and dropped a payload on one house. It belonged to Haiji Qadir, a pole-thin, wizened old man who was hosting more than forty relatives for a wedding party. The bomb split the house in two, killing sixteen, including twelve from Qadir's family, and wounding scores more... The malek [chief] went to the province's governor and delivered a stern warning: protect our villagers or we will turn against the Americans."

That passage caught my eye because, to the best of my knowledge, I'm the only person in the U.S. who has tried to keep track of the wedding parties wiped out, in whole or part, by American military action since the Bush administration invaded Afghanistan in November 2001. With Gopal's report from Garloch, that number, by my count, has reached five (only three of which are well documented in print).

The first occurred in December of that invasion year when a B-52 and two B-1B bombers, wielding precision-guided weapons, managed, according to reports, to wipe out 110 out of 112 revelers in another small Afghan village. At least one Iraqi wedding party near the Syrian border was also eviscerated — by U.S. planes back in 2004. Soon after that slaughter, responding to media inquiries, an American general asked: "How many people go to the middle of the desert... to hold a wedding 80 miles from the nearest civilization?" Later, in what passed for an acknowledgment of the incident, another American general said: "Could there have been a celebration of some type going on?... Certainly. Bad guys have celebrations." Case closed.

Perhaps over the course of an almost eight-year war in Afghanistan, the toll in wedding parties may seem modest: not even one a year! But before we settle for that figure, evidently so low it's not worth a headline in this country, let's keep in mind that there's no reason to believe:

* I've seen every article in English that, in passing, happens to mention an Afghan wedding slaughter — the one Gopal notes, for instance, seems to have gotten no other coverage; or

* that other wedding slaughters haven't been recorded in languages I can't read; or

* that, in the rural Pashtun backlands, some U.S. attacks on wedding celebrants might not have made it into news reports anywhere.

In fact, no one knows how many weddings — rare celebratory moments in an Afghan world that, for three decades, has had little to celebrate — have been taken out by U.S. planes or raids, or a combination of the two.

Turning the Page on the Past

After the Obama administration took office and the new president doubled down the American bet on the Afghan War, there was a certain amount of anxious chatter in the punditocracy (and even in the military) about Afghanistan being "the graveyard of empires." Of course, no one in Washington was going to admit that the U.S. is just such an empire, only that we may suffer the fate of empires past.

When it comes to wedding parties, though, there turn out to be some similarities to the empire under the last Afghan gravestone. The Soviet Union was, of course, defeated in Afghanistan by some of the very jihadists the U.S. is now fighting, thanks to generous support from the CIA, the Saudis, and Pakistan's intelligence services. It withdrew from that country in defeat in 1989, and went over its own cliff in 1991. As it happens, the Russians, too, evidently made it a habit to knock off Afghan wedding parties, though we have no tally of how many or how regularly.

Reviewing a book on the Soviet-Afghan War for the Washington Monthly, Christian Caryl wrote recently:

"One Soviet soldier recalls an instance in 1987 when his unit opened fire on what they took to be a 'mujaheddin caravan.' The Russians soon discovered that they had slaughtered a roving wedding party on its way from one village to another — a blunder that soon, all too predictably, inspired a series of revenge attacks on the Red Army troops in the area. This undoubtedly sounds wearily familiar to U.S. and NATO planners (and Afghan government officials) struggling to contain the effects from the 'collateral damage' that is often cited today as one of the major sources of the West's political problems in the country."

And, by the way, don't get me started on that gloomy companion rite to the wedding celebration: the funeral. Even I haven't been counting those, but that doesn't mean the U.S. and its allies haven't been knocking off funeral parties in Afghanistan (and recently, via a CIA drone aircraft, in Pakistan as well).

Following almost two weeks in which the U.S. (and global) media went berserk over the death of one man, in which NBC, for instance, devoted all but about five minutes of one of its prime-time half-hour news broadcasts to nothing — and I mean nothing — but the death of Michael Jackson, in which the President of the United States sent a condolence letter to the Jackson family (and was faulted for not having moved more quickly), in which 1.6 million people registered for a chance to get one of 17,500 free tickets to his memorial service... well, why go on? Unless you've been competing in isolation in the next round of Survivor, or are somehow without a TV, or possibly any modern means of communication, you simply can't avoid knowing the rest.

You'd have to make a desperate effort not to know that Michael Jackson (until recently excoriated by the media) had died, and you'd have to make a similarly desperate effort to know that we've knocked off one wedding party after another these last years in Afghanistan. One of these deaths — Jackson's — really has little to do with us; the others are, or should be, our responsibility, part of an endless war the American people have either supported or not stopped from continuing. And yet one is a screaming global headline; the others go unnoticed.

You'd think there might, in fact, be room for a small headline somewhere. Didn't those brides, grooms, relatives, and revelers deserve at least one modest, collective corner of some front-page or a story on some prime-time news show in return for their needless suffering? You'd think that some president or high official in Washington might have sent a note of condolence to someone, that there might have been a rising tide of criticism about the slow response here in expressing regrets to the families of Afghans who died under our bombs and missiles.