News
SpaceX’s Falcon 9 Block 5 fleet preps for dual drone ship booster landings
SpaceX engineers and technicians have just completed the second on-pad static fire of a Falcon 9 Block 5 booster, and another test is scheduled on the opposite coast for a different upgraded booster in roughly two days.
Penciled in on July 22 and July 25, these imminent back to back launches will mark the effective beginning of the highly-reusable Block 5 era now that all older versions have flown for the last time. Crucially, the practice of intentionally expending reused boosters will almost certainly come to an end for the indefinite future, beginning with these next missions. Both new cores will land aboard drone ship pair Just Read The Instructions (JRTI; West Coast) and Of Course I Still Love You (OCISLY; East Coast), and both autonomous vessels will be simultaneously stationed at sea for the second time ever.
Static fire test of Falcon 9 complete—targeting early morning launch on Sunday, July 22 of Telstar 19 VANTAGE from Pad 40 in Florida.
— SpaceX (@SpaceX) July 18, 2018
This rare dual drone ship deployment will likely become a regular occurrence for SpaceX Falcon 9 and Falcon Heavy recoveries over the course of the rest of 2018 and 2019, as higher rates of launch from both East and West coast launch facilities and the unlikelihood of a Block 5 booster being expended will translate to a much greater need for the giant rocket recovery vessels.
In fact, the 7-10 days it takes drone ships to travel from their ports of call to booster landing points and back to port again will likely be the most insurmountable constraint on launch cadence, at least for the Falcon family – high energy missions could only be completed every ten or so days on the East Coast, at least until a third drone ship is brought online. To be named A Shortfall of Gravitas (ASoG), a third autonomous spaceport drone ship (ASDS) is in fact planned as an expansion of SpaceX’s fleet, although it’s unknown if the vessel is under construction now, nor when exactly it’s expected to enter service.
SpaceX’s next three missions from its Florida-based LC-40 pad all happen to feature Block 5 Falcon 9 boosters tasked with placing heavy communications satellites in high-energy orbits, and all three launches are currently paced roughly two weeks apart – July 22, August 2, and August 18. That consistent two-week cadence on SpaceX’s launch schedule is for the most part driven equally by launchpad readiness and drone ship availability, both of which require some amount of refurbishment or maintenance after launches/landings.
On the West Coast will be the launch of Iridium NEXT-7 on July 25, carrying ten Iridium NEXT satellites atop a Block 5 booster. That booster – as well as at least two of the three East coast boosters – will be fresh from the factory, conducting (hopefully) the first of many future missions apiece. Excitingly, the planned recovery attempt after Iridium-7 will bring to an end a nearly 10-month drought of rocket landings aboard drone ship JRTI. Further, it looks like chances are good that Iridium-7 will also see recovery vessel Mr Steven break in his massive new net and arms in with an attempted catch of a Falcon 9 fairing half.
- A SpaceX technician works aboard the rain-soaked drone ship Just Read The Instructions, March 2018. (Pauline Acalin)
- The drone ship Of Course I Still Love You spotted in Port Canaveral, FL last December. (Instagram /u/ johnabc123)
- Mr Steven testing his new net in a series of sea trials, July 11
Follow us for live updates, peeks behind the scenes, and photos from Teslarati’s East and West Coast photographers.
Teslarati – Instagram – Twitter
Tom Cross – Twitter
Pauline Acalin – Twitter
Eric Ralph – Twitter
News
Tesla AI and Autopilot VP hints that Robovan will have RV conversions
Tesla’s vice president of AI and Autopilot software, Ashok Elluswamy, hinted at the linitiative in a reply to Y Combinator CEO Garry Tan.
It appears that Tesla is indeed considering an RV in its future pipeline, though the vehicle that would be converted for the purpose would be quite interesting. This is, at least, as per recent comments by a Tesla executive on social media platform X.
Robovan as an RV
Tesla’s vice president of AI and Autopilot software, Ashok Elluswamy, hinted at the linitiative in a reply to Y Combinator CEO Garry Tan, who called for a startup to build RVs with Full Self-Driving capabilities. In his reply, Elluswamy simply stated “On it,” while including a photo of Tesla’s autonomous 20-seat people mover.
Tesla unveiled the Robovan in October 2024 at the “We, Robot” event. The vehicle lacks a steering wheel and features a low floor for spacious interiors. The vehicle, while eclipsed by the Cybercab in news headlines, still captured the imagination of many, as hinted at by X users posting AI-generated images of Robovan RV conversions with beds, kitchens and panoramic windows on social media platforms. One such render by Tesla enthusiast Mark Anthony reached over 300,000 views on X.
Elon Musk on the Robovan
Elon Musk addressed the Robovan’s low profile in October 2024, stating the van uses automatic load-leveling suspension that raises or lowers based on road conditions. The system maintains the futuristic look while handling uneven pavement, Musk wrote on X. The CEO also stated that the Robovan is designed to be very airy inside, which would be great for an RV.
“The view from the inside is one of extreme openness, with visibility in all directions, although it may appear otherwise from the outside. The unusually low ground clearance is achieved by having an automatic load-leveling suspension that raises or lowers, based on smooth or bumpy road conditions,” Musk stated.
Elluswamy’s response on X suggests that Tesla is considering a Robovan RV conversion, though it would be interesting to see how the company will make the vehicle capable of reaching campsites. The Robovan has a very low ground clearance, after all, and campsites tend to be in unpaved areas.
News
Tesla tinkering with Speed Profiles on FSD v14.2.1 has gone too far
Tesla recently released Full Self-Driving (FSD) v14.2.1, its latest version, but the tinkering with Speed Profiles has perhaps gone too far.
We try to keep it as real as possible with Full Self-Driving operation, and we are well aware that with the new versions, some things get better, but others get worse. It is all part of the process with FSD, and refinements are usually available within a week or so.
However, the latest v14.2.1 update has brought out some major complaints with Speed Profiles, at least on my end. It seems the adjustments have gone a tad too far, and there is a sizeable gap between Profiles that are next to one another.
Tesla FSD v14.2.1 first impressions:
✅ Smooth, stress-free highway operation
✅ Speed Profiles are refined — Hurry seems to be limited to 10 MPH over on highways. Switching from Mad Max to Hurry results in an abrupt braking pattern. Nothing of concern but do feel as if Speed…— TESLARATI (@Teslarati) November 29, 2025
The gap is so large that changing between them presents a bit of an unwelcome and drastic reduction in speed, which is perhaps a tad too fast for my liking. Additionally, Speed Profiles seem to have a set Speed Limit offset, which makes it less functional in live traffic situations.
Before I go any further, I’d like to remind everyone reading this that what I am about to write is purely my opinion; it is not right or wrong, or how everyone might feel. I am well aware that driving behaviors are widely subjective; what is acceptable to one might be unacceptable to another.
Speed Profiles are ‘Set’ to a Speed
From what I’ve experienced on v14.2.1, Tesla has chosen to go with somewhat of a preset max speed for each Speed Profile. With ‘Hurry,’ it appears to be 10 MPH over the speed limit, and it will not go even a single MPH faster than that. In a 55 MPH zone, it will only travel 65 MPH. Meanwhile, ‘Standard’ seems to be fixed at between 4-5 MPH over.
This is sort of a tough thing to have fixed, in my opinion. The speed at which the car travels should not be fixed; it should be more dependent on how traffic around it is traveling.
It almost seems as if the Speed Profile chosen should be more of a Behavior Profile. Standard should perform passes only to traffic that is slower than the traffic. If traffic is traveling at 75 MPH in a 65 MPH zone, the car should travel at 75 MPH. It should pass traffic that travels slower than this.
Hurry should be more willing to overtake cars, travel more than 10 MPH over the limit, and act as if someone is in a hurry to get somewhere, hence the name. Setting strict limits on how fast it will travel seems to be a real damper on its capabilities. It did much better in previous versions.
Some Speed Profiles are Too Distant from Others
This is specifically about Hurry and Mad Max, which are neighbors in the Speed Profiles menu. Hurry will only go 10 MPH over the limit, but Mad Max will travel similarly to traffic around it. I’ve seen some people say Mad Max is too slow, but I have not had that opinion when using it.
In a 55 MPH zone during Black Friday and Small Business Saturday, it is not unusual for traffic around me to travel in the low to mid-80s. Mad Max was very suitable for some traffic situations yesterday, especially as cars were traveling very fast. However, sometimes it required me to “gear down” into Hurry, especially as, at times, it would try to pass slower traffic in the right lane, a move I’m not super fond of.
We had some readers also mention this to us:
The abrupt speed reduction when switching to a slower speed profile is definitely an issue that should be improved upon.
— David Klem (@daklem) November 29, 2025
After switching from Mad Max to Hurry, there is a very abrupt drop in speed. It is not violent by any means, but it does shift your body forward, and it seems as if it is a tad drastic and could be refined further.
News
Tesla’s most affordable car is coming to the Netherlands
The trim is expected to launch at €36,990, making it the most affordable Model 3 the Dutch market has seen in years.
Tesla is preparing to introduce the Model 3 Standard to the Netherlands this December, as per information obtained by AutoWeek. The trim is expected to launch at €36,990, making it the most affordable Model 3 the Dutch market has seen in years.
While Tesla has not formally confirmed the vehicle’s arrival, pricing reportedly comes from a reliable source, the publication noted.
Model 3 Standard lands in NL
The U.S. version of the Model 3 Standard provides a clear preview of what Dutch buyers can expect, such as a no-frills configuration that maintains the recognizable Model 3 look without stripping the car down to a bare interior. The panoramic glass roof is still there, the exterior design is unchanged, and Tesla’s central touchscreen-driven cabin layout stays intact.
Cost reductions come from targeted equipment cuts. The American variant uses fewer speakers, lacks ventilated front seats and heated rear seats, and swaps premium materials for cloth and textile-heavy surfaces. Performance is modest compared with the Premium models, with a 0–100 km/h sprint of about six seconds and an estimated WLTP range near 550 kilometers.
Despite the smaller battery and simpler suspension, the Standard maintains the long-distance capability drivers have come to expect in a Tesla.
Pricing strategy aligns with Dutch EV demand and taxation shifts
At €36,990, the Model 3 Standard fits neatly into Tesla’s ongoing lineup reshuffle. The current Model 3 RWD has crept toward €42,000, creating space for a more competitive entry-level option, and positioning the new Model 3 Standard comfortably below the €39,990 Model Y Standard.
The timing aligns with rising Dutch demand for affordable EVs as subsidies like SEPP fade and tax advantages for electric cars continue to wind down, EVUpdate noted. Buyers seeking a no-frills EV with solid range are then likely to see the new trim as a compelling alternative.
With the U.S. variant long established and the Model Y Standard already available in the Netherlands, the appearance of an entry-level Model 3 in the Dutch configurator seems like a logical next step.




