All Academic, Inc. Research Logo

Info/CitationFAQResearchAll Academic Inc.
Document

Politeness is a Problem? Clarity and Miscommunication in Pilot-ATC Interaction
Unformatted Document Text:  Aviation Politeness 3 approach @ to the airport and as they were returning to attempt landing a second time the engines quit due to fuel starvation. There were 73 fatalities, 81 serious injuries, and four with minor injuries. 3. On July 9, 1978 an Allegheny Airlines BAC 1-11 overshot the runway on a landing attempt at Monroe County Airport in Rochester, NY. The first officer provided callouts to the captain regarding the aircraft = s performance (sink rates and airspeed). However, the captain was not listening. The aircraft finally stopped 728 feet past the end of the runway. Damage to the aircraft was substantial but only one person was injured. 4. In 1972 an Eastern Airlines L-1011 crashed at night in the Everglades. The landing gear light did not come on when the gear was put down. As the flight crew examined the situation the autopilot was accidentally turned of f and the aircraft gradually lost altitude. An air traffic controller noticed the odd descent and inquired A how are things comin = along up there? @ The crew probably assumed he was referring to the gear issue and responded that things were okay. The aircraft flew into the swamp. As it turns out the post accident analysis demonstrated that the landing gear was fine B the cockpit indicator light had burned out. 5. In 1978, a DC-8 crashed outside of the Portland airport. As with the previous example, the gear light did not come on when it was expected. As the flight crew attempted to diagnose the problem the flight engineer repeatedly informed the captain about the increasingly urgent fuel situation. The flight engineer was ignored and the aircraft crashed due to fuel starvation. A distressing similarity to the previous accident is that the indicator light was burned out. The human being is an integral part of an aircraft. History has demonstrated that it is also

Authors: howard, john.
first   previous   Page 3 of 37   next   last



background image
Aviation Politeness 3
approach
@
to the airport and as they were returning to attempt landing a second time the
engines quit due to fuel starvation. There were 73 fatalities, 81 serious injuries, and four
with minor injuries.
3.
On July 9, 1978 an Allegheny Airlines BAC 1-11 overshot the runway on a landing
attempt at Monroe County Airport in Rochester, NY. The first officer provided callouts to
the captain regarding the aircraft
=
s performance (sink rates and airspeed). However, the
captain was not listening. The aircraft finally stopped 728 feet past the end of the runway.
Damage to the aircraft was substantial but only one person was injured.
4.
In 1972 an Eastern Airlines L-1011 crashed at night in the Everglades. The landing gear
light did not come on when the gear was put down. As the flight crew examined the
situation the autopilot was accidentally turned of f and the aircraft gradually lost altitude.
An air traffic controller noticed the odd descent and inquired
A
how are things comin
=
along up there?
@
The crew probably assumed he was referring to the gear issue and
responded that things were okay. The aircraft flew into the swamp. As it turns out the
post accident analysis demonstrated that the landing gear was fine
B
the cockpit indicator
light had burned out.
5.
In 1978, a DC-8 crashed outside of the Portland airport. As with the previous example,
the gear light did not come on when it was expected. As the flight crew attempted to
diagnose the problem the flight engineer repeatedly informed the captain about the
increasingly urgent fuel situation. The flight engineer was ignored and the aircraft crashed
due to fuel starvation. A distressing similarity to the previous accident is that the indicator
light was burned out.
The human being is an integral part of an aircraft. History has demonstrated that it is also


Convention
Need a solution for abstract management? All Academic can help! Contact us today to find out how our system can help your annual meeting.
Submission - Custom fields, multiple submission types, tracks, audio visual, multiple upload formats, automatic conversion to pdf.
Review - Peer Review, Bulk reviewer assignment, bulk emails, ranking, z-score statistics, and multiple worksheets!
Reports - Many standard and custom reports generated while you wait. Print programs with participant indexes, event grids, and more!
Scheduling - Flexible and convenient grid scheduling within rooms and buildings. Conflict checking and advanced filtering.
Communication - Bulk email tools to help your administrators send reminders and responses. Use form letters, a message center, and much more!
Management - Search tools, duplicate people management, editing tools, submission transfers, many tools to manage a variety of conference management headaches!
Click here for more information.

first   previous   Page 3 of 37   next   last

©2012 All Academic, Inc.