航空 发表于 2010-4-6 23:33:47

TEM介绍

<P>**** Hidden Message *****</P>

航空 发表于 2010-4-9 11:56:35

1<BR>Defensive Flying for Pilots: An Introduction to Threat and Error<BR>Management<BR>Ashleigh Merritt, Ph.D. &amp; James Klinect, Ph.D.<BR>The University of Texas Human Factors Research Project1<BR>The LOSA Collaborative<BR>December 12, 2006<BR>The easiest way to understand Threat and Error Management (TEM) is to liken it to<BR>defensive driving for a motorist. The purpose of defensive driving is not to teach people how<BR>to drive a vehicle (e.g., how to shift a manual transmission) but to emphasize driving<BR>techniques that people can use to minimize safety risks (e.g., techniques to control rear-wheel<BR>skids). Similarly, TEM does not teach pilots how to technically fly an airplane; instead, it<BR>promotes a proactive philosophy and provides techniques for maximizing safety margins<BR>despite the complexity of one’s flying environment. In this sense, TEM training can be<BR>framed as defensive flying for pilots.<BR>TEM proposes that threats (such as adverse weather), errors (such as a pilot selecting<BR>a wrong automation mode), and undesired aircraft states (such as an altitude deviation) are<BR>everyday events that flight crews must manage to maintain safety. Therefore, flight crews<BR>that successfully manage these events regardless of occurrence are assumed to increase their<BR>potential for maintaining adequate safety margins. It is this notion that provides the<BR>overarching objective of TEM—to provide the best possible support for flight crews in<BR>managing threats, errors, and undesired aircraft states.<BR>This paper provides an introductory orientation to TEM via a discussion of origins,<BR>definitions, and techniques. We will show how TEM was initially developed to help<BR>observers analyse activity in the cockpit and how it has since grown to become an<BR>organizational safety management tool used in training, incident reporting, and accident and<BR>incident analysis. TEM concepts are further explained using real-world examples and<BR>statistics taken from the LOSA Archive, which currently contains more than 5500 TEM-<BR>1 The University of Texas Human Factors Research Project, directed by Dr. Robert Helmreich, is funded by a<BR>research grant from the Federal Aviation Administration, AAR-100, Human Factors Division. For more<BR>information, contact James Klinect at <A href="mailto:klinect@losacollaborative.org">klinect@losacollaborative.org</A>.<BR>2<BR>based observations from 28 commercial airlines in over 14 countries around the world.2 The<BR>final section, TEM tools and techniques, highlights the practical, proactive nature of TEM<BR>and its relevance for all pilots.<BR>Origin and Development of TEM<BR>The origin of TEM is inextricably tied to the origin of Line Operations Safety Audits<BR>(LOSA). It began with a simple question: “Do the concepts taught in training transfer to<BR>normal, everyday flight operations?” The question prompted a partnership between The<BR>University of Texas Human Factors Research Project (UT) and Delta Airlines in 1994 to<BR>develop a line audit methodology utilizing jump-seat observations on regularly scheduled<BR>flights. All parties realized that in order for the audit to work, i.e., to really see what<BR>happened on the line, there had to be a guarantee of confidentiality with no regulatory or<BR>organizational jeopardy for the crews that were observed. Crews had to believe there would<BR>be no individual repercussions; otherwise, they would revert to their best “angel<BR>performance” when being observed and the audit would uncover nothing more than what was<BR>learned from line check or training data.<BR>The first observation form was designed by the UT researchers to evaluate Crew<BR>Resource Management (CRM) behaviours. The form was then expanded to address error and<BR>its management. As well as type of error committed, the form prompted observers to note<BR>who caused the error, the response to the error (i.e., whether the error was detected and by<BR>whom), and the outcome of the error. Knowing an error occurred without really knowing the<BR>conditions under which it occurred seemed to tell only part of the story. Hence, the<BR>researchers developed and included the concepts of threat and threat management in the<BR>observation form to capture the full operational complexity of a flight.<BR>The first full TEM-based LOSA was conducted at Continental Airlines in 1996. Data<BR>from the observation forms were aggregated to develop an airline profile. As well as the<BR>original CRM indicators such as leadership, communication, and monitoring/cross-checking,<BR>the TEM organizational profile highlighted the most frequent threats, threats that were wellmanaged<BR>versus more problematic threats (i.e., those that were mismanaged at higher rates<BR>than other threats), the most common errors, the least versus more problematic errors, and the<BR>2 LOSA stands for Line Operations Safety Audit. See Appendix A for details on the LOSA Archive and how it<BR>was built, including a list of airlines with observations in the Archive.<BR>3<BR>rate of Undesired Aircraft States, including unstable approaches. Among other things, the<BR>airline learned that it had issues with its checklists. It also realized there were no clear<BR>guidelines on when to execute a missed approach, which could explain the rate of unstable<BR>approaches. With a data-driven report that highlighted operational strengths and weaknesses,<BR>the airline set up cross-departmental committees from Flight Operations, Ground Operations,<BR>Training, and the Safety Department to work on solutions.<BR>The company also instigated a one-day TEM training course for all its pilots.<BR>Trainers introduced the concepts of Threat and Error and then debriefed the LOSA findings.<BR>As a result, pilots were able to see a different perspective of safety performance at their<BR>airline as reflected in organizational threat and error prevalence and management rates. The<BR>pilots responded positively, analysing the data for reasons, and using what they learned to<BR>proactively enhance their own performance.<BR>Using the 1996 LOSA results as a baseline, Continental conducted a follow-up LOSA<BR>in 2000. To quote Captain Don Gunther, Senior Director of Safety &amp; Regulatory Compliance<BR>at Continental Airlines:<BR>“The 2000 LOSA, when compared to the results of 1996, showed the pilots<BR>had not only accepted the principles of error management but incorporated<BR>them into everyday operations. LOSA 2000 showed a sizeable improvement<BR>in the areas of checklist usage, a 70 percent reduction in non-conforming<BR>approaches (i.e., those not meeting stabilized approach criteria), and an<BR>increase in overall crew performance. It could be said that Continental had<BR>taken a turn in the right direction.”<BR>Based on the success at Continental as well as other LOSA carriers, the International<BR>Civil Aviation Organization (ICAO) made LOSA a central focus of its Flight Safety and<BR>Human Factors Program and endorsed it as an industry best practice for normal operations<BR>monitoring (ICAO LOSA Manual, Doc 9803). The Federal Aviation Administration (FAA)<BR>also endorses LOSA as one of its voluntary safety programs (FAA Advisory Circular 120-<BR>90). As a result, TEM and LOSA are now recognised world-wide.<BR>4<BR>TEM: Definitions, Examples, and Quizzes<BR>The Threat and Error Management (TEM) framework focuses simultaneously on the<BR>operating environment and the humans working in that environment. Because the framework<BR>captures performance in its “natural” or normal operating context, the resulting description is<BR>realistic, dynamic, and holistic. Because the TEM taxonomy can also quantify the specifics of<BR>the environment and the effectiveness of performance in that environment, the results are also<BR>highly diagnostic.<BR>Threats and their Management<BR>Pilots have to manage various complexities in the operating environment on a typical day<BR>of flying. In TEM, such complexities are known as threats.<BR>Threat Definition<BR>Threats are defined as events or errors that:<BR>&#1048766; occur outside the influence of the flight crew (i.e., not caused by the crew);<BR>&#1048766; increase the operational complexity of a flight; and<BR>&#1048766; require crew attention and management if safety margins are to be maintained.<BR>Using this definition, a threat can be high terrain, icing conditions, an aircraft<BR>malfunction (e.g., inoperative thrust reverser), or other people’s errors, such as an inaccurate<BR>recording of a fuel load by a dispatcher. All these events occur independently of the flight<BR>crew, yet they add to the crew’s workload and need to be managed. Sometimes they can be<BR>managed discreetly and sometimes they interact with one another further complicating the<BR>necessary management. In commercial airlines, threats can be divided into two categories:<BR>environmental threats, which are outside the airline’s direct control, such as weather and<BR>ATC; and airline threats, which originate within flight operations, such as aircraft<BR>malfunctions and ground problems. The table below shows the various threat types with<BR>examples.<BR>5<BR>Threat Types with Examples<BR>Environmental Threats Examples<BR>Adverse Weather Thunderstorms, turbulence, poor visibility, wind shear, icing conditions, IMC<BR>Airport Poor signage, faint markings, runway/taxiway closures, INOP navigational<BR>aids, poor braking action, contaminated runways/taxiways<BR>ATC Tough-to-meet clearances/restrictions, reroutes, language difficulties,<BR>controller errors<BR>Environmental Operational<BR>Pressure Terrain, traffic, TCAS TA / RA, radio congestion<BR>Airline Threats Examples<BR>Aircraft<BR>Systems, engines, flight controls, or automation anomalies or malfunctions;<BR>MEL items with operational implications; other aircraft threats requiring flight<BR>crew attention<BR>Airline Operational Pressure On-time performance pressure, delays, late arriving aircraft or flight crew<BR>Cabin Cabin events, flight attendant errors, distractions, interruptions<BR>Dispatch/Paperwork Load sheet errors, crew scheduling events, late paperwork, changes or errors<BR>Ground/Ramp Aircraft loading events, fuelling errors, agent interruptions, improper ground<BR>support, de-icing<BR>Ground Maintenance Aircraft repairs on ground, maintenance log problems, maintenance errors<BR>Manuals/Charts Missing information or documentation errors<BR>Threat management can be broadly defined as how crews anticipate and/or respond to<BR>threats. A mismanaged threat is defined as a threat that is linked to or induces flight crew<BR>error. Some of the common tools and techniques used in commercial aviation to manage<BR>threats and prevent crew errors include reading weather advisories, turning weather radar on<BR>early, thorough walk-arounds during predeparture, correct use of procedures to diagnose<BR>unexpected aircraft malfunctions, briefing an alternate runway in case of a late runway<BR>change, briefing cabin crew as to acceptable times and reasons for interruptions, and loading<BR>extra fuel when the destination airport is in question due to poor weather or restricted access.<BR>Just how common are threats and when do they occur? Take the quiz below to find out.<BR>6<BR>Threat Management Quiz<BR>Test your knowledge of threats and their management by circling your best guess to the following questions about<BR>findings from the LOSA Archive of more than 4500 observations across 25 airlines. Correct answers with<BR>discussion will be provided at the end of the quiz.<BR>1. On average, how many threats per flight (regularly scheduled, normal operations) are encountered by<BR>flight crews in the LOSA Archive?<BR>A) One threat every 2-3 flights C) 1-3 threats per flight<BR>B) One threat per flight D) 4-6 threats per flight<BR>2. In what phase of flight do most threats occur in the LOSA Archive?<BR>A) Predeparture/Taxi-out C) Cruise<BR>B) Takeoff/Climb D) Descent/Approach/Land<BR>3. What are the most frequently encountered threats by flight crews in the LOSA Archive?<BR>A) Adverse weather (e.g., thunderstorms) C) Aircraft (e.g., malfunctions / anomalies)<BR>B) ATC (e.g., challenging clearances) D) Airport (e.g., poor signage/construction)<BR>4. What percent of threats are successfully managed by flight crews in the LOSA Archive? (i.e.,<BR>percentage of threats not contributing to a flight crew error)<BR>A) 95-100% C) 75-85%<BR>B) 85-95% D) Less than 75%<BR>5. Of all threats encountered by flight crews in the LOSA Archive, which are the most problematic?<BR>A) Adverse weather (e.g., thunderstorms) C) Aircraft (e.g., malfunctions / anomalies)<BR>B) ATC (e.g., challenging clearances) D) Airport (e.g., poor signage/construction)<BR>7<BR>Threat Management Quiz Answers and Discussion<BR>1. The correct answer is (D). Based on the last 25 LOSAs (over 4500 flights in total) in the LOSA Archive, the<BR>typical flight (regularly scheduled, normal operations) encounters an average 4.2 threats per flight. Of those, three<BR>are likely to be Environmental threats and one is likely to be an Airline threat. Only 3% of flights encounter no<BR>threats whatsoever, while 17% of flights encounter seven or more threats per flight. In other words, multiple<BR>threats are the standard and should be considered as such in every flight.<BR>2. The correct answer is (A). Overall, about 40% of all threats occur during Predeparture/Taxi-out and 30% occur<BR>during Descent/Approach/Land. Different types of threats are more prevalent during different phases of flight. For<BR>Environmental threats (weather, ATC, terrain, traffic, airport conditions), the busiest phase of flight is<BR>Descent/Approach/Land, while for Airline threats, the busiest phase is Predeparture/Taxi-out. In percentage<BR>terms, 43% of all Environmental threats occur during Descent/Approach/Land, while 73% of all Airline threats<BR>occur during Predeparture/Taxi-out.<BR>3. The correct answer is (A or B). With 4500 flights having an average of 4.2 threats per flight, there are 19,000<BR>logged threats in the LOSA Archive. So which are the most common? Actually, Adverse Weather and ATC both<BR>account for about one quarter of all observed threats, followed by Aircraft Threats (about 13% of all observed<BR>threats) and Airport Conditions (about 7% of all observed threats).<BR>4. The correct answer is (B). 85-95% of all threats are successfully managed. The average across the Archive is<BR>90%. Put another way, about one-tenth of all threats are mismanaged by the crews, leading to some form of crew<BR>error.<BR>5. The correct answer is (B). Mismanagement rates are actually very close for the top three “offenders”. Thirteen<BR>percent of Aircraft threats, 12% of ATC threats, and 11% of Adverse Weather threats are typically mismanaged.<BR>However, when you combine these mismanagement rates with the frequency with which different threats occur,<BR>ATC threats emerge as the most problematic threat. In particular, challenging clearances and late changes from<BR>ATC are the most problematic of all threats for flight crews.<BR>8<BR>Errors and their Management<BR>From the TEM perspective, error is a crew action or inaction that leads to a deviation<BR>from crew or organizational intentions or expectations. Put simply, threats come “at” the<BR>crew, while errors come “from” the crew. Flight crew errors can be the result of a<BR>momentary slip or lapse, or induced by an expected or unexpected threat. For example, a late<BR>runway change might induce a procedural shortcut that results in further error, just as a gate<BR>agent interruption could distract the flight crew from completing a checklist, causing them to<BR>miss an incorrect flaps setting for takeoff. Other errors are more deliberate. Known as<BR>intentional noncompliance errors in the TEM taxonomy, these errors are often proven<BR>shortcuts used by flight crews to increase operational efficiency even thought they are in<BR>violation of Standard Operating Procedures. High rates of noncompliance at an airline can<BR>often indicate systemic over-procedualization.<BR>Error Definition<BR>Errors are defined as flight crew actions or inactions that:<BR>&#1048766; lead to a deviation from crew or organizational intentions or expectations;<BR>&#1048766; reduce safety margins; and<BR>&#1048766; increase the probability of adverse operational events on the ground or during flight.<BR>Flight crew errors can be divided into three types: aircraft handling, procedural and<BR>communication errors. Aircraft handling errors are those deviations associated with the<BR>direction, speed and configuration of the aircraft. They can involve automation errors, such<BR>as dialling an incorrect altitude, or hand-flying errors, such as getting too fast and high during<BR>an approach. Procedural errors are flight crew deviations from regulations, flight manual<BR>requirements or airline standard operating procedures. Lastly, communication errors involve<BR>a miscommunication between the pilots, or between the crew and external agents such as<BR>ATC controllers, flight attendants, and ground personnel. The table below shows the various<BR>error types with examples.<BR>9<BR>Error Types with Examples<BR>Aircraft Handling Errors Examples<BR>Automation Incorrect altitude, speed, heading, autothrottle settings, mode executed, or<BR>entries<BR>Flight Control Incorrect flaps, speed brake, autobrake, thrust reverser or power settings<BR>Ground Navigation<BR>Attempting to turn down wrong taxiway/runway<BR>Missed taxiway/runway/gate<BR>Manual Flying<BR>Hand flying vertical, lateral, or speed deviations<BR>Missed runway/taxiway failure to hold short, or taxi above speed limit<BR>Systems/Radio/Instruments Incorrect pack, altimeter, fuel switch or radio frequency settings<BR>Procedural Errors Examples<BR>Briefings Missed items in the brief, omitted departure, takeoff, approach, or handover<BR>briefing<BR>Callouts Omitted takeoff, descent, or approach callouts<BR>Checklist<BR>Performed checklist from memory or omitted checklist<BR>Missed items, wrong challenge and response, performed late or at wrong time<BR>Documentation<BR>Wrong weight and balance, fuel information, ATIS, or clearance recorded<BR>Misinterpreted items on paperwork<BR>Pilot Flying (PF)/Pilot Not<BR>Flying (PNF) Duty PF makes own automation changes, PNF doing PF duties, PF doing PNF duties<BR>SOP Cross-verification Intentional and unintentional failure to cross-verify automation inputs<BR>Other Procedural Other deviations from government regulations, flight manual requirements or<BR>standard operating procedures<BR>Communication Errors Examples<BR>Crew to External<BR>Missed calls, misinterpretation of instructions, or incorrect read-backs to ATC<BR>Wrong clearance, taxiway, gate or runway communicated<BR>Pilot to Pilot Within-crew miscommunication or misinterpretation<BR>10<BR>Error management is now recognized as an inevitable part of learning, adaptation, and<BR>skill maintenance; hence, a primary driving force behind TEM is to understand what types of<BR>errors are made under what circumstances (i.e., the presence or absence of which threats) and<BR>how crews respond in those situations. For example, do crews detect and recover the error<BR>quickly, do they acknowledge the error but do nothing, perhaps because they believe it is<BR>inconsequential or will be trapped later, or do they only “see” the error when it escalates to a<BR>more serious undesired aircraft state? This is the heart of error management: detecting and<BR>correcting errors. However, approximately 45% of the observed errors in the LOSA Archive<BR>were errors that went undetected or were not responded to by the flight crew, which gives<BR>credence to an important point for effective error management: An error that is not detected<BR>cannot be managed.<BR>An error that is detected and effectively managed has no adverse impact on the flight.<BR>On the other hand, a mismanaged error reduces safety margins by linking to or inducing<BR>additional error or an undesired aircraft state.3 Just how common are mismanaged errors and<BR>when do they occur? The LOSA Archive provides some insight, as shown in the quiz below.<BR>3 Undesired Aircraft State (UAS): A flight-crew-induced aircraft state that clearly reduces safety margins; a safetycompromising<BR>situation that results from ineffective error management. Discussed in next section.<BR>11<BR>Error Management Quiz<BR>Test your knowledge of flight crew errors and their management by circling your best guess to the following<BR>questions. As with the Threat Management Quiz, correct answers with discussion will be provided at the end of<BR>the quiz.<BR>1. Of flights in the LOSA Archive, how common is flight crew error?<BR>A) Approximately 5% of flights have some form of observable crew error<BR>B) Approximately 50% of flights have some form of observable crew error<BR>C) Approximately 80% of flights have some form of observable crew error<BR>D) All LOSA flights (100%) have at least one observable crew error<BR>2. In what phase of flight do most flight crew errors occur in the LOSA Archive? When do the mismanaged<BR>errors occur? (Hint: The answer is the same phase of flight for both questions)<BR>A) Predeparture/Taxi-out C) Descent/Approach/Land<BR>B) Takeoff/Climb D) Taxi-in/Park<BR>3. What are the most frequently committed flight crew errors in the LOSA Archive?<BR>A) Aircraft Handling (e.g., wrong automation setting)<BR>B) Procedural (e.g., omitted callout)<BR>C) Communication (e.g., incorrect ATC readback)<BR>4. What are the most common procedural errors observed in the LOSA Archive?<BR>A) Briefing C) Callout<BR>B) SOP Cross-verification D) Checklist<BR>5. What percentage of errors are mismanaged by flight crews in the LOSA Archive (i.e., percentage of<BR>errors linking to an additional error or undesired aircraft state)<BR>A) 20-30% C) 40-50%<BR>B) 30-40% D) More than 50%<BR>6. What are the most frequently mismanaged flight crew errors in the LOSA Archive?<BR>A) Manual Handling/Flight Control C) System/Instrument/Radio<BR>B) Automation D) Checklist<BR>12<BR>Error Management Quiz Answers and Discussion<BR>1. The correct answer is (C). Based on the last 25 LOSAs (over 4500 flights in total) in the LOSA Archive, about<BR>80% of flights have one or more errors – the average is about three errors per flight. Twenty percent of flights<BR>have no observable error.<BR>2. The correct answer is (C). The busiest phase of flight for errors is Descent/Approach/Land. About 40% of all<BR>observed errors occur during this phase. Another 30% of errors occur during Predeparture/Taxi-out when crews<BR>are preparing the flight. If you look at the sub-set of errors that are mismanaged, then the rate for<BR>Descent/Approach/Land jumps to 55%. Therefore, the most problematic phase of flight where more errors, and<BR>more mismanaged errors, are likely to occur is Descent/Approach/Land. This likely makes intuitive sense—errors<BR>on the ground aren’t as difficult to manage as errors coming down.<BR>3. The correct answer is (B). About one-half of all observed errors are Procedural errors, one-third are Aircraft<BR>Handling, and one-sixth are Communication errors. However, this ratio changes dramatically for mismanaged<BR>errors. Procedural errors make up half of all errors, but a little less than one-quarter of the mismanaged errors.<BR>Three-quarters of all mismanaged errors are Aircraft Handling errors, with Communication errors comprising the<BR>remaining few percent.<BR>4. The correct answer is (D). Checklist errors are the most common procedural error, followed closely by Callout<BR>and SOP cross-verification errors. Briefing errors are less common.<BR>5. The correct answer is (A). About 25% of all errors are mismanaged—6% of all errors lead to additional error<BR>and 19% result directly in an undesired aircraft state.<BR>6. The correct answer is (A). Manual handling/flight control errors make up 36% of all mismanaged errors.<BR>Automation and System/Instrument/Radio errors each make up 16% of the mismanaged errors. Checklist errors<BR>make up 5% of the mismanaged errors; Crew-ATC communication errors make up 3% of the mismanaged errors.<BR>13<BR>Undesired Aircraft States and their Management<BR>Unfortunately, not all errors are well managed. Sometimes they lead to another error<BR>or a safety-compromising event called an undesired aircraft state (UAS).<BR>Undesired Aircraft State Definition<BR>An undesired aircraft state (UAS) is defined as a position, speed, attitude, or<BR>configuration of an aircraft that:<BR>&#1048766; results from flight crew error, actions, or inaction; and<BR>&#1048766; clearly reduces safety margins<BR>In other words, a UAS is a safety-compromising state that results from ineffective<BR>error management. Examples include unstable approaches, lateral deviations from track, firm<BR>landings, and proceeding towards the wrong taxiway/runway. Events such as malfunctions or<BR>ATC controller errors can also place the aircraft in a compromised position; however, in the<BR>TEM taxonomy, these events are considered threats as they are not the result of actions by the<BR>flight crew.<BR>UAS Types with Examples<BR>UAS Types Examples<BR>Aircraft Handling<BR>Vertical, lateral or speed deviations<BR>Unnecessary weather penetration<BR>Unstable approach<BR>Long, floated, firm or off-centreline landings<BR>Ground Navigation<BR>Runway/taxiway incursions<BR>Wrong taxiway, ramp, gate, or hold spot<BR>Taxi above speed limit<BR>Incorrect Aircraft Configuration Automation, engine, flight control, systems, or weight/balance events<BR>As with errors, UASs can be managed effectively, returning the aircraft to optimally<BR>safe flight, or mismanaged, leading to an additional error, undesired aircraft state, or worse,<BR>an incident, or accident. The last quiz sheds light on the prevalence and mismanagement of<BR>undesired aircraft states in the LOSA Archive.<BR>14<BR>Undesired Aircraft State Management Quiz<BR>Test your knowledge of undesired aircraft states and their management by circling your best guess to the<BR>following questions. As with the previous quizzes, correct answers with discussion will be provided at the end of<BR>the quiz.<BR>1. Of flights in the LOSA Archive, how common are undesired aircraft states (UAS)?<BR>A) Less than 1% of flights have a UAS<BR>B) 15% of flights have a UAS<BR>C) 35% of flights have a UAS<BR>D) 50% of flights have a UAS<BR>2. What are the most frequent UASs observed in the LOSA Archive?<BR>A) Incorrect systems configurations (e.g., wrong anti-ice setting in icing conditions)<BR>B) Speed deviations<BR>C) Lateral and vertical deviations<BR>D) Incorrect automation configurations (e.g., wrong altitude dialled after cross-check)<BR>3. How common are unstable approaches in the LOSA Archive and how often do they result in a missed<BR>approach?<BR>A) Less than 1% of flights have an unstable approach; of those, 95% result in a missed approach<BR>B) 5% of flights have an unstable approach; of those, 5% result in a missed approach<BR>C) More than 15% of flights have an unstable approach; of those, 50% result in a missed approach<BR>4. How many UASs in the LOSA Archive can be linked back, via mismanaged crew error, to a<BR>mismanaged threat?<BR>A) Virtually all UASs come about because of a threat that was mismanaged (95-100%)<BR>B) About 70% of all UASs are linked to a mismanaged threat; the rest emerge from<BR>“spontaneous” crew errors that were mismanaged (“spontaneous” = not linked to a threat)<BR>C) About 30% of all UASs are linked to a mismanaged threat.<BR>15<BR>Undesired Aircraft States Quiz Answers and Discussion<BR>1. The correct answer is (C). Despite being the safest form of transport, fully one-third of all flights in the LOSA<BR>Archive have an undesired aircraft state. Numbers such as these remind us there is still room for improvement!<BR>2. The correct answer is (A). Almost 20% of all UASs involve an incorrect aircraft system configuration (they<BR>occur on approximately 9% of flights). Speed deviations are next at 16%, followed by lateral/vertical deviations<BR>and incorrect automation configuration (each comprises about 13% of all UASs). These UAS types each occur on<BR>approximately 7% of flights.<BR>3. The correct answer is (B). In regularly scheduled, normal operations, 5% of flights involve an unstable<BR>approach. What is disconcerting is that only 5% of those unstable approaches result in a go-around, meaning the<BR>vast majority of crews decide to continue with the landing, even though they know they are not within specified<BR>parameters. Are they choosing to continue the approach because of operational pressure (wanting to save time<BR>and fuel), poor airmanship, or foolish bravado? Perhaps some of all three, what do you think?<BR>4. The correct answer is (C). About 30% of all UASs occur as part of a chain of events that starts with a threat<BR>that is not managed well and leads to a crew error, which in turn is mismanaged to a UAS. An example would be<BR>an Airport Conditions threat such as poor or faded signage (threat) that confuses the crew, leading them to turn<BR>down the wrong runway (error), which results in a runway incursion (UAS).<BR>TEM Tools &amp; Techniques<BR>The principles of TEM are not new to aviation. In fact, Orville and Wilbur Wright no<BR>doubt practiced threat and error management when they took their first controlled flight with<BR>the Wright Flyer in 1903. Since then, various tools and techniques have been developed over<BR>the past century to help flight crews manage threats, errors, and undesired aircraft states.<BR>Some tools—the “hard” safeguards—are associated with aircraft design, and include<BR>automated systems, instrument displays, and aircraft warnings. The Traffic Collision<BR>Avoidance System (TCAS), which provides flight crews with visual and audio warnings of<BR>nearby airplanes to prevent midair collisions, is a good example of a “hard” TEM safeguard.<BR>Even with the best designed equipment however, these “hard” safeguards are not enough to<BR>ensure effective TEM performance.<BR>16<BR>Other tools—the “soft” safeguards—are very common in aviation (and other high-risk<BR>industries). They include regulations, standard operating procedures, and checklists to direct<BR>pilots and maintain equipment; and licensing standards, checks, and training to maintain<BR>proficiency. With the hard and soft safeguards in place, the last line of defence against threat,<BR>error, and undesired aircraft states, is still, ultimately, the flight crew. Checklists only work if<BR>flight crews use them; the autopilot only works when engaged in the correct mode.<BR>Therefore, TEM tools work best when pilots adopt TEM techniques.<BR>The TEM philosophy stresses three basic concepts: anticipation, recognition, and<BR>recovery. The key to anticipation is accepting that while something is likely to go wrong, you<BR>can’t know exactly what it will be or when it will happen. Hence, a chronic unease reinforces<BR>the vigilance that is necessary in all safety-critical professions. Anticipation builds vigilance,<BR>and vigilance is the key to recognizing adverse events and error. Logically, recognition leads<BR>to recovery. In some cases, particularly when an error escalates to an undesired aircraft state,<BR>recovering adequate safety margins is the first line of action: Recover first, analyse the causes<BR>later. For example, a crew enters a Flight Management System (FMS) approach to runway<BR>26L; however, they mistakenly enter data for 26R. Furthermore, the error is not detected by<BR>the flight crew on a SOP required cross-verification. Once the flight crew executes the<BR>incorrect entry and the airplane starts flying on a profile to the wrong runway, the flight is<BR>considered to be in an undesired aircraft state. At this point, the crew can either analyze<BR>what’s wrong with the automation and fix the problem or save valuable time by simply<BR>disconnecting the autopilot and hand-flying the approach to the correct runway. The latter<BR>option is more effective from the TEM perspective because it focuses effort on recovering<BR>from the undesired aircraft state rather than analyzing its causes.<BR>While “hard” and “soft” safeguards help support pilots to best anticipate, recognize<BR>and recover from threats, errors, and undesired aircraft states, there is arguably no better way<BR>to manage these events in multi-pilot cockpits than through effective crew coordination.<BR>Many of the best practices advocated by Crew Resource Management (CRM) can be<BR>considered TEM countermeasures.<BR>&#1048766; Planning countermeasures—planning, preparation, briefings, contingency<BR>management—are essential for managing anticipated and unexpected threats.<BR>17<BR>&#1048766; Execution countermeasures—monitor/cross-check, taxiway/runway management,<BR>workload and automation management—are essential for error detection and error<BR>response.<BR>&#1048766; Review/Modify countermeasures—evaluation of plans, inquiry—are essential for<BR>managing the changing conditions of a flight, such as undesired aircraft states.<BR>Initial research in the LOSA Archive has supported links between TEM and CRM.<BR>For example, crews that develop contingency management plans, such as proactively<BR>discussing strategies for anticipated threats, tend to have fewer mismanaged threats; crews<BR>that exhibit good monitoring and cross-checking usually commit fewer errors and have fewer<BR>mismanaged errors; and finally, crews that exhibit strong leadership, inquiry, workload<BR>management are typically observed to have fewer mismanaged errors and undesired aircraft<BR>states than other crews.<BR>Conclusion: Applications of TEM<BR>TEM is both a philosophy of safety and a practical set of techniques. Originally<BR>designed to simultaneously capture performance and the context in which it occurs, TEM has<BR>demonstrated its usefulness in many settings.<BR>Training: The International Civil Aviation Organization (ICAO) has introduced a<BR>standard making TEM training mandatory for airline flight crews engaged in international<BR>operations. TEM training must now be delivered during initial as well as during recurrent<BR>training. ICAO has also introduced standards making TEM training mandatory for licensing<BR>and training requirements of private and commercial pilots and air traffic controllers. In order<BR>to support these standards, ICAO is continually developing guidance material on TEM which<BR>reflects and is aligned with the concepts discussed in this paper (Human Factors Training<BR>Manual, Procedures for Air Navigation Services, Training, PANS/TRG, and An introduction<BR>to TEM in ATC). In addition, the Australian Transport Safety Bureau and Australian Civil<BR>Aviation Safety Authority are facilitating TEM training courses for pilots.<BR>Line Operations Safety Audits (LOSA): Considered a best practice for normal<BR>operations monitoring and aviation safety by both ICAO and the FAA, TEM-based LOSAs<BR>continue to provide valuable diagnostic information about an airline’s safety strengths and<BR>vulnerabilities.<BR>18<BR>Incident Reporting: Several US airlines now use TEM as the conceptual structure for<BR>their incident reporting systems. Reporting forms prompt pilots to report the threats that were<BR>present, the errors they may have made, how the event was managed, and how the event may<BR>have been avoided or handled better. Even pilots who have not had training in TEM are able<BR>to complete the reporting form, a fact that speaks to the intuitive nature of the TEM<BR>framework.<BR>Incident and Accident Analysis: The International Air Transport Association (IATA)<BR>Safety Committee adopted the TEM model as an analysis framework for its Incident Review<BR>Meetings, based on its ease of use and utility of the extracted data. IATA has also created the<BR>Integrated Threat Analysis Task Force (ITATF). This group analyses data from accidents, incidents,<BR>and normal operations using TEM as the common framework. By selecting specific scenarios, for<BR>example, runway excursions from the incident and accident databases, and precursors to runway<BR>excursions from the LOSA Archive, it is possible to provide a more complete picture of safety issues<BR>within the aviation system.<BR>Other Aviation Settings: Studies are currently underway to adapt TEM to Air Traffic<BR>Control, Flight Dispatch, and Ramp. Of interest, the first ATC trials, called the Normal<BR>Operations Safety Survey (NOSS), were conducted under ICAO sponsorship in Australia,<BR>Canada, and New Zealand, and were well-received. The ICAO sponsored NOSS manual<BR>explaining how to conduct normal operations monitoring in Air Traffic Control, will be<BR>available in 2007.<BR>TEM has proved its utility in many safety management applications. As organizations<BR>and individuals continue to adopt TEM as a way to understand and enhance their<BR>performance, we hope that you too will see the utility of the TEM framework and find ways<BR>to incorporate TEM techniques into your own personal philosophy of safety.<BR>19<BR>Appendix A: The LOSA Archive<BR>The LOSA Archive is a database containing observers’ narratives and coded<BR>observations from all the airlines that have conducted a Line Operations Safety Audit<BR>(LOSA) with the LOSA Collaborative. Because of the stringent quality assurance process<BR>(see below), results from different airlines can be pooled to derive industry averages. The<BR>LOSA Archive can also benchmark an airline’s performance against other airlines, providing<BR>a multi-airline context for understanding an airline’s strengths and weaknesses.<BR>The statistics cited in this paper are based on 4,532 observations taken from the 25<BR>most recent LOSAs (2002-2006). The data generated by those observations include 19,053<BR>observed threats, 13,675 errors, and 2,589 Undesired Aircraft States. The LOSA Archive<BR>currently contains observations from the following airlines.<BR>The LOSA Archive (2002-2006)<BR>AeroMexico (Mexico)<BR>Air New Zealand<BR>Air Transat (Canada)<BR>Alaska Airlines (USA)<BR>Asiana Airlines (Korea)<BR>Braathens ASA (Norway)<BR>Cathay Pacific (Hong Kong)<BR>China Airlines (Taiwan)<BR>Continental Airlines (USA)<BR>Continental Express (USA)<BR>Continental Micronesia<BR>Delta Air Lines (USA)<BR>EVA Air / UNI Air (Taiwan)<BR>Frontier Airlines (USA)<BR>LACSA (Central America)<BR>Malaysia Airlines<BR>Mt Cook Airlines (New Zealand)<BR>Qantas (Australia)<BR>Regional Express (Australia)<BR>SilkAir (Singapore)<BR>Singapore Airlines<BR>TACA International (S America)<BR>TACA Peru (S America)<BR>US Airways (USA)<BR>WestJet (Canada)<BR>LOSA Quality Assurance Process<BR>To ensure successful implementation, airlines are required to participate in a five-part LOSA<BR>quality assurance process.<BR>1. An agreement is reached between airline management and the pilots’ association. This<BR>agreement ensures that all data will be de-identified, confidential, and sent directly to<BR>20<BR>the LOSA Collaborative for analysis. It also states that once the LOSA results are<BR>presented, both parties have an obligation to use the data to improve safety.<BR>2. The airline is assisted in selecting a diverse and motivated group of observers. A<BR>typical observer team will have representatives from a number of different airline<BR>departments, such as flight operations, training, safety, and the flight crew association.<BR>3. The observers receive five days of training in the Threat and Error Management<BR>framework, the observation methodology, and the LOSA software tool, which<BR>organizes data input. The LOSA Collaborative software also provides data security<BR>through automatic encryption. After the initial observer training, observers conduct at<BR>least two sample observations and then reconvene for recalibration sessions. During<BR>this time, observers are given one-on-one feedback on the quality of their<BR>observations and certified to continue as observers on the project. The observer<BR>training and recalibration are considered essential for a standardized LOSA dataset.<BR>Subsequent observations are typically conducted over the next four to eight weeks.<BR>4. When the encrypted observations are sent to the LOSA Collaborative, analysts read<BR>the observers’ flight narratives and check that every threat and error has been coded<BR>accurately. This data integrity check ensures the airline’s data are of the same<BR>standard and quality as other airlines in the LOSA Archive.<BR>5. Once the initial data integrity check is complete, airline representatives who are fleet<BR>experts attend a data-cleaning roundtable with the LOSA Collaborative analysts.<BR>Together they review the data against the airline’s procedures, manuals, and policies<BR>to ensure that events and errors have been correctly coded. After the roundtable is<BR>completed, airline representatives are required to sign off on the data set as being an<BR>accurate rendering of threats and errors. Only then does analysis for the final report<BR>begin.

Virgin 发表于 2010-5-28 23:42:23

看看,谢谢楼主

mrmmx 发表于 2010-10-19 21:42:40

的点对点的的点对点的点对点的

happyzx 发表于 2011-4-25 12:38:58

参考一下,xiexiexiexie

candy 发表于 2011-5-14 22:28:52

回复 1# 航空 的帖子

看看什么内容
页: [1]
查看完整版本: TEM介绍