13.07.2015 Views

communication in aviation safety: lessons learned and ... - ASASI

communication in aviation safety: lessons learned and ... - ASASI

communication in aviation safety: lessons learned and ... - ASASI

SHOW MORE
SHOW LESS

Create successful ePaper yourself

Turn your PDF publications into a flip-book with our unique Google optimized e-Paper software.

COMMUNICATION IN AVIATION SAFETY:LESSONS LEARNED AND LESSONS REQUIREDPaul D. KrivonosProfessor of Communication StudiesCalifornia State University, NorthridgePresented at the2007 Regional Sem<strong>in</strong>ar of theAustralia <strong>and</strong> New Zeal<strong>and</strong> Societiesof Air Safety Investigators9-10 June 2007


Helmreich <strong>and</strong> Foushee (1993) note that 70% of aircraft accidents <strong>in</strong>volve human error,list<strong>in</strong>g several specific accidents as examples (see also Foushee, 1982, 1984; Kayten,1993; Krifka, Martens, & Schwarz, 2003; O’Hare, Wigg<strong>in</strong>s, Blatt, & Morrison, 1994;Sexton & Helmreich, 2000; <strong>and</strong> Taneja, 2002 for treatment of the relationship betweenhuman error <strong>and</strong> aircraft accidents <strong>and</strong> <strong>in</strong>cidents). They go on to state that: “The themeof these cases is human error result<strong>in</strong>g from failures <strong>in</strong> <strong>in</strong>terpersonal <strong>communication</strong>”(Helmreich <strong>and</strong> Foushee, 1993, p. 21). In fact Krifka, et al. (2003) posit that “Factorsrelated to <strong>in</strong>terpersonal <strong>communication</strong> have been implicated <strong>in</strong> up to 80% of all <strong>aviation</strong>accidents <strong>in</strong> the past 20 years” (p. 1). The FAA also estimates that human error is acontribut<strong>in</strong>g factor <strong>in</strong> 60-80% of all air carrier <strong>in</strong>cidents <strong>and</strong> accidents, cit<strong>in</strong>g <strong>in</strong>effective<strong>communication</strong> <strong>and</strong> other <strong>communication</strong>-related <strong>in</strong>dicators as underly<strong>in</strong>g causes of suchhuman error (Federal Aviation Adm<strong>in</strong>istration, 2004).Sexton <strong>and</strong> Helmreich (2000) posit that <strong>communication</strong> is essential for the <strong>safety</strong> <strong>and</strong>efficiency of any flight; the crew needs to convey <strong>in</strong>formation, communicate to issueorders, acknowledge comm<strong>and</strong>s, conduct brief<strong>in</strong>gs, execute callouts, <strong>and</strong> ask questions:In order for cockpit crewmembers to share a “mental model,” or commonunderst<strong>and</strong><strong>in</strong>g of the nature of events relevant to the <strong>safety</strong> <strong>and</strong> efficiency of theflight, <strong>communication</strong> is critical. This is not to say that effective <strong>communication</strong>can overcome <strong>in</strong>adequate technical fly<strong>in</strong>g proficiency, but rather the contrary,that good” stick & rudder” skills can not overcome the adverse effects of poor<strong>communication</strong> (p.1).Smith-Christensen <strong>and</strong> Durkert (1995) posit that effective <strong>communication</strong> <strong>in</strong> the cockpitis a prerequisite for <strong>safety</strong>. Foushee (1982) notes that “At the very least, <strong>communication</strong>patterns are crucial determ<strong>in</strong>ants of <strong>in</strong>formation transfer <strong>and</strong> crew coord<strong>in</strong>ation . . .” (p.1063). Nagel (1988) observes that: “The results of <strong>communication</strong> errors <strong>in</strong> <strong>aviation</strong> canlead to serious impacts on marg<strong>in</strong>s of <strong>safety</strong>” (p. 284). “Perhaps no other essentialactivity is as vulnerable to failure through human error <strong>and</strong> performance limitations asspoken <strong>communication</strong>” (Monan, 1988, p. 3).Communication-related issues have comprised a sizeable portion of NASA’s AviationSafety Report<strong>in</strong>g System (ASRS) database s<strong>in</strong>ce its <strong>in</strong>ception. Over 70% of the reportsto the ASRS database between 1976 <strong>and</strong> 1981, the first five years of the report<strong>in</strong>g system,were either directly or <strong>in</strong>directly related to <strong>communication</strong> issues <strong>and</strong> problems; (Bill<strong>in</strong>gs& Reynard, 1981; Grayson & Bill<strong>in</strong>gs, 1981; see also, Bill<strong>in</strong>gs & Cheaney, 1981; Monan,1988, 1991 for further explication of these f<strong>in</strong>d<strong>in</strong>gs), <strong>and</strong> cont<strong>in</strong>ue to make up a large partof ASRS reports (see for example George, 1993; Callback, 2001, March; Callback, 2003,October; Callback, 2004, April). “Communication problems are mentioned <strong>in</strong> a highpercentage of <strong>in</strong>cidents reported to ASRS” (Callback, 2003, October, p. 1). Bill<strong>in</strong>gs <strong>and</strong>Reynard (1981) go even further when they posit that <strong>communication</strong> problems <strong>in</strong>volve aneven larger proportion of problems <strong>in</strong> the <strong>aviation</strong> system that the 70% that was found <strong>in</strong>their study.3


The Tenerife tragedy, the worst crash <strong>in</strong> <strong>aviation</strong> history, can be attributed <strong>in</strong> large part to<strong>communication</strong> causes. Other high profile accidents, <strong>in</strong>clud<strong>in</strong>g the Avianca crash <strong>in</strong>Jamaica Bay near JFK <strong>and</strong> the American Airl<strong>in</strong>es crash <strong>in</strong> Columbia <strong>in</strong> 1995, are aga<strong>in</strong>,at least <strong>in</strong> part, the results of <strong>communication</strong> problems. The evidence is not simplyanecdotal—the effect of <strong>communication</strong> on <strong>safety</strong> <strong>in</strong> <strong>aviation</strong> has been firmly established(see, for example, Cush<strong>in</strong>g, 1994; Federal Aviation Adm<strong>in</strong>istration, 2004; Faith, 1996;Foushee, 1984; Foushee & Helmreich, 1988; Helmreich, 1997; Kanki & Palmer, 1993;Kayten, 1993; <strong>and</strong> Wiener & Nagel, 1988). In fact Flight Safety Information (2004)reports that “Between 1976 <strong>and</strong> 2000, more than 1100 passengers <strong>and</strong> crew lost theirlives <strong>in</strong> accidents <strong>in</strong> which <strong>in</strong>vestigators determ<strong>in</strong>ed that language had played acontributory role” (p. 12).This paper will briefly explore the role of <strong>communication</strong> <strong>in</strong> <strong>aviation</strong> <strong>safety</strong>, especially as<strong>communication</strong> functions to provide <strong>in</strong>formation, establish <strong>in</strong>terpersonal relationships,coord<strong>in</strong>ate activity, monitor conditions, <strong>and</strong> as a management tool. Lessons <strong>learned</strong> fromthese areas will be used to propose future <strong>communication</strong>-related research needed <strong>in</strong><strong>aviation</strong> <strong>safety</strong> <strong>and</strong> possible topics <strong>and</strong> methods of <strong>communication</strong> tra<strong>in</strong><strong>in</strong>g for improved<strong>aviation</strong> <strong>safety</strong>.Kanki <strong>and</strong> Palmer (1993) highlight the importance of <strong>communication</strong> <strong>in</strong> <strong>aviation</strong> <strong>safety</strong>when they state that “. . . we would like to underscore the importance of <strong>communication</strong>for efficiency <strong>and</strong> <strong>safety</strong> <strong>in</strong> <strong>aviation</strong> . . .” (p. 99). They further note that: “By now itshould be evident that <strong>communication</strong> at its simplest is a multi-faceted, slippery concept.It is clearly a means to an end; that is, <strong>communication</strong> is required <strong>in</strong> accomplish<strong>in</strong>g thefly<strong>in</strong>g task” (Kanki & Palmer, 1993, p. 129). While <strong>communication</strong>, <strong>in</strong> its multi-facetednature, can have myriad functions <strong>in</strong> a variety of sett<strong>in</strong>gs <strong>and</strong> situations, Kanki <strong>and</strong>Palmer (1993) provide an excellent structure for the functions <strong>communication</strong> plays <strong>in</strong><strong>aviation</strong> <strong>and</strong> <strong>aviation</strong> <strong>safety</strong>, especially as it affects crew performance:1. Communication provides <strong>in</strong>formation2. Communication establishes <strong>in</strong>terpersonal relationships3. Communication establishes predictable behavior patterns4. Communication ma<strong>in</strong>ta<strong>in</strong>s attention to task <strong>and</strong> monitor<strong>in</strong>g5. Communication is a management tool (p. 112)Although there are many ways to conceptualize <strong>communication</strong>, Kanki <strong>and</strong> Palmer’s(1993) taxonomy provides an excellent framework for view<strong>in</strong>g <strong>communication</strong> <strong>lessons</strong>for <strong>aviation</strong> <strong>safety</strong>. It should be noted, however, that while these categories appear to bediscreet <strong>in</strong> nature, <strong>communication</strong> is a much more complex, “multi-faceted” <strong>and</strong>“slippery” process that does not always allow for such simple classification. For examplecrew brief<strong>in</strong>gs might realistically be put <strong>in</strong>to most, if not all of the five categories. Thus,while examples will be somewhat arbitrarily assigned to a s<strong>in</strong>gle category, they morelikely than not could be seen as appropriate for exam<strong>in</strong>ation <strong>in</strong> multiple categories.4


LESSONS LEARNEDCOMMUNICATION PROVIDES INFORMATIONInformation shar<strong>in</strong>g is a critical part of the <strong>aviation</strong> <strong>safety</strong> environment. The first topicthat will be explored with regard to problems of <strong>in</strong>formation transfer is that ofexpectation. Bill<strong>in</strong>gs <strong>and</strong> Reynard (1981) <strong>in</strong> their analysis of ASRS data foundexpectation was a key factor <strong>in</strong> messages be<strong>in</strong>g misunderstood. Us<strong>in</strong>g the same databaseGrayson <strong>and</strong> Bill<strong>in</strong>gs (1981) found that: “Pilots <strong>and</strong> controllers alike tend to hear whatthey expect to hear” (p.48).The follow<strong>in</strong>g report to ASRS amply illustrates the impact of expectation on problemswith <strong>in</strong>formation transfer for <strong>aviation</strong> <strong>safety</strong>, where anticipat<strong>in</strong>g a message—hear<strong>in</strong>gwhat we expect to hear—can create any number of problems for pilots <strong>and</strong> controllers.Eng<strong>in</strong>es were started <strong>and</strong> taxi commenced to the pre-briefed departure runway,Runway 36. Before Takeoff checklist was called for <strong>and</strong> completed dur<strong>in</strong>g the<strong>in</strong>itial taxi…My attention turned to observ<strong>in</strong>g for bird flocks as large numbers ofseagulls were present on the airport…I remarked to the First Officer that theflocks seemed to have moved away from the runway. We cont<strong>in</strong>ued the taxisouthbound…Near<strong>in</strong>g the end of this taxi, I remarked aga<strong>in</strong> to the First Officerthat the large flocks of birds seemed to be away from the runway… Near<strong>in</strong>g thedeparture end of Runway 36, Ground queried us ask<strong>in</strong>g ‘Air carrier X, are you onfrequency?’ The First Officer replied ‘Affirmative, is there a problem?’ (I wasanticipat<strong>in</strong>g <strong>in</strong>formation concern<strong>in</strong>g a gate hold at ZZZ or perhaps a birdreport.) Ground replied, ‘You taxied without a clearance.’ We both were <strong>in</strong>disbelief, th<strong>in</strong>k<strong>in</strong>g we had been cleared to taxi. Ground then asked us to change toTower control, which we did, <strong>and</strong> were subsequently cleared for takeoff onRunway 36 (Callback, 2007, March, p. 2; emphasis added).Another <strong>in</strong>cident <strong>in</strong>volv<strong>in</strong>g a General Aviation pilot also clearly demonstrates the effectof expectation:Our IFR clearance was, "As filed, ma<strong>in</strong>ta<strong>in</strong> 3,000 feet, expect 5,000 feet with<strong>in</strong> 10m<strong>in</strong>utes." Sometime after our frequency change to Departure Control, we werecleared to climb to 5,000 feet. As we approached 5,000 feet, I asked the pilot-notfly<strong>in</strong>gto request 7,000 feet. At that po<strong>in</strong>t, ATC said he had cleared us to 4,000feet -- not 5,000 feet. I had understood 5,000 feet, had written it down, <strong>and</strong> had setthe altitude alerter to 5,000 feet. The Controller told us to "just stay at 5,000 feet<strong>and</strong> I'll work on a higher [altitude]." Perhaps the fact that I had been expect<strong>in</strong>g5,000 feet with<strong>in</strong> 10 m<strong>in</strong>utes, per the clearance received prior to takeoff, lured me<strong>in</strong>to the error (Callback, 1999, March, p. 2; emphasis added).Callback, the monthly publication of the ASRS, often <strong>in</strong>cludes analysts’ comments. TheASRS analyst’s comments preced<strong>in</strong>g the next <strong>in</strong>cident report to ASRS exemplify theexpectation factor as a <strong>communication</strong> problem <strong>in</strong> <strong>aviation</strong> <strong>safety</strong>.5


A B757 pilot shows that even when we th<strong>in</strong>k we are pay<strong>in</strong>g attention, the th<strong>in</strong>k<strong>in</strong>gprocess can be short-circuited by a preconceived notion.Approach said, "Expect Runway 18R." On short f<strong>in</strong>al I thought I heard,"Cleared to l<strong>and</strong> Runway 18R." I asked [Tower to] confirm clearance tol<strong>and</strong>. Aga<strong>in</strong>, I thought he said, "Cleared to l<strong>and</strong> Runway 18R." Afterl<strong>and</strong><strong>in</strong>g, Tower said both transmissions were, "Cleared to l<strong>and</strong> Runway18L." [I] don't know what to say. I just kept th<strong>in</strong>k<strong>in</strong>g Runway 18R.The Capta<strong>in</strong> <strong>in</strong>volved <strong>in</strong> this same <strong>in</strong>cident had expectation on his m<strong>in</strong>d:I had been do<strong>in</strong>g this same flight for almost 2 months; runway 22 had beenthe runway 90% of the time, <strong>and</strong> every l<strong>and</strong><strong>in</strong>g on 22 had been followedby, "Exit the highspeed, cross 27, [contact] Ground the other side." Imistakenly expected this, <strong>and</strong> wanted to hear it (Callback, 2002, October,p.1; emphasis added).Monan (1988) perhaps summarized the issue of expectation best when comment<strong>in</strong>g onhis analysis of hearback problems <strong>in</strong> the ASRS database when he stated that: “Pilotsheard what they expected to hear, heard what they wanted to hear <strong>and</strong> frequently did nothear what they did not anticipate hear<strong>in</strong>g . . .” (p.11).A concept allied to that of expectation is that of mak<strong>in</strong>g assumptions. When we makeassumptions, we <strong>in</strong>terpret the message—or situation—to mean what we assume it tomean, not necessarily what was actually said or perceived.The follow<strong>in</strong>g cases from the ASRS database not only illustrate how mak<strong>in</strong>g assumptionscan lead to misunderst<strong>and</strong><strong>in</strong>gs, but also how such unchecked assumptions can impact<strong>safety</strong>:Eng<strong>in</strong>e start was uneventful until the after start flows were accomplished. At thatpo<strong>in</strong>t we experienced a problem with the left bleed air valve. The MEL(M<strong>in</strong>imum Equipment List) showed this as a "return to gate" item. At this po<strong>in</strong>t, Itold the mechanic we needed to be towed back <strong>in</strong>. His response sounded like hewas ask<strong>in</strong>g us to release the park<strong>in</strong>g brake; however, neither of us quiteunderstood what he had said about the brakes. I asked him if he was ask<strong>in</strong>g us torelease the park<strong>in</strong>g brake, to which he responded, "Release park<strong>in</strong>g brake." Ireleased the park<strong>in</strong>g brake <strong>and</strong> the tug operation commenced.With the tug operation underway, I turned my attention towards the logbook,th<strong>in</strong>k<strong>in</strong>g about how I was go<strong>in</strong>g to write up this problem. The First Officer waslook<strong>in</strong>g over the MEL. What seemed like a few seconds after we began to betugged, the First Officer asked, "Where is this guy tak<strong>in</strong>g us?" I looked up I sawthe end of the paved ramp approach<strong>in</strong>g rapidly <strong>and</strong> heard the First Officer saysometh<strong>in</strong>g about stopp<strong>in</strong>g the aircraft. At that po<strong>in</strong>t we were both simultaneouslyon the brakes. After leav<strong>in</strong>g about 20 feet of skid marks on the ramp, the aircraftcame to a stop with the nose wheel approximately eight feet from the end of thepaved surface... without the tug connected!6


