MEMORANDUM FOR A1 - Air Force E-Publishing
MEMORANDUM FOR A1 - Air Force E-Publishing MEMORANDUM FOR A1 - Air Force E-Publishing
50 AFI91-202 5 AUGUST 2011 5.4.1. Safety meetings. 5.4.2. Supervisor safety briefings. 5.4.3. Base newspapers and bulletins. 5.4.4. Safety publications. 5.4.5. HQ/AFSC or MAJCOM publications. 5.4.6. Electronically via e-mail, web page or video. 5.5. Mishap Analysis Program. In order to reduce mishaps, Commanders and Chiefs of Safety must know the type and number of mishaps that occur in their command. Once the type and number are identified, commanders can take risk mitigation actions based on sound statistical data. This historical look-back approach should not preclude a proactive, forward looking mishap prevention plan based on pre-identified hazards that haven’t yet caused a mishap. 5.5.1. MAJCOMs and Wings will: 5.5.1.1. Conduct a annual analysis and develop specific actions to reverse adverse trends. Analysis should target specific problem areas with recommendations for commander approval and appropriate actions. 5.5.1.2. Analysis programs must identify successes or problem areas and trends, measure safety program effectiveness and guide prevention actions. 5.5.2. HQ AFSC will perform Air Force level trend analysis and publish results. In addition, AFSC may conduct Safety Analysis Team (SAT) hazard and mishap trend analysis (as described in paragraph 5.8) for MAJCOMs, as directed by AF/SE. 5.6. Mishap Prevention Analysis Methods. There are several ways to approach analysis of mishap data for mishap prevention purposes. Program analysis functions are to target, monitor and/or study. 5.6.1. Target Approach. This approach is similar to the study method below. After determining causes of mishaps, recommendations are developed and prioritized based on the frequency and severity. Corrective actions are directed at the activities and mechanisms that result in the greatest number of injuries. 5.6.2. Monitor Approach. In this method, the safety staff selects categories of raw data and reviews them regularly in the form of tabulations or rates. The object is to identify trends and problem areas. Selection of the areas to be monitored depends on the available data and the needs of the organization. Mishap reports are a good place to start, but other areas should not be overlooked. Some other categories that may be appropriate for analysis are: 5.6.2.1. Hazardous Air Traffic Reports. 5.6.2.2. High Accident Potential Reports. 5.6.2.3. Deficiency Reports. 5.6.2.4. Inspection/Evaluation Reports. 5.6.2.5. Foreign Object Damage (FOD) Reports. 5.6.2.6. First-Aid Cases.
AFI91-202 5 AUGUST 2011 51 5.6.2.7. Maintenance Logs or Reports. 5.6.2.8. Hazard Reports. 5.6.3. Study Approach. This is a detailed examination of a problem. A study should follow a systematic process. It typically follows the format of the Scientific Method. The researcher first drafts a problem statement that clearly defines the goals of the study. For example, a suitably specific research question might be ―Determine a trend in the frequency of X and identify possible explanations for this trend.‖ The researcher will then conduct background research to identify factors and data relevant to the problem. Then the researcher must draft an objective statement that describes the problem and limits the study (the hypothesis or purpose). An example is ―X is increasing because of Y.‖ Then the researcher develops a plan on how these factors and data are going to be collected, tabulated, compared, plotted and analyzed (methods). Finally, the data is collected and analyzed and results reported confirming or denying the hypotheses. Conclusions and implications regarding application of the results of the study are the most important outcome of the study. 5.7. Use of Analyzed Data. The purpose of analysis is to help prevent mishaps. Present conclusions drawn in a useful format to the people who can use them directly in their prevention programs. The data should also be available to other organizations with like equipment or problems. After taking corrective actions, follow-up analysis may be done to measure the effectiveness of these actions. 5.8. Safety Analysis Team (SAT) Process. The SAT process is a proactive, data-driven process with the goal of providing commanders with unbiased, rank-ordered risk mitigation strategies to assist in resource allocation for the preservation of combat capability. 5.8.1. The SAT process focuses exclusively on Subject Matter Expert (SME) analysis of mishap reports, identification of ―documented‖ risk and development of risk mitigation strategies to meet these hazards. The process then considers the effectiveness of each of the strategies weighed against real-world constraints, and through detailed mathematical analysis provides commanders with a rank-ordered list of qualified and quantified recommendations for implementation. 5.8.2. SAT assessments can be requested through the AFSC Analysis and Integration Division (AFSC/SEA). All requests are approved by AF/SE. HQ AFSC/SEA will conduct the study and provide a final report and out-brief to the requesting commander. For additional information contact HQ AFSC/SEA; DSN: 246-1562, Commercial: (505) 846- 1562. 5.9. Air Force Culture Assessment Safety Tool (AFCAST). AFCAST provides squadron commanders and above with web-based tools to survey aircrew, maintenance and support personnel regarding safety issues. AFCAST also offers ground safety versions for Drinking and Driving, Private Motor Vehicle, Motorcycle, and Off-duty and Outdoor Recreational Activity. 5.9.1. AFCAST helps commanders identify safety concerns and hazards while highlighting where to focus their hazard assessment efforts. This tool’s key goal is identification and correction of subtle organizational conditions that increase mishap potential. Commanders receive real-time feedback on attitudes and perceptions concerning safety climate and culture, resource availability, workload, progress of safety intervention programs and other operational factors relating to safety.
- Page 7 and 8: Clear Zones, as well as apron areas
- Page 9 and 10: BY ORDER OF THE SECRETARY OF THE AI
- Page 11 and 12: AFI91-202 5 AUGUST 2011 3 2.4. Safe
- Page 13 and 14: AFI91-202 5 AUGUST 2011 5 8.6. Haza
- Page 15 and 16: AFI91-202 5 AUGUST 2011 7 Attachmen
- Page 17 and 18: AFI91-202 5 AUGUST 2011 9 (CFR), an
- Page 19 and 20: AFI91-202 5 AUGUST 2011 11 1.5.6.3.
- Page 21 and 22: AFI91-202 5 AUGUST 2011 13 1.5.10.6
- Page 23 and 24: AFI91-202 5 AUGUST 2011 15 1.5.11.1
- Page 25 and 26: AFI91-202 5 AUGUST 2011 17 1.5.14.8
- Page 27 and 28: AFI91-202 5 AUGUST 2011 19 leadersh
- Page 29 and 30: AFI91-202 5 AUGUST 2011 21 disabili
- Page 31 and 32: AFI91-202 5 AUGUST 2011 23 1.5.17.9
- Page 33 and 34: AFI91-202 5 AUGUST 2011 25 1.5.20.8
- Page 35 and 36: AFI91-202 5 AUGUST 2011 27 1.5.21.1
- Page 37 and 38: AFI91-202 5 AUGUST 2011 29 Chapter
- Page 39 and 40: AFI91-202 5 AUGUST 2011 31 ASPM. Th
- Page 41 and 42: AFI91-202 5 AUGUST 2011 33 2.2.4.5.
- Page 43 and 44: AFI91-202 5 AUGUST 2011 35 activiti
- Page 45 and 46: AFI91-202 5 AUGUST 2011 37 2.6.2.2.
- Page 47 and 48: AFI91-202 5 AUGUST 2011 39 Chapter
- Page 49 and 50: AFI91-202 5 AUGUST 2011 41 operatio
- Page 51 and 52: AFI91-202 5 AUGUST 2011 43 3.5.3.4.
- Page 53 and 54: AFI91-202 5 AUGUST 2011 45 office.
- Page 55 and 56: AFI91-202 5 AUGUST 2011 47 4.3.4.4.
- Page 57: AFI91-202 5 AUGUST 2011 49 Chapter
- Page 61 and 62: AFI91-202 5 AUGUST 2011 53 5.11.4.
- Page 63 and 64: AFI91-202 5 AUGUST 2011 55 Chapter
- Page 65 and 66: AFI91-202 5 AUGUST 2011 57 6.3.2.1.
- Page 67 and 68: AFI91-202 5 AUGUST 2011 59 6.3.3.10
- Page 69 and 70: AFI91-202 5 AUGUST 2011 61 (misfire
- Page 71 and 72: AFI91-202 5 AUGUST 2011 63 Chapter
- Page 73 and 74: AFI91-202 5 AUGUST 2011 65 owning M
- Page 75 and 76: AFI91-202 5 AUGUST 2011 67 on wildl
- Page 77 and 78: AFI91-202 5 AUGUST 2011 69 unit mis
- Page 79 and 80: AFI91-202 5 AUGUST 2011 71 construc
- Page 81 and 82: AFI91-202 5 AUGUST 2011 73 8.3.4. R
- Page 83 and 84: AFI91-202 5 AUGUST 2011 75 8.6. Haz
- Page 85 and 86: AFI91-202 5 AUGUST 2011 77 8.7.4.2.
- Page 87 and 88: AFI91-202 5 AUGUST 2011 79 8.8.6.1.
- Page 89 and 90: AFI91-202 5 AUGUST 2011 81 Chapter
- Page 91 and 92: AFI91-202 5 AUGUST 2011 83 9.4.8.12
- Page 93 and 94: AFI91-202 5 AUGUST 2011 85 9.10.2.
- Page 95 and 96: AFI91-202 5 AUGUST 2011 87 Chapter
- Page 97 and 98: AFI91-202 5 AUGUST 2011 89 Chapter
- Page 99 and 100: AFI91-202 5 AUGUST 2011 91 procedur
- Page 101 and 102: AFI91-202 5 AUGUST 2011 93 11.2.4.1
- Page 103 and 104: AFI91-202 5 AUGUST 2011 95 11.2.7.1
- Page 105 and 106: AFI91-202 5 AUGUST 2011 97 support
- Page 107 and 108: AFI91-202 5 AUGUST 2011 99 the char
50 AFI91-202 5 AUGUST 2011<br />
5.4.1. Safety meetings.<br />
5.4.2. Supervisor safety briefings.<br />
5.4.3. Base newspapers and bulletins.<br />
5.4.4. Safety publications.<br />
5.4.5. HQ/AFSC or MAJCOM publications.<br />
5.4.6. Electronically via e-mail, web page or video.<br />
5.5. Mishap Analysis Program. In order to reduce mishaps, Commanders and Chiefs of Safety<br />
must know the type and number of mishaps that occur in their command. Once the type and<br />
number are identified, commanders can take risk mitigation actions based on sound statistical<br />
data. This historical look-back approach should not preclude a proactive, forward looking mishap<br />
prevention plan based on pre-identified hazards that haven’t yet caused a mishap.<br />
5.5.1. MAJCOMs and Wings will:<br />
5.5.1.1. Conduct a annual analysis and develop specific actions to reverse adverse trends.<br />
Analysis should target specific problem areas with recommendations for commander<br />
approval and appropriate actions.<br />
5.5.1.2. Analysis programs must identify successes or problem areas and trends, measure<br />
safety program effectiveness and guide prevention actions.<br />
5.5.2. HQ AFSC will perform <strong>Air</strong> <strong>Force</strong> level trend analysis and publish results. In addition,<br />
AFSC may conduct Safety Analysis Team (SAT) hazard and mishap trend analysis (as<br />
described in paragraph 5.8) for MAJCOMs, as directed by AF/SE.<br />
5.6. Mishap Prevention Analysis Methods. There are several ways to approach analysis of<br />
mishap data for mishap prevention purposes. Program analysis functions are to target, monitor<br />
and/or study.<br />
5.6.1. Target Approach. This approach is similar to the study method below. After<br />
determining causes of mishaps, recommendations are developed and prioritized based on the<br />
frequency and severity. Corrective actions are directed at the activities and mechanisms that<br />
result in the greatest number of injuries.<br />
5.6.2. Monitor Approach. In this method, the safety staff selects categories of raw data and<br />
reviews them regularly in the form of tabulations or rates. The object is to identify trends and<br />
problem areas. Selection of the areas to be monitored depends on the available data and the<br />
needs of the organization. Mishap reports are a good place to start, but other areas should not<br />
be overlooked. Some other categories that may be appropriate for analysis are:<br />
5.6.2.1. Hazardous <strong>Air</strong> Traffic Reports.<br />
5.6.2.2. High Accident Potential Reports.<br />
5.6.2.3. Deficiency Reports.<br />
5.6.2.4. Inspection/Evaluation Reports.<br />
5.6.2.5. Foreign Object Damage (FOD) Reports.<br />
5.6.2.6. First-Aid Cases.