Explosion at Acme Chemical Company

Similar documents
REVIEW OF MANAGEMENT AND OVERSIGHT OF THE INTEGRATED BUSINESS MANAGEMENT SYSTEM (IBMS) January 16, 2009

Virginia State University Policies Manual. Title: Information Security Program Policy: 6110

Vaccine data collection tool Oct Functions, Indicators & Sub-Indicators

BUILDING CYBERSECURITY CAPABILITY, MATURITY, RESILIENCE

Standard Operating Procedure Title: Product Complaint Procedure

Process Safety Management in R&D

Virginia Commonwealth University School of Medicine Information Security Standard

STAFF REPORT. January 26, Audit Committee. Information Security Framework. Purpose:

SMS for Part 121 Notice of Proposed Rulemaking (NPRM)

Law Enforcement Commercial Price List ManTech International Corporation August 2017

Standard Operating Procedure. Data Management. Adapted with the kind permission of University Hospitals Bristol NHS Foundation Trust

Children s Services Council of Palm Beach County

Security and Privacy Governance Program Guidelines

Are You GHS Compliant or at RISK for FINES?

ELECTRICAL ENGINEERING & INSTRUMENTATION MECHANICAL ENGINEERING BIOLOGICAL & INDUSTRIAL ENGINEERING NUCLEAR ENGINEERING STRUCTURAL & CIVIL

BUSINESS CONTINUITY. Topics covered in this checklist include: General Planning

Audit and Compliance Committee - Agenda

manner. IOPA conducts its reviews in conformance with Government Auditing Standards issued by the Comptroller General of the United States.

MNsure Privacy Program Strategic Plan FY

CYBER RISK MANAGEMENT

Informed Consent and the Consent Form

Management s Response to the Auditor General s Review of Management and Oversight of the Integrated Business Management System (IBMS)

Apex Information Security Policy

Appendix 3 Disaster Recovery Plan

Battery Program Management Document

UNIVERSITY OF MASSACHUSETTS AMHERST INFORMATION SECURITY POLICY September 20, 2017

TARGET2-SECURITIES INFORMATION SECURITY REQUIREMENTS

Accreditation Body Evaluation Procedure for AASHTO R18 Accreditation

SECURITY & PRIVACY DOCUMENTATION

NEW YORK CYBERSECURITY REGULATION COMPLIANCE GUIDE

ORA HIPAA Security. All Affiliate Research Policy Subject: HIPAA Security File Under: For Researchers

OPG Comments on REGDOC-1.1.5, Licence Application Guide: Small Modular Reactor Facilities

IRB RESEARCH REPOSITORY COMPLIANCE PROGRAM: Repository Protocols and FAQs

DISASTER RECOVERY PRIMER

NERC Staff Organization Chart 2015 Budget

Standard COM-002-2a Communications and Coordination

DEFINITIONS AND REFERENCES

Chapter 10: Regulatory Documentation

BRANDMAN UNIVERSITY INSTITUTIONAL REVIEW BOARD Continuing Review Request/Closure Report

UNIVERSITY OF MASSACHUSETTS AMHERST INFORMATION SECURITY POLICY October 25, 2017

Cyber Threats? How to Stop?

Purpose: To describe the requirements for managing IP at the clinical site

Emergency Operations Center Management Exercise Evaluation Guide

Information Technology Security Plan Policies, Controls, and Procedures Identify Governance ID.GV

Security Director - VisionFund International

Mark Littlejohn June 23, 2016 DON T GO IT ALONE. Achieving Cyber Security using Managed Services

KENYA ACCREDITATION SERVICE

Hong Kong Accountability Benchmarking Micro-Study. Nymity Accountability Workshop 10 June 2015, Office of the PCPD, Hong Kong

Accountable Care Organizations: Testing Their Impact

State of West Virginia Department of Health and Human Resources (DHHR) Office of Management Information Services (OMIS)

INFORMATION SECURITY AND RISK POLICY

Project Cyber Security - Order No. 791 Identify, Assess, and Correct; Low Impact; Transient Devices; and Communication Networks Directives

ISPE Annual Meeting 8 11 November 2015 Philadelphia, PA. Forensic Auditing for Data Integrity. Rebecca A. Brewer Quality Executive Partners

UK Permanent Salary Index November 2013 Based on registered vacancies and actual placements

REPORT 2015/010 INTERNAL AUDIT DIVISION

AUDIT UNITED NATIONS VOLUNTEERS PROGRAMME INFORMATION AND COMMUNICATION TECHNOLOGY. Report No Issue Date: 8 January 2014

Standard Development Timeline

Public Safety Canada. Audit of the Business Continuity Planning Program

ISO/IEC Solution Brief ISO/IEC EventTracker 8815 Centre Park Drive, Columbia MD 21045

PLEASE NOTE. - Text the phrase MICHAELBERWA428 to the number /23/2016 1

IT SECURITY OFFICER. Department: Information Technology. Pay Range: Professional 18

