News
SpaceX moves next high-altitude Starship to launch pad after fixing fall damage
Update: Right on schedule, SpaceX rolled Starship serial number 9 (SN9) out of its ‘high bay’ assembly roost and transported the 50-meter-tall (~165 ft) stainless steel rocket to a launch pad about a mile down the road.
Wasting no time at all after having preemptively delivered a large crane from factory to pad the day prior, SpaceX began the process of lifting and installing Starship SN9 on one of two simple launch mounts less than three hours after arrival and began securing the rocket to the stand less than an hour after that. As discussed below, it’s nothing short of spectacular (and possibly unprecedented) that Starship SN9 was a victim of a workstand collapse, suffered some damage as a result, had that damage repaired or parts replaced, and was ready to roll to the launch pad to start pre-launch testing within a span of eleven days.
Additionally, SN9’s arrival means that SpaceX has now delivered a second complete Starship less than two weeks after Starship SN8 became the first full-size prototype to launch to high altitude atop multiple Raptor engines and skydive back to Earth. With the landing pad yet to be fully cleared after that launch debut, the crash-landed wreckage of SN8’s nose is even visible behind Starship SN9 in unofficial coverage of the new rocket’s pad transport and launch mount installation. As of December 22nd, SpaceX has one more road closure scheduled on Dec 23, followed by a trio from 8 am to 5 pm CST (UTC-6) from Dec 28-30. Stay tuned for updates as SpaceX prepares the second full-size Starship ever for tank proof and static fire testing!
A handful of days after a workstand collapse threatened to end SpaceX’s next high-altitude Starship before it could leave the cradle, the rocket appears to have shrugged off whatever damage was caused with ease.
On the morning of December 11th and less than 24 hours after SpaceX investors and VIPs like COO Gwynne Shotwell and CEO Elon Musk were standing almost underneath the rocket, an unknown issue cause Starship SN9’s workstand to partially collapse. Seemingly through sheer luck, the part of the circular stand that collapsed was towards the corner of the ‘high bay’ building housing SN9, causing the rocket to tip around five degrees before colliding with the wall’s steel frame.
Again, by some stroke of luck, the same angle of Starship SN9’s fall that prevented the rocket from tipping over onto Super Heavy’s in-work tank section (with workers possibly inside) seemingly allowed its flaps to absorb the bulk of that impact. One of two pairs used to keep the ship steady during a skydiver-like freefall maneuver, SN9’s forward and aft starboard flaps suffered obvious damage, perhaps unintentionally functioning like the crumple zones designed to protect passengers during car crashes.
Aside from one or two subtle dents caused by the thoroughly off-axis stresses, the rest of the fully-assembled vehicle remained visibly untouched, though it was a near-complete unknown if Starship was capable of surviving such an ordeal. For 99% of the world’s rockets, almost all of which are either built out of aluminum or carbon fiber, tipping from a vertical position into a steel wall at anything less than a snail’s pace would likely be the end of any normal propellant tank – probably up to and including even SpaceX’s own reusable Falcon boosters. At a minimum, extensive repairs would be required.
On December 20th, nine days after the incident and six days after a crane lifted SN9 back into a stable position, SpaceX quietly replaced the Starship’s crumpled forward flap after having removed both damaged flaps in the days prior. The installation of that replacement flap – possibly taken from Starship SN10’s nose – all but confirmed a best-case scenario, as it would be hard to remove the damaged hardware and install a new flap so quickly if the underlying hinge and mounting mechanisms had been damaged in the fall. If only the aft – but not forward – flap mechanism was somehow damaged, it would also make little sense to install a new forward flap.
Meanwhile, in another kind of encouraging sign, SpaceX moved the crane needed to lift Starships onto the launch mount from the build site to the launch pad on December 21st – right on schedule. It’s extremely unlikely that SpaceX would complete that move unless it was confident that a Starship prototype would be ready to roll to the launch pad, further implying that Starship SN9 really has shrugged off its workplace accident after less than two weeks of delays. Stay tuned for updates – road closures that could be used to transport SN9 are still in place from around 8 am to 5 pm CST on December 22nd and 23rd.
Tesla Full Self-Driving has officially landed in a new country today, its seventh overall after it launched in both Australia and New Zealand earlier this year.
On Sunday, Tesla owners in South Korea reported that the company’s Full Self-Driving (Supervised) had started arriving in their vehicles. Owners reported that it was v14.1.4, which is not the latest version available in other countries, but is one of the most recent releases Tesla has deployed to drivers:
From 6 to 7
Tesla Full Self-Driving has launched in South Korea; the 7th country to have FSD https://t.co/X6gm1SyoxV
— TESLARATI (@Teslarati) November 23, 2025
This marks the seventh country in which Tesla has enabled its Full Self-Driving suite, following the United States and Puerto Rico, Canada, China, Mexico, Australia, and New Zealand.
Tesla launched Full Self-Driving most recently in Australia and New Zealand about three months ago. The expansion is a major breakthrough for the company as it aims to launch Full Self-Driving on a global scale.
However, the company’s biggest challenge thus far has been getting European regulatory agencies to handle the red tape that has inhibited Tesla from launching its semi-autonomous driving suite on the continent. Recently, it admitted that it sees a pathway through Dutch regulatory bodies, which seem to be the most willing to work with Tesla to get FSD in Europe.
Tesla Full Self-Driving appears to be heading to Europe soon
The company said that it has driven over 1 million kilometers safely on European roads across 17 different countries in internal testing. But its path to success will be by “partnering with the Dutch approval authority RDW to gain exemption for the feature. This involves proving compliance with existing regulations (UN-R-171 DCAS) + filing an exemption (EU Article 39) for yet-to-be-regulated behaviors like Level 2 systems off-highway, system-initiated lane changes with hands-off the wheel, etc.”
Perhaps the expansion into Europe will be the biggest challenge for Tesla, but it could also yield major results and advantages for the company moving forward. Tesla said it hopes to have FSD available in Europe sometime early next year.
For now, the expansion in South Korea is the latest win for Tesla and its self-driving efforts. In the U.S., it now turns its focus toward fully autonomous operation, as it works with state agencies to launch Robotaxi outside of Texas, California, and most recently, Arizona.
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.
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:
Tesla Full Self-Driving lands in a new country, its 7th
Tesla CEO Elon Musk teases insane capabilities of next major FSD update
