Root Cause Analysis

Owned by Anthony Luo, created
Last updated: 2023-02-13 by Aaron Dyck (Deactivated)
1 min read
1 Incident overview | 2  Executive summary | 3  Incident timeline | 4  Postmortem report | 5  Recommendations for future

*** Refrain from using specific names inside an RCA. Refer to roles (ex: PIC) rather than mentioning specific individuals ***

Incident overview

Postmortem owner

Airframe

 

Related incidents

 

Incident date

 

Approx. Damage Costs

 

Report Date

 

 Executive summary

 Incident timeline

Describe (approximate) timelines, cross correlate with telemetry/video recordings/etc if any.

 

 Postmortem report

Instructions

Report

Instructions

Report

 Leadup


List the sequence of events that led to the incident.

 Fault


Describe what didn't work as expected. If available, include relevant data visualizations.

 

 Detection


Report when the team detected the incident and how they knew it was happening. Describe how the team could've improved time to detection.

 

 Response


Report who responded to the incident and describe what they did at what times. Include any delays or obstacles to responding.

 

 Recovery


Report how the user impact was mitigated and when the incident was deemed resolved. Describe how the team could've improved time to mitigation.

 

Five whys root cause identification


Run a 5-whys analysis to understand the true causes of the incident.

 

Related records


Check if any past incidents could've had the same root cause. Note what mitigation was attempted in those incidents and ask why this incident occurred again.

 

 Lessons learned


Describe what you learned, what went well, and how you can improve.

 

 

 Recommendations for future

Actionable Recommendation

Reasoning

Actionable Recommendation

Reasoning