Professional Documents
Culture Documents
004 Incident Investigations PDF
004 Incident Investigations PDF
004
October 2013 Revision 05
SUMMARY:
This EH&S Instruction contains reporting requirements and general instructions for completing incident investigations,
as well as a sample incident investigation form. The sample form in Attachment 1 can be used to gather required data.
For all work related injuries/illnesses the ‘Recordkeeping Rationale Form’ (Attachment 2), must also be completed.
The following incidents must be reported in the UTC EH&S Reporting System using the Incident Investigation module:
• Fatality/serious injury/serious near miss (UTC Policy 33 Reportable Incident)
• Fatality/serious injury/serious near miss for contractor employees (UTC Policy 33 Reportable Incident)
• Recordable injuries/illnesses
• First Aid Cases
• Cardinal Rule Violations2
The following adverse events must be reported in the UTC EH&S Reporting System using the Compliance module1.
• Serious environmental incident / Serious environmental near miss (UTC Policy 52 Reportable Incident)
• Discovery of any chemical spill or release, fire, etc.
• Government notice of violation or receipt of any government agency correspondence that suggests or alleges non-
compliance with any EH&S legal requirement
• Permit / regulatory non-conformance
For an overview and guidance of reporting requirements for EH&S Incidents, see Attachment 7.
The Tap Root® investigation process is required for all Cardinal Rule violations, recordable incidents, serious near
misses, government enforcement actions, serious environmental incidents, and reportable releases.
Cardinal Rule Violations are required to be reported using the process outlined in Attachment 3.
All first aid and near miss incidents require some level of incident investigation to establish root cause using the
appropriate ACE Relentless Root Cause Tool(s) (see Attachment 6).
For trending purposes, root cause and corrective action data shall be entered in the ERS system Incident Investigation
Module for all near miss and first aid cases.
DEFINITIONS:
Cardinal Rule: See the UTC EH&S Management System, Appendix C.
Near Miss: See EH&S Instruction 037 “Reporting of EH&S Serious Incidents.”
Serious Injury: See EH&S Instruction 037 “Reporting of EH&S Serious Incidents”
Serious Near Miss: See EH&S Instruction 037 “Reporting of EH&S Serious Incidents”
1
See UTAS Instruction 001 for a detailed list of additional reporting obligations that must be made to UTAS EH&S
relative to the compliance program.
2
Cardinal Rule Violations must be evaluated for appropriate disciplinary action in accordance with UTAS DP126 and
documented in the EH&S Reporting System in the Safety / Recognition and Discipline module.
This document or file contains no EAR technology or ITAR technical data. iClass Identifier: CLS01143529.
G:\Management Systems\Procedures\EH&S Instructions Page 1 of 17
UTAS EH&S INSTRUCTION No. 004
October 2013 Revision 05
KEY ELEMENTS:
The main purpose of an EH&S incident investigation is to determine the underlying root cause or causes of the incident
and to ensure appropriate corrective actions are identified. The investigation process must provide answers to the
following questions: Who? What? When? Where? How? Why?
The following process provides a framework suitable for use in conducting incident investigations.
Classify significance of
Incident / incident / near miss & report Form Cross Site Evaluation/Data
Near Miss Functional Team Collections
Occurs -Cardinal Rule Violation?
-Recordable Incident?
-Serious Near Miss?
-Government Enforcement Actions?
-Serious Environmental Incidents
-Reportable Releases?
YES - Conduct NO - Use
TapRoot Investigation ACE Tools
The following instructions provide a sample framework suitable for use in conducting incident
investigations. Refer to pages 9 and 10 for instructions on how to complete the incident investigation report.
Incident/Near Miss
Accident or near miss has occurred. Injured employees must be attended to and the scene secured.
Applicable supervisor / manager shall initiate the investigation by identifying who, what, where and when.
Refer to questions 1-25 of the incident investigation report (Attachment 1).
This document or file contains no EAR technology or ITAR technical data. iClass Identifier: CLS01143529.
G:\Management Systems\Procedures\EH&S Instructions Page 2 of 17
UTAS EH&S INSTRUCTION No. 004
October 2013 Revision 05
Analyze Data
Evaluate the collected data utilizing brainstorming and relentless root cause analysis techniques. Define the
problem, document ideas, clarify and combine, prioritize, and discard those that did not contribute to the
incident under investigation. A fishbone diagram is one method to perform this process. Use Tap Root®
investigation process to identify causal factors and root causes for OSHA recordable, Policy 33 incidents,
Cardinal Rules violations, serious near misses, and government enforcement actions. Root causes for first
aid cases must be identified through Tap Root® or other appropriate root cause methodology (i.e., 5 Why’s,
Fishbone diagram, etc.).
Verify Root Cause (when not a Tap Root required event. See pp 1-2)
When a final cause (or causes) have been determined, apply a root cause test. Is the cause a management
system failure? Is it controllable? Apply the 5 Why’s test. Will corrective action prevent recurrences?
This document or file contains no EAR technology or ITAR technical data. iClass Identifier: CLS01143529.
G:\Management Systems\Procedures\EH&S Instructions Page 3 of 17
UTAS EH&S INSTRUCTION No. 004
October 2013 Revision 05
Incident investigations should be conducted as soon as possible after the incident occurs or is reported.
Investigations rely on obtaining the facts of the case from involved parties and important details may be lost
as time progresses. Also, prompt investigation is consistent with the UTC and UTAS commitment to
providing a safe workplace for our employees.
The significant milestones are as follows (see Attachment 5 for an example of a site-specific incident
protocol checklist):
Immediately: Provide treatment / clean-up activities
Within 24 hours: Determine initial severity / significance; verbally report incident as applicable
First 48 hours: Enter initial incident information into ERS
First 14 days: Conduct incident investigation; develop CAPA; prepare incident review
14th day: Send incident review report to UTAS Safety Manager (Attachment 4)
14th – 30th day: Report out on incident review with site & business leadership and Central EH&S
Document
Changes
Revision No. Date Description of Change
0 5/01/07 Initial release
1 6/2/09 Required online reporting of:
• any Cardinal Rule violation (w/ associated TapRooT)
• Near Misses which could have resulted in a serious injury
2 7/1/09 Use of the Tap Root® investigation process is required for all cardinal
rule violations, recordable incidents, serious near misses, government
enforcement actions, serious environmental incidents, and reportable
releases.
3 9/30/11 Amended Incident Investigation Process and amended flow chart (p.1)
Amended paragraph; Classify significance of incident/near miss and
report to include Cardinal Rule violation reporting process
This document or file contains no EAR technology or ITAR technical data. iClass Identifier: CLS01143529.
G:\Management Systems\Procedures\EH&S Instructions Page 4 of 17
UTAS EH&S INSTRUCTION No. 004
October 2013 Revision 05
This document or file contains no EAR technology or ITAR technical data. iClass Identifier: CLS01143529.
G:\Management Systems\Procedures\EH&S Instructions Page 5 of 17
Incident ID:___________
Attachment 1 Assigned by On-Line Reporting System
Incident Investigation Report/Instructions
19) Employees Experience Performing Activity: <3 Months 3-12 Months >12
Months
20) Is there a written SOP for the Task? Yes No
Complete for Injury/Illness Only
21) Source of Injury/Incident
Asphyxiation Bite-Animal Bite- Insect
Burn/Scald Contact Hot Object Burn/Scald Corrosive Chemical Burn/Scald Extreme Temp
Burn/Scald Misc. Burn/Scald Weld Burns to Eyes Caught In, Between,Under Collapse Material
Caught In, Between, Under Machine Caught In, Between, Under Object Caught In, Between, Under Mechanical
Chemical Poisoning Cut, Puncture, Scrape by Tool Cut, Puncture, Scrape by Misc.
Cut, Puncture, Scrape by Lifted Obj. Cut, Puncture, Scrape by Power Tool Electric Shock or Burn Misc.
Explosion/Fire Foreign Body in Eye Misc.
Motor Vehicle – Auto Accident Occupational Skin Disease/Disorder Repetitive Motion
Slip, Trip, Fall from Ladder/Scaffold Slip, Trip, Fall on Same Level Slip, Trip, Fall from Different Level
Slip, Trip, Fall from Stairs Strain/Injured by Continual Noise Strain/Injured by Lifting/Carrying
Strain/Injured by Misc. Strain/Injured by Pushing or Pulling Strain/Injured by Reaching
Strain/Injured by Twisting Strain/Injured by Using Tool Striking Against/Stepping On Misc.
Striking Against/Stepping On Part Struck or Injured by Malicious Intent Struck or Injured by Escalator
Struck or Injured by Hand Tool Struck or Injured by Lift/Elevator Struck or Injured by Machining
Material
Struck or Injured by Motor Vehicle Struck or Injured by Moving Parts Struck or Injured by Object Held by
Others Struck or Injured by Lifted Object Unknown
This document or file contains no EAR technology or ITAR technical data. iClass Identifier: CLS01143529.
G:\Management Systems\Procedures\EH&S Instructions Page 7 of 17
UTAS EH&S INSTRUCTION No. 004
October 2013 Revision 05
34) Hazard:
Broken Tools/Machinery Chemical Exposure Confined Space Electrical Energy Hazard
Equip. Failure/Malfunction Equipment not certified Fire Hazard Hazardous Air Temp
Improper Tool Improper use of tool Inadequate Overhead Protection Insufficient Lighting
Investigation Incomplete Material not designed Mechanical Energy Hazard Other
Other Health Hazards Rotating Moving Equip Safety Equipment Malfunction Trip/Slip/Fall Hazard
Unguarded Equipment Unhealthy Breathing Unprotected Sharp Edge Unsafe Act of Third Party
Unsafe Driving Condition Unsafe Material Handling Unsafe Material Storage Unsafe Noise Level
Unsafe Scaffolding Wet Area
This document or file contains no EAR technology or ITAR technical data. iClass Identifier: CLS01143529.
G:\Management Systems\Procedures\EH&S Instructions Page 8 of 17
UTAS EH&S INSTRUCTION No. 004
October 2013 Revision 05
This document or file contains no EAR technology or ITAR technical data. iClass Identifier: CLS01143529.
G:\Management Systems\Procedures\EH&S Instructions Page 9 of 17
UTAS EH&S INSTRUCTION No. 004
October 2013 Revision 05
This document or file contains no EAR technology or ITAR technical data. iClass Identifier: CLS01143529.
G:\Management Systems\Procedures\EH&S Instructions Page 11 of 17
UTAS EH&S INSTRUCTION No. 004
October 2013 Revision 05
Attachment 2
UT Aerospace Systems
OSHA Recordkeeping Rationale Form
004A OSHA Rationale Form
* Case not recorded on OSHA log because (check all that apply):
the injured or ill person is not an employee
the employee did not experience an injury or illness
the case is not work-related since (check all that apply)
no work event or exposure is a discernable cause of the case or of significant aggravation
to a pre-existing condition
an OSHA exception to work relatedness applies
the case is not new – enter case number if already recorded on an OSHA log:
the case does not meet the general or specific cases recording criteria
Comments:
Recordkeeper: Date
This document or file contains no EAR technology or ITAR technical data. iClass Identifier: CLS01143529.
G:\Management Systems\Procedures\EH&S Instructions Page 12 of 17
UTAS EH&S INSTRUCTION No. 004
October 2013 Revision 05
Attachment 3
Cardinal Rule Violation Reporting Flowchart
Actors
Cardinal Rule Violations
Managers,
Identify CR violations through
Supervisors, Cell Leaders,
Observations, Risk Assessments (JHA
Site Employees,
Gold), Inspections, Audits, Program
EH&S Personnel,
Evaluations & AR/Risk Reviews
External Auditors
This document or file contains no EAR technology or ITAR technical data. iClass Identifier: CLS01143529.
G:\Management Systems\Procedures\EH&S Instructions Page 13 of 17
UTAS EH&S INSTRUCTION No. 004
October 2013 Revision 05
Attachment 4
UTAS Incident Review / TapRoot Template
004B TapRoot Template
This document or file contains no EAR technology or ITAR technical data. iClass Identifier: CLS01143529.
G:\Management Systems\Procedures\EH&S Instructions Page 14 of 17
UTAS EH&S INSTRUCTION No. 004
October 2013 Revision 05
Attachment 5
Example of site-specific incident protocol checklist
Incident:
Date of Incident:
4 5 days Perform RRCA investigation to determine root causes and corrective actions.
5 5 days (immediately after Populate Root Causes and Corrective Actions into the EHS Reporting System, with
RRCA) owners and dates.
6 7-10 days Populate the PowerPoint template with a summary of the incident and investigation.
These slides will be the talking points for management review.
7 Second week of the Discuss Incident and RRCA at monthly SBU EHS Dashboard Call. **
following month
This document or file contains no EAR technology or ITAR technical data. iClass Identifier: CLS01143529.
G:\Management Systems\Procedures\EH&S Instructions Page 15 of 17
UTAS EH&S INSTRUCTION No. 004
October 2013 Revision 05
Attachment 6
Potential tools for root cause analysis of first aids and near misses
(See RRCA Interactive Tool for more information
http://aceprod7.utc.com/vgn-ext-
templating/v/index.jsp?vgnextoid=654a466142440110VgnVCM1000000881000aRCRD)
FAULT TREE:
FLOW CHART:
3-LEGGED 5-WHY:
This document or file contains no EAR technology or ITAR technical data. iClass Identifier: CLS01143529.
G:\Management Systems\Procedures\EH&S Instructions Page 16 of 17
UTAS EH&S INSTRUCTION No. 004
October 2013 Revision 05
Attachment 7
EH&S Incident Reporting Guidance
004G Incident Reporting Guidance Matrix
This document or file contains no EAR technology or ITAR technical data. iClass Identifier: CLS01143529.
G:\Management Systems\Procedures\EH&S Instructions Page 17 of 17