Connect with us

News

SpaceX readies for astronaut capsule recovery backup plan as rocket drone ship deploys to landing zone

The SpaceX autonomous spaceport drone ship Of Course I Still Love You returns empty to Port Canaveral following a Starlink mission missed landing attempt. (Credit: Richard Angle for Teslarati)

Published

on

Mission objectives of the SpaceX Crew Dragon Demo-2 test flight, have already commenced days ahead of the scheduled launch attempt. On Wednesday, May 27th at 4:33 pm EDT, Elon Musk’s rocket launching – and landing – company, SpaceX, will set out to achieve more firsts than it has ever attempted in one launch. The final Crew Dragon test flight will shuttle NASA astronauts Bob Behnken and Doug Hurley to the International Space Station for the very first time. Along with the primary mission objective to deliver the astronauts safely, many secondary objectives are built into the mission profile. One of which is autonomously turning the Falcon 9 booster around shortly after launch to land on a floating barge in the middle of the Atlantic Ocean.

During the late hours of Saturday, May 23rd, a trusted veteran member of the SpaceX fleet of recovery vessels, Tug Hawk, returned to Port Canaveral to transport SpaceX’s autonomous spaceport drone ship, Of Course I Still Love You (OCISLY) to the designated booster recovery zone some 510km downrange. It seems that Tug Hawk and its crew returned specifically to assist with the recovery efforts of SpaceX’s highest-profile launch to date as there was already another tug at Port Canaveral available to assist that was not used. The arrival was captured by long-time port activity documenter, Julia Bergeron, and reported by the unofficial Twitter SpaceX recovery vessel tracking account, SpaceXFleet.

The SpaceX recovery fleet portion of the Demo-2 mission got underway on the morning of Sunday (May 24th). Space Coast local Greg Scott was at Port Canaveral to capture Tug Hawk’s departure with OCISLY in tow just twelve hours after arriving. About an hour later, the OCISLY support vessel that carries cargo and crew essential for booster recovery efforts, GO Quest, departed. It will take Tug Hawk and OCISLY approximately two days to travel to the recovery zone, arriving about 24 hours before the launch attempt.

The propulsive landing of a booster at sea is not a new concept for SpaceX. However, it is a practice that can be somewhat tricky to get right every time due to a multitude of factors. Recently, SpaceX suffered the loss of the Falcon 9 boosters B1056 and B1048 following recent Starlink satellite launches. Both boosters suffered unrelated issues with high winds and software glitches resulting in failed attempts to stick the landing on OCISLY. However, SpaceX successfully demonstrated the reliability of the Falcon 9 landing capability with the flawless launch and landing of the April 22nd Starlink Falcon 9 B1051 booster.

A special circumstance of the Demo-2 mission is the added recovery requirements of the Crew Dragon capsule. With Crew Dragon launching from LC-39A at the Kennedy Space Center in Florida and splashdown designated for the Atlantic Ocean, various recovery zones span almost the entire length of the United States’ eastern seaboard and across the Atlantic Ocean to Ireland. Special recovery zones also are located throughout the Gulf of Mexico.

Typically, the recovery of a crew capsule would only be thought to occur upon mission end when it is on approach for splashdown after re-entry. However, the specially equipped SpaceX Crew Dragon recovery vessels, GO Searcher and GO Navigator, are required to be able to respond to a number of locations during launch and through the entire duration of Crew Dragon’s time on orbit chasing down the International Space Station prior to docking – for Demo-2 that will be nineteen hours. This is to ensure that in the unlikely event of Crew Dragon experiencing an emergency pad or launch abort scenario, the crew aboard can be safely rescued.

Advertisement
-->

To this end, GO Searcher departed Port Canaveral days ago destined for the Naval Air Station in Pensacola on Florida’s west coast. GO Navigator will remain at Port Canaveral until Crew Dragon returns for a splashdown following the conclusion of Demo-2. Dual Dragon recovery vessels stationed on either side of Florida ensures that Hurley and Behnken can be rescued should they require emergency recovery.

Should Demo-2 pass SpaceX’s upcoming final Launch Readiness Review scheduled for Monday, May 25th, all will proceed toward the launch attempt on Wednesday, May 27th at 4:33 pm EDT.

Check out Teslarati’s newsletters for prompt updates, on-the-ground perspectives, and unique glimpses of SpaceX’s rocket launch and recovery processes.

Advertisement
-->

Space Reporter.

Advertisement
Comments

News

Tesla Full Self-Driving lands in a new country, its 7th

Published

on

Credit: Tesla Korea

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:

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.

Continue Reading

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