Tag Archives: Apollo 1

[October 26, 1968] Phoenix from the Ashes (Apollo-7)



by Kaye Dee

In early October Wernher von Braun said that he was “beginning to doubt” America's ability to land an astronaut on the Moon before the Russians, following the Soviet success with its automated Zond-5 mission. But speaking just a few days ago, General Sam Phillips, the Apollo Programme Manager, has described the recently completed Apollo-7 flight as “a perfect mission. We accomplished 101 percent of our objectives”. With both the United States and the Soviet Union finally back in space following the tragedies that struck their respective space programmes in 1967 (an article on Soyuz-2 and 3 is coming soon), NASA has risen from the ashes of the Apollo-1 fire and is once again on track to achieve its manned lunar landing goals.


A Critical Test Flight
Possibly no NASA mission has been more critical to the future of US spaceflight than Apollo-7. The main purpose of the mission has been to prove that the new Block II Apollo spacecraft, extensively redesigned after the Apollo-1 fire, is capable of performing the 480,000-mile round trip to the Moon. If Apollo-7 did not establish the overall safety and performance of the new CM design, von Braun’s pessimism would probably be proved right!

The four critical mission objectives were:

  • test the spacecraft’s navigation and guidance systems in the performance of an orbital rendezvous;
  • prove the Service Propulsion System (SPS) engine’s performance and reliability;
  • demonstrate the safety of the redesigned Command Module (CM) and the performance of its life support systems over the duration of a lunar mission; and,
  • carry out a precise re-entry and splashdown.


The Apollo-7 crew. L – R: LM Pilot Walter Cunningham, CM Pilot Maj. Donn Eisele and mission commnader Capt. Wally Schirra. They were rarin' to go!

The First Team
With a lot riding on their shoulders, the crew of the first successful manned Apollo mission unusually combined a seasoned veteran astronaut with two rookies. Originally the back-up crew for Apollo-1, the three astronauts of Apollo-7 all have US Navy connections.

Mission commander Navy Captain Walter (Wally) Schirra, 45, is the oldest man to make a spaceflight so far. One of the original Mercury astronauts (MA-8 Sigma-7, 1962), he was also the Command Pilot for the Gemini-6 mission in 1965. Apollo-7 makes Schirra the first astronaut to fly all three types of US manned spacecraft. Rumour has it that Capt. Schirra was not particularly interested in making a third spaceflight prior to the loss of Apollo 1 but stepped up to the challenge of ensuring that Apollo-7 was a success in honour of his lost friend, Apollo-1 Commander Gus Grissom. This seems to be borne out by the fact that he announced his intention to resign from NASA two weeks before the launch of his flight.

Apollo-7’s two rookie astronauts both come from Group 3, selected in 1963. 38-year-old Major Donn Eisele (USAF), designated Command Module Pilot, graduated from the US Naval Academy but was commissioned in the Air Force. Originally slated as a member of the Apollo-1 crew, he was switched to the back-up team due to a shoulder injury. Major Eisele has specialised in the CM’s new digital guidance and navigation computer, which is vital for conducting rendezvous during lunar missions.

Mr. Walter Cunninham, 36, is a civilian scientist with a military background. Nominally the Lunar Module Pilot (even though Apollo 7 did not carry a LM), he assumed the role of the crew’s general systems expert on this flight. With a Master’s degree in physics, Mr. Cunnigham spent three years as a physicist at the RAND Corporation before becoming an astronaut, but he is also a former Marine pilot who saw service in Korea and currently a Major in the Marine Corps reserves.

Symbolising a Test Flight
Apollo-7’s mission patch was designed by North American Rockwell artist Allen Stevens, who also created the Apollo-1 patch. Its similar design to the earlier patch depicts an Apollo Command Service Module (CSM) circling the globe trailing a tail of orange flame – a reference to the test firings of the CSM’s SPS engine. The navy-blue background symbolises the depths of space: it’s also a nod to the Navy background of the crew. Centred in the design, North and South America are flanked by blue oceans, with a Roman numeral VII appearing in the Pacific Ocean region. The crew’s names appear around the patch’s lower rim. 

Although refused permission by NASA, Capt. Schirra apparently wanted to name his ship “Phoenix”. I can’t help wondering what mission patch design we would have seen had the name been allowed. We do know, however, what the patch would have looked like (as envisioned by the daughter of backup Commander Tom Stafford) if Eisele's whimsical name "Rub-a-dub-dub" had been adopted…

 

A Safer Spacecraft
Apollo-1’s CM was a Block I type, designed for Earth orbital missions, while Apollo-7 has been a shakedown test for the redeveloped Block II Command Module specifically designed for lunar voyages and able to dock with a Lunar Module (LM). Following the fire, the Block II CM was significantly redesigned to reduce or eliminate fire hazards (especially the use of flammable materials) and increase astronaut safety: many of these modifications, particularly a fully-redesigned quick-opening crew hatch for emergency escape from the spacecraft, were tested on the unmanned Apollo-4 and 6 flights. Emergency breathing masks and a fire extinguisher were also added to the cabin.

Experiments with starting fires in the redesigned cabin have also led to another crew safety enhancement: NASA now uses a 60/40 oxygen/nitrogen atmosphere in the CM during launch, before switching to a lower pressure pure oxygen inflight environment about four hours after lift-off. The astronauts’ spacesuits, and their new casual flight suits, have also been redeveloped using fire retardant materials. 

