News
SpaceX Starship wraps up nosecone ‘cryo proof’ and first of several Raptor static fires
SpaceX has successfully ‘cryoproofed’ the first fully-assembled Starship prototype’s nose-based propellant tank and used that same tank to fire up a Raptor engine, crossing off one of the last major tests before the rocket’s 15-kilometer (~9.5 mile) launch debut.
On November 4th, after a few false-starts, Starship Serial Number 8 (SN8) kicked off its first round of testing after becoming the first prototype to have a nose section permanently installed. On that Wednesday evening, SpaceX most likely put the rocket through a partial cryogenic proof test explicitly focused on SN8’s new nosecone and a small secondary propellant tank situated in its tip. Designed to act as a secondary reservoir for the relatively small amount of propellant Starships need to land, SN8’s two header tanks were likely loaded with cryogenic liquid nitrogen – a safe, nonreactive stand-in for liquid oxygen and methane.
Having proven that Starship SN8’s newly-installed liquid oxygen header tank and associated plumbing is capable of loading, managing, and offloading dozens of tons of cryogenic fluid while navigating a 40-meter-tall (~130 ft) vertical pipe, SpaceX was ready to move onto the next step: a wet dress rehearsal (WDR) and Raptor static fire.
While SpaceX has technically completed eight successful Raptor static fires on four separate prototypes, including the first three-Raptor static fire ever attempted with Starship SN8, the company has never attempted a static fire while solely drawing propellant from header (landing) tanks. All but essential for Starships to be able to reliably reignite their Raptor engines in flight and keep cryogenic landing propellant liquid for hours, days, weeks, and even months, much smaller header tanks make it easier to keep propellant highly pressurized and in the right place to supply Raptors.
After several days of test windows come and gone and an aborted attempt on November 9th, Starship SN8 finally ignited one of its three Raptor engines, feeding the engine with liquid methane and oxygen stored in two separate header tanks. Oddly, a second or two after startup and ignition, Raptor’s usual exhaust plume was joined by a burst of shiny firework-like debris. A relatively normal five seconds later, the Raptor cut off, though the engine appeared to remain partially on fire for another ten or so seconds – also somewhat unusual.
Ultimately, the observed anomaly could be as simple as debris accidentally left in the vicinity of Raptor’s plume or, while less likely, concrete erosion. There’s also a chance that it was pieces of Raptor’s complex turbopumps or preburners, although it’s also unlikely that the engine would have continued running (as it did) if it had lost that much internal hardware.
(Update: Thankfully, NASASpaceflight.com reporter Michael Baylor says that the cloud of debris observed on November 10th “is not a [Raptor performance] concern,” making pad debris the likely source.)
SpaceX has canceled another static fire window on November 11th, leaving the next opportunity for a second (of three) expected static fire between 9am and 9pm CST (UTC-5) on Thursday, November 13th.
News
Tesla Giga Berlin plant manager faces defamation probe after IG Metall union complaint
Prosecutors in Frankfurt (Oder) confirmed they have opened a defamation probe into Gigafactory Berlin plant manager André Thierig.
Tesla’s Giga Berlin plant manager is now under investigation after a complaint from trade union IG Metall, escalating tensions ahead of next month’s works council elections.
Prosecutors in Frankfurt (Oder) confirmed they have opened a defamation probe into Gigafactory Berlin plant manager André Thierig, as per a report from rbb24.
A spokesperson for the Frankfurt (Oder) public prosecutor’s office confirmed to the German Press Agency that an investigation for defamation has been initiated following a criminal complaint filed by IG Metall against Thierig.
The dispute stems from Tesla’s allegation that an IG Metall representative secretly recorded a works council meeting using a laptop. In a post on X, Thierig described the incident as “truly beyond words,” stating that police were called and a criminal complaint was filed.
“What has happened today at Giga Berlin is truly beyond words! An external union representative from IG Metall attended a works council meeting. For unknown reasons, he recorded the internal meeting and was caught in action! We obviously called police and filed a criminal complaint!” Thierig wrote in a post on X.
Police later confirmed that officers did seize a computer belonging to an IG Metall member at Giga Berlin. Prosecutors are separately investigating the union representative on suspicion of breach of confidentiality and violation of Germany’s Works Constitution Act.
IG Metall has denied Tesla’s allegations. The union claimed that its member offered to unlock the laptop for review in order to accelerate the investigation and counter what it called false accusations. The union has also sought a labor court injunction to “prohibit Thierig from further disseminating false claims.”
The clash comes as Tesla employees prepare to vote in works council elections scheduled for March 2–4, 2026. Approximately 11,000 Giga Berlin workers are eligible to participate in the elections.
News
Tesla wins FCC approval for wireless Cybercab charging system
The decision grants Tesla a waiver that allows the Cybercab’s wireless charging system to be installed on fixed outdoor equipment.
Tesla has received approval from the Federal Communications Commission (FCC) to use Ultra-Wideband (UWB) radio technology in its wireless EV charging system.
The decision grants Tesla a waiver that allows the Cybercab’s wireless charging system to be installed on fixed outdoor equipment. This effectively clears a regulatory hurdle for the company’s planned wireless charging pad for the autonomous two-seater.
Tesla’s wireless charging system is described as follows in the document: “The Tesla positioning system is an impulse UWB radio system that enables peer-to-peer communications between a UWB transceiver installed on an electric vehicle (EV) and a second UWB transceiver installed on a ground-level pad, which could be located outdoors, to achieve optimal positioning for the EV to charge wirelessly.”
The company explained that Bluetooth is first used to locate the charging pad. “Prior to the UWB operation, the vehicular system uses Bluetooth technology for the vehicle to discover the location of the ground pad and engage in data exchange activities (which is not subject to the waiver).”
Once the vehicle approaches the pad, the UWB system briefly activates. “When the vehicle approaches the ground pad, the UWB transceivers will operate to track the position of the vehicle to determine when the optimal position has been achieved over the pad before enabling wireless power charging.”
Tesla also emphasized that “the UWB signals occur only briefly when the vehicle approaches the ground pad; and mostly at ground level between the vehicle and the pad,” and that the signals are “significantly attenuated by the body of the vehicle positioned over the pad.”
As noted by Tesla watcher Sawyer Merritt, the FCC ultimately granted Tesla’s proposal since the Cybercab’s wireless charging system’s signal is very low power, it only turns on briefly while parking, it works only at very short range, and it won’t interfere with other systems.
While the approval clears the way for Tesla’s wireless charging plans, the Cybercab does not appear to depend solely on the new system.
Cybercab prototypes have frequently been spotted charging at standard Tesla Superchargers across the United States. This suggests the vehicle can easily operate within Tesla’s existing charging network even as the wireless system is developed and deployed. With this in mind, it would not be surprising if the first batches of the Cybercab that are deployed and delivered to consumers end up being charged by regular Superchargers.
Elon Musk
Tesla posts updated FSD safety stats as owners surpass 8 billion miles
Tesla shared the milestone as adoption of the system accelerates across several markets.
Tesla has posted updated safety stats for Full Self-Driving Supervised. The results were shared by the electric vehicle maker as FSD Supervised users passed more than 8 billion cumulative miles.
Tesla shared the milestone in a post on its official X account.
“Tesla owners have now driven >8 billion miles on FSD Supervised,” the company wrote in its post on X. Tesla also included a graphic showing FSD Supervised’s miles driven before a collision, which far exceeds that of the United States average.
The growth curve of FSD Supervised’s cumulative miles over the past five years has been notable. As noted in data shared by Tesla watcher Sawyer Merritt, annual FSD (Supervised) miles have increased from roughly 6 million in 2021 to 80 million in 2022, 670 million in 2023, 2.25 billion in 2024, and 4.25 billion in 2025. In just the first 50 days of 2026, Tesla owners logged another 1 billion miles.
At the current pace, the fleet is trending towards hitting about 10 billion FSD Supervised miles this year. The increase has been driven by Tesla’s growing vehicle fleet, periodic free trials, and expanding Robotaxi operations, among others.
Tesla also recently updated the safety data for FSD Supervised on its website, covering North America across all road types over the latest 12-month period.
As per Tesla’s figures, vehicles operating with FSD Supervised engaged recorded one major collision every 5,300,676 miles. In comparison, Teslas driven manually with Active Safety systems recorded one major collision every 2,175,763 miles, while Teslas driven manually without Active Safety recorded one major collision every 855,132 miles. The U.S. average during the same period was one major collision every 660,164 miles.
During the measured period, Tesla reported 830 total major collisions with FSD (Supervised) engaged, compared to 16,131 collisions for Teslas driven manually with Active Safety and 250 collisions for Teslas driven manually without Active Safety. Total miles logged exceeded 4.39 billion miles for FSD (Supervised) during the same timeframe.