SpaceX Did Something Never Done before on Booster V3 Test! Dream Chaser Incoming |SpaceWeekly#36 === 00:00: Intro 00:37: B19’s upcoming works 07:50: More tests or launch immediately 09:45: S39 11:23: Conclusion === #greatspacex#elonmusk#spacex#nasa == Advertisers who want to place ads on our channel, please contact the email manager: [email protected] === SpaceX Starship SN Be the first to sponsor us Thank you. https://www.patreon.com/GreatspaceX?fan_landing=true === SpaceX Did Something Never Done before on Booster V3 Test! Dream Chaser Incoming |SpaceWeekly#36 SpaceX has now confirmed what happened during the recent static fire test, after earlier results hinted at possible anomalies. Attention is already shifting to what comes next—the 33-engine test, which could mark a major step forward. At the same time, a disagreement is emerging between NASA and SpaceX over how Starship HLS should be operated, raising questions about the program’s direction. Meanwhile, Sierra Space has completed a runway landing test for Dream Chaser. Let’s break down the biggest developments of the week in this episode of Great SpaceX. SpaceX Did Something Never Done before on Booster V3 Test! Dream Chaser Incoming |SpaceWeekly#36 “Getting closer to Starship launch!” That’s the confident message from Elon Musk following the latest updates from SpaceX on Booster 19 testing. The next step is now confirmed—but the recent test also exposed a number of issues, both with the booster and the launch pad, that still need to be addressed. So what changes will be made in the weeks ahead? And will everything come together in time for an April launch of Starship? Let’s take a closer look in today’s episode of Great SpaceX. The recent engine test of the B19 had been a long time coming. Many were eager to see it in action, though in the end, the test’s power and duration didn’t fully meet expectations. SpaceX Did Something Never Done before on Booster V3 Test! Dream Chaser Incoming |SpaceWeekly#36 Right after the test, a few key signs hinted at what would happen next. The road closure schedule and the movement of the transport stand both suggested that B19 would soon return to the Production Site. That expectation was confirmed on the afternoon of March 17th, when the Chopsticks lifted B19 from the launch pad and placed it onto the transport stand. The moment created a striking visual—rows of Raptor 3 engines illuminated under the Starbase afternoon sun—offering a glimpse of the vehicle’s potential and building anticipation for what comes next. By the morning of March 18th, according to the road closure schedule, B19 had been rolled into Mega Bay. ---- We use images and content in accordance with the YouTube Fair Use copyright guidelines: https://www.youtube.com/intl/en/about/copyright/fair-use/ Any questions about copyright please send us via Gmail: [email protected] To be resolved, thank you.
AI Generated·May contain errors
SpaceX has now confirmed what happened during the recent static fire test after earlier
results hinted at possible anomalies.
Attention is already shifting to what comes next, the 33 engine test, which could mark
a major step forward.
At the same time, a disagreement is emerging between NASA and SpaceX over how Starship
HLS should be operated, raising questions about the program's direction.
Meanwhile, CRSpace has completed a runway landing test for Dream Chaser.
Let's break down the biggest developments of the week in this episode of Great SpaceX.
Getting closer to Starship launch, that's the confident message from Musk following
the latest updates from SpaceX on B19 testing.
The next step is now confirmed, but the recent test also exposed a number of issues, both
with the booster and the launch pad, that still need to be addressed.
So what changes will be made in the weeks ahead?
And will everything come together in time for an April launch of Starship?
The recent engine test of the B19 had been a long time coming.
Many were eager to see it in action, though in the end, the test's power and duration
didn't fully meet expectations.
Right after the test, a few key signs hinted at what would happen next.
The road closure schedule and the movement of the transport stand both suggested that
B19 would soon return to the production site.
That expectation was confirmed on the afternoon of March 17th, when the chopsticks lifted
B19 from the launch pad and placed it onto the transport stand.
The moment created a striking visual.
Rows of Raptor 3 engines illuminated under the starbase afternoon sun, offering a glimpse
of the vehicle's potential and building anticipation for what comes next.
By the morning of March 18th, according to the road closure schedule, B19 had been rolled
into Megabay.
There had been plenty of speculation about how this test would turn out.
Fortunately, SpaceX provided clear answers.
The company shared on X, initial Super Heavy V3 and Starbase Pad 2 activation campaign
complete, wrapping up several days of testing that loaded cryogenic fuel and oxidizer on
a V3 vehicle for the first time.
They also addressed the issue that cut the test short.
While the 10-engine static fire ended early due to a ground-side issue, we saw successful
startup on all installed Raptor 3 engines.
During the test, several unusual signs caught attention, irregular ignition timing and visible
marks on the booster.
These raised concerns, especially since B19 had previously been lifted off the platform
for engine sensor repairs.
At the time, it was reasonable to assume the vehicle itself might be the source of the
problem.
However, the latest update paints a different picture.
Despite those anomalies, the booster remained stable through multiple fueling tests and
even completed a short static fire.
The issue, it seems, came not from the vehicle but from the ground support equipment.
This likely involved a malfunction in a pipe or connection between the pad and the booster,
forcing SpaceX to end the test early to avoid further damage.
Considering this was the first time the new launch pad was operating under such demanding
conditions, like handling rapid refueling cycles and the intense output of Raptor 3,
the setback is understandable.
Looking ahead, the focus now shifts to the launch infrastructure.
SpaceX will need to carefully inspect and upgrade the GSE, including the tank farm,
pipelines, QD system, and connection interfaces.
These systems must not only handle peak performance but also support repeated use as launch cadence
increases.
If Flight 12 proceeds successfully, that pace could ramp up as early as this year.
Ideally, these repairs would be completed within about a week preparing the pad for
B19's return.
As for the booster itself, even though SpaceX reports no major issues, the unusual signs
seen during testing shouldn't be ignored.
Two anomalies stand out.
First, the static fire lasted only around 2 seconds, which is shorter than expected.
Just before ignition, sparks were visible, possibly indicating a leak interacting with
the ignition system.
Second, after ignition, a dark mark appeared near the liquid oxygen tank's chine area,
followed by venting from the same spot.
This raised concerns about a potential structural issue, especially since a similar area was
damaged in the B18 incident.
Even if these issues turn out to be minor, they require careful inspection and, if necessary,
repair.
Because of this, the next phase of testing for B19 may take some time.
If the igniter issue is isolated to a single engine, that engine can simply be replaced.
SpaceX has a full set of 33 engines available, however, if multiple engines are affected,
the situation becomes more complex and may require broader fixes, such as replacing igniters
or sealing potential leaks through welding.
This is where the design of Raptor 3 introduces both advantages and challenges.
The engine has been significantly simplified compared to earlier versions, reducing part
count and complexity, but that simplicity also makes certain repairs more difficult.
Components that were once easier to access and replace may now require cutting and welding
to fix, especially if the issue lies deep within the engine.
If the mark on the booster turns out to be structural damage, it'll need immediate
attention.
Even a small breach in the liquid oxygen tank area is a serious risk.
A leaked bear could ignite, leading to fire and potentially an explosion.
Liquid oxygen intensifies combustion, making such fires extremely difficult to control.
In the B18 incident, this exact region suffered the most severe damage, and nearby components
like engines and COPVs can make the situation even harder to manage.
Even in less extreme scenarios, a leak would still reduce efficiency by wasting fuel, ultimately
affecting both testing and launch performance.
To mitigate this, SpaceX may reinforce the affected area after repairs, possibly adding
structural support to improve resilience, and inspections won't be limited to visible
problem spots.
The entire vehicle will likely undergo a thorough review.
Overall, there's no immediate cause for alarm.
Unlike B18, this situation did not escalate into a major failure.
In fact, B19 has already demonstrated strong performance in several areas.
It successfully completed multiple fueling cycles, including rapid loading that filled
the liquid oxygen tank in just 30 minutes.
It also handled full cryogenic loading without issue.
These are strong indicators that the tank structure and overall design are sound.
Still, several components need closer examination.
The COPVs in V3 feature a new design intended to address earlier weaknesses, but they remain
a critical and somewhat unpredictable element.
Ensuring their reliability will be essential.
Internal systems such as fuel lines and pipelines also require validation.
While they performed well during initial tests, future operations will push them much harder.
With all 33 engines firing at higher thrust levels, the demand on these systems will increase
significantly, subjecting them to higher pressures than ever before.
Even engines outside of the suspected problem areas won't be overlooked.
Unlike Raptor 2, these engines lack heat shields, a deliberate choice by SpaceX to reduce weight,
based on confidence in the new design.
Still, with a first flight approaching, every component must be verified.
Once inspections are complete, attention will shift to final assembling.
This includes installing the remaining engines and potentially swapping out any that showed
signs of trouble.
Additional engines are expected to arrive at Megabase soon to support this process.
The lower section of the booster, the aft area, sometimes referred to as the skirt,
also remains unfinished.
Compared to earlier designs, it still needs protective panels to shield internal wiring
and piping.
Completing this section will be another important step.
Altogether, this phase of work will take time, likely closer to two weeks than one.
As a result, B-19's next move may not happen until the final days of March or early April.
After its work in Megabay, B-19 is set to move into one of its most anticipated milestones,
a full 33-engine static fire.
Earlier there were two possible paths for B-19, either proceed with a full 33-engine
test or skip it and move directly toward launch.
SpaceX has now made that decision clear.
In a recent update, the company confirmed,
Next up, preparing the booster for a 33-engine static fire.
It's a more cautious, methodical approach, one aimed at ensuring the mission's success
rather than rushing ahead.
The earlier 10-engine test, while valuable, only told part of the story.
With just 10 engines firing, the booster produced roughly 2,800 tons of thrust, a fraction of
the more than 9,000 tons expected from all 33 engines.
Just as important, the test lasted under 5 seconds, far too short to fully evaluate how
the engines performed together under sustained conditions.
A full-duration 33-engine static fire will change that.
It'll allow SpaceX to assess not only the raw power of the system, but also how well
the engines operate in unison, how the vehicle handles the stress, and whether any hidden
issues emerge under peak conditions.
At the same time, it'll push the launch pad to its limits, effectively testing whether
the ground systems can withstand and support the most powerful liftoff ever attempted.
The tradeoff, however, is time.
If inspections and engine installation take one to two weeks, this next test phase will
likely fall in early April.
From there, B-19 would need to return to Megabay for final checks and any additional work before
it's cleared for flight.
Taking all of this into account, Flight 12 may shift into the second half of April.
Even so, the overall timeline remains intact.
B-19 is progressing steadily, and while the launch may come slightly later than first
expected, an April liftoff is still within reach.
Of course, the overall schedule will still depend heavily on S-39.
While B-19 is undergoing inspections and installation work, S-39 may already be moving toward its
own static fire test.
It was rolled into Megabay 2 on the morning of March 8th, which means it has likely completed
initial checks by now, and may already have its engines installed.
The absence of visible engine deliveries at Megabay 2 could simply mean they arrived earlier
than expected.
Unlike B-19, which began testing with only six engines, S-39 is expected to receive its
full engine set from the start.
That means its static fire will likely be a full power test, producing more than 1,700
tons of thrust.
The burn duration could extend to around 10 seconds, providing a meaningful look at performance
under sustained conditions.
That said, there is precedent for even longer tests.
Earlier vehicles, such as S-34 and S-35, completed static fires lasting close to a full minute.
Applying that kind of duration to the first ship, V-3, would carry added risk, but it
also raises the question of how far SpaceX is willing to push this initial vehicle to
gather data.
If everything proceeds smoothly, S-39's test campaign could wrap up within March, allowing
it to transition to the next phase soon after.
If final checks and preparations stay within a one-to-two-week window, an early April launch
remains possible.
If delays arise, however, the timeline would likely shift into the second half of April.
The path to Flight 12 is shaping up to be a compelling one, with increasingly powerful
demonstrations of the new engine generation at every step.
Indeed, the road to launch is never simple.
But step-by-step, test-by-test, Starship is getting closer.
B-19 has faced its challenges, from unexpected cutoff to ground system issues.
But it's also proven something critical.
The foundation is strong.
The engines ignite, the tanks hold, the system works.
Now it's about refinement.
Next comes the moment we've all been waiting for, a full 33-engine static fire.
Over 9,000 tons of thrust, all unleashed at once.
A true glimpse of the power behind Starship's next leap.
And alongside it, S-39 is preparing to make its own statement, pushing the limits of what
this new generation can do.
So the question is no longer if Starship is ready, but when everything comes together.
If you want to follow every test, every breakthrough, and every step toward launch, make sure to
subscribe and stay tuned, because the next ignition could be the one that changes everything.
At last, the moment has arrived.
Booster V3, equipped with the latest Raptor engine, has completed a test firing at the
new launch pad.
However, a minor issue has surfaced, raising questions about its impact on upcoming plans.
It's been a long wait to see a Starship booster come to life again.
The last time SpaceX reached this stage was during Flight 11.
Now after more than 5 months, testing has resumed.
Though the result wasn't quite as powerful as many expected.
The planned road closures went ahead as scheduled, even with strong winds at the site.
On the morning of the 16th, before the main test window opened, SpaceX carried out a check
of the Detonation Suppression System, or DSS for short.
Around midday, the massive chopstick arms on the tower were lifted and opened, likely
to keep them clear of the wind ahead of the test.
By early afternoon, preparations were complete.
Fuel loading began at around 1pm central, following a familiar pattern.
The liquid oxygen tank was filled, along with a smaller amount of methane.
At approximately 1.42pm, the test began.
First, water surged through the flame trench to manage heat and pressure.
Then came a flash of ignition, followed by a burst of thrust.
Even with only 10 engines firing, B-19 can produce between 2,500 to 2,800 tons of force.
From a distance, thick clouds of dust could be seen blasting out from both ends of the
trench, a dramatic effect engineers had anticipated when designing the system.
Once the firing ended, the booster went through detanking, visible as frost on its surface
began to fade.
The chopstick arms were then lowered to secure the vehicle.
At first glance, the test appeared successful, but a closer look suggests something may not
have gone entirely as planned.
The firing itself was very short, likely under 5 seconds.
The dust clouds, while visible, quickly faded, partly due to the wind, but also because the
engines didn't run long enough to build a sustained plume.
This has led to speculation that SpaceX may have shut the test down early.
One possible explanation is an issue with one of the engines forcing an immediate abort.
Some analyses point to a brief but noticeable burst of sparks just before ignition.
While this can be normal during engine tests at SpaceX's McGregor facility, it's less
expected at the launch pad.
This raises the possibility of a small fuel leak, which may have ignited prematurely.
The size and clarity of the flash suggest it was more than routine, and it could have
posed a risk to the engines, prompting a quick shutdown.
There are also signs that the booster itself may have been affected.
Comparing images from before and after the test, a dark streak appears along one side
of B-19, something not seen prior to the firing.
In that same area, venting was observed afterward, which could indicate a leak caused by internal
stress or vibration during the test.
At this stage, it's still unclear how serious these issues are or what they mean for the
schedule.
What we do know is that B-19 is preparing for its next move, which is a rollout to the
megabay facility.
A contradiction, something that should not happen while the world is racing to return
humans to the moon.
Yet that is exactly the situation now unfolding between NASA and SpaceX, centered on concerns
about Starship HLS and its lunar landing plans.
So what exactly happened?
Who is right in this dispute, and could it affect SpaceX's role in the lunar program?
Unlike the last century, when NASA went to the moon on its own, today's return to the
lunar surface is built on collaboration between NASA and private companies.
Among the most important partners are SpaceX and Blue Origin.
For many years, NASA and SpaceX have worked closely together.
But recently, a disagreement has emerged, centered on how the Starship HLS should operate
during lunar landings.
The issue comes from a recent 50-page report released by NASA's Office of Inspector General
titled NASA's Management of the Human Landing System Contracts.
In the reports, NASA noted that while the agency has managed contract costs and maintained
strong cooperation with its partners, development challenges with the lunar landers could delay
planned Artemis launch dates.
The report also raises safety concerns.
It states that NASA is working to reduce potential hazards linked to the landers, but currently
does not have the ability to rescue astronauts if they were to become stranded in space or
on the lunar surface.
One of the central points of discussion involves how Starship HLS will be controlled during
landing, especially on missions carrying astronauts.
SpaceX's approach relies heavily on automation.
The company plans to apply systems similar to those used on Dragon spacecraft, where
many operations are handled automatically while astronauts monitor the process through
touchscreen interfaces.
This automated system would support key tasks such as docking with Orion and performing
the final landing on the moon.
NASA, however, has expressed strong reservations about relying too heavily on automation.
The agency prefers to ensure that astronauts have direct manual control over the spacecraft.
In the report, NASA explains the disagreement clearly.
NASA and SpaceX disagree on whether the provider is meeting the intents of the agency's manual
control requirement.
Incorporating the manual control capability is a key element of HLS's human rating certification
and part of an essential crew survival strategy.
NASA's concern appears to be growing.
The report adds that although SpaceX has acknowledged the requirement and committed to addressing
it, NASA's internal tracking suggests that the risk related to manual control is increasing.
Much of NASA's reasoning is based on lessons from past lunar missions.
During the Apollo program, astronauts played an active role in controlling the spacecraft,
particularly during the final moments of landing.
NASA believes that human involvement is critical when dealing with the moon's uneven and unpredictable
terrain.
The agency also pointed to more recent examples, such as a mission involving Boeing's Starliner
spacecraft, where astronauts had to switch to manual control to resolve a docking issue
at the ISS.
SpaceX has not yet issued a detailed response to the report, but the company's confidence
in automation is clear.
In the past, NASA relied heavily on manual control because automated systems were limited.
Computers of that era had very little processing power and could not adjust quickly to changing
conditions.
Human pilots were therefore essential to ensure safe operations.
Today, the situation is very different.
Modern computers are far more powerful, capable of processing vast amounts of data in real
time.
SpaceX has repeatedly demonstrated advanced automation through its rockets and spacecraft.
Falcon 9 boosters routinely perform precise vertical landings on land and on drone ships
at sea.
At Starbase, even more complex operations such as catching rockets with robotic arms
are being developed.
Meanwhile, Dragon spacecraft have completed dozens of automated dockings with the ISS,
carrying both cargo and astronauts.
In fact, a similar debate once occurred between NASA and SpaceX during the development of
Crew Dragon.
At the time, the two sides eventually reached a compromise.
Automated systems would handle most operations, while astronauts would retain the ability
to intervene if necessary.
However, the situation with Starship HLS is more complex.
The lander will need to dock with another spacecraft to transfer astronauts.
This will occur far from Earth, without the support systems available in low Earth orbit.
After that, the vehicle must descend to the moon's surface, where terrain conditions
can vary greatly.
The size of Starship also raises concerns.
The vehicle stands about 50 meters tall, but is only 9 meters wide.
This tall, narrow design has led some experts to worry about stability during landing, especially
on uneven ground.
Even in everyday life, it's easy to see how a tall, narrow object can be less stable
than one that is wider or longer.
Because of these factors, NASA believes astronauts should have the ability to take direct control
if needed.
At the same time, manual control does not eliminate risk.
Landing a spacecraft involves coordinating many systems at once.
Thrusters, landing legs, guidance systems, and attitude control.
Managing all of these elements with precision could be extremely difficult for astronauts
without significant assistance from automated software.
Interestingly, while the report raises concerns about SpaceX's approach, it does not provide
clear evidence that manual control would be safer than the automated systems SpaceX proposes.
The report also highlights another challenge, the lander's elevator.
Because Starship HLS is so tall, astronauts will need to use an elevator to travel between
the lunar surface and the crew cabin high above.
While the system has already undergone testing, NASA still considers it a potential risk.
The report notes that if the elevator were to fail, there is currently no alternate way
for astronauts to re-enter the spacecraft from the lunar surface.
For that reason, the HLS program is working with SpaceX to explore backup methods that
could allow the crew to climb aboard if the elevator becomes stuck or stops working.
In the end, both NASA and SpaceX are relying on their own experience.
NASA draws on decades of human spaceflight and lessons from past missions to the moon.
SpaceX, on the other hand, is building on more recent advances in automation and reusable
rocket technology.
For now, the debate continues, but ideally, it will lead not to conflict, but to improvements
that make the lunar mission safer and more reliable.
So what do you think?
Which approach makes more sense for landing on the moon?
Manual control or automated systems?
Let me know your thoughts in the comment section down below and don't forget to like the
video and subscribe as we continue following SpaceX's journey toward the moon.
Now after discussing operational concerns, we also need to consider the schedule.
In its report, NASA highlighted another major issue, and that is timing.
The agency noted that both SpaceX and Blue Origin have faced delays and technical challenges,
which could raise costs and push back delivery times.
NASA also stated that SpaceX's lunar lander is unlikely to be ready for a crewed landing
by June 2027.
Importantly, this criticism applies to both contractors, not just SpaceX.
NASA's assessment likely reflects the current stage of the Starship program.
Although SpaceX received the HLS contract several years ago, the Starship HLS version
has not yet been formally introduced.
So far, only concept images and design updates have been released.
At the same time, the broader Starship program is still moving toward its next phase, with
much of the effort focused on the V3 design planned for this year.
However, the first V3 flight has not yet taken place.
Because of this uncertainty, NASA is reviewing possible schedule adjustments.
The agency said it is studying proposals from both SpaceX and Blue Origin to speed up lander
development for a potential lunar landing in 2028.
However, officials emphasized that it is still too early to determine whether these plans
are feasible, how much they might cost, or how they would affect the timeline.
It's also important to recognize the scale of what SpaceX is attempting to build.
Starship is designed for frequent launches, rapid turnaround, and full reusability, while
carrying more payload than any launch vehicle before it.
If successful, this capability could reshape how missions to the moon and beyond are conducted.
At the same time, delays are becoming harder to ignore.
Starship HLS missions were originally expected to begin earlier, and the program now faces
increasing pressure to demonstrate progress.
The flights planned for this year will be especially important as SpaceX must prove
key capabilities before moving on to more complex goals such as in-orbit refueling.
The urgency has also increased as the Artemis mission plan has evolved.
Originally, Artemis III was intended to land astronauts on the moon using Starship HLS.
Now the mission is expected to focus on a docking demonstration in Earth orbit rather
than a lunar landing.
Although that mission sounds less demanding, it could still play an important role.
It would allow SpaceX to demonstrate Starship's capabilities and strengthen its position in
the competition with Blue Origin for future landing missions.
The actual crewed lunar landing has now been pushed to 2028 when two separate missions
are planned.
At first glance, this delay might seem to give SpaceX more time.
In reality, the pressure may be even greater.
To take part in those missions, SpaceX may need two operational landers ready before
2028.
Another uncertainty remains, and that is whether or not it's still going to involve cooperation
between SpaceX and Blue Origin, or will it be a direct competition.
In either case, SpaceX will need to show steady progress soon.
At this stage, results are essential not only for the schedule but also for maintaining
confidence in the mission itself.
The Artemis program is clearly entering a period of major change.
After years of progress that many considered slow or inefficient, both completed and unfinished
efforts are now being reassessed.
As a result, several systems and approaches that proved ineffective are being reconsidered,
replaced or removed entirely.
Attention is now turning toward one of the most debated elements of the program, the
schedule and the operational design of Starship HLS.
For SpaceX, the timeline will be something that must be demonstrated through real progress
this year.
Concrete milestones, visible testing, and greater transparency will all play an important
role in proving that the program can stay on track.
At the same time, the debate over how the landers should operate remains unresolved.
Should astronauts rely primarily on manual control or should the system be largely automated?
The answer may ultimately involve a combination of both.
NASA and SpaceX will likely need extensive analysis and possibly real-world testing before
reaching a final decision.
Despite these debates, SpaceX's role in the Artemis program remains central.
The company's technology and rapid development approach could significantly influence how
quickly the United States returns to the moon and how effectively it competes with
other space powers in the coming years.
What matters most now is demonstrating readiness.
SpaceX will need to show that its systems can perform as promised and support the demanding
goals of the Artemis program.
And the story is far from over.
As deadlines approach and international competition increases, especially from China, further
adjustments to the program are likely.
In the end, these debates may actually strengthen the Artemis effort, pushing the program to
become more efficient, more capable, and better prepared for the challenges of returning to
the moon and exploring beyond.
Stay tuned as we continue following every development.
For years, one question has followed Dream Chaser.
When will it finally launch?
The lifting-body spacecraft has promised a new era of orbital access, blending the precision
of an airplane with the power of a rocket.
Yet development delays and rigorous testing kept that first flight just out of reach.
Now that timeline appears closer than ever.
NASA and Sierra Space recently completed a critical runway landing test, a major milestone
that validates the vehicle's approach and landing performance ahead of flight.
The test demonstrated aerodynamic stability, guidance accuracy, and the spacecraft's ability
to touch down smoothly on a conventional runway, a capability that sets it apart from traditional
capsules.
How significant was this test?
When will Dream Chaser make its debut mission?
And what opportunities and technical challenges lie ahead as it prepares to serve NASA's cargo
needs in low-Earth orbit?
Runway landings are routine in commercial aviation.
In spaceflight, however, they are rare.
The most prominent example was the Space Shuttle, which returned from orbit and glided to a
horizontal landing.
Now, Dream Chaser is preparing to follow that same operational model.
NASA and Sierra Space recently completed a high-speed runway landing test at Kennedy
Space Center.
Footage shared on X and YouTube shows Dream Chaser being towed down one of the facility's
longest runways by a fifth-generation Freightliner Cascadia truck.
The towing system connects to the vehicle's nose through an intermediate frame, providing
stability and balanced wheel contact during acceleration.
This test configuration highlights an important design difference.
Unlike the Space Shuttle, Dream Chaser does not use a traditional nose wheel.
While it employs a tricycle-style landing architecture, the forward section uses a skid
rather than a tire.
This approach reduces mass, eliminates concerns about tire performance in the space environment,
and simplifies the system.
During landing, controlled friction at the nose aids deceleration and stability.
According to Sierra Space, the vehicle endured high-speed testing conditions comparable to
those expected during actual runway touchdown.
The objective was to simulate landing dynamics and validate autonomous navigation parameters.
These tests help confirm how the spacecraft will track the runway centerline, manage rollout
stability, and coordinate braking systems after contact.
However, a runway tow test represents only part of the landing sequence.
A true mission will require atmospheric re-entry from orbit, hypersonic deceleration, thermal
protection performance, guided descent, and energy management before final approach.
Those phases introduce aerodynamic forces and heating environments that cannot be fully
replicated in a ground-based towing scenario.
Re-entry validation will occur during flight.
The first mission, designated SSC Demo-1, is currently scheduled for later this year.
The spacecraft will launch aboard a Vulcan Centaur operated by ULA.
According to NASA's revised plans, the mission will be a free-flyer demonstration in low-Earth
orbit without docking to the International Space Station.
After completing its objectives, Dream Chaser will re-enter and attempt a full runway landing,
providing a comprehensive end-to-end systems validation.
Beyond runway testing, NASA and Sierra Space have also conducted communications checks
with Mission Control in Louisville, Colorado using NASA's Satellite Relay Network.
These exercises included a full post-landing recovery rehearsal, ensuring that ground teams
can safely secure and process the vehicle after touchdown.
Significant work remains.
Re-entry, autonomous guidance, and integrated mission operations must still be proven in
flight, yet the recent runway test marks a critical milestone.
It demonstrates that Dream Chaser's landing systems, ground handling procedures, and recovery
planning are advancing toward operational readiness.
If successful, Dream Chaser will re-introduce routine runway landings to orbital missions,
combining spacecraft capability with aircraft-style recovery in a way not seen since the Shuttle
era.
Dream Chaser could become one of the most versatile spacecraft in service.
Unlike traditional capsule-based vehicles, Dream Chaser is a lifting-body spaceplane
inspired by the Space Shuttle, but redesigned with modern materials and simplified systems.
It measures roughly 9 meters in length and 4.5 meters in width, making it significantly
smaller than the Shuttle.
Its wingspan extends to about 7 meters, and notably, its wings can fold to fit inside
a launch vehicle fairing.
This provides aerodynamic protection during ascent and reduces exposure compared to externally
mounted spacecraft.
The vehicle has a dry mass of approximately 9 tons.
When paired with its expendable Shooting Star cargo module, it can deliver about 5-6 tons
of cargo to low-Earth orbit.
In a crewed configuration, it's designed to carry up to 7 astronauts.
One of Dream Chaser's most distinctive advantages is its runway landing capability.
Unlike parachute-assisted ocean splashdowns or land touchdowns under airbags, Dream Chaser
performs a controlled horizontal landing.
The spacecraft is engineered to touch down at forces below 1.5 Gs, reducing stress on
astronauts and sensitive cargo.
Avoiding ocean recovery also eliminates saltwater corrosion and minimizes post-landing refurbishment
requirements.
Runway landings offer operational efficiency.
The vehicle can return directly to a prepared facility, allowing ground crews immediate
access for inspection and turnaround.
This reduces logistical delays compared to spacecraft that land far from refurbishment
centers.
Additionally, the ability to use multiple suitable runways introduces mission flexibility.
Alternate landing sites can be selected if weather or operational constraints arise.
These characteristics align closely with NASA's current needs.
The agency has relied heavily on SpaceX Dragon 2 due to ongoing challenges with Boeing's
Starliner and uncertainties surrounding cargo providers.
While Dragon has demonstrated reliability and cost efficiency, NASA maintains a strategic
preference for redundancy.
A second operational provider strengthens resilience and ensures continued access to
orbit if one system encounters delays.
Dream Chaser enters this environment at a critical time.
Confidence in alternative crew vehicles has fluctuated, and cargo logistics remain a priority
for sustaining orbital operations.
If Dream Chaser proves reliable, it could assume roles in both crew transport and cargo
resupply.
Beyond government missions, the commercial sector presents further opportunity.
Sierra Space is developing Orbital Reef, a commercial space station concept.
Owning both the station architecture and the transportation system creates vertical integration,
reducing dependence on external launch providers, and expanding mission autonomy.
The convergence of technical capability, operational efficiency, and market timing positions Dream
Chaser strategically.
Its runway recovery model, cargo flexibility, and compatibility with emerging commercial
platforms give it a distinct niche in the evolving low-Earth orbit economy.
The opportunity ahead is substantial.
Execution will determine whether Dream Chaser becomes a complementary partner in orbital
transportation or a central pillar of the next phase of space operations.
Dream Chaser faces substantial challenges, making its promise to prior commitments difficult
to uphold.
The most visible issue is schedule delay.
The vehicle was completed in late 2023 and originally targeted for launch in early 2024.
It's now tracking no earlier than the end of this year, placing it more than two years
behind its initial timeline.
In commercial spaceflight, time is market share, delays weaken competitive positioning
and compress future mission opportunities.
Mission success is critical.
The first flight must validate ascent on-orbit operations, re-entry, and runway landing without
major anomalies.
Only a fully successful demonstration will enable NASA to confidently assign regular
resupply missions.
A high-profile failure would significantly reduce Dream Chaser's prospects of supporting
the International Space Station.
Program sequencing adds further complexity.
The first mission is a systems demonstration.
The second vehicle, Reverence, is configured for cargo operations, not crew.
A crew-capable variant represents a later development phase, and its progress remains
less defined.
This staging means that even under optimistic scenarios, human spaceflight applications
remain years away.
Launch vehicle dependency is another constraint.
Dream Chaser is scheduled to fly aboard Vulcan Centaur from United Launch Alliance.
Vulcan itself required multiple flights to achieve certification and must balance national
security launches and commercial commitments.
Its production cadence and fully expendable architecture limit flexibility.
If launch availability becomes constrained, Dream Chaser's operational tempo could suffer
regardless of spacecraft readiness.
Technical tradeoffs also carry risk.
Unlike capsule systems that rely on parachutes, Dream Chaser uses a lifting body design and
runway landing profile.
This requires a comprehensive thermal protection system across the vehicle's underside, as
well as the leading edges.
Heat shield integration adds mass and inspection complexity.
While runway landings offer low g-forces and rapid recovery, they demand precise guidance
and runway availability.
Any deviation during landing introduces risk to nearby infrastructure and personnel.
In short, Sierra Space must demonstrate not only technical viability, but also schedule
discipline and operational reliability.
To become a consistent provider for NASA and future commercial platforms, Dream Chaser
must execute its debut mission flawlessly and transition rapidly into repeatable service.
The opportunity is significant, but so are the hurdles that remain.
Despite the obstacles, Sierra Space continues to make measurable progress.
The recent runway landing test marked the first time in years that a modern space plane
publicly demonstrated its landing profile.
In doing so, Dream Chaser revived an operational model last seen with the Space Shuttle.
That symbolism matters, but the technical validation matters more.
High-speed rollout testing confirms guidance, braking, structural loads, and ground recovery
procedures ahead of flight.
More importantly, the test signals readiness to transition from development to execution.
Dream Chaser's debut mission must validate ascent, orbital performance, re-entry, and
runway landing in one integrated sequence.
After repeated schedule shifts, only a successful flight will restore confidence among stakeholders
and customers.
Yet preparation does not end with a successful test campaign.
Before liftoff, Sierra Space must ensure full system integration, launch vehicle coordination,
and mission operations readiness.
After landing, it must demonstrate efficient inspection and refurbishment cycles.
A viable spacecraft is not defined by one successful mission, but by repeatability and
operational cadence.
This year represents a decisive inflection point.
If Dream Chaser performs as designed, it unlocks expanded cargo roles, potential crew applications,
and commercial station support.
If it falls short, recovery will be far more difficult in an increasingly competitive orbital
market.
The runway landing test established a foundation.
The upcoming flight will determine whether that foundation supports a sustainable future.
And that brings us to the end of today's episode.
Thank you so much for tuning in.
As always, this has been Kevin with Great Space X.
Until next time, keep looking up!