Luxury Accommodation
Compared to NASA’s previous Mercury and Gemini spacecraft, the Apollo CM is a luxury suite, its greater interior volume allowing the crew to move around freely in zero gravity. Beneath the flight couches, where the crew sit for launch and re-entry, there is room for “sleeping quarters”, where two astronauts can zip themselves into sleeping bags underneath their flight seats to keep from floating around.

With ample water provided by its fuel cells, and new food preparation and packaging techniques, the Block II spacecraft finally gives NASA’s astronauts the opportunity to enjoy hot meals! The CM provides both hot and cold water dispensers to rehydrate food packages. Capt. Schirra, a coffee lover, enjoyed his first pouch of inflight instant brew just five hours after launch!

The expanded Apollo flight menu now offers some 60 different food choices, not all of which are dehydrated. Thermostabilisng techniques allow some foods, like frankfurters, to be eaten in their natural state, while small slices of bread, covered in a coating to prevent them crumbling, can now be enjoyed – although judging by the Apollo-7 crew’s complaints about crumbly food, this may not have been entirely successful.

Some of the new bite-size, possibly crumbly, foods available to Apollo astronauts

Bending the Rules
On 11 October (US time), almost four years to the day after the launch of the three-man Voskhod-1 spacecraft, Apollo-7 lifted off from Cape Kennedy Air Force Station's Launch Complex 34 on its crucial test flight. Since the LM is still not ready for spaceflight, and so could not be tested during this mission, a Saturn 1B lofted the mission into orbit.

High-altitude winds threatened to scrub the lift-off, as a post-launch abort might have seen the CM blown back over land, instead of splashing down in the ocean, potentially exposing the crew to serious injury. Mission commander Schirra disagreed with the decision by NASA managers to waive the wind restriction, but finally yielded. However, his unhappiness over this issue may have contributed to his further disputes with Mission Control during the flight.

Despite Schirra reporting the ride to space as “a little bumpy” a few minutes into the flight, ten minutes and 27 seconds after liftoff Apollo-7 was smoothly inserted into its elliptical low Earth orbit.

Coming Together
Rendezvous and docking practice, demonstrating that the CM’s navigation and guidance systems could successfully handle this vital technique for lunar missions, was a major element of the Apollo-7 flight plan, and the first major exercise began within three hours after launch.

Although Apollo 7 was not carrying a Lunar Module, the Spacecraft-LM adapter (SLA) that would normally house one was mounted on top of the Saturn 1B’s S-IVB second stage, carried into orbit to be used as a rendezvous target.

With the S-IVB still attached to the CSM, the astronauts manoeuvred as if conducting the necessary engine burn for Trans Lunar Injection. After separation from the S-IVB, Schirra put his Gemini rendezvous experience to good use, manoeuvring Apollo-7 towards the rocket stage and closing in as if to dock. This simulated the manoeuvre needed to extract the LM from the SLA. He then flew in formation with the stage for 20 minutes, before moving about 76 miles away to prepare for the first practice rendezvous. 

Apollo-7's S-IVB stage, with the SLA petals open to reveal the docking target. The target was designed by Royal Australian Air Force opthalmologist, Dr. John Colvin. (note that one of the petals did not quite open all the way, restricting some of the possible maneuvers)

Power and Precision
The initial rendezvous exercise, occurring about 30 hours after launch, included the first inflight test of the Service Module’s powerful Service Propulsion System engine. Although tested on the ground, the SPS had never yet been fired in space, despite being vital to the success of a lunar mission: its 20,000 pounds of thrust is needed to slow the Apollo spacecraft into orbit around the Moon and propel it on its way back to the Earth. The SPS has to be totally reliable – it must work, every time.

The purpose of the rendezvous itself was to demonstrate the CSM’s ability to match orbits with a LM returning from the lunar surface, or an aborted landing attempt, even without an operating onboard radar (which Apollo-7 lacked, though later missions will have one). The SPS rendezvous burns were computed at Mission Control, but the final manoeuvres to close on the S-IVB saw Major Eisele making observations with the CM’s telescope and sextant to compute the final burns using the onboard guidance computer.

When the SPS engine ignited for the first time, Eisele was apparently startled by its violent jolt, while Schirra yelled excitedly “Yabba Dabba Do! – That was a ride and a half!” The inaugural nine-second burn went perfectly, and Schirra completed the rendezvous using the ship's reaction control system (RCS) thrusters, bringing Apollo-7 to within 70 feet of its tumbling target. The exercise successfully demonstrated that, even without radar data, an Apollo Command Module pilot could effect a rendezvous in lunar orbit.

A (Mostly) Smooth Mission
For the most part, Apollo -7 could be described as a “smooth” mission, with few real technical problems. The flight plan was “front-loaded”, with the most important experiments and activities scheduled for the early part of the mission, in case problems forced an early return to Earth. By day five of the mission, Flight Director Glynn Lunney estimated that the astronauts had already accomplished 70 to 75 percent of the planned test objectives.

The SPS engine was fired eight times in total, working perfectly every time and proving its reliability. The crew tested the fuel cells and battery chargers and checked out the cooling capacity of the thermal control system, putting the CSM into “barbecue mode,” rolling slowly around its long axis to distribute the heat load evenly over the spacecraft skin. Major Eisele thoroughly tested the sextant, telescope and guidance computer: even when vented, frozen urine crystals obscured his star targets, he proved that the optical instruments could provide sightings accurate enough to steer a spacecraft to and from the Moon.

