Moonshot America - America 250th Series
The following was written by Spartan Forge CEO, Bill Thompson
The Moon is 238,855 miles from Earth, on average. A quarter million miles of vacuum, radiation, and silence separates this planet from another world. No atmosphere on arrival. No GPS. No rescue if something goes wrong. No second chances.
On July 16, 1969, at 9:32 in the morning, three American men sat inside a capsule atop a rocket and waited to go.
They got there.
The story of how that happened — the people, decisions, technology, near-disasters, and genius running through all of it — is one of the defining stories of the American experiment. Not because it was only a government achievement, but because it was a human one, produced by a culture that was competitive, improvisational, technically rigorous, and philosophically free.
The Declaration and the Deadline
On September 12, 1962, President John F. Kennedy stood before 35,000 people at Rice University and gave Kennedy’s Rice University address, the speech that set the mission in motion.
“We choose to go to the Moon in this decade and do the other things, not because they are easy, but because they are hard.”
There was no rocket capable of reaching the Moon. There was no spacecraft designed to land on it. There was no computer small enough to guide it, no software that knew how to navigate between worlds, and no complete plan for what to do when — not if — something failed in the void between here and there.
Kennedy was making a bet on the character of the American people. He understood something fundamental about the free market of ideas: it works fastest when the stakes are highest and the problem is hardest.
He was right.
The Scale of the Work
The Apollo program cost roughly $25 billion and, at its peak, employed 400,000 Americans with support from more than 20,000 industrial firms and universities.
That number matters. It represents programmers and welders, machinists and inspectors, mathematicians and technicians, and the woman at a small firm in New England welding a single component that would sit inside a fuel system aboard a rocket almost no one outside the program had ever seen. Each of them owned a piece of the mission.
Almost none of the actual work was done by government alone. Boeing built the first stage of the Saturn V. North American Aviation built the command and service module. Grumman built the lunar module. MIT’s Instrumentation Laboratory wrote the flight software. Rocketdyne built the engines. The government set the goal, held the contracts, and provided the funding. American industry and American universities provided the solution.
That is the free market of ideas. And it landed humans on the Moon.
The Saturn V
Before we talk about navigation and Mission Control, we have to talk about the rocket.
The Saturn V stood 363 feet tall. Fully fueled, it weighed 6.5 million pounds. Its five Saturn V’s F-1 engines generated a combined 7.5 million pounds of thrust at launch. The sound was not just audible. It was physical.
It flew thirteen times between 1967 and 1973. It never failed to reach orbit.
The first test of the complete three-stage Saturn V, Apollo 4, was an all-up test: no conservative, sequential buildup. Test the whole vehicle at once. It worked. That decision — trust your engineers, test at full scale, move fast — was not a bureaucratic instinct. It was an engineering culture instinct.
The Computer That Went to the Moon
In 1960, the term “software engineer” had not been coined. The field had not really been named.
A young MIT mathematician named Margaret Hamilton was recruited to write code for the Apollo Guidance Computer. She would eventually lead the team that developed the onboard flight software for Apollo. The work was not simply programming. It was engineering. It required the same rigor, discipline, and accountability as any physical system.
The Apollo Guidance Computer was built around silicon integrated circuits and had a fraction of the memory of even the simplest modern device. Yet it could guide a spacecraft from Earth orbit to the lunar surface and back again, manage thrusters, interpret astronaut inputs, and prioritize tasks under extreme resource limits.
That was not a minor engineering accomplishment. It was one of the most remarkable feats of applied intelligence in human history.
Three Minutes from the Moon
July 20, 1969. The Eagle, Apollo 11’s lunar module, is in powered descent, 50,000 feet above the surface of the Moon and dropping.
Then the computer throws an alarm.
The 1202 alarm meant program overflow: the computer was being asked to do more than it could handle at once. The rendezvous radar had been left active and was eating computing cycles. In most circumstances, that kind of alarm could have forced an abort.
Flight Director Gene Kranz turned to guidance officer Steve Bales. Bales called to the backroom, where a 24-year-old NASA engineer named Jack Garman had studied the alarm codes. Garman knew the computer was dumping low-priority tasks to protect the critical navigation functions. The guidance system was still working. The descent was still controlled. The alarm was not failure. It was the software doing its job under pressure.
His answer came back in seconds: “We are go.”
The 1202 alarm triggered four more times on the way down. Each time, the answer held.
At 4:17 p.m. Eastern time, the Eagle landed in the Sea of Tranquility with roughly 25 seconds of descent fuel remaining.
“Houston, Tranquility Base here. The Eagle has landed.”
The lesson is not just technical. It is cultural. A young engineer’s judgment, made possible by Kranz’s Mission Control culture and Hamilton’s software architecture, helped keep the mission alive. The hierarchy trusted the expert at the edge of the system.
That is not how rigid bureaucracies work. That is how the free market of ideas works under extreme conditions.
Mission Control
No story of Apollo is complete without Gene Kranz and the culture of Mission Control.
Kranz served as flight director for Apollo 5, 7, 9, 11, 13, 15, and 17. He built his team around competence, preparation, and accountability. Every flight controller owned his system completely. The guidance officer owned guidance. The flight surgeon owned the crew’s biomedical data. Nobody waited for someone else to diagnose a problem in his domain.
Kranz made the final call, but that call was only as good as the intelligence his team gave him.
“Failure is not an option” was not a slogan. It was a doctrine: identify every failure mode you can imagine before launch, plan for it, and when something happens that no one imagined, improvise, trust your people, and do not stop.
Apollo 13
On April 13, 1970, 200,000 miles from Earth, an oxygen tank in the Apollo 13 service module exploded. The command module lost two of its three fuel cells. Oxygen, electrical power, water, and heat all became survival problems at once. NASA’s Apollo 13 mission details remain one of the clearest records of engineering under impossible conditions.
The crew moved into the lunar module, which had been designed to support two people for 45 hours. It now had to support three people for roughly 90.
Power was rationed. The spacecraft grew bitterly cold. Water was restricted. Then carbon dioxide became the next crisis. The lunar module’s scrubbers were round. The command module’s spare canisters were square. In Mission Control, engineers gathered the materials available aboard the spacecraft — plastic bags, cardboard, and duct tape — built a makeshift adapter on the ground, and talked the crew through building the same device in space.
It worked.
With the star tracker blocked by debris, the crew used the sun as a navigational reference. Before re-entry, Mission Control wrote a new command module power-up procedure in three days.
On April 17, 1970, Jim Lovell, Jack Swigert, and Fred Haise splashed down in the Pacific Ocean. All three were alive.
NASA called Apollo 13 a “successful failure.” The mission failed to land on the Moon. It succeeded at bringing three men home against odds that should not have permitted it.
Apollo 8 and the World
On Christmas Eve 1968, Apollo 8 became the first crewed spacecraft to orbit the Moon. During a live Apollo 8 Christmas Eve broadcast, Frank Borman, Jim Lovell, and Bill Anders read from Genesis while circling another world.
One in four people on Earth was watching or listening. The Apollo 8 Genesis reading became one of the most-watched broadcasts in human history.
The choice to read from Genesis was not casual. The suggestion came from Christine Laitin, who as a teenager had been a member of the French Resistance during the Nazi occupation of Paris. The idea traveled from a young French girl risking her life under occupation, through decades of time, to three American astronauts reading the opening verses of civilization from the orbit of the Moon.
That is, in its own way, a story about what the American experiment connects to: courage, endurance, faith, and the human instinct to reach beyond the known world.
What It Means, 250 Years In
Here is what the Moon landing proves about the American experiment.
The Founders built a system that trusts the individual. It assumes that free people, given purpose, competition, responsibility, and the room to solve hard problems, will exceed the ambitions of any centralized authority. The Apollo program was that thesis at maximum resolution.
A 24-year-old engineer was trusted to keep a lunar module flying. A young mathematician helped define a discipline because she refused to accept that software was anything less than engineering. A flight director built a culture where the right answer mattered more than rank.
None of them were told to be extraordinary. They just were.
At Spartan Forge, the people who fly by night, navigate by landmarks, and carry American-made gear into terrain where second chances do not exist are heirs to this same culture. Mission discipline, terrain awareness, navigation precision, and refusal to quit are not limited to spaceflight. They distinguish excellence in any high-stakes human endeavor.
The forge is still churning. The footprints are still there.
Two hundred and fifty years into this experiment, the Moon still holds the tracks of two American men and the shadow of the plaque they left behind.
“We came in peace for all mankind.”
That sentence is true. But it was not inevitable. It was earned by engineers who worked through the night, by flight controllers who rewrote procedures in three days, and by workers who stayed on the line for the second and third shift.
This is for them.
Sources & Further Reading
· John F. Kennedy Presidential Library and Museum — Address at Rice University
· NASA — The First Step: Langley’s Contributions to Apollo
· Smithsonian National Air and Space Museum — F-1 Rocket Engine
· NASA — Apollo Program History
· Smithsonian National Air and Space Museum — Apollo Guidance Computer and the First Silicon Chips
· MIT News / CBS Boston — Margaret Hamilton and Apollo Software
· WeHackTheMoon — Jack Garman and the Apollo 11 Alarms
· Smithsonian National Air and Space Museum — Eugene “Gene” Kranz
· NASA — Apollo 13 Mission Details
