News
SpaceX readies for astronaut capsule recovery backup plan as rocket drone ship deploys to landing zone
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.
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.
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.
Investor's Corner
Tesla analyst maintains $500 PT, says FSD drives better than humans now
The team also met with Tesla leaders for more than an hour to discuss autonomy, chip development, and upcoming deployment plans.
Tesla (NASDAQ:TSLA) received fresh support from Piper Sandler this week after analysts toured the Fremont Factory and tested the company’s latest Full Self-Driving software. The firm reaffirmed its $500 price target, stating that FSD V14 delivered a notably smooth robotaxi demonstration and may already perform at levels comparable to, if not better than, average human drivers.
The team also met with Tesla leaders for more than an hour to discuss autonomy, chip development, and upcoming deployment plans.
Analysts highlight autonomy progress
During more than 75 minutes of focused discussions, analysts reportedly focused on FSD v14’s updates. Piper Sandler’s team pointed to meaningful strides in perception, object handling, and overall ride smoothness during the robotaxi demo.
The visit also included discussions on updates to Tesla’s in-house chip initiatives, its Optimus program, and the growth of the company’s battery storage business. Analysts noted that Tesla continues refining cost structures and capital expenditure expectations, which are key elements in future margin recovery, as noted in a Yahoo Finance report.
Analyst Alexander Potter noted that “we think FSD is a truly impressive product that is (probably) already better at driving than the average American.” This conclusion was strengthened by what he described as a “flawless robotaxi ride to the hotel.”
Street targets diverge on TSLA
While Piper Sandler stands by its $500 target, it is not the highest estimate on the Street. Wedbush, for one, has a $600 per share price target for TSLA stock.
Other institutions have also weighed in on TSLA stock as of late. HSBC reiterated a Reduce rating with a $131 target, citing a gap between earnings fundamentals and the company’s market value. By contrast, TD Cowen maintained a Buy rating and a $509 target, pointing to strong autonomous driving demonstrations in Austin and the pace of software-driven improvements.
Stifel analysts also lifted their price target for Tesla to $508 per share over the company’s ongoing robotaxi and FSD programs.
Tesla Full Self-Driving v14.2 – Full Review, the Good and the Bad
SpaceX issues statement on Starship V3 Booster 18 anomaly