It obviously wasn't easy for Maj. Eisele to take star sightings during the rendezvous exercise!

But the mission did experience a few technical issues. A power failure briefly struck Mission Control abut 80 minutes after launch. A mysterious “fuzz” or fog partially obscured the spacecraft’s windows, blurring the external view, although it gradually eased as the mission progressed, enabling photographic observations of the Earth (there are early indications that this may have been due to window seals outgassing). Perhaps the most annoying problem was the difficulty of using the crew’s “solid waste disposal system” – bags taped to an astronaut’s buttocks into which he excreted. The process proved to be very messy and rather smelly! 

Despite issues with window fogging, the Apollo-7 crew has returned impressive images like these, showing the Gulf of Mexico (top) and Hurricane Gladys (bottom)

Grumpy Astronauts
About 15 hours into the flight, Schirra reported that he was experiencing a head cold. Unfortunately for him, a cold in space quickly becomes a miserable experience, because congested sinuses don’t drain in weightlessness. Cunningham and Eisele also developed stuffy noses and dry nostrils, but as they experienced colds a few days before the flight, flight surgeons believe that their condition may have been due more to breathing pure oxygen for long periods.

An astronaut with a head cold is not a happy man!

Despite the use of aspirin and decongestant tablets, the cold made Schirra tired and irritable and prone to sharp exchanges with Mission Control. When Houston suggested early in the mission to add some new engineering tests into the already busy flight plan and power up the TV system ahead of schedule to check the circuits, the mission commander testily refused, citing scheduling pressures and the need for the crew to eat. Over the first few days, Schirra repeatedly delayed the scheduled public television broadcasts, considering them non-essential.

Throughout the flight, the crew had difficulty sleeping, particularly as NASA insisted that at least one astronaut was always on duty to monitor the new spacecraft’s systems during the crucial test flight. Lack of sleep and exhaustion from working long hours on a packed flight plan undoubtedly contributed to the crew’s irritability throughout the mission.

Are You a Turtle?
Capt. Schirra has a reputation for playing practical jokes and "gotchas" and decided at one point to take out his frustrations on fellow astronaut and Director of Flight Crew Operations Deke Slayton. Both men are members of a private club, which has a joking requirement that if one member asks another "Are you a turtle?" the person so asked must immediately respond with a specific vulgar reply, or else buy drinks for everyone who heard the question.

Slayton had tried to catch Schirra out during his Mercury flight by publicly asking on an open communication if Schirra was a turtle. The Apollo-7 commander decided to "return the favour" during this mission by mischievously holding up a card during the second television broadcast from the spacecraft that said "Deke Slayton, are you a turtle?" Slayton avoided giving the rude answer in a public broadcast by recording it to be played to the crew after the mission.

The Mission Commander is in Command!
Perhaps the most serious disagreement between Schirra and Mission Control arose over the issue of whether or not the astronauts would wear their space helmets during re-entry. During the descent from orbit, cabin pressure rises from 5.9 to 14.7 psi (sea level pressure). Still suffering from his head cold Capt. Schirra apparently feared a sealed helmet would prevent him from pinching his nostrils to equalise the pressure, possibly leading to a ruptured eardrum. Although helmets protect the astronauts from cabin depressurisation and landing impact forces, Schirra stood on his right to make a decision as the mission commander and insisted that the crew would not wear their helmets for re-entry.

The discussion between Apollo-7 and the ground became quite heated on this point. Although Mission Control finally acquiesced to Schirra’s decision, comments suggest that they were exasperated and surprised by the astronauts’ testiness throughout the mission, which was definitely a departure from the usual respectful communications between space and the ground. While Capt. Schirra may have been prepared to speak his mind and have his way because he has already decided to leave NASA and has nothing to lose, I wonder if the clashes between the crew and Mission Control will impact upon the careers of Major Eisele and Mr. Cunningham?

“From the Lovely Apollo Room”
Despite Schirra’s early refusal to conduct television tests, the crew became TV stars when the first live television broadcast from an American spacecraft finally occurred on 14 October. Technical limitations with the television system meant that the live broadcast was restricted to the United States, but the audience was reportedly treated to a lively piece of entertainment, with Cunningham as camera operator and Eisele as MC.

Drawing from an old radio tagline, the “Apollo-7 Show” opened with a card reading “From the lovely Apollo Room high atop everything”. The seven-minute broadcast treated viewers to a look inside the spacecraft and showed views of Lake Pontchartrain and New Orleans, before closing with Schirra holding up another sign reading “Keep those cards and letters coming in folks”, another radio tag line re-popularised by Dean Martin.

For the rest of the mission, daily television broadcasts of about 10 minutes each took place, with the crew holding up more fun signs and describing how the Apollo spacecraft worked. Since the broadcasts seem to have been very popular with audiences in America, I wonder if television’s newest stars might find themselves in line for an Emmy Award next year? 

Back to Earth
Without the crew wearing helmets, Apollo 7 made a successful re-entry on 22 October splashing down about 200 nautical miles SSW of Bermuda, with a mission duration of 10 days, 20 hours, 9 minutes and 3 seconds. The conical CM landed upside down in the water, although it was soon righted with the use of floatation bags. However, the inverted position apparently interfered with communications, giving Mission Control an agonising 10-minute wait for contact to be established by search helicopters and aircraft.

