Eureka-1: A Collegiate Liquid Bipropellant Flight Worth Studying

Oct 31, 2026 Last reply: 15 hours ago 3 Replies
Jump to replies (3)

Here is the detail that got me: the drogue came out while the engine was still burning. That is not how recovery normally goes, and seeing deployment hardware fire mid-burn on a first liquid flight is something I have never come across before.



The vehicle is Eureka-1, a liquid bipropellant rocket, and it counts as the first of that kind flown by a UC Berkeley team. Everything major was developed under the team's own roof: propulsion, avionics, simulation software and the aerostructure, each designed and validated in-house. Three years of work went into it. One interesting mix: alongside all that custom engineering sits a commercial Eggtimer Protons handling deployment.



The lead-up reads like a proper operation. The rocket was static-fired while secured upright to the launch tower out in a desert. On flight day, operators in a mobile control station watched system status gauges on computer displays, ran radio checks confirming RQD release, igniter arming and igniter continuity, then called a five-second countdown to ignition. Ground support covered gas cylinders, a cryogenic dewar, fluid lines and valves, and the fuselage with its orange nose cone and EUREKA lettering rose off a lattice rail tower set on a utility trailer. An onboard camera looked straight down the body during the climb.



The flight reached roughly 3,300 meters, about 11,000 feet, and that kind of result places the team among a select few collegiate groups to pull it off. The open question is the drogue: a barometric altitude spike may have triggered it early, and the cause is still being investigated. The vehicle was not recovered successfully. Next semester brings a fresh system to design and validate, with cryogenic flows, static fires and launches on the list.



Project by Space Enterprise at Berkeley. Watch it on their YouTube channel:

formatting link


The choice that stands out to me is running a commercial Eggtimer Protons for deployment next to fully in-house propulsion and avionics. Recovery electronics are mature, off-the-shelf gear, so building those from scratch would add risk without much payoff. The early drogue does raise questions about how much visibility the team had into that unit's logic. Even so, I think spending limited development hours on the liquid engine side was the right call.

Does anyone know whether the investigation into the early drogue deployment is focused on the barometric altitude spike itself, or on how the deployment computer interpreted it? Pinning that down seems like the key step before the next recovery design gets locked in.

For the next system, I would suggest adding an independent backup path for drogue deployment, one that requires agreement between separate altitude readings before firing. If a single barometric spike can trigger the charge early, a redundant check would guard against a repeat. Since a new system is being designed and validated next semester anyway, now is the time to build that safeguard in.

Join the Discussion

Have something to add? Share your thoughts — no account required.

Didn't find your answer?

Ask the community — no account required