Connect with us

News

SpaceX’s Starship prototype is looking increasingly rocket-like as hop test pad expands

SpaceX workers began welding Starhopper's upper tank dome cap, perhaps the most rocket-like structure yet installed on the craft. (NASASpaceflight - bocachicagal, 02/05/19)

Published

7 years ago

on

As SpaceX’s South Texas operations continue full steam ahead in pursuit of the first integrated hop tests of a full-scale Starship prototype, the company’s Starhopper and its complementary launch/hop pad are dramatically and visibly evolving on a daily basis.

This week’s progress has been signified by the installation of familiar rocket hardware on the Ship and a burst of construction – centered around pipelaying, plumbing, foundation work, and berm-building – at its pad. Just a few hundred miles north of Boca Chica, SpaceX’s team of propulsion engineers and technicians reached their own dramatic milestone, conducting the first static fire of a finalized version of the Raptor engine set to power Starship and Super Heavy (formerly BFR).

A pad fit for a Starhopper

In the last ~10 days alone (Jan 24-Feb 4), SpaceX pad construction workers and contractors transformed the former dirt mound from a generally flat, planed surface with a spattering of shipping containers and building materials into a hive of welding rigs, propellant and water tanks, major plumbing progress, shaped earth, and the beginnings of new concrete foundations. Thanks to local student Austin Barnard’s reliable drone photography, that pad-specific progress can be more properly visualized.

 

