News
Tesla factory worker sues company over alleged race and sexual harassment
A new lawsuit filed by a former Tesla employee alleges that the company did not take action after what they claim was overwhelming evidence of a hostile workplace at the company’s Fremont, California factory.
Dewitt Lambert is being represented by the California Civil Rights Law Group who filed the suit this week which details charges including Race Harassment, Race Discrimination, Sexual Harassment, Retaliation, Failure to Prevent Harassment, Discrimination and Retaliation, Threats of Violence in Violation of the Ralph Act, Violation of the Bane Act, Failure to Accommodate, Failure to Engage in the Interactive Process, and Assault and Battery.
The suit and accompanying cellphone video which was taken in 2015, during the timeframe of the alleged harassment, show a tirade of racial slurs and strong language taking place inside a partially assembled Tesla Model S in the Fremont factory.
“The complaint alleges that Tesla failed, under California law, to take immediate and appropriate corrective action on Mr. Lambert’s behalf,” said Organ. “Because of this inaction my client is claiming psychological harm and medical problems. Tesla is liable for Mr. Lambert’s damages because it failed to adequately investigate and prevent damaging abuse from taking place in the workplace.”
The California Civil Rights Law Group sent Teslarati the video above and accompanying press release that includes a 10-month of the alleged discrimination, complaints and promotions of offending employees. It is not clear if the promotions are related to the allegations but it could certainly be seen as a motivating factor for the suit. It seems to indicate that Lambert was not able to get promoted while being subjected to the alleged workplace abuse while his supervisors were rewarded in light of the behavior.
A representative from Tesla provides Teslarati with the following statement in response to Lambert’s suit.
We believe strongly in having a good working environment and that people should look forward to coming to work every day. That means Tesla must always aspire to be transparent, respectful, fair and just. When we hear complaints or concerns raised by our employees, we take them very seriously.
A video recently came to light showing behavior by a group of employees at our factory acting in a way that we found disappointing and contrary to our values. It appears that a lawsuit is now being filed against Tesla in connection with this video. In the interest of transparency, we want to share what we know:
- Based on interviews we have done, in April 2016, an employee named Dewitt Lambert got into an argument with a coworker and threatened him with violence. Dewitt, this coworker, and other employees had been part of a group of friends who worked together at the factory and also socialized together outside of work. The other employee filmed Dewitt making the threat and Dewitt mistakenly believed that some of these other employees had provided the video to HR in order to get him in trouble. (In actuality, the video wasn’t provided to HR).
- Later that day, in an apparent attempt to turn the tables on the complaint that he thought had been made against him, Dewitt filed a complaint with HR about these other employees, claiming it was they who had mistreated him, including by using racially insensitive language.
- HR personnel investigated, interviewing all of the employees who were reportedly involved. That investigation turned up conflicting accounts of what happened, with other employees saying that Dewitt had the “dirtiest mouth” they had “ever heard,” including using the same racially insensitive language that he had complained about. In the end, there was no objective evidence that anything inappropriate occurred toward Dewitt. As a result, our HR team coached this group of employees on the importance of behaving professionally and the investigation was closed.
- Dewitt thereafter was transferred to another work area where he would have no further contact with those he complained about. There are no records of him complaining about new events for about a year after this. It seems that the transfer had its intended effect.
- On July 6, 2016, during an unrelated conversation with HR in which Dewitt was receiving a final written warning for posting proprietary photos of Tesla equipment on social media against company policy, Dewitt showed HR an old video (taken in late 2015) containing the kind of language that he had previously complained about. This was the first time any video was mentioned or shown. The investigation was reopened.
- The HR representative who had led the prior investigation left the company two days later on July 8, 2016 and didn’t hand off the investigation to anyone else.
- Although Dewitt continued to have regular interaction with HR on a host of topics, for which he thanked them for their support, we have no evidence indicating that he came to HR with any further complaints of this nature. Then, through an attorney, Dewitt submitted a letter six months later demanding a very large payment or he would file a lawsuit.
- Once again, we looked into his claims and found that the co-workers Dewitt complained about described the situation very differently. They claimed once again they had all been friends and socialized outside of work, and that all of them (including Dewitt) used similar insensitive language with each other on a regular, ongoing basis, including in social contexts outside of the workplace.
- Confirming this, one of the employees Dewitt accused shared personal instant messages (attached) which showed Dewitt using the same language when describing other colleagues involved in the argument from April 2016. One of those messages indicated why he apparently decided to make these accusations – he was upset because of his belief that these colleagues had turned a video into HR showing Dewitt threatening one of them. The employee stated this was what led Dewitt to conjure up false claims about these other individuals.
- Dewitt alleges that he was not promoted as retaliation for having made complaints. This is false. Dewitt was promoted 12 months ago, and the reason he wasn’t given a second promotion within 12 months is that, among other things, he had been given a final written warning for posting pictures of confidential Tesla technology on Facebook in clear violation of company policy.
That brings us to today. We have been told by Dewitt’s attorney that they will be following up on their previous demand for a large payment by filing a lawsuit. The lawsuit has been timed to coincide with a carefully planned media blitz in an attempt to create a disingenuous narrative that is at odds with the facts.
It’s clear that our investigation should have continued uninterrupted until all the facts were known. We have terminated several employees based on what we’ve learned and have suspended Dewitt with pay so that we can finish investigating the circumstances of the instant messages that were just provided to us about his threats of violence against coworkers. We will continue to take action as necessary, including parting ways with anyone whose behavior prevents Tesla from being a great place to work. However, it’s also clear that Dewitt’s version of events is not supported by the facts. It would never be right to take action based on an accusation alone — there must be objective evidence or credible witnesses to ensure that an innocent person is not treated unfairly.
It is night and day to work at a company with strong purpose and great team spirit, where people look forward to coming to work. Monday either feels like jail or joy, and the people you work with make all the difference in the world.
The full lawsuit can be seen here:
https://www.teslarati.com/wp-content/uploads/2017/03/Tesla-Complaint-Filed-2017.03.27.pdf
Elon Musk
Tesla CEO Elon Musk teases insane capabilities of next major FSD update
Tesla CEO Elon Musk teased the insane capabilities of the next major Full Self-Driving update just hours after the company rolled out version 14.2 to owners.
Tesla Full Self-Driving v14.2 had some major improvements from the previous iteration of v14.1.x. We were on v14.1.7, the most advanced configuration of the v14.1 family, before Tesla transitioned us and others to v14.2.
However, Musk has said that the improvements coming in the next major update, which will be v14.3, will be where “the last big piece of the puzzle finally lands.”
14.3 is where the last big piece of the puzzle finally lands
— Elon Musk (@elonmusk) November 21, 2025
There were some major improvements with v14.2, most notably, Tesla seemed to narrow in on the triggers that caused issues with hesitation and brake stabbing in v14.1.x.
One of the most discussed issues with the past rollout was that of brake stabbing, where the vehicle would contemplate proceeding with a route as traffic was coming from other directions.
We experienced it most frequently at intersections, especially four-way stop signs.
Elon Musk hints at when Tesla can fix this FSD complaint with v14
In our review of it yesterday, it was evident that this issue had been resolved, at least to the extent that we had no issues with it in a 62-minute drive, which you can watch here.
Some owners also reported a more relaxed driver monitoring system, which is something Tesla said it was working on as it hopes to allow drivers to text during operation in the coming months. We did not test this, as laws in Pennsylvania prohibit the use of phones at any time due to the new Paul Miller’s Law, which took effect earlier this year.
However, the improvements indicate that Tesla is certainly headed toward a much more sentient FSD experience, so much so that Musk’s language seems to be more indicative of a more relaxed experience in terms of overall supervision from the driver, especially with v14.3.
Musk did not release or discuss a definitive timeline for the release of v14.3, especially as v14.2 just rolled out to Early Access Program (EAP) members yesterday. However, v14.1 rolled out to Tesla owners just a few weeks ago in late 2025. There is the potential that v14.3 could be part of the coming Holiday Update, or potentially in a release of its own before the New Year.
News
Tesla Full Self-Driving v14.2 – Full Review, the Good and the Bad
Tesla rolled out Full Self-Driving version 14.2 yesterday to members of the Early Access Program (EAP). Expectations were high, and Tesla surely delivered.
With the rollout of Tesla FSD v14.2, there were major benchmarks for improvement from the v14.1 suite, which spanned across seven improvements. Our final experience with v14.1 was with v14.1.7, and to be honest, things were good, but it felt like there were a handful of regressions from previous iterations.
While there were improvements in brake stabbing and hesitation, we did experience a few small interventions related to navigation and just overall performance. It was nothing major; there were no critical takeovers that required any major publicity, as they were more or less subjective things that I was not particularly comfortable with. Other drivers might have been more relaxed.
With v14.2 hitting our cars yesterday, there were a handful of things we truly noticed in terms of improvement, most notably the lack of brake stabbing and hesitation, a major complaint with v14.1.x.
However, in a 62-minute drive that was fully recorded, there were a lot of positives, and only one true complaint, which was something we haven’t had issues with in the past.
The Good
Lack of Brake Stabbing and Hesitation
Perhaps the most notable and publicized issue with v14.1.x was the presence of brake stabbing and hesitation. Arriving at intersections was particularly nerve-racking on the previous version simply because of this. At four-way stops, the car would not be assertive enough to take its turn, especially when other vehicles at the same intersection would inch forward or start to move.
This was a major problem.
However, there were no instances of this yesterday on our lengthy drive. It was much more assertive when arriving at these types of scenarios, but was also more patient when FSD knew it was not the car’s turn to proceed.
Can report on v14.2 today there were ZERO instances of break stabbing or hesitation at intersections today
It was a significant improvement from v14.1.x
— TESLARATI (@Teslarati) November 21, 2025
This improvement was the most noticeable throughout the drive, along with fixes in overall smoothness.
Speed Profiles Seem to Be More Reasonable
There were a handful of FSD v14 users who felt as if the loss of a Max Speed setting was a negative. However, these complaints will, in our opinion, begin to subside, especially as things have seemed to be refined quite nicely with v14.2.
Freeway driving is where this is especially noticeable. If it’s traveling too slow, just switch to a faster profile. If it’s too fast, switch to a slower profile. However, the speeds seem to be much more defined with each Speed Profile, which is something that I really find to be a huge advantage. Previously, you could tell the difference in speeds, but not in driving styles. At times, Standard felt a lot like Hurry. Now, you can clearly tell the difference between the two.
It seems as if Tesla made a goal that drivers should be able to tell which Speed Profile is active if it was not shown on the screen. With v14.1.x, this was not necessarily something that could be done. With v14.2, if someone tested me on which Speed Profile was being used, I’m fairly certain I could pick each one.
Better Overall Operation
I felt, at times, especially with v14.1.7, there were some jerky movements. Nothing that was super alarming, but there were times when things just felt a little more finicky than others.
v14.2 feels much smoother overall, with really great decision-making, lane changes that feel second nature, and a great speed of travel. It was a very comfortable ride.
The Bad
Parking
It feels as if there was a slight regression in parking quality, as both times v14.2 pulled into parking spots, I would have felt compelled to adjust manually if I were staying at my destinations. For the sake of testing, at my first destination, I arrived, allowed the car to park, and then left. At the tail-end of testing, I walked inside the store that FSD v14.2 drove me to, so I had to adjust the parking manually.
This was pretty disappointing. Apart from parking at Superchargers, which is always flawless, parking performance is something that needs some attention. The release notes for v14.2. state that parking spot selection and parking quality will improve with future versions.
Any issues with parking on your end? 14.1.7 didn’t have this trouble with parking pic.twitter.com/JPLRO2obUj
— TESLARATI (@Teslarati) November 21, 2025
However, this was truly my only complaint about v14.2.
You can check out our full 62-minute ride-along below:
Elon Musk
SpaceX issues statement on Starship V3 Booster 18 anomaly
The incident unfolded during gas-system pressure testing at the company’s Massey facility in Starbase, Texas.
SpaceX has issued an initial statement about Starship Booster 18’s anomaly early Friday. The incident unfolded during gas-system pressure testing at the company’s Massey facility in Starbase, Texas.
SpaceX’s initial comment
As per SpaceX in a post on its official account on social media platform X, Booster 18 was undergoing gas system pressure tests when the anomaly happened. Despite the nature of the incident, the company emphasized that no propellant was loaded, no engines were installed, and personnel were kept at a safe distance from the booster, resulting in zero injuries.
“Booster 18 suffered an anomaly during gas system pressure testing that we were conducting in advance of structural proof testing. No propellant was on the vehicle, and engines were not yet installed. The teams need time to investigate before we are confident of the cause. No one was injured as we maintain a safe distance for personnel during this type of testing. The site remains clear and we are working plans to safely reenter the site,” SpaceX wrote in its post on X.
Incident and aftermath
Livestream footage from LabPadre showed Booster 18’s lower half crumpling around the liquid oxygen tank area at approximately 4:04 a.m. CT. Subsequent images posted by on-site observers revealed extensive deformation across the booster’s lower structure. Needless to say, spaceflight observers have noted that Booster 18 would likely be a complete loss due to its anomaly.
Booster 18 had rolled out only a day earlier and was one of the first vehicles in the Starship V3 program. The V3 series incorporates structural reinforcements and reliability upgrades intended to prepare Starship for rapid-reuse testing and eventual tower-catch operations. Elon Musk has been optimistic about Starship V3, previously noting on X that the spacecraft might be able to complete initial missions to Mars.
