News
Tesla’s health clinic surgeon explains practice amid Reveal’s new allegations
Last Monday, an expose was published accusing Tesla of intentionally ignoring workers’ injuries. Citing former employees and a physician assistant who briefly worked in the company’s health clinic at the Fremont factory, Reveal, a publication that prides itself with its investigative reporting, accused Tesla of withholding medical care to its workers, to minimize how many injuries the company includes in its official records.
The new expose is not the first time Reveal trained its sights on the electric car maker. Earlier this year, the publication, based on accounts from former employees, accused Tesla of misreporting injury rates and ignoring safety concerns due to the whims of executives like Elon Musk. The publication’s allegations ultimately resulted in an investigation by the CAL-OSHA, which lasted four months. As noted by VP for Environmental, Health and Safety (EHS) Laurie Shelby during the third quarter earnings call and in a following blog post in Tesla’s official website, the CAL-OSHA investigation found no misreporting on Tesla’s part. The CAL-OSHA did find one safety issue and one record-keeping error during its four month-long investigation, in the form of an extension cord that was categorized as a trip hazard and an injury log that had an incorrect date.
Apart from doubling down on previous allegations — such as Tesla’s factories lacking hazard signs due to Elon Musk’s dislike of the color yellow — Reveal‘s new expose, written by journalist Will Evans, related several accounts of workers being denied proper medical care. One such instance involved a worker who severed the top of a finger being sent to the emergency room in a Lyft, as well as an employee who was asked to report to work even after being injured in the Model X line. The publication also alleged that Tesla forbids employees to call 911 without a doctor’s permission. Former PA Anna Watson, who worked in Tesla’s Fremont health clinic for about three weeks, noted that Tesla’s employees are paying the price for the company’s unsafe practices. Watson further alleged that she was terminated by Access Omnicare after raising safety concerns.
“The goal of the clinic was to keep as many patients off of the books as possible. The way they were implementing it was very out of control. Every company that I’ve worked at is motivated to keep things not recordable. But I’ve never seen anybody do it at the expense of treating the patient,” she said.
The publication’s new allegations have emerged as a dark cloud hovering over Tesla’s revamped workers’ safety programs, which have been at the forefront of the company as it continues to ramp its operations. Since hiring VP for Environmental, Health and Safety (EHS) Laurie Shelby last year, Tesla has actively rolled out new initiatives to raise the level of safety for its facilities’ amidst the company’s ever-increasing number of workers. Shelby, for one, has noted that Tesla remains focused on its efforts to become the safest car factory in the world.
Tesla is yet to respond to Reveal‘s new report, though a spokesperson from the company noted that Watson completed a total of five shifts before her employment was terminated. Dr. Basil Besh, an orthopedic surgeon and founder of Access Omnicare, has also issued a statement explaining the company’s practices when dealing with workers’ injuries. Besh, who currently serves as the chair of the American Academy of Orthopaedic Surgeons (AAOS) Board of Councilors (BOC), noted that the care that Access Omnicare gives to Tesla’s employees is the same care he gives to his personal clientele. The orthopedic surgeon noted that he had spoken to Reveal journalist Will Evans about the safety practices in the Fremont factory.
“I spent nearly one hour with Reveal detailing Tesla’s decision earlier this year to bring me and my medical team on site at Fremont, providing its employees with state-of-the-art occupational and musculoskeletal health care. I detailed our vision for exemplary patient care, and I gave specific examples of protocol improvements and subsequent successes in outcomes in only four short months, including accurate diagnoses and reducing needless delays for advanced testing and treatment. I patiently educated Will Evans on how Tesla allowed me to give the same care to Tesla employees that I do to my private patients including ones who are professional athletes, with the ability to get necessary testing and treatment in a timely manner without being hindered by an often cumbersome California Worker’s Compensation System that sometimes negatively effects injured workers.”
-
Dr. Besh further noted that different types of injuries require different types of immediate care. The medical professional also denies that any malpractice is ongoing in the Tesla factory.
“I counseled Will on the difference between subjective complaints of pain, which cannot be proven and are often magnified, and objective signs found only on careful clinical examination by an experienced physician. I even mailed Will a copy of a relevant chapter from the American Medical Association Return to Work Guidelines and offered to make myself available for additional questions. Research and evidence-based medicine indicate that deconditioning injuries involving sore muscles should not be treated with inactivity as this only exacerbates the problem, but should instead be treated by proactive conditioning, ergonomic modifications, and supportive care. Not all patients in pain should be off work, at home, and on opioids. In fact, it is most often in these patients’ best interest to have supportive care that enhances their activity, their function, and their well-being.
“As a physician, my foremost obligation is to perform a careful history and physical examination, order additional tests when clinically indicated, make an accurate diagnosis, and deliver the absolute best care possible. If patients are injured, and continued work presents safety issues for the patient, myself and my fellow physicians prescribe the appropriate work restrictions. Any suggestion that myself or any of my medical team at AOC allow external factors to influence our medical care in any way is false and inaccurate.”
Ultimately, Dr. Besh also pointed out that ambulances are reserved for life or limb-threatening injuries. The surgeon did not provide a direct comment about former physician assistant Anna Watson, due to the latter being the subject of an ongoing investigation by the California Medical Board.
“Rather than deliver an informative and balanced piece of journalism, Reveal has instead chosen to hitch its wagon to Ms. Anna Watson, a provider with whom we severed ties after less than two weeks at our clinic and about whom I cannot provide any additional comment as she is currently the subject of an investigation by the California Medical Board. Instead of highlighting the tremendous progress being made in both patient safety and patient care at Tesla, this report uses poor sourcing to tell a story consistent with a predetermined agenda,” Dr. Besh stated.
Tesla released Full Self-Driving version 14.3.6 last week, and after what was potentially one of the best FSD releases in v14.3.5, there has been a bit of a regression. While there are some bright spots, the changes made to v14.3.6 seem to have backtracked some behaviors.
Overall, it is hard to really complain about FSD in any sense; it has revolutionized how I travel literally anywhere. According to my self-driving app, the last time I went a day without using it was 59 days ago.
However, I think it’s also important to recognize when things are just plain bad with FSD. There are times it does truly mind-boggling things, and I’ll dive into those here. Additionally, I only had these issues on local roads, not on highways. Highway operation, generally, is always incredible other than the occasional complaint about speed or left lane camping.
With those things being said, my personal experience may not represent others’ experiences. A handful of people have said they have had a similar experience on v14.3.6, while others have said it is more than normal.
Turning Hesitancy, Inaccuracy
I’ve noticed more inaccuracy turning into multi-lane stretches of road than in any version I can remember. I’ve had at least three instances of FSD turning into a stretch of roadway that has two or more lanes, and not selecting a lane confidently as it has in past versions.
I think Tesla FSD v14.3.6 is a regression from previous .3 branches
This version in particular has been incredibly hesitant, jerky, and indecisive at times. There’s actually been two drives that I have decided to not used FSD for the remainder of the trip. These were local trips… pic.twitter.com/YobHDOKRS6
— TESLARATI (@Teslarati) July 26, 2026
-
Instead, the car will drive over one of the dashed road lines, and the steering wheel will jerk back and forth before picking the lane. It should be said that it has always picked the correct lane when choosing based on the navigation, but it is still very indecisive. The steering wheel jerking is reminiscent of some of the later versions of v13.
I admit I really hate to see the steering wheel jerking come back. However, I think when Tesla releases v14.3.7, it won’t be present. When there are occurrences of it in FSD versions, it is usually resolved by the following release.
FSD Disregards Manual Turn Signals
This is my biggest bone to pick with FSD other than Navigation issues, but this one seems like it would be such an easy fix.
If Tesla is going to put the word “Supervised” on the end of “Full Self-Driving,” then when I tell the car to do something, it should do it. If I input an increase in speed by pressing the accelerator, the car will immediately respond. It does not disregard my input because it feels it is traveling at the right speed.
FSD should never disobey and turn off turn signals that the driver inputs. Trying to direct the car into the correct lane, I had initiated the left turn signal not once, not twice, but three times, with the car turning it off all three times and continuing in a lane that would end in just one block. The only solution at this point would be to zipper merge.
This goes back to the fact that self-driving’s biggest bottleneck might be rider preference. A zipper merge might have been more than reasonable, might have saved me time that I spent sitting through an additional light cycle, and might be something many drivers would do. I was in no hurry, I traditionally do not try to zipper merge because it feels inconsiderate, and lastly, the car should have just followed my input.
-
This caused me to disengage and drive manually the rest of the way home. Sometimes I just do not need FSD to try to pass every car it can at intersections.
Bird Braking is a Thing of the Past
The big complaint with recent versions of Full Self-Driving has been what we’ve coined as “bird braking,” which is when the car will brake suddenly as a bird flies past.
There have been zero issues with this so far in v14.3.6, which is an excellent improvement.
FSD Might Already Be Taking Note of Driver Preferences
Another thing I have noticed over the past few days is that v14.3.6 seems to already be taking my preferences with navigation into account.
This is something that is supposed to be rolling out with the Summer Update, but I have a hunch it’s already present and might have been included in this v14.3.6 build. On Friday, FSD pulled into an entrance to a local convenience store that it had never attempted to go into before.
Typically, I manually pull into this entrance because it avoids heavy cross traffic at the main entrance. FSD has always chosen that congested main entrance.
I don’t want to get anyone excited but my Tesla running FSD v14.3.6 just:
✅ Pulled into an entrance at my local Sheetz that I routinely pull into manually but FSD never has entered
-✅ Pulled into my assigned parking space at home despite many other spots being vacant https://t.co/ZUShvknTWO pic.twitter.com/83O5a2S0eh
— TESLARATI (@Teslarati) July 24, 2026
Additionally, FSD has pulled into my assigned parking spot at my townhouse community on multiple occasions with this release. This is something that used to happen ocassionally, but not consistently.
It also navigated back to the same convenience store last night, drove through crazy cars scrambling to gas pumps, navigated out of the parking lot correctly, drove me home, and, once again, parked in my assigned spot.
As previously stated, this release just seems to have a few things that need to be brought to Tesla’s attention, and also to make others who use FSD aware of some things that I’ve experienced. I look forward to the next release that will remedy these issues, just as Tesla has always done in the past.
-
Elon Musk’s massive Terafab project, which will be the first true conglomeration between each of his major entities, is set to get its final location soon, the CEO said on Tesla’s recent earnings call.
“The Terafab, we expect to announce a location soon, and provide more details about our plans in that regard. We’ll leave that to the product, the launch announcement rather than try to squeeze it into an earnings call,” Musk said last Wednesday.
Tesla Terafab set for launch: Inside the $20B AI chip factory that will reshape the auto industry
Terafab was announced by Musk back in March and was essentially a massive, vertically integrated semiconductor manufacturing project that would provide all the chips the three companies needed for their AI initiatives without needing third-party companies.
The plant will produce over 1 terawatt of AI compute each year, and will help back up projects like Optimus, Full Self-Driving, and other AI-based projects that Musk’s companies are working on.
In April, less than a month after the project was launched, Intel announced it would join the project, contributing manufacturing expertise and consulting to Terafab as a whole. Intel is one of three chip manufacturers that produce sub-5 nanometer chips at scale. TSMC and Samsung are the other two.
However, there was no true indication of where Terafab would end up, but most believe it will likely be somewhere in Texas. Business Insider has reported that SpaceX plans to build out Terafab in Grimes County, Texas, but this is unconfirmed.
-
Musk confirmed recently that it would not be on Giga Texas property, as it is simply too large.
The sheer scale of TERAFAB is going to be insane.
Elon said it wouldn’t be suitable for anywhere on Giga Texas property because it’s too big:
“We couldn’t possibly fit the Terafab on the GigaTexas campus. It will be far bigger than everything else combined there.
Several… pic.twitter.com/79GbhNNuf4
— TESLARATI (@Teslarati) March 23, 2026
Terafab holds much of Musk’s grand ambitions for the future within its construct. It holds so much responsibility for the future and the biggest projects that Musk’s companies can imagine.
-
“I think this is a very big announcement and it deserves to have its own day in the spotlight and not be squeezed into an earnings call,” he said. “I do think Terafab is going to be an amazing initiative and a necessary one, and one without which we will be constrained in our ability to scale Optimus production, because we simply won’t have enough AI chips.”
He continued by stating that Terafab is necessary for scaling Optimus, which Musk said could be the biggest product of any kind of all time. “It’s crucial to solve that, and we’ll have to solve memory, logic, and packaging in order to scale Optimus.”
SpaceX performed a secret test on a specific portion of Starship with its recent 13th test flight last week, CEO Elon Musk revealed.
Starship’s 13th test flight took place last Friday, and in many aspects, it was one of the most overwhelmingly successful launches in the project’s history.
All of the mission objectives were met without incident, both the Super Heavy Booster and Ship managed to perform safe splashdowns in the Gulf of America and the Indian Ocean, respectively, and the deployment of Starlink satellites came and went without any complications.
— Elon Musk (@elonmusk) July 25, 2026
However, there was more on the agenda for SpaceX with Flight 13. Musk revealed an internal test of the ship’s heat shield tiles, as the space exploration company wanted to push them to the limits after previous issues.
Many noticed that Starship’s initial launch seemed to be more accelerated than normal, and that was not a mistake. Musk revealed that SpaceX decided to give Flight 13 an intentionally aggressive acceleration rate in an effort to test how well the tiles would remain attached to the ship:
-
This flight intentionally had much higher acceleration to test how well the heat shield tiles would remain attached at high dynamic pressure.
Test was successful.
— Elon Musk (@elonmusk) July 25, 2026
SpaceX had issues with some of the heat shield tiles remaining attached early on in the Starship program. The first six test flights presented some kind of anomaly with them, so the company’s big focus with them was to figure out a way to keep them intact through the duration of the flight.
Things truly improved as Flight 10 showed that ceramic tiles generally stayed attached to the ship far better due to refined attachment, as SpaceX utilized pins instead of adhesives. Flights 10 through 13 truly showed some clear progress with the heat shield tiles, and this latest test seems to be where some real progress was noticed, especially by Musk.
The 13th Starship launch last Friday was the second with Starship V3, SpaceX’s latest and greatest iteration of the spacecraft. Goals and ambitions are getting even grander as the project continues to progress. Musk has already hinted that SpaceX will likely try to catch Starship with Flight 14.
-
Tesla Full Self-Driving v14.3.6 review: a rare regression, but some bright spots
Musk’s massive Terafab project will get final location soon
