Archive for category automation
More on the pilots who overshot MSP by 150 miles
Posted by jasonwong in automation on November 7th, 2009
NPR says: Expert: Wayward Flight Shows Risks Of Automation
As aviation consultant Michael Goldfarb tells NPR’s Renee Montagne, it’s still very safe to fly. The problem, he says, is that pilots are now more susceptible to boredom and fatigue.
“There’s so much automation in the cockpit that, literally, an aircraft taking off from Los Angeles and landing in New York can have very little attendance by the crew,” says Goldfarb, a former chief of staff at the Federal Aviation Administration.
In fact, there was a panel discussion at the recent 2009 Human Factors and Ergonomics Society annual meeting called “Current Concepts and Trends in Human-Automation Interaction.” What did Dietrich Manzey of the Berlin Institute of Technology speak on?
Automation-Induced Complacency: A Controversial Concept of Human-Automation Interaction
Complacency induced by automation, eh? Sounds… familiar.
Here is a copy of the conference proceedings paper for more information: Conference Proceedings
Human Factors in the News
Posted by jasonwong in attention, automation on October 23rd, 2009
The Human Factors and Ergonomics Society conference took place this past week in San Antonio, TX. I saw a lot of interesting talks that are relevant to my work with the Navy, and I got to see a lot of friends from my previous life as an undergrad at the University of Illinois and grad student at George Mason University.
I am honestly amazed, however, that this story happened during the Human Factors conference:
Pilots missed Twin Cities by 150 miles – but how?
WASHINGTON — Were the pilots distracted? Catching up on their sleep? Federal investigators struggled to determine what the crew members of a Northwest Airlines jetliner were doing at 37,000 feet as they sped 150 miles past their Minneapolis destination and military jets readied to chase them. Unfortunately, the cockpit voice recorder may not tell the tale.
A report released late Friday said the pilots passed breathalyzer tests and were apologetic after Wednesday night’s amazing odyssey. They said they had been having a heated discussion about airline policy. But aviation safety experts and other pilots were frankly skeptical they could have become so consumed with shop talk that they forgot to land an airplane carrying 144 passengers.
They did not respond to communications from air traffic control, they missed every alert the flight management system threw at them… who knows what else they missed? Was it a case of pilot fatigue? Inattentiveness due to a heated discussion?
And if it WAS all due to a heated discussion, what does that mean for us drivers? No more passengers in the car? If you get into an argument or too involved in a conversation that you have to pull over?
Insanity! It seemed like everyone was talking about this story. At least you had 1000+ human factors professionals on the case!
Aeroflot and its drunken pilot get too reliant on automation
Posted by jasonwong in automation on February 8th, 2009
Sometimes people get over-reliant on automation. From a USA Today blog post that summarized many good articles about the incident (emphasized text mine):
London’s Daily Mail writes “Captain Alexander Cheplevsky sparked panic as Aeroflot flight 315 from Moscow to New York was about to take off. He started his pre-flight ‘welcome aboard’ message in Russian that was barely intelligible, then switched to English that was even worse.”
“The first thought that occurred to me was, ‘This guy is drunk,’ ” Flight 315 passenger Khatuna Kobiashvili tells The Moscow Times. “His speech was so slurred it was hard to tell what language he was speaking.” The Moscow Times adds that “as passengers, including a Moscow Times reporter, related their concerns to the flight crew, they were told to ’stop making trouble’ or get off the Boeing 767 jet.
But passengers apparently weren’t going to take “no” for an answer, according to the Times of London. The paper writes “as the rebellion spread, Aeroflot representatives boarded the aircraft to try to calm down the 300 passengers. One sought to reassure them by announcing that it was ‘not such a big deal’ if the pilot was drunk because the aircraft practically flew itself.”
The plane practically flew itself. Thank goodness for automation – now our pilots can get drunk without any concern whatsoever!
The entire article is truly bizarre and definitely worth a read. But from a human factors standpoint, we need to think about how our designs, typically thought of to make life easier and/or safer, may be used for purposes that are less…. noble.
Robo-ethics and Levels of Automation
Posted by jasonwong in automation on November 29th, 2008
Let me start out with a quote from a New York Times article on Ethical Killing Machines:
… a 2006 survey by the surgeon general of the Army, which found that fewer than half of soldiers and marines serving in Iraq said that noncombatants should be treated with dignity and respect, and 17 percent said all civilians should be treated as insurgents. More than one-third said torture was acceptable under some conditions, and fewer than half said they would report a colleague for unethical battlefield behavior.
Those statistics are… disheartening to say the least. While a majority of soldiers are good people I’m sure, the bad apples are the ones that get the bad press (Gitmo, anyone?). The ethics of our soldiers are certainly not under the control of anyone but the soldiers themselves. That’s pretty worrisome.
One solution, of course, are robots. As the military moves closer towards autonomous robots that do all the fighting for us, some are asking the question of whether we can build ethics into robots (which is the topic of the New York Times article quoted from above. Anyone who has read “I, Robot” and is familiar with the three laws of robotics may get worried about the idea of robots with ethics.

Some may frown at the flexible ethics of some soldiers and demand robots who cannot break their ethics codes. I think a greater number of people will be worried about robots with their own code of ethics, and would rather not see robots given such autonomy at all. However, this is a question that must be asked. It’s only logical that we end up building robots that can fire on enemy soldiers, tanks, or buildings. The order to fire can be left up to a soldier at some distant command center, but those decisions take time and someone who is not directly in the situation may not have full situational awareness. It may be a better solution to let the robot make the decision.
Anyone who has taken an ethics class knows that there are no black and white areas, and anyone who has taken a computer science class knows that computers are bad at gray areas. This seems to be an issue of Levels of Automation, which is a huge area of research aimed at determining how much responsibility to give to a human and how much to a robot.
If the robot does everything and a human just has to press Yes all the time, the job gets boring and the human doesn’t pay attention. However, if the human has to do a majority of the work, why bother with a robot at all? This is a vast field of research, with an abundance of experimentation and case studies to draw from. Thankfully, while some roboticists and ethicists work on installing an ethics module into automated robots, most people will require some human in the loop and somehow responsible for who lives and dies. This requires the knowledge of a human factors specialist, and it is comforting to know that ergonomists will be on the forefront of determining how soldiers interact with these automated killing machines.
GPS devices, automation, and creepy men with chainsaws
Posted by jasonwong in automation, driving, thoughts on June 2nd, 2008
I have been totally reliant on my GPS since I got to Rhode Island, and it has been mostly reliable. There have been a couple of errors, but nothing too drastic. Coming back from nearby Whole Foods last night, however, nearly gave me a panic attack. The route given to me by my GPS took me through a dark industrial park, past dimly lit residential areas, a giant warehouse with big loading docks, and a construction zone with a recently leveled building.
Did the GPS get me home? Yes. Did it take the shortest route? Yes. Did I have no choice but to fully trust the automation and hope that I wouldn’t encounter creepy men with chainsaws? Yes.
Automation is a wonderful thing, but it is distressing to be at the mercy of a machine. Yet, in many ideal futures, our cars drive for us so we don’t have to do any work. Except worry about creepy man with chainsaws.
Thankfully, there has been a lot of research on automation in the human factors literature. Much of the research examines how humans trust automation and how automation use changes after a failure. One of the better review articles is:
Parasuraman, R. & Riley, V. (1997). Humans and Automation: Use, Misuse, Disuse, Abuse. Human Factors, 39(2), 230-253. (link)