...
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. | Drone did not fly as intended have unexpected flight behavior that is not even controllable in loiter mode. . Did run into a lot of prearm warning before the crash but the error does not appear when take off |
👁 DetectionReport when the team detected the incident and how they knew it was happening. Describe how the team could've improved time to detection. | The timing for the crash and not understood well. Need to reserach more to understand what is there. Probably involve more testing and document. |
🙋♂️ ResponseReport who responded to the incident and describe what they did at what times. Include any delays or obstacles to responding. | PIC for the flight test respond. Disarm the drone after lose control authority. |
🙆♀️ 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. | Suggesting to do auto tune and disable mag 0 since a lot of warning observed is MAG 0 realigned |
🤔 Lessons learnedDescribe what you learned, what went well, and how you can improve. |
...