📋Incident overview
Postmortem owner | |
---|---|
Airframe | Houston |
Related incidents | |
Incident date |
|
Approx. Damage Costs | $35 |
Report Date | Completed |
🔮 Executive summary
While testing and setting up the Baby Ratel 2 camera with the on-screen display for video testing on Houston, an incorrectly ordered JST-GH cable with a flipped positive and negative connection caused a short on the camera.
The short smoked the camera which is now fully unusable.
⏱ Incident timeline
The members testing the camera found a JST-GH cable that was unused and from a different product that was 3-pin and needed to be used to interface with the OSD.
The members disassembled the Camera + 1.3GHz VTX setup that was connected with no OSD
The members began assembly with the Houston flight controller, adding the camera and VTX to the OSD and connecting it to the power connectors on Houston
The members plugged in Houston with a 3S LiPo battery. A flipped positive and negative wire on the OSD connecting to the camera caused the camera to smoke out.
The power was promptly disconnected. No other damage has been reported, and all other parts have been tested and verified as working.
⛑ 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. | Houston was instantly unplugged and the wiring connections from the OSD to the camera, as well as to all other parts of the video setup were rigorously verified, including with a DMM to ensure that no other oversight was taking place. |
🗃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. | A similar issue was caused before the February 19th flight test where the negative and positive connectors on an ESC on cornflakes was flipped. While the cause of the accident rhymed, the cause of this accident was due to trust that the cable we found matched the pin out. On the ESC, the accident was caused by incorrectly soldered cables. |
🤔 Lessons learnedDescribe what you learned, what went well, and how you can improve. |
|
✅ Recommendations for future
Actionable Recommendation | Reasoning |
---|---|