Connect with us

News

SpaceX Starship prototype charred but intact after catching fire [photos]

SpaceX employees inspect Starship SN4 for the first time some two days after the rocket finished its third Raptor engine test. (NASASpaceflight - bocachicagal)

Published

on

SpaceX teams have finally safed the fourth full-scale Starship prototype nearly two days after a Raptor engine test caught it on fire, an anomaly that left the massive rocket charred and damaged – but still intact.

While SN4’s survival is a welcome and unexpected outcome, the fire that broke out near the base of the rocket caused damage that will have to be repaired, while the fault that allowed that fire to occur in the first place will also need to be rectified. Had the same events transpired during the ship’s inaugural flight test, things could have gone even further south after the rocket lifted off, carrying it away from remotely-controlled water jets used to suppress unplanned fires on the pad.

Thankfully, SpaceX’s focus on testing, testing, and testing some more meant that Starship SN4’s minor self-immolation occurred on the ground when the stakes – while high – were much lower than they would have been with an airborne rocket. The problems uncovered will, of course, need to be fixed, inevitably delaying the ship’s first flight test, but odds are that SN4 now has a better shot at success thanks to those hiccups.

Starship SN4 has thankfully survived a ~48-hour ordeal that may have left the rocket partially uncontrolled. (NASASpaceflight – bocachicagal)

Thanks to the fact that Starships are constructed almost entirely out of steel, a little (or a lot of) fire shouldn’t theoretically be much of a problem. However, SpaceX has taken a rather freeform approach to its early Starship SNx prototypes, opting to bolt, weld, or tape on the vast majority of external hardware with little or no protection from the elements, including fires ignited by the ships themselves.

With SN4, it appears that the pressure jump experiences immediately after Raptor ignition (the ship’s third such test) shook some methane-related plumbing loose. Raptor continued to burn for another five or so seconds after that minor failure, shutting down as planned – but not before it ignited the methane the burst pipe was leaking. Additionally, after that new plume of boiling liquid methane caught fire, the fire it sustained proceeded to ignite insulation wrapped around the rocket’s launch. It burned vigorously, likely helping to damage wiring, ultimately causing SpaceX to partially lose control of the rocket and preventing attempts to inspect and fix the damage for two full days.

Advertisement
A May 8th view of the pipe (bottom right of Starship SN4) that failed on May 19th, starting a fire and damaging the rocket. (NASASpaceflight – bocachicagal)
A large scorch mark and blackened cabling are the only signs on Starship that anything went wrong on May 19th. (NASASpaceflight – bocachicagal)
Around the other side of the rocket, (apparently flammable) insulation haphazardly wrapped around part of the launch mount ~24 hours before testing caught fire and burned aggressively. The leftovers are pictured here on May 21st. (NASASpaceflight – bocachicagal)

It’s safe to say that SpaceX is probably going to prioritize avoiding the series of events that caused May 19th’s anomaly from here on out, considering that things could have easily gone much worse. Thankfully, whatever control SpaceX or the rocket itself retained after wire damage allowed it to safely offload its flammable propellant and vent expanding gases to prevent SN4’s tanks from bursting. Installing highly flammable insulation approximately 10 feet away from an active Raptor engine and giant controlled fire and explosion was also inadvisable and probably won’t be repeated.

(NASASpaceflight – bocachicagal)

Thankfully, the damage is clearly minimal and Starship SN4 survived the ordeal otherwise unscathed. With any luck, inspections and repairs will be quick and easy and SpaceX – as NASASpaceflight reporter Michael Baylor notes – will be able to complete an identical static fire test without starting a fire on Starship SN4. SpaceX has requested a new road closure (signifying planned testing) on May 28th with backup windows on May 29th and June 1st.

Thanks to Starship SN4’s unplanned delays, it now looks quite likely that SpaceX’s next full-scale Starship prototype (SN5) will be completed – or nearly so – by the time that its predecessor is cleared for flight. “Too many Starships” is certainly a welcome problem to have.

Eric Ralph is Teslarati's senior spaceflight reporter and has been covering the industry in some capacity for almost half a decade, largely spurred in 2016 by a trip to Mexico to watch Elon Musk reveal SpaceX's plans for Mars in person. Aside from spreading interest and excitement about spaceflight far and wide, his primary goal is to cover humanity's ongoing efforts to expand beyond Earth to the Moon, Mars, and elsewhere.

Advertisement
Comments

Elon Musk

Tesla Full Self-Driving’s newest behavior is the perfect answer to aggressive cars

According to a recent video, it now appears the suite will automatically pull over if there is a tailgater on your bumper, the most ideal solution for when a driver is riding your bumper.

Published

on

Credit: Tesla

Tesla Full Self-Driving appears to have a new behavior that is the perfect answer to aggressive drivers.

According to a recent video, it now appears the suite will automatically pull over if there is a tailgater on your bumper, the most ideal solution for when a driver is riding your bumper.

With FSD’s constantly-changing Speed Profiles, it seems as if this solution could help eliminate the need to tinker with driving modes from the person in the driver’s seat. This tends to be one of my biggest complaints from FSD at times.