When the aircraft was stopped <strong>and</strong> the eng<strong>in</strong>es shut down, my next concern wasthe location of the mechanic <strong>and</strong> whether he was okay. He was.Although this mechanic speaks fairly good English, I was truly surprised at thelevel of <strong>communication</strong> breakdown that had just occurred. The mechanic told mehe thought I was tell<strong>in</strong>g him that I was releas<strong>in</strong>g the park<strong>in</strong>g brake.Once we started roll<strong>in</strong>g he did not tell us to stop, but <strong>in</strong>stead simply unplugged hisheadset <strong>and</strong> got out of the way.What <strong>lessons</strong> can be <strong>learned</strong> or re<strong>learned</strong> from all of this? First of all this is arem<strong>in</strong>der of someth<strong>in</strong>g we all know, that be<strong>in</strong>g towed is an operation whichrequires someone to be monitor<strong>in</strong>g the aircraft. Secondly, never assumeanyth<strong>in</strong>g. S<strong>in</strong>ce we never saw the tug pull away (it pulled away while we were <strong>in</strong>the books) <strong>and</strong> we were told to release the park<strong>in</strong>g brake, we thought we wereunder tow.Dur<strong>in</strong>g approach brief<strong>in</strong>gs, simulator tra<strong>in</strong><strong>in</strong>g, <strong>and</strong> l<strong>in</strong>e non-normal operationsflight, someone is always assigned the task of monitor<strong>in</strong>g the aircraft. Let thisserve as a rem<strong>in</strong>der to do the same dur<strong>in</strong>g tow operations.Thank goodness no one was hurt, no metal was bent, <strong>and</strong> no careers were put <strong>in</strong>jeopardy, but we sure came darn close (Callback, 2005, November, p. 1; emphasisadded).While be<strong>in</strong>g vectored on a downw<strong>in</strong>d leg to Runway 01L, Tower asked if we hadthe field <strong>in</strong> sight, which we did. At that time we were cleared for a visualapproach to Runway 01L <strong>and</strong> a left turn back to the field was <strong>in</strong>itiated to result <strong>in</strong>a f<strong>in</strong>al of approximately 6 miles. When approximately 60° from the runwayhead<strong>in</strong>g, Tower reported traffic (a B-757) jo<strong>in</strong><strong>in</strong>g a f<strong>in</strong>al for runway 01R. Whilelook<strong>in</strong>g for the traffic the First Officer, who was fly<strong>in</strong>g the aircraft, took his eyesoff the field <strong>and</strong> shallowed his bank... When I realized he was not just squar<strong>in</strong>goff his f<strong>in</strong>al but was go<strong>in</strong>g to overshoot the runway I told him he was go<strong>in</strong>g toovershoot <strong>and</strong> ordered a turn back to our runway. He seemed disoriented <strong>and</strong> wasslow <strong>in</strong> respond<strong>in</strong>g, result<strong>in</strong>g <strong>in</strong> a significant overshoot approach<strong>in</strong>g the approachcorridor for Runway 01R. A TCAS II-Resolution Advisory resulted with a"monitor vertical speed" comm<strong>and</strong> which was complied with. Tower questionedif we had the traffic <strong>in</strong> sight which we answered <strong>in</strong> the affirmative. We correctedback to the 01L centerl<strong>in</strong>e <strong>and</strong> l<strong>and</strong>ed with no further <strong>in</strong>cident.In talk<strong>in</strong>g to the First Officer after the l<strong>and</strong><strong>in</strong>g, he <strong>in</strong>dicated that he lost sight ofthe runway <strong>in</strong> the left turn. Also that he never actually saw the B-757. Although I<strong>in</strong>dicated that I saw the traffic <strong>and</strong> po<strong>in</strong>ted it out, the First Officer did not see it,but I assumed he did. I also assumed that he had the runway <strong>in</strong> sight, so I wasunaware that he had lost situational awareness.The lesson to me is to never assume another crew member is see<strong>in</strong>g the sameth<strong>in</strong>g I am <strong>and</strong> to work to communicate what I am see<strong>in</strong>g even when weather is7


good <strong>and</strong> "easy" visual approaches are be<strong>in</strong>g conducted (Callback, 1999,September, p. 2; emphasis added).As important as the concepts of expectation <strong>and</strong> mak<strong>in</strong>g assumptions are with regard to<strong>communication</strong> problems <strong>in</strong> <strong>aviation</strong> <strong>safety</strong>, perhaps the key issues for creat<strong>in</strong>gdifficulties <strong>in</strong> <strong>in</strong>formation transfer <strong>in</strong>volve mean<strong>in</strong>g, language, <strong>and</strong> jargon. The ASRSdatabase is rife with examples of how mean<strong>in</strong>g can be mis<strong>in</strong>terpreted with<strong>in</strong> the cockpit,between the cockpit <strong>and</strong> ATC, between the cockpit <strong>and</strong> the cab<strong>in</strong>, <strong>and</strong> essentiallythroughout the <strong>aviation</strong> environment.This type of mis<strong>in</strong>terpretation can occur whether it is based on expectation, mak<strong>in</strong>gassumptions, or the fact that we can <strong>in</strong>terpret the mean<strong>in</strong>g of a message to fits our frameof reference, not necessarily what the sender had <strong>in</strong>tended the message to mean. AsRedd<strong>in</strong>g <strong>and</strong> S<strong>in</strong>coff (1984) posit, <strong>communication</strong> is not like a conveyor belt where themean<strong>in</strong>g is transferred from person to another, arriv<strong>in</strong>g—<strong>and</strong> be<strong>in</strong>g <strong>in</strong>terpreted—exactlysame way that it was sent. This type of mis<strong>in</strong>terpretation can be seen <strong>in</strong> the follow<strong>in</strong>gASRS report.Approach<strong>in</strong>g [dest<strong>in</strong>ation airport] from the east we were cleared to 1l,000 feet/250knots. We checked <strong>in</strong> with Approach at 11,000 feet with the ATIS <strong>in</strong>formation.When Approach acknowledged our check they issued a new altimeter sett<strong>in</strong>g of30.00. We acknowledged the updated <strong>in</strong>formation. As I reset the two altimeterson the Capta<strong>in</strong>'s side, I <strong>in</strong>advertently said 3000 (3 thous<strong>and</strong>), referr<strong>in</strong>g to thealtimeter sett<strong>in</strong>g rather than a more appropriate verbiage of 30.00 (three zero zerozero). No other conversation was ongo<strong>in</strong>g at the time. We were both monitor<strong>in</strong>gApproach Control <strong>and</strong> at the time I thought my mean<strong>in</strong>g was clear. Severalmoments later I noticed we were descend<strong>in</strong>g out of 11,000 feet <strong>and</strong> 3,000 was set<strong>in</strong> the altitude w<strong>in</strong>dow. We began a climb back to 11,000 as I reconfirmed ourassigned altitude...After l<strong>and</strong><strong>in</strong>g we discussed the <strong>in</strong>cident further <strong>and</strong> how a similar situation mightbe avoided <strong>in</strong> the future. The First Officer is relatively new a month or two withthe airl<strong>in</strong>e. I <strong>learned</strong> that he had mis<strong>in</strong>terpreted my verbalization of the altimetersett<strong>in</strong>g as a newly assigned altitude <strong>and</strong> thought when I restated it that I wantedhim to reset the altitude select w<strong>in</strong>dow I expla<strong>in</strong>ed that I would be more precise <strong>in</strong>the future. We also used this event as a basis for discuss<strong>in</strong>g why, per our[company] procedures, the Pilot Not Fly<strong>in</strong>g always is the person to reset theassigned altitude <strong>and</strong> that it is verified by the Pilot Fly<strong>in</strong>g prior to any altitudechanges (Callback, 2001, August, p. 2).The follow<strong>in</strong>g exchange between the cockpit <strong>and</strong> the cab<strong>in</strong> also shows how susceptiblewe are to mis<strong>in</strong>terpret<strong>in</strong>g another person’s message:Prior to eng<strong>in</strong>e start, company procedure requires secur<strong>in</strong>g the cockpit door. Thisprocedure was followed <strong>and</strong> the door <strong>in</strong>dicated "locked." Dur<strong>in</strong>g climb out, theflight attendant called the flight deck. The Capta<strong>in</strong> answered <strong>and</strong> after a briefconversation, he <strong>in</strong>structed me to level the aircraft <strong>and</strong> prepare to return to8


[departure airport] due to a disturbance <strong>in</strong> the cab<strong>in</strong>. Dur<strong>in</strong>g the descent, theCapta<strong>in</strong> assumed control of the aircraft. As we were near<strong>in</strong>g [dest<strong>in</strong>ation], theflight attendant called the flight deck to ask if we were l<strong>and</strong><strong>in</strong>g. I replied that wewere. The Capta<strong>in</strong> took this opportunity to get additional <strong>in</strong>formation regard<strong>in</strong>gthe situation <strong>in</strong> the cab<strong>in</strong>. She advised him that the only problem was that thecockpit door was open. The door was then secured <strong>and</strong> the flight cont<strong>in</strong>ued to itsorig<strong>in</strong>al dest<strong>in</strong>ation. Apparently <strong>in</strong> her <strong>in</strong>itial report to the Capta<strong>in</strong>, the flightattendant had simply stated, "Turn around." Her <strong>in</strong>tent was for the Capta<strong>in</strong> to seethe open door, but the Capta<strong>in</strong> perceived her comment to mean that the flight was<strong>in</strong> jeopardy <strong>and</strong> the aircraft should be turned around <strong>and</strong> returned to [departureairport] (Callback, 2004, April, p. 2).The fact that English is the <strong>in</strong>ternational language of <strong>aviation</strong> can also lead tomisunderst<strong>and</strong><strong>in</strong>gs. As has been noted, it is easy enough for native speakers of English tomis<strong>in</strong>terpret other peoples’ messages. Putt<strong>in</strong>g non-native English speakers <strong>in</strong>to the mixcan compound the problem. Pr<strong>in</strong>zo, Hendrix, <strong>and</strong> Hendrix (2006) note that issues relatedto English language proficiency <strong>in</strong> the <strong>aviation</strong> <strong>safety</strong> system need to be addressed.Aga<strong>in</strong>, the ASRS database provides numerous examples of the impact <strong>and</strong> problemsassociated with English as the language of <strong>aviation</strong>. Here are two, both of which <strong>in</strong>cludethe ASRS analyst’s comments that illustrate the <strong>communication</strong> issues <strong>in</strong>volved.U.S. flight crews must exercise extra vigilance when operat<strong>in</strong>g <strong>in</strong>ternationally <strong>in</strong>toairports where accented English, <strong>and</strong> the use of native languages by air trafficcontrollers, can create confusion <strong>and</strong> uncerta<strong>in</strong>ty about ATC <strong>in</strong>structions. A recentASRS report describes how an alert flight crew relied on "gut <strong>in</strong>st<strong>in</strong>cts" <strong>and</strong> priorexperience to avoid a ground collision:We beg<strong>in</strong> with the First Officer's concise account:We were cleared for an immediate departure on Runway 09L, but we hadto do a low-speed abort because the prior aircraft that l<strong>and</strong>ed took anexcessively long time to clear the runway. We also had a hard timeclarify<strong>in</strong>g our clearance because Tower was hav<strong>in</strong>g a long conversation <strong>in</strong>[non-English language]. When we were f<strong>in</strong>ally able to <strong>in</strong>form them of ouractions, they told us to taxi clear of the runway <strong>and</strong> to contact Ground. Weelected to stop immediately after leav<strong>in</strong>g Runway 09L because taxi<strong>in</strong>gwell clear of Runway 09L would have placed us on [a] taxiway which alsodoubles as Runway 09R. We wanted to make sure that it was safe toproceed any further. [It is] fortunate we did because Tower had clearedanother aircraft to l<strong>and</strong> on Runway 09R/taxiway <strong>and</strong> follow<strong>in</strong>g their<strong>in</strong>structions could have resulted <strong>in</strong> a collision.The Capta<strong>in</strong>'s report added this clarify<strong>in</strong>g <strong>in</strong>formation...To clear Runway 09L conservatively would take us on totaxiway/Runway 09R. Taxiway/Runway 09R had not been used as arunway s<strong>in</strong>ce we had been <strong>in</strong> the vic<strong>in</strong>ity [but]...I decided to stay on Towerfrequency wait <strong>and</strong> look first aware that our tail might be <strong>in</strong> close9


