| I am probably closer to one of the "mini-cult of adherents who worship it with near-religious fervor" than I'd like to admit, but I make a kind of pilgrimage to sit under and stare at the F1 engine at my local museum every now and then. It's very much wormed into my consciousness _without_ any asbestos or foil wrapping: https://steelcityelectronics.com/2017/02/07/powerhouse-museu... (Not my pic, just one I found on DDG that fits with my memory of it) As a cultist, I recall a similar story to the Fogbank one about the fuel pumps for thoe F-1 motors. Apparently in spite of having all the docs, we still needed to reverse engineer them from museum pieces to find out how to build new ones: https://arstechnica.com/science/2013/04/how-nasa-brought-the... Why was NASA working with ancient engines instead of building a new F-1 or a full Saturn V? One urban legend holds that key "plans" or "blueprints" were disposed of long ago through carelessness or bureaucratic oversight. Nothing could be further from the truth; every scrap of documentation produced during Project Apollo, including the design documents for the Saturn V and the F-1 engines, remains on file. If re-creating the F-1 engine were simply a matter of cribbing from some 1960s blueprints, NASA would have already done so. A typical design document for something like the F-1, though, was produced under intense deadline pressure and lacked even the barest forms of computerized design aids. Such a document simply cannot tell the entire story of the hardware. Each F-1 engine was uniquely built by hand, and each has its own undocumented quirks. In addition, the design process used in the 1960s was necessarily iterative: engineers would design a component, fabricate it, test it, and see how it performed. Then they would modify the design, build the new version, and test it again. This would continue until the design was "good enough." Further, although the principles behind the F-1 are well known, some aspects of its operation simply weren't fully understood at the time. The thrust instability problem is a perfect example. As the F-1 was being built, early examples tended to explode on the test stand. Repeated testing revealed that the problem was caused by the burning plume of propellent rotating as it combusted in the nozzle. These rotations would increase in speed until they were happening thousands of times per second, causing violent oscillations in the thrust that eventually blew the engine apart. The problem could have derailed the Saturn program and jeopardized President Kennedy's Moon landing deadline, but engineers eventually used a set of stubby barriers (baffles) sticking up from the big hole-riddled plate that sprayed fuel and liquid oxygen into the combustion chamber (the "injector plate"). These baffles damped down the oscillation to acceptable levels, but no one knew if the exact layout was optimal. |
Now... most of my memory for rockets is from when I did space camp way back in the mid 90s. So... Yeah, I don't have picture perfect memory of that.
This just feels like when I'm told that CS majors don't learn about the involvement of women in computer science. By and large, that is not totally accurate. It is accurate enough for the point, which is that there is sexism. But, as the software person in the room that went to college, I was almost guaranteed to be the only one that knew the names of the women that our education supposedly skipped on.