Problems of Knowing Thine Enemy

From What the Taliban Told Me, by Ian Fritz (Simon & Schuster, 2023), Kindle pp. 230-234:

No single individual is held responsible for the people that our planes kill. It’s a crew effort. There is no ammunition without a loadmaster to balance the plane; a FCO [Fire Control Officer] can’t fire that ammunition without gunners loading the weapons; the gunners won’t ready the weapons till the sensor operators find a bad guy; the sensor operators couldn’t find that bad guy without pilots flying the plane; the pilots couldn’t have flown the plane to the location where the sensors found that bad guy without a navigator guiding them across the country; the navigator couldn’t have safely gotten across that country without an EWO [Electronic Warfare Officer] making sure no one hit the plane with a rocket; the EWO couldn’t have used his equipment without a flight engineer making sure everything was in working order.

I didn’t mention the role of DSOs because DSOs, while nice to have around, are not remotely necessary for a C-130 to carry out its mission. And so, if I heard something that proved to be the key piece of information that resulted in us shooting, a piece of information, that, if lacking, would have prevented us from shooting, then didn’t I kill someone on my own? Conversely, if I didn’t hear anything that was related to why we shot, then did I kill anyone at all?

The problem with this argument is that according to my official records I have in fact killed 123 people. The actual wording is “123 insurgents EKIA” (EKIA = enemy killed in action, so not quite people, but definitely killed). These records don’t say that I was part of a crew that killed these people, or that I supported other people who did the killing, just that I killed those 123 humans. I can’t know, and will never know, if all of these kills belong to me. I do know, and will always know, that I belong to all of them.

...

These are the things I wish I hadn’t heard.

If I hadn’t heard those things, infinity would have remained, well, infinite. I would have been able to tell myself that the Taliban were not men, were not even human, that they were in fact Enemies, whose only purpose was to be Killed in Action. If I hadn’t heard those things, I wouldn’t have loved the men I was listening to. If I hadn’t loved them, killing them would have been easy. If killing them had been easy, my consciousness would have remained intact.

To say that I loved the Taliban is surely anathema to most anyone who reads this. It doesn’t feel good, or right, for me to say it. But I checked, and of the many definitions that exist for the word love, one of them is the following: “strong affection for another arising out of kinship or personal ties.” I most certainly had personal ties to the men I was listening to; they told me shit they wouldn’t tell their best (non-Talib) friends, their wives, their fathers. And at some point, not because they were Talibs, in fact in spite of that, because they were human, I came to have the strong affection for them that I firmly believe it is impossible not to develop for virtually any other person if you can get past your own bullshit and just accept that they’re people too.

Let me be clear about something here: I in no way support the Taliban, their stated goals, their practices, or really anything about them. Nor do I support the individual men who comprise the greater Taliban. Their movement and many of their beliefs are an affront to modernity in all of its complicated, messy, but ultimately better than the shit that actively and gleefully removes myriad human rights from everyone who isn’t a God-fearing man, splendor. They are not the good guys.

None of these things detract from the fact that they’re still human. They’re still people. I have no desire for you to identify with them or wish for their lives to be spared. What I do ask is that you understand that I did identify with them. I had to. My job required it. All that talking with my teachers in language school, so I could figure out how they think? That’s what made me a good linguist. The translation we did isn’t something that can be done by a computer or a robot, it isn’t the simple transformation of the sounds of one language into another. You have to understand the intent, the tone, the playfulness, the fear, the anger, the confusion, all of the nuances that attach themselves to spoken words and drastically change their meanings.

It was impossible for me to do this without internalizing the speakers’ logic (it’s possible for others, but I don’t understand that process). It was also impossible, despite all this knowing and feeling, for me to wish for their lives to have been spared. To have spared their lives would have been to guarantee that many others would have been taken.

Pashto Regionalects

From What the Taliban Told Me, by Ian Fritz (Simon & Schuster, 2023), Kindle pp. 161-162:

The Whiskeys [MC-130W] were becoming the new hotness. On my first deployment, we were usually just tasked to whichever flight didn’t conflict with our crew rest. Now, as more commanders became aware of the Whiskeys, and the presence of DSOs [Direct Support Officers] on the Whiskeys, we started being requested for specific missions. But there was no way we could fly on every mission that wanted us; there simply weren’t enough DSOs to go around.

As far as we could tell, the people requesting us had no idea that Pashto varies massively depending on where you are in Afghanistan. This was strange, or, really, plain ignorant, as anyone with a cursory knowledge of the language should know that at baseline it has two main dialects that pronounce entire letters differently. Hell, some of the people who speak it don’t even call it Pashto. They call it Pakhto. The second letter in the word پښتو, that little collection of three nubs with the one dot above it and one below it, ښ, can be pronounced as either a sh sound (though you have to curl your tongue to the top of your mouth to get the sh just right) or a kh sound (same tongue movement). There’s another letter that on one side of the country is pronounced as a g and on the other side as a zh. The “o” in Pashto isn’t always an o, sometimes it’s a u, as in Pashtu/Pakhtu.

