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.
News
Tesla Summon got insanely good in FSD v14.3.2 — Navigation? Not so much
There were two new lines of improvements in the release notes: one addressing Actually Smart Summon (ASS), and another that now allows drivers to choose a reason for an intervention via a small menu during disengagement.
Tesla Full Self-Driving v14.3.2 began rolling out to some owners earlier this week, and there are some notable improvements that came with this update.
There were two new lines of improvements in the release notes: one addressing Actually Smart Summon (ASS), and another that now allows drivers to choose a reason for an intervention via a small menu during disengagement.
Overall operation saw a handful of slight improvements, especially with parking performance, which has been the most notable difference with the arrival of FSD v14.3. However, there are still some very notable shortcomings, most notably with region-specific signage and navigation.
Tesla Assisted Smart Summon (ASS) improvements
There are noticeable improvements to ASS operation, which has definitely been inconsistent in terms of performance. Tesla wrote in the release notes for v14.3.2:
“Unified the model between Actually Smart Summon, FSD, and Robotaxi for more capable and reliable behavior.”
As recently as this month, I used Summon with no success. It had pulled around the parking lot I was in incorrectly, leaving the range at which Summon can be operated and losing a signal while moving in the middle of the lot.
This caused me to sprint across the lot to retrieve the vehicle:
It was pouring when I left the gym so I tried to Summon my Model Y
It turned the opposite way and drove out of range, stopping here and forcing me to walk even further across the lot in the rain for it 🤣
One day pic.twitter.com/iD10c8sriB
— TESLARATI (@Teslarati) April 5, 2026
Unfortunately, Summon was not dependable or accurate enough to use regularly. It appears Tesla might have bridged the gap needed to make it an effective feature, as two tests in parking lots proved that Summon was more responsive and faster to navigate to the location chosen.
It also did so without hesitation, confidently, and at a comfortable speed. I was able to test it twice at different distances:
🚨 Tesla FSD v14.3.2 ASS testing part 1
This was a significant improvement than recent tries using ASS. The parking lot was pretty empty but getting it to come to my location in one singular motion and maneuver was encouraging. https://t.co/vF7TS48GGV pic.twitter.com/sYt8tyHgNn
— TESLARATI (@Teslarati) April 23, 2026
Tesla Full Self-Driving v14.3.2 ASS testing part 2 https://t.co/lxfWfnLUxf pic.twitter.com/2R0r3ohI3M
— TESLARATI (@Teslarati) April 23, 2026
I plan to test this more thoroughly and regularly through the next few weeks, and I avoided using it in a congested parking lot initially because I have not had overwhelming success with Summon in the past. I wanted to set a low baseline for it to see if it could simply pull up to the place I pinned in the Tesla app.
It was two for two, which is a big improvement because I don’t think I ever had successful Summon attempts back-to-back. It just seems more confident than ever before.
New Disengagement Categories
This is a really good idea from Tesla, but there are some issues with it. The categories you can select are Critical, Comfort, Preference, and Other.
I think the reasons why people choose to take over would be a better way to prompt drivers, like, “Traveling Too Fast,” “Incorrect Maneuver,” “Navigation Error,” would be more beneficial.
I say this because it seems that how we each categorize things might be different. For example, I shared a video of an intervention because the car had navigated to an exit to a parking lot and put its left blinker on, despite left turns not being allowed there.
I disengaged and chose Critical as the reason; it’s not a comfort issue, it’s not a preference, it’s quite literally an illegal turn, and it’s also dangerous because it cuts across several lanes of traffic and is 180 degrees.
I chose to label this Navigation error as “Critical” while testing FSD v14.3.2
Here’s why:
✅ This intervention wasn’t “preference,” as the maneuver FSD routed was illegal
✅ If a police officer saw this maneuver, it would result in a ticket https://t.co/znhHb4haAo pic.twitter.com/bZOiLwWmQa— TESLARATI (@Teslarati) April 23, 2026
Some said I should not have labeled this as Critical, but that’s the description I best characterized the disengagement as.
Categorizing interventions is a good thing, but it’s kind of hard to determine how to label them correctly.
Inconsistency with Regional Traffic Patterns
Tesla Full Self-Driving is pretty inconsistent with how it handles regional or local traffic patterns and road rules. The most frequent example I like to use is that of the “Except Right Turn” stop sign, which has become a notorious sighting on our social media platforms.
In the initial rollout of v14.3, my Model Y successfully navigated through one of these stop signs with no issues. However, testing at two of these stop signs yesterday proved it is still not sure how to read signs and navigate through them properly.
🚨 Tesla FSD v14.3.2 attempts the “Except Right Turn” stop sign: https://t.co/W5MjAybaNK pic.twitter.com/P6oeUsk4PN
— TESLARATI (@Teslarati) April 23, 2026
Off camera, I approached another one of these signs and felt the car coming to a stop, so I nudged it forward with the accelerator pedal pressed.
This helped the car go through the sign without stopping, but I could feel the bucking of the vehicle as the car really wanted to stop.
Musk said on the earnings call earlier this week that unsupervised FSD would probably be available in some regions before others, including a state-to-state basis in the U.S.
“It’s difficult to release this like to everyone everywhere all at once because we do want to make sure that they’re not unique situations in a city that particularly complex intersection or — actually, they tend to be places where people get into accidents a lot because they’re just — perhaps there’s — and like I said, an unsafe intersection or bad road markings or a lot of weather challenges. So I think we would release unsupervised gradually to the customer fleet as we feel like a particular geography is confirmed to be safe.”
This could be one of those examples that Tesla just has to figure out.
Highway Operation
Full Self-Driving is already pretty good at routine roadway navigation, so I don’t have too much to report here.
However, I was happy with FSD’s decision-making at several points, including its choice not to pass a slightly slower car and remain in the right lane as we approached the off-ramp:
🚨 Tesla FSD v14.3.2 highway operation: generally happy with the performance here, especially behavior near the exit
Love that the car got over in the right lane after its final pass, and stayed there as the off ramp was approaching https://t.co/qVRVhg6XGR pic.twitter.com/1ELwHf2XKS
— TESLARATI (@Teslarati) April 23, 2026
Better Maneuvering at Stop Signs
Many FSD users report some strange operations at stop signs, especially four-way intersections where there is a stop sign and a line on the road, and they’re not even with one another.
I experienced this quite frequently and found that FSD would actually double stop: once at the stop sign and again at the line.
This created some interesting scenarios for me and I had many cars honk at me when the second stop would happen. Other vehicles that had waved me on to proceed through the intersection would become frustrated at the second stop.
FSD seems to have worked through this particular maneuver:
🚨 Tesla FSD v14.3.2 with a singular stop at the correct spot
No double stopping anymore in my experience https://t.co/Wd0TaNjc1R pic.twitter.com/CdQPvJHaAM
— TESLARATI (@Teslarati) April 23, 2026
FSD should know to go to the more appropriate location (whichever provides better visibility), and proceed when it is the car’s turn to move. The double stop really ruined the flow of traffic at times and generally caused some frustration from other drivers.
News
Tesla plans to resolve its angriest bunch of owners: here’s how
Since the rollout of the AI4 chip in Tesla vehicles, owners with the last generation self-driving chip, known as Hardware 3, have been persistent in their quest for a solution to their issue: they were told their cars were capable of unsupervised Full Self-Driving. It turns out the cars are not.
Tesla has a plan to make Hardware 3 owners whole after CEO Elon Musk admitted that those with that self-driving chip in their cars will not have access to unsupervised Full Self-Driving.
The company’s strategy is so crazy that it is sort of hard to believe.
Since the rollout of the AI4 chip in Tesla vehicles, owners with the last generation self-driving chip, known as Hardware 3, have been persistent in their quest for a solution to their issue: they were told their cars were capable of unsupervised Full Self-Driving. It turns out the cars are not.
Tesla owners with HW3 finally get their answer: https://t.co/CSZTKKkWXx
— TESLARATI (@Teslarati) April 22, 2026
During the Tesla Q1 earnings call on Wednesday, Musk finally clarified what the company’s plans are for Hardware 3 owners, what they will be offered, and what Tesla will have to do internally to prepare for it.
The answer was somewhat mind-boggling.
Musk said:
“Unfortunately, Hardware 3 — I wish it were otherwise, but Hardware 3 simply does not have the capability to achieve unsupervised FSD. We did think at one point it would have that, but relative to Hardware 4, it has only 1/8 of the memory bandwidth of Hardware 4. And memory bandwidth is one of the key elements needed for unsupervised FSD.”
He continued, stating that HW3 owners would have the opportunity to trade their cars in at a discounted rate in order to get the AI4 chip:
“So for customers that have bought FSD, what we’re offering is essentially a trade-in — like a discounted trade-in for cars that have AI4 hardware, and we’ll also be offering the ability to upgrade the car, to replace the computer. And you also need to replace the cameras, unfortunately, to go to Hardware 4.”
Obviously, Tesla has a lot of people to work with and make this whole thing right. Musk was adamant that HW3 would be capable of FSD, and now that the company has finally admitted that it is not, there are some things that could come of this.
There has been open talk about some sort of class action lawsuit against Tesla. The promises that Tesla made previously could be considered a breach of contract or even false advertising, and that’s according to Grok, Musk’s own AI program.
Musk went on to say that Tesla would likely have to establish new microfactories to effectively and efficiently replace HW3 computers and cameras:
…So to do this efficiently, we’re going to have to set up, like kind of micro factories or small factories in major metropolitan areas in order to do it efficiently. Because if it’s done just at the service center, it is extremely slow to do so and inefficient. So we basically need like many production lines to make the change.”
This is going to be an extremely costly process, especially if Tesla has to buy real estate, properties, and equipment to complete this work. Additionally, there was no wording on pricing, but Musk never said it would be free. It will likely come with some kind of price tag, and HW3 owners, after being left hanging for so long, will have something to say about that.
Elon Musk
SpaceX just got pulled into the biggest Weapons Program in U.S. history
SpaceX joins the Golden Dome software group, deepening its role in America’s most expensive defense program.
SpaceX has joined a nine-company group developing the core operating software for the Golden Dome, America’s next-generation missile defense system. According to a Bloomberg report, SpaceX is focused on integrating satellite communications for military operations and is working alongside eight other defense and artificial intelligence companies, including Anduril Industries, Palantir Technologies, and Aalyria Technologies, to build software connecting missile defense capabilities.
The Golden Dome concept dates back to President Trump’s 2024 campaign, and on January 27, 2025, he signed an executive order directing the U.S. Armed Forces to construct the system before the end of his term. The system is planned to employ a constellation of thousands of satellites equipped with interceptors, with data centers in space providing automated control through an AI network.
FCC accepts SpaceX filing for 1 million orbital data center plan
Space Force Gen. Michael Guetlein, director of the Golden Dome initiative, has described the software layer as a “glue layer” that would enable officers to manage and control radars, sensors, and missile batteries across services. The consortium is aiming to test the platform this summer.
Trump selected a design in May 2025 with a $175 billion price tag, expected to be operational by the end of his term in 2029, though the Congressional Budget Office projected the cost could reach $831 billion over two decades.
The Golden Dome role is only the latest in a string of military wins for SpaceX. As Teslarati reported, the U.S. Space Force awarded SpaceX a $178.5 million task order on April 1, 2026 to launch missile tracking satellites for the Space Development Agency, covering two Falcon 9 launches beginning in Q3 2027. That came on top of more than $22 billion in government contracts held by SpaceX as of 2024, per CEO Gwynne Shotwell, spanning NASA resupply missions, classified intelligence satellites through its Starshield program, and military broadband.
The accumulation of defense contracts, now including a seat at the table on the most expensive weapons program in U.S. history, positions SpaceX as the dominant infrastructure provider for American national security in space. With a SpaceX IPO still on the horizon, each new contract adds weight to what is already one of the most consequential companies in aerospace history, raising real questions about how much of America’s defense architecture will depend on a single private operator before it ever trades publicly.
Tesla Summon got insanely good in FSD v14.3.2 — Navigation? Not so much
Tesla plans to resolve its angriest bunch of owners: here’s how