proximity to Runway 09L. We felt that due to the limited Englishspeak<strong>in</strong>g capability of the controller, it would be unlikely that we couldget any k<strong>in</strong>d of clarification from him. Also, at the time he was block<strong>in</strong>gthe channel with some lengthy [non-English] dialog. Unknown to me,perhaps because all this occurred on the radio <strong>in</strong> [another language], theaircraft <strong>in</strong> close l<strong>and</strong><strong>in</strong>g proximity now off to our right <strong>and</strong> slightly beh<strong>in</strong>dhad been recleared. At about the time the aircraft touched down [onRunway 09R] right <strong>in</strong> front of us, the Tower controller told us to holdshort of Runway 09R. Yet he had previously h<strong>and</strong>ed us off to Ground...Even this crew's commendable caution could not avoid a ground conflict with thel<strong>and</strong><strong>in</strong>g aircraft on the parallel runway (Callback, 2001, August, p. 2).The language-related problems cited by ASRS reporters <strong>in</strong> foreign airspaceoperations <strong>in</strong>clude unfamiliar controller phraseology, a controller's unclearEnglish or heavy accent, <strong>and</strong> readback/hearback issues. A Capta<strong>in</strong>'s report of anear runway <strong>in</strong>cursion provides a glimpse of the language barrier sometimesexperienced:Dur<strong>in</strong>g taxi, Tower issued <strong>in</strong>structions <strong>in</strong> a very heavy [European] accentthat sounded like, "Cleared <strong>in</strong>to position <strong>and</strong> wait." The First Officer,employ<strong>in</strong>g a phraseology that is common <strong>in</strong> the U.S., asked <strong>in</strong> a very clear<strong>and</strong> enunciated fashion, "Did you clear us <strong>in</strong>to position <strong>and</strong> hold?" TheTower's answer was "Yes." I proceeded beyond the ILS [critical area] holdl<strong>in</strong>e. The Tower shouted, "Stop!" We spotted an airl<strong>in</strong>er break<strong>in</strong>g out ofthe clouds. Although we never penetrated the area of the runway, thesudden stop, the proximity to the runway, <strong>and</strong> the sight <strong>and</strong> sound of thel<strong>and</strong><strong>in</strong>g aircraft scared all of us.It is clear that we misunderstood each other. In all probability, he said,"Cleared to the hold l<strong>in</strong>e <strong>and</strong> wait." Perhaps if we had asked him, "Do youwant us to go on the runway?" he would have responded with a strong"No!" (Callback, 1996, November, p. 1)Even when only native English speakers are <strong>in</strong>volved <strong>in</strong> a <strong>communication</strong> <strong>in</strong>teraction,English language problems can arise as is seen <strong>in</strong> the follow<strong>in</strong>g example that took placeon an Air New Zeal<strong>and</strong> flight.On March 31, 1985, a young man boarded an Air New Zeal<strong>and</strong> flight <strong>in</strong> Londonfor his home <strong>in</strong> Oakl<strong>and</strong>, California. The plane stopped <strong>in</strong> Los Angeles, whereU.S. bound passengers were to deplane <strong>and</strong> board other flights for their domesticdest<strong>in</strong>ations, then boarded new passengers <strong>and</strong> reboarded transit<strong>in</strong>g passengers forthe onward flight to Auckl<strong>and</strong>. He became conv<strong>in</strong>ced that the Air New Zeal<strong>and</strong>crew was direct<strong>in</strong>g Oakl<strong>and</strong>-bound passengers <strong>in</strong>to a transit area, where heheaded, then later reboarded with the rest of the New Zeal<strong>and</strong> bound passengers.Airl<strong>in</strong>e personnel claim that he was asked twice if he was go<strong>in</strong>g to Auckl<strong>and</strong>, <strong>and</strong>10


twice answered <strong>in</strong> the affirmative. His explanation was that the New Zeal<strong>and</strong>accentedcrew didn’t say Auckl<strong>and</strong>, but rather, they said Oakl<strong>and</strong>. It was not untilsometime after takeoff that he realized his error, but it was too late, <strong>and</strong> he foundhimself <strong>in</strong> New Zeal<strong>and</strong>’s largest city at the end of his flight. The next day theairl<strong>in</strong>e flew him home—to Oakl<strong>and</strong>—from Auckl<strong>and</strong> at no charge (Baker, 1985,April 11).As we can see, <strong>in</strong>formation transfer—<strong>and</strong> attendant hazards—can occur <strong>in</strong> any facet ofthe <strong>aviation</strong> environment, not just <strong>in</strong> the cockpit or between the cockpit <strong>and</strong> ATC orcab<strong>in</strong>. The cab<strong>in</strong> is an area where <strong>in</strong>formation transfer is also important. One of thebasic <strong>in</strong>formation functions of the cab<strong>in</strong> crew is send<strong>in</strong>g messages to keep passengers<strong>in</strong>formed about <strong>safety</strong> issues. The messages that flight attendants convey to passengersmay take the form of <strong>in</strong>formation about on-board services, connection gate data, required<strong>safety</strong> brief<strong>in</strong>gs, <strong>and</strong> <strong>in</strong>formation passengers need to cope with <strong>and</strong> survive emergencysituations, <strong>in</strong>clud<strong>in</strong>g evacuations. For the airl<strong>in</strong>e passenger this type of <strong>in</strong>formationtransfer may be vital to survival <strong>in</strong> an emergency. For a thorough treatment of preflight<strong>safety</strong> brief<strong>in</strong>g <strong>and</strong> other aspects of <strong>in</strong>formation transfer <strong>in</strong> the cab<strong>in</strong>—<strong>and</strong> the potential<strong>communication</strong> problems that may occur <strong>in</strong> that environment, see Parker (2006), Barkow<strong>and</strong> Rutenberg (2002), Darby (2006), <strong>and</strong> Krivonos (2005).Jargon, the use of language <strong>in</strong> a profession, trade, or <strong>in</strong> a specialized situation (as <strong>in</strong><strong>aviation</strong>), provides a shorth<strong>and</strong> means for communicat<strong>in</strong>g well—when everyoneunderst<strong>and</strong>s the jargon. The <strong>aviation</strong> <strong>safety</strong> environment is loaded with jargon that oftenmakes <strong>communication</strong> more efficient <strong>and</strong> effective. However, when others don’tunderst<strong>and</strong> the jargon or use it <strong>in</strong>correctly, then problems of misunderst<strong>and</strong><strong>in</strong>g <strong>and</strong>mis<strong>in</strong>terpretation can easily occur.The follow<strong>in</strong>g example from the ASRS database provided by Matchette (1995) illustrateshow such difficulties can arise with the misuse of jargon, as it did for one unfortunatepilot:The Pilot-Controller Glossary def<strong>in</strong>es squawk as "activate specificmode/code/function on the aircraft transponder." Therefore, "squawk youraltitude" is a controller's <strong>in</strong>struction to activate the altitude function of a Mode3/A transponder.Squawk<strong>in</strong>g 7500 is the <strong>in</strong>ternational code to <strong>in</strong>dicate a hijack<strong>in</strong>g. The AIM<strong>in</strong>structs pilots of hijacked aircraft to set 7500 <strong>in</strong>to the aircraft transponder, whichtriggers a flash<strong>in</strong>g "HIJK" <strong>in</strong> the aircraft's data block on the Controller's radarscreen. The Controller will then ask the pilot to "verify squawk<strong>in</strong>g 7500." If thepilot verifies the code or makes no response at all, the Controller will not askfurther questions, but will cont<strong>in</strong>ue to flight-follow, respond to pilot requests, <strong>and</strong>notify appropriate authorities. These procedures are exactly the ones thatoccurred, as this reporter can testify:"Burbank assigned me a squawk code. Several m<strong>in</strong>utes later the Controller11


asked me my altitude <strong>and</strong> I responded 7,500 feet. He told me to squawk myaltitude. I replied, 'Squawk<strong>in</strong>g 7500', <strong>and</strong> the Controller confirmed mycode...After l<strong>and</strong><strong>in</strong>g, Ground directed me to a specific park<strong>in</strong>g area, <strong>and</strong> Iwas immediately surrounded by three police cars with a number of officerspo<strong>in</strong>t<strong>in</strong>g their weapons at me...They frisked me <strong>and</strong> h<strong>and</strong>cuffed me. Theyreally roughed me up...I would suggest that Controllers never use theterm<strong>in</strong>ology 'squawk your altitude.' "This poor pilot forgot to review his AIM, which would have <strong>in</strong>formed him that:"Code 7500 will never be assigned by ATC without prior notification from thepilot that his aircraft is be<strong>in</strong>g subjected to unlawful <strong>in</strong>terference [hijack<strong>in</strong>g]. Thepilot should refuse the assignment of Code 7500 <strong>in</strong> any other situation <strong>and</strong> <strong>in</strong>formthe controller accord<strong>in</strong>gly" (p. 20).One of the problems with the use of jargon is that if someone isn’t familiar with thejargon, you might as well be speak<strong>in</strong>g a foreign language. Us<strong>in</strong>g jargon when othersdon’t know what it means is an example of what I term the COIK pr<strong>in</strong>ciple—Clear OnlyIf Known. Aga<strong>in</strong>, if we know what the jargon means, it is a h<strong>and</strong>y way to help <strong>in</strong> the<strong>in</strong>formation transfer process. If we do not know what the jargon means, then the<strong>in</strong>formation is seldom, if ever, transferred effectively.Majoros (1990) offers a personal example that effectively captures the essence of theCOIK pr<strong>in</strong>ciple:I would like to relate an <strong>in</strong>cident that happened as I was board<strong>in</strong>g a plane <strong>in</strong>Orange County to come to Wash<strong>in</strong>gton. At this time the John Wayne Airport isundergo<strong>in</strong>g a major build<strong>in</strong>g program <strong>and</strong> does not have jetways or othermotorized conveniences for plan<strong>in</strong>g <strong>and</strong> deplan<strong>in</strong>g, Planes must l<strong>in</strong>e up on theapron or tarmac or gate area one-by-one <strong>and</strong> passengers have to walk to theaircraft. Just before I boarded the flight, the board<strong>in</strong>g agent said over the publicaddress system, “Flight 1256 is <strong>in</strong> f<strong>in</strong>al board<strong>in</strong>g. Passengers should proceedthrough Gate C. The plane is <strong>in</strong> the middle of the runway, it is fac<strong>in</strong>g south, <strong>and</strong>it is a Boe<strong>in</strong>g.” Other than the experienced traveler, who would know where togo with these <strong>in</strong>structions? How much of our <strong>communication</strong> <strong>in</strong> ma<strong>in</strong>tenancecould take on similar tones because the <strong>communication</strong> is not clear <strong>and</strong> thema<strong>in</strong>ta<strong>in</strong>er does not know where to go with the <strong>in</strong>structions? (p.44)While there are a number of <strong>communication</strong> <strong>and</strong> <strong>in</strong>formation transfer issues <strong>and</strong> problemsthat are apparent <strong>in</strong> the above discussion, there are some effective <strong>communication</strong>pr<strong>in</strong>ciples that can lead to greater <strong>safety</strong> <strong>and</strong> less risk <strong>and</strong> error <strong>in</strong> the system. Althoughmore effective listen<strong>in</strong>g skills would be generally helpful, two specific <strong>communication</strong>skills that can be applied to create more effective <strong>in</strong>formation transfer <strong>in</strong> the <strong>aviation</strong>environment are us<strong>in</strong>g feedback <strong>and</strong> ask<strong>in</strong>g questions. Given that a substantial number ofASRS reports <strong>in</strong>volve readback/hearback problems (Callback, 2001, March), these skillsare especially important.12


With regard to feedback both Ruffell Smith (1979) <strong>and</strong> Foushee <strong>and</strong> Manos (1981) notethat feedback <strong>in</strong> the form of acknowledgement, monitor<strong>in</strong>g, <strong>and</strong> cross-check<strong>in</strong>g areimportant aspects of <strong>communication</strong> for effective flight operations. The follow<strong>in</strong>gexample from the ASRS data base, <strong>in</strong>clud<strong>in</strong>g the analyst’s comments, illustrates theimportance of feedback.M<strong>and</strong>atory readback of certa<strong>in</strong> parts of clearances provides a mechanism toreduce misunderst<strong>and</strong><strong>in</strong>gs between ATC <strong>and</strong> flight crews. An ATC supervisorreports on a readback error that slipped by both him <strong>and</strong> an ATC tra<strong>in</strong>ee, with apotentially hazardous result.Aircraft A was given a descent from 8,000 feet to only 7,000 feet (6,000feet would be the norm on this route). Pilot read back 6,000 feet, whichwas not caught by either of us. We tried to get him back to 7,000 feet, buthe went to 6,500 before he climbed back. Aircraft B was one mile <strong>in</strong> trailat 6,000 feet, same speed.A contribut<strong>in</strong>g factor was my over-reliance on the tra<strong>in</strong>ee, who is fairlywell along <strong>in</strong> tra<strong>in</strong><strong>in</strong>g. I was assum<strong>in</strong>g he would catch the problem, so Iwas not listen<strong>in</strong>g as <strong>in</strong>tently. Also, the [typical] descent from 8,000 to6,000 feet probably had the pilot expect<strong>in</strong>g to hear 6,000. Only goes toprove the importance of readbacks be<strong>in</strong>g heard <strong>and</strong> understood (Callback,1997, October, p. 1).The follow<strong>in</strong>g comment by an ASRS analyst about the example provided aboveconcern<strong>in</strong>g the mis<strong>in</strong>terpretation of “position <strong>and</strong> hold” provides an excellent justificationfor ask<strong>in</strong>g questions:The reporter realized after the fact that the crew either misheard or mis<strong>in</strong>terpretedthe Controller's clearance. Regardless, the reporter's suggestion is a good one:seek clarification by rephras<strong>in</strong>g the clearance <strong>in</strong> pla<strong>in</strong>, simple words, differentfrom those used by the controller. Although some foreign controllers may nothave a broad comm<strong>and</strong> of English, they often will underst<strong>and</strong> the crew's restatedquestions <strong>and</strong> be able to provide clarification (Callback, 1996, November, p. 1).These reports certa<strong>in</strong>ly underscore the need for feedback to clear up uncheckedassumptions <strong>and</strong> expectations. For a full treatment of readback/ hearback issues <strong>in</strong><strong>aviation</strong> <strong>safety</strong> see Monan (1988, 1991).Ask<strong>in</strong>g questions is another effective <strong>communication</strong> skill that can help reduce<strong>in</strong>formation transfer problems <strong>in</strong> the <strong>aviation</strong> <strong>safety</strong> environment, thus m<strong>in</strong>imiz<strong>in</strong>g risk.Krifka, et al. (2003) found that questions were slightly more frequent <strong>in</strong> good crews <strong>and</strong>that good crews also answered a considerably higher number of questions; <strong>in</strong> contrast togood crews, comm<strong>and</strong>s were more frequent <strong>in</strong> poor crews. Flight Safety Foundation(2000) <strong>in</strong>dicates that the failure to request clarification or to question ATC <strong>in</strong>structions isan <strong>in</strong>effective aspect of pilots’ <strong>communication</strong>. Follow<strong>in</strong>g are an ASRS report <strong>and</strong> then13


accident report from the FAA that clearly illustrate the importance of ask<strong>in</strong>g questions forclarification:After complet<strong>in</strong>g our run-up, we taxied to the hold short l<strong>in</strong>e of Runway 16. Mystudent was at the controls <strong>in</strong> the left seat. He called the tower say<strong>in</strong>g "Skyhawkhold<strong>in</strong>g short Runway 16, ready for takeoff." The tower replied, "Skyhawk, taxiup <strong>and</strong> hold." I thought the tower meant taxi <strong>in</strong>to position <strong>and</strong> hold...<strong>and</strong> wecrossed the hold short l<strong>in</strong>e. Tower then told us to stop <strong>and</strong> clear the runway. Wecomplied immediately, but the <strong>in</strong>bound plane elected to go around. Factorscontribut<strong>in</strong>g to this <strong>in</strong>cident were the use of non-st<strong>and</strong>ard phraseology by thetower, <strong>and</strong> my failure to verify whether he meant "hold short" or "taxi <strong>in</strong>toposition <strong>and</strong> hold." To avoid this type of situation <strong>in</strong> the future, I will always askif I am not sure of a clearance, especially before enter<strong>in</strong>g the active runway(Callback, 2004, April, p. 2; emphasis added):. . . a lack of <strong>communication</strong> between the crew <strong>and</strong> air traffic controllers dur<strong>in</strong>g al<strong>and</strong><strong>in</strong>g <strong>in</strong> a severe thunderstorm contributed to the accident, accord<strong>in</strong>g to theNTSB report. The crew did not request clarification about the weatherconditions or change its course of action to take these conditions <strong>in</strong>to account.The w<strong>in</strong>ds associated with the storm forced the plane down precipitously, caus<strong>in</strong>gan emergency l<strong>and</strong><strong>in</strong>g without the l<strong>and</strong><strong>in</strong>g gear’s be<strong>in</strong>g fully extended. The planeskidded off the runway, caus<strong>in</strong>g serious damage to the aircraft <strong>and</strong> an emergencyevacuation of the passengers (Federal Aviation Adm<strong>in</strong>istration, 1997, p.11;emphasis added).Monan (1991) effectively sums up the importance of ask<strong>in</strong>g questions when he states:“Ask for verification of any ATC <strong>in</strong>struction about which there is doubt” (p. 4). Thissuggestion goes for any <strong>communication</strong> <strong>in</strong>teraction <strong>in</strong> the <strong>aviation</strong> <strong>safety</strong> environment,not just between pilot <strong>and</strong> ATC. It is useful advice with<strong>in</strong> the cockpit or cab<strong>in</strong>, betweencockpit <strong>and</strong> cab<strong>in</strong>, or for any aspect of the <strong>aviation</strong> <strong>safety</strong> system.COMMUNICATION ESTABLISHES INTERPERSONAL RELATIONSHIPSA large part of <strong>in</strong>teraction among flight crew, among cab<strong>in</strong> crew, <strong>and</strong> between flight <strong>and</strong>cab<strong>in</strong> crew <strong>in</strong>volves <strong>communication</strong> function<strong>in</strong>g to establish <strong>in</strong>terpersonal relationships.Davis (<strong>in</strong>terviewed by Schultz, 2002) notes the importance of <strong>communication</strong>relationships <strong>in</strong> <strong>aviation</strong> when he states that:In virtually every organization, the ability to create effective relationships isessential. . . The same is true <strong>in</strong> the cockpit of an airplane. Dur<strong>in</strong>g criticalmoments, effective <strong>communication</strong> can mean the difference between life <strong>and</strong>death. You can avoid accidents most of the time if you have a flight crew whosemembers can talk to one another <strong>and</strong> whose voices are listened to (p. 3).14


