News
Boeing Starliner abort test (mostly) a success as SpaceX nears Crew Dragon static fire
On November 4th, Boeing completed a crucial pad abort test of its reusable Starliner spacecraft, successful in spite of an unintentional partial failure of its parachute recovery system. Three days later, Boeing revealed what it believed to be the cause of that anomaly in a November 7th press conference.
Meanwhile, SpaceX – having completed Crew Dragon’s pad abort test in 2015 – is preparing for an equally important In-Flight Abort (IFA) test and is perhaps just a day or two away from static firing the Crew Dragon capsule assigned to the test flight.
According to a NASA press release after the test, it “was designed to verify [that] each of Starliner’s systems will function not only separately, but in concert, to protect astronauts by carrying them safely away from the launch pad in the unlikely event of an emergency prior to liftoff.” Although the test wasn’t without flaws, the pad abort test successfully demonstrated the ability of the four launch abort engines and control thrusters to safely extricate astronauts from a failing rocket.
Those theoretical astronauts would have almost certainly survived the ordeal unharmed despite the failed deployment of one of Starliner’s three main parachutes, testing the spacecraft’s abort capabilities and redundancy quite a bit more thoroughly than Boeing intended. To put it bluntly, Boeing’s above tweet and PR claim that the failed deployment of 1/3 parachutes is “acceptable for the test parameters and crew safety” is an aggressive spin on a partial failure that NASA undoubtedly did not sign off on.
Boeing and SpaceX have both suffered failures while testing parachutes, leading NASA to require significantly more testing. However, in a November 7th press conference, Boeing revealed that Starliner’s parachute anomaly wasn’t the result of hardware failing unexpectedly under planned circumstances, but rather a consequence of a lack of quality assurance that failed to catch a major human error. Boeing says that a critical mechanical linkage (a pin) was improperly installed by a technician and then not verified prior to launch, causing one of Starliner’s three drogue chutes to simply detach from the spacecraft instead of deploying its respective main parachute.
Space is Parachutes are hard
Parachutes have been a major area of concern for the Commercial Crew Program. Both SpaceX and Boeing have now suffered failures during testing and have since been required to perform a range of additional tests to verify that upgraded and improved parachutes are ready to reliably return NASA astronauts to Earth. Although the Starliner pad abort test did indeed demonstrate the ability to land the capsule safely under two main chutes, an inadvertent test of redundancy, the series of Boeing actions that lead to the failure will almost certainly be scrutinized by NASA to avoid reoccurrences.
Boeing believes that the parachute failure won’t delay the launch of Starliner’s Orbital Flight Test (OFT), currently targeting a launch no earlier than (NET) December 17th. However, it can be said with some certainty that it will delay Starliner’s crewed launch debut (CFT), at least until Boeing can prove to NASA that it has corrected the fault(s) that allowed it to happen. SpaceX is similarly working to qualify upgraded Crew Dragon parachutes for astronaut launches, although the company has thus far only suffered anomalies related to the structural failure of parachute rigging/seams/fabric.
Abort tests galore
Boeing’s Starliner pad abort test occurred just days prior to a different major abort test milestone – this time for SpaceX. SpaceX Crew Dragon capsule C205 will perform a static fire test of its upgraded SuperDraco abort system, as well as its Draco maneuvering thrusters.
SpaceX has made alterations to the SuperDraco engines to prevent a failure mode that abruptly reared its head in April 2019, when a leaky valve and faulty design resulted in a catastrophic explosion milliseconds before a SuperDraco static fire test. Prior to its near-total destruction, Crew Dragon capsule C201 was assigned to SpaceX’s In-Flight Abort test, and its loss (and the subsequent failure investigation) delayed the test’s launch by at least six months. Crew Dragon’s design has since been fixed by replacing reusable check valves with single-use burst discs, nominally preventing propellant or oxidizer leaks.
If capsule C205’s static fire testing – scheduled no earlier than November 9th – goes as planned, SpaceX may be able to launch Crew Dragon’s in-flight abort (IFA) test before the end of 2019e. Likely to be a bit of a spectacle, Crew Dragon will launch atop a flight-proven Falcon 9 booster and a second stage with a mass simulator in place of its Merlin Vacuum engine, both of which will almost certainly be destroyed when Dragon departs the rocket during peak aerodynamic pressure.
NASA made in-flight abort tests an optional step for its Commercial Crew providers and Boeing decided to perform a pad abort only and rely on modeling and simulations to verify that Starliner’s in-flight abort safety. Assuming that NASA is happy with the results of Starliner’s pad abort and Boeing can alleviate concerns about the parachute anomaly suffered during the test, Starliner’s uncrewed orbital flight test (OFT) could launch as early as December 17th. Starliner’s crewed flight test (CFT) could occur some 3-6 months after that if all goes as planned during the OFT.
If SpaceX’s In-Flight Abort (IFA) also goes as planned and NASA is content with the results, Crew Dragon could be ready for its crewed launch debut (Demo-2) as early as February or March 2020.
Check out Teslarati’s newsletters for prompt updates, on-the-ground perspectives, and unique glimpses of SpaceX’s rocket launch and recovery processes.
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.
Tesla Giga Berlin plant manager faces defamation probe after IG Metall union complaint
Tesla wins FCC approval for wireless Cybercab charging system
