The AirSafe.com News

↑ Grab this Headline Animator

Showing posts with label overflight. Show all posts
Showing posts with label overflight. Show all posts

19 June 2010

Mapping the intersection of mind and computer in the cockpit

The following is based on the article Mapping the intersection of mind and computer from guest writer Christine Negroni


Well my inbox is filling up again with emails, as it did last month when I reported the following story for The New York Times on pilot complacency and cockpit automation.

Prompting the latest flurry of comments is a June 15, 2010 article by Andy Pasztor and Daniel Michaels in the Wall Street Journal about the crash in May 2010 crash of an Afriqiyah Airways A330. Only one of the 104 people on the Airbus A330 from Johannesburg to Tripoli survived the accident.

According to Pasztor and Michaels the landing accident is being seen as one in “which confused pilots got out of sync with the plane's computerized controls and ended up flying an apparently functioning commercial jet into the ground.”

This is no one-off event. A number of studies over the past 15 years indicate pilots fail to adequately monitor what the airplane is doing in one-half to three-quarters of all accidents. So in the wake of the Afriqiyah Airways disaster, what’s the big idea being proposed? More automation. That’s right, Airbus is said to be working to “devise foolproof automated ground-collision avoidance systems” that in cases of emergency transfer control from the pilots to the airplane.

“This is very disturbing”, wrote Hugh Schoelzel, a retired captain who worked as director of safety for TWA. “The more automation we add, the more training and pilot qualification issues arise. I believe in automation, but as an adjunct to basic pilot skills, not as an ‘end-all’.”

While automation may be causing a decrease in piloting skills as Mr. Schoelzel suggests, Professor Missy Cummings of the Massachusetts Institute of Technology says there is another reason to be concerned about cockpit automation; boredom.

Dr. Cummings a former Navy pilot, is director of the humans and automation laboratory at MIT’s department of Aeronautics and Astronautics. Not surprisingly she is a proponent of automation and envisions a future that will include at least some pilotless commercial flights. But first some extremely troublesome problems have to be wrestled to the ground, problems demonstrated by one of Dr. Cummings students, Master’s degree candidate First Lt. Christin S. Hart, who has found that too much automation can prove counter-productive.

“Increased automation can lower an operator’s workload too much, leading to mental underload, which can cause a decrement in vigilance, or sustained alertness, and lead to boredom. It has been shown that boredom produces negative effects on morale, performance, and quality of work,” she wrote in her paper, Assessing the Impact of Low Workload in Supervisory Control of Networked Unmanned Vehicles.

These findings do not surprise Dr. Cummings “The human mind craves stimulation”, she explained to me last week during a visit to her office in Cambridge. Failing to find that stimulation in the task at hand, the mind will wander.

This cuts to the heart of a number of events outlined by industry researchers but takes us at warp speed to the episode last October in which two Northwest Airlines pilots overflew their destination - the Minneapolis airport. The Northwest pilots were doing personal work on their laptops which is not allowed.

“It doesn’t have anything to do with automation,” FAA Administrator Randy Babbitt told me. “Any opportunity for distraction doesn’t have any business in the cockpit. Your focus should be on flying the airplane.”

But if I’m reading Lt. Hart’s study properly, the automation itself is an opportunity for distraction, even as it assists pilots by reducing workload and increasing the precision of calculations and navigation.

This is a conundrum. In today’s cockpit, two highly complex systems – the mind and the computer – come together, even though the contours of that intersection are still being mapped. It is not only unwise to race to a fix that fails appreciate these systems in balance, but it is unlikely to result in success.

Related Content
NTSB opens public docket on Northwest overflight

16 December 2009

NTSB to Open Up Public Docket on Northwest Airlines A320 Overflight in October 2009

Detailed information from the NTSB investigation into the October 21, 2009 incident involving the distracted Northwest Airlines pilots have been released to the public. The incident, which resulted in a large amount of media attention, occurred when the pilots of Northwest Airlines flight 188 was out of contact with air traffic control for about for 77 minutes while cruising from San Diego to Minneapolis.

The Airbus A320 (N03274) overflew Minneapolis by more than 100 miles before re-establishing radio contact with air traffic controllers and landing at the destination airport. There were no injuries to the 149 aircraft occupants, or damage to the aircraft.

Overview of Final Stages of the Flight


Reportedly, one of the reasons why the pilots did not respond to radio calls was because they were using their laptop computers in the cockpit and were distracted. While using laptops in the cockpit is allowed by the FAA, use of personal computers in the cockpit was not allowed by Delta (which owns Northwest). Both pilots were dismissed by the airline, and the FAA revoked their licenses.

Included in the docket will be factual reports from several of the NTSB-led groups involved in the investigation, including the Operations Group, Air Traffic Control Group, Survival Factors Group, Cockpit Voice Recorder Group and Flight Data Recorder Group. The docket will be available on Wednesday morning, December 16th. To view the contents of the docket, visit the the public docket page for this incident.

