BPP Wiki - User contributions [en]

NS-122

2023-10-17T17:30:48Z

Kruti:

== '''NS-122 Eclipse Launch Summary''' ==

[[File:annular_eclipse.jpg|450px|Image:1400 pixels]]
[[File:Solar_eclipse.jpg|530px|Image:1400 pixels]]

The UMD Nearspace Team successfully launched two balloons during the annular solar eclipse on Saturday, 14 October 2023. The winds were not as bad as predicted, so we managed to inflate both balloons inside an open wind-break constructed in the driveway of our Airbnb. The first balloon was released right after the beginning of our launch window around 10:35 AM and then the second balloon almost immediately afterwards at 10:45 AM.

The first balloon to be released was the Eclipse Balloon carrying the UMD Vent System (to achieve float), an Iridium unit & Occams board (for tracking), Pterodactyl (sensor suite for atmospheric science data), an Insta360 panoramic camera, and the Streaming Video system. The balloon ascended through 60,000 ft and the vent was commanded to open, but unfortunately when the vent was subsequently commanded to close, there was latency in the system resulting in too much helium being vented. Fortunately, even though the balloon was descending, it was still in the air during maximum occultation so there's hope that we may have gotten some good video. The Pterodactyl payload and tracking system both worked well on this flight string which landed in a deer lease hunting area. A couple of hunters saw the payload string and brought it out and back to their home before calling us - needless to say we were tracking it the whole way and were very appreciative when they gave it back!

The second balloon was the UMD balloon carrying a number of unique payloads: GHOUL (UMD vent system), Command (tracking and data module), RFD900 (an eclipse payload downlinking telemetry in flight), more cameras (another Insta 360 and panoramic camera), and MCAT (Methane sensing payload). This balloon was supposed to ascend to about 78,000 ft, and then achieve float, but, again most likely because of a lag time between sending a command and receiving it, the vent did not open and the balloon did not float but instead continued ascending to burst at about 92,000 ft. After burst, the balloon, the neck insert, and a tether line that had gotten stuck, all managed to wrap around the parachute, resulting in a fast descent and a hard landing that destroyed a number of payloads. The landing was just on the inside of a cattle ranch, so the game warden was called and the property owner contacted, and both ended up being helpful in recovering our payloads.

Even though we have not fully assessed the status of the payloads or the quality of data obtained during this eclipse, the team is proud to have launched two balloons in quick succession, tracked them to landing and beyond, and recovered both payload strings. The launch operation went smoothly, both balloons were released during the launch window, and overall the team worked well together, the recovery was very lucky, and we definitely learned a lot! All of the lessons learned will be acted upon for the next eclipse in approximately 6 months – the total eclipse on Monday, 8 April 2024.

[[File:Team_picture.jpg|1400px|Image:1400 pixels]]

=== Balloon Launch Details ===
When:
Saturday 14 October 2023
Eclipse Balloon Release 10:35 AM
UMD Balloon Release 10:45 AM

=== Launch Site: ===
520 Mountain Valley Road
(Our Airbnb Driveway!)
Concan, Texas 78838

=== Landing Sites: ===
Eclipse Payload String landed in a Deer Lease
UMD Payload String landed on a Cattle Ranch
Both NorthWest of San Antonio

=== Future Updates ===
All of the data from this flight will be uploaded and accessible for anyone interested. Please contact Dr. Mary Bowden for more information if needed.

File:Annular eclipse.jpg

2023-10-17T17:26:40Z

Kruti:

Partial eclipse

File:Solar eclipse.jpg

2023-10-17T17:20:56Z

Kruti:

Ring of Fire Solar Eclipse

NS-122

2023-10-17T17:17:17Z

Kruti:

NS-122 Eclipse Launch Summary

[[File:Team_picture.jpg|400px|Image:400 pixels]]
The UMD Nearspace Team successfully launched two balloons during the annular solar eclipse on Saturday, 14 October 2023. The winds were not as bad as predicted, so we managed to inflate both balloons inside an open wind-break constructed in the driveway of our Airbnb. The first balloon was released right after the beginning of our launch window around 10:35 AM and then the second balloon almost immediately afterwards at 10:45 AM.

