News
SpaceX’s Florida Starship shown off in aerial footage as Texas prototype grows rapidly
Local amateur photographer and spaceflight fan Michael Tapes has graciously shared a new aerial view of SpaceX’s Florida Starship facility, where dozens of workers can be seen buzzing around what is hoped to become the first orbital-class prototype of the massive spaceship and upper stage.
Tapes’ aerial footage offers a unique look at the layout of SpaceX’s Florida site as of July 9th, illustrating just how active and expansive it is. Some workers can be seen building something (perhaps preparing a new worksite) under a large, white tent, while another group surveys two large Starship segments and a third works to prepare new stainless steel ring sections. Of note, those two large Starship segments appear to be bereft of any obvious activity, perhaps a consequence of a fire that caused about $100,000 in damage the day prior (July 8th).
In fact, the shipping container that took what looks like the entirety of fire-related damage is visible on the west side of the SpaceX facility’s main hangar. Workers could be seen heading inside the extremely scorched container, likely removing debris, cleaning up the site of the incident, and preparing to scrap the damaged container itself.
Thankfully, nobody was injured by the fire and ~$100K of damage is certainly an inconvenience but is definitely nothing more for a multibillion-dollar company like SpaceX. Given that dozens of vehicles are visible in the parking lot, it’s safe to say that tons of work is ongoing under the roofs of the site’s many covered buildings, potentially designing Starship/Super Heavy, working on the rocket’s first orbital-class thrust structures, building new steel ring segments, and much more. With any luck, work on orbital Starship assembly and integration has already resumed following the small July 8th fire.


Star(ship) Wars
Speaking of that work, prior to the last week or so of progress on SpaceX South Texas’ own orbital Starship prototype, both Florida and Texas appeared to be more or less tied with two large Starship segments each and various other 9m-diameter subsections spread around their respective facilities. Impressively, Boca Chica has been marked by a flurry of recent work as multiple in-process steel rings were stacked on top of the Texas Starship’s propulsion and tankage section.
In just the last two weeks of June, workers thus pushed through the brutal South Texas heat and humidity to stack three new sections of fuselage, literally doubling the height of Boca Chica’s (hopefully) orbital-class Starship prototype in a dozen or so days. The ship’s conical nose section continues to be polished, while some sort of additional work is likely going on inside, away from public view. It’s hard to get a good overhead view but it’s safe to assume that – in the large barrel sections both in Florida and Texas – technicians are working to install (or at least prepare for) stainless steel tank domes, one of the last major finishing touches for spacecraft’s tank sections.
A huge amount of work remains for both sites but the visible progress as new ship segments are stacked and welded together is undeniably cathartic and satisfying. Working 10-12 hour shifts exposed to the Texas and Florida summer sun, heat, and wildlife is in no uncertain terms bound to be a hellish experience, but at least the hard work is so obviously producing results.
The most exciting kind of grass-watching
Back in Florida, several additional Starship barrel sections are in various stages of work, at least two of which appear to be nearly ready for stacking atop the propellant tank section already being assembled. Meanwhile, propellant tank domes were spotted in different stages of fabrication inside the Florida facility’s main hangar-cum-production-line, awaiting their turn to leave the building and prepare for installation on Starship East.
All said and done, once those visible segments are installed, Starship East will (at least by appearances) be neck and neck with its Texas sibling once more. In reality, there is likely no actual race between the two sites and they are reportedly sharing any critical discoveries and lessons-learned. Nevertheless, humans are notoriously competitive and one can only begin to imagine the (hopefully friendly) rivalry forming between the geographically distinct teams.