One aspect of <strong>communication</strong> relationships is how people <strong>in</strong>teract with one another,especially <strong>in</strong> a hierarchical sett<strong>in</strong>g, as is the case <strong>in</strong> operation of an airplane. L<strong>in</strong>de(1988) found that suggestions by crew members to capta<strong>in</strong>s are more likely to fail if theyare more polite <strong>and</strong> <strong>in</strong>direct than if they are direct, <strong>and</strong> notes the dangers of excessivemitigation (politeness <strong>and</strong> <strong>in</strong>directness) <strong>in</strong> the cockpit. Thomas (2004a, 2004b, 2005) <strong>and</strong>Thomas <strong>and</strong> Petrilli (2004) associate poor <strong>communication</strong> between <strong>and</strong> among crewmembers with a lack of assertiveness, especially on the part of First Officers, <strong>and</strong> that thistype of relational <strong>in</strong>teraction could lead to poor crew coord<strong>in</strong>ation <strong>and</strong> performance.L<strong>in</strong>de (1988) does note, however, results <strong>in</strong> her study which found that crews classifiedas high <strong>in</strong> <strong>safety</strong> performance have higher rates of mitigation that those classified as poor<strong>in</strong> <strong>safety</strong> performance. Her explanation is that mitigation is a “k<strong>in</strong>d of social oil, whichcan help to prevent the development of <strong>in</strong>terpersonal <strong>and</strong> relational misunderst<strong>and</strong><strong>in</strong>gs<strong>and</strong> animosity” (p. 396). Merritt, (1995) echoes L<strong>in</strong>de’s notion that mitigation <strong>and</strong><strong>in</strong>directness are not necessarily a problem for <strong>aviation</strong> <strong>safety</strong>:I th<strong>in</strong>k we need to acknowledge that <strong>in</strong>direct <strong>communication</strong> will always bepresent <strong>in</strong> <strong>aviation</strong>, <strong>and</strong> that it is not automatically a bad th<strong>in</strong>g. Indirect<strong>communication</strong> can facilitate teamwork, it can promote non-defensiveness <strong>in</strong>tra<strong>in</strong><strong>in</strong>g <strong>and</strong> debrief situations, <strong>and</strong> <strong>in</strong> high face-threat situations it may be theonly form of <strong>communication</strong> that less experienced or lower status crewmemberscan articulate (p. 2).Clearly there is disagreement about the value of assertiveness or mitigation <strong>in</strong> the<strong>aviation</strong> environment, especially the cockpit. Perhaps most important <strong>in</strong> this discussionof assertiveness versus <strong>in</strong>directness (or mitigation) is the need to take a situationalperspective on <strong>communication</strong> <strong>in</strong>teraction <strong>and</strong> not try to apply a one-size-fits-all solutionto every situation. It is probably that neither the assertiveness perspective nor themitigation perspective is completely correct or <strong>in</strong>correct. Rather it is most likely thateach is appropriate <strong>in</strong> different <strong>communication</strong> situations. One example might be evident<strong>in</strong> an emergency situation which would most likely call for greater assertiveness.COMMUNICATION ESTABLISHES PREDICTABLE BEHAVIOR PATTERNSFunction<strong>in</strong>g as predictable patterns of behavior, <strong>communication</strong> can help us coord<strong>in</strong>atehuman activities <strong>in</strong>clud<strong>in</strong>g the teamwork necessary for the effective operation of aircraft<strong>and</strong> thus have an impact on <strong>aviation</strong> <strong>safety</strong>. Ruffell Smith (1979) conducted <strong>in</strong> a flightsimulator study from which he found that most of the “fly<strong>in</strong>g” difficulties were related tocrew coord<strong>in</strong>ation problems, not poor technical skills or lack of knowledge. Becauseeffective crew coord<strong>in</strong>ation is ma<strong>in</strong>ly accomplished through effective <strong>communication</strong>, itfollows then that effective crew performance is more closely associated with effectivecrew <strong>communication</strong> than with any <strong>in</strong>dividual pilot’s fly<strong>in</strong>g proficiency.In a follow up study to that of Ruffell Smith (1970), Foushee <strong>and</strong> Manos (1981) analyzedthe cockpit voice record<strong>in</strong>g utiliz<strong>in</strong>g Ruffell Smith’s data from his study. Foushee <strong>and</strong>15


Manos (1981) found a positive relationship between <strong>communication</strong> <strong>and</strong> good flightperformance: “Overall, there was a tendency for crews who did not perform as well tocommunicate less, suggest<strong>in</strong>g that as expected, poor crew coord<strong>in</strong>ation tends to result <strong>in</strong>more marg<strong>in</strong>al performance (p. 66).They also found that it was not simply the amount of <strong>communication</strong> that was importantfor effective crew coord<strong>in</strong>ation, but more importantly the type of <strong>in</strong>formation that wasshare. They found that the greater the <strong>in</strong>formation about flight status that was shared, thefewer errors there were <strong>in</strong> the operation of the flight. In addition the type of<strong>communication</strong> ulilized also played a role: more <strong>in</strong>quiries, observations, <strong>and</strong>acknowledgements were also related to fewer operational errors, while poor<strong>communication</strong>, lack of underst<strong>and</strong><strong>in</strong>g, <strong>and</strong> such specific <strong>communication</strong> behaviors asfrustration, anger, uncerta<strong>in</strong>ty, <strong>and</strong> embarrassment were related to higher operationalerrors (Foushee & Manos, 1981).Federal Aviation Adm<strong>in</strong>istration (1997) notes that a lack of coord<strong>in</strong>ation among membersof the cockpit crew can lead to problems <strong>and</strong> emphasizes the importance of effective<strong>communication</strong> to accomplish effective coord<strong>in</strong>ation. Taneja (2002) notes that lack ofeffective <strong>communication</strong> by aircrew cont<strong>in</strong>ues to be the most causal factor <strong>in</strong> <strong>aviation</strong>accidents. In his review of human factors <strong>in</strong> aircraft accident <strong>and</strong> <strong>in</strong>cident <strong>in</strong>vestigations,Adams (2006) po<strong>in</strong>ts to <strong>communication</strong> as one of the key factors lead<strong>in</strong>g to errors thattranspired because of poor crew coord<strong>in</strong>ation.Aga<strong>in</strong>, the cockpit crew is but one aspect of the <strong>aviation</strong> system. While criticallyimportant for the <strong>safety</strong> of any flight, they are not the only source of <strong>communication</strong> forprovid<strong>in</strong>g predicable behavior patterns or coord<strong>in</strong>at<strong>in</strong>g activity. The cab<strong>in</strong> crew is alsocharged with that task, especially when it comes to cab<strong>in</strong> <strong>safety</strong>. Burian, Kismukes, <strong>and</strong>Barshi (2003) posit the importance of <strong>communication</strong> <strong>and</strong> coord<strong>in</strong>ation dur<strong>in</strong>g emergencysituations <strong>and</strong> as an example note that <strong>communication</strong> problems between the cab<strong>in</strong> <strong>and</strong>cockpit had negative consequences the evacuation of a flight <strong>in</strong>to LaGuardia <strong>in</strong> 2003.Flight Safety Foundation (2003) <strong>in</strong>dicates that poor <strong>communication</strong> can contribute toproblems dur<strong>in</strong>g evacuation procedures. Transportation Safety Board of Canada (1995)reports several evacuations <strong>in</strong> which <strong>in</strong>effective cab<strong>in</strong> crew <strong>communication</strong> jeopardizedthe chances of successful evacuations <strong>in</strong> several <strong>in</strong>cidents:Effective crew coord<strong>in</strong>ation is crucial to a successful evacuation, but <strong>in</strong>effectivecrew <strong>communication</strong> leads to <strong>in</strong>effective crew coord<strong>in</strong>ation. As evidenced by theoccurrence data, poor crew <strong>communication</strong> may result <strong>in</strong> unnecessary <strong>in</strong>juries orfatalities <strong>and</strong> unnecessary exposure to risk for passengers <strong>and</strong> aircrew alike (p.20).Effective coord<strong>in</strong>ation between cab<strong>in</strong> crew <strong>and</strong> flight deck crew is also essential for thesafe operation of an aircraft. S<strong>in</strong>ce 9/11, effective <strong>communication</strong> from the cab<strong>in</strong> crew tothe flight crew is even more important. “The ‘sealed’ cockpit environment has <strong>in</strong>creasedthe reliance on Flight Attendants for the transfer of vital <strong>in</strong>formation” (Callback, 2003,16


March). The FAA clearly states that effective <strong>communication</strong> between all crewmembersis a prerequisite for such coord<strong>in</strong>ation (Federal Aviation Adm<strong>in</strong>istration, 1988). ASRSre<strong>in</strong>forces this po<strong>in</strong>t: “Flight attendants are an <strong>in</strong>tegral part of the aircraft crew <strong>and</strong> theirprimary responsibilities are <strong>safety</strong> related” (Callback, 2003). Rice (2001, May-June)suggests that better <strong>communication</strong> between cab<strong>in</strong> crew <strong>and</strong> flight crew have resulted <strong>in</strong>fewer fatalities. Chute <strong>and</strong> Wiener (1995) make the tie between <strong>communication</strong> <strong>and</strong><strong>safety</strong> even more explicit:There are two critical <strong>safety</strong> obligations for the flight attendant. The first is toprevent accidents, primarily by means of conveyance of <strong>in</strong>formation regard<strong>in</strong>ghazardous conditions to the flight deck. If the accident cannot be prevented, thesecond is to maximize survivability. Both roles require effective <strong>communication</strong>between the two cultures (p. 15).There are a large number of reports that confirm the success with regard to <strong>safety</strong> ofeffective <strong>communication</strong> <strong>in</strong> the cab<strong>in</strong>-cockpit <strong>in</strong>teraction (see, for example, Callback1999, August; 2003, March; 2004, February). Yet, the work<strong>in</strong>g <strong>and</strong> relationship <strong>and</strong><strong>communication</strong> <strong>in</strong>teraction between cab<strong>in</strong> crew <strong>and</strong> flight crew cont<strong>in</strong>ues to be a vex<strong>in</strong>gone. “Communication <strong>and</strong> coord<strong>in</strong>ation problems between cockpit crewmembers <strong>and</strong>flight attendants cont<strong>in</strong>ue to challenge air carriers <strong>and</strong> the FAA” (Federal AviationAdm<strong>in</strong>istration, 2004, p. 15).Helmreich, Wiener, <strong>and</strong> Kanki (1993) <strong>and</strong> Kayten (1993) cite numerous examples wherecrew coord<strong>in</strong>ation problems <strong>and</strong> poor <strong>communication</strong> were contribut<strong>in</strong>g factors <strong>in</strong> severalaccident reports. Murphy (2001) conveys stories from flight attendants who felt that vital<strong>in</strong>formation they tried to pass along to the cockpit was ignored. In their study of flightattendants <strong>and</strong> pilots, Chute & Wiener (1996) found cab<strong>in</strong>-cockpit <strong>communication</strong> to be<strong>in</strong>effective. Chute (2001) also ma<strong>in</strong>ta<strong>in</strong>s that cab<strong>in</strong>-cockpit <strong>communication</strong> is not alwaysnecessarily effective.In a report on evacuation procedures, the Transportation Safety Board of Canada (1995)<strong>in</strong>dicated that poor <strong>communication</strong> between flight <strong>and</strong> cab<strong>in</strong> crew possibly jeopardizedsafe evacuations <strong>in</strong> several <strong>in</strong>stances. Regard<strong>in</strong>g one specific <strong>in</strong>cident, the report statesthat:Inadequate <strong>communication</strong> between the cab<strong>in</strong> <strong>and</strong> the flight deck resulted <strong>in</strong> asignificant delay before the flight crew was aware of the existence <strong>and</strong> seriousnessof the fire <strong>and</strong> contributed to the fact that the evacuation was not <strong>in</strong>itiated untilone m<strong>in</strong>ute 55 seconds follow<strong>in</strong>g the rejected take-off (Transportation SafetyBoard of Canada, 1995, p. 19).Perhaps the two most dramatic examples, however, of <strong>safety</strong> problems due to poor cab<strong>in</strong>cockpitcoord<strong>in</strong>ation <strong>and</strong> <strong>communication</strong> are the crash of the Air Ontario flight whiletak<strong>in</strong>g off from Dryden, Canada on March 10, 1989 (Baker & Frost, 1994; Chute &Wiener, 1996; Merritt, 1995; Moshansky, 1992; Murphy, 2001) <strong>and</strong> the crash of theBritish Midl<strong>and</strong>s flight on January 8, 1989 at Kegworth after tak<strong>in</strong>g off from London’s17


