News
NASA spacecraft successfully slams into asteroid ten months after SpaceX launch
Ten months after launching into interplanetary space on a SpaceX Falcon 9 rocket, NASA’s Double Asteroid Redirect Test (DART) spacecraft has successfully impacted an asteroid moon.
Falcon 9 lifted off from Vandenberg Space Force Base (VSFB) Space Launch Complex 4 (SLC-4) carrying the 630-kilogram (~1400 lb) spacecraft on November 24th, 2021. The rocket performed flawlessly, continuing a streak of successful launches, and boosted DART on its way to a near-Earth asteroid pair.
The goal: slam into the small asteroid moon Dimorphos at an eyewatering speed of 6.3 kilometers per second (14,000 mph / Mach 18). Ten months later, the spacecraft has accomplished exactly that, successfully crashing into a target about 160 meters (530 ft) wide just 17 meters away from a perfect ‘bullseye’ after traveling for ten months and hundreds of millions of kilometers through space. Depending on the results NASA and dozens of other groups will now attempt to glean from ground and space telescopes, the successful impact could be a major leap forward for the field of planetary defense.
The main goal of planetary defense is to protect humanity’s home planet from asteroids, a threat that has routinely caused mass-extinction events throughout the multibillion-year history of life on Earth. With the technology to both detect and reach virtually all near-Earth objects (NEOs) more or less at hand, DART is the first attempt to test and verify what would seem to be the easiest and most obvious method of redirecting asteroids: knocking them off course with the spacecraft itself.
Planetary science and the behavior of things in microgravity conditions have a tendency to defy expectations, however, so testing that assumption is essential. The perfect way to do so came to DART Lead Investigator Andy Chang in a burst of mid-exercise inspiration: instead of hitting any odd NEO, a small spacecraft could slam into a tiny asteroid moon of a much larger parent asteroid. Hitting an asteroid moon would mitigate the small but nonzero risk of accidentally redirecting the target towards Earth while also amplifying the results, making them much easier to observe from tens of millions of kilometers away.
Rather than being forced to search for a virtually imperceptible change in a single asteroid’s half-billion-kilometer-long orbit, the results of hitting the right asteroid moon would be much more easily detectable as a change in the moon’s much smaller orbit around its untouched parent asteroid.
The problem is that aside from spectrographic readings that tell scientists the broad strokes of an asteroid’s composition and other telescope images that can make out the rough shape, it’s very difficult to scout the objects without actually visiting them. And given the difficulty, spacecraft have only visited a handful of the virtually countless asteroids of our solar system. Without knowing exactly what a target asteroid’s surface and subsurface are like, it’s hard to predict exactly what a spacecraft impacting that asteroid will do. A looser surface, which is what most visited asteroids appear to have, would be much worse at momentum transfer than a boulder or relatively solid surface of rock.
As an example, as DART rapidly approached and revealed more detailed views of the surface of Didymos and Dimorphos in its final minutes, Chang himself was surprised to see just how rough and boulder-strewn the surface of both asteroids were. Then, after the spacecraft impact, many scientists were also surprised to almost immediately see a massive cloud of dust – easily visible from ground-based telescopes – ejected from Dimorphos.
Despite the DART spacecraft’s eventful demise, the fun has only just begun on the ground as scientists attempt to solve that riddle (and many others) and begin searching for changes in Dimorphos’ orbit. Data will soon arrive from even larger and more prestigious observatories, including NASA’s space-based Hubble and Webb Space Telescopes. Italian companion cubesat LICIACube, which deployed from DART shortly before impact, will also downlink images it took up close, potentially offering the most detailed view of the impact for years.
Meanwhile, the European Space Agency (ESA) is developing a spacecraft called Hera that will launch in 2024 and attempt to enter orbit around Didymos and Dimorphos as early as late 2026 to examine the aftermath of DART’s last stand in even greater detail.
In the more distant future, particularly if the international science community ultimately concludes that DART did successfully redirect an asteroid (moon), it’s possible that the mission will help to kickstart an entirely new global project and fleet of spacecraft that will stand ready to protect Earth if the need ever truly arises. With a little luck and a modest amount of government funding, humanity may soon be able to entirely eradicate one of the most infamous sources of mass extinction.
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