The astronauts’ arrival by helicopter on the recovery ship USS Essex was carried live to the world on television, relayed via satellite – although we here in Australia were not able to see most of the broadcast due to technical difficulties. Despite the issues with colds and stuffy noses, the crew experienced no trouble during re-entry and are said to be generally in good health. They are now back in Houston, facing three weeks of technical debriefings and medical tests.

While the disagreements between the crew and Mission Control may have cast a shadow, Apollo-7 is being hailed as a technical triumph, with the mission successfully verifying the flightworthiness of the redesigned Command Module and SPS engine.

What comes next?
Even before Apollo-7 launched, Apollo Spacecraft Manager George Low proposed that, with the delays in the construction of the LM, Apollo-8 should be a manned circumlunar flight, to build programme momentum and pre-empt a possible similar mission by the USSR. This mission prospect was being openly discussed while Apollo-7 was in orbit. With its safe and successful return, let’s hope a decision will be made very soon on this ambitious and exciting next step in space exploration: Apollo-8 is already on the pad!


[February 2, 1967] It's About Time (Star Trek: "Tomorrow is Yesterday")


by Elijah Sauder

A time to laugh, a time to weep

Before I discuss the latest episode of Star Trek, I feel it would be remiss of me to not acknowledge the loss that we experienced on the 27th with the deaths of Gus Grissom, Ed White, and Roger B. Chaffee in the mishap during the Apollo 1 rehearsal test. It is in times like these, times when our dreams of reaching the stars seem to be shaken, that we are reminded of the danger involved in such dreams. However, though the stark reality and harshness of the danger can make the dream seem unattainable, we should stand and support the astronauts that choose to risk their lives, and follow the footsteps of those who have gone on without us, follow their dream and see it to fruition.  This mighty loss deserves remembering, let us remember these brave three and carry their dreams with us.

It feels weird to transition to summarizing an episode of a fictional TV show about space after remembering the events of the 27th, but “Tomorrow is Yesterday”, one of my favorite episodes so far, provides an eerily appropriate counterpoint to the Apollo 1 disaster.

We find the crew of the Enterprise in the late 1960s, stranded in the past after a brush with a "dark star", which renders the ship largely inoperable. While they are trying to figure out how to get the ship operational and get back to their own time, the Air Force detects them and sends fighters to investigate. This results in one of the pilots, Captain John Christopher, being beamed aboard. All well and good, Captain Kirk thinks. But the pilot had taken and transmitted recordings of the sighting. The crew beams down to try and destroy the recordings and set history to rights.


"You're coming with me to see Colonel Bellows!"

During all sorts of amusing antics, another non-crew member gets beamed aboard and Kirk gets captured. Spock, Sulu, and the pilot, go down to rescue Kirk and despite some duplicity, manage to retrieve him and beam back to the ship with everything they went to acquire. The episode ends with Scotty and his crew getting the ship running again (though still in need of more thorough repairs) and then using Spock’s idea to try and repeat the maneuver that got them to the past but in reverse by using the sun to 'slingshot' the ship forward in time. Through this process they go back in time a bit, which allows them to return the pilot to the past before the Enterprise beamed him up. They then continue forward, making it back to their own time and communicate to Starfleet that they have returned.


It's a sharp right past Mercury.

I absolutely loved this episode. It felt lighthearted and didn’t take itself too seriously. And whether it was meant or not, the fights in the show were quite humorous. But those things alone do not make a good episode. All the actors did a wonderful job this episode really selling the characters. I also appreciated the more science fictional premise. The previous couple of episodes have involved highly advanced species that border on gods and while I feel those stories have their place in science fiction, I much prefer premises like this episode’s.


Flying Kirk Attack!

Of course, "Tomorrow is Yesterday" was not without its flaws. The most glaring ones were at the end where the Enterprise beamed the pilot down to a location his past self already was, and that the timeline seemed to be rewritten after doing that; no trace of the Enterprise or its Earth-based gamboling. I personally didn’t mind these too much as I felt the fun of the rest of the show made up for them, but they may turn some people off.


"UFO? What UFO?"

Overall, for me this episode was a solid 4.5/5.


Get me to the Church on Time


by Abigail Beaman

Since this is my first time contributing to The Galactic Journey, I thought I would introduce myself. My name is Abigail Beaman or Abby for short. I started watching Star Trek during its 11th episode, "The Menagerie (Part One)", and to date, my favorite episode is "The Galileo Seven". I may or may not have created a wedding certificate for me and Mr. Spock–a girl's got to prepare for the future.


Mr. Abigail Beaman

Star Trek as a whole is a very interesting and wild concept that I support, but I feel that most episodes suffer from slow plots or the crew feeling out of place. That’s how I originally thought "Tomorrow is Yesterday" would have played out. While I normally dislike time-traveling episodes for their bad writing and forced narratives, this episode has helped change my opinion. With that being said I wholeheartedly believe that this episode wasn’t interesting because of the time travel, but rather how the characters interacted with said travel.


"And this is how you make a warp engine!" "That's enough, Lieutenant…"

In past episodes, there have been moments where I thought a character acted strangely or dumb just to continue the story. However I feel proud to say, not once did I question any of the characters' actions in this episode. Mr. Lieutenant Commander Spock was probably my favorite example of this episode. While yes, he was already my most beloved and favorite character, the sheer number of witty, very logical, and utterly Spockish retorts made the episode even better. I found the scene when Captain Christopher pulls a gun on Sulu and Kirk to be my favorite. Spock is already expecting this, so he beams up to the ship and then beams back down to knock out Captain Christopher. A nice application of logic and technology.