The first balloon to be released was the Eclipse Balloon carrying the UMD Vent System (to achieve float), an Iridium unit & Occams board (for tracking), Pterodactyl (sensor suite for atmospheric science data), an Insta360 panoramic camera, and the Streaming Video system. The balloon ascended through 60,000 ft and the vent was commanded to open, but unfortunately when the vent was subsequently commanded to close, there was latency in the system resulting in too much helium being vented. Fortunately, even though the balloon was descending, it was still in the air during maximum occultation so there's hope that we may have gotten some good video. The Pterodactyl payload and tracking system both worked well on this flight string which landed in a deer lease hunting area. A couple of hunters saw the payload string and brought it out and back to their home before calling us - needless to say we were tracking it the whole way and were very appreciative when they gave it back!

The second balloon was the UMD balloon carrying a number of unique payloads: GHOUL (UMD vent system), Command (tracking and data module), RFD900 (an eclipse payload downlinking telemetry in flight), more cameras (another Insta 360 and panoramic camera), and MCAT (Methane sensing payload). This balloon was supposed to ascend to about 78,000 ft, and then achieve float, but, again most likely because of a lag time between sending a command and receiving it, the vent did not open and the balloon did not float but instead continued ascending to burst at about 92,000 ft. After burst, the balloon, the neck insert, and a tether line that had gotten stuck, all managed to wrap around the parachute, resulting in a fast descent and a hard landing that destroyed a number of payloads. The landing was just on the inside of a cattle ranch, so the game warden was called and the property owner contacted, and both ended up being helpful in recovering our payloads.

Even though we have not fully assessed the status of the payloads or the quality of data obtained during this eclipse, the team is proud to have launched two balloons in quick succession, tracked them to landing and beyond, and recovered both payload strings. The launch operation went smoothly, both balloons were released during the launch window, and overall the team worked well together, the recovery was very lucky, and we definitely learned a lot! All of the lessons learned will be acted upon for the next eclipse in approximately 6 months – the total eclipse on Monday, 8 April 2024.

Balloon Launch Details
When:
Saturday 14 October 2023
Eclipse Balloon Release 10:35 AM
UMD Balloon Release 10:45 AM

Launch Site:
520 Mountain Valley Road
(Our Airbnb Driveway!)
Concan, Texas 78838

Landing Sites:
Eclipse Payload String landed in a Deer Lease
UMD Payload String landed on a Cattle Ranch
Both NorthWest of San Antonio

Future Updates
All of the data from this flight will be uploaded and accessible for anyone interested. Please contact Dr. Mary Bowden for more information if needed.

Our video live stream should still be on YouTube at the following link:
UMD Live Stream Link
Our channel name is UMD Nearspace.

NS-122

2023-10-17T17:16:54Z

Kruti:

NS-122 Eclipse Launch Summary

[[File:Team_picture.jpg|200px|Image: 200 pixels]]
The UMD Nearspace Team successfully launched two balloons during the annular solar eclipse on Saturday, 14 October 2023. The winds were not as bad as predicted, so we managed to inflate both balloons inside an open wind-break constructed in the driveway of our Airbnb. The first balloon was released right after the beginning of our launch window around 10:35 AM and then the second balloon almost immediately afterwards at 10:45 AM.

The first balloon to be released was the Eclipse Balloon carrying the UMD Vent System (to achieve float), an Iridium unit & Occams board (for tracking), Pterodactyl (sensor suite for atmospheric science data), an Insta360 panoramic camera, and the Streaming Video system. The balloon ascended through 60,000 ft and the vent was commanded to open, but unfortunately when the vent was subsequently commanded to close, there was latency in the system resulting in too much helium being vented. Fortunately, even though the balloon was descending, it was still in the air during maximum occultation so there's hope that we may have gotten some good video. The Pterodactyl payload and tracking system both worked well on this flight string which landed in a deer lease hunting area. A couple of hunters saw the payload string and brought it out and back to their home before calling us - needless to say we were tracking it the whole way and were very appreciative when they gave it back!

The second balloon was the UMD balloon carrying a number of unique payloads: GHOUL (UMD vent system), Command (tracking and data module), RFD900 (an eclipse payload downlinking telemetry in flight), more cameras (another Insta 360 and panoramic camera), and MCAT (Methane sensing payload). This balloon was supposed to ascend to about 78,000 ft, and then achieve float, but, again most likely because of a lag time between sending a command and receiving it, the vent did not open and the balloon did not float but instead continued ascending to burst at about 92,000 ft. After burst, the balloon, the neck insert, and a tether line that had gotten stuck, all managed to wrap around the parachute, resulting in a fast descent and a hard landing that destroyed a number of payloads. The landing was just on the inside of a cattle ranch, so the game warden was called and the property owner contacted, and both ended up being helpful in recovering our payloads.

