Connect with us

News

SpaceX fires up Starship rocket twice in 30 hours ahead of next big tests

Starship SN4 is looking downright shiny after successfully completing multiple wet dress rehearsals and two Raptor static fire tests. (NASASpaceflight - bocachicagal)

Published

on

SpaceX has successfully fired up a full-scale Starship rocket for the second time in barely 30 hours and removed the ship’s Raptor engine to perform an additional suite of “cryo testing”.

Around 7pm CDT on May 6th, SpaceX technicians began loading the fourth full-scale Starship with liquid oxygen and methane, filling up a large portion of its massive propellant tanks. Just the latest in a line of several tests involving wet dress rehearsals (WDR) completed in the days prior, this test would soon become exceptional. About an hour and a half after work began, Starship SN4’s lone Raptor engine ignited and burned for ~3 seconds, marking the first time in history a next-generation SpaceX rocket truly came alive with one of the engines designed to take it all the way to orbit.

In line with tests performed with Starhopper – a low-fidelity, subscale tested that flew twice with Raptor – last year, it would have been business as usual if SpaceX had called it a day and moved on to something else with Starship SN4. Instead, Starship performed another WDR and fired up its Raptor engine for a second time in just 30 hours after SpaceX teams inspected the rocket and cleared it for another round. It’s unknown why two back-to-back static fires were performed but, to be clear, every step Starship SN4 takes forward is a step into uncharted territory. Already, the ship’s next steps could come as soon as Friday, May 8th.

According to CEO Elon Musk, SpaceX’s second Starship SN4 static fire test was completed successfully and actually marked the operational debut of a critical aspect of the next-generation launch vehicle and spacecraft. Known as header tanks, Starship needs two smaller secondary propellant tanks to complement its main tanks, a need driven mainly by the challenges of landing such a large and mobile spacecraft. Smaller header tanks will also make it dramatically easier for SpaceX to insulate cryogenic propellant and ensure it remains liquid over long-duration cruises in space, but safe and reliable landings are a more pressing concern for these early prototypes.

Advertisement

During landing operations, the main benefits smaller header tanks offer are relative ease of pressurization (needed to safely feed Raptor engines) and a much lower risk of issues from sloshing, which can introduce bubbles and voids that can obliterate rocket engines if ingested. Impressively, per Musk, Starship SN4 completed its second static fire test using its internal liquid methane header tank – a sort of bubble attached to the bottom of the main methane tank dome.

Starship SN5’s common methane and oxygen tank dome (and spherical methane header tank) is pictured here on May 1st. (NASASpaceflight – bocachicagal)
While header tanks will be invaluable for Starships attempting to landing on other planets or Moons after weeks- or months-long coasts in space, they’re also a great help for landing on Earth. (SpaceX)

Starship’s liquid oxygen header tank is situated at the tip of the conical nose section, a part that all full-scale ships have been tested without thus far. However, the use of the fuel header tank on May 7th means that Starship SN4 already has a functional, plumbed header tank installed, verifying the partial functionality of a critical part of the next-generation launch vehicle. A second static fire will have also provided SpaceX a wealth of extra data about Raptor’s performance while installed on Starship, invaluable at such an early stage of integrated testing.

Two Starship static fires now under its belt, SpaceX removed SN4’s Raptor engine around 12 hours after its second test and returned it to storage at the company’s nearby factory facilities. According to public notices provided by Cameron County, Texas officials, SpaceX’s next Starship SN4 activity is expected to occur on May 8th with backup windows on the 9th and 10th and will involve “cryo testing”.

SpaceX removed Starship SN4’s Raptor engine after two successful back-to-back static fires. (NASASpaceflight – bocachicagal)

The most obvious conclusion is that SpaceX – having completed enough static fire testing to verify Starship SN4’s performance – now wants to really put the rocket through its paces with another cryogenic test. Completed on April 26th, the ship’s first cryogenic ‘proof’ test maxed out at around 4.9 bar (70 psi), enough for low-stress hop tests but well short of the sustained pressure needed for orbital spaceflight. While testing singular propellant tanks in the first few months of 2020, Musk revealed that SpaceX was targeting a minimum of 6 bar (~90 psi) for orbital Starship flights – ~8 bar (115 psi) with a 25% safety factor.

