Team Moon: How 400,000 People Landed Apollo 11 on the Moon

Team Moon: How 400,000 People Landed Apollo 11 on the Moon

by Catherine Thimmesh

Narrated by Andy Paris

Unabridged — 1 hours, 39 minutes

Team Moon: How 400,000 People Landed Apollo 11 on the Moon

Team Moon: How 400,000 People Landed Apollo 11 on the Moon

by Catherine Thimmesh

Narrated by Andy Paris

Unabridged — 1 hours, 39 minutes

Audiobook (Digital)

$8.99
FREE With a B&N Audiobooks Subscription | Cancel Anytime
$0.00

Free with a B&N Audiobooks Subscription | Cancel Anytime

START FREE TRIAL

Already Subscribed? 

Sign in to Your BN.com Account


Listen on the free Barnes & Noble NOOK app


Related collections and offers

FREE

with a B&N Audiobooks Subscription

Or Pay $8.99

Overview

When three heroic men traveled aboard the Apollo 11 spacecraft bound for the moon, the entire world sat glued to their television sets in suspense. But few knew just how much it took to get that far. To put a man on the moon, thousands of people diligently worked behind the scenes. Countless preparations had to be made and no detail, however small, could be overlooked-the lives of the crewmen were at stake. From the seamstresses who wove the multi-layered materials for the spacesuits, to the computer experts who designed and tested the flight software, the combined efforts of many little-known heroes helped make this monumental endeavor a success. Based on NASA transcripts and national archives, this 2007 ALA Best Book for Young Adults by Catherine Thimmesh received starred reviews from both Publishers Weekly and Kirkus Reviews. Narrator Andy Paris lends her talents to this triumphant story of the race to the moon. "This beautiful and well-documented tribute will introduce a new generation to that triumphant time."-Kirkus Reviews, starred review

Editorial Reviews

Publishers Weekly

This behind-the-scenes look at the first Apollo moon landing has the feel of a public television documentary in its breadth and detail.The book opens with several photographs of people huddled around TVs to view the event (one shows Italians watching a small set at an outdoor cafe). The author then delves into the back story of the organizations and hundreds of thousands of people who made the 1969 mission possible. Readers meet 24-year-old "computer whiz kid Jack Garman," who helped work through worrisome computer glitches during the Eagle's landing, as well as one of the seamstresses who sewed the spacesuits ("We didn't worry too much until the guys on the moon started jumping up and down. And that gave us a little bit of an eyebrow twitch"). The 16 chapter-like segments flow chronologically, from John F. Kennedy's 1961 speech to Apollo 11's splashdown. Thimmesh (Madame President) peppers her lengthy, fact-filled narrative with folksy adages (e.g., "Here they were, less than 500 feet from the moon, and just about plumb out of fuel"). The colloquialisms sometime seem at odds with the myriad of engineering acronyms and jargon. But the author maintains a conversational tone, and tackles and explains tough topics such as "cluster interference" in parachute deployment and a bit of the chemistry behind developing the astronauts' dramatic photographs, many of which illustrate the story. Even if the jargon gives readers pause, the little-known facts will keep their interest level high. Ages 9-up. (June) Copyright 2006 Reed Business Information.

School Library Journal

Gr 5 Up-In infectiously hyperbolic prose that's liberally interspersed with quotes and accompanied by sheaves of period photos, Thimmesh retraces the course of the space mission that landed "an actual man, on the actual Moon." It's an oft-told tale, but the author tells it from the point of view not of astronauts or general observers, but of some of the 17,000 behind-the-scenes workers at Kennedy Space Center, the 7500 Grumman employees who built the lunar module, the 500 designers and seamstresses who actually constructed the space suits, and other low-profile contributors who made the historic flight possible. Despite occasional contrast issues when the white-on-black text is printed over blown-up photographs, this dramatic account will mesmerize even readers already familiar with the event-and also leave them awed by the level of care and dedication it took to surmount so many daunting technological challenges. Drawn from personal interviews and oral histories as well as a wide array of published sources, this stirring, authoritative tribute to the collective effort that left "...footprints, crisp and clear, pressed purposefully and magnificently into the lunar dust" belongs in every collection.-John Peters, New York Public Library Copyright 2006 Reed Business Information.

