Liftoff
Inside the space race revolution
Description
On a remote coral atoll in the Pacific called Omelek, part of the Kwajalein chain in the Marshall Islands, a small group of engineers spent the mid-2000s trying to launch a rocket most of the aerospace world assumed would never fly. The island was barely six acres. Equipment arrived by boat and got eaten by salt air. The team slept in bunk rooms, drank warm beer after failed test firings, and rebuilt hardware with parts flown in from a warehouse in California. The rocket was called Falcon 1, and the company behind it, SpaceX, was less than five years old and burning through the personal fortune of a founder who had made his money on the internet.
Eric Berger, a veteran space journalist, tells this story in Liftoff, and it is not the polished origin myth that gets repeated at conferences. It is the version with the failed launches, the flooded electronics, the engineers who quit, the ones who cried, and the very real moment when the company had money for exactly one more try. Three of the first Falcon 1 launches ended in failure. The fourth would decide whether SpaceX survived at all. Berger reconstructs those years from the inside, through the people who lived on the island and in the factory, before anyone knew how the story ended.
What makes the account worth reading is that it treats the early SpaceX not as an inevitability but as a near-miss — a company that came within one launch of vanishing, run by people who had no guarantee any of it would work. The rocket that eventually reached orbit in 2008 was small, cheap by the standards of the industry, and largely unnoticed by the public. But it changed what a private company was believed capable of building.
The question we’re asking : How did a startup with almost no institutional experience build an orbital rocket from scratch, and what did it cost the people who did it?What we’ll see : The years on Omelek, the engineering gambles, the failures that nearly ended everything, and what the whole episode reveals about how hardware breakthroughs really happen.
Table of contents
01Chapter 1 — Four rockets and a running clock
SpaceX was founded in 2002 with a deceptively simple premise: rockets were absurdly expensive, and much of that expense came from how the established industry did business rather than from physics. Elon Musk had made a fortune from PayPal and decided to spend a large chunk of it proving that a small team could build an orbital rocket for a fraction of the going rate. The plan was Falcon 1 — a two-stage vehicle small enough to be affordable, big enough to matter. Berger's book is essentially the story of that single rocket, from the first hire to the launch that finally worked.
The early team was small and deliberately unconventional. Musk recruited engineers who were young, hungry, and willing to work brutal hours, and he mixed them with a few veterans who knew how rockets actually behaved. Tom Mueller, a propulsion engineer who had built engines as a hobby, became the man responsible for the thing that would either carry the company or sink it. The culture was fast and unforgiving: build, test, break, fix, repeat. Where the traditional aerospace world ran on paperwork and layers of review, SpaceX ran on the belief that you learn more from flying hardware than from analyzing it endlessly on paper.
02Chapter 2 — The engine that had never been done
The heart of Falcon 1 was the Merlin engine, and Berger spends real time on it because it was the hardest problem the company faced. Building a rocket engine from scratch is one of the least forgiving tasks in engineering. The machine has to survive temperatures and pressures that destroy most materials, burn thousands of pounds of propellant in seconds, and do it without tearing itself apart. Established manufacturers had spent decades and enormous sums refining their engines. SpaceX intended to design one in a few years with a team that could fit in a conference room.
Tom Mueller led the effort, and the book portrays him as the sort of engineer who understood engines in his bones. But intuition only went so far. The Merlin went through repeated test failures — combustion instability, hardware that cracked, components that behaved on the stand differently from how the models predicted. Each failure meant tearing down, diagnosing, and rebuilding, often under the knowledge that the clock was running and the money was finite. Berger captures the grind of it: the long nights in Texas at the test site, the smell of scorched metal, the small victories that felt enormous.
03Chapter 3 — A speck of aluminum, and the launch that finally worked
The first Falcon 1 launch, in March 2006, failed shortly after liftoff. A fuel line fitting had corroded in the salt air and leaked, and the rocket caught fire and fell back near the island. It was a devastating result after years of work, and Berger does not soften it. The second attempt, in 2007, flew far better but the rocket began to oscillate and the flight ended before reaching orbit. The third, in 2008, failed when the first and second stages collided during separation — a subtle timing problem caused by a change in the engine. Three attempts, three failures, and by now the money was nearly gone.
The details of the third failure are the kind Berger excels at. A residual thrust in the upgraded engine, a matter of a moment, caused the stages to bump after separation. It was the sort of error that looks obvious in hindsight and was invisible until it happened. The team on Omelek watched years of effort end again, and the mood, as Berger describes it, was close to despair. The company had, by most accounts, resources for a single further attempt. If the fourth launch failed, SpaceX would very likely fold, and the wider verdict that private startups could not build orbital rockets would stand confirmed.
04Chapter 4 — When a company becomes a bet on one person
Read at a distance, the Falcon 1 story says something uncomfortable about how genuine hardware breakthroughs happen. They do not emerge from consensus or from careful, distributed decision-making. Berger's account shows a company that succeeded precisely because it was willing to do what large institutions cannot: concentrate risk, tolerate public failure, and keep flying hardware that the cautious playbook would have grounded. The speed that let SpaceX iterate faster than the incumbents was the same speed that produced three failed launches on a global stage.
That model depended almost entirely on one person's willingness to keep funding it. Berger is clear-eyed about this. The company survived because Musk kept writing checks and refused to stop even as the money ran low and the failures mounted. This is the strength of the founder-driven approach and also its fragility. A traditional aerospace program spreads its risk across committees, contractors, and government budgets, and it moves slowly as a result. SpaceX collapsed all of that into a single decision-maker who could absorb catastrophic risk and act on conviction rather than consensus. It worked. It also meant the entire enterprise rested on the resolve and resources of one individual, which is not a repeatable formula so much as a specific circumstance.
05Conclusion
The fourth Falcon 1 reached orbit in September 2008 with a team that was worn down, nearly broke, and unsure until the last minutes whether any of it would hold together. The rocket carried no famous payload and made few headlines. But it settled a question the aerospace world had answered confidently in the negative: whether a private startup could build an orbital rocket from nothing. Berger's achievement in Liftoff is to put us back on that coral island before the answer was known, among people who had staked years of their lives on a machine that kept failing.