Pictured here on May 7th, Starship SN5 could be just days away from its final tank section stacking operation and just a week from rolling to the launch pad for proof testing. (NASASpaceflight – bocachicagal)

The company actually achieved 8.4 bar with one of its Starship test tanks, the same processes of which were used to build Starship SN4, but a full-scale ship has yet to demonstrate those pressures. Now, SpaceX already has a fifth full-scale prototype (Starship SN5) likely just a week or so away from pad readiness, meaning that Starship SN4’s potential destruction during pressure testing wouldn’t have a big impact on plans for a series of imminent flight tests. If SN4 survives pressure testing, it would likely have its Raptor engine reinstalled and move on to a 150m (500 ft) hop test.

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

Elon Musk reveals unfortunate truth of Tesla Full Self-Driving development

In a candid reply to a dramatic video of Tesla’s Full Self-Driving (FSD) system averting disaster, Elon Musk laid bare a harsh reality facing autonomous vehicle technology.

Published

on

Tesla’s Full Self-Driving suite is one of the most significant technological developments in terms of passenger travel in decades, but it is not all sunshine and rainbows, even with major strides in safety, CEO Elon Musk revealed.

In a candid reply to a dramatic video of Tesla’s Full Self-Driving (FSD) system averting disaster, Elon Musk laid bare a harsh reality facing autonomous vehicle technology.

The clip shows a Model 3 traveling at over 65 mph on a foggy, rain-soaked highway when a pedestrian suddenly steps into traffic.

Full Self-Driving instantly detects the threat and swerves safely, preventing what could have been a fatal collision for both the pedestrian and the driver’s cousin.

Musk’s response was unequivocal:

“Tesla self-driving saves a lot of lives – the statistics are unequivocal. That doesn’t mean it’s perfect, of course.” Even with a projected 10x safety improvement over human drivers, FSD would still prevent roughly 90% of the world’s approximately one million annual auto fatalities. The remaining 10%—roughly 100,000 deaths—would expose Tesla to relentless lawsuits. Meanwhile, the vast majority of lives saved would go unnoticed. “The 90% who are still alive mostly won’t even know that Tesla saved them. Nonetheless, it is the right thing to do.”

This “unfortunate truth,” as Musk implicitly framed it, highlights a fundamental asymmetry in how society perceives safety technology. Human drivers cause the overwhelming majority of crashes through distraction, fatigue, or error.

Yet when FSD errs, the incident becomes headline news and a courtroom target. Prevented tragedies, by contrast, leave no trace.

Survivors simply continue their journeys, unaware of the split-second intervention that kept them alive. The result is a distorted public narrative that amplifies failures while rendering successes invisible.

We have seen this through various headlines throughout the years, including the mainstream media’s obsession with only mentioning the manufacturer’s name in the instance of an accident when it is “Tesla.”

Opinion: Tesla Autopilot NHTSA investigation headlines are out of control

The video’s real-world example underscores FSD’s current capabilities. In near-zero visibility, the system’s cameras and neural network reacted faster than any human could, demonstrating the life-saving potential Musk cites.

Tesla’s latest safety data already shows FSD (Supervised) performing significantly better than the U.S. average, with crashes occurring far less frequently per mile driven.

Still, regulatory scrutiny, liability concerns, and media focus on edge-case failures continue to slow widespread adoption. Musk’s frank admission suggests Tesla is prepared to push forward despite the legal and perceptual headwinds.

As FSD edges closer to unsupervised autonomy, Musk’s post serves as both a progress report and a reality check. The technology is already saving lives today.

The unfortunate truth is that proving it and scaling it responsibly will require society to value statistical lives saved as much as dramatic stories of those lost. In the race toward safer roads, perception may prove as formidable an obstacle as the fog and rain in that viral video.

Continue Reading

News

