Sophomore at Westborough High School. I design parts in Fusion 360, lay out PCBs, and write the embedded code that makes hardware do things. I also lead the rocketry club I brought back from the dead. Next stop: aerospace engineering at MIT. Scroll down to take a rocket apart.
I'm a sophomore at Westborough High School, and I build across the whole stack: CAD models that become 3D-printed parts, PCB layouts and circuits that become working hardware, and the embedded code that ties it all together. Rockets are where all of it has to work at once, which is exactly why I like them.
I worked through every prerequisite course for MIT Beaver Works' autonomous drone racing program, covering flight control, quadrotors, Python, and a lot of linear algebra, and I still use that material constantly. I also lead our school's rocketry club, which was completely dead when I took it over. Today there are fifteen of us building and flying together.
A Raspberry Pi 3B+ with a small OLED screen that acts like a face. It blinks, has moods, and reacts when you scan RFID tags, with a different message for each tag. Most of the work turned out to be debugging: timing problems, glitchy drawing, and getting the expressions to actually look like expressions.
A Python simulator I wrote while working through the MIT Beaver Works coursework. It models a quadrotor held level by PID loops, lets you add wind to knock it around, and plots what the controller does to recover. Tuning the gains myself taught me more than the lectures did.
A Raspberry Pi tool that reads OpenRocket's .ork simulation files and flags stability or recovery problems before we launch. Results show up through a little pixel-art assistant. It started as an excuse to learn XML parsing and is turning into an actual pre-flight check for the club.
A set of parametric Fusion 360 models for nose cones, fin cans, and centering rings. Type in a body tube diameter and it's ready to print. The goal is for a new club member to go from idea to printed part in one meeting.
A drone that records GPS position and RF signal strength while it flies, then turns the log into a heatmap of where control signal drops out. Useful for anyone flying somewhere new.
An ignition controller for club launch days: key-switch arming, a continuity check, and one big red button. Modeled on how real launch ranges handle safety, scaled down to what a school club actually needs.
When I took over the Westborough Rocketry Club, it was dead. No meetings, no launches, nobody showing up. Rebuilding it took a while, but now we're an active 15-member club. I run the meetings and teach CAD to anyone who wants to learn it, and we plan our builds and launch days together.
We've flown in the American Rocketry Challenge, and every flight changed how we built the next rocket. For next season the plan is better preparation: altimeter data from every launch and OpenRocket sims before we fly, so we find problems on a screen instead of on the pad.
Last June we put on Rocket Day, a full-day program to get middle schoolers into rocketry. I led the planning and the whole club made it happen. Presentation, CAD lesson, build, lunch, and a real launch at the end.
A full-day program for rising 7th–9th graders: an intro presentation, a hands-on CAD lesson, rocket building, lunch, and a real launch to close it out.
Flight control, quadrotors, Python, linear algebra, probability. Every prereq for the autonomous drone racing course.
Took over a completely inactive club and grew it back to 15 members who build and fly together.
Flew our first competition season. Every flight became notes for the next build.
A full-day program the whole club put on for ~20 rising 7th–9th graders. I led the planning: presentation, CAD lesson, build, and launch.
An altimeter in every club rocket and OpenRocket sims before each launch, so we stop guessing.
Back to the American Rocketry Challenge with a season of experience behind us.
Where all of this is pointed.