Connect with us

News

Tesla factory worker sues company over alleged race and sexual harassment

Published

on

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.

Advertisement
-

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:

Advertisement
-

https://www.teslarati.com/wp-content/uploads/2017/03/Tesla-Complaint-Filed-2017.03.27.pdf

I'm passionate about clean technology, sustainability and life. I've worked in manufacturing, IT, project management and environmental...and enjoy unpacking complex topics in layman's terms. TSLA investor. Find more of my words on my website or follow me on Twitter for all the latest. Tesla Referral link: http://ts.la/kyle623

Advertisement
Comments

Lifestyle

Watch Tesla’s “guardian angel” FSD feature take over for collision evasion

Published

on

By

Tesla’s Automatic Collision Evasion feature can be seen in one of the first owner videos of it in action.

Tesla owner Spencer (@scotsrule08) posted on Monday that the feature “worked flawlessly,” saying FSD reengaged itself just as he was about to hit a curb. Ashok Elluswamy, who leads Tesla’s AI team, shared the clip and wrote, “A guardian angel always looking out for you.”

The video arrives in the middle of a staged rollout. Tesla first shipped Automatic Collision Evasion with FSD (Supervised) v14.3.9 in software update 2026.27.6 earlier this month, which Teslarati covered as it reached cars. Update 2026.27.10, which began going out on September 19, carried the feature improvements with FSD v14.3.10, according to release notes tracked by Not a Tesla App. The newer 2026.27.11 build is now reaching another wave of vehicles.


The feature only runs on HW4 vehicles, and it requires an active FSD purchase or subscription with both FSD (Supervised) and Automatic Emergency Braking enabled. HW3 owners receive FSD v14.2 Lite in the same updates, but that build does not include collision evasion.

Advertisement
-

Tesla’s release notes describe two triggers. The first is an imminent frontal collision that braking alone may not prevent, in which case the car can activate FSD to steer, brake or accelerate around the hazard. That scenario is limited to highways below 85 mph, with no pedestrians or cyclists detected and no slippery road surface. The second covers a driver who appears inattentive, such as reaching into the back seat, or who seems to have switched off FSD by accident. Spencer’s curb clip appears to fall into that second category.

Tesla plans big safety improvements for Full Self-Driving v15

Once the system takes over, the accelerator is muted and light brake input will not cancel the maneuver. Drivers need to apply firm, deliberate steering force to take back control, and the car chimes to hand control back once the danger has passed.

Elluswamy recently noted that earlier hazard prediction, faster reaction time and better collision avoidance would arrive with FSD v15, the next major version.

Continue Reading

News

Tesla Roadster event gets delayed due to unfavorable weather

Published

on

Credit: Tesla

Tesla is delaying its event for the Roadster, moving it from this Thursday, October 1, to Thursday, October 15, due to unfavorable weather.

The company has said it has been tracking the weather for this Thursday closely with local meteorologists, and because the event can only be held outside, Tesla is making the call to delay it:

“We’ve been tracking the weather closely with local meteorologists, but given the severe conditions predicted & because this event can only be held outdoors, we’ve made the difficult decision to reschedule. New date is October 15. Additional details to follow.”

We are sure that this is bringing back PTSD for some Tesla fans, and we know it is not ideal, but this also reveals some things about the event. Tesla said that this can only be held outdoors, meaning it bodes well for the rumors that the vehicle could potentially hover.

Some believe that this was essentially confirmed by the FAA airspace restriction they were granted, but this could have been for a drone show or to keep drones from spying on the event.

Tesla Roadster is available for order once again following brief hold

The Roadster event has been long-awaited, and it is unfortunate that the weather is going to keep us all waiting a little bit longer.

The Tesla Roadster will be unveiled in Waco, Texas.

Advertisement
-
Continue Reading

Elon Musk

SpaceX turned a heralding moment for Starship into its greatest

Starship reached orbit despite losing an engine, deployed 26 Starlink V3 satellites on Flight 14.

Published

on

By

SpaceX’s Starship reached orbit for the first time on Monday, and for a few nail-biting minutes it looked like it wouldn’t. During ascent on Flight 14, one of Ship 41’s six Raptor engines shut down early, and SpaceX’s livestream host Dan Huot told viewers the team had decided not to commit to orbit. Minutes later, after what Huot described as a lot of conversation in the control room, the final poll came back in favor, and a roughly 19 second burn of a single Raptor pushed the ship into orbit about 170 miles up.

The reversal matters because SpaceX had written the exit ramp into the mission plan. The company said it would only fire the orbital insertion burn if flight controllers confirmed enough backup hardware remained for the deorbit burn, a condition Teslarati laid out ahead of the flight. Losing an engine was exactly the scenario that rule was built for.

Pressing forward fits Elon Musk’s history. Falcon 1 failed three straight times before its fourth launch reached orbit in 2008, with SpaceX nearly out of money, and Starship was developed by flying prototypes until they broke. What changed this year SpaceX going public, and with $SPCX sliding below its IPO price in July when Flight 13 slipped, the short interest climbed significantly, as Teslarati reported at the time. A Starship potentially lost today with revenue generating next-gen Starlink satellites aboard would have landed directly on shareholders.

That pressure showed up after orbit. SpaceX cut a flight planned to last nearly 10 hours to about three, moving splashdown from west of Chile to the North Pacific near Hawaii. SpaceX gave no reason, though Musk said this month the company was being extremely cautious about debris risk. The single Raptor for deorbit worked, and Ship 41 completed its flip and landing burn before breaking apart in the water, an outcome SpaceX expected. Musk has structured SpaceX’s governance to shield long term bets from market pressure.

Advertisement
-

The payload is the bigger business story. Musk posted that all 26 Starlink V3 satellites deployed and are “operating nominally.” Each V3 is rated for about 1 Tbps of downlink and 160 Gbps of uplink, so this single launch adds roughly 26 Tbps, about 10 times what a Falcon 9 load of V2 Mini satellites adds. The V3 is too large for Falcon 9, making Starship the only vehicle that can build out the planned 100,000 satellite constellation, at up to 60 per flight once it reaches routine service. Unlike the 20 V3 units on Flight 13, which reentered on a suborbital path, these will raise their orbits and could begin serving customers within weeks and bring in hundreds of millions of additional dollars in projected Starlink revenue.

SpaceX has already begun winding down Falcon 9 Starlink launches from Florida in favor of Starship. Reported targets put Flight 15 as early as October 19, leaving about three weeks to diagnose Monday’s engine shutdown before the next orbital attempt.

Continue Reading