Instructions | Report |
|---|
 Leadup
List the sequence of events that led to the incident.
| Unclear. Potentially: unprotected circuits inside the frame, loose cabling, water damage, overheating motor connections? |
🙅♀️ Fault
Describe what didn't work as expected. If available, include relevant data visualizations.
| PDB ended up burning a hole through itself. |
👁 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.
| Analysis was done in the bay, when we realized that the PDB on phoenix had scorch marks, as did the pizza box underneath the pdb. |
🙋♂️ Response
Report who responded to the incident and describe what they did at what times. Include any delays or obstacles to responding.
| Batteries unplugged upon arrival at crash. Drone moved to safe location clear of flammable materials (middle of road or sidewalk - was I prepared to chuck it? yes.) Electronics recovered from airframe.
|
🙆♀️ 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.
| < help Aidan Bowers (Deactivated) > Perhaps telemetry logging to prevent this from happening? |
🔎Five whys root cause identification
Run a 5-whys analysis to understand the true causes of the incident.
| why did pdb short? → 5s? but it’s rated for 2-12s → electrical loose connections? then how did it recover → ?!??!?!? <help Aidan Bowers (Deactivated) > |
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.
| Vanny short april 2022? |
🤔 Lessons learned
Describe what you learned, what went well, and how you can improve.
| Electrical Isolation, waterproofing, check cables before flight? |