And those are just the two major divisions, Western and Eastern Pashto/Pakhto/Pashtu/Pakhtu. Realistically there are dozens of dialects, some of which aren’t understood all that well even by native Pashto speakers. So, to expect us to be able to fly over bumfuck Khost and have any clue as to what the bad guys were saying was to have no idea of how the language worked. Which, I guess, we shouldn’t have been surprised by. Unrealistic expectations being the norm in Afghanistan.

Flying in places where we couldn’t understand anything that was being said was both a serious waste of us as a resource and, more importantly, at least to us, boring as fuck. Like anything that you do every day, even flying eventually loses its excitement. After enough missions, all you’re doing is sitting in a tiny chair for six or seven hours waiting for something to happen. The fact that you’re fifteen or twenty thousand feet in the air traveling at two hundred plus miles an hour falls by the wayside. Those hours are short if you’re busy listening to guys planning attacks or actually fighting. They’re a little longer if all you’re doing is listening to them bullshit. But those six or seven hours feel like an eternity if what you’re supposed to be listening to is utterly incomprehensible. What’s a DSO to do?

USAF DSO Job Description

From What the Taliban Told Me, by Ian Fritz (Simon & Schuster, 2023), Kindle pp. 2-4:

A DSO [Direct Support Operator] (pronounced “dizzo”) is just an airborne cryptologic linguist by another name. Historically, there weren’t very many DSOs, mostly because the Air Force didn’t want or need that many, and partly because DSOs like feeling special, so they artificially limited the number of spots available to other non-DSO linguists. And because there were so few DSOs, it was that much easier to craft an image as badass “operators,” the best of the best, the only people who could do what they do. This was plausible; there are those elite groups within the military who have been selected for their talent, grit, and exceptionalism. And, like those elite groups, if you pushed the DSOs on it, they would be able to credibly say that because their job was highly classified (true) they couldn’t tell you specifically what they did (untrue).

A DSO does what all airborne linguists do. They “translate intelligence communications or data received or intercepted while in the air,” aka listen to what the bad guys (usually) are saying in another language and turn it into English (that quote is from the USAF’s Quincy, Massachusetts, recruiter’s Facebook page). Most airborne linguists do this aboard a jumbo jet, the RC-135 Rivet Joint, or RJ, flying thirty thousand or so feet above the ground at four or five hundred miles an hour, in an orbit that encompasses a few hundred miles. This is strategic work; the communications they receive or interpret rarely have an immediate impact on something actively happening on the ground. But it is important, at least according to the military, as “a lot of the things we do might end up on the desk of the president” (ibid., and a little misleading, though technically not a lie if you note the usage of “might”).

The primary difference between these linguists and DSOs is one of location. DSOs don’t fly on RC-135s, or any similar massive aircraft. DSOs fly exclusively on the planes that are utilized by Air Force Special Operations Command, or AFSOC. For the most part, these are C-130s that have been modified for various purposes. Some of these, like the AC-130s, or gunships, have been changed so much from their original cargo-carrying mission as to be unrecognizable; the only cargo a gunship carries is bullets. Others, like the MC-130s, still can and do carry cargo, but they’ve been made to be better at doing it. [Later MC-130Ws, nicknamed Whiskeys, were modified to carry weapons.] AFSOC has other aircraft that DSOs are trained to fly on, but in my time in Afghanistan, we almost exclusively flew on C-130s.

Timing is the other thing that makes a DSO’s work different from that of other linguists. AFSOC doesn’t do strategic work all that often, and so neither do DSOs. In Afghanistan, our job was to “provide real-time threat warning” to the planes we were on and to the people on the ground that these planes were supporting. How we did this work is unimportant, and honestly quite boring.

I don’t know if they still think of themselves as badasses, but when I was a DSO, that was the ethos of the community. We (not all, but most of us) felt that we were the best of the best: better than other linguists, cooler than other linguists, more important than other linguists. Once upon a time, some of this may have been true. Long before I did it, in order to be a DSO you had to be very good at the language(s) you spoke, and you had to be handpicked by other DSOs, interviewed, and tested; it was a whole process. And there were those DSOs who flew scary, complex missions in dangerous places. But by 2010 the Air Force just randomly assigned new linguists to become DSOs, and the thing most likely to take down the aircraft a DSO was in was a drone (seriously, they have a bad habit of losing connection and orbiting at preselected altitudes that are, let’s say, inconvenient for other, human-containing aircraft).

The U.S. Air Force students in the Romanian-language class ahead of me at the Defense Language Institute in 1969-1970 were assigned to an airbase in Turkey, where they listened constantly to Romanian-language radio broadcasts and recorded any that contained reference to military assets or movements, which were then translated. The two other Army students, one in the class ahead of me and one in my class, were both assigned to Military Intelligence units. The one in my class went to Germany and did some undercover work. The only other person in my 3-person Romanian class was an FBI agent from Chicago who probably didn't get much more use out of his new language skills than I did as a company clerk in Ft. Gordon, Georgia.