Related Information
Northwest Flight 188 public docket page
Previous AirSafeNews.com Incident Update
Original AirSafeNews.com article on this incident
Delta Airlines Statement 26 October 2009
FAA air traffic control transcripts and audio recordings
NTSB Update from 26 October 2009

25 October 2009

Podcast About the Recent Northwest Airlines A320 Overflight Event and the Delta 767 Landing Incident

The latest episode of the Conversation at AirSafe.com reviews two events from the week of October 19, 2009 that could have become major airline disasters. In Atlanta, a 767 landed on the taxiway instead of the runway, and in Minneapolis an airline crew stopped communicating with the outside world for over an hour while flying past its destination by well over 100 miles.

More detailed descriptions of these two incidents are in the AirSafeNews.com article from 23 October 2009. The podcast that is based on this article, which you will find below, is a bit unusual. Previous episodes of the Conversation at AirSafe.com were hosted by Dr. Todd Curtis. This show features a computer-generated narrator. We ask you to listen to the show and tell us what you think about this narrator.

Northwest Airlines A320 Overflies Airport and Delta 767 Lands on Taxiway by Mistake (4:37)

Evaluation of Text-to-Speech Narration
AirSafeNews.com conducted a survey of this narration by computer generated voice, and you can see the results of the survey in an article published on 30 October 2009.

23 October 2009

Two Recent Scary Incidents: Northwest Airlines A320 Overflies Airport and Delta 767 Lands on Taxiway by Mistake

This has been an unusual week with two airliner incidents which did not result in any injuries or damage, but which had the potential to become catastrophic plane crashes.

Airliner Lands on Taxiway Instead of Runway
On 19 October 2009, Delta Air Lines Flight 60, a 767 on a scheduled flight from Rio de Janeiro to Atlanta, GA, mistakenly landed on a taxiway at Atlanta Hartsfield Airport. The aircraft had been cleared to land on the 12,000-foot long runway 27R, but instead landed on the taxiway which is parallel to the runway. The FAA reported there were no other aircraft on the taxiway and the landing and rollout were normal.

The runway lights for runway 27R were illuminated but the localizer and approach lights for 27R were not turned on. The taxiway was active but was clear of aircraft and ground vehicles at the time the aircraft landed. The wind was calm with 10 miles visibility. The landing occurred at about 6 am, a little over an hour and a half before sunrise.

The NTSB is investigating this event, and it will likely generate extra scrutiny within the organization. Runway safety has been an area of great concern for the NTSB for many years, and has been one of their Most Wanted Transportation Safety Improvements since 1990. Among the recent runway related events that the NTSB has investigated was a September 2008 near collision of a regional jet and a small Cessna at Allentown, PA, and the fatal crash of a Comair regional jet in Lexington, KY in August 2006.

Related Information
Additional Details from the Professional Pilots Rumor Network



Airliner Overshoots Airport by 150 Miles
On 21 October 2009, a Northwest Airlines Airbus A320, Flight 188 from San Diego, CA to Minneapolis/St. Paul, MN, with 147 passengers on board, stopped communicating with air traffic control while the aircraft was in cruise at 37,000 feet.

Authorities were concerned that the flight was being hijacked and had military jets on standby at two locations to intercept the aircraft, though no aircraft were launched.

About an hour after the crew stopped communicating, the aircraft flew over the destination airport and continued northeast for approximately 150 miles. Air traffic control then reestablished communications with the crew and requested that the flight proceed to Minneapolis. The aircraft was out of radio contact for about 75 minutes. The crew landed the aircraft without further incident.

Overview of Final Stages of the Flight

According to the Federal Aviation Administration, the crew was interviewed by the FBI and airport police. The crew stated they were in a heated discussion over airline policy and they lost situational awareness. The Safety Board will interview with the crew and review the data on the flight data recorder and cockpit voice recorder. While the flight data recorder has the capacity to record all data from the flight, the cockpit voice recorder would have only recorded the last 30 minutes of the flight. The two pilots have been suspended from flying while Delta (which owns Northwest) conducts an internal investigation.

This isn't the first time that an airliner has overflown its destination. On 13 February 2008, a Go! airlines jet on a flight from Honolulu, HI to Hilo, HI and with 40 passengers on board overflew Hilo by about 26 miles after both pilots fell asleep during cruise. After the crew woke up, the flight landed in Hilo without further incident.

The investigation into this week's Northwest Airlines event is ongoing, and it may be months before that investigation ends and a cause is determined. However, the full report on the go! Airlines event is available below.

go! Airlines Event Information
NTSB Factual Report
NTSB Probable Cause Findings
NTSB Full Narrative


Listen to the podcast of this article