News
SpaceX’s next Falcon Heavy launch may feature record-breaking center core landing
Thanks to a temporary reopening of the US federal government, SpaceX was finally able to continue the process of filing FCC and FAA paperwork needed to acquire permits for upcoming launches, including Falcon Heavy.
One such filing related to the first operational Falcon Heavy launch has revealed a fairly impressive statistic: comprised of three first stage boosters, SpaceX indicated that Falcon Heavy’s center core will attempt to land on drone ship Of Course I Still Love You (OCISLY) nearly 1000 km (600 mi) away from its launch site, easily smashing the record for the greatest distance traveled by a Falcon booster in flight.
Of Course I Still Love You will be positioned a record ~965km downrange. That's nearly 300km further that the previous greatest distance of 681km, set during the Eutelsat-117WB mission in June 2016. (The landing was a failure, with the booster running out of LOX!) https://t.co/RECKjMtd37
— Gav Cornwell (@SpaceOffshore) January 28, 2019
The same FCC filings also revealed a No Earlier Than (NET) launch date: March 7, 2019. Originally targeted for mid to late February, the complexity and logistical challenges of building, shipping, testing, and delivering two side boosters, a center core, one upper stage, and a payload fairing from SpaceX’s California factory to its Texas test facilities and Florida launch pad unsurprisingly took a small toll on the launch’s aspirational schedule. Nevertheless, if the launch data actually holds to March 7th, SpaceX will not have missed the mark by much considering that this Falcon Heavy – based on new and more powerful Block 5 boosters – is likely a significant departure from the Block 2/Block 3 hardware that has flight heritage from the triple-booster rocket’s Feb. 2018 launch debut.
Just shy of a year after Falcon Heavy’s launch debut, it appears that the rocket’s second and third launches were pushed back by a fundamental lack of production capacity. In other words, SpaceX’s Hawthorne rocket factory simply had to focus on more critical priorities in the 6-9 months that followed the demo mission. At nearly the same time as Falcon Heavy was lifting off for the first time, SpaceX’s world-class production crew was in the midst of manufacturing the first upgraded Falcon 9 Block 5 booster (B1046) and wrapped up final checkouts just 10 days after Heavy’s Feb. 6 launch debut, sending the pathfinder rocket to McGregor, Texas for the first static fire of a Block 5 booster.
In the meantime, SpaceX’s decision to intentionally expend otherwise recoverable reused Falcon boosters after their second launches meant that the company’s fleet of flightworthy rockets was rapidly approaching zero, a move CEO Elon Musk specifically indicated was meant to make room for Block 5, the future (and final form) of the Falcon family. SpaceX’s busy 2018 launch manifest and multiple critical missions for the US government were thus balanced on the success, reliability, and rapid production of a serious number of Merlin engines, boosters, and upper stages. This included B1051 – the first explicitly crew-rated Falcon 9 – and B1054, the first SpaceX rocket rated to launch high-value US military (specifically Air Force) satellites. However, SpaceX also needed to produce a cadre of Falcon 9 boosters capable of easy reuse to support the dozen or so other commercial launches on the manifest.
-
- Falcon 9 B1046 is processed in Port of LA shortly after its third successful launch and landing, December 2018. (Pauline Acalin)
-
- Falcon 9 B1047 is pictured here beneath an upper stage and satellite Es’hail-2 prior to its second launch. (Tom Cross)
-
- Falcon 9 B1048 returned to Port of Los Angeles aboard drone ship Just Read The Instructions after its first launch. July 27. (Pauline Acalin)
-
- Falcon 9 B1049 returned to Port of Los Angeles after its second successful launch and landing in four months. (Pauline Acalin)
-
- Falcon 9 B1050 is seen here just after liftoff. GPS III SV01’s Falcon 9 will feature no grid fins or landing legs. ☹ (Tom Cross)
-
- Falcon 9 B1051 and Crew Dragon vertical at Pad 39A. (SpaceX)
That gamble ultimately paid off, with Block 5 performing admirably and supporting a reasonable – if not record-breaking – rate of reuse. SpaceX successfully launched B1054 for the USAF, completed B1051 (now at Pad 39A awaiting NASA’s go-ahead), and built enough reusable Block 5 boosters to support nine additional commercial missions in 2018. In hindsight, barring an assumption of a truly miraculous and unprecedented Falcon booster production rate, Falcon Heavy’s next launches were almost guaranteed to occur no fewer than 6-12 months after the rocket’s launch debut – SpaceX’s entire launch business depended on building 5+ unrelated Falcon 9 boosters, while Falcon Heavy customers Arabsat and the USAF were unlikely to be swayed to launch on flight-proven hardware so early into Block 5’s career.
https://twitter.com/_TomCross_/status/1048483536917823488
All cylinders firing
Once Falcon 9 B1054 departed SpaceX’s Hawthorne factory (see above) in early October, it appears that the company’s production team pivoted directly to integrating and shipping the next three (or more) Falcon Heavy boosters back to back for the rocket’s second and third launches. The first new side booster departed the factory in mid-November, followed by a second side booster in early December and a (presumed but highly likely) center core at the turn of 2019. Both side boosters have been static-fired in Texas and are now at SpaceX’s Florida facilities, while the center core either just completed its Texas static fire testing or is already on its way East.
-
- SpaceX’s Falcon Heavy Block 5 side booster is pictured here in Texas in November 2018. (Teslarati/Aero Photo)
-
- The second (and third) flight of Falcon Heavy is even closer to reality as a new side booster heads to Florida after finishing static fire tests in Texas. (Reddit /u/e32revelry)
-
- SpaceX Facebook group member Joshua Murrah captured the second Falcon Heavy side booster to arrive in Florida in the last month. (Joshua Murrah, 01/17/19)
-
- The next Falcon Heavy’s first side booster delivery was caught by several onlookers around December 21. (Instagram)
-
- A booster – likely the next Falcon Heavy center core – was vertical at McGregor’s S1 static fire stand. (Instagram /u/tcryguy)
-
- A booster – either Falcon Heavy’s next center core or a new Falcon 9 – was vertical at SpaceX’s McGregor, TX test facilities on Jan 28. (Instagram /u/n75sd)
-
- A diagram from a recent SpaceX document offers an idea of what Falcon Heavy Block 5 will look like. (SpaceX)
Once the center core and upper stage make their way to SpaceX’s Kennedy Space Center Pad 39A, the company’s technicians and engineers will be able to integrate the second Falcon Heavy to have ever existed in preparation for a critical static fire test. That could occur as early as February, although the launch debut of Crew Dragon (DM-1) – now NET March from Pad 39A after a relentless string of slips – will likely take precedence over Falcon Heavy and could thus directly interfere with its launch, as the launch pad and transporter/erector (T/E) has to undergo at least a few days of modifications to switch between Falcon 9 and Heavy.
Regardless, the next two Falcon Heavy launches will be well worth the wait. SpaceX’s FCC filings indicate that the center core may travel nearly 1000 km (600 mi) East of Pad 39A to land on drone ship OCISLY after launch, smashing the previous record attempt – during the June 2016 launch of Eutelsat 117WB – of ~700 km (430 mi). That Falcon 9 booster – albeit a less-powerful Block 2 variant – was unsuccessful in its landing attempt, running out of oxidizer seconds before landing. Falcon Heavy’s debut center core also happened to suffer a wholly different but no less fatal anomaly during landing, causing it to miss the drone ship and slam into the Atlantic Ocean at almost half the speed of sound (300 mph/480 km/h).
Looks like early liquid oxygen depletion caused engine shutdown just above the deck pic.twitter.com/Sa6uCkpknY
— Elon Musk (@elonmusk) June 17, 2016
Known for their rocket performance estimates, NASASpaceflight forum user “Orbiter” first pointed out the impressive distance – gathered by mapping coordinates included in SpaceX’s Jan. 28th FCC filing – and estimated that the Falcon Heavy center booster flying a trajectory as implied could be traveling as fast as ~3.5 km/s (2.2 mi/s) at main engine cut-off (MECO), the point at which the booster separates from the upper stage and fairing. This would be a nearly unprecedented velocity for any Falcon booster, let alone a booster with plans to land after launch. Falcon 9 MECO typically occurs at velocities between 1.5 and 2.5 km/s for recoverable missions, while even the recent expendable GPS III launch saw F9 S1’s engines cut off around 2.7 km/s.
Whether that MECO velocity estimate is correct, Falcon Heavy’s NET March launch of the ~6000 kg (13,300 lb) Arabsat 6A satellite is likely to be an exceptionally hot reentry and recovery for the center core, while the rocket’s duo of side boosters will attempt a repeat of the debut mission’s spectacular double-landing at LZ-1.
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’
