News
SpaceX may perfect reusable rockets in 2018: Evolution in the Falcons’ Nest
2017 has in almost every respect been an unrivaled halcyon year for SpaceX: over the course of its twelves months, SpaceX has returned to flight, begun reusing Falcon 9 boosters, and overall completed 18/18 successful launches and 15/15 first stage recoveries – five of which were commercial reuses of ‘flight-proven’ boosters. It is difficult to fathom how the year could have been more successful, aside from a slight hiccup with fairing manufacturing that may have prevented the launch company from racking up 20 or more missions in 2017.
And yet, despite the flooring and incontrovertible triumphs, I can state with confidence that, barring any serious anomalies, SpaceX’s 2018 docket will utterly eclipse 2017’s varied achievements. This series of articles will act as a sort of preview of SpaceX’s imminent future in 2018, each looking at what the new year may hold for the company’s three most fundamental pursuits: the Falcon rocket family, the Starlink satellite internet initiative, and its ambitions of interplanetary colonization.
Sooty Falcon 9 1035 before its second flight with an also-reused Dragon payload, CRS-13. (Tom Cross/Teslarati)
Falcon finds its wings
While 2015 and 2016 both saw their own hints of potential successes to come, 2017 is the first year that SpaceX managed a truly impressive launch cadence for Falcon 9 without a serious vehicle failure. Every 2017 launch flew on either a Block 3 or Block 4 iteration of Falcon 9 1.2. Esoteric model numbers aside, this simply means that Falcon 9’s design, manufacture, and operation are all maturing rapidly; SpaceX has clearly learned from the CRS-7 and Amos-6 failures and responded accordingly with a more cautious and tempered perspective.
From a historical perspective, it is extraordinarily impressive that Falcon 9 and Cargo Dragon have experienced such a tiny number of failures over their short but active existences. Both Falcon 9 and Dragon have experienced several miscellaneous teething issues and technical difficulties over their ~7 years of launches, but only three anomalies resulted in failures that catastrophically impacted customer payloads: CRS-1, CRS-7, and Amos-6. Thus, out of a total of 46 Falcon 9 launches, approximately 94% have been complete successes. For perspective SpaceX’s first orbital rocket, Falcon 1, experienced total failures during its first three launch attempts, for a success rate of 40%.
SpaceX’s Falcon family of rockets. (Wikipedia)
Barring further flight hardware anomalies in the Falcon family, however, 2018 is likely to be even more of a boon for Falcon 9 (and Falcon Heavy). While Falcon Heavy is set to ring in the new year sometime in January 2018, just a few weeks away, far more significant for SpaceX’s launch business is the debut of the “final” iteration of Falcon 9, dubbed Block 5 or ‘V5,’ likely within the next several months. Block 5 has been heavily modified almost entirely for the sake of more efficient reuse, and will feature titanium grid fins (most recently spotted on Falcon Heavy) and several other changes. Altogether, SpaceX’s public goal is to be able to reuse Falcon 9 Block 5 as many as a dozen times with relative ease, and each booster’s lifespan could potentially be lengthened by a factor of 5-10 with more extensive periodic maintenance.
For now, we only use those on super hot reentry missions. Will go to all Ti with Falcon 9 V5, which is a few months away.
— Elon Musk (@elonmusk) December 17, 2017
This ‘final’ version of Falcon 9 will almost undoubtedly go through its own period of tweaks, changes, and iterative improvements once it debuts and begins to gather flight experience. Nevertheless, it’s plausible that once its minor problems are ironed out, SpaceX will choose to “freeze” the design and begin to aggressively transfer large sections of its engineering and manufacturing base over to the company’s Mars rocket, BFR. Ultimately, the highly reusable Block 5 evolution of Falcon 9 will allow SpaceX to transfer over its customers to reused rockets and thus recoup the cost of reusability R&D far faster than ever before, both by lowering the material cost of launch and enabling a considerably higher frequency of launches.
This crop of Falcon Heavy shows off its side cores, both sporting titanium grid fins that are considerably larger than the original aluminum fins. (SpaceX)
Taken as a whole, the culmination of the Falcon family’s evolution will pave SpaceX’s path to realizing its even wilder ambitions of providing ubiquitous and superior satellite internet and transforming itself into the backbone of crew and cargo transport to the Moon, Mars, and beyond. But that’s a story for another day…
While we wish we could jump forward to the end of 2018 and reflect upon even more incredible SpaceX achievements, you can follow SpaceX’s day by day progress live with our launch photographer Tom Cross on Twitter and Instagram @Teslarati. Significant upcoming events include the ever-secretive launch of Zuma (7:57pm EST, January 4) and the inaugural static fire and launch of the titanic Falcon Heavy (no earlier than Jan. 6 and Jan. 15).
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’
