Like many people (including my Atlantic colleague Jim Fallows), when I first heard about Northwest Airlines Flight 188 going radio silent for 75 minutes and overshooting its destination by 150 miles in October, I figured the pilots must have fallen asleep. As a pilot myself, I could think of no other conceivable reason for such a jaw-dropping lapse in pilot performance. And like Fallows, I, too, reacted with disbelief when the pilots said they had simply been too absorbed with company scheduling issues on their laptop computers. For over an hour?? With absolutely zero thought to where the heck are we??
In subsequent conversations with airline pilots I know, I discovered that to those who fly the line, it's not inconceivable. Just appalling. Suffice it to say that there are apparently a few other pilots out there whose sense of professionalism is noticeably and irritatingly lacking. And while pilots usually try to cut each other a little slack, especially from critiques outside the industry, I've only received one email from an airline pilot defending the actions of the Northwest crew. The rest ran along the lines of "they should be stripped of their ratings and pensions and never be allowed to fly an airplane again. Period."
The FAA agreed, revoking the pilots' certificates within days of the event. The reason all this is noteworthy again is that the pilots are currently in the process of appealing those revocations. And in statements to the FAA released Monday, they tried to shift the blame onto the air traffic controllers who failed to get in touch with them, saying that failures by the air traffic controllers that were "a causal or contributing factor in the incident."
I'm not sure which is more outrageous, actually. To get so engrossed in your personal priorities that you don't bother to ask, "gee, why is Center not calling us," or glance at any of the navigation screens that show you fast approaching your destination, or notice any of the eight separate text messages your own dispatchers have sent you, accompanied by warning lights ... in short, to not think for even one minute about actually flying the airplane ... or to try to blame it on controllers who didn't manage to yell at you loudly enough to get your distracted attention.
It is drilled into every pilot, from the earliest days of their flight training, that the pilot in command is just that: the person who holds final responsibility and accountability for the safe outcome of every flight. If you're flying in busy airspace, in clouds, or at altitudes where the airlines cruise, there are rules that say you have to be in contact with controllers and on a flight plan, at all times. If a controller says you need to do something, in most cases, you should do it. But the pilot retains final responsibility and say over the operation of the aircraft--as it should be. After all, as pilots are fond of saying, the furthest a controller can fall is the 18 inches from their chair to the floor.
If a pilot doesn't feel they can safely execute a controller's request, the simple response "unable" trumps the controller's direction. If worse comes to worst, a pilot can simply declare an emergency and do whatever is necessary to save the airplane and sort the details out on the ground. So blaming the controllers for not doing a better job at getting you to do your job is an even flimsier excuse than saying "the dog ate my homework" or "Johnny made me do it."
Controllers can make mistakes, of course, and from reading the transcripts of the air traffic control communications related to that flight, it seems as if there might have been room for improvement. Not in getting the attention of the Northwest pilots (one controller tried to contact the pilots more than a dozen times), but in realizing that a potentially serious situation, with potentially serious security concerns, was unfolding before them.
In the years since the attacks of 9/11, any number of small airplane pilots who strayed out of approved flight paths or airspace have found themselves eye to eye with pilots in military aircraft and helicopters, signaling stern orders to follow them to an airport and land NOW. This, mind you, for little training aircraft that weigh less than a Honda Civic and could probably do less damage. Yet an airliner with the fuel and mass to really do damage goes radio silent for over an hour, and cruises right past its destination, and nobody moved to intercept it--at least in part because controllers were slow to process what was going on and notify the appropriate agencies.
A mismanaged shift change in Denver may account for some of the delay. And in all fairness, the controllers after that assumed a benign explanation: that the flight had simply lost its radios and was unable to talk to anyone. So they treated it as such. And that kind of thing does happen. But the transcripts also show confusion among controllers about what was really going on and what to do about it. The same kind of confusion that the transcripts of controllers on 9/11 showed. Where are they? Are you talking to them? Can you get someone to try to reach them? Did someone call their company dispatchers?
Of course, the airliner had not departed from its flight path, or shown erratic behavior that would have raised more alarm. And enough little glitches happen in air traffic control communications that controllers are not trigger-loaded to ring alarm bells at the first sign of something amiss. But, still. The Commander of the North American Aerospace Defense Command is not pleased.
It's been said that the attacks of 9/11 succeeded due to a lack of imagination on our part. We simply couldn't conceive of hijackers using box cutters to take over airplanes and fly them into buildings. And perhaps the controllers working with Flight 188 had, thankfully, gotten so used to safe skies again that they assumed a lack of contact from an airliner meant an inoperable radio rather than imagining something more serious.
So I hope controllers are getting a refresher course on the importance of better coordination, keeping alert for anomalies, and and questioning all the possible reasons a problem might be occurring. But for the Northwest crew to blame the controllers for not preventing their own transgressions is, as Jim Fallows said of the transgressions themselves, beyond the pale.
I'm guessing that the pilots are following the advice of their lawyers, who are trying to find any and all angles out of a thin list of possibilities that might get their clients off the hook. But ever since the first officer confidently told the press that the passengers were in no danger at any time, the crew has shown an appalling lack of awareness of just how egregious their sins were. What if the flight had been intercepted, as it perhaps should have been? Not to mention multiple other hazards that come with having a flight crew so detached from what's going on in the cockpit.
Perhaps it's asking too much to expect pilots who thought so little of their professional responsibilities in the first place to step up and take professional, mature responsibility for their failures. And the idea of minimizing their professional and legal exposure and cost is surely a tempting one. But redemption doesn't come as easily as a legal victory. And it surely doesn't come from blaming someone else for your own mistakes.
The social network learns more about its users than they might realize.
Facebook, you may have noticed, turned into a rainbow-drenched spectacle following the Supreme Court’s decision Friday that same-sex marriage is a Constitutional right.
By overlaying their profile photos with a rainbow filter, Facebook users began celebrating in a way we haven't seen since March 2013, when 3 million peoplechanged their profile images to a red equals sign—the logo of the Human Rights Campaign—as a way to support marriage equality. This time, Facebook provided a simple way to turn profile photos rainbow-colored. More than 1 million people changed their profile in the first few hours, according to the Facebook spokesperson William Nevius, and the number continues to grow.
“This is probably a Facebook experiment!” joked the MIT network scientist Cesar Hidalgo on Facebook yesterday. “This is one Facebook study I want to be included in!” wrote Stacy Blasiola, a communications Ph.D. candidate at the University of Illinois, when she changed her profile.
The second episode of the new season was a slow burner with a dramatic twist.
Let’s start at the beginning, with Frank in bed with his wife, Jordan, discussing water stains on the ceiling and childhood entombments. I don’t know about you guys, but I found this whole bit slack and familiar. Maybe there was a two-minute scene in there, but five? Maybe a more charismatic actor could have pulled off that lengthy monologue. But Vince Vaughn is no Robert Shaw, and his childhood basement is no U.S.S. Indianapolis.
The Islamic State is no mere collection of psychopaths. It is a religious group with carefully considered beliefs, among them that it is a key agent of the coming apocalypse. Here’s what that means for its strategy—and for how to stop it.
What is the Islamic State?
Where did it come from, and what are its intentions? The simplicity of these questions can be deceiving, and few Western leaders seem to know the answers. In December, The New York Times published confidential comments by Major General Michael K. Nagata, the Special Operations commander for the United States in the Middle East, admitting that he had hardly begun figuring out the Islamic State’s appeal. “We have not defeated the idea,” he said. “We do not even understand the idea.” In the past year, President Obama has referred to the Islamic State, variously, as “not Islamic” and as al-Qaeda’s “jayvee team,” statements that reflected confusion about the group, and may have contributed to significant strategic errors.
Over the last two weeks, Republican presidential candidates have repeatedly missed opportunities to demonstrate that they care about communities outside of their traditional base.
After Mitt Romney’s defeat in 2012, the Republican National Committee published an “autopsy.” “When it comes to social issues,” the autopsy declared, “the Party must in fact and deed be inclusive and welcoming. If we are not, we will limit our ability to attract young people.” The autopsy also added that, “we need to go to communities where Republicans do not normally go to listen and make our case. We need to campaign among Hispanic, black, Asian, and gay Americans and demonstrate we care about them, too.”
The last two weeks, more than any since Romney’s defeat, illustrate how miserably the GOP has failed.
Start with June 17, when Dylann Roof, a young white man enamored of the Confederate flag, murdered nine African Americans in church. Within three days, Romney had called for the Confederate flag’s removal from South Carolina’s capitol. Four days later, the state’s Republican governor and senators called for its removal too. But during that entire week—even as it became obvious that the politics of the flag were shifting—not a single GOP presidential candidate forthrightly called for it to be taken down. Instead, they mostly called it a state decision, a transparent dodge politicians deploy when they don’t want to make a difficult call.
The historian and Knesset member Michael Oren accuses the president of distancing the U.S. from Israel, and calls out left-wing Jews and Israel’s Jewish critics in the American press.
In a recent post, I suggested that the intervention of two men, the former U.S. national security advisor Tom Donilon and the former Israeli ambassador to the United States, Michael Oren, might help improve the dysfunctional relationship between the Obama administration and the government of Israeli Prime Minister Benjamin Netanyahu.
At the time I wrote this, both men had reputations as people who were concerned about preserving the extraordinarily complicated, and extraordinarily close, U.S.-Israel relationship, and both had spent a good deal of time calming the waters between Obama and Netanyahu. Today, Donilon maintains that reputation. As for Oren …
Put it this way: If Goldblog readers would allow me to withdraw the suggestion, I’d be much obliged. Oren has created a new role for himself: acid critic of the Obama administration and of left-leaning American Jews (especially in the press and in the White House) who, he believes, are trading on their Jewishness when they criticize Israel. Oren’s critique, at its heart, is simple: Obama, in part because he wanted to reconcile the U.S. with the “Muslim world” (a very large, ill-defined, and politically complicated concept, in Oren’s mind), decided to distance the United States from Israel; to surprise Israel by altering U.S. Middle East policy without prior notice; and to negotiate with Israel’s most potent enemy without alerting Israeli leaders.
For centuries, experts have predicted that machines would make workers obsolete. That moment may finally be arriving. Could that be a good thing?
1. Youngstown, U.S.A.
The end of work is still just a futuristic concept for most of the United States, but it is something like a moment in history for Youngstown, Ohio, one its residents can cite with precision: September 19, 1977.
For much of the 20th century, Youngstown’s steel mills delivered such great prosperity that the city was a model of the American dream, boasting a median income and a homeownership rate that were among the nation’s highest. But as manufacturing shifted abroad after World War II, Youngstown steel suffered, and on that gray September afternoon in 1977, Youngstown Sheet and Tube announced the shuttering of its Campbell Works mill. Within five years, the city lost 50,000 jobs and $1.3 billion in manufacturing wages. The effect was so severe that a term was coined to describe the fallout: regional depression.
The president delivers his single most accomplished rhetorical performance, and it’s one you should watch rather than read.
I think Barack Obama’s eulogy yesterday for parishioners of the Emanuel African Methodist Episcopal Church in Charleston was his most fully successful performance as an orator. It was also one that could have come only at this point in his public career—and not, for instance, when he was an intriguing figure first coming to national notice, as he was during his celebrated debut speech at the Democratic National Convention in Boston 11 years ago; or when he was a candidate fighting for political survival, as he was when he gave his “Race in America” speech in Philadelphia early in 2008.
I’ll explain why I say so, but first a word about the odd circumstances in which I’ve heard and learned about the speech.
In 1784, the doctor Benjamin Rush described alcohol as a threat to morality—and a danger to the nascent republic.
Go ahead, have a small beer; it will bring “Serenity of Mind, Reputation, Long Life, & Happiness.” Even a strong beer would be fine, for that brings “Cheerfulness, Strength, and Nourishment,” as long as it’s only sipped at meals. So declared Benjamin Rush, one of the signers of the Declaration of Independence and the early republic’s most prominent physician. In his loquaciously named pamphlet, An Inquiry Into the Effects of Ardent Spirits on the Human Mind and Body, first published in 1784, Rush describes the “usual” downward spiral of drink. What starts as water and wine quickly turns into punches and toddies and cordials, ending with a hopeless vortex of gin, brandy, and rum, “day and night.”* In the pits of intemperance, one can expect such vices as “Idleness, Gaming, peevishness, quarrelling, Fighting, Horse-Racing, Lying and Swearing, Stealing and Swindling, Perjury, Burglary, [and] Murder,” with punishments including “Black eyes and Bags,” “State prison for Life,” or, worst of all, “Gallows.”**
The meaning of the Confederate flag is best discerned in the words of those who bore it.
This afternoon, in announcing her support for removing the Confederate flag from the capitol grounds, South Carolina Governor Nikki Haley asserted that killer Dylann Roof had “a sick and twisted view of the flag” which did not reflect “the people in our state who respect and in many ways revere it.” If the governor meant that very few of the flag’s supporters believe in mass murder, she is surely right. But on the question of whose view of the Confederate Flag is more twisted, she is almost certainly wrong.
Roof’s belief that black life had no purpose beyond subjugation is “sick and twisted” in the exact same manner as the beliefs of those who created the Confederate flag were “sick and twisted.” The Confederate flag is directly tied to the Confederate cause, and the Confederate cause was white supremacy. This claim is not the result of revisionism. It does not require reading between the lines. It is the plain meaning of the words of those who bore the Confederate flag across history. These words must never be forgotten. Over the next few months the word “heritage” will be repeatedly invoked. It would be derelict to not examine the exact contents of that heritage.
Twenty-five percent of Americans are spending more than half of their income just to keep a roof over their head.
If you’ve gone through the painstaking process of renting a new apartment in the past few years, you probably faced some sticker-shock. Vacancy rates are low, really low. And despite ever-present scaffolding, construction in many cities is still slow, as new tenants move in but few move out. The result is that in almost every major metro area, the rent is, in fact, too damn high.
Basic wisdom (which was largely established by rules governing public housing eligibility) warns a healthy bank account means that one’s housing costs shouldn’t exceed about one-third of a person’s take home pay. While that might be a prudent suggestion because, after all, people do have other bills and savings goals, it’s become virtually impossible to adhere to for many who live in major metro areas.