Networked Access to Library Resources

Manager, Infrastructure Services. Position Number Community Division/Region Yellowknife Technology Service Centre

TURNING STRATEGIES INTO ACTION DISASTER MANAGEMENT BUREAU STRATEGIC PLAN

Putting It All Together:

PRODUCT SAFETY PROFESSIONAL CERTIFICATION PROGRAM DETAILS. Overview

MHCC Emergency Notification System (ENS) Protocols

POWER AND WATER CORPORATION POLICY MANAGEMENT OF EXTERNAL SERVICE PROVIDERS

National Policy and Guiding Principles

Laboratory Safety Guideline Laboratory Safety Data Sheets (SDS) Management, Understanding, Preparation

Continuity of Operations During Disasters: Electronic Systems and Medical Records

CYBERSECURITY RESILIENCE

Chapter 18 SaskPower Managing the Risk of Cyber Incidents 1.0 MAIN POINTS

The Role of the American National Standards Institute (ANSI) Irwin Silverstein, Ph.D. IPEA

STATE OF NEW JERSEY IT CIRCULAR

Emergency Support Function (ESF) #17a: COMMUNICATIONS: PUBLIC. ESF Activation Contact: Cornell University Police (607)

European Aviation Safety Agency

Reviewed by ADM(RS) in accordance with the Access to Information Act. Information UNCLASSIFIED.

Data Protection Policy

Policy Title; Business Continuity Management Policy. Date Published/Reviewed; February 2018

2017 LEGISLATIVE recommendations cyber security

Arctic Data Center: Call for Synthesis Working Group Proposals Due May 23, 2018

NERC Staff Organization Chart

ACCREDITATION COMMISSION FOR CONFORMITY ASSESSMENT BODIES

Management & Operations Excellence

CRISIS TEAM GUIDE TO RESPONSE IN US WATERS

ISO27001 Preparing your business with Snare

NRC INSPECTION MANUAL MANUAL CHAPTER 0609

11/14/2018. Istanbul Governance, risk, and compliance (GRC)

RPR CRITERIA AND FORMATS

Number: USF System Emergency Management Responsible Office: Administrative Services

NHS Gloucestershire Clinical Commissioning Group. Business Continuity Strategy

MDCSystems. MICHAEL A. BAKER, P.E., M.S.E.M. Consulting Engineer

FLORIDA S PREHOSPITAL EMERGENCY MEDICAL SERVICES TRACKING & REPORTING SYSTEM

Completing & Submitted the IRB Approval of Human Subjects Form

NERC Staff Organization Chart Budget

Global Life Sciences Royalty Rates & Deal Terms Survey 2018 Survey

Code of Practice for the TL 9000 Certification Process. Release 8.0

RI AND RF CRITERIA AND FORMATS

NERC Staff Organization Chart Budget 2018

Transcription:

ROOT CAUSE ANALYSIS REPORT EXAMPLE: Explosion at Acme Chemical Company AGENCY Acme Chemical Co. REFERENCE NO. ACH#200-1 PROGRAM Lab DATE RCA COMPLETED 12/11/16 FACILITY Seattle West DATE OF EVENT 11/27/16 ADDRESS RCA TEAM MEMBERS 123 Pine St., Seattle, WA Mark Berry, Laboratory Manager; Bob Graphy, Company Safety Officer; Team Leader: Rick James, R&D Officer 1. THE EVENT Describe what happened and any harm that resulted. Identify the proximate cause, if known. During synthesis of a large batch of nickle hydrazine perchlorate (NHP) derivative, a laboratory explosion occurred. The compound detonated, injuing one laboratory analyst. 2. BACKGROUND & FACTORS SUMMARY Answer the following questions briefly, attach supporting documents if necessary 2.1. Describe the sequence of events that was expected to take place. Attach flowchart if necessary. As single batch of less than 100 milligrams of NHP was to be synthesized, with any deviation from the protocol being checked through the Prinicipal Investigator (PI). 2.2. Was there a deviation for the expected sequence of events? If yes, describe. Attach flowchart if necessary. Yes, a batch of 10 grams was planned for synthesis. The PI was not consulted in the scaling up of the production. 2.3. Was any deviation from the expected sequence likely to have led to or did contribute to the adverse event? If yes, describe. Yes, a batch of over a 300 milligram quantity becomes unstable and explosive. 2.4. Was the expected sequence described in written policy, procedure, guidelines, or expressed in staff training? If yes, cite the source. Yes, the Laboratory Analyst was trained in Lab Safety procedures and further trained in additional lab satefy techniques (all training is current). It was reiterated in the morning meeting that any deviations to lab protocol must be assessed by the PI. 2.5. Does the expected sequence or process meet any regulatory requirements and/or practice standards? Cite any references reviewed by the team. If no, describe the the deviation from the requirements. Yes. The team reviewed the American Chemical Society manual, MSDS sheets, and official laboratory safety policies. 2.6. Did human action or inaction appear to contribute to the adverse event? If yes, describe the actions and how they contributed. Yes, the laboratory analyst should have checked the scaling up of the chemical compound manufacture with the PI prior to mixing the chemicals. 2.7. Did a defect, malfunction, misuse of, or absence of equipment appear to contribute to the event? If yes, describe what equipment and how it appeared to contribute. No. 2.8. Was the procedure or activity involved in the event being carried out in the usual location? If no, describe where and why a different location was utilized. Yes. 2.9. Was the procedure or activity being carried out by regular staff familiar with the consumer and activity? If no, describe who was carrying out the activity and why regular staff were not involved. Yes. However, this staff member has only performed the synthesis on four occasions. 2.10. Were involved staff credentialed/skilled to carry out the tasks expected of them? If no, describe the perceived inadequacy.