At the same time, SpaceX’s Florida team has several home-field advantages, so to speak, owing to their proximity to the several hundred SpaceXers working at the company’s Florida launch facilities and recovery fleet. Additionally, Florida’s Starship facility is just a few dozen miles away from SpaceX’s Kennedy Space Center Pad 39A, the most likely site of Starship’s (and Super Heavy’s) first suborbital and orbital launch attempts.
At the end of the day, a little friendly internal competition and – more so – a literal Starship A/B test are bound to be a huge benefit for SpaceX’s next-gen launch vehicle program, significantly increasing the speed at which the company can make mistakes, solve problems, and get Starship ready for orbit.
Check out Teslarati’s Marketplace! We offer Tesla accessories, including for the Tesla Cybertruck and Tesla Model 3.
Elon Musk
Tesla CEO Elon Musk teases insane capabilities of next major FSD update
Tesla CEO Elon Musk teased the insane capabilities of the next major Full Self-Driving update just hours after the company rolled out version 14.2 to owners.
Tesla Full Self-Driving v14.2 had some major improvements from the previous iteration of v14.1.x. We were on v14.1.7, the most advanced configuration of the v14.1 family, before Tesla transitioned us and others to v14.2.
However, Musk has said that the improvements coming in the next major update, which will be v14.3, will be where “the last big piece of the puzzle finally lands.”
14.3 is where the last big piece of the puzzle finally lands
— Elon Musk (@elonmusk) November 21, 2025
There were some major improvements with v14.2, most notably, Tesla seemed to narrow in on the triggers that caused issues with hesitation and brake stabbing in v14.1.x.
One of the most discussed issues with the past rollout was that of brake stabbing, where the vehicle would contemplate proceeding with a route as traffic was coming from other directions.
We experienced it most frequently at intersections, especially four-way stop signs.
Elon Musk hints at when Tesla can fix this FSD complaint with v14
In our review of it yesterday, it was evident that this issue had been resolved, at least to the extent that we had no issues with it in a 62-minute drive, which you can watch here.
Some owners also reported a more relaxed driver monitoring system, which is something Tesla said it was working on as it hopes to allow drivers to text during operation in the coming months. We did not test this, as laws in Pennsylvania prohibit the use of phones at any time due to the new Paul Miller’s Law, which took effect earlier this year.
However, the improvements indicate that Tesla is certainly headed toward a much more sentient FSD experience, so much so that Musk’s language seems to be more indicative of a more relaxed experience in terms of overall supervision from the driver, especially with v14.3.
Musk did not release or discuss a definitive timeline for the release of v14.3, especially as v14.2 just rolled out to Early Access Program (EAP) members yesterday. However, v14.1 rolled out to Tesla owners just a few weeks ago in late 2025. There is the potential that v14.3 could be part of the coming Holiday Update, or potentially in a release of its own before the New Year.
News
Tesla Full Self-Driving v14.2 – Full Review, the Good and the Bad
Tesla rolled out Full Self-Driving version 14.2 yesterday to members of the Early Access Program (EAP). Expectations were high, and Tesla surely delivered.
With the rollout of Tesla FSD v14.2, there were major benchmarks for improvement from the v14.1 suite, which spanned across seven improvements. Our final experience with v14.1 was with v14.1.7, and to be honest, things were good, but it felt like there were a handful of regressions from previous iterations.
While there were improvements in brake stabbing and hesitation, we did experience a few small interventions related to navigation and just overall performance. It was nothing major; there were no critical takeovers that required any major publicity, as they were more or less subjective things that I was not particularly comfortable with. Other drivers might have been more relaxed.
With v14.2 hitting our cars yesterday, there were a handful of things we truly noticed in terms of improvement, most notably the lack of brake stabbing and hesitation, a major complaint with v14.1.x.
However, in a 62-minute drive that was fully recorded, there were a lot of positives, and only one true complaint, which was something we haven’t had issues with in the past.
The Good
Lack of Brake Stabbing and Hesitation
Perhaps the most notable and publicized issue with v14.1.x was the presence of brake stabbing and hesitation. Arriving at intersections was particularly nerve-racking on the previous version simply because of this. At four-way stops, the car would not be assertive enough to take its turn, especially when other vehicles at the same intersection would inch forward or start to move.
This was a major problem.
However, there were no instances of this yesterday on our lengthy drive. It was much more assertive when arriving at these types of scenarios, but was also more patient when FSD knew it was not the car’s turn to proceed.
Can report on v14.2 today there were ZERO instances of break stabbing or hesitation at intersections today
It was a significant improvement from v14.1.x
— TESLARATI (@Teslarati) November 21, 2025
This improvement was the most noticeable throughout the drive, along with fixes in overall smoothness.
Speed Profiles Seem to Be More Reasonable
There were a handful of FSD v14 users who felt as if the loss of a Max Speed setting was a negative. However, these complaints will, in our opinion, begin to subside, especially as things have seemed to be refined quite nicely with v14.2.
Freeway driving is where this is especially noticeable. If it’s traveling too slow, just switch to a faster profile. If it’s too fast, switch to a slower profile. However, the speeds seem to be much more defined with each Speed Profile, which is something that I really find to be a huge advantage. Previously, you could tell the difference in speeds, but not in driving styles. At times, Standard felt a lot like Hurry. Now, you can clearly tell the difference between the two.
It seems as if Tesla made a goal that drivers should be able to tell which Speed Profile is active if it was not shown on the screen. With v14.1.x, this was not necessarily something that could be done. With v14.2, if someone tested me on which Speed Profile was being used, I’m fairly certain I could pick each one.
Better Overall Operation
I felt, at times, especially with v14.1.7, there were some jerky movements. Nothing that was super alarming, but there were times when things just felt a little more finicky than others.
v14.2 feels much smoother overall, with really great decision-making, lane changes that feel second nature, and a great speed of travel. It was a very comfortable ride.
The Bad
Parking
It feels as if there was a slight regression in parking quality, as both times v14.2 pulled into parking spots, I would have felt compelled to adjust manually if I were staying at my destinations. For the sake of testing, at my first destination, I arrived, allowed the car to park, and then left. At the tail-end of testing, I walked inside the store that FSD v14.2 drove me to, so I had to adjust the parking manually.
This was pretty disappointing. Apart from parking at Superchargers, which is always flawless, parking performance is something that needs some attention. The release notes for v14.2. state that parking spot selection and parking quality will improve with future versions.
Any issues with parking on your end? 14.1.7 didn’t have this trouble with parking pic.twitter.com/JPLRO2obUj
— TESLARATI (@Teslarati) November 21, 2025
However, this was truly my only complaint about v14.2.
You can check out our full 62-minute ride-along below:
Elon Musk
SpaceX issues statement on Starship V3 Booster 18 anomaly
The incident unfolded during gas-system pressure testing at the company’s Massey facility in Starbase, Texas.
SpaceX has issued an initial statement about Starship Booster 18’s anomaly early Friday. The incident unfolded during gas-system pressure testing at the company’s Massey facility in Starbase, Texas.
SpaceX’s initial comment
As per SpaceX in a post on its official account on social media platform X, Booster 18 was undergoing gas system pressure tests when the anomaly happened. Despite the nature of the incident, the company emphasized that no propellant was loaded, no engines were installed, and personnel were kept at a safe distance from the booster, resulting in zero injuries.
“Booster 18 suffered an anomaly during gas system pressure testing that we were conducting in advance of structural proof testing. No propellant was on the vehicle, and engines were not yet installed. The teams need time to investigate before we are confident of the cause. No one was injured as we maintain a safe distance for personnel during this type of testing. The site remains clear and we are working plans to safely reenter the site,” SpaceX wrote in its post on X.
Incident and aftermath
Livestream footage from LabPadre showed Booster 18’s lower half crumpling around the liquid oxygen tank area at approximately 4:04 a.m. CT. Subsequent images posted by on-site observers revealed extensive deformation across the booster’s lower structure. Needless to say, spaceflight observers have noted that Booster 18 would likely be a complete loss due to its anomaly.
Booster 18 had rolled out only a day earlier and was one of the first vehicles in the Starship V3 program. The V3 series incorporates structural reinforcements and reliability upgrades intended to prepare Starship for rapid-reuse testing and eventual tower-catch operations. Elon Musk has been optimistic about Starship V3, previously noting on X that the spacecraft might be able to complete initial missions to Mars.