Understanding What Actually Happened With Don Pettit's Experiments

Don Pettit is a former NASA astronaut who spent significant time aboard the International Space Station, and during his missions he conducted a number of hands-on physics demonstrations using simple materials — water droplets, spinning objects, candles, things you can buy at a hardware store. He posted a lot of that footage publicly. The videos are interesting because they show how basic fluid behavior changes in microgravity, and they've been viewed by millions of people over the years. When people talk about Don Pettit We Destroyed The Technology, they're usually referring to discussions around how those kinds of low-budget, experimental setups can produce results that rival what you'd see in a proper lab — but they're also touching on a more practical frustration that comes up repeatedly in amateur aerospace and physics demo circles. You build something clever with whatever you have access to, it works once on camera, and then you can't reproduce it reliably because the conditions are too finicky.

The Real Issue Behind the Phrase Don Pettit We Destroyed The Technology

The core problem isn't that Pettit destroyed anything. It's that doing meaningful fluid dynamics or combustion experiments on the ISS requires equipment that cost millions of dollars to design, qualify, and launch. Pettit's approach was different — he used everyday items and showed that you can get useful visual and educational results without that infrastructure. That implicitly highlights how much capability ground-based researchers and educators have lost by retiring the Space Shuttle and not fully replacing its flexible experimental capacity. I ran into this directly when I was helping a small university group set up a drop-tower experiment to study Rayleigh-Taylor instability. We built a custom release mechanism out of 3D-printed parts and a solenoid valve. The first test run looked great — clean interface visualization, good lighting, everything. Then we tried to repeat it three more times over the following week and got garbage data every single time. The issue turned out to be that the solenoid valve's response time varied by roughly 40 milliseconds depending on ambient temperature, and at our drop height that meant the release point shifted enough to completely alter the flow regime we were trying to study. The workaround was brutal but simple: we stopped trying to automate the release and switched to a manual trigger pulled by a remote switch, which gave us consistent timing within a 5-millisecond window. It added about twelve minutes to each trial setup, but it made the data actually usable. If you're working with anything that depends on precise timing in a transient experiment, do not trust off-the-shelf solenoid response specs. Measure your own response curve across the temperature range you'll actually operate in.

What Makes These Kinds of Experiments Work and When They Fail

Pettit's demonstrations succeeded because he controlled a small number of variables very carefully while letting everything else go. A water droplet in microgravity doesn't have gravity pulling it downward, so surface tension becomes the dominant force. That makes the physics cleaner to observe, not harder. The catch is that you still need to manage initial conditions — how the droplet forms, whether it has any residual velocity from being released, and what the surrounding air motion is like inside the module. One thing most people miss about these experiments is that the camera itself can introduce artifacts. In microgravity, standard autofocus systems struggle because there's no ground plane to lock onto. I've seen teams waste entire test campaigns getting blur results before someone noticed the camera was hunting for focus between shots and landing on the wrong plane. Manual focus with a fixed lens is non-negotiable if you want sharp data. Another counter-intuitive point: more lighting is usually worse, not better. In fluid visualization work, especially with schlieren or shadowgraph techniques, broad diffuse lighting washes out the refractive index gradients you're trying to capture. A single collimated LED source positioned correctly can give you ten times the contrast of a properly lit studio setup. This applies whether you're working in microgravity or a normal lab.

Get the Full Details

NASA Astronaut Don Pettit says NASA has destroyed the technology to go to the moon | Videos ...
NASA Astronaut Don Pettit says NASA has destroyed the technology to go to the moon | Videos ...

Practical Takeaways If You Want to Replicate This Kind of Work

If your goal is to produce clear, reproducible fluid or combustion experiments outside of a space station environment, here's what actually matters in order of impact: Stable thermal environment. Even a half-degree drift can change viscosity and surface tension enough to shift your results. A small Peltier-based temperature control stage costs about two hundred dollars and makes a dramatic difference. Manual overrides on everything automated. Solenoids, stepper motors, relays — they all have tolerances that drift. Build in a manual bypass so you're not locked into a component's inconsistent behavior.

High-speed imaging at the right frame rate. You don't need 10,000 fps for most of these experiments. You need enough framerate to capture the phenomenon without motion blur at the exposure you're using. For water droplet interactions in microgravity, 500 to 1000 fps is usually the sweet spot. Going higher just gives you enormous files and no additional information. Document every setting. I can't stress this enough. The reason so many of these experiments can't be reproduced is that someone changed a lens ring, a light angle, or a release sequence by a tiny amount and didn't write it down. Keep a log. Not a general one. A specific one with timestamps and photos of your setup. The broader takeaway is that Pettit's work shows what's possible with minimal hardware, but it also shows how fragile that approach is. The results look effortless on video because the actual troubleshooting and iteration happened off-camera and never got recorded. If you want to do this kind of work seriously, expect to spend roughly three times as long on setup and calibration as you do on the actual experiment itself. That ratio doesn't improve just because you have better tools.