Connect with us

News

SpaceX’s orbital Starship launch pad tank farm comes to life for the first time

SpaceX's orbital Starship tank farm has begun venting for the first time in a sign that testing of the storage vessels has finally begun. (NASASpaceflight)

Published

on

Update: Two days after a bevy of tanker trucks began to arrive at SpaceX’s orbital Starship launch site with load upon load of cryogenic liquid nitrogen, the company’s custom-built tank farm appears to have taken its very first ‘breaths.’

In other words, at least one of seven massive propellant storage tanks – two of which appear to have been fully completed and insulated – began venting. For a tank like SpaceX’s ground support equipment (GSE) tanks, the level of venting observed can only mean one thing: pressure maintenance during operations with cryogenic fluids. As cryofluids are loaded into empty tanks, they inevitably come into contact with warm pipes and tank walls, rapidly warming a portion of the liquid that then boils into gas. Tanks then need to vent that excess gas to avoid bursting.

In the case of SpaceX’s two completed liquid oxygen GSE tanks and a spate of liquid nitrogen (LN2) deliveries this week, it’s clear that the company has begun the process of testing and activating part of its brand new orbital-class Starship tank farm – beginning with much less risky LN2 proof testing. Filling the two finished LOx tanks with LN2 should also serve the dual purpose of flushing and cleaning them of any debris or contaminants, ensuring that it’s safe to fill them with LOx when the time comes.

For the first time, SpaceX appears to have begun delivering large quantities of cryogenic fluids to Starship’s orbital launch pad – still under construction but fast approaching some level of initial operational capability.

Advertisement

Sometime in the morning on September 19th, a semi-truck carrying a cryogenic liquid nitrogen (LN2) transport trailer arrived at SpaceX’s Starbase launch facilities. Normally, that would be a completely mundane, uninteresting event: SpaceX has used and will continue to use liquid nitrogen to safely proof test Starship prototypes and supercool their liquid methane (LCH4) and oxygen (LOx) propellant for the indefinite future. However, up to now, 100% of all Starbase cryogen deliveries have gone to the suborbital launch site, where two “mounts” and a few concrete aprons have supported all Starship and Super Heavy tests and launches to date.

Instead, this particular LN2 tanker headed for Starbase’s first orbital tank farm and began to offload its cryogenic liquid cargo at a number of brand new fill stations specifically designed for the task.

Still well under construction and at least a few weeks or months from total complete, Starship’s orbital launch site tank farm will ultimately be a group of eight massive storage tanks surrounded by thousands of feet of insulated plumbing, industrial pumps, a small army of “cryocoolers,” a blockhouse filled with human-sized valves, and much more. Said tank farm has been under construction for the better part of 2021, beginning with work on its concrete foundation this January.

Nine months later, the orbital tank farm is nearly complete. A power distribution and communications blockhouse has been complete for weeks with virtually all the wiring and cabling needed for the orbital launch mount and tower already in place. Several hundred feet of concrete cable and plumbing conduit have been filled with thousands of feet of wires, cables, and pipes and been sealed and buried. The tank farm blockhouse – where a dozen or so massive valves control the flow of propellant to and from the orbital launch mount and tower – is complete save for some final plumbing.

Advertisement

Finally, seven of eight GSE (ground support equipment) tanks have been installed and partially plumbed. Built in the same factory, six are virtually identical to Starship and Super Heavy tanks and will store LOx (3x), LN2 (2x), LCH4 (2x), and around a million gallons of water. Save for one LCH4 tank, all have been installed at the farm and that last tank (known as GSE8) is nearly complete back at the build site. Additionally, to insulate those seven thin, steel storage tanks, SpaceX has contracted with a water/storage tank company to build seven “cryoshells” and said million-gallon water tank.

The water tank was installed months ago and all seven shells are completed and ready to go as of last month. Only two of those seven cryoshells have been installed – and, rather asymmetrically, both on LOx tanks. SpaceX recently rolled the first LN2 tank cryoshell to the farm and could install it soon but as of now, it will likely be weeks before the orbital tank farm will have sleeved, insulated LOx, LN2, and LCH4 tanks ready for testing.

SpaceX appeared to (partially) fill Starship’s orbital launch pad ‘tank farm’ with cryogenic fluid for the first time on Sunday. (Starship Gazer)

At the moment, that’s one of the biggest points of uncertainty standing between SpaceX and the ability to test Super Heavy or Starship at the orbital launch site. It’s entirely unclear if uninsulated GSE tanks can support any kind of substantial testing – like, say, the first full Super Heavy static fire test campaign – before their contents effectively boil off. As such, it’s a bit of mystery why SpaceX then had at least three tanker loads of liquid nitrogen – likely more than 70 tons (~150,000 lb) total – delivered to the orbital tank farm on September 19th.

By all appearances the first time that the farm’s actual main tanks have been filled with anything, that liquid nitrogen seems to have been loaded into one or both of the two insulated LOx tanks. There are two or three main explanations. First, SpaceX could simply be testing those more or less completed tanks with their first cryogenic fluids. Those partial ‘cryo proof’ tests would also help clean and flush out the interior of the LOx tanks, removing mundane debris or contamination that could become a major hazard when submerged in a high-density oxidizer. Given that both tanks can easily hold ~1300 tons (~2.9M lb) of liquid nitrogen, 70 tons is more of a tickle than a test, though, so a magnitude more would need to be delivered to perform even a half-decent bare-minimum cryoproof.

The other distinct possibility is that SpaceX plans to temporarily use one or both of the only two finished orbital pad tanks to store liquid nitrogen for Super Heavy Booster 4’s first cryogenic proof test. Either way, SpaceX has test windows scheduled every day this week, beginning with a six-hour window that opens at 5pm CDT today (Sept 20). Stay tuned to find out what exactly SpaceX plans to test and if the orbital tank farm and its first taste of liquid nitrogen are involved!

Advertisement

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