Summary of Gene Kranz's Failure Is Not an Option , livre ebook

Everest Media LLC - Everest Media

Découvre YouScribe en t'inscrivant gratuitement

Je m'inscris

Obtenez un accès à la bibliothèque pour le consulter en ligne
En savoir plus

56 pages

English

Vous pourrez modifier la taille du texte de cet ouvrage

Obtenez un accès à la bibliothèque pour le consulter en ligne
En savoir plus

A propos
Informations
Extrait

Description

Please note: This is a companion version & not the original book.
Sample Book Insights:
#1 The human factor is what saves the crew of Apollo 13. It is what saves the crew of Apollo 13 when all the glittering technology seems useless.
#2 I was excited to be at the Cape Canaveral launch site, as I had been assigned to NASA to help with the American space program. I was shocked to see that the base looked like any other military base.
#3 I had never driven that fast on a military base in my life. I was thinking I had hitchhiked with a madman, or at least someone who had no concern about being pulled over by the Air Police for speeding and breaking every regulation in the book.
#4 The first orbiting satellite, Sputnik, was a shock to American pride. The reverberations of that little sphere were far-reaching. It sparked a massive federal education funding program, and the creation of the National Aeronautics and Space Administration.

Sujets

Science and technology

Informations

Publié par	Everest Media LLC
Date de parution	05 avril 2022
Nombre de lectures	0
EAN13	9781669377863
Langue	English
Poids de l'ouvrage	1 Mo

Informations légales : prix de location à la page 0,0150€. Cette information est donnée uniquement à titre indicatif conformément à la législation en vigueur.

Extrait

Insights on Gene Kranz's Failure Is Not an Option
Contents Insights from Chapter 1 Insights from Chapter 2 Insights from Chapter 3 Insights from Chapter 4 Insights from Chapter 5 Insights from Chapter 6 Insights from Chapter 7 Insights from Chapter 8 Insights from Chapter 9 Insights from Chapter 10 Insights from Chapter 11 Insights from Chapter 12 Insights from Chapter 13 Insights from Chapter 14 Insights from Chapter 15 Insights from Chapter 16 Insights from Chapter 17 Insights from Chapter 18 Insights from Chapter 19 Insights from Chapter 20 Insights from Chapter 21 Insights from Chapter 22
Insights from Chapter 1

#1

The human factor is what saves the crew of Apollo 13. It is what saves the crew of Apollo 13 when all the glittering technology seems useless.

#2

I was excited to be at the Cape Canaveral launch site, as I had been assigned to NASA to help with the American space program. I was shocked to see that the base looked like any other military base.

#3

I had never driven that fast on a military base in my life. I was thinking I had hitchhiked with a madman, or at least someone who had no concern about being pulled over by the Air Police for speeding and breaking every regulation in the book.

#4

The first orbiting satellite, Sputnik, was a shock to American pride. The reverberations of that little sphere were far-reaching. It sparked a massive federal education funding program, and the creation of the National Aeronautics and Space Administration.

#5

I was given the task of writing the manual for Mercury Control, which was the team that was in charge of the launch operations at the Cape. I was given this assignment mainly because I was available.

#6

I was assigned to Mercury Control, the team that was in charge of the launch countdown for the first American into space. It was a scary thought, but not for anyone who had been around test pilots.

#7

The first American rockets were barely adequate, and the communication network was run out of NASA’s Goddard Space Flight Center in Greenbelt, Maryland. The Cape facility that would become the Kennedy Space Center was beyond our wildest dreams in 1960.

#8

I had left behind a world where airplanes were flying at roughly five miles a minute. In this new, virtually uncharted world, we would be moving at five miles per second. During a mission countdown, or even a flight test, so many things would be happening so fast that you didn’t have any time for second thoughts or arguments.

#9

The launch process was extremely stressful, but I was starting to feel like I was getting the hang of it. The few days of hands-on familiarity with MCC systems had helped me understand the MCC team.

#10

I felt like I was finally feeling at home at the Mercury control room, with its three rows of pedestal-style consoles. The only instruments were a clock and an intercom panel with a rotary phone at the top.

#11

The tracking network voice system used a massive manual switchboard up at Goddard. The radar information from the launch, orbit, and reentry was transmitted by tracking sites around the world to the computers at Goddard for processing, and then sent down to Mercury Control.

#12

The first Mercury-Redstone launch, MR-1, was only eight days away when Kraft’s team arrived at the Cape. My guardian angel, Johnson, arrived to save my bacon. He took a place to the right of the console and punched up the buttons of the intercom during our dress rehearsal.

#13

