News
SpaceX’s first Falcon Heavy launch in three years eyes late-October liftoff
For the second time in 2022, SpaceX’s Falcon Heavy rocket has a firm launch date for the first time in more than three years.
Cursed by a seemingly relentless flood of delays impacting almost every one of the rocket’s payloads, Falcon Heavy made it within three or four months of ending its launch drought as recently as June 2022. At the time, the rocket was more or less ready to begin assembly, but NASA announced late that month that the Jet Propulsion Laboratory (JPL) and supplier Maxar had failed to finish qualifying software needed to power its Psyche spacecraft. Designed to journey to and enter orbit around the asteroid 16 Psyche, the complex trajectory required to reach it constrained the mission to a launch window sometime between August and October.
When JPL and Maxar were unable to properly test the spacecraft’s software in time for that window, they were forced to stand down and wait until the next earliest window, which begins in July 2023. That left Falcon Heavy with three more possible payloads to launch in 2022, but all three were chronically delayed and there was little reason to believe that even one of them would be ready to launch before 2023. However, Falcon Heavy’s single most delayed payload appears to have made a breakthrough, giving the most powerful rocket currently in operation at least one more shot at a 2022 launch.
Continuing an excellent series of reports tracking Falcon Heavy’s never-ending US military payload delays, Spaceflight Now broke the news with an official statement from the US Space Force, which confirmed that an unspecified industry partner had finally resolved payload problems that have delayed the military’s USSF-44 mission by two years. More importantly, the USSF spokesperson revealed a specific target of October 28th.
The US military has repeatedly offered implausible launch targets for USSF-44 with little to no official explanation for the mission’s delays, making it reasonable to appraise any specific launch date much like a boy crying wolf. But this particular target, announced within the same month as its date, is a bit more believable on its own.
Thankfully, it’s not on its own. On October 7th, SpaceX sent out an email confirming that Falcon Heavy is scheduled to launch USSF-44 sometime in October and asking members of the media to register for press site access and remote camera setup opportunities. It’s possible that the rocket or USSF-44 satellites will run into issues and trigger additional delays, but a press accreditation email is about as close as one can get to a believable guarantee that a secretive US military payload is on track for a SpaceX launch scheduled more than a week or so in the future.
The mission’s next major step forward will be the assembly of Falcon Heavy inside SpaceX’s main hangar at its NASA Kennedy Space Center LC-39A pad. Photos SpaceX shared last month and earlier this month of preparations for Crew-5, Falcon 9’s eighth successful astronaut launch, show that at least two of the four main stages that make up Falcon Heavy are already inside that hangar. One of two new Falcon Heavy side boosters was clearly spotted on September 30th.



The rocket’s expendable upper stage was also clearly visible in a September 23rd photo. Ordinarily, Falcon upper stages are nearly indistinguishable from each other, but the upper stage stored behind the Crew-5 upper stage in the foreground features a unique grey band around the bottom of its airframe. In July 2019, SpaceX tested another Falcon 9 upper stage with the same grey band, which a spokesperson explained was meant to improve the rocket’s longevity in orbit.
Long orbital coasts of six or more hours are necessary for some of the most challenging launch trajectories. Direct-to-geostationary launches are the most common type of mission to require long coast capabilities and are often demanded by the US military. The grey band’s purpose is to increase the amount of heating absorbed from sunlight to warm the liquid kerosene (RP-1) fuel contained within that part of the rocket. When it gets too cold, kerosene – which freezes at a much higher temperature than Falcon’s liquid oxygen oxidizer – becomes viscous and slush-like before it freezes solid. If ingested, slushy fuel would likely prevent ignition or destroy the upper stage’s Merlin engine.
USSF-44 will be SpaceX’s first direct geostationary launch attempt, explaining why the grey band has reappeared more than three years after its first test. Coincidentally, Falcon Heavy’s third and latest launch occurred in June 2019, just one month before that upper stage test. 40 months later, the rocket might finally launch again, and it will do so by attempting what is likely SpaceX’s most difficult customer mission to date. To enable the high performance required for the mission, USSF-44 will also intentionally expend a Falcon Heavy booster for the first time. The rocket’s two new side boosters will boost back to Florida and land side by side at LZ-1 and LZ-2, but its new center core will be expended after a single flight.

SpaceX has already finished converting Pad 39A’s mobile transporter/erector, which was previously set up for single-core Falcon 9 rockets. The T/E will eventually roll inside the pad’s integration hangar, confirming that Falcon Heavy has been fully assembled and is about to be installed on the structure. The rocket will then be rolled out to the pad and brought vertical for static fire testing, a process that will likely begin at least a week before the current October 28th launch target.
If testing is successful, Falcon Heavy will return to the hangar, have its fairing and USSF-44 payload installed, and roll out to the pad one last time. Stay tuned for updates on that ongoing process.
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.