Even though we have not fully assessed the status of the payloads or the quality of data obtained during this eclipse, the team is proud to have launched two balloons in quick succession, tracked them to landing and beyond, and recovered both payload strings. The launch operation went smoothly, both balloons were released during the launch window, and overall the team worked well together, the recovery was very lucky, and we definitely learned a lot! All of the lessons learned will be acted upon for the next eclipse in approximately 6 months – the total eclipse on Monday, 8 April 2024.

Balloon Launch Details
When:
Saturday 14 October 2023
Eclipse Balloon Release 10:35 AM
UMD Balloon Release 10:45 AM

Launch Site:
520 Mountain Valley Road
(Our Airbnb Driveway!)
Concan, Texas 78838

Landing Sites:
Eclipse Payload String landed in a Deer Lease
UMD Payload String landed on a Cattle Ranch
Both NorthWest of San Antonio

Future Updates
All of the data from this flight will be uploaded and accessible for anyone interested. Please contact Dr. Mary Bowden for more information if needed.

Our video live stream should still be on YouTube at the following link:
UMD Live Stream Link
Our channel name is UMD Nearspace.

NS-122

2023-10-17T17:15:34Z

Kruti:

NS-122 Eclipse Launch Summary

<gallery>
Team_picture.jpg|300px|NS-122 Team Picture
</gallery>
The UMD Nearspace Team successfully launched two balloons during the annular solar eclipse on Saturday, 14 October 2023. The winds were not as bad as predicted, so we managed to inflate both balloons inside an open wind-break constructed in the driveway of our Airbnb. The first balloon was released right after the beginning of our launch window around 10:35 AM and then the second balloon almost immediately afterwards at 10:45 AM.

The first balloon to be released was the Eclipse Balloon carrying the UMD Vent System (to achieve float), an Iridium unit & Occams board (for tracking), Pterodactyl (sensor suite for atmospheric science data), an Insta360 panoramic camera, and the Streaming Video system. The balloon ascended through 60,000 ft and the vent was commanded to open, but unfortunately when the vent was subsequently commanded to close, there was latency in the system resulting in too much helium being vented. Fortunately, even though the balloon was descending, it was still in the air during maximum occultation so there's hope that we may have gotten some good video. The Pterodactyl payload and tracking system both worked well on this flight string which landed in a deer lease hunting area. A couple of hunters saw the payload string and brought it out and back to their home before calling us - needless to say we were tracking it the whole way and were very appreciative when they gave it back!

The second balloon was the UMD balloon carrying a number of unique payloads: GHOUL (UMD vent system), Command (tracking and data module), RFD900 (an eclipse payload downlinking telemetry in flight), more cameras (another Insta 360 and panoramic camera), and MCAT (Methane sensing payload). This balloon was supposed to ascend to about 78,000 ft, and then achieve float, but, again most likely because of a lag time between sending a command and receiving it, the vent did not open and the balloon did not float but instead continued ascending to burst at about 92,000 ft. After burst, the balloon, the neck insert, and a tether line that had gotten stuck, all managed to wrap around the parachute, resulting in a fast descent and a hard landing that destroyed a number of payloads. The landing was just on the inside of a cattle ranch, so the game warden was called and the property owner contacted, and both ended up being helpful in recovering our payloads.

Even though we have not fully assessed the status of the payloads or the quality of data obtained during this eclipse, the team is proud to have launched two balloons in quick succession, tracked them to landing and beyond, and recovered both payload strings. The launch operation went smoothly, both balloons were released during the launch window, and overall the team worked well together, the recovery was very lucky, and we definitely learned a lot! All of the lessons learned will be acted upon for the next eclipse in approximately 6 months – the total eclipse on Monday, 8 April 2024.

Balloon Launch Details
When:
Saturday 14 October 2023
Eclipse Balloon Release 10:35 AM
UMD Balloon Release 10:45 AM

Launch Site:
520 Mountain Valley Road
(Our Airbnb Driveway!)
Concan, Texas 78838

Landing Sites:
Eclipse Payload String landed in a Deer Lease
UMD Payload String landed on a Cattle Ranch
Both NorthWest of San Antonio

Future Updates
All of the data from this flight will be uploaded and accessible for anyone interested. Please contact Dr. Mary Bowden for more information if needed.

Our video live stream should still be on YouTube at the following link:
UMD Live Stream Link
Our channel name is UMD Nearspace.

File:Team picture.jpg

2023-10-17T17:09:10Z

Kruti:

