09.07.2015 Views

On the Design of Flight-Deck Procedures - Intelligent Systems ...

On the Design of Flight-Deck Procedures - Intelligent Systems ...

On the Design of Flight-Deck Procedures - Intelligent Systems ...

SHOW MORE
SHOW LESS

You also want an ePaper? Increase the reach of your titles

YUMPU automatically turns print PDFs into web optimized ePapers that Google loves.

mission simulation (see Wiener et al., 1991). They reported that crews who scheduled <strong>the</strong>ir task earlywithin <strong>the</strong> window tended to be rated as high performing crews. Conversely, crews who scheduled <strong>the</strong>irtasks late within <strong>the</strong> window tended to be rated as low performing crews. Laudeman and Palmerconcluded that “scheduling <strong>of</strong> a task early in <strong>the</strong> window <strong>of</strong> opportunity is <strong>the</strong> optimal task schedulingstrategy” (p. 20). Figure 11 is a graphical depiction <strong>of</strong> several windows <strong>of</strong> opportunity in <strong>the</strong> Laudemanand Palmer study.Altitude(feet)20,000TaskApproach briefingDescent checklistApproach checklistCSD Low oil light proc.Window <strong>of</strong> OpportunityReceiving ATIS -> 11,00 feetTop <strong>of</strong> Descent -> 11,000 feet11,000 feet -> Outer MarkerDetecting low oil light -> Outer Marker15,000Approach Briefing & Descent Checklist11,00010,000Abnormal Indication:CSD Low Oil Light5,000ApproachChecklistCSD Low OilProcedure2,1000500 1000 1500Time(seconds)Figure 11. Windows <strong>of</strong> opportunity during <strong>the</strong> descent to Columbia, SC.The above findings are applicable in light <strong>of</strong> a recent airline accident (NTSB, 1991):In 1990 a MarkAir B-737 crashed about 7.5 miles short <strong>of</strong> runway 14, Unalakleet, Alaska. The captain (whowas <strong>the</strong> PF) incorrectly deduced <strong>the</strong> location <strong>of</strong> <strong>the</strong> FAF to be 10 DME from <strong>the</strong> localizer, ra<strong>the</strong>r than 5 DME.He <strong>the</strong>refore prematurely descended to 500 feet MSL, 5 miles prior to <strong>the</strong> FAF and consequently hit <strong>the</strong> ground(meteorological information was: ceiling, 500 feet overcast; visibility 1.5 miles with fog). The first <strong>of</strong>ficer(who was new on <strong>the</strong> aircraft) did not notice, or did not make <strong>the</strong> captain aware <strong>of</strong>, <strong>the</strong> departure from <strong>the</strong>approach procedure. The Safety Board, however, “believes it is more likely that <strong>the</strong> first <strong>of</strong>ficer was notmonitoring <strong>the</strong> approach closely because he was preoccupied with his o<strong>the</strong>r duties.”In addition to <strong>the</strong> regular tasks <strong>of</strong> <strong>the</strong> PNF, <strong>the</strong> first <strong>of</strong>ficer had two o<strong>the</strong>r tasks to perform: (1)reconfiguring <strong>the</strong> engine bleeds to aid in avoiding foreign object damage, and (2) starting <strong>the</strong> APU. Themanufacturer <strong>of</strong> <strong>the</strong> aircraft (Boeing), recommends that <strong>the</strong> bleeds be reconfigured below 10,000 feet; <strong>the</strong>MarkAir written procedure specifies doing this below 5,000 feet; a MarkAir management pilot stated“we try to keep <strong>the</strong>m reconfigured as low as possible...usually down around couple thousand feet...” (p.9); <strong>the</strong> captain briefed <strong>the</strong> first <strong>of</strong>ficer to reconfigure <strong>the</strong> bleeds “when we roll in on final...” (p. 59).44

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

Saved successfully!

Ooh no, something went wrong!