A video posted on X shows a Tesla on Full Self-Driving pulling over to the shoulder on windy, wet roads after another car seemed to be following it quite aggressively. The car looks to have automatically sensed that the vehicle behind it was in a bit of a hurry, so FSD determined that pulling over and letting it by was the best idea:

We can see from the clip that there was no human intervention to pull over to the side, as the driver’s hands are stationary and never interfere with the turn signal stalk.

This can be used to override some of the decisions FSD makes, and is a great way to get things back on track if the semi-autonomous functionality tries to do something that is either unneeded or not included in the routing on the in-car Nav.

FSD tends to move over for faster traffic on the interstate when there are multiple lanes. On two-lane highways, it will pass slower cars using the left lane. When faster traffic is behind a Tesla on FSD, the vehicle will move back over to the right lane, the correct behavior in a scenario like this.

Perhaps one of my biggest complaints at times with Full Self-Driving, especially from version to version, is how much tinkering Tesla does with Speed Profiles. One minute, they’re suitable for driving on local roads, the next, they’re either too fast or too slow.

When they are too slow, most of us just shift up into a faster setting, but at times, even that’s not enough, see below:

There are times when it feels like it would be suitable for the car to just pull over and let the vehicle that is traveling behind pass. This, at least up until this point, it appears, was something that required human intervention.

Now, it looks like Tesla is trying to get FSD to a point where it just knows that it should probably get out of the way.

Continue Reading

Elon Musk

Tesla Megapack powers $1.1B AI data center project in Brazil

By integrating Tesla’s Megapack systems, the facility will function not only as a major power consumer but also as a grid-supporting asset.

Published

on

Credit: Tesla

Tesla’s Megapack battery systems will be deployed as part of a 400MW AI data center campus in Uberlândia, Brazil. The initiative is described as one of Latin America’s largest AI infrastructure projects.

The project is being led by RT-One, which confirmed that the facility will integrate Tesla Megapack battery energy storage systems (BESS) as part of a broader industrial alliance that includes Hitachi Energy, Siemens, ABB, HIMOINSA, and Schneider Electric. The project is backed by more than R$6 billion (approximately $1.1 billion) in private capital.

According to RT-One, the data center is designed to operate on 100% renewable energy while also reinforcing regional grid stability.

“Brazil generates abundant energy, particularly from renewable sources such as solar and wind. However, high renewable penetration can create grid stability challenges,” RT-One President Fernando Palamone noted in a post on LinkedIn. “Managing this imbalance is one of the country’s growing infrastructure priorities.”

Advertisement

By integrating Tesla’s Megapack systems, the facility will function not only as a major power consumer but also as a grid-supporting asset.

“The facility will be capable of absorbing excess electricity when supply is high and providing stabilization services when the grid requires additional support. This approach enhances resilience, improves reliability, and contributes to a more efficient use of renewable generation,” Palamone added.

The model mirrors approaches used in energy-intensive regions such as California and Texas, where large battery systems help manage fluctuations tied to renewable energy generation.

The RT-One President recently visited Tesla’s Megafactory in Lathrop, California, where Megapacks are produced, as part of establishing the partnership. He thanked the Tesla team, including Marcel Dall Pai, Nicholas Reale, and Sean Jones, for supporting the collaboration in his LinkedIn post.

Advertisement
Continue Reading

Elon Musk

Starlink powers Europe’s first satellite-to-phone service with O2 partnership

The service initially supports text messaging along with apps such as WhatsApp, Facebook Messenger, Google Maps and weather tools.

Published

on

Credit: SpaceX

Starlink is now powering Europe’s first commercial satellite-to-smartphone service, as Virgin Media O2 launches a space-based mobile data offering across the UK.

The new O2 Satellite service uses Starlink’s low-Earth orbit network to connect regular smartphones in areas without terrestrial coverage, expanding O2’s reach from 89% to 95% of Britain’s landmass.

Under the rollout, compatible Samsung devices automatically connect to Starlink satellites when users move beyond traditional mobile coverage, according to Reuters.

The service initially supports text messaging along with apps such as WhatsApp, Facebook Messenger, Google Maps and weather tools. O2 is pricing the add-on at £3 per month.

Advertisement

By leveraging Starlink’s satellite infrastructure, O2 can deliver connectivity in remote and rural regions without building additional ground towers. The move represents another step in Starlink’s push beyond fixed broadband and into direct-to-device mobile services.

Virgin Media O2 chief executive Lutz Schuler shared his thoughts about the Starlink partnership. “By launching O2 Satellite, we’ve become the first operator in Europe to launch a space-based mobile data service that, overnight, has brought new mobile coverage to an area around two-thirds the size of Wales for the first time,” he said.

Satellite-based mobile connectivity is gaining traction globally. In the U.S., T-Mobile has launched a similar satellite-to-cell offering. Meanwhile, Vodafone has conducted satellite video call tests through its partnership with AST SpaceMobile last year.

For Starlink, the O2 agreement highlights how its network is increasingly being integrated into national telecom systems, enabling standard smartphones to connect directly to satellites without specialized hardware.

Advertisement
Continue Reading