Heathrow Airport (Baker & Frost, 1994; Department for Transport, 1990).In the Dryden crash, the pilots of a Fokker F-28 tried to take off, even though the uppersurface of the w<strong>in</strong>gs were covered with snow; the plane clipped the treetops <strong>and</strong> came torest <strong>in</strong> a heavily wooded area, with the loss of twenty-four lives (Baker & Frost, 1994).A flight attendant, one of the few (<strong>and</strong> only crew member) to survive, saw that the w<strong>in</strong>gswere not properly de-iced, but did not convey that <strong>in</strong>formation to the pilots:Moments before takeoff, the F28 was tak<strong>in</strong>g out for the f<strong>in</strong>al takeoff withsignificant amounts of snow visible on the w<strong>in</strong>gs, <strong>and</strong> while a flight attendant <strong>and</strong>two airl<strong>in</strong>e capta<strong>in</strong>s travel<strong>in</strong>g as passengers notices, this was never communicatedto the pilots. The flight attendant, who was the only crew member to survive,testified later that she had concerns over the snow, but because she had beenrebuffed by company pilots over a similar situation <strong>in</strong> the past, it <strong>in</strong>fluenced herdecision no [sic] to go to the cockpit (Aviation Safety Letter, 2004, p. 2).Similarly, the Kegworth crash provides another example of cab<strong>in</strong> crew not provid<strong>in</strong>gcrucial <strong>in</strong>formation to the flight crew. The British Midl<strong>and</strong>s Boe<strong>in</strong>g 737-400 experiencedan eng<strong>in</strong>e fire <strong>in</strong> the left eng<strong>in</strong>e, a fact that several cab<strong>in</strong> staff <strong>and</strong> passengers noticed, butthis <strong>in</strong>formation was not conveyed to the flight crew, who reduced power to one eng<strong>in</strong>e,then when vibrations <strong>and</strong> smoke ceased, mistakenly shut down the wrong eng<strong>in</strong>e <strong>and</strong>crashed <strong>in</strong>to an embankment of the M1 Motorway, with the loss of forty-seven lives(Department for Transport, 1990).Another area where <strong>communication</strong> plays a coord<strong>in</strong>at<strong>in</strong>g role between flight <strong>and</strong> cab<strong>in</strong>crew is <strong>in</strong> pre-flight brief<strong>in</strong>gs. While a greater amount of time for the brief<strong>in</strong>g would beadvisable (Chute & Wiener, 1995; Murphy, 2001), this is not always possible. Withappropriate <strong>communication</strong>, even a short period of time can help to establish positiverelationships between the cab<strong>in</strong> crew <strong>and</strong> flight crew. Zun<strong>in</strong> <strong>and</strong> Zun<strong>in</strong> (1974) feel thatthe first four m<strong>in</strong>utes of any relationship are critical <strong>in</strong> establish<strong>in</strong>g rapport. The FAA hassuggested a number of simple behaviors that can enhance the work<strong>in</strong>g relationshipbetween flight attendants <strong>and</strong> flight crewmembers to establish a positive climate for good<strong>communication</strong> <strong>and</strong> effective crew coord<strong>in</strong>ation; seem<strong>in</strong>gly, one of the easiest ways to doso is through courteous mutual <strong>in</strong>troductions (Federal Aviation Adm<strong>in</strong>istration, 1988).Chute <strong>and</strong> Wiener (1994), however, found that flight attendants were almost universal <strong>in</strong>their compla<strong>in</strong>t that pilots, especially capta<strong>in</strong>s, failed to <strong>in</strong>troduce themselves. Pilots alsoexpressed a desire that flight attendants take the <strong>in</strong>itiative to <strong>in</strong>troduce themselves (Chute& Wiener, 1995).Surpris<strong>in</strong>gly, even pilot-to-cab<strong>in</strong> brief<strong>in</strong>gs themselves seem to be the exception ratherthan the rule. Pilots perceived that such brief<strong>in</strong>gs occurred at a much higher frequencythan did flight attendants (Chute & Wiener, 1995) <strong>and</strong> both pilots <strong>and</strong> flight attendantscompla<strong>in</strong> about how often such brief<strong>in</strong>gs are omitted <strong>and</strong> disregarded (Chidester &Vaugn, 1994). Thus, even “before the crew board the aircraft, the stage is set for poor<strong>communication</strong>” (Chute & Wiener, 1996, p. 3).18


[A capta<strong>in</strong>’s report about an <strong>in</strong>cident]While we were <strong>in</strong> level cruise at FL330, Center cleared us to FL290, "pilot'sdiscretion" to 11,000 feet (or so I thought). I dialed <strong>in</strong> 11,000 feet <strong>in</strong> the altitudew<strong>in</strong>dow, <strong>and</strong> the First Officer [FO] acknowledged. The first clue I had thatsometh<strong>in</strong>g was amiss was when I noticed another aircraft...we were approach<strong>in</strong>gFL270, <strong>and</strong> the FO told me we were only cleared to FL290.[The First Officer’s report about the <strong>in</strong>cident]Dur<strong>in</strong>g the conversation with the controller, a conversation was go<strong>in</strong>g on with<strong>in</strong>the cockpit with a deadhead<strong>in</strong>g crew member, which may have contributed to theFO <strong>and</strong> Capta<strong>in</strong> not verify<strong>in</strong>g the altitude assignment with each other. The crewhad several tasks <strong>in</strong> progress, with brief<strong>in</strong>g, receiv<strong>in</strong>g ATIS, <strong>and</strong> mak<strong>in</strong>g "<strong>in</strong>range" calls (Callback, 1998, September, p. 2).One possible remedy (which will be explored <strong>in</strong> the discussion of <strong>communication</strong>tra<strong>in</strong><strong>in</strong>g) is effective listen<strong>in</strong>g which can help provide greater focus <strong>and</strong> attention.The nature of distraction <strong>in</strong> the cockpit <strong>and</strong> problems that occur because of it is treated <strong>in</strong>excellent fashion by Australian Transportation Bureau (2005).COMMUNICATION IS A MANAGEMENT TOOLWhile much of the <strong>communication</strong> functions noted <strong>in</strong> relationships <strong>and</strong> coord<strong>in</strong>at<strong>in</strong>gactivities could also be classified as a management tool, perhaps the most importantaspect of <strong>communication</strong> <strong>in</strong> this regard is to create <strong>and</strong> ma<strong>in</strong>ta<strong>in</strong> a <strong>safety</strong> culture <strong>in</strong> any<strong>aviation</strong> organization. It is through leadership <strong>and</strong> messages about the importance of<strong>safety</strong> (<strong>and</strong> the effective transfer of <strong>in</strong>formation, teamwork, <strong>and</strong> attention to task)—<strong>and</strong>behaviors <strong>and</strong> resources to back up those messages—that a <strong>safety</strong> culture can be built <strong>and</strong>nourished.LESSONS REQUIREDThis paper has outl<strong>in</strong>ed several areas where <strong>lessons</strong> have been <strong>learned</strong> with regard to<strong>communication</strong> <strong>in</strong> <strong>aviation</strong> <strong>safety</strong> with regard to how <strong>communication</strong> functions to provide<strong>in</strong>formation, establish <strong>in</strong>terpersonal relationships, coord<strong>in</strong>ate activity, monitor conditions,<strong>and</strong> as a management tool. A number of suggestions for possible future research <strong>and</strong>proposals for tra<strong>in</strong><strong>in</strong>g for improv<strong>in</strong>g <strong>aviation</strong> <strong>safety</strong> will be offered. While there arecerta<strong>in</strong>ly a large number of important subjects that would provide valuable <strong>in</strong>sight <strong>in</strong>to<strong>safety</strong>, this paper will focus only on <strong>communication</strong>-related issues.20


NEED FOR FUTURE RESEARCH ABOUT COMMUNICATIONSeveral areas of potential study st<strong>and</strong> out as need<strong>in</strong>g future research to f<strong>in</strong>d their impacton <strong>aviation</strong> <strong>safety</strong>, <strong>in</strong>clud<strong>in</strong>g <strong>communication</strong> dur<strong>in</strong>g emergency <strong>and</strong> evacuation situations,<strong>in</strong>terpersonal variables that affect <strong>communication</strong> <strong>in</strong> an aircraft, particularly<strong>communication</strong> between flight crews <strong>and</strong> flight attendants, language <strong>and</strong> mean<strong>in</strong>gdifferences with<strong>in</strong> the cockpit <strong>and</strong> between the cockpit <strong>and</strong> cab<strong>in</strong> crew <strong>and</strong> betweencockpit <strong>and</strong> ATC (especially those lead<strong>in</strong>g to ambiguity <strong>and</strong> distortion), <strong>and</strong> how tocreate greater clarity <strong>in</strong> such <strong>communication</strong> <strong>in</strong>teractions.In the team <strong>and</strong> organizational sett<strong>in</strong>g roles play a critical part <strong>in</strong> <strong>communication</strong><strong>in</strong>teractions. Research concern<strong>in</strong>g the <strong>communication</strong> implications of roles <strong>and</strong> rolerelationships would provide an important advance <strong>in</strong> knowledge about <strong>communication</strong><strong>in</strong>teractions <strong>in</strong> the cockpit, between the cockpit <strong>and</strong> the cab<strong>in</strong>, <strong>and</strong> from a management<strong>and</strong> organizational perspective concern<strong>in</strong>g <strong>aviation</strong> <strong>safety</strong> <strong>and</strong> a culture of <strong>safety</strong>. Nevile(2006) provides several valuable directions such research about roles <strong>in</strong> the <strong>aviation</strong><strong>safety</strong> environment could take.Allied with the concept of roles is that of crew member’s <strong>communication</strong> style based onthose roles; for example the use of assertiveness versus <strong>in</strong>directness <strong>in</strong> communicat<strong>in</strong>g<strong>in</strong>formation. Because there is disagreement as to the efficacy of assertiveness versus<strong>in</strong>directness, there is def<strong>in</strong>itely a need for greater research to clear up the nature ofpoliteness <strong>and</strong> <strong>in</strong>directness <strong>in</strong> <strong>communication</strong> <strong>in</strong> the <strong>aviation</strong> environment, <strong>in</strong>clud<strong>in</strong>glook<strong>in</strong>g at the issue from a situational perspective. More research <strong>in</strong>to this seem<strong>in</strong>gcontradiction is needed to clarify <strong>and</strong> explicate this important area of team <strong>in</strong>teraction,both <strong>in</strong> the cockpit <strong>and</strong> between flight crew <strong>and</strong> cab<strong>in</strong> crew. Also, given the perceivedneed for assertive <strong>communication</strong> behavior on the part of cab<strong>in</strong> crew members <strong>in</strong> anemergency, either directed toward passengers or to overcome the reticence <strong>in</strong>herent <strong>in</strong> theflight attendant’s dilemma (to not convey needed <strong>in</strong>formation to the flight deck), research<strong>in</strong>to the effects of such assertive behavior on the part of flight attendants <strong>and</strong> how thatbehavior is perceived by passengers <strong>and</strong> pilots would prove to be worthwhile.Because the <strong>safety</strong> of any flight depends on effective team <strong>in</strong>teraction, research <strong>in</strong>to<strong>in</strong>terpersonal <strong>communication</strong> variables <strong>in</strong> the cockpit <strong>and</strong> <strong>in</strong> cab<strong>in</strong>-flight crew <strong>in</strong>teractionis essential, but is also a difficult proposition. The transitory nature of the relationshipsthat are established—<strong>and</strong> then quickly broken—among aircraft crews make forchalleng<strong>in</strong>g <strong>communication</strong> <strong>and</strong> <strong>communication</strong> research. It is probably most fruitful toresearch the types of <strong>communication</strong> that flight attendants <strong>and</strong> pilots perceive asestablish<strong>in</strong>g rapport, trust, <strong>and</strong> credibility <strong>in</strong> such teams. A survey of pilot <strong>and</strong> flightattendant preferences for certa<strong>in</strong> types of <strong>communication</strong>, particularly dur<strong>in</strong>g brief<strong>in</strong>gs,might be a first step <strong>in</strong> discover<strong>in</strong>g how a positive, supportive <strong>communication</strong> climate canbe established <strong>in</strong> the momentary aircraft crew relationship. Chute <strong>and</strong> Wiener (1995)allude to the need for this type of research when they note that: “Further research needs tobe done to measure the quantity <strong>and</strong> quality of <strong>in</strong>teraction that occurs with greaterfamiliarity <strong>and</strong> the impact on <strong>aviation</strong> <strong>safety</strong>” (p. 13).21


Very little has been written about <strong>communication</strong> issues <strong>in</strong> <strong>aviation</strong> ma<strong>in</strong>tenance <strong>and</strong><strong>in</strong>spection. The FAA did sponsor a two day meet<strong>in</strong>g <strong>in</strong> December 1989 which focusedon <strong>in</strong>formation exchange <strong>and</strong> <strong>communication</strong> <strong>in</strong> the ma<strong>in</strong>tenance area (Parker &Shepherd, 1990). Latorella <strong>and</strong> Prabhu (2000) note that <strong>communication</strong> is a contribut<strong>in</strong>gfactor to error <strong>in</strong> <strong>aviation</strong> ma<strong>in</strong>tenance. Some research regard<strong>in</strong>g <strong>communication</strong> <strong>in</strong> thema<strong>in</strong>tenance arena would be worthwhile, especially <strong>in</strong>to the effectiveness of writtendocuments which Piotrowski (1990) amd Majoros (1990) ma<strong>in</strong>ta<strong>in</strong> is an important part ofma<strong>in</strong>tenance <strong>communication</strong>. Aviation ma<strong>in</strong>tenance is an area where jargon <strong>and</strong>acronyms abound (Taylor, 1990). It would be important to <strong>in</strong>vestigate how the usejargon <strong>and</strong> acronyms impacts <strong>aviation</strong> <strong>safety</strong> with<strong>in</strong> ma<strong>in</strong>tenance itself <strong>and</strong> from a widerperspective.These suggestions are but a few that might be important to <strong>in</strong>vestigate regard<strong>in</strong>g theeffects of <strong>communication</strong> <strong>in</strong> <strong>aviation</strong> <strong>safety</strong>. Given the critical nature of <strong>communication</strong>many other research areas with<strong>in</strong> the cockpit, the cab<strong>in</strong>, <strong>and</strong> <strong>in</strong>teractions between airl<strong>in</strong>ecrew <strong>and</strong> other parts of the <strong>aviation</strong> system are ripe for research study.THE NEED FOR COMMUNICATION TRAININGThere have been numerous calls for <strong>communication</strong> tra<strong>in</strong><strong>in</strong>g, both as an <strong>in</strong>dependenteffort <strong>and</strong> as part of Crew Resource Management (CRM) for flight crews <strong>and</strong> for flightattendants (Baker & Frost; 1994; Butler, 1993; Chidester & Vaughn, 1994; Chute &Wiener, 1996; Edwards, 1992; Federal Aviation Adm<strong>in</strong>istration, 1988, 2004; Grommes<strong>and</strong> Dietrich, 2002; Helmreich, 2000; Sexton & Helmreich, 2000; Young, 1994).Perhaps, more important have been the calls for jo<strong>in</strong>t pilot-flight attendant tra<strong>in</strong><strong>in</strong>g(Baker & Frost, 1994; Butler, 1993; Chidester & Vaughn, 1994; Chute & Wiener, 1995,1996; ETSC, 1996; Federal Aviation Adm<strong>in</strong>istration, 2004; Helmreich, Wiener, & Kanki,1993; Kayten, 1993; Murphy, 2001; Moshansky, 1994, NTSB, 2000). “We must teachcrews that <strong>communication</strong> <strong>and</strong> cooperation are <strong>safety</strong> issues” (Chute, Wiener, Dunbar, &Hoang, 1996, p. 17).Flight <strong>and</strong> cab<strong>in</strong> crew, while a critical part of the <strong>aviation</strong> environment, should not be theonly focus of <strong>communication</strong> tra<strong>in</strong><strong>in</strong>g as part of an <strong>aviation</strong> <strong>safety</strong> tra<strong>in</strong><strong>in</strong>g program.Flight Safety Foundation (2000) notes that tra<strong>in</strong><strong>in</strong>g programs should <strong>in</strong>clude specialemphasis on pilot controller <strong>communication</strong>. Thomas (2005b) <strong>and</strong> Thomas <strong>and</strong> Petrilli(2004) argue for <strong>communication</strong> tra<strong>in</strong><strong>in</strong>g as part of error management. Latorella <strong>and</strong>Prabhu (2000) <strong>and</strong> Petrowski (1990) note that the importance of <strong>communication</strong> <strong>in</strong><strong>aviation</strong> ma<strong>in</strong>tenance tra<strong>in</strong><strong>in</strong>g. Baron (2002) emphasizes the importance of provid<strong>in</strong>gtra<strong>in</strong><strong>in</strong>g about runway <strong>in</strong>cursions for pilots, controllers, <strong>and</strong> ground vehicle operators.Etem & Patten (1998) suggest the need for <strong>communication</strong> tra<strong>in</strong><strong>in</strong>g <strong>in</strong> flight <strong>in</strong>struction.However, such calls for tra<strong>in</strong><strong>in</strong>g generally do not often <strong>in</strong>clude or <strong>in</strong>dicate which<strong>communication</strong> topics are needed, especially when it comes to <strong>in</strong>terpersonal<strong>communication</strong> tra<strong>in</strong><strong>in</strong>g; nor are the specific subtopics needed to help <strong>in</strong>crease<strong>communication</strong> effectiveness generally explicated. The Federal Aviation Adm<strong>in</strong>istration22