Funny. That's now how I look when he does that to me…

At the end of the line, I am going to rate "Tomorrow is Yesterday" very highly, as it was altogether a silly episode that made my day. However, I understand not everyone likes silly time travel episodes and their usually unaddressed ramifications. It’s all up to personal opinion, and with that said I rate this episode 4.5/5.



by Lorelei Marcus

Tragic Predictions

I had originally intended to write about my thoughts on the episode's predictions of when we will be launching our first manned moonshot. With ten Gemini missions rapidly successfully flown, and the Apollo program just around the corner, I felt "the late '60s" was a perfectly reasonable estimate. The Moon was practically in our grasp. Or so I thought.

On January 27, at 6:31 PM, three astronauts were killed in a freak accident fire on the Apollo One spacecraft. Experts think it was caused by faulty wiring which sparked with the 100% oxygen atmosphere of the cockpit.

I was numb when I first heard Mike Wallace report on the disaster. The dread and realization mounted over the course of the CBS Special Report, but the reality of what had occurred didn't really hit me until Walter Cronkite, a face I associate strongly with another world-shifting tragedy, came on the screen.  To paraphrase his words, "This may shift our plans back from 1967 to 1968, from '68 to '69, from '69 to even 1970.  But we must have courage…no, the guts to continue forward with this space program."

I'm glad "Tomorrow is Yesterday" writer D.C. Fontana never explicitly named the three men who will be on the Apollo flight to the Moon.  While an author could never have predicted something like the Apollo 1 fire, not hearing Grissom or White's names mentioned in the episode allows it to remain plausibly our future and the Enterprise's past.

Maybe "the late 60s" won't be a far off guess after all.

Four stars.



by Andrea Castaneda

A dimension too far

Star Trek already has a grandiose premise, which I love and appreciate. It leads to many possible scenarios for adventure, conflict, and character development. But when time travel gets added, it takes it a dimension too far and exponentially expands the potential for plot holes and inconsistencies.

The episode started out strong. I liked seeing how our 1967 perspective would process seeing a starship suddenly appear. I also liked the high stakes of a small event altering the future irrevocably.


The Enterprise as seen from Captain Christopher's F-104. This is one of the more effective shots in the show.

However, the setting of outer space has fixed rules, whereas the logic of time travel seems too flimsy to be consistent. We're given a brief explanation of Trekian physics. One needs massive amounts of energy and velocity to propel oneself through space and time. Therefore it makes sense that stars with their immense gravities are necessary to do so, and that the crew would repeat this process to go home. But then the logic starts to bend to fit the narrative. They conveniently go back a day in time before they arrived, returning their 20th century guests.

Yet despite how inexperienced they are with time travel, they manage to know the precise moment they were beamed up and can seamlessly beam them back to that exact moment. Which somehow removes their memories of everything ensuing. And because the Enterprise has gone back in time, it now could never exist in our time, making the entire second act pointless. Everyone goes home, the crew of the Enterprise cheer, and they continue to go boldly where no man's gone before.


Time travel fixes everything!