This is our team for NS-122 who undertook the expedition to launch weather balloons during October 2023 Annular Eclipse

GHOUL

2023-06-26T17:13:28Z

Kruti:

GHOUL - Generalized Helium Outgassing Unit for Latex balloons

When Dr Mary Bowden and JJ Kuznetsov, a junior pursuing aerospace engineering and math at University of Maryland, attended workshop hosted by Montana Space Grant Consortium for NEBP (NASA's eclipse ballooning project), they found out that one of the main flight systems still in development was the venting system. While UMD NearSpace Balloon Payload Program has in past made several almost successful attempts building this system, JJ figured with the tribal knowledge and fresh skills and mindsets, BPP has potential to build our own venting system.
Helios, a venting system developed by program in past, had a rich history within the Nearspace balloon payload program as it was initially designed by two talented seniors, Cooper and Joseph Breeden. Their work had set the standard for innovation and pushed the boundaries of what was possible within the program.

JJ, an enthusiastic and creative individual has always dreamed of contributing something significant to the program. He has a natural talent for engineering and loved to design and build things. So, he came up with an idea to create a new venting system for the balloon payload to control its ascent and descent during flights. Excited about his concept, JJ shared his idea with his friends and fellow payload enthusiasts, Michael Kalin and Kruti Bhingradiya. Michael and Kruti were intrigued by JJ's proposal and immediately agreed to help him bring his vision to life. They formed a small team dedicated to creating new past payload design, while still keeping the name Helios.

However, as luck would have it, the initial design iteration of Helios leaked during its launchpad test, causing a setback for the team. Determined not to give up, JJ, Michael, and Kruti took this as an opportunity to learn from their mistakes and create an even better design iteration. They named their new creation "Ghoul." The journey to create the perfect payload design was not an easy one. Ghoul faced multiple challenges, including catastrophic launches and battery failures at high altitudes. However, JJ's unwavering dedication and his ability to inspire and lead the team kept their spirits high.

As time went on, two talented freshmen, Jack Bishop (JB) and Akemi, joined the Ghoul payload team. JB had an incredible knack for electronics and was passionate about designing circuits. Akemi, on the other hand, had a keen interest in temperature monitoring and control systems. Together, they formed an unstoppable force.While JB and Akemi worked on developing a temperature monitoring and control circuit for Ghoul, JJ's friend Daniel Grammer (DG) lent a helping hand to JJ with the venting flap opening mechanism. DG was a skilled technician and knew the ins and outs of mechanical engineering. With his expertise, he assisted JJ in refining the venting system to ensure it worked flawlessly.While JJ, DG, JB, and Akemi were focused on their respective areas of expertise, Michael Kalin worked diligently on the software side of things. His programming skills ensured that Ghoul's onboard systems could communicate and function seamlessly. Kruti, on the other hand, dedicated her efforts to perfecting the cutdown mechanisms, which allowed the payload to separate from the balloon and safely return to the ground after the mission.

As the team progressed, they faced numerous challenges and setbacks. But JJ's fearless leadership and the team's unwavering commitment pushed them forward. They learned from each failure and used those lessons to improve their design. During their journey, the team received guidance and support from a computer engineering major named Michael Shipman. Michael was well-versed in creating printed circuit boards and provided invaluable expertise to the team, ensuring their electronic systems were optimized for performance.

Finally, after many iterations, late nights, and a lot of hard work, the team succeeded in creating a payload that had both a reliable venting system and a robust cutdown mechanism. With their newly improved Ghoul payload, the team embarked on a series of launches. The first few attempts ended in disappointment, but with each failure, they learned important lessons and made necessary adjustments. Finally, on the third launch, Ghoul soared into the sky, collecting valuable data and achieving its mission objectives. It was a moment of triumph for JJ and his team.

As the team prepared for future flights, they look back at their journey with gratitude. They know that their accomplishments are the result of a collective effort and the unwavering belief in their vision. With each launch, they are growing stronger, more skilled, and more passionate about engineering designs and nearspace exploration.

GHOUL

2023-06-26T17:12:23Z

Kruti: Created page with "GHOUL - Generalized Helium Outgassing Unit for Latex balloons When Dr Mary Bowden and JJ Kuznetsov, a junior pursuing aerospace engineering and math at University of Maryland, attended workshop hosted by Montana Space Grant Consortium for NEBP (NASA's eclipse ballooning project), they found out that one of the main flight systems still in development was the venting system. While UMD NearSpace Balloon Payload Program has in past made several almost successful attempts..."

GHOUL - Generalized Helium Outgassing Unit for Latex balloons

When Dr Mary Bowden and JJ Kuznetsov, a junior pursuing aerospace engineering and math at University of Maryland, attended workshop hosted by Montana Space Grant Consortium for NEBP (NASA's eclipse ballooning project), they found out that one of the main flight systems still in development was the venting system. While UMD NearSpace Balloon Payload Program has in past made several almost successful attempts building this system, JJ figured with the tribal knowledge and fresh skills and mindsets, BPP has potential to build our own venting system.
Helios, a venting system developed by program in past, had a rich history within the Nearspace balloon payload program as it was initially designed by two talented seniors, Cooper and Joseph Breeden. Their work had set the standard for innovation and pushed the boundaries of what was possible within the program.

JJ, an enthusiastic and creative individual has always dreamed of contributing something significant to the program. He has a natural talent for engineering and loved to design and build things. So, he came up with an idea to create a new venting system for the balloon payload to control its ascent and descent during flights. Excited about his concept, JJ shared his idea with his friends and fellow payload enthusiasts, Michael Kalin and Kruti Bhingradiya. Michael and Kruti were intrigued by JJ's proposal and immediately agreed to help him bring his vision to life. They formed a small team dedicated to creating new past payload design, while still keeping the name Helios.

However, as luck would have it, the initial design iteration of Helios leaked during its launchpad test, causing a setback for the team. Determined not to give up, JJ, Michael, and Kruti took this as an opportunity to learn from their mistakes and create an even better design iteration. They named their new creation "Ghoul."

The journey to create the perfect payload design was not an easy one. Ghoul faced multiple challenges, including catastrophic launches and battery failures at high altitudes. However, JJ's unwavering dedication and his ability to inspire and lead the team kept their spirits high.

As time went on, two talented freshmen, Jack Bishop (JB) and Akemi, joined the Ghoul payload team. JB had an incredible knack for electronics and was passionate about designing circuits. Akemi, on the other hand, had a keen interest in temperature monitoring and control systems. Together, they formed an unstoppable force.

While JB and Akemi worked on developing a temperature monitoring and control circuit for Ghoul, JJ's friend Daniel Grammer (DG) lent a helping hand to JJ with the venting flap opening mechanism. DG was a skilled technician and knew the ins and outs of mechanical engineering. With his expertise, he assisted JJ in refining the venting system to ensure it worked flawlessly.

While JJ, DG, JB, and Akemi were focused on their respective areas of expertise, Michael Kalin worked diligently on the software side of things. His programming skills ensured that Ghoul's onboard systems could communicate and function seamlessly. Kruti, on the other hand, dedicated her efforts to perfecting the cutdown mechanisms, which allowed the payload to separate from the balloon and safely return to the ground after the mission.

As the team progressed, they faced numerous challenges and setbacks. But JJ's fearless leadership and the team's unwavering commitment pushed them forward. They learned from each failure and used those lessons to improve their design.

During their journey, the team received guidance and support from a computer engineering major named Michael Shipman. Michael was well-versed in creating printed circuit boards and provided invaluable expertise to the team, ensuring their electronic systems were optimized for performance.

Finally, after many iterations, late nights, and a lot of hard work, the team succeeded in creating a payload that had both a reliable venting system and a robust cutdown mechanism. With their newly improved Ghoul payload, the team embarked on a series of launches. The first few attempts ended in disappointment, but with each failure, they learned important lessons and made necessary adjustments. Finally, on the third launch, Ghoul soared into the sky, collecting valuable data and achieving its mission objectives. It was a moment of triumph for JJ and his team.

As the team prepared for future flights, they look back at their journey with gratitude. They know that their accomplishments are the result of a collective effort and the unwavering belief in their vision. With each launch, they are growing stronger, more skilled, and more passionate about engineering designs and nearspace exploration.

Payloads / Projects

2023-04-04T18:57:57Z

Kruti: /* Reoccurring Program Payloads */

WIP Payloads and Projects. Tricky to organize because most things will fall into multiple categories. Would also be ideal to indicate active vs. past payloads and some way to show # of flights.

== Payloads and Projects ==
{| class="wikitable"
|-
! Payload !! Description !! Status
|-
| [[GHOUL]] (Gross Horrible Outrageous Ugly Leaking Payload) || Helium venter for floating || '''ACTIVE'''
|-
| [[TUFF]] (Tension Under Flight Forces payload) || Drag and wind oscillation measurement || '''ACTIVE'''
|-
| [[SLAPS]] (Solar Launched Automatic Power System) || Solar power collection for extended flights || '''ACTIVE'''
|}

== RF and Tracking Payloads ==
{| class="wikitable"
|-
! Payload !! Description !! Status
|-
| [[Command]] || Primary tracking payload || '''ACTIVE'''
|-
| [[LIVE]] || Live streaming || '''ACTIVE'''
|-
| [[LINK]] || ||
|-
| [[BEEP]] || Image downlink || '''INACTIVE'''
|}

== Weather Monitoring ==
{| class="wikitable"
|-
! Payload !! Description !! Status
|-
| [[Tyrion]] || || '''INACTIVE'''
|-
| [[Dany]] || || '''INACTIVE'''
|-
| [[Bach's Box]] || || '''INACTIVE'''
|}

== Flight Extension and Termination ==
{| class="wikitable"
|-
! Payload !! Description !! Status
|-
| [[Choppy]] || Cutdown payload || '''ACTIVE'''
|-
| [[HELIOS]] || Helium venter || '''INACTIVE'''
|-
| [[CHARM]] || Cutdown payload || '''INACTIVE'''
|}

== Reoccurring Program Payloads ==
{| class="wikitable"
|-
! Payload !! Description !! Status
|-
| [[Panoramic]] || 360° Camera payload || '''ACTIVE'''
|-
| [[Turtle Nest]] || Payload for flying souvenirs || '''ACTIVE'''
|-
| [[Frankenstein/Medusa]] ||360° Camera payload on selfie stick || '''ACTIVE'''
|}

== Ground Systems ==
{| class="wikitable"
|-
! Payload !! Description !! Status
|-
| [[ATLAS RES]] || || '''ACTIVE'''
|}
== Outreach Projects ==
{| class="wikitable"
|-
! Payload !! Description !! Status
|-
| [[BPP Stem Workshop 2023]] || || '''ACTIVE'''
|}

Payloads / Projects

2023-04-04T18:56:55Z

Kruti: /* RF and Tracking Payloads */

WIP Payloads and Projects. Tricky to organize because most things will fall into multiple categories. Would also be ideal to indicate active vs. past payloads and some way to show # of flights.

== Payloads and Projects ==
{| class="wikitable"
|-
! Payload !! Description !! Status
|-
| [[GHOUL]] (Gross Horrible Outrageous Ugly Leaking Payload) || Helium venter for floating || '''ACTIVE'''
|-
| [[TUFF]] (Tension Under Flight Forces payload) || Drag and wind oscillation measurement || '''ACTIVE'''
|-
| [[SLAPS]] (Solar Launched Automatic Power System) || Solar power collection for extended flights || '''ACTIVE'''
|}

== RF and Tracking Payloads ==
{| class="wikitable"
|-
! Payload !! Description !! Status
|-
| [[Command]] || Primary tracking payload || '''ACTIVE'''
|-
| [[LIVE]] || Live streaming || '''ACTIVE'''
|-
| [[LINK]] || ||
|-
| [[BEEP]] || Image downlink || '''INACTIVE'''
|}

== Weather Monitoring ==
{| class="wikitable"
|-
! Payload !! Description !! Status
|-
| [[Tyrion]] || || '''INACTIVE'''
|-
| [[Dany]] || || '''INACTIVE'''
|-
| [[Bach's Box]] || || '''INACTIVE'''
|}

== Flight Extension and Termination ==
{| class="wikitable"
|-
! Payload !! Description !! Status
|-
| [[Choppy]] || Cutdown payload || '''ACTIVE'''
|-
| [[HELIOS]] || Helium venter || '''INACTIVE'''
|-
| [[CHARM]] || Cutdown payload || '''INACTIVE'''
|}

== Reoccurring Program Payloads ==
{| class="wikitable"
|-
! Payload !! Description !! Status
|-
| [[Panoramic]] || 360° Camera payload || '''ACTIVE'''
|-
| [[Turtle Nest]] || Payload for flying souvenirs || '''ACTIVE'''
|}

== Ground Systems ==
{| class="wikitable"
|-
! Payload !! Description !! Status
|-
| [[ATLAS RES]] || || '''ACTIVE'''
|}
== Outreach Projects ==
{| class="wikitable"
|-
! Payload !! Description !! Status
|-
| [[BPP Stem Workshop 2023]] || || '''ACTIVE'''
|}

Payloads / Projects

2023-04-04T18:56:25Z

Kruti: /* RF and Tracking Payloads */

WIP Payloads and Projects. Tricky to organize because most things will fall into multiple categories. Would also be ideal to indicate active vs. past payloads and some way to show # of flights.

== Payloads and Projects ==
{| class="wikitable"
|-
! Payload !! Description !! Status
|-
| [[GHOUL]] (Gross Horrible Outrageous Ugly Leaking Payload) || Helium venter for floating || '''ACTIVE'''
|-
| [[TUFF]] (Tension Under Flight Forces payload) || Drag and wind oscillation measurement || '''ACTIVE'''
|-
| [[SLAPS]] (Solar Launched Automatic Power System) || Solar power collection for extended flights || '''ACTIVE'''
|}

== RF and Tracking Payloads ==
{| class="wikitable"
|-
! Payload !! Description !! Status
|-
| [[Command]] || Primary tracking payload || '''ACTIVE'''
|-
| [[LIVE]] || Live streaming || '''ACTIVE'''
|-
| [[LINK]] || ||
|-
| [[BEEP]] || || '''INACTIVE'''
|}

== Weather Monitoring ==
{| class="wikitable"
|-
! Payload !! Description !! Status
|-
| [[Tyrion]] || || '''INACTIVE'''
|-
| [[Dany]] || || '''INACTIVE'''
|-
| [[Bach's Box]] || || '''INACTIVE'''
|}

== Flight Extension and Termination ==
{| class="wikitable"
|-
! Payload !! Description !! Status
|-
| [[Choppy]] || Cutdown payload || '''ACTIVE'''
|-
| [[HELIOS]] || Helium venter || '''INACTIVE'''
|-
| [[CHARM]] || Cutdown payload || '''INACTIVE'''
|}

== Reoccurring Program Payloads ==
{| class="wikitable"
|-
! Payload !! Description !! Status
|-
| [[Panoramic]] || 360° Camera payload || '''ACTIVE'''
|-
| [[Turtle Nest]] || Payload for flying souvenirs || '''ACTIVE'''
|}

== Ground Systems ==
{| class="wikitable"
|-
! Payload !! Description !! Status
|-
| [[ATLAS RES]] || || '''ACTIVE'''
|}
== Outreach Projects ==
{| class="wikitable"
|-
! Payload !! Description !! Status
|-
| [[BPP Stem Workshop 2023]] || || '''ACTIVE'''
|}

Payloads / Projects

2023-04-04T18:56:11Z

Kruti: /* RF and Tracking Payloads */

WIP Payloads and Projects. Tricky to organize because most things will fall into multiple categories. Would also be ideal to indicate active vs. past payloads and some way to show # of flights.

== Payloads and Projects ==
{| class="wikitable"
|-
! Payload !! Description !! Status
|-
| [[GHOUL]] (Gross Horrible Outrageous Ugly Leaking Payload) || Helium venter for floating || '''ACTIVE'''
|-
| [[TUFF]] (Tension Under Flight Forces payload) || Drag and wind oscillation measurement || '''ACTIVE'''
|-
| [[SLAPS]] (Solar Launched Automatic Power System) || Solar power collection for extended flights || '''ACTIVE'''
|}

== RF and Tracking Payloads ==
{| class="wikitable"
|-
! Payload !! Description !! Status
|-
| [[Command]] || Primary tracking payload || '''ACTIVE'''
|-
| [[LIVE]] || Live streaming || '''ACTIVE'''
|-
| [[LINK]] || ||
|-
| [[BEEP]] || || || '''INACTIVE'''
|}

== Weather Monitoring ==
{| class="wikitable"
|-
! Payload !! Description !! Status
|-
| [[Tyrion]] || || '''INACTIVE'''
|-
| [[Dany]] || || '''INACTIVE'''
|-
| [[Bach's Box]] || || '''INACTIVE'''
|}

== Flight Extension and Termination ==
{| class="wikitable"
|-
! Payload !! Description !! Status
|-
| [[Choppy]] || Cutdown payload || '''ACTIVE'''
|-
| [[HELIOS]] || Helium venter || '''INACTIVE'''
|-
| [[CHARM]] || Cutdown payload || '''INACTIVE'''
|}

== Reoccurring Program Payloads ==
{| class="wikitable"
|-
! Payload !! Description !! Status
|-
| [[Panoramic]] || 360° Camera payload || '''ACTIVE'''
|-
| [[Turtle Nest]] || Payload for flying souvenirs || '''ACTIVE'''
|}

== Ground Systems ==
{| class="wikitable"
|-
! Payload !! Description !! Status
|-
| [[ATLAS RES]] || || '''ACTIVE'''
|}
== Outreach Projects ==
{| class="wikitable"
|-
! Payload !! Description !! Status
|-
| [[BPP Stem Workshop 2023]] || || '''ACTIVE'''
|}

Payloads / Projects

2023-04-04T18:55:28Z

Kruti: /* RF and Tracking Payloads */

WIP Payloads and Projects. Tricky to organize because most things will fall into multiple categories. Would also be ideal to indicate active vs. past payloads and some way to show # of flights.

== Payloads and Projects ==
{| class="wikitable"
|-
! Payload !! Description !! Status
|-
| [[GHOUL]] (Gross Horrible Outrageous Ugly Leaking Payload) || Helium venter for floating || '''ACTIVE'''
|-
| [[TUFF]] (Tension Under Flight Forces payload) || Drag and wind oscillation measurement || '''ACTIVE'''
|-
| [[SLAPS]] (Solar Launched Automatic Power System) || Solar power collection for extended flights || '''ACTIVE'''
|}

== RF and Tracking Payloads ==
{| class="wikitable"
|-
! Payload !! Description !! Status
|-
| [[Command]] || Primary tracking payload || '''ACTIVE'''
|-
| [[LIVE]] || Live streaming || '''ACTIVE'''
|-
| [[LINK]] || ||
|-
| [[BEEP]] || ||
|}

== Weather Monitoring ==
{| class="wikitable"
|-
! Payload !! Description !! Status
|-
| [[Tyrion]] || || '''INACTIVE'''
|-
| [[Dany]] || || '''INACTIVE'''
|-
| [[Bach's Box]] || || '''INACTIVE'''
|}

== Flight Extension and Termination ==
{| class="wikitable"
|-
! Payload !! Description !! Status
|-
| [[Choppy]] || Cutdown payload || '''ACTIVE'''
|-
| [[HELIOS]] || Helium venter || '''INACTIVE'''
|-
| [[CHARM]] || Cutdown payload || '''INACTIVE'''
|}

== Reoccurring Program Payloads ==
{| class="wikitable"
|-
! Payload !! Description !! Status
|-
| [[Panoramic]] || 360° Camera payload || '''ACTIVE'''
|-
| [[Turtle Nest]] || Payload for flying souvenirs || '''ACTIVE'''
|}

== Ground Systems ==
{| class="wikitable"
|-
! Payload !! Description !! Status
|-
| [[ATLAS RES]] || || '''ACTIVE'''
|}
== Outreach Projects ==
{| class="wikitable"
|-
! Payload !! Description !! Status
|-
| [[BPP Stem Workshop 2023]] || || '''ACTIVE'''
|}

History

2023-04-04T18:54:21Z

Kruti:

In 2003, our dearest Dr Bowden went to a workshop teaching how to launch high altitude weather balloons as a representative of Maryland Space Grant Consortium(MDGSC). Little did she know that it would result in this wonderful program hosting more than hundred launches of high altitude weather balloons and payloads and a place for engineers to do hands on work outside academic curriculum and build near space systems and test them in real flights.

History

2023-04-04T18:53:55Z

Kruti: Created page with "In 2003, our dearest Dr Bowden was sent to workshop teaching how to launch high altitude weather balloons as a representative of Maryland Space Grant Consortium(MDGSC). Little did she know that it would result in this wonderful program hosting more than hundred launches of high altitude weather balloons and payloads and a place for engineers to do hands on work outside academic curriculum and build near space systems and test them in real flights."

In 2003, our dearest Dr Bowden was sent to workshop teaching how to launch high altitude weather balloons as a representative of Maryland Space Grant Consortium(MDGSC). Little did she know that it would result in this wonderful program hosting more than hundred launches of high altitude weather balloons and payloads and a place for engineers to do hands on work outside academic curriculum and build near space systems and test them in real flights.

BPP Wiki:About

2023-04-04T18:47:11Z

Kruti: Created page with "The aim of BPP Wiki is to document all the information gathered over years whether it be failed tests of payloads or failed launches or successful launches. The idea is that future generation of BPP will be able to use this as resource and instead of thinking about issues in their systems for very long and failing to analyze what went wrong, they will learn from the experiences of their ancestors."

The aim of BPP Wiki is to document all the information gathered over years whether it be failed tests of payloads or failed launches or successful launches. The idea is that future generation of BPP will be able to use this as resource and instead of thinking about issues in their systems for very long and failing to analyze what went wrong, they will learn from the experiences of their ancestors.