(2004) offers some general <strong>communication</strong> topics, which this paper will exp<strong>and</strong> uponwith regard to <strong>communication</strong> tra<strong>in</strong><strong>in</strong>g, <strong>in</strong>clud<strong>in</strong>g <strong>in</strong>terpersonal <strong>communication</strong>, listen<strong>in</strong>gskills, decision-mak<strong>in</strong>g skills, <strong>and</strong> conflict management, though they did <strong>in</strong>dicate, asnoted above that cockpit-cab<strong>in</strong> crew <strong>communication</strong> coord<strong>in</strong>ation cont<strong>in</strong>ues to challengethe <strong>aviation</strong> system (Federal Aviation Adm<strong>in</strong>istration, 2004). The Federal AviationAdm<strong>in</strong>istration (2004) also offers some specific areas where jo<strong>in</strong>t cab<strong>in</strong>-cockpit<strong>communication</strong> tra<strong>in</strong><strong>in</strong>g can focus, <strong>in</strong>clud<strong>in</strong>g pre-flight brief<strong>in</strong>gs, post <strong>in</strong>cident <strong>and</strong>accident procedures, sterile cockpit procedures, notifications <strong>and</strong> pre-flight, pre-l<strong>and</strong><strong>in</strong>g,<strong>and</strong> turbulence passenger-h<strong>and</strong>l<strong>in</strong>g issues.In addition, the Federal Aviation Adm<strong>in</strong>istration (2004) notes that the “importance ofclear <strong>and</strong> unambiguous <strong>communication</strong> must be stressed <strong>in</strong> all tra<strong>in</strong><strong>in</strong>g activities<strong>in</strong>volv<strong>in</strong>g pilots, flight attendants, <strong>and</strong> aircraft dispatchers” (p. 10). As noted previously<strong>communication</strong> is a two-way transaction, not a one-way transfer. Thus the concepts ofperception <strong>and</strong> mean<strong>in</strong>g are important to <strong>in</strong>clude <strong>in</strong> any <strong>communication</strong> tra<strong>in</strong><strong>in</strong>g. Wecommunicate about the world <strong>in</strong> the way we perceive it, therefore, everyone <strong>in</strong> the<strong>aviation</strong> <strong>safety</strong> system needs to underst<strong>and</strong> how perception operates <strong>and</strong> how peoplediffer, sometimes radically, <strong>in</strong> the ways they perceive a situation.Layered upon differ<strong>in</strong>g perceptions is the concept that when we communicate about theworld, we do so <strong>in</strong> symbolically, so that we give mean<strong>in</strong>g to our perceptions. As we haveseen, people will <strong>in</strong>terpret messages <strong>in</strong> such a way that makes sense to them <strong>and</strong> makessense of the world around them. George (1993) <strong>and</strong> Matchette (1995) provide severalsuggestions, some <strong>in</strong>clud<strong>in</strong>g the use or misuse of jargon, for improv<strong>in</strong>g <strong>communication</strong>between pilots <strong>and</strong> controllers that can be <strong>in</strong>corporated <strong>in</strong>to any <strong>communication</strong> tra<strong>in</strong><strong>in</strong>gfor <strong>aviation</strong> <strong>safety</strong>. Thus, the areas of perception, language (<strong>in</strong>clud<strong>in</strong>g mean<strong>in</strong>g <strong>and</strong>jargon) need to be part of any <strong>communication</strong> tra<strong>in</strong><strong>in</strong>g for <strong>aviation</strong> <strong>safety</strong>. As we<strong>in</strong>dicated earlier, feedback <strong>and</strong> ask<strong>in</strong>g questions are critical to greater success <strong>and</strong>effectiveness <strong>in</strong> our <strong>communication</strong> <strong>in</strong>teractions. Majoros (1990) re<strong>in</strong>forces the need forfeedback as one method to improve <strong>communication</strong> effectiveness.In addition to the exploration of the effects of mean<strong>in</strong>g <strong>and</strong> jargon on <strong>communication</strong>,two other related concepts need to be <strong>in</strong>cluded: message distortion <strong>and</strong> <strong>in</strong>formationoverload—<strong>and</strong> how to m<strong>in</strong>imize them. As much as we underst<strong>and</strong> <strong>and</strong> desire to haveclear <strong>and</strong> unambiguous <strong>communication</strong>, especially regard<strong>in</strong>g <strong>aviation</strong> <strong>safety</strong> issues, giventhe nature of language <strong>and</strong> human <strong>in</strong>teraction, we can only hope to m<strong>in</strong>imize messagedistortion <strong>and</strong> <strong>in</strong>formation overload. Underst<strong>and</strong><strong>in</strong>g these important <strong>communication</strong>barriers <strong>and</strong> how to deal with them effectively are needed <strong>in</strong> cab<strong>in</strong> <strong>safety</strong> tra<strong>in</strong><strong>in</strong>g. As faras <strong>in</strong>terpersonal <strong>communication</strong> tra<strong>in</strong><strong>in</strong>g is concerned, more <strong>in</strong> depth treatment of suchareas as establish<strong>in</strong>g a positive, supportive <strong>communication</strong> climate, underst<strong>and</strong><strong>in</strong>g howtrust <strong>and</strong> credibility are achieved, conflict management skills, <strong>and</strong> active listen<strong>in</strong>g isrequired.The process of conflict, underly<strong>in</strong>g reasons for conflict, <strong>and</strong> effective <strong>communication</strong>behaviors dur<strong>in</strong>g conflict are also crucial topics <strong>in</strong> this area of <strong>aviation</strong> <strong>safety</strong> tra<strong>in</strong><strong>in</strong>g.For example cab<strong>in</strong> crew assertiveness—with respect to evacuations, poor passenger23


ehavior <strong>and</strong> air rage, <strong>and</strong> reticence to convey important <strong>safety</strong> <strong>in</strong>formation to thecockpit—is an <strong>in</strong>tegral aspect of the conflict management portion of <strong>communication</strong>tra<strong>in</strong><strong>in</strong>g. Like any other <strong>communication</strong> behavior, conflict management requires asituational perspective. The conflict management <strong>and</strong> assertiveness portions of thetra<strong>in</strong><strong>in</strong>g will take this concept <strong>in</strong>to account, for example, when to be assertive, when to beaccommodative, <strong>and</strong> when other <strong>communication</strong> behaviors might be appropriate. Thissituational nature of conflict management will also provide a thought provok<strong>in</strong>gopportunity for when flight <strong>and</strong> cab<strong>in</strong> crew need to be assertive <strong>and</strong> when <strong>in</strong>directness ormitigation is a more effect method of communicat<strong>in</strong>g.Tra<strong>in</strong><strong>in</strong>g with regard to establish<strong>in</strong>g a positive supportive climate needs to explore suchtopics as defensive <strong>communication</strong> <strong>and</strong> disconfirm<strong>in</strong>g messages. Gibb (1961) notes thata defensive <strong>communication</strong> climate is extremely disruptive to the <strong>in</strong>terpersonal<strong>communication</strong> process. In fact a negative climate can make effective team<strong>communication</strong> very difficult, if not impossible. Communication tra<strong>in</strong><strong>in</strong>g for cockpit <strong>and</strong>cab<strong>in</strong> crew should <strong>in</strong>clude the underst<strong>and</strong><strong>in</strong>g of defensive <strong>communication</strong>, disconfirm<strong>in</strong>gmessages, <strong>and</strong> the practice of supportive <strong>and</strong> confirm<strong>in</strong>g messages. Defensive <strong>and</strong>disconfirm<strong>in</strong>g messages are basically ones that ignore others <strong>and</strong> treats them as if thy donot exist or do not matter. Supportive <strong>and</strong> confirm<strong>in</strong>g messages let others know thatthey—<strong>and</strong> their ideas—are worthwhile <strong>and</strong> valuable. Trust, too, is an important aspect ofa positive, supportive climate, one that can lead to much greater rapport, cohesion, <strong>and</strong>team coord<strong>in</strong>ation for the flight crew as a whole unit. Thus, underst<strong>and</strong><strong>in</strong>g trustbehaviors <strong>and</strong> messages needs to be an <strong>in</strong>tegral part of this aspect of tra<strong>in</strong><strong>in</strong>g.The brief<strong>in</strong>g process offers an ideal opportunity for jo<strong>in</strong>t cab<strong>in</strong>-cockpit <strong>communication</strong>tra<strong>in</strong><strong>in</strong>g to <strong>in</strong>tegrate the concepts of trust, supportiveness, teamwork, <strong>and</strong> a positive<strong>communication</strong> climate <strong>in</strong> tra<strong>in</strong><strong>in</strong>g. It is <strong>in</strong> this aspect of <strong>communication</strong> between cab<strong>in</strong><strong>and</strong> cockpit crews that many problems occur, potentially sett<strong>in</strong>g a negative tone for therest of the flight. Likewise, underst<strong>and</strong><strong>in</strong>g <strong>and</strong> utiliz<strong>in</strong>g <strong>communication</strong> that engenders apositive climate dur<strong>in</strong>g the brief<strong>in</strong>g process can create a collaborative <strong>and</strong> productiveatmosphere for the flight.Active listen<strong>in</strong>g comprises the f<strong>in</strong>al part of <strong>communication</strong> <strong>in</strong> <strong>aviation</strong> <strong>safety</strong> tra<strong>in</strong><strong>in</strong>g.This aspect of the tra<strong>in</strong><strong>in</strong>g could cover the importance of listen<strong>in</strong>g, the cost of poorlisten<strong>in</strong>g, the process of listen<strong>in</strong>g, barriers to effective listen<strong>in</strong>g, <strong>and</strong> steps to betterlisten<strong>in</strong>g. Barriers to effective listen<strong>in</strong>g covers such topics as lack of concentration,prejudg<strong>in</strong>g messages, mak<strong>in</strong>g unchecked assumptions, rehears<strong>in</strong>g a response, focus<strong>in</strong>g onstyle <strong>and</strong> delivery, unconscious projection, <strong>and</strong> a w<strong>in</strong>/lose perspective on listen<strong>in</strong>g. Stepsto better listen<strong>in</strong>g covers such topics as a w<strong>in</strong>/w<strong>in</strong> perspective to listen<strong>in</strong>g, focus,patience, <strong>and</strong> ask<strong>in</strong>g questions. The tra<strong>in</strong><strong>in</strong>g would <strong>in</strong>clude practice <strong>in</strong> such importantlisten<strong>in</strong>g skills as paraphras<strong>in</strong>g, respond<strong>in</strong>g, <strong>and</strong> feedback. Active, effective listen<strong>in</strong>gskills are crucial <strong>in</strong> creat<strong>in</strong>g the best possible <strong>communication</strong> environment for theexchange of accurate, unambiguous messages that m<strong>in</strong>imize distortion <strong>and</strong> overload.Such a <strong>communication</strong> environment also contributes to a positive, supportive climatewhere rapport <strong>and</strong> trust can develop <strong>and</strong> thrive.24


As important as specific topics needed for tra<strong>in</strong><strong>in</strong>g for effective <strong>aviation</strong> <strong>safety</strong><strong>communication</strong> are, the methodologies required for deliver<strong>in</strong>g such tra<strong>in</strong><strong>in</strong>g are alsocritical. As with most <strong>communication</strong> tra<strong>in</strong><strong>in</strong>g, there should be limited didacticpresentation. Rather, there needs to be a great deal of <strong>in</strong>teraction, practice, <strong>and</strong><strong>in</strong>trospection. The best methods for this type of tra<strong>in</strong><strong>in</strong>g would <strong>in</strong>clude experientialexercises, practic<strong>in</strong>g <strong>communication</strong> skills, role play<strong>in</strong>g, small group <strong>and</strong> team build<strong>in</strong>gexercises <strong>and</strong> discussion, case study scenarios, <strong>and</strong> self-assessment tools (for example,the Thomas-Kilman Conflict Mode Instrument)—all centered around <strong>communication</strong> <strong>in</strong><strong>aviation</strong> <strong>safety</strong>, with particular emphasis on <strong>communication</strong> specific, applicable situation,such as <strong>in</strong> the cockpit, the cab<strong>in</strong>, <strong>and</strong> between cab<strong>in</strong> <strong>and</strong> flight deck crews.ASRS publications, especially Callback <strong>and</strong> Directl<strong>in</strong>e, afford abundant examples of bothpoor <strong>and</strong> good <strong>communication</strong> <strong>in</strong> the <strong>aviation</strong> system that can be used to create casestudies <strong>and</strong> scenarios which can be used to ga<strong>in</strong> <strong>in</strong>sight <strong>in</strong>to effective <strong>communication</strong>skills. These actual <strong>communication</strong> occurrences <strong>in</strong> the <strong>aviation</strong> <strong>safety</strong> environment needto be <strong>in</strong>tegrated <strong>in</strong>to cab<strong>in</strong> <strong>safety</strong> <strong>communication</strong> tra<strong>in</strong><strong>in</strong>g. Young (1994) <strong>and</strong> FlightSafety Foundation (1994), <strong>in</strong> addition to numerous ASRS reports, provide <strong>in</strong>cidents <strong>in</strong>which cockpit crew, flight attendants, ATCs, <strong>and</strong> ma<strong>in</strong>tenance personnel were able to usetheir good sense <strong>in</strong> emergency or potentially unsafe situations <strong>in</strong> order to prevent possibletragedies. While examples of poor <strong>communication</strong> can provide excellent examples forscenarios that would be useful for tra<strong>in</strong><strong>in</strong>g, so too should such examples of good<strong>communication</strong> be used for tra<strong>in</strong><strong>in</strong>g purposes.LESSONS FOR AIR SAFETY INVESTIGATORSMuch of the discussion <strong>in</strong> this presentation has focused on the <strong>aviation</strong> <strong>safety</strong> milieu <strong>in</strong>general, especially on <strong>communication</strong> <strong>in</strong> the cockpit <strong>and</strong> between the cockpit <strong>and</strong> otheraspects of the system. There are <strong>lessons</strong> to be <strong>learned</strong> for air <strong>safety</strong> <strong>in</strong>vestigators <strong>in</strong> thisconversation.Harle (1995) argues that it is essential for air <strong>safety</strong> <strong>in</strong>vestigators to <strong>in</strong>tegrate humanfactors <strong>in</strong>formation. Given that <strong>communication</strong> is an critical aspect of human factors,then <strong>communication</strong> issues need also be <strong>in</strong>tegrated <strong>in</strong>to <strong>aviation</strong> <strong>safety</strong> <strong>in</strong>vestigations asone possible, if not at times, key aspect of the possible causes of accidents <strong>and</strong> <strong>in</strong>cidents.Sexton <strong>and</strong> Helmreich (2000) discuss the relationship between language use <strong>and</strong> flightoutcome measures. While their discussion was not directly <strong>in</strong>vestigation related, oneoutcome measure important to <strong>in</strong>vestigators is an accident <strong>and</strong> any potential underly<strong>in</strong>gfactors.Von Thaden <strong>and</strong> Steelman (2005) posit that the purpose of accident <strong>in</strong>vestigation is toidentify the process through which <strong>in</strong>teract<strong>in</strong>g <strong>and</strong> underly<strong>in</strong>g factors lead to an accident;they argue that “. . .if accident <strong>in</strong>vestigators lack a cohesive def<strong>in</strong>ition of human factorsissues, the <strong>in</strong>vestigation <strong>in</strong>to human performance may be unsystematic, <strong>in</strong>complete, orleave significant po<strong>in</strong>ts unresolved” (p. 1). As we have seen, <strong>communication</strong> is not onlya critical part of human factors, but is <strong>in</strong> <strong>and</strong> of itself a crucial aspect of <strong>aviation</strong> accidents25