Tesla Full Self-Driving v14.3: First Impressions

Published

on

Tesla started rolling out Full Self-Driving v14.3 to Early Access Program (EAP) members earlier today, and I had the opportunity to see some of the improvements that were made from v14.2.2.5.

While a lot of things got better, and I truly enjoyed using Full Self-Driving again after being stuck with the widely confusing and frustrating v14.2.2.5, Tesla still has one major problem on its hands, and it has to do with Navigation and Routing. I truly believe those issues will be the biggest challenges Tesla will face with autonomy: the car simply going the correct way, not conflicting with what the navigation says, and taking the simplest and most ideal route to a destination.

Here’s what I noticed as an improvement with my first hour with v14.3. This is not a full review, nor is it reflective of everything I will likely experience with this new version. This is simply what I saw as a noticeable improvement from the past version, v14.2.2.5.

There is also a more streamlined version on X, available at the thread below:

Yellow Light Behavior is Significantly Better

On v14.2.2.5, I had so many instances of the car slamming the brakes on to stop at a yellow light when it was clearly the safer option to proceed through. There were several times when the car would be about 20 feet from the line, traveling at 15-20 MPH, the light would turn yellow, and it would slam the brakes to stop. I would nudge it through yellow lights constantly because of this by putting my foot on the accelerator.

The instances I’m talking about here would not have been close calls — the car would have likely moved through the intersection completely before the light would turn red.

On multiple occasions this evening, FSD proceeded through yellow lights safely, without hesitation or any brake stabbing. It was refreshing:

This was a huge complaint with v14.2.2.5. Sometimes, it’s a safer option to go through a yellow light, especially when you have traffic behind you. It’s a great way to get rear-ended.

Parking Performance

I had four instances of parking, and FSD v14.3 really did a flawless job. I was very impressed with how solid it was, but also with how efficiently it moved into the spot. When there was traffic around with past versions, I usually chose to park manually just because FSD took its time getting into a spot. I don’t see that being an issue anymore.

I complained about parking a lot and shared several images on X and Facebook of those examples:

No issues with it this evening. 4/4. Here are two looks:

Highway Performance

FSD v14.3 passed the five cars shown in this image:

The sixth was 200-300 yards ahead of the fifth. In v14.2.2.5, FSD would usually stay in the left lane, especially on Hurry and Mad Max. It did not do that, as it instead chose to get back over in the right lane after passing the final car.

Speed was not much of a concern here, even though it was going 21 MPH over. Although it was fast, I did have a line of cars behind me traveling at the same speed, and FSD had just merged about a half mile prior, so I chose to let it continue.

There were no instances of camping in the left lane for extended periods of time. I do want to do more testing with the Speed Profiles because they were in need of some work with the previous version. I am starting to side with those who want a Max Speed setting, which was removed last year.

Navigation and Routing Still Need Work

I was heading back toward where I came from, so I turned “Avoid Highways” on to take a different way. This confused the Routing system, and instead of turning left, then right, as the Routing said, the car turned right, then indicated for another right, basically going in a big rectangle. The car ignored the second right-hand turn and continued straight. I ended up turning “Avoid Highways” off and letting the car pick the same routing option as what took me here.

I have truly complained so much about Navigation and Routing that I’m starting to feel sort of bad. It is obviously such a massive challenge for some reason, but I am confident it will improve. I recall seeing Tesla hiring someone for this role a few months back, so perhaps there is hope for it to get better.

Smarter Behavior When Approaching Exits/Routing

This probably should be grouped in with Highway Behavior, but I wanted to highlight it on its own.

The highway exit pictured was always frustrating for v14.2.2.5. In the Hurry speed profile, I have seen it try to execute passes on multiple cars with as little as 0.6 miles to spare before taking the exit.

With three cars ahead of it, it chose to reduce speed and just wait until the exit. It was refreshing to see an improvement here, so I hope this behavior persists. Sometimes there’s just no reason to pass when you’re less than a mile from getting off the highway anyway.

Larger Visibility Warnings

