@bUpdate the title following the format: Jan 01, 2023 - RCA Name
📋Incident overview
Postmortem owner | |
---|---|
Airframe | Tube |
Related incidents | Apr 09 Flight Test |
Incident date |
|
Approx. Damage Costs | $25 |
Report Date |
|
🔮 Executive summary
Pilot lost orientation of aircraft
Pilot crashed aircraft
Noticed no puncture in any of the cells, decided to transport back to the bay
Got to the bay, noticed battery was slightly warmer than other 3S packs
Attempted to communicate with safety office, got deferred to special constable (off hours)
Special Constable came, investigated the situation
Special Constable attempted to contact the safety office, unsuccessful, directed to contact the fire department
Fire department concluded no risk, and left
Special
⏱ Incident timeline
Describe (approximate) timelines, cross-correlate with telemetry/video recordings/etc if any.
⛑ Postmortem report
Instructions | Report |
---|---|
LeadupList the sequence of events that led to the incident. | |
🙅♀️ FaultDescribe what didn't work as expected. If available, include relevant data visualizations. | |
👁 DetectionReport when the team detected the incident and how they knew it was happening. Describe how the team could've improved time to detection. | |
🙋♂️ ResponseReport who responded to the incident and describe what they did at what times. Include any delays or obstacles to responding. | |
🙆♀️ RecoveryReport 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 identificationRun a 5-whys analysis to understand the true causes of the incident. | |
🗃Related recordsCheck 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 learnedDescribe what you learned, what went well, and how you can improve. |
✅ Recommendations for future
Actionable Recommendation | Reasoning |
---|---|