Incident Inv

Module from the Process Safety Management Curriculum curriculum.

Module 8 - Incident Investigation (Element 12) · Learning Objectives · 1. Investigate any incident that could have resulted in catastrophic release · 2. Apply RCA methods: 5-Why, Fishbone, Apollo, TapRoot, Causal Tree · 3. Identify causes: physical (immediate), human, organizational · 4. Drive corrective actions to closure; track recurrence · 5. Report per API RP 754 for industry learning · Incident Investigation Method Comparison

Method	Complexity	Time Req	Best For	Notes	Ref
5-Why	Simple	< 1 day	Routine incidents	Can miss multi-cause	Toyota
Fishbone (Ishikawa)	Moderate	1-2 days	Brainstorming	Visual	Ishikawa
Fault Tree Analysis	Complex	Days-weeks	Quantitative	Can be probabilistic	CCPS
TapRoot	Moderate	Days	Multi-factor	Structured	TapRoot
Apollo RCA	Moderate	Days	Evidence-based	Cause-and-effect chain	Apollo
CCPS CASE HIStory	Structured	Days-weeks	PSM-specific	Industry standard	CCPS

Source: Process_Safety_Management_Curriculum_v1.xlsx · Sheet: Incident Inv

© 2026 Inflection Point Engineering, LLC. All rights reserved. The content of this page — including calculation methods, reference data, written analysis, interactive tools, and source code — is the intellectual property of Inflection Point Engineering, LLC and is protected under applicable copyright, trademark, and trade secret laws. Unauthorized reproduction, redistribution, modification, or derivative use in whole or in part is prohibited without prior written consent.

Disclaimer. This material is provided for informational and educational purposes only and does not constitute professional engineering advice. Calculations, reference data, and methodologies are based on published standards and accepted engineering practice but are not a substitute for engineering judgment, site-specific analysis, or review by a licensed Professional Engineer. Inflection Point Engineering, LLC makes no warranties, express or implied, regarding the accuracy, completeness, or fitness for a particular purpose of any content presented here, and shall not be liable for any direct, indirect, incidental, or consequential damages arising from its use. Users assume all risk associated with applying this content to real-world design, operations, or decisions.