Kirkus Reviews

"For me, that was the time in history and the event to participate in above all others." That comment, from one of the 400,000 involved in the team effort to put men on the moon in 1969, sums up the essence of this dramatic account of the work of people behind the scenes in the Apollo program. Illustrated with striking black-and-white photos, the white text on a black background of each page underscores the risk of this venture into the unknown. Beginning with Nixon's just-in-case prepared announcement of the astronaut's "sacrifice," the author presents the expedition as a series of challenges, including surprising details. Not all the challenges were directly related to the voyage: a windstorm in Australia threatened television transmission; photographs had to be perfect and the film disinfected (of nonexistent bacteria) before it was developed. The authors emphasizes the paper-and-pencil calculations, the endless testing and checking, and elaborate recordkeeping that supported this work, and the sense of personal responsibility each participant felt. This beautiful and well-documented tribute will introduce a new generation to that triumphant time. (author's note, resources, bibliography, glossary) (Nonfiction. 10+)

From the Publisher

Winner of the Robert F. Sibert Informational Book Award * "This behind-the-scenes look at the first Apollo moon landing has the feel of a public television documentary in its breadth and detail." —Publishers Weekly, starred review * "This beautiful and well-documented tribute will introduce a new generation to that triumphant time."  —Kirkus Reviews, starred review "This dramatic account will mesmerize even readers already familiar with the event-—and also leave them awed by the level of care and dedication it took to surmount so many daunting technological challenges."  —School Library Journal "Thimmesh gives names and voices to the army that got Neil Armstrong and company to the moon and back. The result is a spectacular and highly original addition to the literature of space exploration."  —Horn Book "Catherine Thimmesh tells us the stories of the 400,000 people it took to make...that 'one giant leap'...Their collective devotion to an exciting goal comes across strongly."  —Chicago Tribune * "Kids . . . probably feel they know quite a bit about the first manned moon landing. But until they've read Thimmesh's breathless behind-the-scenes account, they know zip."  —Bulletin, starred review "An edge-of-your-seat adventure . . . lavishly illustrated . . . this exhilarating book . . . will captivate."  —Chicago Sun-Times "So often in history, the actual participants get lost in the retelling of the story. But in Thimmesh's highly engaging book, Team Moon, the thousands of people responsible for landing man on the moon finally and deservedly get their due. This engrossing historical account is extremely timely; for it is today's children who will make up the team of tomorrow. These kids will be returning to the moon, privatizing space, and, as I hope, finally placing human footprints upon Martian soil. And as this remarkable book shows, it'll take astronauts — and a whole lot of others — to fuel the space exploration that is our future." —Buzz Aldrin, astronaut, Apollo 11, and moonwalker on the first lunar landing "Thimmesh's enthusiasm for her subject is palpable, and the sense of excitement she brings is as vital to Team Moon's success the book's very premise." —Chris Barton, author of Shark vs. Train An NCTE Orbis Pictus Honor Book AAAS/Subaru SB&F Prize for Excellence in Science Books An ALA Best Book for Young Adults An ALA Notable Children’s Book —

Product Details

BN ID: 2940170831111
Publisher: Recorded Books, LLC
Publication date: 03/20/2009
Edition description: Unabridged
Age Range: 10 - 13 Years

Read an Excerpt

CHAPTER 1

Beyond Imagination

It was mind-boggling. The television itself had been a flat-out miracle when it began to dominate the scene a mere twenty years previous. And now, that technological wonder of wonders was going to trump itself. Because very soon, if all went according to plan, it would transmit pictures of an actual man, on the actual moon. In 1969, on July 20 (in one part of the world) and July 21 (in the other part), half a billion people on the blue-marbled globe clicked on their TV sets — flush with anticipation — eager to watch as Apollo 11 would attempt to put man on the moon for the first time in all of history. The moon!

And now, at this defining moment, the world had come together — like nothing ever before — not only to wish the astronauts Godspeed, but to bear personal witness to this incredible event. On that day, people gathered: in homes and schools and businesses; in restaurants and shops; and on sidewalks and streets and in parks. They were eager to be a part, however small, of something so out-of-this-world big. If there was a TV in the vicinity, it was on. And people sat. And watched — wide-eyed, waiting.

"Fate has ordained that the men who went to the moon to explore in peace will stay on the moon to rest in peace. ... These brave men, Neil Armstrong and [Buzz] Aldrin, know that there is no hope for their recovery. But they also know there is hope for mankind in their sacrifice."

Rest in peace? On the moon? Thankfully, no; those ominous words (penned in top secret for President Nixon) were never spoken. But while millions upon millions of people were spellbound and starry-eyed with moon mania (sitting, watching, waiting), those people behind the scenes fretted over more problems and concerns and plans for emergencies than the rest of the world could ever know. The "Fate Has Ordained" speech was to be delivered in the event that the worst possible scenario came to pass. The speech's very existence proved that, beneath all the excitement, those people running the show never for a moment lost sight of the all too real dangers they were choosing to run into head-on. And though millions of eyes were focused front and center on the astronauts and the spacecraft, much of the action would, in fact, be taking place on the sidelines.

When those millions of people tuned in hoping to witness the moonwalk, one thing they wouldn't see (or at best might just catch a glimpse of) were the nonastronauts, those beyond the glare of the limelight. The regular folks whose efforts made an impossible mission possible in the first place. All the people behind the scenes whose ideas and expertise, imagination and inventiveness, dedication and focus, labor and skill, combined in one great endeavor — on the grandest of grand scales — and conspired to put man on the moon. Yes, three heroic men went to the moon; but it was a team of four hundred thousand people that put them there. They were the flight directors, controllers, planners, and engineers; the rocket designers and builders and technicians; the managers, supervisors, quality control and safety inspectors; the programmers, electricians, welders, seamstresses, gluers, painters, doctors, geologists, scientists, trainers, and navigators ...

Apollo 11 is their story too.

CHAPTER 2

In the Beginning ...

They were going to the moon, all right — at least that was the plan. That was the dream and the challenge set forth by one man, President John F. Kennedy, when he declared in May of 1961:

"I believe this nation should commit itself to achieving the goal, before this decade is out, of landing a man on the Moon and returning him safely to Earth."

So they came by the thousands — kids really, twenty-somethings, a few in their thirties. No one knew for sure how to get to the moon, how to land, or get home. But their goal was clear-cut, and that was enough. That gave them purpose: a reason to puzzle out the problems and seek solutions rather than sleep.

Kennedy's decision was triggered by an intense "space race" with the old Soviet Union. The Soviets were first in space (with Sputnik); first too with a man in space. But for those who actually worked on the moon shot, the "race" became an afterthought. They were fueled instead by a desire to explore the heavens — the poetry of it all, the scientific challenge of it all, the "We're going to the moon!" excitement of it all.

But the moon? Could it really be done? Right from the getgo, administrators had identified ten thousand individual tasks that would have to be completed. And that was only the beginning. So much to do. Too much? An aide to Kennedy quietly predicted that it would take forty-four attempts. Forty-four tries before ever landing once on the great gray rock in the sky.

CHAPTER 3

Moving Forward ...

The final picture was altogether different from the dream. Most thought they'd be going straight to the moon with one spacecraft, land, and come straight back. Instead, as the plan evolved, it called for two very different craft: a command and service module for flight and a lunar module (LM) to land on the surface. No one ever imagined landing on the moon in a seatless, gold-foil-encased, four-legged, spidery-ish thingamajig nicknamed the "LEM." After all, no one knew what a lunar module was even supposed to look like. And so, form followed function. Never mind if it looked like a bug.

"I can't say that I'm aware of any program where more people understood what the schedule was, how important it was, and worked so hard to make it happen. We had a great team," recalled Joe Gavin, vice president of the Grumman Aerospace Corporation, contractor for the lunar module.

That team at Grumman was 7,500 workers strong. They designed, developed, and built the lunar module, christened Eagle for Apollo 11, from the ground up. Reliability was insisted upon. They had a motto: There is no such thing as a random failure. And failures were eliminated — one by one. Because it was their baby, their handiwork — eight years of their lives — that, very soon, would settle down (fingers crossed) on that giant glowing ball in the inky-black soup of space.

CHAPTER 4

And Onward ...

Space ... it's dangerous out there: micrometeoroids, radiation, airlessness. And coming home would be no picnic either. The compact-car-size space capsule would be greeted and surrounded by searing white-hot flames as it slammed madly back down to Earth.

"In designing the command module, the one thing we had to be sure of was that we could keep the crew alivethat was a big item," said Max Faget, NASA chief engineer and principal designer of the command module.

Keeping the crew alive under such extreme conditions was indeed a big item. Only the command module, Columbia, would make the complete journey from Earth to the moon and back home again. It would serve as crew living quarters and as the spacecraft control center. And Columbia alone would confront the fiery Earth reentry.

But the wizards at North American Rockwell (NASA's prime contractor for the command module) were up to the challenge. Fourteen thousand folks there, plus a skilled hodgepodge of eight thousand other companies, toiled to ensure that millions of components on the command module were in top-notch order.

Columbia was off to confront danger. Its builders would need to rely on their eight years of effort to give them confidence for a successful outcome. But it would be five hundred thousand miles before the truth of the matter would be told. Could their command module keep the crew alive?

CHAPTER 5

And Upward ...

Launch operations at Kennedy Space Center (KSC) in Florida was like its own little town. A whopping seventeen thousand engineers, technicians, mechanics, contractors, and managers were needed to pull together the Apollo 11 launch. Needed to check, check, check the spacecraft: test it, stack the three rocket stages in the vehicle assembly building, or VAB, roll it out, recheck it, fuel it, and ready it for liftoff.

One of the most critical preparations for launch was the orchestration and performance of the crucial CDDT.

"The Countdown Demonstration Test, or CDDT, gives us confidence that we're going to get there in time and everything's going to percolate [work perfectly] together," explained Ernie Reyes, chief of the Pre-flight Operations Branch for Apollo 11. "It's a dress rehearsal for the countdown. The only thing we don't do, is we don't load the vehicle with all its fluids and juices [rocket fuel]."

Come launch day, Ernie Reyes and about five hundred others would work the consoles from the Firing Room of the Launch Control Center (LCC), the nucleus of launch operations. They would run the controls that would catapult Apollo 11 moonward bound. Five thousand others would directly support them for the actual liftoff.

It was a long, long march to that day, and the little town of KSC became a second home to quite a few folks. Many a lunch — dinners, anniversaries, birthdays — were forsaken in pursuit of Ready to Launch. On July 16, 1969, they were indeed ready. And at 9:32 A.M.... whoosh!

CHAPTER 6

Maiden Voyage ... The Final 10 Miles

"The Eagle has wings!" radioed Neil Armstrong from the lunar module as he and Buzz Aldrin flew sixty-nine miles above the moon. Four words. Slightly cryptic, but oh so lyrical. There was no doubt of their meaning: The lunar module Eagle had separated from the command module Columbia and was now flying solo. It was ready to descend to the surface of the moon. Magical words, those four. Big smiles back on Earth, back in Houston, at Mission Control.

In Houston, the White Team was at the consoles in the control room monitoring and facilitating the moon landing. Gene Kranz was the flight director on duty — the person in charge of the mission during that time and responsible for the final decisions. He had arrived at the Mission Control complex (MCC) shortly past dawn, accepting the good lucks that were tossed his way by those he passed in the lobby. He refused the elevator, instead climbed three flights of stairs to the MOCR (Mission Operations Control Room, pronounced MOE-ker). They were attempting to put man on the moon today — a dazzling technological triumph — but at home, technology had a habit of getting stuck between floors, and Flight Director Kranz was taking no chances. "Today is not the day to get stuck in an elevator," he wrote in his memoir.

Forty minutes prior to beginning the landing sequences, Kranz addressed his flight controllers:

"In the next hour we will do something that has never been done before. We worked long hours and had some tough times but we have mastered our work. Now we are going to make this work pay off. You are a hell of a good team. One that I feel privileged to lead. Whatever happens, I will stand behind every call that you will make."

It was time. As instructed by Mission Control in Houston, astronauts Neil Armstrong and Buzz Aldrin fired their descent rocket engine, lowering the Eagle to an altitude of just 50,000 feet above the moon's surface. (On an earlier mission, several months previous, Apollo 10 had gotten to this very point — 50,000 feet — close, but still so far.) But now, for the first time, Neil and Buzz would go that last leg — the final ten miles.

"You are Go for PDI [powered descent ignition,"] Mission Control radioed the crew.

Never had more monumental words been spoken so simply: The green light was given to go ahead and land on the moon. Twelve minutes, now. And they would be on the surface of the moon. Or not.

CHAPTER 7

Challenge 1: Alarms

BAM! Suddenly, the master alarm in the lunar module rang out for attention with all the racket of a fire bell going off in a broom closet. "Program alarm," astronaut Neil Armstrong called out from the LM ("LEM") in a clipped but calm voice. "It's a 'twelve-oh-two.'"

"1202," repeated astronaut Buzz Aldrin. They were 33,500 feet from the moon.

Translation: We have a problem! What is it? Do we land? Do we abort? Are we in danger? Are we blowing up? Tell us what to do. Hurry!

In Mission Control, the words TWELVE OH TWO tumbled out of the communications loop. The weight of the problem landed with a thud in the lap of twenty-six-year-old Steve Bales. Bales, call name GUIDO, was the mission controller for guidance and navigation.

A moment earlier (after some worries with navigation problems), Bales had relaxed with a deep breath, thinking at last: We're going to make it. Now, wham! His mind, again sent racing; his blood rushing; his heart fluttering; his breath — still as stone. But he wasn't alone.

A voice on another loop — belonging to one of Bales's backroom support guys, twenty-four-year-old computer whiz kid Jack Garman — burst in to make sure Bales was aware of the 1202. A quick glance at a master list told them a 1202 was executive overflow. Simply put, the computer had too much to do. But program alarms, as Garman knew firsthand, were built into the computer solely to test the software. By their very definition, they weren't alarms that should happen in flight. (During development, these alarms were testing computing cycles.)

Yet there it was: 1202. An unreal reality. First, stunned inactivity at Steve Bales's console.

Then, a bombardment of thoughts: What's the problem? Do they land? Do they abort? Are they in danger? Are they blowing up? Tell them what to do. Hurry!

Bales scoured his guidance and navigation data.

Searching. Sifting. Sorting.

Flight Director Kranz plucked details from a flood of incoming information.

Juggling. Judging.

Backroom guy Jack Garman (call name AGC) consulted his handwritten program alarm list, mandated by Gene Kranz (and neatly stashed beneath the Plexiglas on his console).

CapCom Charlie Duke (or Capsule Communicator, the voice link between Mission Control and the spacecraft) mused aloud: "It's the same one we had [in the simulator]."

And indeed, in one of the very last simulations, or practice sessions, before liftoff of Apollo 11, mission controllers found themselves stumped when faced with a similar program alarm. While training with the backup crew, SimSup Jay Honeycutt (or Simulation Supervisor) had asked software expert Jack Garman to concoct some sort of computer glitch for the controllers to solve. So Garman remembered the hidden software testing alarms and threw out one of those. It wasn't a 1202, but a similar type — one that supposedly should never happen in actual flight (because the situations that would trigger those alarms had presumably already been removed from the software).

During that simulation, that test, GUIDO Steve Bales had called for an abort — an immediate end to the landing. They stopped the pretend-land on the moon. But it was the wrong call. While the computer was definitely having difficulties, it would still have been safe to continue the landing because the LM's critical functions were still working.

"And so [Flight Director] Gene Kranz, who's the real hero of that situation, sat us all down and said, 'You WILL document every single program alarm, every single possible one that can happen' and what we should do about it if it happens," recalled AGC Jack Garman, explaining how they ended up with a written record of those "nonexistent" program alarms.

Sometimes, after the bugs have all been removed during development, programmers might go back in and remove all their testing alarms. But often, it's considerably more efficient (and cheaper) to just leave them buried unseen, deep down in the software.

"So I remember," continued Jack Garman, "going back to my little corner with my friends — my colleagues — and we wrote them all down. Wrote them on a sheet of paper (twenty or thirty of these alarms that were not supposed to happen), taped this list to a piece of cardboard, and stuck it underneath the Plexiglas on the console."

As they would discover later, though it seemed an impossible situation, it wasn't a false alarm. Executive overflow meant the computer was too busy. And the computer was too busy (it turned out) because a switch had been mistakenly left on.

"Give us a reading on the 1202 program alarm," said Armstrong from the lunar module as it continued its rapid — and very real — descent to the moon.

"The astronauts had no idea what these alarms were," explained Garman. "Absolutely no idea. These alarms were software development alarms. They'd never seen them. Never studied them. Never had them. No one in Mission Control knew what they were, not Kranz or anybody."

GUIDO Steve Bales determined the computer had not lost track of the LM's altitude or speed — critical for avoiding a lunar crash — and still had its guidance control, also essential. Flight Director Gene Kranz determined, with input from his controllers, that all other systems were functioning within acceptable parameters. AGC Jack Garman concluded that as long as the alarm didn't recur, they were okay.

Garman prompted GUIDO Steve Bales, who gave the "Go" to Flight Director Kranz, who in turn gave the command to CapCom Charlie Duke. CapCom relayed the message to Armstrong and Aldrin. "We are Go on that alarm," he told Neil and Buzz and the hundreds of others listening in on the loops. Not more than twenty seconds had passed from the time the 1202 was first called out.

"Program alarm!" Buzz responded from the LM. "Same one."

Garman clarified to Bales that as long as the alarm was not constant — not continuous — they were okay. The rest of Bales's information looked good. He told the Flight Director, "We're Go." Flight Director Kranz "went around the horn" — polling his controllers for their status reports — they were all "Go." Kranz told his voice link to the astronauts, "CapCom, we are Go for landing."

Aldrin acknowledged the good-to-Go. They were 3,000 feet from the moon now.

"Program alarm!" Buzz called. "1201."

"When it occurred again a few minutes later," Jack Garman recalled, "a different alarm but it was the same type ... I remember distinctly yelling — by this time yelling, you know, in the loop here —'SAME TYPE!' [in other words, Hang tight!] and he [GUIDOSteve Bales] yells 'SAME TYPE!' I could hear my voice echoing. Then the CapCom says, 'SAME TYPE!' Boom, boom, boom, going up."

(Continues…)


Excerpted from "Team Moon"
by .
Copyright © 2006 Catherine Thimmesh.
Excerpted by permission of Houghton Mifflin Harcourt Publishing Company.
All rights reserved. No part of this excerpt may be reproduced or reprinted without permission in writing from the publisher.
Excerpts are provided by Dial-A-Book Inc. solely for the personal use of visitors to this web site.

From the B&N Reads Blog

Customer Reviews