Adapted by:
Matías S. Zavia
WriterAerospace and energy industries journalist at Xataka.
Alba Mora
WriterAn established tech journalist, I entered the world of consumer tech by chance in 2018. In my writing and translating career, I've also covered a diverse range of topics, including entertainment, travel, science, and the economy.
Starship’s eighth flight was intended to be a repeat of the previous launch, which SpaceX was unable to complete due to the spacecraft disintegrating over the Atlantic Ocean. Unfortunately, the same outcome happened again.
The spacecraft exploded once more. The explosion occurred at the same phase of the flight: eight minutes after liftoff. At the time, Starship 34 was about to shut down its engines to begin its suborbital trajectory toward the Indian Ocean.
Just like Starship 33, the spacecraft lost control when several of its engines shut down or exploded, starting with the first three and then a fourth. It began to spin on its axis until it exploded. This could have been due to disintegration like its predecessor. Alternatively, it could have been because the flight termination system was activated, causing the rocket to self-detonate for safety reasons.
Reentry was visible from Miami. Videos quickly emerged showing the spacecraft’s wreckage disintegrating in the atmosphere. Observers from the Bahamas, the Turks and Caicos Islands, and the Dominican Republic captured similar footage. Additionally, images came from Cape Canaveral and Miami since the explosion occurred while the rocket was traveling at 12,400 km/h. In contrast, the Starship from Flight 7 exploded at more than 13,000 km/h, resulting in debris falling farther away.
As was the case in January, aircraft were immediately diverted. When rocket debris falls, specific areas are designated as danger zones. In the event of an incident, SpaceX notifies authorities, who then close the airspace. Pilots are instructed to reroute to other airports if necessary.
Is this déjà vu? According to SpaceX’s investigation, Starship 33 failed due to an unexpectedly strong “harmonic response.” This phenomenon caused vibrations that led to an oxygen leak in the lower part of the rocket, which in turn triggered a fire. All this ultimately resulted in an explosion of the engines.
To better understand the problem, SpaceX conducted a one-minute ground ignition test. Engineers also attempted to mitigate the effects of these vibrations by improving ventilation in the lower part of the spacecraft to prevent gas buildup. Although the company hasn’t confirmed that Starship 34 failed for the same reasons, a small fire was observed in one live image, and an engine explosion was seen in another.
Something’s wrong with Starship Block 2. The recent major setback in the program’s history coincides with a version change. Starship 33 and Starship 34 are the first models of Block 2, marking the second generation of the rocket.
These new models are 6 feet taller than the previous generation. Additionally, they feature larger methane and liquid oxygen tanks and improved heat shields. SpaceX has also redesigned the forward ailerons and modified the propulsion subsystems. Whatever the problem may be, something has gone wrong with this iteration. Fortunately, the company now has more data to analyze in order to resolve it.
Image | SpaceX
View 0 comments