due to poor <strong>communication</strong>. Thus, it is essential for accident <strong>in</strong>vestigators to have anunderst<strong>and</strong><strong>in</strong>g of the effects of <strong>communication</strong> <strong>in</strong> the <strong>aviation</strong> <strong>safety</strong> environment to beable to fully <strong>in</strong>vestigate the causes of an accident, whether primary or secondary.CONCLUSIONThis paper exam<strong>in</strong>ed the status of <strong>communication</strong> as a crucial aspect of <strong>aviation</strong> <strong>safety</strong>.Effective <strong>communication</strong> is essential for <strong>aviation</strong> <strong>safety</strong>, whether with<strong>in</strong> the cockpit, thecab<strong>in</strong>, ma<strong>in</strong>tenance, or between flight deck <strong>and</strong> other parts of the <strong>aviation</strong> system.Effective crew coord<strong>in</strong>ation is fundamentally dependent upon effective <strong>communication</strong>.Teach<strong>in</strong>g effective <strong>communication</strong> is an essential requirement for <strong>aviation</strong> <strong>safety</strong> tra<strong>in</strong><strong>in</strong>gfor all <strong>in</strong>volved <strong>in</strong> this enterprise. Short of ground<strong>in</strong>g all aircraft, it is probablyimpossible to elim<strong>in</strong>ate the risk of <strong>in</strong>effective <strong>communication</strong> lead<strong>in</strong>g to <strong>in</strong>cidents <strong>and</strong>accidents. However, it is possible to m<strong>in</strong>imize such risk by creat<strong>in</strong>g an awareness of theimportance of effective <strong>communication</strong>, <strong>in</strong>tegrat<strong>in</strong>g such awareness <strong>in</strong>to our th<strong>in</strong>k<strong>in</strong>g, <strong>and</strong>apply<strong>in</strong>g this <strong>in</strong>tegration <strong>in</strong>to a proactive approach to communicat<strong>in</strong>g by <strong>in</strong>corporat<strong>in</strong>geffective <strong>communication</strong> behaviors <strong>in</strong>to all aspects of the <strong>aviation</strong> <strong>safety</strong> environment.An article <strong>in</strong> the ASRA Directl<strong>in</strong>e perhaps said it best with regard to <strong>communication</strong> <strong>in</strong><strong>aviation</strong> <strong>safety</strong> when not<strong>in</strong>g that <strong>communication</strong> errors are the most frequently citedproblems <strong>in</strong> the <strong>in</strong>cidents that are reported to ASRS:Communication problems take a variety of forms. Equipment deficiencies,phraseology, similar call signs, speech rated, blocked transmission, <strong>and</strong> failure ofthe readback/hearback process are just a few types of <strong>communication</strong> problems.The subject is too broad to be covered by any degree <strong>in</strong> this article, but I do wantto make the po<strong>in</strong>t that <strong>communication</strong> problems often lead to a “FlawedInformation Transfer” (FIT), <strong>and</strong> if the flawed <strong>in</strong>formation transfer is notcorrected soon enough, the result may be an “Occasional Semi-HystericalInformation Transfer” (acronym unknown) (George, 1993, June, p. 16).26


REFERENCESAdams, D. (2006). A Layman’s Introduction to Human Factors <strong>in</strong> Aircraft Accident <strong>and</strong>Incident Investigation. ATSB Information Paper B2006/0094, ACT Australia. Electronicversion retrieved March 6, 2007 fromhttp://www.atsb.gov.au/publications/2006/pdf/B20060094.pdfAustralian Transport Safety Bureau (2005). Dangerous distraction. ATSB AviationResearch Investigation Report B2004/0324. Electronic version retrieved March 14, 2007from http://www.atsb.gov.au/publications/2005/pdf/Distraction_report.pdfAviation Safety Letter (2004). Scrut<strong>in</strong>iz<strong>in</strong>g <strong>aviation</strong> culture: professional courtesy. CivilAviation, Transport Canada. Electronic version retrieved November 15, 2004 from:http://www.tc.gc.ca/civil<strong>aviation</strong>/system<strong>safety</strong>/newsletters/tp185/1-04/538.htmBaker, B. (1985, April 11). Wrong-way Mike, f<strong>in</strong>d<strong>in</strong>g fame pa<strong>in</strong>ful. Los Angeles Times,Metro, Part 2, p. 1.Baker, R. & Frost, K. (1994). Australian Airl<strong>in</strong>es Pilot/Flight Attendant Integrated CrewTra<strong>in</strong><strong>in</strong>g. The CRM Advocate, 94 (1). Electronic version retrieved December 10, 2004from:http://s92270093.onl<strong>in</strong>ehome.us/crmdevel/resources/crmadvocate/94_1/94_1/htmBarkow, B. & Rutenberg, V. (2002). Improv<strong>in</strong>g the effectiveness of aircraft cab<strong>in</strong> <strong>safety</strong>brief<strong>in</strong>gs. Transportation Development Centre (TP13973E). Montreal, Canada.Electronic version retrieved November 12, 2004 fromhttp://www.tc.gc.ca/tdc/publication/pdf/13900/13973e.pdfBarnard, C.I. (1938). The functions of the executive. Boston, MA: Harvard UniversityPress.Baron, R. (2002). Runway <strong>in</strong>cursions: where are we? Airl<strong>in</strong>eSatety.Com. Electronicversion retrieved March 7, 2007 fromhttp://airl<strong>in</strong>e<strong>safety</strong>.com/editorials/RunwayIncursions.htmBill<strong>in</strong>gs, C.E. & Cheaney, E.S. (1981). The <strong>in</strong>formation transfer problem: summary <strong>and</strong>comments. In C.E. Bill<strong>in</strong>gs & E.S. Cheaney (Eds.), Information transfer problems <strong>in</strong> the<strong>aviation</strong> system (NASA Technical Paper 1875; pp. 85-94). Moffett Field, CA: NASA-Ames Research Center.Bill<strong>in</strong>gs, C.E. & Reynard, W.D. (1981). Dimensions of the <strong>in</strong>formation transfer problem.In C.E. Bill<strong>in</strong>gs & E.S. Cheaney (Eds.), Information transfer problems <strong>in</strong> the <strong>aviation</strong>system (NASA Technical Paper 1875; pp. 9-15). Moffett Field, CA: NASA-AmesResearch Center.27


Burian, B.K., Dismukes, R.K., & Barshi, I. (2003). The Emergency <strong>and</strong> AbnormalSituations Project. In T. McCarthy (Ed.), Proceed<strong>in</strong>gs of the ISASI 2003 Conference (pp.26-33). Wash<strong>in</strong>gton, D.C. Electronic version retrieved March 13, 2007 fromhttp://hsi.arc.nasa.gov/publications/20051028110357_EAS_Project.pdfButler, R.E. (1993). LOFT: full-mission stimulation as crew resource <strong>in</strong> managementtra<strong>in</strong><strong>in</strong>g. In E. Wiener, B. Kanki, & R. Helmreich (Eds.), Cockpit resource management(pp. 231-259). San Diego, CA: Academic Press.Callback (1984, December). 66Callback (1995, October). 197.Callback (1996, November). 209.Callback (1997, October). 220.Callback (1998, March). 225.Callback (1998, September). 231.Callback (1998, December). 234.Callback (1999, August). 242.Callback (1999, September). 243.Callback (2000, April). 250.Callback (2001, March). 259.Callback (2001, May). 261.Callback (2001, August). 264.Callback (2002, October). 277.Callback (2003, March). 282.Callback (2003, June). 285.Callback (2003, October). 289.Callback (2004, February). 293.Callback (2004, April). 295.28


Callback (2004, July). 298.Callback (2005, May). 308.Callback (2005, November).313.Callback (2007, March). 237.Chidester, T. & Vaughn, L. (1994). Pilot flight attendant coord<strong>in</strong>ation. The CRMAdvocate. 94, (1). ”. The CRM Advocate 94 (1), January-November. Electronic versionretrieved December 11, 2004 from:http://s92270093.onl<strong>in</strong>ehome.us/crmdevel/resources/crmadvocate/94_1/94_1.htmChute, R.D. (2001). Synergy <strong>in</strong> an emergency: The <strong>in</strong>terface between flight-deck <strong>and</strong>cab<strong>in</strong> crews. Paper presented at the 13 th Airbus Human Factors Symposium, Toronto,Canada, July, 2001. Electronic version retrieved December 23, 2004 from:http://cab<strong>in</strong>factors.com/pages/Synergy_airbus.htmChute, R.D, & Wiener, E.L. (1994). Cockpit <strong>and</strong> cab<strong>in</strong> crews: do conflict<strong>in</strong>g m<strong>and</strong>atesput them on a collision course? Cab<strong>in</strong> Crew Safety, 29 (2), 1-8.Chute, R.D, & Wiener, E.L. (1995). Cockpit /cab<strong>in</strong> <strong>communication</strong>: I. A tale of twocultures. International Journal of Aviation Psychology, 5 (3), 257-276. Electronicversion retrieved December 23, 2004 from:http://cab<strong>in</strong>factors.com/pages/tale_of_two_cultures.htmChute, R.D., & Wiener, E.L. (1996). Cockpit /cab<strong>in</strong> <strong>communication</strong>: II. Shall we tell thepilots. International Journal of Aviation Psychology, 6 (3), 211-231. Electronic versionretrieved 29 December, 2004 from:http://cab<strong>in</strong>factors.com/pages/Shall_We_Tell_The_Pilots.htmChute, R.D., & Wiener, E.L., Dunbar, M.G., & Hoang, V.R. (1995). Cockpit /cab<strong>in</strong> crewperformance: recent research. Proceed<strong>in</strong>gs of the 48 th International Air Safety Sem<strong>in</strong>ar,Seattle, WA. November, 1995. Electronic version retrieved December 29, 2004 from:http://cab<strong>in</strong>factors.com/pages/CockpitCab<strong>in</strong>CrewPerformance.htmCush<strong>in</strong>g, S. (1994). Fatal words: <strong>communication</strong> clashes <strong>and</strong> aircraft crashes. Chicago,IL: The University of Chicago Press.Darby, R. (2006). Listen up! Aviation Safety World, 1 (5), 25-27. Electronic versionretrieved March 12, 2007 fromhttp://www.flight<strong>safety</strong>.org/asw/nov06/asw_nov06_p25-27.pdfDepartment for Transport (1990). Report on the accident to Boe<strong>in</strong>g 737-400-G-OBMEnear Kegworth, Leicestershire on 8 January 1989. Electronic version retrieved November29


15, 2004 from:http://www/dft.gov.uk/stellent/groups/dft_av<strong>safety</strong>/documents/page/dft_av<strong>safety</strong>_502831Dismukes, R. K., Young, G., & Sumwalt, R. (1998). Cockpit <strong>in</strong>terruptions <strong>and</strong>distractions: effective management requires a careful balanc<strong>in</strong>g act. ASRS Directl<strong>in</strong>e, 10,4-10.Edwards, M. (1992). Crew coord<strong>in</strong>ation problems persist, dem<strong>and</strong> new tra<strong>in</strong><strong>in</strong>gchallenges. Cab<strong>in</strong> Crew Safety, 27 (6), 1-5Etem, K. & Patten, M. (1998, December). Communications-related <strong>in</strong>cidents <strong>in</strong> general<strong>aviation</strong> dual flight tra<strong>in</strong><strong>in</strong>g. ASRS Directl<strong>in</strong>e, 10, 16-22.Federal Aviation Adm<strong>in</strong>istration (2004). Crew resource management. Advisory Circular120-51E. Wash<strong>in</strong>gton, D.C.Federal Aviation Adm<strong>in</strong>istration (1997). Human factors: FAA’s guidance <strong>and</strong> oversightof pilot crew resource management tra<strong>in</strong><strong>in</strong>g can be improved (GAO/RCED-98-7). UnitedStates General Account<strong>in</strong>g Office. November 1997. Wash<strong>in</strong>gton, D.C. Electronicversion retrieved March 14, 2007 from http://www.gao.gov/archive/1998/rc98007.pdfFEDERAL AVIATION ADMINISTRATION. (1988). Communication <strong>and</strong> coord<strong>in</strong>ationbetween flight crew members <strong>and</strong> flight attendants. Advisory Circular 120-48.Wash<strong>in</strong>gton, D.C.Faith, N. (1996). Black box: the further <strong>in</strong>vestigations. London: Macmillan PublishersLtd.Flight Safety Foundation (1994). Accident <strong>and</strong> <strong>in</strong>cident reports show importance of‘sterile cockpit’ compliance. Cab<strong>in</strong> Crew Safety 13 (7), 1-8.Flight Safety Foundation (2000). Pilot-Controller Communication, Flight Safety Digest,19 (8-11), 47-53. Electronic version retrieved March 20, 2007 from:http://www.flight<strong>safety</strong>.org/fsd/fsd_aug-nov00.pdfFlight Safety Foundation (2003). Communication problems contribute to misperceptionsof evacuation urgency. Cab<strong>in</strong> Crew Safety 38 (2), 1-8Flight Safety Information (2004). Language proficiency requirements. Flight SafetyInformation Quarterly Journal. Electronic version retrieved May 1, 2007 fromhttp://www.fs<strong>in</strong>fo.org/docs/FSI%202Q04.pdfFoushee, H.C. (1982). The role of <strong>communication</strong>s, socio-psychological, <strong>and</strong> personalityfactors <strong>in</strong> the ma<strong>in</strong>tenance of crew coord<strong>in</strong>ation. Aviation, Space, <strong>and</strong> EnvironmentalMedic<strong>in</strong>e, 53, 1062-1066.30


