Update the title following the format: Jan 01, 2023 - RCA Name
📋Incident overview
Postmortem owner | |
|---|---|
Airframe | Houston |
Related incidents | |
Incident date |
|
Approx. Damage Costs | $2 |
Report Date |
|
🔮 Executive summary
When flying Houston, sometime it yaws and rolls unexpectedly without any RC input. This only happens once every while but it has a serious potential to damage on-board electronics and must be rectified.
⏱ Incident timeline
2024-07-06 Houston Autonomy and EFS flight test A detailed summary of the timeline and recap are included in this document.
⛑ Postmortem report
Instructions | Report |
|---|---|
|
|
🙅♀️ FaultDescribe what didn't work as expected. If available, include relevant data visualizations. | Drone did not fly as intended in loiter mode. |
👁 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. |
Leadup✅ Recommendations for future
Actionable Recommendation | Reasoning |
|---|---|