Connect with us

News

SpaceX, NASA set to launch humanity’s first ‘dinosaur avenger’ spacecraft [webcast]

Published

on

SpaceX is firmly on track to launch NASA’s Double Asteroid Redirection Test (DART) mission – sometimes half-seriously referred to as the first spacecraft designed to avenge the dinosaurs – at 10:21 pm PST, Tuesday, November 23rd (06:21 UTC 24 Nov).

Weighing about 622 kilograms (1370 lb) at liftoff, the Johns Hopkins-built spacecraft will be sent directly towards the binary Didymos asteroid system by a SpaceX Falcon 9 rocket, marking the company’s first interplanetary launch for a paying customer – the first of many more to come. Though DART carries a first-of-its-kind electric thruster and plenty of xenon fuel, Falcon 9 is expected to do almost all of the work, leaving the spacecraft to perform a few small trajectory correction burns with simple chemical thrusters as it homes in on Didymos’ moon Dimorphos.

Falcon 9 is ready for its first interplanetary launch. (NASA)

After liftoff, Falcon 9 will send DART on a trajectory that will take around ten months to reach Dimorphos. About 10 days before that ‘arrival,’ Italian-built cubesat LICIACube will separate from DART and back a few kilometers away. As a result, LICIACube will intentionally miss both asteroids but will be as close as possible to ensure that the two cameras it carries have a front-row seat when DART slams into Dimorphos at 6.6 km/s (4.1 mi/s). Interestingly, while the goal is obviously to not miss, a DART project manager indicated that the spacecraft would probably have plenty of longevity – and 90% of its electric thruster propellant – to retarget a different asteroid system in the event it somehow misses.

If it succeeds, though, NASA anticipates that it’ll be able to observe a slight 1.5% change in Dimorphos’ orbital period (how long it takes to orbit Didymos) with Earth-based telescopes. The most important part of the mission will be confirming whether those theoretical estimates are accurate and, if they aren’t, which assumptions were wrong. Planetary defense is a brand new science and DART will be its first truly verifiable test, so it’s more likely than not that most prelaunch predictions will be somewhat wrong and that determining why they were wrong will help scientists learn about the behavior of asteroids.

Perhaps one day – building upon DART, follow-up reconnaissance mission HERA, and other asteroid missions like Hayabusa2 and OSIRIS-REx – NASA and other space agencies will team up to develop a fleet of planetary defense spacecraft that can intentionally redirect asteroids that threaten Earth, preventing catastrophic impacts like the one that likely wiped out 75% of species and virtually all nonavian dinosaurs around 66 million years ago.

Watch SpaceX’s first interplanetary Falcon 9 launch live at the webcast below, likely beginning around 9:50 pm PST (05:50 UTC).

Advertisement
-->

Eric Ralph is Teslarati's senior spaceflight reporter and has been covering the industry in some capacity for almost half a decade, largely spurred in 2016 by a trip to Mexico to watch Elon Musk reveal SpaceX's plans for Mars in person. Aside from spreading interest and excitement about spaceflight far and wide, his primary goal is to cover humanity's ongoing efforts to expand beyond Earth to the Moon, Mars, and elsewhere.

Advertisement
Comments

Elon Musk

Tesla CEO Elon Musk teases insane capabilities of next major FSD update

Published

on

Credit: Tesla China/Weibo

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.”

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.

Continue Reading

News

Tesla Full Self-Driving v14.2 – Full Review, the Good and the Bad

Published

on

Credit: Teslarati

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.

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.

However, this was truly my only complaint about v14.2.

You can check out our full 62-minute ride-along below:

Continue Reading

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. 

Published

on

Credit: SpaceX/X

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.

Advertisement
-->
Continue Reading