Clusterphiliac
Active Member
- Joined
- Sep 2, 2013
- Messages
- 39
- Reaction score
- 0
Hey all,
Last year I had a build thread for my Level 1 certification project, the Derecho. Scratchbuilt, 3" diameter, about 54" tall...
Well, to make a long story short, I done goofed. Today at Chili Blaster 7, I screwed something up, and it came in ballistic from an estimated 2500 feet.
The result was my first ever "shovel recovery." The rocket was almost completely destroyed. Photos are available here. In summary:
The immediate cause of the accident was obvious from initial inspection of the wreckage: neither the apogee nor the main ejection charge (in a Cable Cutter) had fired. One severed charge well still had the dog barf and unburned e-match in it, although the black powder had spilled out on impact. Both e-matches were later successfully fired using a drill battery.
Upon reviewing the Raven manual, I believe the cause of the failure is user error: I forgot that the Raven uses low beeps to indicate insufficient voltage or no charges detected, and did not correctly interpret the beeping. I remember it beeping out a battery voltage of 4 volts on testing the day of the launch, and I think it beeped out 4 volts on the pad, which indicates that the secondary cause was incorrect wiring of the charges. The custom-made avionics bay had not been flight-tested before. During construction, I tested the resistance between the Raven terminals and the avbay terminals and found it to be low, but I may have missed a wire or it may have come loose.
I will be rebuilding this rocket, and further posts in this thread will discuss design changes.
At the moment, my main question is whether there is any chance of recovering the data from the Raven to confirm the cause of the failure. I do not yet know whether it will power on, but as mentioned the data port was torn off. I don't trust my soldering skills on something that small, but if I sent it to Adrian is there a possibility that he could repair it enough to retrieve the data?
Last year I had a build thread for my Level 1 certification project, the Derecho. Scratchbuilt, 3" diameter, about 54" tall...
Well, to make a long story short, I done goofed. Today at Chili Blaster 7, I screwed something up, and it came in ballistic from an estimated 2500 feet.
The result was my first ever "shovel recovery." The rocket was almost completely destroyed. Photos are available here. In summary:
- The nose cone embedded itself into the ground for its full 12" length, requiring a shovel to remove. The cardboard coupler tube I was using as a shoulder was pushed about 3" forward into the nose, along with the entire avionics bay and possibly part of the upper airframe. Interestingly, the polypropylene was bent and folded outwards, and had almost no cracking. I suspect that heating from the Pueblo sun got the plastic hot enough to soften it.
- The cardboard upper airframe section, predictably, disintegrated. A small piece remained attached to the nose; the rest stayed with the Blue Tube coupler. The tube was attached to the coupler by three plastic removable rivets. These did not shear, but the holes were so deformed that the airframe slid backwards on the coupler, smushing its end against the lower airframe.
- The lower airframe also came apart where it wasn't held together by the coupler or centering rings. It crumpled right down to the forward ring, making repair by cutting away damaged tube impossible.
- The fincan itself was mostly intact, apart from one fine, which was severely cracked. The other two fins were completely undamaged, so this was likely due to the rocket bending and allowing the fincan to slam into the ground at high speed, landing on the fin that broke.
- The avionics bay built into the nose cone did not react well to being rammed into said nose cone. Basically every single piece broke, and it was so well embedded that I had to cut the nose cone apart using a bandsaw to look inside. Basically, the tracker bay got smashed into the end of the nose, and was crumpled at the other end, the weld nuts popped free of their mounting ring, pushing the allthread rods backward, the altimeter holder tubes crumpled, the bulkheads were shattered, the charge wells popped off, etc.
- When I saw the state of the nose cone, I though the Raven 3 altimeter would be in tiny pieces. As it turned out, it was mostly together. The terminal block on the end bent, the capacitor was bent in the direction of impact, and the micro USB data port was forcibly removed (possibly due to being hit by the capacitor). A trace on that side of the board was also peeled up; it looks like it used to be attached to the data port.
The immediate cause of the accident was obvious from initial inspection of the wreckage: neither the apogee nor the main ejection charge (in a Cable Cutter) had fired. One severed charge well still had the dog barf and unburned e-match in it, although the black powder had spilled out on impact. Both e-matches were later successfully fired using a drill battery.
Upon reviewing the Raven manual, I believe the cause of the failure is user error: I forgot that the Raven uses low beeps to indicate insufficient voltage or no charges detected, and did not correctly interpret the beeping. I remember it beeping out a battery voltage of 4 volts on testing the day of the launch, and I think it beeped out 4 volts on the pad, which indicates that the secondary cause was incorrect wiring of the charges. The custom-made avionics bay had not been flight-tested before. During construction, I tested the resistance between the Raven terminals and the avbay terminals and found it to be low, but I may have missed a wire or it may have come loose.
I will be rebuilding this rocket, and further posts in this thread will discuss design changes.
At the moment, my main question is whether there is any chance of recovering the data from the Raven to confirm the cause of the failure. I do not yet know whether it will power on, but as mentioned the data port was torn off. I don't trust my soldering skills on something that small, but if I sent it to Adrian is there a possibility that he could repair it enough to retrieve the data?