Isn’t It Time to Land?
by Stephen Cox | Posted July 20, 2013
This is why some people regard Word Watch as a theater of cruelty. I am about to attack the verbal antics of a spokesman for the San Francisco fire department, which was responsible for rescuing many of the people who survived the wreck of the Korean airliner at San Francisco on July 6.
People often say that catastrophes bring out the best in people. I say that they bring out the worst, verbally. The lead bureaucrat in the government investigation of the plane crash, Deborah Hersman, immediately emerged as one of the biggest blowhards in the nation, jumping into interviews and news conferences in which she announced, at length, that she had no conclusions to offer. This did not prevent her from delivering lectures about the wondrous complexity and significance of the impending inquiry, about the tremendous workload of her agency . . . you get the picture.
What can such an expression mean? Has an army of goons been deployed in this country to maim or kill any advocate of safety?
She filled out some of the borders when she commented, a few days later, on the idiotic decision of the flight crew not to allow an evacuation of the plane until they were assured by an upstart flight attendant that the thing was actually, positively on fire. (And what else do you expect planes to be, after they’ve crashed?)
When asked if it was unusual that the crew wouldn’t announce the order to evacuate, Hersman said the pilots might not have been aware of the damage in the cabin.
"We don't know what the pilots were thinking, but I can tell you, in previous accidents there have been crews that don't evacuate," she said. "They wait for other vehicles to come to get the passengers out safely. Certainly if there's an awareness that there's a fire aboard the aircraft, that is a very serious issue. There was a fire, and then the evacuation began."
"Hindsight is 20/20," she continued. "We all have a perspective that's different than the people involved in this. We need to understand what they were thinking, what their procedures are, whether they complied with these, whether that evacuation proceeded in a timely manner" (Los Angeles Times,July 10).
Blah, blah, blah. Here’s a person who can fill any number of columns, yapping about what she doesn’t know. And by the way, Ms. Hersman, if you don’t know what the pilots were thinking, go ask them. You’re the “National Transportation Safety Board Chairwoman.” But also by the way, the plane had crashed. Its landing gear had been ripped off. Its tail was missing. Miraculously, it had come to rest on a dry, flat piece of land. Who cares what the pilots “were thinking”? They should have been evacuating the passengers. Right away.
In some circles, the bloviating Ms. Hersman is known as “a fearless advocate of safety.” Tell me: what can such an expression mean? Has an army of goons been deployed in this country to maim or kill any advocate of safety? If so, I also bid the goons defiance. Fearlessly I declare: I advocate safety!
Now we return to the scene of the accident, maybe three minutes after the crash. Flames are spurting from the airplane; fire engines are arriving; passengers, thank God, have taken it into their heads to evacuate. And, very unfortunately, one of them, a teenage girl, has been killed, apparently by a fire engine on its way to the wreck. Certainly, no one was trying to run her over. All was confusion: a giant machine, smashed to the ground, leaking fuel and shooting flames; hundreds of passengers, still alive but in desperate need of medical assistance; rescue vehicles racing from every direction. I feel sorry for whatever would-be rescuer ran down the young woman, if the coroner’s office is right in thinking that’s what occurred. But I hope that he or she feels no guilt. The driver was not responsible. The woman died. It was no one’s fault.
But about 36 hours later, along comes Dale Carnes, the aforementioned spokesman for the San Francisco fire department, to explain what happened:
Approximately half to two-thirds of the way through the incident as we were transitioning from the fire attack and rescue phase into both overhauling the fire in the aircraft and starting to concentrate on the three-minute transport of patients it became aware to one of our fire attack battalion chiefs that there was a possibility that one of their two fatalities might have been contacted by one of our apparatus at an unknown point during the incident.
Could anyone have constructed a more gruesome pile of words? And the guy wasn’t stumbling along; he was proceeding calmly and confidently, as if he had rehearsed those very phrases. That’s the horrible thing. People learn — they are trained — to communicate in that way.
Suppose that you didn’t know, more or less, what had happened. Would you ever have guessed what that 79-word sentence was about?
Let’s take it in order.
- “Approximately.” One rule of bad wording is never to use a short word (“about”) when you can use a long one (“approximately”).
- “Incident” (note that this word is repeated). Disasters become incidents when someone with an official position changes the focus from something that went wrong to something that just, you know, happened.
- “Transitioning,” used instead of the common “going from” or “changing from.” Always be long; always be Latinate; always be pseudo-technical.
- “Fire attack and rescue phase,” used instead of “fighting the fire and rescuing people.” An assertion of professionalism is always more important than saying what happened so that other people can understand it.
- “The three-minute transport of patients.” You don’t know what that is? Too bad for you. Does it mean they’re supposed to be picked up in three minutes, or delivered somewhere in three minutes? And where are they being delivered? To a hospital, or to some memory hole where they can lie in peace, next to the English language?
- “It became aware.” Did the spokesman ever read a word of English? I mean, actual writing in English? Did he ever notice that, in written English, things (“it”) cannot become aware? But actually, they can’t become aware in spoken English, either. Because they’re things, that’s all. Nevertheless, “it became aware” is growing on us. Watch for it. Try to avert it.
- “There was a possibility.” Observe how the distant past is creeping up on us here. There may possibly have been another incident at some “unknown point during the incident,” but the only way it’s becoming aware to us is that, we are told, some unnamed official detected the “possibility” at some other point, after the incident within the incident.
- “One of their two fatalities might have been contacted by one of our apparatus.” In published redactions of these remarks, “their” is often rendered as “the.” In video versions, it’s “their.” So the speaker lost control of his referent. But he remained very much in control of his theme, which was that nothinghappened. Well, nothing much. It was an incident. With some other incidents attached. There were two fatalities. (Nobody died; that would be going too far.) “Contacted,” of course, means run over. If you’re like me, you would rather be contacted by an apparatus than run over by a fire engine. I dunno; maybe it’s just a subjective preference, but that’s the way I feel. I’ve been contacted by many apparatuses in my time, and suffered no harm. But now the fire department informs me that a fatality might have been contacted by an apparatus. Picture that, if you can. Evidently, however, that is what the fire department does not want you to do. Otherwise its spokesman would say that “a person who had escaped from the burning airplane may accidentally have been killed by a fire engine.”
Like much bureaucratic talk, the language I’ve been analyzing is not only absurd and arrogant, and offensive to normal human feeling; it is also false to the conditions of normal human life. The horror of a young person who escaped from one disaster only to be overwhelmed by another — that is matter for profound reflection, because it exemplifies conditions that are, regrettably, not abnormal at all. The horror of a driver who, with the best intentions, is speeding to the scene of an accident and who accidentally destroys the life of another person on the way — if that’s what happened, it’s a matter for the deepest human sympathy. The bureaucratic “language” panders to whatever inclination the audience may have to ignore the facts and the problems and proceed as if all of it had, in fact, been explained, or at least officially encapsulated. Move along; there’s nothing to see here.
Another bad thing — I was going to say the worst thing — about this kind of talk is that it’s not even naturally produced. No one just pops out with “overhauling” as a synonym for “putting down,” or “apparatus” as a synonym for “fire engine,” or “at an unknown point during the incident” as a synonym for “at some time.” Granted, “it became aware” is simple ignorance, but why should people ignorant of words be chosen to speak for official agencies? Presumably because they can be trained in jargon. I wonder how much tax money is spent on this enterprise alone.
Disasters become incidents when someone with an official position changes the focus from something that went wrong to something that just, you know, happened.
You might, however, bring up another sense of the word natural. You might suggest that bureaucracies naturally resort to obfuscation, because they want to protect themselves. You might suggest that because they are collective and usually collectivist organizations, they often try to protect themselves in silly ways. There can be no check on silliness when no one in the org wants to stand out against the mob of “colleagues” and say, “This makes no sense.” If you reasoned in that way, I think you would be right. You would have identified one reason why nonsensical language is flooding our bureaucratized society.
But now for something completely different. Here’s what was posted on the Facebook page of Egypt’s Supreme Council of the Armed Forces, just before the army conducted its coup: "We swear to God that we will sacrifice even our blood for Egypt and its people, to defend them against any terrorist, radical or fool.”
I’m stating no view about the coup itself. It’s really none of my business. But I like the statement. It’s short; it’s serious; and it uses words that actually mean something. It doesn’t call terrorism “workplace violence.” And it ends with the word fool. This is an expression that is seriously underused in American society and especially in American formal language. The Bible doesn’t mind calling people fools; the word appears, with its various derivations, about 100 times in the King James Version. “Fool” runs back through Old French and Latin into the original Indo-European, which apparently used it in the sense of “windbag.” In English, it eventually came to be used for people with more serious impairments, although it’s hard for me to think of any impairment that is worse than being a windbag — if only because, in our bureaucratized society, people are actually rewarded for being that way. And now, the curtain of psychological correctness has descended. “Idiot,” “moron,” and “imbecile” are out, not just as pseudo-clinical terms, but also as terms of social analysis. And so is “fool.”
I think it needs to be restored — as a term of analysis, not just of abuse. Some people are mistaken. Fine. Other people are fools. It’s a distinct species, requiring identification and understanding. Words are the tools of understanding. As the Egyptian generals maintain, someone’s folly, once identified and understood, can become a reason for taking action, in a way that someone’s mere mistakenness may not be. It is a sad day when America’s terms of analysis are less useful than Egypt’s.
Stephen Cox is editor of Liberty, and a professor of literature at the University of California San Diego. His recent books include The Big House: Image and Reality of the American Prison and American Christianity: The Continuing Revolution.
- November 2010 (24)
- December 2010 (24)
- January 2011 (31)
- February 2011 (17)
- March 2011 (29)
- April 2011 (21)
- May 2011 (22)
- June 2011 (18)
- July 2011 (20)
- August 2011 (20)
- September 2011 (19)
- October 2011 (18)
- November 2011 (17)
- December 2011 (15)
- January 2012 (21)
- February 2012 (15)
- March 2012 (18)
- April 2012 (16)
- May 2012 (20)
- June 2012 (14)
- July 2012 (24)
- August 2012 (20)
- September 2012 (19)
- October 2012 (19)
- November 2012 (21)
- December 2012 (17)
- January 2013 (21)
- February 2013 (16)
- March 2013 (13)
- April 2013 (16)
- May 2013 (12)
- June 2013 (15)
- July 2013 (13)
- August 2013 (13)
- September 2013 (12)
- October 2013 (15)
- November 2013 (13)
- December 2013 (13)
- January 2014 (15)
- February 2014 (13)
- March 2014 (14)
- April 2014 (13)
- May 2014 (13)
- June 2014 (10)
- July 2014 (12)
- August 2014 (14)
- September 2014 (1)