News
SpaceX drone ship dodges high seas en route to first rocket landing of 2020
SpaceX has delayed the first orbital launch of the new year by a handful of days to allow both Falcon 9 and the drone ship it’s scheduled to land on the opportunity to dodge bad weather on the Florida coast and out in the Atlantic Ocean.
Originally scheduled to launch no earlier than December 30th, SpaceX delayed its next mission – Starlink-2 – to January 3rd for unknown reasons. Weather on the new date was unfortunately forecast to be terrible at SpaceX’s LC-40 launch pad and had a 60% chance of scrubbing the mission. SpaceX must have been at least as concerned about conditions for drone ship Of Course I Still Love You (OCISLY) in the Atlantic Ocean, as the company ultimately skipped over a 90%-GO backup window on January 4th for the latest launch target – January 6th.
Historically, only a few Falcon launches have been delayed for booster recovery purposes, but it’s been apparent that – while incredibly sturdy – some of the tacked-on equipment installed on SpaceX’s drone ships (modified barges) can be easily damaged by high seas. Perhaps more importantly, high seas (and thus a pitching drone ship deck) can make booster landings much riskier. Bad luck could easily cause a booster to cut off its landing burn at exactly sea level but still be a dozen or more feet above the drone ship’s deck if it’s coincidentally in the trough of a big swell, potentially destroying or damaging the rocket.
Ultimately, on missions where SpaceX has nothing to lose by delaying the launch, the company now puts a successful booster recovery much higher on its list of priorities. As recently as March 2018, SpaceX intentionally expended a new Falcon 9 booster because ocean conditions would have been extremely risky to OCISLY and crew and the company (or customer) had no interest in delaying the launch further to wait for calmer seas.
By all appearances, that is – for the most part – no longer the case. SpaceX would likely expend a rocket for a few days of schedule for high-priority customers like the USAF and especially NASA, where even a few days of delays could trigger several years of delays to quite literally wait for the planets to realign. It has and will continue to require a significant culture shift in the market for launch but SpaceX is clearly changing those norms and expectations bit by bit, to the point that the company was recently willing to delay Cargo Dragon launches for NASA to ensure that the mission’s Falcon 9 booster the best possible chance of recovery.
For an internal Starlink launch, delaying the mission to prevent drone ship damage and ensure Falcon 9 recovery is thus an absolute no-brainer. Starlink-2 is also partially unique because it will mark the second time a Falcon 9 booster launches for the fourth time, following on the footsteps of B1048 after it became the first booster to launch four times during SpaceX’s November 2019 Starlink-1 mission.
B1048 thus became SpaceX’s lone pathfinder for Falcon 9 booster reusability, hopefully providing excellent insight and some unequivocal physical data to determine the rocket’s health and readiness for a 5th launch. Still, even though the sample sizes available to even the most prolific orbital launch vehicles would make any statistician cringe, it’s safe to say that two data points are better than one, and B1049 – scheduled to launch for the fourth time on Starlink-2 – would thus be quite valuable to SpaceX’s recovery engineers and technicians.
Only one additional Falcon 9 booster – B1056 – has already flown three missions, meaning that SpaceX will – at best – likely have to suffice with three data points (B1048, B1049, B1056) before moving onto the next reusability milestone – launching the same booster five times. Ultimately, every time SpaceX pushes that envelope and demonstrates that Falcon boosters can be definitively reused 3 or 4 or 5 times, the company multiplies the number of launches its fleet of booster can perform by a factor of two.
For, say, the eight flightworthy boosters in SpaceX’s existing fleet, proving that a 4th reuse is possible will ultimately allow the company to squeeze an additional seven launches from existing hardware with almost zero capital investment. For now, the fourth flight of Falcon 9 boosters will remain cutting edge, but with more than three-dozen launches planned in 2020, it’s all but guaranteed that SpaceX will push the envelope of reusability like never before in the coming months.
Check out Teslarati’s Marketplace! We offer Tesla accessories, including for the Tesla Cybertruck and Tesla Model 3.
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:
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.
Tesla CEO Elon Musk teases insane capabilities of next major FSD update
Tesla Full Self-Driving v14.2 – Full Review, the Good and the Bad
