News
SpaceX, NASA targeting separate Moon launches days apart
NASA and a SpaceX customer have announced plans to launch two unrelated Moon missions days apart next month.
On October 12th, NASA confirmed that it will roll its Space Launch System (SLS) rocket out to its Kennedy Space Center LC-39A pad for the fourth time as early as November 4th. Barring surprises, the rocket’s next launch attempt is scheduled no earlier than (NET) 12:07 am EDT (17:07 UTC), November 14th. SLS is tasked with launching an uncrewed prototype of NASA’s Orion crew capsule on its way to the Moon, where the spacecraft will attempt to enter lunar orbit and conduct tests before returning to Earth.
The same day, Japanese startup ispace confirmed that HAKUTO-R M1, its first commercial Moon lander, is scheduled to launch on a SpaceX Falcon 9 rocket sometime between November 9th and 15th. While NASA has a $73M contract with ispace to develop a second-generation SERIES-2 Moon lander in the United States, the first-generation HAKUTO-R program has been an almost entirely private endeavor. The first M1 lander will attempt to deliver two rovers – one built by Japan and the other by the United Arab Emirates – and several other commercial and government payloads to the surface of the Moon.
As of 2020, HAKUTO-R is expected to weigh around 1050 kilograms (~2300 lb) at launch and has been designed to land up to 30 kilograms (~66 lb) of usable payload on the Moon. ispace has designed and built most of the lander’s structures but contracted with Europe’s ArianeGroup to provide the propulsion system and fully assemble, integrate, and test the lander in Germany.
According to ispace’s documentation [PDF], Falcon 9 will launch HAKUTO-R into a “supersynchronous” Earth orbit, where the lander will check out its systems before eventually using its own propulsion to thrust itself free of Earth’s gravity well and into the Moon’s. It expects a nominal transit from Earth orbit to the lunar surface to take at least 20 days. The lander is designed to survive up to 12 days on the Moon, during which it will attempt to operate its onboard experiments, deploy both of its tiny rovers, and transmit all the data gathered back to Earth.
The startup initially [PDF] described its arrangements with SpaceX as contracts to launch two landers as secondary payloads on two Falcon 9 rockets. In its press releases, ispace no longer specifies whether the one-ton spacecraft will be the only payload on Falcon 9. It’s possible that HAKUTO-R M1 will be a secondary payload on SpaceX’s launch of the Eutelsat 10B geostationary communications satellite, which is currently scheduled NET November 11th. In a rare move, SpaceX will reportedly expend Falcon 9’s reusable first-stage booster during the mission, leaving much more performance on the table.
Update: Launch photographer Ben Cooper reports that Falcon 9’s reusable booster will fly back to the Florida coast to land on land after launching HAKUTO-R, strongly implying that the Moon lander will actually be the rocket’s only payload.
ispace has raised approximately $210 million since it was founded in 2010 – coincidentally the same year that the US Congress forced NASA to begin developing the SLS rocket. 12 years later, there’s a chance that the first launches of SLS and HAKUTO-R could occur hours apart.
When it rolls out next month, NASA’s SLS rocket will be heading to the launch pad for the fourth time. SLS and Orion have had a less-than-smooth journey to their first launch, suffering half a decade of delays and running tens of billions of dollars over budget as a result. Once all the pieces had arrived in Florida, it took NASA and its contractors about 12 months to finish assembling SLS and Orion and begin testing the integrated rocket.
Since integrated testing began in April 2022, SLS has undergone five publicized wet dress rehearsal (WDR) tests in April, June, and September. It also attempted to launch twice on August 29th and September 3rd, although both attempts were arguably a continuation of WDR testing in everything but name. But it appears that when the rocket rolls out for the fourth time, NASA will have finally completed nearly all of the testing it should have finished before loudly proclaiming that its “Mega Moon Rocket” was ready to launch back in August.
The SLS launch debut will almost certainly take precedence over any other Cape Canaveral launch around the same time, including HAKUTO-R M1, but SpaceX could potentially launch the Moon lander roughly one day before or after NASA’s Moon rocket.
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