Tesla seems to have increased the size of these “Camera Visibility Limited” warnings. Previously, they were just small thumbnails:

Stop Sign Behavior

This is probably the biggest improvement of all, because how it behaved at Stop Signs in v14.2.2.5 was so incredibly terrible and disruptive to the flow of a busy intersection.

There are several four-way, all-stop intersections near me. In the past, FSD would stop well behind the Stop Sign or the white-painted line on the road. It would then inch forward, stopping again at this line, essentially making two stops at a single intersection.

If there is visibility, I don’t truly care where FSD stops, as long as it stops once. Stopping twice just isn’t ideal or logical. I can’t imagine many humans would do it, I know I wouldn’t.

I didn’t have that issue this evening:

This was pretty tight, too, in the sense that both my car and the other one got to the intersection at the same time. FSD may have stopped first, but the other vehicle was probably around the same point that I was when FSD decided to stop. I was happy to see the assertiveness to proceed; it felt like it was ideal to just go through. I was happy it didn’t stop a second time up at the line. I’d be fine if it stopped at the line, as long as that was the only stop it made.

Continue Reading

News

Tesla Full Self-Driving v14.3 rolls out: here’s what’s new

We are in EAP and will be on the road with v14.3 in the coming hours, so we’ll have a lot of things to discuss over the next few days, especially coming from v14.2.2.5, which I called the most “confusing” FSD release of all time.

Published

on

Tesla has officially started rolling out Full Self-Driving v14.3 to Early Access Program (EAP) members, and there are a lot of new improvements.

We are in EAP and will be on the road with v14.3 in the coming hours, so we’ll have a lot of things to discuss over the next few days, especially coming from v14.2.2.5, which I called the most “confusing” FSD release of all time.

Tesla brought out a lot of improvements, according to the v14.3 release notes, which list a vast number of fixes, new features, and new capabilities.

Here’s what Tesla’s release notes for the v14.3 release state:

  • Improved parking location pin prediction, now shown on a map with a P icon.
  •  Increased decisiveness of parking spot selection and maneuvering.
  • Rewrote the Al compiler and runtime from the ground up with MLIR, resulting in 20% faster reaction time and improving model iteration speed.
  • Enhanced response to emergency vehicles, school buses, right-of-way violators, and other rare vehicles.
  • Mitigated unnecessary lane biasing and minor tailgating behaviors.
  • Improved handling of small animals by focusing RL training on harder examples and adding rewards for better proactive safety.
  • Improved traffic light handling at complex intersections with compound lights, curved roads, and yellow light stopping – driven by training on hard RL examples sourced from the Tesla fleet.
  • Upgraded the Reinforcement Learning (RL) stage of training the FSD neural network, resulting in improvements in a wide variety of driving scenarios.
  • Upgraded the neural network vision encoder, improving understanding in rare and low-visibility scenarios, strengthening 3D geometry understanding, and expanding traffic sign understanding.
  • Improved handling for rare and unusual objects extending, hanging, or leaning into the vehicle path by sourcing infrequent events from the fleet.
  • Improved handling of temporary system degradations by maintaining control and automatically recovering without driver intervention, reducing unnecessary disengagements.

Tesla also listed a handful of future improvements as well:

  • Expand reasoning to all behaviors beyond destination handling
  • Add pothole avoidance
  • Improve driver monitoring system sensitivity with better eye gaze tracking, eye wear handling, and higher accuracy in variable lighting situations

CEO Elon Musk has said that v14.3 could be “where the last big piece of the puzzle finally lands.” We have high expectations for this release because, in a lot of ways, v14.2’s final version was extremely disappointing and seemed to be a regression more than anything.

Nevertheless, Full Self-Driving v14.3 is going to be quite an interesting test, considering this is also the first time Musk has stated it will feel like the car will be “sentient.”

Reasoning will be a bigger piece of the puzzle with this release, although there were some elements of it in v14.2.

Tesla AI Head says future FSD feature has already partially shipped

We plan to travel plenty of miles with it over the next few days, so we’ll keep you posted on what our thoughts are.

Continue Reading