Result: Flight Recovered!! Partial success.
OLHZN-4 was the fourth high altitude weather balloon flight for Overlook Horizon High Altitude Balloons. This flight featured our first onboard astronaut in front of one of the flight cameras. We named our astronaut and this flight “Butchy” in honor of our friend, Oliver “Butch” Mousseau who tragically passed away earlier this spring after a head injury he sustained while officiating.
This flight was launched on August 20, 2016 at 6:00pm EDT (22:00 UTC). The goal of this flight was to ensure full radio tracking capabilities for the entire flight. Unfortunately, similar to OLHZN-3, we received no radio tracking once the balloon was launched. For this flight, we simplified some of the software code and added some safeguards to try to eliminate possible erroneous calculations. We were also able to identify that some of the Arduino Mega boards we purchased were actually counterfeit boards and not genuine Arduino boards which we were unaware of. The counterfeit boards were replaced with a genuine Arduino Mega to ensure quality results. We tested the boards extensively and could not replicate the issue on the ground prior to the flight, but we still had no radio tracking throughout the flight. Additionally, our backup tracking device did operate once landing, however, it did not have a strong enough GPS signal to report an accurate position. The backup tracker was indicating its position with a degree of accuracy of +/- 50 miles which left a huge zone of uncertainty. The backup tracker was actively reporting its position for hours after landing, just not accurately enough for us to locate it. We were able to establish two-way communication with the backup tracker around 11:30pm EDT and instructed the backup tracker to go into a power-save mode to try to prolong the battery life of the tracker which would hopefully result in a different result for location accuracy at some point.
After breaking for the night, we woke up on Sunday morning to find that the backup tracker was reporting an accurate position with an accuracy of +/- 2 feet! We arrived at the landing site around 8:00am EDT (12:00 UTC) and recovered the payload. One camera had the entire flight saved as it, fortunately, ran out of battery around 4:00am EDT. The second camera’s battery lasted longer (until about 6:00am EDT) and eventually filled the entire camera storage card. The camera mode we (intentionally) use causes the camera to start overwriting older videos once this occurs so the beginning of the flight was lost on this camera. We were able to recover the last 55 minutes (38%) of the flight, though. The main tracking unit’s data was not saved, sadly. It appears that the tracking unit power cycled a few times during flight and ultimately did not record much data. We’re going to review to determine more about this soon to try to correct these issues for the next flight.
UPDATE: We were able to replicate some issues on the ground post-fight with the cameras interfering with the GPS signal when they are in close proximity to the tracking unit. We’ve now identified that electromagnetic interference from the flight cameras was indeed the cause of the issue.
Unfortunately, we do not have any flight data for the flight path as our flight tracker failed entirely for this flight. We do, however, have the launch and landing coordinates which revealed a distance of 18.22 miles from launch to landing.
- Launch Date: August 20, 2016 at 5:59pm EDT (21:59 UTC)
- Launch Location: 42.907188, -77.273521
- Estimated Ascent Rate: 4.45 m/s
- Estimated Burst Altitude: 95,100 ft.
- Time to Burst: 100.5 minutes
- Estimated Helium Volume: 104.94 cu ft.
- Payload Mass: 1546g (3.41 lbs)
- Neck Positive Lift: 773g
- Estimated Landing Speed: 7 m/s
- Descent Time: 33 minutes
- Landing Site: 42.9858, -76.9294