News
SpaceX fires Falcon Heavy’s 27 booster engines ahead of “most difficult launch ever”
For the third time ever, SpaceX has successfully performed a critical static-fire test of an integrated Falcon Heavy, briefly igniting all 27 of its Merlin 1D engines to verify the health and readiness of the rocket.
Per SpaceX’s official confirmation, a “quick-look” inspection of static fire telemetry has indicated that the company’s Falcon Heavy rocket is ready for its second launch in less than three months, a milestone that could also allow both flight-proven side boosters to tie SpaceX’s own record for booster turnaround. Falcon Heavy Flight 3 is now scheduled to launch the US Air Force’s Space Test Program 2 (STP-2) mission no earlier than 11:30 pm ET (03:30 UTC), June 24th. According to SpaceX CEO Elon Musk, the mission will unequivocally be the company’s “most difficult launch ever”.
Coincidentally, on top of being Falcon Heavy’s first scheduled night launch, STP-2 has now also marked the massive rocket’s first nighttime static fire. During this critical test, Falcon Heavy briefly ignites all 27 of its three boosters’ Merlin 1Ds and throttles the engines up to full thrust, much like airliners sometimes set their brakes and throttle up before attempting to take off. The difference between Falcon Heavy and passenger aircraft is nevertheless rather significant, given that Falcon Heavy produces ~15x the thrust of an A380 – the world’s most powerful mass-produced passenger aircraft – at liftoff: 22,820 kN (5.1M lbf) to the massive jet’s meager 1,440 kN (0.3M lbf).
Despite all of that thrust, Falcon Heavy is held down during static fire by eight accurately-named hold-down clamps, themselves a part of a massive transport/erector, which is itself anchored directly to Pad 39A’s concrete foundation. In short, Falcon Heavy (and especially Falcon 9) is not going anywhere until those hold-down clamps are explicitly released. Thanks to SpaceX’s avoidance of the solid rocket boosters used by almost every other modern launch vehicle, Falcon 9 and Heavy rockets can abort at any point prior to clamp release, offering a uniquely broad abort capability.
As such, not only does SpaceX’s dedicated pre-launch static fire fully test the rocket’s health, but the same procedure is essentially repeated in the seconds before clamp release during an actual orbital launch attempt. If at any point Falcon 9’s autonomous onboard computer decides that it doesn’t like any of the thousands of channels of telemetry it’s constantly analyzing, it can command an engine shutdown and total launch abort even if all first stage engines have already ignited and reached full thrust. If routine McGregor, TX acceptance testing – also involving a full static fire – is accounted for, every single Falcon 9 booster technically completes three fully-integrated static fires before its inaugural liftoff. Falcon Heavy is slightly different, as each booster is independent test-fired in Texas but the integrated rocket can only perform static fires at Pad 39A.
After those three critical tests, flight-proven Falcon boosters are subjected to the less stringent few-second static fires SpaceX performs at the launch pad 3-7 days before a given launch. With Falcon Heavy Flight 3, the rocket’s center core, upper stage, and payload fairing are all brand new, fresh from either SpaceX’s Hawthorne factory or McGregor acceptance testing. However, both side cores – Block 5 boosters B1052 and B1053 – are flight-proven, having successfully completed their first launches and landings on April 11th, less than 70 days ago.
Set by regular old Falcon 9 boosters, SpaceX’s current record for booster turnaround time (time between two launches) is 71 days (set in June 2018), while the Block 5 upgrade’s record stands at 74 days (set in October 2018). If Falcon Heavy’s STP-2 launch holds strong on June 24th, B1052 and B1053 will simultaneously tie SpaceX’s Block 5 turnaround record. This would be accomplished despite the added pressure from the US Air Force’s decision to use STP-2 as a sort of dress rehearsal for certifying all flight-proven commercial rockets, an honor (and burden) that likely added extra work, oversight, and scrutiny to the process of refurbishing and relaunching B1052 and B1053.
“[T]he US Air Force has decided that STP-2 presents an excellent opportunity to begin the process of certifying flight-proven SpaceX rockets for military launches. The STP-2-related work is more of a preliminary effort for the USAF to actually figure out how to certify flight-proven commercial rockets, but it will still be the first time a dedicated US military mission has flown on a flight-proven launch vehicle. Down the road, the processes set in place thanks – in part – to STP-2 and Falcon Heavy may also apply to aspirational rockets like Blue Origin’s New Glenn and ULA’s “SMART” proposal for Vulcan reuse.”
— Teslarati.com, 06/16/2019
In a last-second surprise, SpaceX updated Falcon Heavy center core B1057’s planned drone ship landing site from a brief 40 km (25 mi) to more than 1240 km (770 mi) off the coast of Florida. SpaceX set its current record for recovery distance less than three months ago during Falcon Heavy’s commercial launch debut, in which Block 5 center core B1055 landed nearly 970 km (600 mi) offshore on drone ship Of Course I Still Love You (OCISLY). If all goes well, B1057 – the second finished Block 5 center core – will absolutely crush its predecessor’s record, implying that the booster will likely be subjected to SpaceX’s most difficult reentry and recovery yet.
For more on what CEO Elon Musk describes as “[SpaceX’s] most difficult launch ever”, check out these previous articles on an unexpected ultra-fast booster reentry and the extraordinary challenge facing Falcon upper stage.
Check out Teslarati’s Marketplace! We offer Tesla accessories, including for the Tesla Cybertruck and Tesla Model 3.
A new report from Reuters claims that a transport authority in Sweden is pushing back against the approval of Tesla’s Full Self-Driving suite because it will travel over speed limits.
The report says the Swedish Transport Administration (TRV) recommends the European Union votes against FSD’s approval. TRV believes it should not be approved until Tesla disables FSD’s ability to speed.
TRV sent a letter to the European Union’s Technical Committee on Motor Vehicles (TCMV), which is set to meet on June 30 to discuss the potential approval of the Tesla FSD suite in the country. Tesla, which has received various approvals in Europe over the past two months, has not provided a comment.
Teslas operating on FSD do travel over the speed limit, depending on the Speed Profile that is chosen. Drivers have the ability to disengage FSD at any point; Tesla specifically states that those supervising the suite are responsible for its actions.
Let’s cut to the chase: humans operating any vehicle speed almost daily in the United States. Realistically, speed limits in the U.S. are more frequently treated as speed minimums. However, other countries are different, and driving behaviors are less aggressive.
TRV believes that “allowing automated systems to systematically exceed legal speed limits…risks undermining both the legal framework and the expected safety benefits of vehicle automation,” the report stated. It’s surprising that Tesla has not received this claim from other countries previously.
This could be a good argument to bring Max Speed back, the setting that previously allowed the driver to choose the absolute fastest the car would travel.
This would still put the responsibility of supervision in the hands of the driver. It would allow the driver to choose whether the car would travel over the speed limit or not, acknowledging that they set the speed, and if they get pulled over, there would be no ability to argue it.
However, it does not seem as if this is something Tesla will do, especially considering many U.S. drivers have requested the feature in an effort to eliminate speeding or at least tone it down. The company has not shown any interest in bringing it back.
Tesla has approvals for FSD in Europe in Estonia, Lithuania, Denmark, the Netherlands, and Belgium.
Tesla is going to let you guide Full Self-Driving with Grok in 3 months, CEO Elon Musk confirmed on X.
The response from Musk, which revealed Tesla plans to allow drivers to effectively control the car and its navigation more explicitly using Grok, puts the feature for about September.
A Tesla owner said that Full Self-Driving is great, but owners should be able to “converse with Grok like we can with an Uber driver.” She then used examples like, “Grok, turn right here,” and “Drop us off right here, we’ll walk due to traffic,” and finally,” Drop at entrance first, then park far away.”
Coincidentally, the final piece of dialogue would also mean features like Banish are potentially on the way soon.
This functionality will be there in about 3 months or so
— Elon Musk (@elonmusk) June 18, 2026
Banish is also referred to as “Reverse Summon,” and would enable the car to self-park while dropping occupants off at their destination.
This would be a great way to improve the overall experience while supervising FSD. Navigation is already a major painpoint that many owners complain about. Manual overrides when a maneuver is requested or canceled (like using the turn signal stalk to override a navigation route), do not always work.
The feature could be especially useful in street parking scenarios in a city, where spots are sometimes tough to come by. Many of us who grab dinner in a more populated area will park a street or two over from wherever we’re going, because sometimes you know that’s the best you will get. If a driver using FSD could say, “Hey Grok, turn right here on Queen St. and park in that open spot on the right,” it could save a lot of confusion FSD might have on its own.
Musk teased that a similar feature was “coming” back in February:
Tesla Full Self-Driving set to get an awesome new feature, Elon Musk says
It is certainly surprising that Tesla is doing it at this point. The company’s more recent moves have been more evident of taking control and inputs away from humans and putting them in the AI’s hands more frequently. The biggest example of this was taking away Max Speed in AI4 cars, giving us Speed Profiles, and not having any input on the fastest speed the car will travel.
Of course, giving navigation preferences to Grok is availble already in Teslas, but not at the drop of a hat. Instead, you can suggest a certain route at the beginning of your drive.
Here’s an example of that from December:
🚨🏈 I am taking my parents and Fiancee to the @Ravens game next weekend and asked @Grok to help me route my @Tesla through a specific neighborhood to reach the correct Lot we will park in.
This is a great example of the new @grok nav integration with the Tesla Holiday Update: pic.twitter.com/rPp4I7q8Yv
— TESLARATI (@Teslarati) December 13, 2025
Finally, the original post that Musk responded to mentioned a parking preference after dropping off the occupants, which describes the Banish feature that Tesla has teased for years.
We’re not sure if Musk was responding more to the ability to guide the car with Grok, or whether he also was including Banish in the three-month prediction timeframe.
A close-up image of a Cybercab engineering vehicle in Peabody, Massachusetts, reveals a compact triangular side repeater camera housing equipped with an integrated washer mechanism.
This seemingly small hardware addition could prove to be one of the most critical components for achieving reliable, unsupervised Full Self-Driving (FSD) — not just for the dedicated Robotaxi but potentially for existing AI4-equipped vehicles as well.
The washer system’s importance cannot be overstated in Tesla’s vision-only autonomy approach. Cameras are the sole sensory input for the neural networks powering FSD, constantly interpreting the environment for safe navigation. In real-world conditions, however, lenses quickly accumulate rain, snow, mud, dust, or road spray.
Many of us Tesla owners, especially those who deal with any sort of winter weather at all, know the all-too-common alert that pops up when cameras are obstructed:
Even brief obstructions can drop perception confidence, trigger safety disengagements, or force the vehicle to pull over, although these are relatively rare. Instead, most of the time, the camera will need a wipe from the owner next time they stop the car.
But unlike human drivers who can manually clear their view, a Robotaxi operating 24/7 without a steering wheel or mirrors must maintain pristine vision autonomously. The Cybercab’s side repeater washer delivers targeted cleaning bursts precisely where needed for merging, lane changes, and blind-spot monitoring — functions that demand uninterrupted visibility from the external cameras:
And this is how the side camera and washer look like on a Cybercab. This is from an Engineering vehicle in Peabody MA. pic.twitter.com/Re8VknpmLM
— Tobias Goebel (Unsupervised) (@tpgoebel) June 17, 2026
This hardware directly tackles a known pain point in current FSD deployments. Owners frequently report camera-related alerts during inclement weather, which is understandable, but needs to be solved for a true autonomous experience.
For a production Robotaxi fleet aiming for high utilization and minimal downtime, robust washer systems represent a foundational reliability upgrade; essentially, they’re a must-have. Early sightings suggest the design may extend to rear cameras as well, creating a comprehensive cleaning architecture that keeps the entire vision suite operational in harsh environments.
Without it, even the most advanced neural nets struggle when their “eyes” are compromised.
What Does This Mean for AI4 Cars?
This Cybercab detail raises timely questions for AI4 cars already on the road. While Hardware 4 delivers superior compute and camera resolution compared to earlier versions, production models typically lack dedicated side and rear washers. Tesla has included them on Model Y robotaxis that it is using in the fleet:
Tesla Robotaxi has a highly-requested hardware feature not available on typical Model Ys
As Tesla refines unsupervised FSD for broader release, the gap in environmental resilience becomes evident. Software improvements can help mitigate issues, but they cannot fully replace physical cleaning in heavy rain or muddy conditions. Analysts and owners increasingly speculate that AI4 vehicles may eventually require similar washer retrofits — or a future AI4.5 variant — to match the Cybercab’s all-weather readiness and support the same level of autonomy.
As testing progresses, the Cybercab’s washer mechanism highlights Tesla’s pragmatic focus on real-world robustness. It may well become the hardware piece that determines how quickly and reliably FSD scales from prototypes to everyday vehicles.
Tesla faces Full Self-Driving pushback in EU over ‘speeding’
Tesla teases greater Grok FSD integration and ‘Banish’ feature ‘in about 3 months’