Taken on January 24th and February 4th respectively, the devil is definitely in the details when it comes to SpaceX’s prospective Starhopper pad development. Most notable is the progress made with the rapidly developing propellant plant and ground systems infrastructure in the left half of the images, marked by hundreds of feet of freshly-installed piping meant to support the process of fueling Starhopper with liquid methane and oxygen. For a rocket as powerful as Starhopper (even with just three Raptor engines), cooling both the propellant and the concrete launch and landing pad is no less important, visible in the shape of three large water tanks (lefthand foreground) and a smaller radiator stack (just to the right of two taller, skinnier white tanks.

Aside from the rapid rise of the first BFR propellant farm and its supporting equipment, SpaceX has progressed into the installation of a trio of concrete foundations just to the right of the dirt berm and propellant tank area. Standing as close as it is to said propellant tanks, it seems unlikely that the new foundation-laying is related to the pad (or a stand) meant to support early Starhopper hop tests, although SpaceX’s Falcon 9-era Grasshopper and F9R hop test vehicles operated about the same distance from its propellant infrastructure. SpaceX’s South Texas site also features a sort of satellite pad at its east end (the right side in attached photos) that could have a future as an integration hangar or a secondary landing zone to allow for Starhopper to perform divert tests.

Advertisement
-
-

 

Depending on whether SpaceX actually intends to develop the land shown above into an actual full-scale launch facility for BFR (Super Heavy and Starship), it could also remain generally unchanged until Starhopper’s hop test program has been run to completion, at which point everything seen above would likely be rebuilt from scratch to accommodate for any drastic changes in function. SpaceX’s Boca Chica might simply be too small to support a pad capable of launching Super Heavy (nearly twice as powerful as Saturn V at full thrust), measuring in at considerably less than ~10 acres of usable area compared to LC-40’s ~20 acres and Pad 39A’s ~50+ acres. CEO Elon Musk has also hinted at using a giant floating platform for early orbital BFR launches, although that might prove even harder (and more costly) than building a traditional land-based pad.

Becoming a rocket

Meanwhile, the aft engine/fin/tank section of SpaceX’s Starship prototype (unofficially nicknamed Starhopper) has experienced a stream of hardware additions and improvements, modifying its relatively awkward and unfinished steel base with what appear to be Falcon 9-sized quick-disconnect umbilical panels, a functional propellant tank header, and mounting hardware for carbon-overwrapped pressure vessels (COPVs). By using hardware that is proven and easy to manufacture, SpaceX can save a huge amount of time that would otherwise need to be spent engineering subassemblies that (at risk of undervaluing the challenge) are generally known-quantities – more a matter of time and effort than an actual technical hurdle.

 

While they are clearly still in a rough, unfinished form, Starhopper’s umbilical panels are already easy to recognize when compared alongside Falcon 9’s iconic red and blue panel pairs. In essence, whereas Starhopper has been a largely unknown quantity with no familiar aspects since it began to come together late last year, the Starship prototype has recently had hardware installed that is finally revealing subtle SpaceX signatures in its design and assembly.

Check out Teslarati’s newsletters for prompt updates, on-the-ground perspectives, and unique glimpses of SpaceX’s rocket launch and recovery processes!

Advertisement
-
-
Related Topics:

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

News

Tesla briefly offered this Robotaxi part for your personal car

Published

1 hour ago

on

July 28, 2026

By

Credit: @tpgoebel | X

Tesla briefly offered one Robotaxi part in its Parts Catalog for your personal car, only to remove it just a short time after it was first noticed.

Tesla’s Robotaxi camera washer apparatus was briefly available for purchase on the company’s Online Parts Catalog. The camera washer was first noticed on Model Y Robotaxi vehicles about six months ago in Austin.

First noticed by Not a Tesla App, the Camera Washer entries appeared for the new “Juniper” Model Y under a category called “Halo,” which has also now disappeared. Interestingly, Halo probably is related to Tesla’s internal “Project Halo,” which was a project that aimed to retrofit customer-owned Model Ys into functional Robotaxis.

This hardware addition would likely be required for the vehicle to operate as a Robotaxi, as the Camera Washer seems to be a non-negotiable part of the vision-based system Tesla utilizes for self-driving efforts.

However, this part has since been removed and is no longer visible on the EPC.

Advertisement
-
-

Now the true question lingers: Why would Tesla add this Camera Washer to the Model Y parts catalog? Is it planning to make it available for owners to utilize on their own cars for personal use, or will it become a prerequisite for Robotaxi operation in customer-owned cars?

While discussing the upgrade options for Hardware 3 vehicles during the Q1 Earnings Call, Tesla CEO Elon Musk had said that the company could establish small, satellite shops that would upgrade cameras and self-driving computers. Perhaps this same strategy could be utilized for vehicles that want to be included in Robotaxi but do not have the correct hardware.

AI4 is currently represented as capable of unsupervised self-driving, and the same was said about HW3 at one point, only for Tesla to admit last quarter that it would, unfortunately, not be possible. Perhaps AI4 vehicles might need this camera washer as a prerequisite, just as HW3 cars will need that camera and computer upgrade.

This could be the first hint of that’s where we are headed.

Continue Reading

News

Tesla Robotaxi gets sweeping but polarizing change

Published

3 hours ago

on

July 28, 2026

By

Credit: Tesla

Tesla has started rolling out a broader change to the ride experience for its Robotaxi fleet by silencing turn signals, but the change is certainly polarizing.

Tesla has generally made it clear that its purpose-built ride-hailing platform, Robotaxi, will cater to the rider in nearly every way possible. This includes having climate preferences, music, and other personal settings loaded up in the car as the rider enters.

But Tesla is taking it a step further by muting turn signal chimes altogether, a change that appears to be a way to make the ride more peaceful:

However, there are a handful of people who are not thrilled about this change. Turn signals are a conditioned part of the human mind for those who ride in a car regularly.

Advertisement
-
-

Taking a turn without one feels strange and odd, and not hearing it click while activated could set off some alarms for riders, who might use the noise as confirmation that other drivers know of their intention to turn.

Turn signal noises are still audible in customer cars, so if you use FSD in your personal vehicle, you will still hear the turn signal.

The move is certainly one that is unique, but not one that separates it from other ride-sharing services. In a normal car, the clicking sound confirms to the driver that the blinker is active. In a fully driverless Robotaxi, that feedback serves no purpose for passengers, other than peace of mind.

Continue Reading

News

Tesla Full Self-Driving v14.3.6 review: a rare regression, but some bright spots

Published

24 hours ago

on

July 27, 2026

By

Credit: Tesla

Tesla released Full Self-Driving version 14.3.6 last week, and after what was potentially one of the best FSD releases in v14.3.5, there has been a bit of a regression. While there are some bright spots, the changes made to v14.3.6 seem to have backtracked some behaviors.

Overall, it is hard to really complain about FSD in any sense; it has revolutionized how I travel literally anywhere. According to my self-driving app, the last time I went a day without using it was 59 days ago.

However, I think it’s also important to recognize when things are just plain bad with FSD. There are times it does truly mind-boggling things, and I’ll dive into those here. Additionally, I only had these issues on local roads, not on highways. Highway operation, generally, is always incredible other than the occasional complaint about speed or left lane camping.

With those things being said, my personal experience may not represent others’ experiences. A handful of people have said they have had a similar experience on v14.3.6, while others have said it is more than normal.

Turning Hesitancy, Inaccuracy

I’ve noticed more inaccuracy turning into multi-lane stretches of road than in any version I can remember. I’ve had at least three instances of FSD turning into a stretch of roadway that has two or more lanes, and not selecting a lane confidently as it has in past versions.

Instead, the car will drive over one of the dashed road lines, and the steering wheel will jerk back and forth before picking the lane. It should be said that it has always picked the correct lane when choosing based on the navigation, but it is still very indecisive. The steering wheel jerking is reminiscent of some of the later versions of v13.

I admit I really hate to see the steering wheel jerking come back. However, I think when Tesla releases v14.3.7, it won’t be present. When there are occurrences of it in FSD versions, it is usually resolved by the following release.

FSD Disregards Manual Turn Signals

This is my biggest bone to pick with FSD other than Navigation issues, but this one seems like it would be such an easy fix.

If Tesla is going to put the word “Supervised” on the end of “Full Self-Driving,” then when I tell the car to do something, it should do it. If I input an increase in speed by pressing the accelerator, the car will immediately respond. It does not disregard my input because it feels it is traveling at the right speed.

FSD should never disobey and turn off turn signals that the driver inputs. Trying to direct the car into the correct lane, I had initiated the left turn signal not once, not twice, but three times, with the car turning it off all three times and continuing in a lane that would end in just one block. The only solution at this point would be to zipper merge.

This goes back to the fact that self-driving’s biggest bottleneck might be rider preference. A zipper merge might have been more than reasonable, might have saved me time that I spent sitting through an additional light cycle, and might be something many drivers would do. I was in no hurry, I traditionally do not try to zipper merge because it feels inconsiderate, and lastly, the car should have just followed my input.

Advertisement
-
-

This caused me to disengage and drive manually the rest of the way home. Sometimes I just do not need FSD to try to pass every car it can at intersections.

Bird Braking is a Thing of the Past

The big complaint with recent versions of Full Self-Driving has been what we’ve coined as “bird braking,” which is when the car will brake suddenly as a bird flies past.

There have been zero issues with this so far in v14.3.6, which is an excellent improvement.

FSD Might Already Be Taking Note of Driver Preferences

Another thing I have noticed over the past few days is that v14.3.6 seems to already be taking my preferences with navigation into account.

This is something that is supposed to be rolling out with the Summer Update, but I have a hunch it’s already present and might have been included in this v14.3.6 build. On Friday, FSD pulled into an entrance to a local convenience store that it had never attempted to go into before.

Typically, I manually pull into this entrance because it avoids heavy cross traffic at the main entrance. FSD has always chosen that congested main entrance.

Additionally, FSD has pulled into my assigned parking spot at my townhouse community on multiple occasions with this release. This is something that used to happen ocassionally, but not consistently.

It also navigated back to the same convenience store last night, drove through crazy cars scrambling to gas pumps, navigated out of the parking lot correctly, drove me home, and, once again, parked in my assigned spot.

As previously stated, this release just seems to have a few things that need to be brought to Tesla’s attention, and also to make others who use FSD aware of some things that I’ve experienced. I look forward to the next release that will remedy these issues, just as Tesla has always done in the past.

Advertisement
-
-
Continue Reading