Contacts
Info
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...
show more
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?
show less
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?
Episodes & Posts
Episodes
Posts
3 NOV 2026 · A shuttle commander watches onboard computers cut engines on the pad, then faces a pad fire and emergency evacuation-did they make it in time?
The onboard computer cut engines four seconds into ignition and forced an abort
In this episode, we follow Michael Lloyd Lloyd from decorated naval aviator to NASA astronaut as a launch abort on T-minus four seconds forces an unprecedented shutdown and a pad fire. The episode traces the buildup to that aborted launch and asks what the record reveals about risk, decision-making, and the crew’s next moves.
Person: Michael Lloyd Lloyd
Date: June 26, 1984
Event: Shuttle launch abort at T-minus 4 seconds
Location: Kennedy Space Center launchpad
Mission: STS-41-D
- Lloyd logged 315 combat departures and earned 32 Strike Flight Air Medals before age 27, a career built on repetition and precision.
- He accumulated 5,000 flight hours, 28 aircraft types, and 400 carrier landings before joining NASA’s astronaut class of 1978.
- Assigned to command STS-41-D after years as CAPCOM and support crew, Lloyd had been training for his first flight for six years.
- On June 26, 1984 the main engines ignited, then onboard computers detected an anomaly and initiated a shutdown four seconds into ignition.
- An unburned hydrogen residue ignited at the base of the launch structure, damaging the pad and forcing crew evacuation and mission delay. 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 NOV 2026 · A teacher-turned-astronaut braces on a handrail two hundred fifty miles up as a single bolt stalls a spacewalk. Will they make it in time?
The handrail bolt that stalled a six-hour spacewalk clock
In this episode, we follow Joseph Acaba from classrooms and field labs to the vacuum outside the International Space Station, tracing the skills he brought to a stalled spacewalk. What did a cart and a rail have to do with keeping the station powered?
Person: Joseph Acaba
Date: March 17, 2009
Event: Spacewalk to move a cart along a rail on the ISS
Mission: STS-119 / installation of the S6 truss segment
Training programs: NEEMO undersea habitat; ESA CAVES program
- Acaba spent six hours and twenty-seven minutes outside the ISS working on a cart along a rail two hundred fifty miles above Earth.
- His background moved from a Bachelor of Science in Accounting to a master's in geology and years teaching middle school in Morocco, Saudi Arabia, Indonesia, and Romania.
- He worked at Horn Point Laboratory on biostratigraphy, pulling sediment cores and reading environmental change in layers.
- NASA selected him in 2004; his training included a twelve-day NEEMO mission living in the Aquarius undersea habitat and six nights in Sardinian caves with ESA CAVES.
- The shuttle Discovery launched March 15, 2009 carrying the S6 truss segment-new solar arrays intended to complete the station’s power-generating backbone. 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.
1 NOV 2026 · A spider named Arabella spins a web aboard a crippled Skylab while engineers race to prove a half-disabled Apollo can bring three men home.
The Spider's Web Held the Clock That Saved Skylab
In this episode, we follow the sequence of events aboard Skylab in 1973: a damaged station, a cramped crew, a student experiment, and a failing return vehicle. What choices and calculations did NASA make while a spider kept weaving above Earth?
Person: Arabella
Event: Skylab second crew mission
Date: 1973
Location: Skylab, 435 kilometers above Earth
- Arabella and another garden spider, Anita, were part of a student-proposed experiment to test orb-weaving without gravity.
- Skylab launched unmanned on May 14, 1973; a micrometeorite and debris shield tore away 73 seconds after launch, costing one solar panel and jamming another.
- The first crew deployed an improvised parasol sunshade through an airlock to lower internal temperatures and stabilize power.
- Commander Alan Bean, Owen Garriott, and Jack Lousma launched July 28, 1973 for a planned 59-day mission that included solar physics and medical experiments.
- During docking and the first six days, two of four thruster quads on the Apollo command module developed propellant leaks, forcing engineers to compute whether reentry with only two quads was survivable. 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.
31 OCT 2026 · One hundred and eighty thousand miles from solid ground, a man in a spacesuit floats free to retrieve a film cassette. His spaceflight record hinges on this critical task.
The film cassette he pushed out of the hatch decided whether they made it
This episode explores the story of Ron Evans and his unprecedented spacewalk, detailing the circumstances that led to this historic moment and the personal journey of a man often overlooked by history. It delves into the significance of his actions and the true stakes involved in his hour outside the spacecraft.
Person: Ron Evans
Date: December 17, 1972
Location: 180,000 miles from any solid ground
Event: Spacewalk to retrieve a film cassette
- Ron Evans performed a spacewalk 180,000 miles from any planetary body, a record that still stands.
- Before his astronaut selection, Evans survived an electrical failure that locked a live bomb under his aircraft during a combat mission.
- He was initially rejected by NASA in 1963 but later selected in 1966 for Group Five.
- Evans served as a Capcom for Apollo Seven, Eleven, and Fourteen, communicating with crews going to the Moon.
- He was assigned as Command Module Pilot for Apollo Seven, orbiting the Moon while his crewmates landed. 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.
30 OCT 2026 · Diagnostic cameras on Discovery's external tank captured cracking metal - why did the shuttle's final flight keep being delayed?
The cameras that stayed on Discovery showed it cracking
This episode details the challenges faced by Space Shuttle Discovery during its final mission, STS-133, as engineers race against time to address unprecedented issues. It explores the series of technical problems that threatened to ground the most experienced spacecraft ever built.
Mission: STS-133
Spacecraft: Space Shuttle Discovery
Original Launch Date: September 16, 2010
Actual Launch Date: February 24, 2011
Crew: Six astronauts
- Engineers bolted diagnostic cameras to Discovery's external fuel tank to monitor cracking during the countdown, intending to remove them before launch.
- The STS-133 mission, also known as Utilization and Logistics Flight Five, was tasked with delivering the Leonardo Permanent Multipurpose Module.
- Delays began with a monomethyl hydrazine leak detected by a "fishy smell" from the Orbital Maneuvering System propellant line.
- A subsequent hydrogen leak at the Ground Umbilical Carrier Plate stopped fueling, revealing an internal seal compression issue.
- Inspection teams later found cracks in the spray-on foam insulation and two nine-inch cracks in stringer S-72, one of the tank's aluminum-lithium ribs. 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.
29 OCT 2026 · A sailor towed a lost Space Shuttle external tank from a hurricane - seven months later it faced a courtroom fight. Did they make it in time?
The towline a sailor threw saved ET‑70 - and bought him a house in time
In this episode, we follow the chain of events linking a November hurricane, a maritime salvage case, and NASA’s first Shuttle‑Mir docking mission. The episode traces the decisions, engineering limits, and human moves that had to hold together for ET‑70 and Atlantis to make a rendezvous in orbit.
Person: Robert Gibson
Event: STS‑71 (Shuttle‑Mir docking mission)
Object: ET‑70 external tank
Date: November 1994 (hurricane), mid‑1995 (launch)
Location: Atlantic Ocean (salvage), Mir/Low Earth Orbit
- A tanker crew on the Cherry Valley found and towed the orange external tank adrift after Hurricane Gordon swept it from a barge.
- NASA filed a salvage claim that led to a courtroom fight; a judge initially awarded $6.4 million, later reduced on appeal to $4.125 million.
- One sailor split his share with crewmates and used his portion to buy a house he called “the house that NASA bought.”
- Engineers prepared a manual R‑Bar approach requiring the shuttle to close at 33 millimeters per second when Robert Gibson took control at 800 meters.
- Atlantis and Mir had to rendezvous with tolerances measured in millimeters while both tumbled together at orbital velocity. 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.
28 OCT 2026 · An astronaut crew fights to stop Columbia on a White Sands runway as speedbrakes oscillate during a high-speed landing - did they make it in time?
The speedbrakes oscillated and forced Columbia to stop by inches
In this episode, we follow the final minutes of STS-3’s landing at White Sands where the shuttle’s systems, the incomplete autoland software, and the crew’s split roles collide. What choices and improvisations did Jack Lousma and Gordon Fullerton make as the approach became the only shot at bringing Columbia safely to a stop?
Person: Jack Lousma
Person: Gordon Fullerton
Event: Landing at White Sands
Date: March 30, 1982
Topic: Autoland system limitations
- The autoland software was aboard Columbia to collect data but was not capable of an autonomous safe stop.
- Kennedy Space Center was ruled out because the runway was wet; Edwards exceeded wind limits, leaving White Sands as the sole option.
- At 46 meters altitude the landing gear deployed with Columbia traveling 509 km/h, turning the approach into a high-energy final.
- The crew’s division of duties-Lousma managing energy from the left seat, Fullerton calling the runway from the right-shaped real-time responses.
- White Sands’ gypsum dust penetrated tiles and cavities, creating an unexpected physical and technical complication during and after landing. 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.
27 OCT 2026 · A sample-return capsule lands in the Australian desert with asteroid rocks, and the Hayabusa2 team races the clock. Did they make it in time?
The boulder-strewn surface that shrank their departure window to a race against fuel
In this episode, we follow the Hayabusa2 mission from proposal to arrival at asteroid Ryugu and the sudden discovery that upends plans. What choices did the team make when Ryugu's surface proved far rockier than expected, and how did a tightening departure window change everything?
Person: Makoto Yoshikawa
Date: December 5, 2020
Event: Sample return capsule landing at Woomera Test Range
Spacecraft: Hayabusa2
Target: Asteroid 162173 Ryugu
- Yoshikawa proposed a follow-up mission to Hayabusa with a more distant target, a complex sampling sequence, and an impactor, winning approval in August 2010.
- The mission budget was set at 16.4 billion yen, roughly $149 million at the time of estimation.
- Hayabusa2 launched December 3, 2014, used four ion engines producing ~28 millinewtons each, and performed an Earth gravity assist in December 2015.
- Ryugu arrived June 27, 2018, and imagery revealed a surface densely covered in multi-meter boulders, not the flat terrain the team expected.
- The densely boulder-strewn surface forced months of extra reconnaissance and delayed the first sampling attempt, narrowing a fixed departure window tied to orbital mechanics and fuel. 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.
26 OCT 2026 · 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.
25 OCT 2026 · 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.
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...
show more
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?
show less
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
| Author | OBOMEDIA ENTERTAINMENT |
| Organization | OBOMEDIA ENTERTAINMENT |
| Categories | Astronomy , History , Society & Culture |
| Website | - |
| creators@obomedia.com |
Copyright 2026 - Spreaker Inc. an iHeartMedia Company
