News
SpaceX recaps historic Starship landing in 4K as next ship readies for flight
SpaceX has published a new 4K video recapping Starship’s first intact landing after a high-altitude launch right as the company is preparing the next ship for flight.
On March 3rd, Starship serial number 10 (SN10) briefly became the first prototype to successfully launch to 10 km (6.2 mi), ‘skydive’ back to Earth, flip around, and land in one piece. Put simply, Starship SN10 made it unequivocally clear that the exotic, unproven method of landing selected by SpaceX could be made to work. Unfortunately, while Starship SN10 did land in one piece, the landing was much harder than planned.
Due to some combination of that hard landing and an apparent onboard fire that started in the last ~20 seconds of flight, SpaceX only had around six minutes to contemplate its success before Starship SN10’s propellant tanks were breached, violently depressurizing the rocket and causing a large explosion and fire.
Previously discussed on Teslarati, SpaceX CEO Elon Musk later took to Twitter to offer some educated guesses as to why Starship SN10 exploded.
“Starship SN9 ultimately failed a few seconds earlier than Starship SN8 when one of its Raptor engines failed to ignite, precluding a true flight test of the helium pressurization fix. As it turns out, Musk believes that that very fix may have doomed Starship SN10.
As Starship SN10 forged ahead past the points of failure that killed SN8 and SN9, the SpaceX CEO thinks that one or more of the vehicle’s three Raptor engines began to ingest some of that helium as they drained the methane header tank. As a result, engine thrust fell below expected values, preventing Starship SN10 from fully slowing down for a soft landing. Instead, the Starship hit the ground traveling a solid 25 mph (~10 m/s), obliterating its tiny landing legs and damaging its skirt section.”
Teslarati.com – March 10th, 2021
In other words, the losses of Starships SN8, SN9, and SN10 all share a relatively common point of failure – propulsion reliability. Technically, only Starship SN9’s failure can be blamed specifically on Raptor, one of which failed to ignite during its flip and landing maneuver. SN8 and SN10 both failed because of issues in the complex network of plumbing and pressurization systems responsible for feeding Raptors the right amount of propellant.
For SN8, the ship’s pressurization system failed to provide the necessary fuel head pressure at the last second, starving the Starship’s Raptors. SN10 ironically failed because the quick fix inspired by SN8’s failure – partially replacing a methane pressurant with helium – likely contaminated its methane fuel with helium, effectively watering down Raptor’s performance. While likely frustrating for SpaceX, the failures are still extremely valuable and loss of hardware remains a routine and intentional part of the company’s approach to iterative rocket development.
On the plus side, the FAA has already cleared SpaceX’s next Starship for flight after SN10’s momentary success and subsequent explosion. Spurred by that brief taste of total success, SpaceX wasted no time to prepare that next prototype – Starship SN11 – for flight and rolled the rocket to the launch pad mere days after SN10’s March 3rd flight. That very same day, SpaceX completed ambient pressure testing – a basic verification that Starship SN11 is leak-free.
A few days later, SN11 appeared to pass its first cryogenic proof test, replacing room-temperature gas with cryogenic liquid nitrogen. Three days after that, SpaceX attempted to put the Starship through its first triple-Raptor static fire test but appeared to suffer an abort milliseconds after a partial ignition of one or two of its three engines. Starship SN11 briefly caught fire and burned for at least 20-40 seconds after the abort, unsurprisingly triggering several days of delays. Nevertheless, if SN11 can make it through a second static fire attempt without issue on Thursday or Friday, the Starship is still well on track to take flight weeks earlier than any of its predecessors.
News
Tesla Cybercab fleet grows in Austin ahead of launch event
Tesla is bolstering its Cybercab fleet with the State of Texas’s regulatory bodies ahead of the planned launch of the all-electric ride-hailing vehicle this Thursday.
Seven purpose-built Tesla Cybercabs have been added to Texas’s official automated vehicle registry, appearing in the Texas Motor Carrier Credentialing System (TxMCCS) public lookup just three days before Tesla’s invite-only Cybercab launch event in Austin on September 3.
The records, visible through TxDMV’s Motor Carrier and Automated Motor Vehicle Operator Lookup, list seven 2026 Tesla Cybercabs under Tesla Robotaxi, LLC. Their VINs begin with the 5YJA prefix, distinct from the 7SAYG Model Y robotaxis that already dominate Tesla’s Texas fleet.
Community trackers that scrape the same public database recorded the new entries on August 31, bringing Tesla’s authorized Texas robotaxi total to 276 vehicles: 269 Model Ys and the seven Cybercabs:
🚨 There are now SEVEN Tesla Cybercabs registered with the state of Texas
We are just three days from Cybercab! pic.twitter.com/ndwhuFYsep
— TESLARATI (@Teslarati) August 31, 2026
Texas Senate Bill 2807, which took effect in late May 2026, created a self-certification framework for commercial Level 4 operations. Operators file through TxMCCS, attest to SAE Level 4 capability, maintain insurance, and keep an active vehicle list.
Tesla completed that process months earlier for its existing Model Y Robotaxi service, which has carried paying passengers in Austin, Dallas, Houston and other markets. Adding the Cybercabs to the same authorization means the new two-seat, steering-wheel-free vehicles are now legally recognized for commercial use on Texas roads.
The timing is deliberate as Tesla scheduled the September 3 event at its Austin campus after sending invitations to selected Robotaxi riders and other guests. The company has described the evening as a chance to “experience the future of full autonomy” and plans to livestream it.
Production Cybercabs, which lack pedals and a steering wheel, have been rolling off the Giga Texas line for months; some earlier examples still carried temporary driver controls for data collection. Registering a small fleet of the finished design immediately before the public event signals that Tesla intends to move the purpose-built vehicle from factory and test tracks into the same Robotaxi app already used by Model Y passengers.
The seven units remain a tiny fraction of Tesla’s overall Texas authorization and far smaller than competing fleets. Registration does not automatically equal unsupervised public rides; it is the legal prerequisite.
Still, the sudden appearance of Cybercab VINs in the state’s lookup system, after a year of Model Y-only listings, is the clearest official confirmation yet that Tesla’s dedicated robotaxi hardware is entering the regulatory pipeline at the same moment the company is preparing to show it to invited guests and a global livestream audience.
Whether those seven vehicles appear at the September 3 event or begin carrying passengers shortly afterward, their presence in TxMCCS marks a concrete regulatory step that has been anticipated since the Cybercab concept was first revealed.
News
Tesla expands driverless Robotaxi geofence in Austin
Tesla has expanded the operational geofence for its driverless Robotaxi service in Austin, Texas, marking the first such increase in some time. The updated Service Area for Robotaxi in Austin now spans about 288 square miles and is roughly 9 percent larger than the previous boundary.
This incremental growth adds approximately 24 square miles of coverage, bringing the prior zone of roughly 264 square miles into a broader footprint that better serves northern suburbs.
The expansion extends the geofence northward toward Pflugerville along the US 183 corridor, incorporating additional neighborhoods north of the Domain and areas such as Mesa Park. These additions include higher-end residential and commercial districts that previously sat just outside the allowed operating zone.
Riders can now request unsupervised trips that begin or end in these newly included locations, provided the entire route remains inside the digital boundary:
Tesla has just expanded its Robotaxi service area in Austin, Texas for the first time in 10 months.
The new service area is roughly 9% larger than the old one, and is about 288 square miles in total. pic.twitter.com/i4oBM1KfWS
— Sawyer Merritt (@SawyerMerritt) August 31, 2026
Tesla first launched public Robotaxi operations in Austin in mid-2025 with a modest initial zone of about 20 square miles. Subsequent enlargements in 2025 and early 2026 steadily grew the map until it covered much of the metropolitan area.
After the last major update roughly ten months earlier, the company held the boundary steady while it collected additional miles and refined the FSD suite.
The modest nine percent increase still matters for daily utility. Longer trips become possible, more residents gain access, and the fleet can accumulate more diverse real-world data across new road types and traffic patterns. Observers note that the added territory aligns with existing Tesla service infrastructure, which could support more efficient vehicle staging in the North end of Austin.
Although the geofence has grown, Tesla continues to operate a relatively small unsupervised fleet in the city. The company has emphasized safety and software readiness over rapid geographic scaling. This latest map update signals that Tesla remains committed to expanding Robotaxi availability in its home market as it prepares for further software improvements and potential Cybercab deployments.
The 288-square-mile zone now gives Austin riders one of the larger driverless service areas currently available in the United States.
Elon Musk
Elon Musk’s Grok can basically control anything in your Tesla now
Tesla’s 2026 Summer Update turns Grok from a talking companion into a true in-car controller, with considerably expanded capabilities. Where the assistant once answered questions and handled navigation, it can now operate hardware and software through ordinary speech, including several requests at the same time.
Grok has become incredibly robust over the past few quarters, and this new ability that Tesla has included with its Summer Update is perhaps the clearest sign of just how capable it has become.
You can issue many commands to Grok at once, and each will be taken care of: anything from headlight control to climate adjustments to mirror folding can now all be taken care of with a simple sentence spoken toward Grok:
This is cool, you can now give Grok a ton of commands at once in your Tesla and it’ll do them all together.
The commands I gave:
• Fold mirrors
• Turn on wipers to fastest setting
• Change temp to 65°
• Open self-driving app
• Open gloveboxComes with Tesla’s 2026 Summer… pic.twitter.com/drZxoHrknv
— Sawyer Merritt (@SawyerMerritt) August 26, 2026
Here’s another example I used in my Model Y:
🚨 Using Grok to control the cabin temperature and turn on headlights in 2026 Model Y on FSD v14.3.8 and 2026.26.6.5 pic.twitter.com/7clgQkGABk
— TESLARATI (@Teslarati) August 27, 2026
Tesla’s official Release Notes list the core powers of Grok’s new capabilities: Grok can place phone calls from a paired phone, search a streaming service and queue music, adjust climate, and search the Controls panel. Drivers can also ask it questions about the vehicle or the latest features included in a recent software update.
It can also take care of driving settings, dynamics, and other relevant preferences that deal with how the car operates and handles.
Tesla Summer Update begins rolling out: a look at the new features
It’s also more of a use case than a novelty feature. Grok was great for learning about something that was being pondered while Full Self-Driving was taking care of the major automotive responsibilities, but it did have some useful functionality when it came to navigation.
Another less-noted improvement is the swift transition that Grok has from thinking of its answer to giving you one. In the past, it would take a few seconds for Grok to truly come up with a valuable response. It now seems that it is improving, at least slightly.