News
SpaceX tests Starship and Frankenstein ‘test tank’ simultaneously
After another few weeks of downtime, SpaceX has simultaneously tested the first orbital-class Starship prototype and a Frankenstein-esque ‘test tank’ at its South Texas facilities. While nothing that occurred was all that visually spectacular, the afternoon of testing was still noteworthy for a couple of reasons.
First up, following a successful six-engine Raptor static fire – the first in Starbase history – on November 12th, all signs pointed to Starship S20 attempting another static fire (its fourth) on December 1st. In the almost three weeks of inactivity between those planned tests, SpaceX likely performed extensive inspections of the pathfinder prototype and its Raptor engines. Technicians also repaired the minor heat shield damage and tile loss that testing incurred and patched a few other ‘holes’, effectively leaving Ship 20 with the first fully finished heat shield by the end of November.
Earlier this week, one of the few remaining Boca Chica Village residents received a safety notice from SpaceX indicating that a static fire test was scheduled on Wednesday, December 1st – followed soon after by a notice to mariners (NOTAM) warning boaters to keep to a safe distance. Two hours into the 10am to 6pm CST test window, Starship S20 was already venting and starting to get frosty, confirming that propellant loading had begun. A little over an hour later, it was clear that SpaceX had aborted the first static fire attempt of the day. For the next three hours, Ship 20 exhibited some unusual behavior including new vents, an apparent header tank pressurization or fill test, and still more odd venting in new places.
In the middle of Starship’s weird nose-related testing, SpaceX began simultaneously loading a new ‘test tank’ known as B2.1 with liquid nitrogen (LN2) – marking the first truly simultaneous test of multiple Starship test articles. As Ship 20 seemingly detanked for the second time that day, the B2.1 tank was fully loaded with LN2 and apparently pressure-tested not long after. A few hours later, the test tank was also detanked and the road to the pad was reopened, marking the end of the day’s testing.
Normally, nothing is particularly unusual or noteworthy about test tank testing. Since January 2020, SpaceX has routinely built and tested tanks that are effectively just shorter versions of actual tanks and hardware, using them to qualify changes to Starship’s design, materials, operations, and more before applying those changes to full-size prototypes. B2.1 is the tenth dedicated test tank to reach the launch pad in a little under two years.
Normally, the ‘B2.1’ name SpaceX has given the tank would imply that it’s a newer booster test tank (using Bx instead of BNx) following in the footsteps of BN2.1, which passed cryogenic and load testing this summer. Instead, though, B2.1 is a bit of a nightmarish amalgamation of seemingly random Starship and Super Heavy parts. Its forward dome is an old, unused booster section complete with the hexagonal structure grid fins would have been brace against. Its aft section is a booster thrust structure. Up to that point, it’s effectively just a copy of BN2.1.
However, SpaceX inexplicably installed a Starship thrust dome inside B2.1’s booster thrust structure, creating a test tank with no obvious relevance to any conceivable Starship or Super Heavy design or prototype. Further, SpaceX rolled B2.1 to the launch site for testing only after installing it on an unused device that’s believed to be the aft half of a dedicated booster structural test stand. In theory, a sort of ‘cap’ would be fitted on top of a booster or test tank installed in the stand’s base and strong cables would connect the two, allowing SpaceX to subject prototypes to compressive stress – like, perhaps, the forces a booster might experience while carrying a fully-fueled 1300-ton Starship to space. The upper half of that test structure has yet to be moved to the launch site.
Altogether, the weird half-complete test stand and bizarre fusion of ship and booster parts make B2.1’s purpose and initial testing a complete mystery. It’s unclear what value it provides that makes it more of a priority than, say, finally starting to test the first flightworthy Super Heavy booster (B4). Ultimately, the most interesting thing about B2.1’s test debut is the fact that it appears to mark the first use of Starbase’s brand new orbital tank farm, which is approaching completion.
Tesla is being accused of infringing robotics patents by a company called Perrone Robotics, which is based out of Charlottesville, Virginia.
The suit was filed in Alexandria, Virginia, and accuses Tesla of knowingly infringing upon five patents related to robotics systems for self-driving vehicles.
The company said its founder, Paul Perrone, developed general-purpose robotics operating systems for individual robots and automated devices.
Perrone Robotics claims that all Tesla vehicles utilizing the company’s Autopilot suite within the last six years infringe the five patents, according to a report from Reuters.
Tesla’s new Safety Report shows Autopilot is nine times safer than humans
One patent was something the company attempted to sell to Tesla back in 2017. The five patents cover a “General Purpose Operating System for Robotics,” otherwise known as GPROS.
The GPROS suite includes extensions for autonomous vehicle controls, path planning, and sensor fusion. One key patent, U.S. 10,331,136, was explicitly offered to Tesla by Perrone back in 2017, but the company rejected it.
The suit aims to halt any further infringements and seeks unspecified damages.
This is far from the first suit Tesla has been involved in, including one from his year with Perceptive Automata LLC, which accused Tesla of infringing on AI models to interpret pedestrian/cyclist intent via cameras without licensing. Tesla appeared in court in August, but its motion to dismiss was partially denied earlier this month.
Tesla also settled a suit with Arsus LLC, which accused Autopilot’s electronic stability features of infringing on rollover prevention tech. Tesla won via an inter partes review in September.
Most of these cases involve non-practicing entities or startups asserting broad autonomous vehicle patents against Tesla’s rapid iteration.
Tesla typically counters with those inter partes reviews, claiming invalidity. Tesla has successfully defended about 70 percent of the autonomous vehicle lawsuits it has been involved in since 2020, but settlements are common to avoid discovery costs.
The case is Perrone Robotics Inc v Tesla Inc, U.S. District Court, Eastern District of Virginia, No. 25-02156. Tesla has not yet listed an attorney for the case, according to the report.
News
Tesla has passed a critical self-driving milestone Elon Musk listed in Master Plan Part Deux
Tesla China announced that the company’s Autopilot system has accumulated 10 billion kilometers of driving experience.
Tesla has passed a key milestone, and it was one that CEO Elon Musk initially mentioned more than nine years ago when he published Master Plan, Part Deux.
As per Tesla China in a post on its official Weibo account, the company’s Autopilot system has accumulated over 10 billion kilometers of real-world driving experience.
Tesla China’s subtle, but huge announcement
In its Weibo post, Tesla China announced that the company’s Autopilot system has accumulated 10 billion kilometers of driving experience. “In this respect, Tesla vehicles equipped with Autopilot technology can be considered to have the world’s most experienced and seasoned driver.”
Tesla AI’s handle on Weibo also highlighted a key advantage of the company’s self-driving system. “It will never drive under the influence of alcohol, be distracted, or be fatigued,” the team wrote. “We believe that advancements in Autopilot technology will save more lives.”
Tesla China did not clarify exactly what it meant by “Autopilot” in its Weibo post, though the company’s intense focus on FSD over the past years suggests that the term includes miles that were driven by FSD (Beta) and Full Self-Driving (Supervised). Either way, 10 billion cumulative miles of real-world data is something that few, if any, competitors could compete with.
Elon Musk’s 10-billion-km estimate, way back in 2016
When Elon Musk published Master Plan Part Deux, he outlined his vision for the company’s autonomous driving system. At the time, Autopilot was still very new, though Musk was already envisioning how the system could get regulatory approval worldwide. He estimated that worldwide regulatory approval will probably require around 10 billion miles of real-world driving data, which was an impossible-sounding amount at the time.
“Even once the software is highly refined and far better than the average human driver, there will still be a significant time gap, varying widely by jurisdiction, before true self-driving is approved by regulators. We expect that worldwide regulatory approval will require something on the order of 6 billion miles (10 billion km). Current fleet learning is happening at just over 3 million miles (5 million km) per day,” Musk wrote.
It’s quite interesting but Tesla is indeed getting regulatory approval for FSD (Supervised) at a steady pace today, at a time when 10 billion miles of data has been achieved. The system has been active in the United States and has since been rolled out to other countries such as Australia, New Zealand, China, and, more recently, South Korea. Expectations are high that Tesla could secure FSD approval in Europe sometime next year as well.
Elon Musk
SpaceX maintains unbelievable Starship target despite Booster 18 incident
It appears that it will take more than an anomaly to stop SpaceX’s march towards Starship V3’s refinement.
SpaceX recently shared an incredibly ambitious and bold update about Starship V3’s 12th test flight.
Despite the anomaly that damaged Booster 18, SpaceX maintained that it was still following its plans for the upgraded spacecraft and booster for the coming months. Needless to say, it appears that it will take more than an anomaly to stop SpaceX’s march towards Starship V3’s refinement.
Starship V3 is still on a rapid development path
SpaceX’s update was posted through the private space company’s official account on social media platform X. As per the company, “the Starbase team plans to have the next Super Heavy booster stacked in December, which puts it on pace with the test schedule planned for the first Starship V3 vehicle and associated ground systems.”
SpaceX then announced that Starship V3’s maiden flight is still expected to happen early next year. “Starship’s twelfth flight test remains targeted for the first quarter of 2026,” the company wrote in its post on X.
Elon Musk mentioned a similar timeline on X earlier this year. In the lead up to Starshp Flight 11, which proved flawless, Musk stated that “Starship V3 is a massive upgrade from the current V2 and should be through production and testing by end of year, with heavy flight activity next year.” Musk has also mentioned that Starship V3 should be good enough to use for initial Mars missions.
Booster 18 failure not slowing Starship V3’s schedule
SpaceX’s bold update came after Booster 18 experienced a major anomaly during gas system pressure testing at SpaceX’s Massey facility in Starbase, Texas. SpaceX confirmed in a post on X that no propellant was loaded, no engines were installed, and personnel were positioned at a safe distance when the booster’s lower section crumpled, resulting in no injuries.
Still, livestream footage showed significant damage around the liquid oxygen tank area of Booster 18, leading observers to speculate that the booster was a total loss. Booster 18 was among the earliest vehicles in the Starship V3 series, making the failure notable. Despite the setback, Starship V3’s development plans appear unchanged, with SpaceX pushing ahead of its Q1 2026 test flight target.
Tesla accused of infringing robotics patents in new lawsuit
Tesla has passed a critical self-driving milestone Elon Musk listed in Master Plan Part Deux