This end frustrates me not only because of the paradox it creates (how is the Enterprise no longer in the past? Shouldn't it exist twice?) but because the character development in Captain Christopher is now rendered moot. He was, to me, the strongest aspect about this episode. Through him and Kirk, we see what past and future can learn about each other and how despite the centuries between them, they're both still human.

I think a scenario where things ended in a time loop would have been far more interesting. Christopher could have returned home, had his son destined to explore Saturn, and raised him to keep looking to the stars– all inspired from his day-long romp in space, making the end of this episode feel less hollow. Certainly, it would have been a less problematic presentation of the time travel cliché.

Still, this "Tomorrow is Yesterday" was overall enjoyable to watch. It allowed much of the ensemble to shine, offered up hilarious gags and an interesting perspective about humanity's advancement. I just hope that going forward, the writers keep this time travel plot device to a minimum.

Three stars.


Well, at least it's unlikely this week's episode will involve time travel.  Join us tonight at 8:30 PM (Eastern and Pacific)!


"Captain Kirk, This is Your Life!"

Come join us!



[January 31, 1967] The Law of Averages (February 1967 Analog)


by Gideon Marcus

Bump in road

Here, just a few days after human spaceflight's greatest catastophe, it's easy to begin to doubt.  Is this madcap race to the Moon, hanging on a construction leased out to the lowest bidders, all worth it?  The cost in money and lives?  We've lost six astronauts thus far; Elliot, Bassett and See were all killed in training accidents, but their souls are no less valuable than those of Grissom, White, and Chaffee.

Indeed, the Russians have already announced that they've given up.  With the war heating up in Vietnam, with society on Earth not yet Great, should we continue to bother?

The answer, of course, is yes.  Any man's death diminisheth me, as John Donne said, but as large as this tragedy looms in our vision now, it will be the smallest of footnotes compared to humanity's epic trek to the stars, which surely must come.  It is our species' saving grace that we recover from missteps and proceed more vigorously than ever.  And it is out there in the stars that we will find the answers to the riddles of the universe, the exciting frontiers, the possible partners in science and empathy.

Out there

This month's Analog offers a sneak preview of what this far future, when humanity is established in space, will look like..


by Kelly Freas

Pioneer Trip, by Joe Poyer


by Kelly Freas

On the first expedition to Mars, an electrical fire causes one member of a three-man crew to succumb to chemical-induced emphysema.  His condition, fatal if the ship does not turn 'round (though dubious even if it does) jeopardizes the mission.  The commander makes one decision; the stricken crewman another.

I'm not usually a fan of Joe Poyer, who writes as if he gets the same thrill from technical writing as others might from the works sold under the counter and wrapped in brown paper.  Nevertheless, this story was pretty affecting–and all the more poignant in light of last week.  A solid three star effort.

There Is a Crooked Man, by Jack Wodhams


by Kelly Freas

Science fiction usually explores the positive effects of technology.  This mildly droll story deals with how new advances are used for nefarious purposes.  Teleportation, brain transplant, mind-blanking frequencies, a precognition drug–these all lead to a race between criminal elements and the police.

Told in a bunch of very short snippets, it's a surprisingly readable, if not tremendous, tale.

Three stars.

The Returning, by J. B. Mitchel


by Leo Summers

A little spore, the only remaining particle of an alien expedition thousands of years old, is awoken by a flash flood through a desert air force proving ground.  The creature quickly awakens, eager to make contact with the sender of the modulated signals it is receiving.  To its dismay, the alien finds only a weaponized drone, hallmark of a savage society.  But the pacifistic being has other uses for the plane…

If J.B. Mitchel be "John Michel", then he is a veteran, indeed.  He first started writing in the 1930s, and I don't believe I've seen anything from him since I started the Journey.  His skill shows.  His prose is evocative, his descriptions vivid.  And I very much appreciate a story where the "monster from outer space" is basically a good guy, not bent on Earth's conquest.

Four stars.

The Quark Story, by Margaret L. Silbar

The one piece by a woman published in any SF magazine this month is this nonfiction article.  It's quite good. 

Last year, I read a lot of physics books for laymen.  The consensus has been that the menagerie of subatomic particles was reminiscent of the zoo of elements discovered by the late 19th Century.  There must be some underlying simplicity that results in the multiplicity.  For elements, it was electrons, protons, and neutrons.  For those and smaller elementary particles, the answer appears to be still smaller bits called "quarks".

It all makes perfect sense the way Ms. Silbar lays it out, even if editor John Campbell is a doubting Thomas about it.  The only fault to the article is it could have used another page or two to explain some of the trickier concepts (e.g. Pauli Exclusion Principle).

Four stars.

Amazon Planet (Part 3 of 3), by Mack Reynolds


by Kelly Freas

The final chapter of Mack Reynold's latest turns everything on its head.  In the first installment, we followed Guy Thomas, a would-be merchant, to the planet of Amazonia.  Said world is reputed to be utterly dominated by women, and men aren't allowed to escape.  Upon arriving, it was revealed that Thomas is none other than Ronny Bronston, Section G agent extraordinaire.

Part Two involved Bronston meeting up with a domestic masculine resistance movement, "The Sons of Liberty", several attempts on his life, capture and truth-drug doping by the Amazon government, and copious examples of an almost laughable communistic, female-run despotism.  At this point, I had to wonder what the normally sensitive Reynolds was trying to do.  His matriarchy was a paper-thin caricature.

Turns out it was all a big put-on, mostly at the instigation of the daughter of one of the world's leaders.  Amazonia has long since evolved beyond its primitive beginnings and is actually quite a good example of enlightened equality and meritocracy.  The trouble in paradise comes not from within, but without–at the hands of a rogue Section G agent.

Part Three is half adventure story and half political lecture (as opposed to Part One which was all lecture and Part Two, which was mostly adventure).  Nevertheless, Reynolds isn't bad at both, and I do appreciate his both subverting expectations and extrapolating an interesting political experiment. 

Three stars for this segment, and three and a half for the whole, which is greater than the sum of its parts.

Elementary Mistake, by Winston P. Sanders


by Kelly Freas

I really liked the setup on this one: there's no faster than light drive, but there are matter transmitters (a la Poul Anderson's story "Door to Anywhere" in Galaxy).  So ships are sent out at relatavistic speeds to set up teleporters on distant worlds.  The trip takes five or ten or twenty years for outside observers, but the actually crew experience only a matter of months.  And so, humanity spreads.

Only on the world of Guinevere, not only are none of the required minerals available to build the transmitter, but the atmosphere itself has an inebriating effect.  What's a creative crew to do?

It's a reasonable puzzle story, though I have trouble contemplating a world where calcium doesn't exist but strontium does in quantity.  The only thing I took umbrage with was 1) the lack of women on the exploration team, and 2) the explicit implication that the only thing women are good for is servicing men.

Given that this issue has both a great science article by a woman and the conclusion of a serial about a perfectly good planet run by women, this stag story set in the far future is particularly jarring.  But Anderson/Sanders has always had a problem with this, which strikes me as strange given that his wife is herself a science fiction writer.

Anyway, three stars.

Leading the pack

Speaking of averages, Analog, which had hitherto been relatively low in the ranks of magazines for several months suddenly emerges as the best of the lot, clocking in at a decent 3.3 stars.  That's partly because its competition is rather weak.  Only SF Impulse (3.1) finished above water.  All the others scored less than three stars: IF (2.9), Fantasy and Science Fiction (2.6), Worlds of Tomorrow (2.5), Galaxy (2.4), and Amazing (2.2).

