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 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.
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.
Tesla CEO Elon Musk teases insane capabilities of next major FSD update
Tesla Full Self-Driving v14.2 – Full Review, the Good and the Bad
