Detailed Summary:
SpaceX Starship Launch Discussion
The group discussed SpaceX’s recent Starship launch, which John described as a partial success with significant technical challenges including an engine outage that caused the booster to deviate from its course. David praised the high-quality camera work and photography during the launch, while Dr. Sherry noted that SpaceX itself considered the mission a success and emphasized their approach of learning from mistakes. The team also explained the satellite ejection mechanism used in the launch, with Charles and Robert providing details about how the satellites were deployed from the rocket.
The group discussed SpaceX’s Starship Flight 12 (IFT-12), with participants evaluating its significance for future Artemis missions. Bob explained that while the flight was important for testing new engines and systems, it wasn’t critical for SpaceX’s overall success, particularly given their upcoming IPO and existing Starlink revenue. The discussion highlighted the technical challenges involved in the flight, including new Raptor 3 engines and a rebuilt launch pad, with participants agreeing that the flight achieved its main objectives of reaching orbit and conducting necessary tests.
The Wisdom Team discussed the recent Starship test flight, comparing it to SLS development and emphasizing that the technologies are not comparable due to different approaches and goals. David defended SpaceX’s methodology of learning from failures, while Ajay highlighted specific technical issues with the first stage during the test. The discussion included observations about engine problems and a puncture in the tile, with participants noting that this is part of the development process for new technology.
The group discussed the recent SpaceX Starship test flight, with Dr. Ajay clarifying that one engine blew up before separation, causing other engines to shut down due to fuel sloshing. Phil expressed concerns about the program’s timeline, arguing that SpaceX is not on track to meet the goal of reaching the moon within a couple of years, while Robert countered that abandoning the current approach would only cause further delays. The discussion concluded with Dallas defending the mission’s success in achieving its suborbital trajectory goals, though Phil maintained that the program has not yet proven its ability to deliver the required 100 tons of payload to orbit.
The team discussed SpaceX’s satellite deployment program, with Marshall clarifying that dummy satellites weighed about 2 tons each but Phil found conflicting information suggesting 17 tons total for 22 satellites. The discussion then shifted to refueling capabilities, where Doug shared insights from a leading researcher who estimated a 50% chance of success on the first attempt and near 100% on the second attempt for propellant docking and transfer. The conversation concluded with Ajay noting that while Progress has done fuel transfer with storable fuel, cryogenic fuel transfer remains untested in orbit, though SpaceX had previously demonstrated cryogenic propellant transfer during IFT-10.
The group discussed SpaceX’s development of in-orbit refueling capabilities, with Dallas sharing details about their 2008 demonstration using vapor-cooled skins and a crawl cooler from Criari. The discussion focused on comparing SpaceX’s progress with Blue Origin’s approach, with Robert noting that while SpaceX has outlined plans for a several-week refueling mission this year involving two Starship launches, Blue Origin’s development pace remains slower. The conversation concluded with debate about propellant requirements for lunar missions, with Dallas explaining that the HLS mission would need approximately 40 tons of propellant for the Gateway and lunar lander in the lunar vicinity.
Phil suggested that NASA should design the optimal lunar lander and then assign contracts to commercial companies like Boeing or SpaceX for manufacturing, while also working to reduce the cost of SLS rockets through mass production. Robert clarified that NASA’s investment in SpaceX’s Starship program is minimal compared to SpaceX’s private funding, which includes $12 billion raised for Starlink and an expected $75 billion from an IPO. The discussion highlighted concerns about Starship’s timeline and feasibility, with participants noting that alternative approaches using existing technology like SLS and a modified lander could potentially be faster than Starship development, though still facing significant challenges.
Robert discussed the challenges with NASA’s rocket development programs, highlighting that despite being 16 years since launch, they have only launched twice and suggesting that competition from multiple companies would be beneficial. Phil argued that NASA should handle advanced projects internally due to their track record of successful first-time launches, while Dallas clarified that NASA did not design the SLS but served as system integrator. David raised concerns about safety risks in human spaceflight programs, citing a former Artemis team engineer’s warnings about discontinuity in systems engineering when switching between commercial companies, which Marshall supported by noting that most bugs occur at interfaces between different components or companies.
The group discussed software engineering interfaces and their impact on system safety, particularly comparing Apollo and Artemis programs. Marshall and Ajay explained that while multiple companies building different components can create interface challenges, proper system engineering and testing can mitigate these risks. Robert emphasized that Artemis’s current issues stem from lack of overall NASA-designed architecture and distributed ownership, suggesting NASA should consolidate components and hire companies to build major components with fewer interfaces. Doug cautioned against attributing 90% of problems to interfaces alone, noting that known issues in NASA’s culture contributed to previous shuttle program losses.
The discussion focused on comparing NASA’s Apollo-style approach with SpaceX’s commercial approach for returning to the moon. Doug and Charles argued that the commercial approach using Starship offers better long-term sustainability and permanence on the moon compared to the Apollo-style urgency-driven approach using SLS and Orion. Philip countered that Starship is not necessarily the permanent solution and that a racal departure from rocket technology might be needed for true permanence. The conversation also highlighted that SpaceX’s Starship development represents a smaller portion of their overall investment compared to their other projects like Starlink, with Starship serving as a transportation system to support broader capabilities.
The group discussed the evolution of chemical rockets and reusability, with Phil and Doug clarifying that full reusability is not a revolutionary change compared to the space shuttle. David challenged critics like Phil and AJ to support the current Artemis program rather than continuously criticize it, asking what constructive role they could play given the program’s commitment to Starship and Artemis missions. Ajay expressed support for the Artemis program overall but raised concerns about Starship’s size and propellant fraction requirements, suggesting it should be reduced to about one-third its current size for lunar missions. Phil shared insights from his recent presentation at Ascend, noting that NASA engineers lack access to critical technical details about Starship’s development, similar to the broader public’s understanding of the program.
The group discussed concerns about NASA’s involvement and insight into SpaceX’s Starship program, with Philip expressing concerns that NASA’s team lacks sufficient information to properly assess Starship’s performance and safety. The discussion revealed that while NASA has embedded engineering teams with SpaceX and extensive visibility into various aspects of development, they don’t have complete control over architectural decisions. The conversation ended with John mentioning SpaceX’s improvements to the launch site and Raptor 3 engine, and Sherry praising the video footage of Starlink satellites in space.
The group discussed SpaceX’s achievements and role in the space industry, with participants praising their rideshare and Starlink initiatives while expressing concerns about relying too heavily on Starship for the Artemis program. Phil suggested reassessing NASA’s lunar landing strategy by considering alternative solutions like using Falcon Heavy or smaller landers from companies like Dynetics or Blue Origin. The conversation ended with Robert promoting an upcoming Space Show discussion and David reflecting on Memorial Day, thanking veterans for their service and contributions to space exploration.
Special thanks to our sponsors:American Institute of Aeronautics and Astronautics, Helix Space in Luxembourg, Celestis Memorial Spaceflights, Astrox Corporation, Dr. Haym Benaroya of Rutgers University, The Space Settlement Progress Blog by John Jossy, The Atlantis Project, and Artless Entertainment
We use Zoom phone numbers for program participation.
For real time program participation, email Dr. Space at: drspace@thespaceshow.com for instructions and access.
The Space Show is a non-profit 501C3 through its parent, One Giant Leap Foundation, Inc. To donate via Pay Pal, use:
To donate with Zelle, use the email address: david@onegiantleapfoundation.org.
If you prefer donating with a check, please make the check payable to One Giant Leap Foundation and mail to:
One Giant Leap Foundation, 11035 Lavender Hill Drive Ste. 160-306 Las Vegas, NV 89135
Upcoming Programs:
Broadcast 4594: Zoom: Bob Zimmerman (Special 6 PM PDT start time) | Tuesday 26 May 2026 600PM PT
Guests: Robert Zimmerman
Zoom: (6 PM PDT Start Time) Bob Zimmerman is back on Starship and all space matters. Don’t miss it! to Listen and participate use Zoom phone lines. Email DrSpace before airtime for the number access.
Broadcast 4595: Hotel Mars TBD | Wednesday 27 May 2026 930AM PT
Guests: John Batchelor, Dr. David Livingston
Hotel Mars TBD
No Program for Friday, May 29, 2026 | Friday 29 May 2026 930AM PT
Guests: Dr. David Livingston
No program today, Friday, May 26, 2026
Broadcast 4596: Zoom: Open Lines Discussion | Sunday 31 May 2026 1200PM PT
Guests: Dr. David Livingston
Zoom: Open Lines Discussion. Email DrSpace prior to air time for Zoom phone number access.
