Space Exploration Stories

OBOMEDIA ENTERTAINMENT
  • 0.0 (0)
  • Astronomy
  • Updated Daily

Have you ever looked into the night sky and wondered what it actually took for humans to reach beyond it? Behind every launch is a chain of decisions, risks and discoveries that transformed distant worlds from points of light into places we could study. Space Exploration Stories follows the missions, breakthroughs and extraordinary moments that pushed exploration farther than anyone once thought possible. Each episode explores space missions, scientific discoveries and the people behind humanity’s journey beyond Earth. From ambitious engineering to unexpected challenges, the stories reveal how exploration advances through curiosity, persistence and calculated risk. The universe keeps giving us new questions faster than we can answer them—so what might the next mission discover that changes everything we thought we knew?

  1. 22h ago

    The single wrong character that shut down Phobos‑1's sun lock-was there time?

    A wrong character told Phobos‑1 to shut its thrusters, and engineers raced to stop a sun lock slipping away. Did they make it in time? The single wrong character that shut down Phobos‑1's sun lock-was there time? In this episode, we follow the sequence of decisions, design choices, and human procedures that let one character in a maintenance upload execute a ground-only routine on a deep-space craft. The episode traces the Phobos program’s goals, the flight computer’s built‑in test command, and the ticking clock once the wrong character was sent - could human process and protocol avert disaster? Person: Engineers and operators who handled Phobos‑1 uplinks Date: August 29-30, 1988 (wrong character uploaded); September 2, 1988 (spacecraft stopped answering) Event: Phobos‑1 received a maintenance command that shut down attitude control thrusters Platform: One F flight computer with firmware-stored ground-test routine in read-only memory Payload: Instruments from 14 nations including CNES infrared spectrometer and Swedish ASPERA - The Phobos program aimed for orbital operations and lander deployment on Mars’s moon Phobos, carrying international instruments and the novel PROP‑F lander. - The one F flight computer included a ground-testing routine in ROM that, if executed, disables three‑axis attitude control. - Replacing the flight computer to remove that routine was technically possible but incompatible with the launch schedule, so the routine remained in firmware. - The operational safeguard relied on human discipline: the specific character string that would trigger the routine was never to be sent. - On the night of August 29-30, 1988, a maintenance upload contained a single wrong character; the transmission reached Phobos‑1, and the command executed. To listen to this podcast ad-free and access premium episodes, try our subscription with a 14-day free trial at obomedia.com. © 2026 OBOMEDIA. All rights reserved. This episode and its content (audio, text, and related materials) are the exclusive property of OBOMEDIA and are protected by applicable copyright laws. Reproduction, distribution, editing, or commercial use, in whole or in part, without prior written permission from OBOMEDIA is prohibited. For permissions, licensing, and business inquiries: business@obomedia.com.

  2. 1d ago

    The restartable Agena engine relit after coast - did the spy payload live?

    A restartable Agena engine fires again after a coast above Earth-one spy payload hangs in orbit; did they make it in time? The restartable Agena engine relit after coast - did the spy payload live? In this episode, we trace the Agena from a cancelled weapons project to a standardized orbital workhorse and follow its role carrying both NASA experiments and secret military payloads. What happened on the flight when the engine reignited after coast, and what did it mean for the classified satellite it carried? Person: Lawrence Edwards Date: 1959-1987 (program flight history) Location: Earth orbit Topic: Agena restartable engine and classified payloads - The Agena evolved from the cancelled Weapons System 117L upper stage, repurposed and built by Lockheed. - The Agena-B introduced the near-miraculous capability to restart its Bell 8096-derived engine after coasting in orbit. - The Bell 8096 lineage traces back to engineering work on a cancelled rocket-propelled nuclear warhead pod, including propellant chemistry of IRFNA and UDMH. - In 1962, Lawrence Edwards pushed to standardize the design, producing the Agena-D which flew unchanged for 25 years. - Of 365 flights, 33 carried NASA payloads with public records; 332 carried classified military payloads whose records remain largely sealed. To listen to this podcast ad-free and access premium episodes, try our subscription with a 14-day free trial at obomedia.com. © 2026 OBOMEDIA. All rights reserved. This episode and its content (audio, text, and related materials) are the exclusive property of OBOMEDIA and are protected by applicable copyright laws. Reproduction, distribution, editing, or commercial use, in whole or in part, without prior written permission from OBOMEDIA is prohibited. For permissions, licensing, and business inquiries: business@obomedia.com.

  3. 2d ago

    Segment Fifty-One flashed, claiming Friendship 7's heat shield - and time ran out

    A single console light in Mercury Control claims Friendship 7’s heat shield during John Glenn’s return-did Mission Control stop a fireball in time? Segment Fifty-One flashed, claiming Friendship 7's heat shield - and time ran out In this episode, we follow the tense hours of John Glenn's 1962 Mercury-Atlas Six flight from prelaunch delays to a life-or-death sensor reading during reentry. The episode traces the decisions inside Mercury Control and asks whether the team could act fast enough to save him. Person: John Glenn Glenn Date: February 20, 1962 Spacecraft: Friendship 7 (Spacecraft Number Thirteen) Controller: Don Arabian Mission Directors: Chris Kraft, Walter Williams - Prelaunch: seven weeks of delays, faulty bolts, ice fog, and a defective hatch that cost forty-two minutes. - Launch timeline: Glenn entered the capsule at 06:11 ET, ignition at 09:47 ET after multiple scrubs and a heart rate reading of 110 bpm. - In-orbit: three orbits planned; a small warning appeared on the first orbit and stayed unresolved. - Critical moment: at 4 hours 33 minutes into flight, Segment Fifty-One lit, indicating the heat shield had unlatched. - Decision room: Don Arabian reran checks, then Flight Director Chris Kraft and Mission Director Walter Williams confronted the impossible readout. To listen to this podcast ad-free and access premium episodes, try our subscription with a 14-day free trial at obomedia.com. © 2026 OBOMEDIA. All rights reserved. This episode and its content (audio, text, and related materials) are the exclusive property of OBOMEDIA and are protected by applicable copyright laws. Reproduction, distribution, editing, or commercial use, in whole or in part, without prior written permission from OBOMEDIA is prohibited. For permissions, licensing, and business inquiries: business@obomedia.com.

  4. 3d ago

    The Pressurized Mating Adapter stalled outside - did they make it?

    A veteran astronaut floats outside the station to move a Pressurized Mating Adapter-did they make it in time? The Pressurized Mating Adapter stalled outside - did they make it? In this episode, we follow the mission that turned an ordinary logistics task into an endurance legacy. The story tracks James Voss’s path from a boy in Alabama to an astronaut assigned a long, precise spacewalk that would test training, patience, and procedure-what happened next? Person: James Voss Date: March 8, 2001 Event: Relocation of the Pressurized Mating Adapter Duration referenced: Eight hours and fifty-six minutes Mission: STS-101 (Discovery) - Voss grew up in Opelika, Alabama, raised by his grandparents with an early fascination for the sky. - He worked as a Vehicle Integration Test Engineer and joined the Challenger investigation after the January 28, 1986 disaster. - Selected as an astronaut candidate in June 1987 and qualified as a mission specialist in August 1988. - Previous EVAs: six hours on STS-69 (1995) and six hours with Jeff Williams on STS-101 (2000) installing hardware on the station. - On March 8, 2001, Discovery crew assigned Voss and a partner to move the Pressurized Mating Adapter from one docking port to another during a planned spacewalk. To listen to this podcast ad-free and access premium episodes, try our subscription with a 14-day free trial at obomedia.com. © 2026 OBOMEDIA. All rights reserved. This episode and its content (audio, text, and related materials) are the exclusive property of OBOMEDIA and are protected by applicable copyright laws. Reproduction, distribution, editing, or commercial use, in whole or in part, without prior written permission from OBOMEDIA is prohibited. For permissions, licensing, and business inquiries: business@obomedia.com.

  5. 4d ago

    The Calm Bay That Took a Shuttle Pilot Before He Could Reach Shore

    Veteran shuttle pilot Alan Poindexter drifts in Little Sabine Bay after a family outing-can anyone get to him in time? The Calm Bay That Took a Shuttle Pilot Before He Could Reach Shore In this episode, we follow the life and career that led Alan Poindexter from Naval flight school to carrier decks and the left seat of Space Shuttle Discovery, and we set the scene for the afternoon in Little Sabine Bay that changes everything. What happened that July day, and why no procedure could save him, drives the episode's central question. Person: Alan Poindexter Poindexter Date: July 12, 2012 Location: Little Sabine Bay Career hours: more than 4,500 flight hours Assignments: two Space Shuttle missions (STS-122 pilot, STS-131 commander) - Grew up near Washington, studied aeronautical engineering at the Naval Postgraduate School, and trained as a Navy pilot in Pensacola. - Served as a methodical test pilot at Patuxent River and was named Test Pilot of the Year in 1996 after proving new digital flight controls on an F-14. - Accumulated 450+ carrier landings, logged over 4,000 hours across 30+ aircraft types, and circled Earth 441 times during two shuttle missions. - Flew STS-122 as pilot in 2008 (12 days, 19 hours, 46 minutes, 203 orbits) and commanded STS-131 in 2010 (15 days, 2 hours, 47 minutes, 238 orbits). - Resigned from NASA in December 2010 after a career defined by procedure, precision, and missions where failure had contingency plans - except for the afternoon on the bay. To listen to this podcast ad-free and access premium episodes, try our subscription with a 14-day free trial at obomedia.com. © 2026 OBOMEDIA. All rights reserved. This episode and its content (audio, text, and related materials) are the exclusive property of OBOMEDIA and are protected by applicable copyright laws. Reproduction, distribution, editing, or commercial use, in whole or in part, without prior written permission from OBOMEDIA is prohibited. For permissions, licensing, and business inquiries: business@obomedia.com.

  6. 5d ago

    The Remote Manipulator Arm grabbed the dying satellite - and the clock began

    A Remote Manipulator Arm must grapple a dying 15,400-pound satellite in low orbit while a countdown ticks from launch - did they make it in time? The Remote Manipulator Arm grabbed the dying satellite - and the clock began In this episode, we follow the mission that put an astronaut, a robotic arm, and a decaying communications satellite on a collision course with the clock. What decisions and actions did the crew take as the satellite’s orbit fell and time ran out? Person: John Michael Lounge Event: STS-51-I deployment and capture attempt Date: Launch August 27, 1985 Location: Low Earth orbit Payload mass: 15,400 pounds - Lounge operated the Shuttle Remote Manipulator System to deploy and later approach satellites from Discovery’s payload bay. - SYNCOM IV-3 failed to fire its perigee kick motor and was left in a decaying low orbit months before STS-51-I. - Ground teams attempted multiple remote fixes for the dead satellite before the Shuttle mission launched. - Discovery carried three satellites deployed successfully before the crew prepared to rendezvous with the already-orbiting SYNCOM IV-3. - The mission timeline started with a running clock from launch, setting strict windows for rendezvous and capture operations. To listen to this podcast ad-free and access premium episodes, try our subscription with a 14-day free trial at obomedia.com. © 2026 OBOMEDIA. All rights reserved. This episode and its content (audio, text, and related materials) are the exclusive property of OBOMEDIA and are protected by applicable copyright laws. Reproduction, distribution, editing, or commercial use, in whole or in part, without prior written permission from OBOMEDIA is prohibited. For permissions, licensing, and business inquiries: business@obomedia.com.

  7. 6d ago

    The fuel alarm that forced Grabe's shuttle to burn early

    A NASA shuttle pilot feels a fuel alarm on approach to launch and must decide to burn early-did he make it in time? The fuel alarm that forced Grabe's shuttle to burn early In this episode, we follow Ronald John Grabe’s path from combat pilot to test pilot to NASA astronaut and trace the moments and decisions that led to a tense shuttle launch sequence. The narrative focuses on procedures, training, and the alarm that forced an early burn-what choices did the crew and ground teams face in that moment? Person: Ronald John Grabe Date: born June 13, 1945 Location: New York City; later assignments include Bien Hoa, Cannon AFB, Edwards AFB, Boscombe Down Event: selected by NASA in August 1981 Topic: combat missions, test pilot work, and a shuttle fuel alarm - Flew 200 combat missions over Vietnam and received the Distinguished Flying Cross and the Air Medal with seven Oak Leaf Clusters - Studied aeronautics on a Fulbright at Technische Hochschule Darmstadt before attending pilot training - Transitioned from F-100 and F-111 operational flying to test pilot school, earning the Liethen-Tittle Award - Served as an exchange test pilot with the RAF at Boscombe Down and became chief project pilot for the Harrier and Sea Harrier - Was selected by NASA after accumulating systems-level experience in combat, engineering evaluation, and cross-cultural flight testing To listen to this podcast ad-free and access premium episodes, try our subscription with a 14-day free trial at obomedia.com. © 2026 OBOMEDIA. All rights reserved. This episode and its content (audio, text, and related materials) are the exclusive property of OBOMEDIA and are protected by applicable copyright laws. Reproduction, distribution, editing, or commercial use, in whole or in part, without prior written permission from OBOMEDIA is prohibited. For permissions, licensing, and business inquiries: business@obomedia.com.

  8. Oct 19

    The Thirty-One Seconds That Saved Columbia From Exploding

    A space shuttle launch faces a critical engine failure, threatening an explosion on the pad. The crew is unaware of how close they are to disaster. The Thirty-One Seconds That Saved Columbia From Exploding This episode explores the near-catastrophic launch of the Space Shuttle Columbia on January 6, 1986, and the role of a payload specialist who spent years building the satellite it carried. It raises the question of what happens when a system designed to prevent failure barely catches it in time. Event: Space Shuttle Columbia launch attempt STS-61-C Date: January 6, 1986 Payload: Satcom Ku-one commercial communications satellite Person: Robert Cenker Status: Automatic hold triggered at T-minus 31 seconds - The automatic hold was triggered at T-minus 31 seconds, preventing an uncontrolled engine ignition. - 18,000 pounds of liquid oxygen had already drained from the external tank before the hold. - Robert Cenker, a satellite engineer, was a payload specialist on the mission, having spent 18 years building communications satellites like Satcom Ku-one. - Columbia's mission STS-61-C had accumulated seven scrubbed launch attempts before January 6, 1986. - The abort protocols were designed to catch complex system failures that were difficult to predict in full simulation. To listen to this podcast ad-free and access premium episodes, try our subscription with a 14-day free trial at obomedia.com. © 2026 OBOMEDIA. All rights reserved. This episode and its content (audio, text, and related materials) are the exclusive property of OBOMEDIA and are protected by applicable copyright laws. Reproduction, distribution, editing, or commercial use, in whole or in part, without prior written permission from OBOMEDIA is prohibited. For permissions, licensing, and business inquiries: business@obomedia.com.

See All (92)

About

Have you ever looked into the night sky and wondered what it actually took for humans to reach beyond it? Behind every launch is a chain of decisions, risks and discoveries that transformed distant worlds from points of light into places we could study. Space Exploration Stories follows the missions, breakthroughs and extraordinary moments that pushed exploration farther than anyone once thought possible. Each episode explores space missions, scientific discoveries and the people behind humanity’s journey beyond Earth. From ambitious engineering to unexpected challenges, the stories reveal how exploration advances through curiosity, persistence and calculated risk. The universe keeps giving us new questions faster than we can answer them—so what might the next mission discover that changes everything we thought we knew?

Information

  • Creator
    OBOMEDIA ENTERTAINMENT
  • Years Active
    2026
  • Episodes
    92
  • Rating
    Clean
  • Copyright
    © Copyright OBOMEDIA ENTERTAINMENT
  • Show Website
    Space Exploration Stories