Analog also, atypically, featured the most women contributors…since none appeared anywhere else!  Given that Lieutenant Uhura appears front and center on every episode of Star Trek, I think it's time literary SF caught up with its boob tube sibling.

Or we might end up with a much more lasting disaster!





[January 28, 1967] "Fire in the cockpit!" (The AS-204 Accident)


by Kaye Dee

As I write this, I’m still in shock. It’s only a few hours since the news broke here in Australia of the tragic loss of the crew of Apollo 204 in a fire on the launchpad at Cape Kennedy, during a launch rehearsal. Spaceflight is difficult and dangerous – we know that. Astronauts Freeman, Bassett and See were killed in plane crashes during training; Armstrong and Scott had a narrow escape from inflight disaster during Gemini VIII.

Unconfirmed rumours abound of Soviet cosmonauts who died in unsuccessful space missions before Gagarin, and the Russians have probably had training accidents to which they have not yet admitted. When I wrote about Gemini VIII’s aborted mission, I asked if spaceflight was moving too fast. There’s certainly been a headlong rush on NASA’s part to get to the Moon ahead of the Soviet Union, so perhaps this tragedy is the answer to my rhetorical question.


The first image available showing the fire-ravaged interior of the Apollo 204 spacecraft

Details are still sketchy at this time, although no doubt more information about the accident will emerge in the coming days and weeks as investigations take place. But right now, let’s explore the background to the mission and what we know about the catastrophe.

The Lost Crew
Apollo 204 (AS-204) was intended to be the first manned test flight of the new Apollo Command and Service Modules, the spacecraft that will be used to carry the first NASA astronauts to the Moon within the next few years. As such, two experienced astronaut test pilots were assigned to the flight: USAF Lt. Colonels Virgil “Gus” Grissom, the Command Pilot, and Senior Pilot Edward White. Grissom was the United States’ second space traveller, flying the Mercury MR-4 mission. He also commanded the first manned Gemini mission, Gemini III. Rumour even has it that Grissom was already under possible consideration to command NASA’s first lunar landing mission. Lt. Col. White is famous as the first American to make a spacewalk, during Gemini IV. These veteran astronauts were joined for this mission by rookie US Navy Lt. Commander Roger Chaffee. Chaffee was selected as a member of the third astronaut group and specialised in communications: he had been a CapCom for both Gemini III and IV.


Official Apollo 204 crew portrait, including a model of the new Apollo Command Module which their mission was intended to test. Left to right Ed White, "Gus" Grissom and Roger Chaffee

The Apollo 204 back-up crew consists of experienced Mercury and Gemini astronaut Walter Schirra and first-time fliers Donn Eisele and Walter Cunningham. Astronaut Eisele had originally been assigned in Lt. Commander Chaffee’s role for the Apollo 204 mission but had to be replaced when he needed shoulder surgery in early 1966. I assume that once Apollo missions resume after the accident investigation, this crew will fly the first orbital mission that should have been accomplished by AS-204.

What’s in a Name?
The design for the official Apollo 204 patch, developed by the crew and illustrated by North American Rockwell artist Allen Stevens, carries the designation Apollo 1. At the time that it was approved by NASA, in June 1966, this was the flight’s official name. However, it seems that only recently some doubt arose as to whether the formal designation of the mission would be Apollo 1 after all, which is why it is presently being referred to as Apollo 204, or AS-204. I’ve heard from the Australian liaison officer at NASA, that just last week approval for the patch was withdrawn and that, if this accident had not occurred, the patch might have had to be redesigned, depending on the final mission designation.

But as it stands, the mission patch uses the American flag for a background, with a central image depicting an Apollo spacecraft in Earth orbit. The Moon appears to the right of the Earth, reminding us of the eventual goal of Project Apollo. The designation Apollo 1 and the names of the crew appear in a border around the central image, while the patch is edged with a black border – a touch that is poignantly even more appropriate in view of the loss of the crew. I do hope that this patch, and the designation Apollo 1, will be re-instated as the official insignia of this mission in honour of its lost crew.

The Mission that Should Have Been
The fire that has killed the Apollo 204 crew occurred during a preflight test ahead of a launch scheduled for 21 February. It was planned to be the first manned orbital test flight of the Apollo Command and Service Modules, launched on a Saturn IB rocket. The mission was to have tested launch operations, ground tracking and control facilities, as well as the performance of the Apollo-Saturn launch vehicle. Depending on how well the spacecraft performed, the mission might have lasted up to two weeks, perhaps equalling Gemini VII's record spaceflight and demonstrating that the Apollo spacecraft could function successfully for the duration of the longest Moon flights currently in planning.


The Apollo 204 crew in front of Pad 34, from which they should have launched, and where they have been killed

The Command Module allocated to Apollo 204, CM-012, was a so-called “Block I” version, originally designed before the lunar orbit rendezvous landing strategy was selected. Block 1 spacecraft aren’t able to dock with a lunar module, but future “Block II” versions will.

Was It a Lemon?
The Apollo Command and Service Modules are undoubtedly far more complex than any previously-built spacecraft, so it isn’t surprising that their development has had many teething problems. Over the last few months, I’ve heard from my former colleagues at the WRE that many issues with the Command Module became evident last year, especially when CM-012 was delivered to Kennedy Space Centre in August to be prepared for its flight. Even before it arrived, the Apollo 1 crew had expressed concerns to Apollo Spacecraft Program Office manager Joseph Shea about the quantity of flammable materials, such as nylon netting and Velcro, being used in the spacecraft cabin to hold tools and equipment in place. It seems that, even though Shea ordered these flammable materials removed, this may not have happened.


