Measured the flow around an airfoil in a water tank with particle image velocimetry at eight angles of attack, then turned the vector fields into circulation, lift, and Reynolds number.
What I did
Processed all eight angles in PIVlab and found why the exported images held almost no particles, then picked ensemble correlation and a three-pass window schedule that worked anyway.
Wrote a MATLAB batch script on PIVlab's own functions, checked it against the GUI result at 0° (all 377 valid vectors match), and used it for the remaining angles.
ResultLift coefficient follows the reference chart's trend from −5° to +5°; a MATLAB pipeline that reproduces the PIVlab GUI vector for vector
Founded an engineering society, led it as president, and led the turbocharger-based jet engine its technical core builds.
What I led
Founded JAS in October 2023, then ran for president and won. Grew it past 500 members with 6 officers and a 30-engineer technical core.
Ran weekly engineering reviews, partnered with Blue Origin, AMD, and Northrop Grumman, whose engineers attended meetings and gave guidance, and led the turbocharger jet engine design.
A packed general body meetingTurbocharger jet engine PDR, Mar 2024
Experience
I have a strong bias for hands-on engineering where the data proves the design. The Starship program taught me that humility is part of the engineering. Look past your own assumptions and lean on the technicians who run the hardware every day. Care about getting it right for the vehicle, not just your own design. Everything I build runs through the same four steps: design, build, test, and scale.
~10xproduction-rate scale-up my bonding cell was designed for, adopted at CDR
~90%cost cut from a DOE I ran
80%+less marking time per part with my laser cell
12projects owned or led, concept to hand-off
I worked on the team responsible for Starship's thermal protection hardware at Cape Canaveral. My days were split between development work and the production floor. Development meant research, design, planning, and building out project proposals. On the floor, I worked with technicians to integrate equipment and run down root causes when something failed. Much of the job was taking requirements that were undefined or still moving and turning them into proposals, engineering models, drawings, and hardware. Then I validated how they actually held up during integration and testing.
Two areas took most of my time. The first was inspection and test. I developed clearer ways to verify heatshield components at every stage, from the first step through integration on the vehicle. That included physical testing on T1 flight hardware. The second was equipment engineering, where I ran trade studies, specified cells, and stayed with them through procurement, installation, and the first weeks on the floor. I also replaced a manned, semi-automatic ink station with an automated laser marking cell that cut marking time per part by more than 80%. I designed it in NX, assembled it alongside technicians, and it ran with near-continuous uptime. My largest project was an automated bonding cell for Starship V3, designed from the start around the rate the program needs. In July, the thermal protection system had flight-blocking needs in Texas. It's still the most critical system on the vehicle, so I surged from the Cape to the Starfactory at Starbase to help on site.
Read more +Show less −
I split my time close to evenly between the desk and the floor. I mentored technicians and other interns on the work I owned. I learned that a big part of being an efficient engineer is teaching others how they can help instead of doing everything yourself. Late in my term I presented my work to Starship program leadership. My review package became a reference for the rest of the team.
Operating at the speed of a flight program was my biggest learning curve. Early on, some of my work was set aside as requirements shifted. That taught me not to take pivots personally and to refocus where the team needed me. Later I was trusted with sole ownership of several systems that are still operational today. I learned that acting quickly and with intent, then learning from the result, beats waiting for the perfect decision.
How SpaceX changed how I work
First principlesQuestion every requirement and delete steps before optimizing them.
Stay paranoidAssume every failure mode can happen and design it out.
Fail fastA fast test that fails teaches more than a slow one that's perfect.
Root cause5 Whys, fault trees, and FMEA before any fix.
The full stack at Starbase▶A Super Heavy booster rolling outWith a ship at Starbase during the July surge▶Launch day at Starbase, before the scrubA launch lighting up the sky on an early drive into work
May 2025 - Aug 2025 · 4 mo
Firehawk Aerospace
Propulsion Design Engineering InternAddison, TX
DesignBuildTestScale
360%projected fuel grain capacity gain from my tooling
U.S. Armyprograms carried through hot fire and delivery
I was a propulsion design engineering intern at a hybrid rocket startup in Addison, Texas. My days were split between the desk and the floor. At the desk I designed in Creo Parametric 9, ran structural analysis, and developed tooling. The rest was hands-on work on the floor.
My main project was FDM tooling for fuel grain production: one-time-use molds with O-ring glands and vacuum-capable iterations. Testing validated seal integrity, bond-layer uniformity, and cure. The projected result was a 360% gain in production capacity. I also spent real time in the lab formulating adhesives and iterating fuel grain geometry. That work fed straight back into the same bottleneck my tooling was built to fix.
Read more +Show less −
I kept up with my project well enough to go looking for more. I helped build out a water flow test stand. I also designed a 50,000+ lbf horizontal static fire stand, from CAD through the plumbing and assembly. On a 3,500 lbf N2O/ABS hybrid campaign, I designed, built, and fired parachute bay assemblies. The successful hot fire was presented to the U.S. Army. They used a shear-screw breakaway and a black powder charge of my own design. I owned their test plans in Epsilon3. I also worked with the company machine shop to CNC and lathe parts on the critical path for flight tests, including igniters and test fixtures for U.S. Army programs that went on to a successful hot fire and delivery.
What I walked away with came from the tests that didn't go the way we expected. There was a lot of failure. Many times, something I thought I understood got challenged. It taught me to work backwards from a result to find where and how something failed. That prepared me for what came next more than any result that went right.
How Firehawk changed how I work
Failure is the dataMost of what I learned came from tests that didn't go as expected. I work backwards from the result to where it broke.
Own the testI designed, built, and fired my parachute bay assemblies, owned their test plans in Epsilon3, and the successful hot fire was presented to the U.S. Army.
Fix the bottleneckMy grain tooling, adhesive work, and geometry changes all went after the same production limit.
Then ask for moreOnce my project was on track, I went looking for more. I helped build a water flow test stand and designed a 50,000+ lbf static fire stand.
The Firehawk team, summer 2025A flight test off the Firehawk towerThe vehicle I worked on, on the prep table · Image: Firehawk AerospaceA hot fire in the Firehawk test cell · Image: Firehawk Aerospace
Drawings I made for Firehawk
Firehawk 3D prints its propellant and fuel grains. These are the three product cutaways I drew for their website, each one sectioned to show the printed grain inside.
Solid rocket motorA 3D printed propellant grain inside a motor case built to hold combustion pressure and temperature, lit by the igniter at the forward end.
Base bleed motorAn artillery shell with a printed base bleed grain. Gas bled from the base during flight cuts drag so the round flies farther, with the payload up front and fins for stability.
Hybrid rocket engineA 3D printed fuel grain, the control system that throttles it, and the oxidizer tank that feeds it.
May 2024 - Aug 2024 · 4 mo
Space Resource Technologies
Manufacturing Engineering InternOrlando, FL
DesignBuildTestScale
4 wk → 6 hsame-batch processing
100sruns tracked
I'd call this my first real engineering job. SRT made regolith simulant for aerospace customers, and the process ran almost entirely on tribal knowledge.
I spent my days watching where waste was produced and working out how to fix it. Then I worked entire shifts on the line myself with the operators to make sure each fix actually held. Before changing anything, I tracked units per day, batch time, labor, faults, and downtime across hundreds of runs.
Then I reorganized the production cells around Lean Six Sigma, integrated the equipment, and wrote the SOPs. Same-batch processing went from four weeks to six hours. The lead manufacturing engineer adopted the flow.
The SRT production teamThe crushing and screening lineRegolith simulant in the mixer
Jan 2023 - Apr 2023 · 4 mo
UNEW
Engineering InternPort Salerno, FL
DesignBuildTestScale
1stinternship, senior year of high school
Scan vs CADredesigned parts checked against ATOS blue-light scans in GOM Inspect
H₂gas-turbine fuel research presented to the engineering team
My first internship, at a company that reverse engineers and manufactures replacement parts for industrial gas turbines.
Most of my time went into learning Siemens NX and redesigning several turbine fixtures and parts. Then I blue-light scanned the real parts on an ATOS ScanBox and compared them to my models in GOM Inspect. That comparison is where tolerances, manufacturing defects, and what machining actually does to a design first made sense to me.
I worked through my assignments quickly enough to ask for more. So I researched hydrogen as a fuel for gas turbines: what it takes to produce, store, and use it responsibly. I presented what I found to the engineering team. It was the first time I saw how engineering actually gets done. It's a large part of why I chose aerospace.
The automated scan cellBlue-light scanning on the ATOS ScanBoxPresenting my work and hydrogen research to the engineering team
The story so far
I'm an aerospace engineering student at the University of Central Florida, finishing my degree in December 2027. In Florida, launches have always been part of the view. Chasing that feeling pulled me into a cockpit first, and then onto test stands and factory floors.
Here's the path so far, in order. Tap any entry for the photos and the story behind it.
Latest
Oct 2026Built Spinfield, my benchtop magnet spinner. Testing is next.
Sep 2026sterlingpearson.com went live, designed and launched by me.
Aug 2026Started planning the L1 active-fin GNC project.
Aug 2026Wrapped eight months on Starship thermal hardware at SpaceX.
Building it myself, next to the people who run it.
Swagelok high-pressure plumbingRegulators, solenoids, relief valvesTorque toolingSoldering and harnessesCNC and manual machiningAdditive / FDMLaser cuttingFixtures and toolingSOPsLean Six Sigma3P
In progressL1 active-fin GNC, planningLatest buildSpinfield magnet spinner, built Oct 2026Last flightSingularity 26, NAR Level 1, Apr 2025Hot firesRDE pre-detonator, 100 to 1,000 psiIn industry20 mo experience, four companiesFoundedJAS at UCF, 500+ membersThis siteDesigned and launched Sep 2026
In progressL1 active-fin GNC, planningLatest buildSpinfield magnet spinner, built Oct 2026Last flightSingularity 26, NAR Level 1, Apr 2025Hot firesRDE pre-detonator, 100 to 1,000 psiIn industry20 mo experience, four companiesFoundedJAS at UCF, 500+ membersThis siteDesigned and launched Sep 2026
Before rockets there were airshows. In 2014 I went to Sun 'n Fun in Lakeland and the Stuart Air Show. I got as close as I could to every jet and prop on the field.
The Stuart show was at Witham Field, the same airport I trained out of eight years later.
Under an F-14's exhausts at Sun 'n FunSun 'n Fun, LakelandSun 'n Fun, LakelandStuart Air Show, Witham Field
Flight training in a C172, ~70 hrs
Flying
I trained toward my private pilot license in Cessna 172s out of Stuart, Florida, and logged about 70 hours. I had to stop just short of the final exam. The clip below is my first solo touch-and-go landings.
Flying taught me rigor. Stick to the checklist every time. Always respect safety with healthy margins. Make calm decisions when conditions take a turn for the worse or turn out unexpected.
More than anything, it trained me how to think. In the air you are constantly making decisions under time, pressure, and stress. You learn quickly that what you expect to see is not always what is there. It taught me critical thinking in fast-moving situations and to never trust my own assumption bias. I check, then act. That habit carries straight into my engineering work.
A lot of my flying was along the coast, late in the evening and into the night. The sights were spectacular, a truly one of a kind experience.
▶My first solo touch-and-go landings
Cross-country · Feb 6, 2023
My first cross-country
Out of Stuart, south of Lake Okeechobee to a turn near Immokalee. Then north up the west side of the lake on GPS waypoints to Okeechobee County, and home to Stuart. I sketched the loop by hand first, then built and flew it from a ForeFlight plan.
Route redrawn from my ForeFlight plan. Waypoints to scale, lake outline approximate.
AircraftCessna 172 · N1589D
RouteKSUA → Immokalee → KOBE → KSUA
Planned130 nm · 1 h 19 m
NavigationForeFlight · GPS waypoints
Return leg95 kt groundspeed
The G1000, inbound to Stuart
With a 172 on the rampN1589D at duskThe beach off the wingSunset under the wingCity lights under the wing
Surge support · Jul 2026
Starbase
During my co-op I surged from the Cape to the Starfactory at Starbase. I helped with flight-blocking work on the thermal protection system, which is still the most critical system on the vehicle.
Outside of work I got to see the site up close. I saw a ship rolling out with its heat shield facing us, the booster and ship lit up on the pad after dark, and the full stack at first light. On launch day I joined the crowd for the attempt, but it scrubbed and didn't fly that day.
Dawn at the launch siteThe stack under the lights▶Super Heavy under the lightsStage separation, seen from the ship · Image: SpaceXStarship above the Earth · Image: SpaceXThe pad after darkThe stack at first lightThe full stack venting▶A ship rolling out, up close on the heat shield tilesRollout with the crowd along the highwayA Super Heavy booster at duskIn front of the rocket garden▶Launch day crowd, before the scrub
Jun to Jul 2023 · 9 stops
Japan
In the summer of 2023 a friend and I spent nearly four weeks in Japan on a trip we planned and made on our own. We flew into Tokyo and crossed to Kanazawa. From there we worked down through Kyoto, Nara, Osaka, Kobe, and Hiroshima. Then we came back east to Kawaguchiko and climbed Mount Fuji before flying home out of Tokyo.
It was an extraordinary experience and completely eye opening. Figuring out every leg of it ourselves showed me how much is possible when you set your mind to something. I've carried that sense of limitless potential into everything since.
Tokyo at nightTokyo TowerSenso-ji, AsakusaKanazawa CastleKenroku-en gardenKinkaku-ji, KyotoFushimi InariArashiyama bamboo groveTodai-ji, NaraDeer among the stone lanternsOsaka CastleDotonbori, OsakaThe whale shark tank, OsakaThe ropeway above KobeHiroshima Peace MemorialMount Fuji from FujikawaguchikoA torii on the mountainAbove the clouds before dawnMorning from the mountain
Knights Shadow Program · Aug 2024
Shadowing NASA
Through UCF's Knights Shadow Program I spent a day at Kennedy Space Center shadowing NASA scientists and engineers.
We walked Launch Complex 39B and looked down into the flame trench. We stood inside the Vehicle Assembly Building next to Artemis hardware. Then we toured the labs and shops where test articles get built and shaken. Seeing the people behind that hardware at work made the path feel real.
Our group at Launch Complex 39BThe mobile launcher at 39BInside the Vehicle Assembly BuildingWith the SLS core stageOur group in the VABThe machine shop
With SEDS at UCF · Feb 2024
Blue Origin tour
I toured Blue Origin's Florida facility with SEDS at UCF. Standing under a flown booster and witnessing the real engineering happening so close by gave me motivation and passion to push harder into the industry.
Up to then the industry had felt far away. Seeing it such a short drive from home, and meeting the people doing that work, pushed me to go after hands-on experience. That experience led to everything after it.
Arriving at Blue OriginUnder the flown boosterLooking up at a flown booster
Skiing in Utah, Dec 2025
Park City
When I get the chance, I love to ski. My family, my girlfriend, and I spent the end of 2025 in Park City, Utah. We skied and enjoyed the winter snow and Christmas before my co-op at SpaceX.
A few days on the mountain was exactly the unwind I needed. It gave me space to reset and head into the biggest step of my career so far with a clear head.
Park City, UtahAt the bottom of a runSnowfall at dusk
← BackUCF Propulsion and Energy Research Laboratory
Rotating detonation test cell
A 6 in dual-mode rotating detonation engine needs a pre-detonator that reliably turns a flame into a detonation. It also needs a test cell that can feed it, time it, and record it safely. I helped build and run that cell.
Deflagration-to-detonation transition only happens inside a narrow window of pressure, mixture, and timing. To find that window you need three things: a propellant system you trust at 1,000 psi, valve timing you can repeat to the millisecond, and data fast enough to see a detonation wave go by.
A day I remember
The day I remember most was an RDE hot fire. It started hours earlier with the plumbing: cleaning, prepping, fitting, and installing hardware on the test bed and the engine. Then we started firing, and it was incredibly loud. Run after run, the engine only deflagrated instead of detonating. When it finally detonated, I watched the Mach diamonds form in real time. It was an extraordinary feeling.
Why it matters to me
I did this on my own time. It showed me what being on a research team is actually like, working on hardware that's personal to me. More than anything, it showed me the full cycle of engineering: building an engine, then operating it.
What I did
Plumbed and instrumented the Swagelok high-pressure fluid system and the DAQ hardware. Proof and helium leak checked the lines before every hot-fire series.
Fabricated the electronics enclosures. Designed and soldered custom wiring harnesses for DAQ integration.
Automated solenoid valve timing and synchronized data capture in Python and Arduino.
Ran liquid pre-detonator hot-fire campaigns from 100 to 1,000 psi, characterizing injector spray and verifying deflagration-to-detonation transition at the exit plane.
Reduced the pressure data in MATLAB to estimate wave speed and pick out stable operating regimes.
Figures
DAQ and power wiring for the test cellDAQ rack model, SolidWorks
Over two years with KXR I worked on three propulsion teams: combustion for the IREC hybrid, then fluids on the Hall effect thruster and the liquid bi-propellant feed system. Each one is below, in order.
RolesCombustion · fluids
WhenFall 2023 to Dec 2025
TeamsIREC hybrid, Ion propulsion, Liquid bi-prop
ToolsTrade studies, P&ID, MATLAB, Ansys CFD
Presenting the ablative liner at the IREC propulsion CDR
Three teams
IREC
IREC · Fall 2023
IREC hybrid combustion
RoleCombustion team
TeamKXR · IREC, Spaceport America Cup
ToolsTrade studies, CDR, manufacturing
KXR's IREC team was building a hybrid rocket for the Spaceport America Cup. I worked the combustion side, from the injector trade to pouring the fuel grain propellant.
IREC · Injector trade
Ran trade studies comparing showerhead, vortex, swirl, and throttle injector plate designs against regression rate and efficiency. The vortex injector was selected and carried forward with specific manufacturing angles.
IREC · Thermal liner
Owned the chamber's ablative liner and presented it at the propulsion Critical Design Review: fiberglass and phenolic resin, 0.125 in thick, built up from biaxial and unidirectional plies.
Wrote its requirements with a verification method for each: survive chamber pressure and temperature (test), integrate with the combustion assembly and seal on the nozzle and forward bulkhead (demonstration).
Scored its failure modes, burn-through and cracking, in the project risk matrix with a mitigation for each.
Worked the manufacturing of the liner and its mandrel, laid and cured the phenolic liner with a few teammates, and mixed and poured the fuel grain propellant by hand.
Liner design and requirements, from my CDR slidesLiner cost and risk matrix
Walking reviewers through the liner designPouring the fuel grain propellant
IREC · When it didn't fly
The motor suffered an anomaly and the rocket couldn't fly. It was the first time I had put real hours into hardware that failed, and it became a pivotal point in how I think about engineering. A failure isn't the end of the work. It's the most honest data you get. You go back through every decision, find where it broke, and carry that forward.
I leaned on that mindset later at Firehawk and SpaceX. There, the tests that didn't go to plan taught me more than the ones that did.
Hall
Hall · Fall 2023
Hall effect thruster
RoleMechanical fluids team
TeamKXR · Ion Propulsion, 10 to 20 people
ToolsTrade studies, P&ID, component selection
A propellant decision made before any hardware was bought. On the mechanical fluids team I worked the feed trade and drafted the first P&IDs ahead of the design review.
Hall · The trade
Ran propellant feed trade studies between argon, krypton, and xenon, weighing acquisition, handling, and cost alongside performance. Carried the result into the design review.
Hall · Feed system
Drafted the initial P&IDs and helped select hardware ahead of the PDR.
Hall · What came next
I moved to other projects after the design review. The team of 10 to 20 took the thruster on into testing, where it was successful.
Hall · PDR
Our subteam at the Ion Propulsion PDR, Nov 30, 2023The full Ion Propulsion team after the PDR
On the fluids side, I needed an architecture that was safe first and sized second. I designed the P&ID, sized the system, and specified the regulators down to the seat material.
Bi-prop · Architecture
Bi-prop · Safety first
Defined flow paths, interfaces, isolation points, and testability in the P&ID before sizing anything.
Set 850 psi relief protection on the nitrous run tank and remote solenoid actuation so nobody is near the stand when it's live.
Screened PCTFE and PEEK seats against LOX/GOX oxygen-compatibility and cold-temperature data. PCTFE went on the oxidizer side, PEEK on the hydrocarbon side.
Bi-prop · Regulator selection
Line
Inlet
Outlet
Body
Seat
Cv
Candidates
N₂O
850 psi
600-700 psig
316 SS
PCTFE
0.20
Swagelok KPR · Parker IR4000
Propane
~150 psi
~120 psig
316 SS
PEEK
0.20
Swagelok KPR · Parker IR4000
Bi-prop · Injector
Modeled injector internal flow and spray formation in Ansys CFD to set preliminary fluid-system requirements before committing to hardware.
A small airfoil sat in a seeded water tank while a camera filmed the particles at 160 frames a second. I processed every angle of attack from −10° to +25° in PIVlab, built a MATLAB pipeline to run them the same way, and wrote the experiment and results sections of the team report.
StatusComplete
RoleTeam of 4. This page shows my part: the PIV processing and report Sections IV and V
WhenOct 2026
ToolsDantec EduPIV, PIVlab 3.14, MATLAB, Excel
Velocity magnitude and streamlines around the airfoil at 0°, from 80 image pairs
The setup
▶The airfoil stepping from −10° to +25°, with tracers carried by the measured PIV field at each angle. Frames between two angles blend the two measured fields, and the airfoil is drawn as a smooth outline fitted to each mask
The tank is a Dantec EduPIV. An LED sheet lights a thin slice of seeded water, and a FlowSense USB 2M-165 camera records pairs of frames 6.25 ms apart. The airfoil has a 90 mm chord and 76 mm span. I calibrated the images at 853 px for the 90 mm chord and ran 160 frames at each of eight angles, −10° to +25° in 5° steps.
We took the data in one session on October 6. The tank and camera (a FlowSense USB 2M-165 and an LED light) were already set up, and the TA handled the camera. I set the angle of attack at each step, our team ran acquisition, calibration, and the particle density check in DynamicStudio, and I kept the session notes. I owned the processing that followed.
▶Particle motion around the airfoil at 0°
The data problem
One exported frame as PIVlab received it. Every pixel is black or white
The exported frames held almost no particles. Left, one frame with three 96 px windows (particles drawn larger to show). Right, mean particles per window over 40 frames, under one in every open window. The handout asks for 5 to 10
In the lab the particle count read 7 to 9 per window, inside the handout's 5 to 10. The frames we exported were black and white only, 0 or 255, and almost every window held less than one particle. The particles were there in the tank. The export threw away their brightness and most of them with it.
Standard PIV correlates one pair of frames at a time and needs several particles in each window to find a peak. With under one, single pairs gave noise. So I switched to ensemble correlation, which adds the correlation of all 80 pairs before looking for the peak.
Choosing the settings
Valid vectors at 0° for three PIVlab settings. Run B, three passes down to 64 px, kept the most real vectors
I set the windows by hand at 256, 128, then 64 px. The suggested settings were too small to hold any particles.
Mean background subtraction removed the white model and the glare, which never move. Contrast enhancement only amplified noise in two-level images, so I left it off.
I traced a tight mask just inside the model edge. Most particles travel close to the surface, and a wider mask removed them. PIVlab's automatic mask kept 4 to 13% fewer valid vectors than mine.
Run B gave 377 valid vectors at 0°. High robustness (run C) took longer and kept fewer, so I kept B.
Checking the script against the GUI
My batch script against the PIVlab GUI at 0°. All 377 valid vectors match, largest difference 0.0001 m/s
Processing each angle by hand in the GUI took a long time, so I wrote a MATLAB script that calls PIVlab's own ensemble and validation functions with my settings. Before using it I ran it on the 0° case I had done by hand. Every vector got the same valid or rejected label, and the largest velocity difference was 0.0001 m/s. Then I ran the rest with it. In all, three angles were processed by hand in the GUI and five by the script.
The core of the script is PIVlab's own ensemble and validation functions, called with my settings:
% Ensemble PIV with PIVlab's own function, three passes: 256 -> 128 -> 64 px
[x, y, u, v, typevector, corrmap] = piv.piv_FFTensemble( ...
filepath=filepath, interrogationarea=256, step=128, ...
bg_img_A=bgA, bg_img_B=bgB, clahe=0, ...
converted_mask=converted_mask, passes=3, ...
int2=128, int3=64, int4=32, imdeform='*linear');
% Calibration: 853 px = 90 mm chord, 6.25 ms between frames
calxy = 0.090 / 853; dt = 0.00625; calu = calxy / dt; calv = calu;
% Same validation the GUI applies: velocity limits, stdev 8, local median 3,
% correlation filter 0.5
[~, ~, typevector_filtered] = validate.filtervectors_all_parallel( ...
x, y, u, v, typevector, calu, calv, velrect, 1, 8, 1, 3, ...);
The flow at every angle
Velocity magnitude at all eight angles on one color scale, in PIVlab's display style (red x marks the mask)u-velocity along the upper and lower surface at every angleVelocity magnitude and streamlines at +20°, where the flow behind and above the airfoil breaks up
The fastest flow, about 0.3 m/s, runs along the lower surface. Past +15° the flow above and behind the airfoil slows and breaks up, which is what stall looks like. The Reynolds number stayed between 3,900 and 6,200, so the boundary layer was laminar at every angle. That uses water at about 25 °C, since the tank temperature wasn't recorded.
Circulation and lift
Circulation against angle of attack. The shaded range is where the upper surface was measured well enough to trustLift coefficient from the measured circulation against the handout's example chart for typical airfoils, −5° to +5°
I found circulation by integrating the velocity around five circles centered on the chord, 0.52c to 0.64c in radius, and averaging them. The geometry was the same at every angle. Then I computed lift from Kutta-Joukowski, F = ρVΓb. From −5° to +5° the lift coefficient follows the reference chart, −0.63, 0.33, and 0.62 against about −0.45, 0.1, and 0.6.
Above +5° it goes the wrong way. The airfoil shadowed the light sheet over its upper surface, so almost no vectors were measured there, and the circulation is dominated by the lower side. I report those angles as measured and flag them instead of adjusting them.
What I learned
Check the data before the algorithm. I spent the first runs changing PIVlab settings before I counted particles in the frames. The count explained everything, including why the vectors flipped direction when I changed the window size.
Validate a script against a known answer first. Matching the GUI at 0° vector for vector is what let me trust the batch results at the other angles.
Know which parts of the field you can believe. The circulation sign looked like a lift result at every angle. Separating the circle above the airfoil from the one below showed the upper side was nearly empty, and that changed what I could claim.
The freestream is a measurement too. The tank speed was never recorded. I took it from the mean u along the top row of the field. At +20° and +25° that row sat in disturbed flow, so with the pump at one setting throughout I used the mean of the other angles there, 0.048 m/s.
How I'd run it again
Export 8-bit grayscale frames and check the particle count in the exported files before leaving the lab.
Record the pump setting and measure the freestream directly.
Add a second light sheet or camera angle so the upper surface is lit at high angles of attack.
← BackNASA L'SPACE Mission Concept Academy · Team 15
Martian rover mechanical subsystem
NASA's L'SPACE Mission Concept Academy asked our team for a small, low-cost robotic reconnaissance mission to Mars. The goals were to find the regions best suited for a future human landing and characterize the water a crew would depend on. Science drives the design, and the customer's limits were fixed. Break any one of them and the mission is cancelled.
RoleMechanical engineer and scientist
WhenSpring 2024
TeamTeam 15 · 10 members
MilestonePDR, the academy's final review · Apr 15, 2024
Rover general arrangement, Siemens NX
The mission
A human landing site lives or dies on access to about 100 metric tons of water. Our rover's job was to scout Exploration Zones in the Martian mid-latitudes, within ±60° where temperatures are tolerable and solar power is reliable, and characterize the water feedstock across Regions of Interest within about 100 km of a central landing site.
The profile: launch on Dec 31, 2028, a 240-day cruise, and arrival on Aug 28, 2029.
The academy
The work ran through four staged reviews, MCR → SRR → MDR → PDR, each led by a different subteam. The PDR was the full-team consolidation and the final accomplishment of the academy.
My part
Owned the rover's chassis, suspension, wheels, and robotic arm, the majority of its mechanical design. That included how they fit with what the other subteams built.
Modeled all of it in Siemens NX.
On the science side, researched the Martian wind and radiation environment that set two of the mechanical requirements.
When teammates left partway through, I picked up a second role as a scientist to cover the gap, alongside my mechanical work.
Team 15's final org chart. I was a mechanical engineer and scientist
Constraints
Customer limit
Value
Result
Mass
≤ 45 kg
Mechanical subsystem at 16 kg
Stowed volume
100 × 100 × 100 cm
Fits the stowed cube
Cost
≤ $300M
Mission-level analysis
Science instruments
≤ 2
Mission-level
Power source
No RTG
Mechanical draw 20 W · 0 g radioactive material
Mechanical requirements
Six subsystem requirements, each traced to a parent, given a number, and assigned a verification method. All six were marked met at the PDR.
Req
Requirement
Number
Verified by
MSR-1
Traverse the Martian terrain
1 cm/s average
Test
MSR-2
Carry the full mass allocation
45 kg
Test
MSR-3
Fit the stowed envelope
100 × 100 × 100 cm
Demonstration
MSR-4
Arm range of motion
350° horizontal, 340° vertical
Demonstration and test
MSR-5
Mean Martian wind
1 to 4 m/s
Demonstration and test
MSR-6
Native Martian radiation
24 to 30 rad per year
Demonstration
Trade studies
Four weighted studies, each with explicit criteria and a 10 / 5 / 1 / 0 rubric.
Decision
Selected
Score
Runner-up
Why
Robotic arm
Three-axis
71.5%
Five-axis 62.5%
Fewer joints, fewer failure modes, and NASA heritage beyond the score
Suspension
Rocker-bogie
80.0%
Independent 62.0%
Longevity weighted 30%, climbs 14 cm, tilts to ~45°
Landing
Airbags
65.0%
Skycrane 55.0%
Cost and flight heritage at this mass
Wheels
Aluminum
70.0%
Steel 65.0%
Six steel wheels ate too much mass. Risk accepted and mitigated
Verification
Every requirement got a method, Test, Inspection, Demonstration, or Analysis, and a written plan.
A regolith test bed with a cable to offload gravity for the wheel system.
A 45° incline demonstration for the rocker-bogie.
FEA against Martian temperature swings, then vibration with a 3-axis fixture, acoustic, and vacuum for launch and cruise.
TRL assessed per component, from 5 for the wheels to 7 for the arm.
What stuck with me
It's one of the projects I think about most. Nothing was open ended: a hard 45 kilogram budget and a one meter cube to stow inside, so every choice was a trade I had to write down and defend. It gave me insight into the complexity of the machines that go and explore worlds beyond ours. I still remember the in-depth discussions over the different arm axes. We had to consider how things could fail an average of 140 million miles from home. What stuck with me most was how rigorous the requirements were. The data had to back up every decision I made, to a tee. It gave me real experience with how things are done at NASA and strengthened my mental toolbox.
Rocker-bogie suspension climbing, from the PDRArm and deployable design overview, from the PDR
← BackUniversity of Central Florida · Student organization
Jet & Aeronautics Society
I founded JAS in October 2023 to give students a place to build jet and aerospace hardware, not just talk about it. I started as its Outreach and Marketing Officer and Turbocharger Jet Engine lead, then ran for president and won. When I handed it off in January 2026, it had grown past 500 members. It's still active under new leadership.
RoleFounder · Outreach and Marketing Officer and Turbocharger Jet Engine Lead, then President
WhenOct 2023 to Jan 2026
Team6 officers · 30-engineer technical core
PartnersBlue Origin, AMD, Northrop Grumman
Presenting JAS at a recruiting event
Leading JAS
I founded JAS and started as its Outreach and Marketing Officer and the Turbocharger Jet Engine lead. The next year I ran for president and won. Most of my time then went into leading it: setting the direction, running the reviews, and getting in front of the room to pitch what we were building and why it mattered. When my term ended, I handed it off to the next team.
Founded and grew JAS to 500+ members, and as president led 6 officers and a 30-engineer technical core.
Ran weekly engineering reviews, technical workshops, and a project cadence, and built partnerships with Blue Origin, AMD, and Northrop Grumman, whose engineers attended meetings and gave members guidance through external channels.
Recruited at campus events, pitching the society and its projects to incoming students.
Pitching our projects at a recruiting eventA packed general body meeting
The turbocharger jet engine
The technical side I led was a turbocharger-based jet engine. I kicked the project off in front of the members: the goal, the major subsystems from the flame tube to the turbocharger, the timeline, and the open questions we had to answer first. Then I sketched the layout on the whiteboard, fuel and spark into the combustor, with the turbocharger closing the loop.
Guided the team through trade studies, preliminary design, and critical design reviews with industry partners.
Drove the flame-tube combustor through trades to manufacturable geometry.
The engine was design only while I led it. The team is taking it into testing now under new leadership.
The whiteboard sketch of the engine layoutTurbocharger jet engine PDR, Mar 2024Presenting at the PDR
Blue Origin GBM
Blue Origin came to UCF for a general body meeting with JAS, talking our members through their careers and the path into the industry. It was exactly the kind of access I wanted JAS to create for its members.
My first high-power rocket and my NAR Level 1 certification vehicle. I designed it, built it, and flew it. The name comes from my passion for space and for singularities, whose mystery has always fascinated me.
RoleDesigner and builder
MotorH135W · Tripoli launch near Melbourne, FL
ResultNAR Level 1 certified
ToolsOpenRocket, SolidWorks, additive, machining
Me with Singularity 26 on the rail before its flight
Design
Modeled flight stability in OpenRocket and designed the structures in SolidWorks.
Printed the nose cone and fabricated the remaining components with additive manufacturing and machining.
Nose cone in CADThe printed nose cone
Build
Airframe on the benchRecovery gear back out after the flightMe with the finished rocket
Flight
Launch day was in April 2025. I flew it on an H135W at a Tripoli launch near Melbourne, Florida, with a single-deploy recovery system. A successful launch and recovery earned my Level 1 certification.
▶Singularity 26 lifting off on its certification flight (video)Singularity 26 off the rail
Spinfield spins a magnet under a nail to set the pattern in magnetic polish. I designed it in Siemens NX and took it through three builds: a manual spinner, a preliminary automatic design, and the test design.
StatusBuilt · testing next
RoleSole engineer
StartedSep 2026
ToolsSiemens NX, FDM / PLA, PWM motor control
The finished spinner with its horseshoe magnet rotor
Progression
All three builds, left to right: manual spinner, preliminary automatic design, test design
Stage 1Manual spinner
A hand-turned disc with a spoke and an insert that holds the magnet. No motor: the magnet is spun by hand.
Stage 2Preliminary automatic design
The first full print of the station: housing, door, and base in white PLA, with the parts placed differently than in the final build.
Stage 3Test design
The finished unit: black housing, the red horseshoe magnet on a set-screw mount, the worm gearmotor, a PWM speed knob, a toggle, and a barrel jack.
The model
Full assembly · Siemens NX exportDrag to rotate
Loading model…
The full assembly from Siemens NX: printed housing and door, horseshoe magnet on its printed mount, right-angle worm gearmotor with its shims, PWM speed controller, toggle, and barrel jack. Pick a part to isolate it, or explode the set to see the drive.
Build
A PWM speed controller, the toggle, and a barrel jack sit inside the housing, wired to the worm gearmotor.
The finished unit from the frontHousing open, with the wiring insideSpeed controller, toggle, and jack in the housing
Power and drive
The master toggle is a convenience power switch, not a safety-rated stop.
Wiring
Draft wiring diagram · 12 V in through the toggle to the PWM controller, which sets the gearmotor speed
Design decisions
Kept a right-angle worm gearmotor because it matches the mechanism. An axial motor would mean redesigning the enclosure.
The rotor gets positive magnet retention, a cap, strap, or cross-pin. Press fit or glue alone isn't accepted near a finger.
Direct drive is only for the small magnet. A 20 lb magnet on a 3 mm gearbox shaft would load the bushings and shake, so it's a separate, bearing-supported configuration.
Found that the exported toggle-body STEP was an open shell even after the STL was healed, so the solid gets rebuilt before release.
Next: test plan
Variable
Levels
Measured
Loaded shaft speed
40 · 70 · 100 · 130 · max rpm
Optical tach or frame-counted video
Magnet-to-nail gap
2 · 3 · 4 · 5 mm
Result photos under fixed lighting, 3 reps each
Health
Every run
Current, motor and controller temperature, runout, vibration
The operating speed will come out of this DOE, not out of forum posts.
Status
Built to this design. Not yet tested; results go here once the DOE runs.