I was assigned to be the MCC procedures controller for the first mission, a ballistic test of a Redstone booster rocket and a Mercury capsule. The Redstone’s engine was scheduled to burn for two and one half minutes. After the booster engine cut off, the escape tower separated from the capsule by firing the tower ring attachment bolts and igniting the tower escape rocket.

#14

The launch complex from which we would launch the Redstone consisted of the launch pad, service tower, and a blockhouse for launch site command and control. The blockhouse team was a mixture of German rocket scientists, former Army technicians, and booster contractors.

#15

The Russian program was powered by the virtually unrestricted resources and funding of a military command economy. President John F. Kennedy and Vice President Lyndon B. Johnson pushed for the funding and resources that would enable an explicitly civilian space program to succeed.

#16

I was at the procedures console one month and four days after I was hired. I had no problems with the mechanics, but I had a long way to go before I would have the sense of being ahead of the airplane or ahead of the power curve as pilots put it.

#17

When the escape tower cut loose, it flew to an altitude of about 4,000 feet. The launch team in the blockhouse was as stunned as Mercury Control. The Redstone rocket, surrounded by smoke, was armed and fueled but still sitting on the launch pad.

#18

The launch of the Redstone was a success, but the most embarrassing episode yet for the young engineers of the Mercury program. The history books call this mission The Four-Inch Flight.

#19

After only a few weeks of training, the controllers went to the most remote outposts, which were connected to Mercury Control by a communications system that was, in 1961, extremely brittle. The CapComs were all college graduates, and they were paired with systems monitors who had no more than two years’ experience working at the global satellite tracking stations.

#20

The tracking stations were often primitive corrugated steel buildings like the hootches I lived in while in Korea, and they were easily identified by their numerous antennas. The key sites were located at the points for the major Go NoGo decisions, and the locations of the deorbit maneuver.
Insights from Chapter 2

#1

The American public was caught up in the beauty pageant aspect of the first manned launch, which astronaut would be first.

#2

Following two successful Redstone launches, we moved on to the unmanned Atlas mission, which was designed to test the spacecraft and the global network. The mission that would follow was the first American into space.

#3

The simulation team was made up of another small group of controllers. Their task was to create what we now call virtual reality, and they did so by replicating every element of the mission, from countdown to completion.

#4

The final MA-3 training run was no exception. Our novices stumbled from the start, when the wrong tapes were selected. After several restarts, tempers flared as controllers at the separate sites began improvising in an attempt to complete the test.

#5

The destruction of the Mercury-Atlas 3 left us dazed and disheartened. We had gone to launch feeling that with three successful unmanned suborbital missions, the jinx seemed broken, the odds were turning in our favor. Then the Atlas had to be blown up.

#6

The failure of the Mercury program was a shock to the entire team, and they knew that it would mean more time away from their families. They were consumed with the goal of the successful flight of America’s first man in space.

#7

The flight rules that were a mystery in the beginning now anchored me at the center of the mission policy and decision process. They were an upscale equivalent of the Go NoGo criteria used in aircraft flight tests.

#8

The first manned launch was set for May 1, 1961, and the capsule servicing began as we conducted our final simulations. I slept poorly that night, as I had spent most of my time with the team at the Cape in unmanned rocket testing.

#9

The press was excited about the launch, and began to speculate who would be the first astronaut to fly in space. The control team, led by Shorty Powers, neither confirmed nor denied any of the press speculation.

#10

The first American astronaut, Alan Shepard, was ready to launch in May 1961. However, the weather was stormy at midnight, and the launch was canceled. Shepard shimmied out of his space suit and down a shot of brandy. The secret was out.

#11

The beverage of choice after the volleyball matches was Swan Lager, an Australian beer, and our supplier was Jack Dowling, the Australian government’s envoy to NASA.

#12

The space program produced a spirit that was able to respond to the challenge of John Kennedy’s inaugural address: Ask not what your country can do for you; ask what you can do for your country.

#13

The launch was scrubbed on May 2, but was reset for May 4. The weather was windy but clearing when Huss and I left the motel shortly after midnight. We drove around the east end of the motel to see if the searchlights at the launch pad were on. If we saw the lights, we would know that the launch complex was active and the countdown progressing.

#14

The launch was going smoothly, and the support team finished their checks. Kraft checked communications from his voice panel to the pad team. The IBM engineers, Ira Saxe and Al Layton, periodically reported on the results of the network data flow testing.

#15

The launch was delayed because of a computer crash at Goddard. The crew chiefs were tense, and when they heard the comedian Bill Dana’s high-pitched parody of a reluctant astronaut, they laughed.

#16

The launch was smooth, and after a brief hold at two minutes, the rocket continued toward liftoff. The weightless period was five minutes, and then the retrofire and reentry. The drive from the hotel to Mercury Control was longer than the fifteen-minute flight time.