Foushee, H.C. & Manos, K.L. (1981), Information transfer with<strong>in</strong> the cockpit: problems<strong>in</strong> <strong>in</strong>tracockpit <strong>communication</strong>s. In C.E. Bill<strong>in</strong>gs & E.S. Cheaney (Eds.), Informationtransfer problems <strong>in</strong> the <strong>aviation</strong> system (NASA Technical Paper 1875; pp. 63-72).Moffett Field, CA: NASA-Ames Research Center.George, D. (1993, March). The unexpected results of “expect” clearance technique.ASRS Directl<strong>in</strong>e, 4, 12-17.Gibb, J.R. (1961). Defensive <strong>communication</strong>. Journal of Communication, 11, 141-148.Grayson, R.L. & Bill<strong>in</strong>gs, C.E. (1981). Information transfer between air traffic control<strong>and</strong> aircraft: <strong>communication</strong> problems <strong>in</strong> flight operations. In C.E. Bill<strong>in</strong>gs & E.S.Cheaney (Eds.), Information transfer problems <strong>in</strong> the <strong>aviation</strong> system (NASA TechnicalPaper 1875; pp. 47-62). Moffett Field, CA: NASA-Ames Research Center.Grommes, P. & Dietrich, R. (2002). Coherence <strong>in</strong> operat<strong>in</strong>g room team <strong>and</strong> cockpit<strong>communication</strong>: a psychol<strong>in</strong>guistic contribution to applied l<strong>in</strong>guistics. In Alatis, J.E.Hamilton, H.E., & Tan, A.H. (Eds.) Round Table on Language <strong>and</strong> L<strong>in</strong>guistics 2000 (pp.190-219). Wash<strong>in</strong>gton, D.C.: Georgetown University Press. Electronic version retrievedMarch 12, 2007 from http://digital.georgetown.edu/gurt/2000/gurt_2000_14.pdfHarle, P.G. (1995). Investigation of Human Factors: the l<strong>in</strong>k to accident prevention. InN, McDonald, N. Johnson, & R. Fuller (Eds.), Applications of psychology to the <strong>aviation</strong>system: proceed<strong>in</strong>gs of the 21 st Conference of the European Association for AviationPsychology, Volume 1 (pp. 101-107). Cambridge, Great Brita<strong>in</strong>: University Press.Helmreich, R.L. (1997, May). Manag<strong>in</strong>g human error <strong>in</strong> <strong>aviation</strong>. Scientific American,62-67.Helmreich, R.L., & Foushee, H.C. (1993). Why crew resource management? Empirical<strong>and</strong> theoretical bases of human factors tra<strong>in</strong><strong>in</strong>g <strong>in</strong> <strong>aviation</strong>. In E. Wiener, B. Kanki, & R.Helmreich (Eds.), Cockpit resource management (pp. 3-45). San Diego, CA: AcademicPress.Helmreich, R. L., Wiener, E. L., & Kanki, B.G. (1993). The failure of crew resourcemanagement <strong>in</strong> the cockpit <strong>and</strong> beyond. In E. Wiener, R., B. Kanki, & Helmreich (Eds.),Cockpit resource management, (pp. 479-501). San Diego, CA: Academic Press.Kanki, B. G., & Palmer, M. T. (1993). Communication <strong>and</strong> crew, resource management.In E. Wiener, B. Kanki, & R. Helmreich (Eds.), Cockpit resource management (pp. 99-136). San Diego, CA: Academic Press.Kayten, P. (1993). The accident <strong>in</strong>vestigator’s perspective. In E. Wiener, R., B. Kanki, &Helmreich (Eds.), Cockpit resource management (pp. 283-314). San Diego, CA.Academic Press.31


Krifka, M., Martens, S., & Schwarz, F. (2003). Group <strong>in</strong>teraction <strong>in</strong> the cockpit: somel<strong>in</strong>guistic factors. In R. Dietrich (Ed.), Communication <strong>in</strong> High Risk Environments, (pp.75-101). Hamburg, Germany. Helmut Buske Verlag. Electronic version retrieved3/12/07 from http://amor.rz.hu-berl<strong>in</strong>.de/~h2816i3x/GihreLB-Krifka.pdfKrivonos, Paul D. (2005). Communication <strong>in</strong> aircraft cab<strong>in</strong> <strong>safety</strong>: <strong>lessons</strong> <strong>learned</strong> <strong>and</strong><strong>lessons</strong> required. Proceed<strong>in</strong>gs of the 22 nd Annual International Aircraft Cab<strong>in</strong> SafetySymposium. Los Angeles, CA.Latorella, K.A. & Prabhu, V. (2000). A review of human error <strong>in</strong> <strong>aviation</strong> ma<strong>in</strong>tenance<strong>and</strong> <strong>in</strong>spection. International Journal of Industrial Ergonomics, 26 (2), 133-161.L<strong>in</strong>de, C. (1988). The quantitative study of communicative success: politeness <strong>and</strong>accidents <strong>in</strong> <strong>aviation</strong> discourse. Language <strong>in</strong> Society, 17 (3), 375-399.Majoros, A. (1990). Human factors issues <strong>in</strong> manufacturers’ ma<strong>in</strong>tenance-related<strong>communication</strong>. In J.F. Parker, Jr. & W.T. Shepherd, (Eds.) Human Factors <strong>in</strong> AircraftMa<strong>in</strong>tenance <strong>and</strong> Inspection: Information Exchange <strong>and</strong> Communications (pp. 39-44).Wash<strong>in</strong>gton, D.C.: FAA (DOT/FAA/AM-90-14). Electronic version retrieved 4/7/07from http://amelia.db.erau.edu/reports/faa/am/AM90-14.pdfMatchette, R. (1995). Say what: non-st<strong>and</strong>ard phraseology <strong>in</strong>cidents. ASRS Directl<strong>in</strong>e, 7,18-24.Merritt, A. (1995). Fac<strong>in</strong>g the issue. CRM Advocate, 95(4). Electronic version retrieved12 November, 2004 from:http://s92270093.onl<strong>in</strong>ehome.us/crmdevel/resources/crmadvocate/95_4/95_4.htm#1Monan, B. (1991). Reedback/hearback. ASRS Directl<strong>in</strong>e, 1, 3-4.Monan, W.P. (1988). Human factors <strong>in</strong> air-carrier operations: the hearback problem.NASA Report CR 177398. Moffett Field, CA: National Aeronautics <strong>and</strong> SpaceAdm<strong>in</strong>istration.Moshansky, V.P. (1992). Commission of <strong>in</strong>quiry <strong>in</strong>to the Air Ontario crash at Dryden,Ontario. Toronto, Canada.Murphy, A. G. (2001). The flight attendant dilemma: An analysis of <strong>communication</strong> <strong>and</strong>sensemak<strong>in</strong>g dur<strong>in</strong>g <strong>in</strong>-flight emergencies. Journal of Applied Communication Research,29, 30-53.Nagel, D.C. (1988). Human error <strong>in</strong> <strong>aviation</strong> operations <strong>in</strong> E.L. Wiener & D. Nagel(Eds.), Human Factors <strong>in</strong> Aviation (pp. 263-303). San Diego, CA: Academic Press.Nevile, M (2006). Communication <strong>in</strong> context: a conversational analysis tool forexam<strong>in</strong><strong>in</strong>g recorded data <strong>in</strong> <strong>in</strong>vestigations of <strong>aviation</strong> occurrences. ATSB Research <strong>and</strong>32


Analysis Report B2005/0118, ACT Australia Electronic version retrieved March 6, 2007from http://www.atsb.gov.au/publications/2006/pdf/B20050118.pdfO’Hare, D., Wigg<strong>in</strong>s, M., Blatt, R., & Morrison, D. (1994). Cognitive failure analysis foraircraft <strong>in</strong>vestigation. Ergonomics, 37, 1855-1869.Parker, A. (2006). Public attitudes, perceptions, <strong>and</strong> behaviours toward cab<strong>in</strong> <strong>safety</strong><strong>communication</strong>s. Australian Transport Safety Bureau Research <strong>and</strong> Analysis ReportB2004/0238. Electronic version retrieved March 13, 2007 fromhttp://www.atsb.gov.au/publications/2006/pdf/B20040238.pdfParker, J.F. Jr. & Shepherd, W.T., (Eds.) (1990). Human Factors <strong>in</strong> Aircraft Ma<strong>in</strong>tenance<strong>and</strong> Inspection: Information Exchange <strong>and</strong> Communications. Wash<strong>in</strong>gton, D.C.: FAA(DOT/FAA/AM-90-14). Electronic version retrieved 4/7/07 fromhttp://amelia.db.erau.edu/reports/faa/am/AM90-14.pdfPiotrowski, D. (1990). FAA overview of Ma<strong>in</strong>tenance-related <strong>in</strong>formation exchange, <strong>in</strong>J.F., Jr. & W.T. Shepherd, (Eds.) Human Factors <strong>in</strong> Aircraft Ma<strong>in</strong>tenance <strong>and</strong>Inspection: Information Exchange <strong>and</strong> Communications (pp. 15-17). Wash<strong>in</strong>gton, D.C.:FAA (DOT/FAA/AM-90-14). Electronic version retrieved 4/7/07 fromhttp://amelia.db.erau.edu/reports/faa/am/AM90-14.pdfPr<strong>in</strong>zo, .V., Hendrix, A.M. & Hendrix, R. (2006). The Outcome of ATCMessage Complexity on Pilot Readback Performance. U.S. Department ofTransportation, Office of Aerospace Medic<strong>in</strong>e, DOT/FAA/AM-06/25. Wash<strong>in</strong>gton, DC:Electronic version retrieved March 16, 2007 from:http://www.faa.gov/library/reports/medical/oamtechreports/2000s/media/200625.pdfPr<strong>in</strong>zo, V.O. & Morrow, D.G. (2002). Improv<strong>in</strong>g pilot/air traffic control <strong>in</strong> general<strong>aviation</strong>. The <strong>in</strong>ternational journal of <strong>aviation</strong> psychology, 12, 341-357.Redd<strong>in</strong>g, W.C., & S<strong>in</strong>coff, M.Z. (1984). Corporate Manager’s Guide to BetterCommunication. Glenview, IL: Scott, Foresman.Report on Aviation Safety (1988). V. Language Barriers. Aviation Today: SpecialReport. Electronic version retrieved November 29, 2004 from:Http://www.<strong>aviation</strong>today.com.reports/V.htmRice, Sue. (2001, May-June). Analysis. Flight Safety Australia, 5 (3), 19.Ruffell Smith, H.P. (1979). A Simulator study of the <strong>in</strong>teraction of pilot workload witherrors, vigilance <strong>and</strong> decisions. (NASA Technical Memor<strong>and</strong>um 78482). Moffett Field,CA: NASA-Ames Research Center.Sexton, B.J. & Helmreich, R.L. (2000). Analyz<strong>in</strong>g cockpit <strong>communication</strong>: the l<strong>in</strong>ksbetween language, performance, error, <strong>and</strong> workload. Human Performance <strong>in</strong> Extreme33


Environments, 5, 63-68. Electronic version retrieved April 25, 2007 fromhttp://homepage.psy.utexas.edu/HomePage/Group/HelmreichLAB/Publications/pubfiles/pub243.pdfSchultz, J. (2002). Hear What They’re Say<strong>in</strong>g: The Influence Of Culture On CockpitCommunication. Quest, 5, 1. Electronic version retrieved April 24, 2007 fromhttp://www.odu.edu/ao/<strong>in</strong>stadv/quest/cockpitcommun.htmlSimon, H.A. (1965). Adm<strong>in</strong>istrative behavior: a study of decision mak<strong>in</strong>g processes <strong>in</strong>adm<strong>in</strong>istrative organizations. New York: The Free Press.Smith-Christensen, A. & Duckert, F. (1995). The multi-national crew: verbal <strong>and</strong> nonverbal<strong>communication</strong>, with special reference to <strong>safety</strong>. In N, McDonald, N. Johnson, &R. Fuller (Eds.), Applications of psychology to the <strong>aviation</strong> system: proceed<strong>in</strong>gs of the21 st Conference of the European Association for Aviation Psychology, Volume 1 (pp.180-184). Cambridge, Great Brita<strong>in</strong>: University Press.Sussman, L. & Krivonos, P.D. (1976). Reduc<strong>in</strong>g the distortion <strong>in</strong> upward distortion data.Paper presented at the meet<strong>in</strong>g of the Western Speech Communication Association, SanFrancisco, CA, November, 1976.Taneja, N. (2002). Human factors <strong>in</strong> aircraft accidents: a holistic approach to <strong>in</strong>terventionstrategies. Proceed<strong>in</strong>gs of the 46th Annual Meet<strong>in</strong>g of the Human Factors <strong>and</strong>Ergonomics Society. Santa Monica, CA. Electronic version retrieved March 13, 2007from http://www.humanfactors.uiuc.edu/Reports&PapersPDFs/humfac02/tanejahf02.pdfTaylor, J. (1990). Facilitation of <strong>in</strong>formation exchange among units with<strong>in</strong> <strong>in</strong>dustry. InJ.F. Parker, Jr. & W.T. Shepherd, (Eds.) Human Factors <strong>in</strong> Aircraft Ma<strong>in</strong>tenance <strong>and</strong>Inspection: Information Exchange <strong>and</strong> Communications (pp. 45-49). Wash<strong>in</strong>gton, D.C.:FAA (DOT/FAA/AM-90-14). Electronic version retrieved 4/7/07 fromhttp://amelia.db.erau.edu/reports/faa/am/AM90-14.pdfThomas, M.J.W. (2004a). Predictors of Threat <strong>and</strong> Error Management: Identification ofCore Nontechnical Skills <strong>and</strong> Implications for Tra<strong>in</strong><strong>in</strong>g Systems Design. TheInternational Journal of Aviation Psychology, 14, 207–231.Thomas, M.J.W. (2004b). Error management tra<strong>in</strong><strong>in</strong>g: def<strong>in</strong><strong>in</strong>g best practice. ATSBAviation Safety Research Grant Scheme Project 2004/0050Electronic version retrieved March 19, 2007 fromhttp://www.atsb.gov.au/publications/2004/pdf/error_management_tra<strong>in</strong><strong>in</strong>g_best_practice.pdfThomas, M.J.W. (2005). Error management tra<strong>in</strong><strong>in</strong>g: an <strong>in</strong>vestigation of expert pilots’error management strategies dur<strong>in</strong>g normal operations <strong>and</strong> flight crew tra<strong>in</strong><strong>in</strong>g studytwo: simulator study to identify error management tra<strong>in</strong><strong>in</strong>g <strong>in</strong> current practice. ATSBAviation Safety Research Grant Scheme Project 2004/005034


Electronic version retrieved March 19, 2007 fromhttp://www.atsb.gov.au/publications/2004/pdf/error_management_tra<strong>in</strong><strong>in</strong>g_study2.pdfThomas, M.J.W. & Petrilli, R.M. (2004). Error management tra<strong>in</strong><strong>in</strong>g: an <strong>in</strong>vestigation ofexpert pilots’ error management strategies dur<strong>in</strong>g normal operations <strong>and</strong> flight crewtra<strong>in</strong><strong>in</strong>g, study one: <strong>in</strong>terview study to identify error management practices <strong>in</strong>experienced tra<strong>in</strong><strong>in</strong>g capta<strong>in</strong>s. ATSB Aviation Safety Research Grant Scheme Project2004/0050. Electronic version retrieved March 19, 2007 fromhttp://www.atsb.gov.au/publications/2004/pdf/error_management_tra<strong>in</strong><strong>in</strong>g_study1.pdfTransportation Safety Board of Canada (1995). A <strong>safety</strong> study of evacuations of largerpassenger carry<strong>in</strong>g aircraft (Report Number SA9501). Electronic version retrievedNovember 11, 2004 from http://www.tsb.gc.ca/en/reports/air/studies/sa9501/sa9501.aspvon Thaden, T.L. & Steelman, K.S. (2005). Classify<strong>in</strong>g crew performance failures <strong>in</strong>commercial <strong>aviation</strong> accidents: can we get the numbers right? Paper presented at theSafety Across High-Consequence Industries Conference, St. Louis, MO, September,2005. Electronic version retrieved May 3, 2007 from:http://www.humanfactors.uiuc.edu/Reports&PapersPDFs/miscconf/vonste05.pdfWever, R. Van Es, G., & Verbeek, M. (2006). Air-Ground Communication Safety Study:Causes <strong>and</strong> Recommendations. Brussels: EATMP Infocentre, Eurocontrol. Electronicversion retrieved April 25, 2007 fromhttp://www.eurocontrol.<strong>in</strong>t/<strong>safety</strong>/gallery/content/public/library/AGC%20<strong>safety</strong>%20study%20causes_recommendations.pdfYoung, L. B. (1994). Communications <strong>and</strong> pilot/flight attendant crew performance. TheCRM Advocate, 94 (1). Electronic version retrieved November 12, 2004 from:http://s92270093.onl<strong>in</strong>ehome.us/crmdevel/resources/crmadvocate/94_1/94_1/htmZun<strong>in</strong>, L., & Zun<strong>in</strong>, N. (1974). The first four m<strong>in</strong>utes. New York: Ballant<strong>in</strong>e Books.35

Hooray! Your file is uploaded and ready to be published.

Saved successfully!

Ooh no, something went wrong!