Yes. 2.11. Were staff trained to carry out their respective responsibilities? If no, describe the perceived inadequacy. Yes. 2.12. Were staffing levels considered to have been adequate at the time of the incident? If no, describe why. No. The PI, nor any other PI's were present in the laboratory that day. 2.13. Were there other staffing factors identified as responsible for or contributing to the adverse event? If yes, describe those factors. Yes. The responsible Analyst was the most senior in the lab that day, with only two years experience, while the other analysts present all had less than one year experience. 2.14. Did inaccurate or ambiguous information contribute to or cause the adverse event? If yes, describe what information and how it contributed. Yes. Analysts regularly scale up when making compounds in order to make enough for multiple tests. The MSDSs did not specify risk associated with making this compound above a threshold. 2.15. Did a lack of communication or incomplete communication contribute to or cause the adverse event? If yes, describe who and what and how it contributed. Yes. The PI responsible should have reviewed all potential risks associated with this project prior to the project commencing. 2.16. Did any environmental factors contribute to or cause the adverse event? If yes, describe what factors and how they contributed. No. 2.17. Did any organizational or leadership factors contribute to or cause the adverse event. If yes, describe what factors and how they contributed. Yes. The PI is ultimately responsible for this accident due to inadequately preparing the team. 2.18. Did any assessment or planning factors contribute to or cause the adverse event? If yes, describe what factors and how they contributed. Yes. Proper assessment of the chemical synthesis risk should have been reviewed. 2.19. What other factors are considered relevant to the adverse event? Describe. N/A 2.20. Rank order the factors considered responsible for the adverse event, beginning with the proximate cause, followed by the most important to less important contributory factors. Attach Contributory Factors Diagram, if available. 1. Lack of PI oversight, project safety review 2. Lack of chemical safety information on MSDS sheet 3. Lack of analyst experience 2.21. Was a root cause identified? If yes, describe. Yes. The PI should have performed a comprehensive safety review of the chemicals being synthesized in the experiment and any potential safety indications prior to starting the project work. Since scaling up is done regularly in the lab, this should have been anticipated. 3. RISK REDUCTION ACTIONS TAKEN List the actions that have already been taken to reduce the risk of a future occurrence of the event under consideration. Note the date of implementation.

A safety semainar was conducted with all project PIs on staff. Reviewed were the protocols for reviewing each project with their team prior to work being performed, looking for potential hazards. HR has assigned each PI a cellular phone to be carried at all times so that their team may reach team (especially night shift). All lab analysts were retrained on lab safety policies. Each shift will also have a senior analyst scheduled. The MSDS sheet for NHP was updated with batch size notes. 4. PREVENTION STRATEGIES List from highest priority to lowest priority the recommended actions designed to prevent a future occurrence of the adverse event. Begin with a rank of 1 (highest). For each strategy or action provide an estimated cost, if known, and any additional considerations or recommendations for implementing the strategy (e.g., phase-in, immediate need, triage by risk. RANK STRATEGY ESTIMATED COST SPECIAL CONSIDERATIONS 1 All lab-staff safety training $1500-$2000 Batch size considerations, personal protective equipment 2 Communication equipment $7,000 See current cell contract in HR 5. INCIDENTAL FINDINGS List and describe any incidental findings that should be carefully reviewed for corrective action. Consider discipline of PI. HR recommendations under consideration. 6. APPROVAL After review of this summary report, all team members should notify the team leader of either their approval or recommendations for revision. Following all revisions the report should be signed by the team leader prior to submission. Signature of Team Leader /s/ Rick James Date of Signature 12/11/16 The information contained in this report is confidential and intended solely to promote safety and reduce consumer risk. Forward this report to all RCA Janet Pritchard Mack Davis Judy Harris NAME TITLE ORGANIZATION ADDRESS EMAIL HR Liasion HR same as above jpritch@ach.com Div Chief Admin same as above mdavis@ach.com Deputy CEO Admin same as above jharris@ach.com CLICK HERE TO CREATE ROOT CAUSE ANALYSIS REPORT TEMPLATES IN SMARTSHEET