...
We can’t really confirm because the servo was ripped off, but hopefully we have pictures of the photos before it was damaged
Damage was 2 motors, 2 props, entire airframe, at least one wing
Other electronics are okay
One battery is GGed (puffed out), other is probably bad but needs to be replaced anyways
these were old batteries anyways
We have more motors coming in, but we are out for now
Both have been clearly sharpie labelled
Design airframe to protect critical components in the future
We need some way to protect the motor
This is more about protecting the motor than the prop, Mech to reassess
We will need to retest all electronics following this even the ones that aren't visually destroyed.
We weren't able to successfully transition back to quad during the crash
From logs it seems like it was trying to pull out of nose dive before transitioning to quad
It cant transition to quad when at such a steep angle - it may want to turn all on at once
Possibly the aircraft was fully inverted
Data cuts off at 40m altitiude.
We crashed above where we took off, but no way it was 40 meters
We need to take photos as we unplug and disassemble the cabin to see if the Pixhawk was unplugged
We should check things sooner rather than later to assess if we need to reorder stuff.
Someone needs to take this mess of notes and properly fill out this RCA lmao
Review of the elevator servo motor, as well as the flight controller configuration reveals that the autopilot sent elevator commands inverted to expected (pitch up requests were actually pitch down). This is likely the primary cause of the dramatic pitch down events which lead to the crash.
⏱ Incident timeline
Describe (approximate) timelines, cross-correlate with telemetry/video recordings/etc if any.
Pilot inputs as perceived by pilot on sortie 3:
arm
took off in QLoiter
switched to FBWA
switched to QLoiter
switched to FBWA
spammed the button to switch to QLoiter
⛑ 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. |
...