News
FBI taps Tesla Sentry Mode footage to help catch man behind alleged hate crimes
It appears that some members of the Federal Bureau of Investigation (FBI) are now becoming familiar with Tesla’s built-in security features like Sentry Mode, which allows vehicles to record videos from their cameras to actively monitor their surroundings. This was undoubtedly the case in an incident back in December, which involved slashed tires, arson, and what appears to be a racially motivated attack against a church.
In an affidavit dated April 15, 2021, FBI Special Agent Casey Anderson outlined the events that led to an incident that resulted in the destruction of the Martin Luther King, Jr. Community Presbyterian Church in Springfield, Massachusetts. The suspect behind the incident, 44-year-old Maine resident Dushko Vulchev, is a naturalized United States citizen from Bulgaria. As per the FBI agent’s affidavit, Vulchev had previously run afoul of the law prior to his apparent arson in December, having been convicted of threatening a foreign official in 2015 and a series of offenses such as domestic violence assault in 2017.
The Martin Luther King, Jr. Community Presbyterian Church in Springfield, Massachusetts before the fires. (Credit: CourtListener)
The Attacks
In December 2020, the MLK Church experienced a series of fires, one of which eventually destroyed the whole building. The first of these fires were reported on December 13, when the fire department was deployed to extinguish a blaze behind the church. On the same day, a vehicle had its tires slashed two miles away from the church. The next day, a BMW about 1.5 miles away from the MLK church and a Tesla parked less than a mile away from the church had their tires slashed. In the case of the Tesla, its owner found that one of the vehicle’s wheels was also missing.
Another fire behind the Martin Luther King, Jr. Community Presbyterian Church was set on December 15, 2020, at around 6:32 p.m. The Springfield Police Department (SPD) Arson and Bomb Squad investigated the fire and promptly determined that the blaze had been intentionally ignited. Interestingly enough, another fire in the church was reported at 11:03 p.m. that same day. Upon investigation, the SFD reported that the blaze had been “intentionally set to eventually involve the structure” of the church.
Things essentially calmed down until December 27, when a Dodge Charger had its tires slashed just 400-500 feet away from the MLK Church. At around 5:06 a.m. the next day, the American International College campus police reported a new blaze at the MLK Church. This time, the fire was started just outside the basement side door, where it burned through and up through the church’s main floor. The blaze essentially destroyed the church, and upon investigation, the SPD concluded that the fire was intentional.
Photos of the MLK Church during the December 28, 2020 blaze. (Credit: CourtListener)
-
The Investigation
Investigators working on the case were able to obtain several video footage relevant to the case. In the first tire slashing incident on December 13, footage from the City of Springfield recorded a gray Chevy Cruze pulling up into the same parking lot as the vehicle that was attacked. The car was found to have been registered to the suspect, Vulchev. City video footage captured the suspect crossing the street in the direction of the MLK Community Center later that day. The gray Chevy Cruze was also recorded circling the MLK Church.
Vulchev’s Chevy Cruze was sighted by city video footage once more the next day, when the BMW tire slashing incident transpired. As per the FBI agent’s affidavit, a while male matching Vulchev’s height, gait, and clothing, was spotted approaching the BMW. Later that day, a Tesla became the next victim of the suspect’s tire slashing tendencies. But this time around, the special agent didn’t just have a faraway shot of a man approaching a vehicle. This time around, authorities were able to get a clear shot of Vulchev as he was slashing and stealing the Tesla’s tires and stealing a wheel, thanks to Sentry Mode. Tesla’s built-in cameras even captured the suspect putting the stolen goods inside his trunk.
Special Agent Casey Anderson related his experience with Teslas and their built-in cameras in his affidavit. “Based on my training and experience and this investigation, I am aware that the Tesla referenced above is equipped with cameras at various points around the body. ATF Special Agent Marc Maurino (“SA Maurino”) and I have reviewed video footage retrieved from the Tesla showing an individual that I can identify as Vulchev, based on my observation of Vulchev during the Vulchev PPD Interview.
“The video footage from the Tesla shows Vulchev at a close distance crouching near the Tesla and using a tire iron to remove the wheels. Additional Tesla video footage captured Vulchev removing one of the Tesla’s wheels and placing it in the trunk of Vulchev’s car. Vulchev’s face is clearly visible in the video. Vulchev was wearing grey pants and a dark-colored sweatshirt, Adidas three-stripe sneakers, a black hat with two grey stripes, and light-colored work gloves, the agent noted in his affidavit.
Vulchev and his vehicle were spotted around the MLK Church fires, as well as subsequent tire slashing incidents.
The MLK Church after the December 28, 2020 fire. (Credit: CourtListener)
The Arrest
On December 30, 2020, a complaint about a vehicle driving erratically was reported to authorities. When provided with the license plate of the vehicle in question, it was determined that the car was Vulchev’s. Police stopped the suspect’s vehicle on suspicion of erratic driving and possible links to the multiple tire slashing incidents. Since they were aware of the ongoing federal investigation into the fires against MLK Church, local authorities promptly contacted FBI Supervisory Special Agent of the Springfield Resident Agency Matthew Fontaine.
-
Special Agent Fontaine arrived at the scene of the stop, and upon initial investigation, the FBI agent noted that the suspect may have been living in his car for some time. The FBI agent spoke with the suspect for about eight minutes outside, and immediately, Fontaine noted that Vulchev was wearing the sneakers that were captured clearly by Tesla’s Sentry Mode. PPD officers initially released the suspect, though he was arrested the day after over his links to the multiple tire slashing incidents and the Martin Luther King, Jr. Community Presbyterian Church fires.
On January 4, 2021, the FBI and ATF conducted a search of Vulchev’s vehicle, where they found a computer, a hard drive, and several USB storage devices. A search of the computer revealed Vulchev’s shocking racially charged stance against non-white people. This was seen in messages to an ex-girlfriend—who currently has a lifetime protective order against Vulchev—which featured numerous slurs against Muslims and blacks. Vulchev’s apparent hate against non-whites was notable, as seen in a message to his ex-girlfriend where he was complaining about the race of ABC’s The Bachelorette. A search of the suspect’s phone revealed photos of several notable items, such as a firearm, an image of Adolf Hitler in an Adidas tracksuit, and a “White Lives Matter” mural, as well.
With these in mind, FBI Special Agent Casey Anderson noted that there is probable cause to believe that Vulchev committed damage to religious property, which is in violation of 18 USC §§ 247(c) and (d)(3), and the use of fire to commit a federal felony, which is in violation of USC § 844(h)(1). As per a press release from the US Department of Justice, Vulchev is currently in state custody and is due to make an initial appearance in federal court in Springfield at a later date.
FBI Special Agent Casey Anderson’s complete affidavit could be accessed below.
gov.uscourts.mad.233009.2.1_1 by Simon Alvarez on Scribd
Don’t hesitate to contact us for news tips. Just send a message to tips@teslarati.com to give us a heads up.
-
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
