Connect with us

News

FBI taps Tesla Sentry Mode footage to help catch man behind alleged hate crimes

Credit: CourtListener

Published

on

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. 

Advertisement

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.

Advertisement

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. 

Advertisement

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. 

Advertisement

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

Advertisement

Don’t hesitate to contact us for news tips. Just send a message to tips@teslarati.com to give us a heads up.

Simon is an experienced automotive reporter with a passion for electric cars and clean energy. Fascinated by the world envisioned by Elon Musk, he hopes to make it to Mars (at least as a tourist) someday. For stories or tips--or even to just say a simple hello--send a message to his email, simon@teslarati.com or his handle on X, @ResidentSponge.

Advertisement
Comments

News

Tesla Cybercab gets crazy change as mass production begins

Tesla has officially kicked off mass production of its groundbreaking Cybercab robotaxi at Giga Texas, and the first units rolling off the line feature a striking transformation that’s turning heads across the EV community.

Published

on

Credit: TechOperator | X

Tesla Cybercab has evidently received a pretty crazy change from an aesthetic standpoint, as the company has made the decision to offer an additional finish on the vehicle as mass production is starting.

Tesla has officially kicked off mass production of its groundbreaking Cybercab robotaxi at Giga Texas, and the first units rolling off the line feature a striking transformation that’s turning heads across the EV community.

VIN Zero—the very first production Cybercab—showcases a vibrant champagne gold exterior with a high-gloss finish, a dramatic departure from the flat, matte-wrapped prototypes that debuted at the 2024 “We, Robot” event.

This glossy sheen is a pretty big pivot from what was initially shown by Tesla. The company has maintained a pretty flat tone in terms of anything related to custom colors or finishes.

A specialized clear coat or process delivers the deep, reflective gloss without conventional painting. The result is a premium, mirror-like shine, and it looks pretty good, and gives the compact two-seater a more luxurious and futuristic presence than the subdued matte prototypes.

Photos shared by Tesla community members reveal VIN Zero in a showroom-like setting at Giga Texas, highlighting refined panel gaps, large aero wheel covers, and the signature no-steering-wheel, no-pedals interior optimized for full autonomy.

Advertisement

The open frunk in some images offers a glimpse of practical storage, while the overall build quality appears more polished than that of test mules.

This glossy evolution aligns with Tesla’s broader production ramp. After the first unit in February 2026, the company has shifted to volume manufacturing, with dozens of units already spotted in outbound lots. CEO Elon Musk and the team aim for hundreds per week, paving the way for unsupervised FSD robotaxi networks that could slash ride costs to pennies per mile.

The Cybercab holds Tesla’s grand ambitions of operating a full-service ride-hailing service without any drivers in its grasp. Tesla has yet to solve autonomy, but is well on its way, and although its timelines are usually a bit off, improvements often come through the Over-the-Air updates to the Full Self-Driving suite.

Advertisement
Continue Reading

News

Tesla confirms Cybercab with no steering wheel enters production

Published

on

Tesla has confirmed today that its steering wheel-less and pedal-less Cybercab, the vehicle geared toward launching the company’s autonomous ride-hailing hopes, has officially entered production at its Giga Texas production facility outside of Austin.

The Cybercab is a sleek two-door, two-passenger coupe engineered from the ground up as an electric self-driving vehicle. It features no steering wheel or pedals, relying instead on Tesla’s advanced vision-only Full Self-Driving system powered by multiple cameras and artificial intelligence.

The minimalist cabin centers on a large display screen that serves as the primary interface for passengers, creating an open, futuristic space optimized for comfort during unsupervised rides. A compact 35-kilowatt-hour battery pack delivers exceptional efficiency at 5.5 miles per kilowatt-hour, providing an estimated 200-mile range.

Additional innovations include inductive charging compatibility and a lightweight design that enhances aerodynamics and performance.

Production at Giga Texas builds on earlier prototypes and initial units completed earlier in 2026. The facility, already a hub for Model Y and Cybertruck assembly, now ramps up dedicated lines for the Cybercab.

Advertisement

This shift to volume manufacturing reflects Tesla’s strategy to scale affordable autonomous vehicles rapidly.

By focusing on a dedicated platform rather than adapting existing models, the company aims to keep costs low while prioritizing safety and reliability through continuous AI improvements.

The Cybercab’s debut in production carries broad implications for urban mobility. As the cornerstone of Tesla’s Robotaxi network, it promises on-demand, driverless rides that could slash transportation expenses, reduce traffic accidents caused by human error, and lower emissions through its all-electric powertrain.

Accessibility features, such as space for service animals or assistive devices, further broaden its appeal. Regulators and cities worldwide will soon evaluate its deployment, but the vehicle’s design already addresses key hurdles in scaling unsupervised autonomy.

Advertisement

Challenges persist, including full regulatory clearance and building charging infrastructure. Yet this production launch signals momentum. With Cybercabs poised to roll out in increasing numbers, Tesla edges closer to a future where personal ownership meets shared fleets of intelligent vehicles.

The start of Cybercab production is more than just a new vehicle entering mass manufacturing for Tesla, as it’s a signal autonomy is near. Being developed without manual controls is such a massive sign by Tesla that it trusts its progress on Full Self-Driving.

While the development of that suite continues, Tesla is making a clear cut statement that it is prepared to get its fully autonomous vehicle out in public roads as it prepares to revolutionize passenger travel once and for all.

Advertisement
Continue Reading

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.

Published

on

(Photo: Hector Perez/YouTube)

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:

Advertisement

“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:

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.

Advertisement

It also did so without hesitation, confidently, and at a comfortable speed. I was able to test it twice at different distances:

Advertisement

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.

Advertisement

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.

Advertisement

Some said I should not have labeled this as Critical, but that’s the description I best characterized the disengagement as.

Advertisement

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.

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.

Advertisement

“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:

Advertisement

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.

Advertisement

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:

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.

Advertisement
Continue Reading