The Apollo 204 crew sent Program manager Jospeh Shea a parody of their crew portrait to express their concernes about the spacecraft. They are shown praying, and the picture carried the inscription: "It isn't that we don't trust you, Joe, but this time we've decided to go over your head"

When CM-012 arrived at Kennedy Space Center, there were still 113 significant planned engineering changes to be completed, and another 623 engineering change orders were made following delivery! This suggests that many issues with the spacecraft design were still being resolved. Apparently, the engineers in charge of the spacecraft training simulators just couldn’t keep up with all these changes, and I’ve heard that Lt. Colonel Grissom expressed his frustration about this by bringing a lemon from a tree at his home and hanging it on the simulator.


CM-012, at that time designated Apollo 1, arriving at Kennedy Space Centre

There were several problems with the environmental control unit in the Command Module, which was twice returned to the manufacturer for designed changes and repairs. During a high-speed landing test, when the Command Module was dropped into a water tank to simulate splashdown, its heat shield split wide open, and the ship sank like a stone! There were also apparently concerns about a propellant tank in the Service Module that had ruptured during pre-delivery testing. NASA had it removed and tested at Kennedy Space Centre to be sure there were no further problems. 

CM-012 finally completed a successful altitude chamber test on 30 December and was mated to its Saturn IB launch vehicle on Pad 34 at Cape Kennedy on 6 January. So, was this particular spacecraft a lemon – an accident waiting to happen? Or has this tragedy shown that the design of the Apollo Command Module is inherently flawed? We’ll undoubtedly have to wait for the results of the accident investigation before we know the answer.

Countdown to Disaster
At this point, we still know very little about the disastrous fire or what led to its breakout, but my WRE colleagues have helped me put together some information accident from their contacts at NASA. The fire broke out during what had apparently been a trouble-plagued launch simulation known as a "plugs-out" test. This kind pre-flight simulation is intended to demonstrate that the spacecraft will operate as it should on internal power, detached from all cables and umbilicals, and successfully carrying out this test was essential for confirming the 21 February launch date.


The AS-204 crew in the CM simulator on 19 January, as part of their preparations ahead of the "plugs out" test

Almost as soon as the astronauts entered the Command Module, there were problems when Grissom experienced a strange odour in his oxygen supply from the spacecraft, which delayed the start of the test. Problems with a high oxygen flow indication that kept triggering the master alarm also caused delays. There were also serious communications issues: at first, it was Command Pilot Grissom experiencing difficulty speaking with the control room, but the problems spread to include communications between the operations and checkout building and the blockhouse at complex 34, forcing another hold in the simulated countdown.

Fire Erupts
It was not until five and a half hours after the simulation began that the countdown finally resumed, and when it did instruments apparently showed an unexplained rise in the oxygen flow into the crew’s spacesuits. Within seconds, there were calls from the spacecraft indicating that a fire had broken out in the cabin and that the astronauts were facing a serious emergency, trying to escape. The final transmission from inside the spacecraft ended with a cry of pain.

Of course, there are emergency escape procedures for the Command Module, but with the triple spacecraft hatch, it requires at least 90 seconds to get it open, and it seems that the crew had never been able to accomplish the escape routine in that minimum time. There is some evidence that Lt. Col. White was trying to carry out his assigned emergency task of opening the hatch, but in the pure oxygen atmosphere of the spacecraft, the fire became incredibly intense very rapidly and rising internal pressure would have made it difficult, if not impossible to open the inward-opening hatch.


Picture taken shortly after the fire was extinguished showing the external damage to the Command Module caused by the hull rupture resulting from the fire

In less than 20 seconds from the first detection of the fire, the pressure inside CM-012 rose to the point where it actually ruptured the hull of the spacecraft, sending flame, heat and dense smoke into the pad service structure. The ground crew bravely tried to rescue the astronauts, but the dangerous conditions and unsuitable emergency equipment made it virtually impossible. Many were later treated for smoke inhalation. There were fears the CM had exploded, and that the fire might ignite the solid fuel rocket in the launch escape tower above it. If this happened, it could set fire to the entire service structure.

It took about five minutes for the ground crew to finally get the spacecraft hatch open, but their efforts were in vain, as the astronauts were already dead. The exact cause of death has yet to be determined: it may have been physical burns from the fire, or carbon monoxide asphyxia, from the fire's by-products.

Whatever the cause, three brave men have died, and an exhaustive investigation of the fire and its causes will now take place as part of the accident investigation. Exactly what effect this tragedy will have on the future of the Apollo programme will very much depend upon the findings of that investigation. If the design of the Command Module is found to be intrinsically flawed, the necessary redesigns could delay the programme for years, causing NASA to miss President Kennedy’s deadline for a Moon landing, and allowing the Soviet Union to overtake the United States again in the Space Race.

Grissom and White have both said in past interviews that they recognized the possibility that there could be catastrophic failures and accidents in spaceflight and that they accepted that possibility and continued with their work. I’d just like to give the last word in this article to Astronaut Frank Borman, who said in a 1965 interview "I hope that the people in the US are mature enough that when we do lose our first crews they accept this as part of the business". It would not honour the loss of the Apollo 204 crew if this tragedy led to the termination of the Apollo programme.