The goal
Take a rocket from a simulated design to a recoverable flight, then add onboard instrumentation to understand how the real flight compares with the model. This is a personal learning project combining aerodynamics, hands-on construction, embedded programming, and data analysis.
Current focus
The OpenRocket design is complete. I am now selecting the internal components, modeling parts in Fusion 360 to 3D print on my Bambu Lab P1S, and ordering hardware. Airframe construction and a first flight without electronics come next; sensor testing, logging firmware, and the avionics sled follow, with the instrumented flight kept as a separate milestone so the airframe and recovery can be evaluated first.
Next milestone
The first launch is targeted for mid-November 2026, followed by an instrumented flight in January 2027. Both are planning targets, dependent on build readiness, club launch availability, and conditions. Flight results and measured performance will be added after testing.
Design and simulation
The design phase uses OpenRocket to model the airframe, motor mount, and fins, then compare candidate motors and their predicted flight profiles. The plan tracks apogee, velocity leaving the launch guide, center of gravity, and center of pressure. After construction, measured mass and balance will replace estimates in the model before the flight configuration is selected.
Airframe and recovery
The build sequence covers dry-fitting parts, aligning and attaching fins, adding epoxy fillets, and installing the launch-guide hardware and recovery attachment. A parachute and shock cord provide recovery. The first flight is planned without onboard electronics; the later logging flight retains motor-ejection recovery rather than assigning deployment control to the new flight computer.
Planned avionics
The electronics plan considers a Teensy 4.1 or Feather Adalogger, a BMP390-class barometer, an inertial sensor, and microSD storage. Pressure-derived altitude, acceleration, and rotation will be logged for later analysis. Board and sensor choices remain provisional. Bench tests will check sensor readings, battery runtime, and whether logging continues reliably before integration.
Firmware and bench testing
The planned firmware records sensor data and identifies flight phases: pad idle, boost, coast, apogee, descent, and landing. The logging plan targets 25–50 samples per second and includes checks for dropped samples. Stairwell altitude tests and replay of recorded data will help evaluate filtering and event detection before a flight. An arming switch and buzzer are planned for clear operating feedback.
Flight analysis
Python, pandas, and matplotlib are planned for plotting altitude and acceleration against time, marking flight events, and comparing measured apogee with the OpenRocket prediction. The write-up will examine possible differences in drag, actual mass, motor performance, and launch conditions. The aim is to use those observations to improve the model and identify changes for the next test.
Project roadmap
The 17-week plan runs from late September 2026 through January 2027. Early October focuses on design and simulation; later October on airframe construction; early November on updated simulations and flight preparation. After the first launch, the focus shifts to sensors and firmware, followed by electronics integration, an instrumented flight, and a final report with plots and lessons learned.
Budget and resources
The planning document estimates roughly $295 for a lean build using borrowed tools and launch equipment, or about $415 with a larger allowance for motors and equipment. These are preliminary estimates, not recorded spending. Membership, launch fees, transport, sled fabrication, and replacement parts are outside those totals. The hardware list and budget will be updated as parts are selected.
What I plan to share
As the project progresses, this page will document the evolving design, build photos, simulation results, flight logs, and measured data. The final deliverable is a report that connects the design choices to flight behavior and records what worked, what changed, and what I would improve. The project is currently in progress; no flight results are claimed yet.