News
Tesla Model S police cruiser not to blame for mishap, says Fremont PD
The Fremont Police Department released a statement on Thursday evening clarifying reports that its Tesla Model S cruiser ran out of battery during a high-speed pursuit on Interstate 680.
On Monday, the Tesla Model S gained national attention as a journalist contacted the department requesting information regarding a high-speed chase from the Irvington District of Fremont, California to Washington Boulevard. The chase eventually ended up on Interstate 680, heading south toward San Jose, CA. The journalist released a portion of the police scanner recordings from the chase, where the officer driving the Model S told other units in the pursuit that he would have to abandon due to his battery running low.
However, the suspect then drove onto the shoulder of the interstate, passing a vehicle in an increasingly unsafe manner. The Sargeant of the Fremont PD then made the decision to halt the pursuit of the vehicle as it was becoming more of a public safety risk. All three police units disengaged the vehicle, and the chase was stopped after about 10 miles.
When the Sargeant made the announcement to stop pursuing the vehicle, the Tesla Police Cruiser was at a nearby charging station. The statement from the Fremont PD stated, “at no time did the battery of the Tesla become a factor in our ability to pursue the suspect or perform our duties. This situation, while embarrassing, is no different from cases where a patrol car runs low (or even dry) of fuel.”
Fremont’s statement noted that the journalist who released the initial story contacted the department with questions and subsequently published the article. It reached the national spotlight due to public interest. Fremont Police were sure to clarify the fact that the Tesla having to drop out of the chase could have happened to any vehicle and that they recommend each officer have at least half of a tank of gas or half a battery charge when they begin their shift. “While not policy, we recommend officers begin their shift with at least a half tank of gas or in this case, a battery charge of 50%. On this date, our officer driving the Tesla noted approximately 50% of battery life when he began his shift,” they said. The fact that the vehicle had to stop was in no way the fault of the Model S.
In fact, the department has been so pleased with their Tesla cruiser, they have already had initial talks about buying a second vehicle, most likely a Model X. “So far, the vehicle is performing extremely well, and has exceeded our expectations. We are already in initial conversations about testing a second vehicle, likely an SUV model, and we look forward to providing our initial results in the near future,” Captain Sean Washington said.
The Fremont PD stated that their Model S police cruiser has outperformed their expectations and they are extremely happy with its performance, as they have tracked the performance of the vehicle since its induction into the police force. “Over the last six months, data on range, performance, equipment, and other elements has been gathered by officers through its use as a patrol vehicle. During this time we have documented two police pursuits, where the vehicle met and exceeded expectations.”
-
Fremont is the location of the original Tesla Factory. The company bought the facility in 2010. Previously, it was the home of General Motors from 1962 to 1982 and eventually, Toyota also produced vehicles there. Tesla and Toyota worked conjunctively to work toward producing electric vehicles. Tesla officially opened the factory as its own on October 27, 2010.
Read the full statement from the Fremont Police Department below:
Our Department has unfortunately been in the news this week for an incident involving our electric police patrol vehicle (Tesla Model S). We first deployed the Tesla in March of this year as a fully outfitted patrol vehicle. Over the first six months, the performance feedback and initial data collection has been very positive and we are in early discussions of expanding the program. During a pursuit last Friday night, the battery charge began to run low, and we’d like the opportunity to clarify and provide additional context with regard to what occurred.
On Friday afternoon, a patrol officer checked out our Tesla patrol vehicle at the start of his shift and noticed the battery was half-charged. A typical battery at full charge ranges from 220-240 miles and during an 11 hour patrol shift, Fremont patrol officers drive approximately 70-90 miles. While not policy, we recommend officers begin their shift with at least a half tank of gas or in this case, a battery charge of 50%. On this date, our officer driving the Tesla noted approximately 50% of battery life when he began his shift. While the vehicle is routinely charged between shifts, on Friday the vehicle had just been returned from our Corporation Yard. The vehicle is regularly returning at the end of every shift with 40-60%, if not more, of the battery charge remaining.
Nine hours into the officer’s shift, at 11:05 p.m., he became involved in a vehicle pursuit that lasted a total of 8 minutes. The pursuit began in our Irvington District and traveled on Washington Blvd., before merging southbound onto I680 towards San Jose. Within minutes, two additional Fremont patrol units were behind the Tesla and in the pursuit. Additionally, the California Highway Patrol (CHP) was notified and responding. As standard protocol, once CHP has sufficient units, they take over our pursuits on the freeway.
The pursuit spanned approximately 10 miles and at times exceeded 110 mph. Regular updates regarding the speed, location, general traffic and roadway conditions were provided by the second officer in the pursuit. Just before the pursuit ended at 11:13 p.m., the officer driving the Tesla responsibly notified his cover units he was going to have to back out of the pursuit because his battery was running low. Just after they passed the Montague Expressway exit, the suspect drove on the left shoulder of the road to pass a vehicle. At that time, the Fremont Police Sergeant monitoring the pursuit gave orders to terminate to ensure public safety. All three units deactivated their emergency equipment and returned to normal driving conditions. At that point, the Tesla was driven to a nearby charging station and the additional Fremont units returned to the City. CHP located the unoccupied vehicle in the area of I680 and the Berryessa exit. At no time did the battery of the Tesla become a factor in our ability to pursue the suspect or perform our duties. This situation, while embarrassing, is no different from cases where a patrol car runs low (or even dry) of fuel.
In recent years police radio traffic has become readily accessible through phone applications and its common practice for news media and even community members to monitor and even record. On Monday, a local journalist contacted our Department requesting additional details regarding the pursuit. The journalist subsequently wrote an article and released a portion of our radio traffic. Since that time, the Department has received numerous media inquiries regarding the vehicle’s battery. Unfortunately, public interest in the original story propelled it into the national spotlight.
-
Over the last six months, data on range, performance, equipment, and other elements has been gathered by officers through its use as a patrol vehicle. During this time we have documented two police pursuits, where the vehicle met and exceeded expectations. Our final results and data will ultimately help us determine if the EV technology meets current patrolling applications and cost effectiveness. We remain dedicated to our continued research into the benefits of using electric vehicles and the effects they have on our environment. We hope to share our initial data and feedback soon.
Captain Sean Washington stated, “So far, the vehicle is performing extremely well, and has exceeded our expectations. We are already in initial conversations about testing a second vehicle, likely an SUV model, and we look forward to providing our initial results in the near future.”
For more information on our electric vehicle pilot program, visit www.fremontpolice.org/electricvehicle.
Tesla released Full Self-Driving version 14.3.7 yesterday, and after about 90 miles of testing today, it is evident there are some definite fixes from version 14.3.6, which I wrote about last week and called a regression.
Within the first 40 minutes of my drive on v14.3.7, it saved me from getting into an accident with an unaware Dodge Charger driver, and some of the things Tesla seemed to miss in v14.3.6 were definitely improved. All in all, the release so far has some really great performance, and I’m looking forward to testing it further.
For now, here’s everything I noticed with v14.3.7:
Overall Improvement
Just generally speaking from a ride perspective, this was a really great experience. A lot of the hesitancy I experienced on v14.3.6 was gone. There were no instances of brake-stabbing, wheel-jerking, or any uncertain or unconfident movements. It was void of anything that I felt made it timid with v14.3.6.
The one thing I do hope to see down the road is a smaller need to adjust Speed Profiles so often. Because Tesla calls FSD “Supervised,” I’m okay with needing to hit the scroll wheel a few times a drive.
However, I hope that things can be incrementally improved upon with speed. Sometimes it’s too fast; other times it’s too slow. It’s a difficult thing to hone in and refine, but I hope it eventually gets there.
I didn’t notice any significant left lane camping or any behaviors that were completely out of line. I am hopeful that this opinion does not change, but after driving a few days with this version and putting it in a variety of different situations, you are exposed to more behaviors, some of which are not necessarily what I’d prefer.
-
The big things to notice, at least in my experience thus far, are that the major issues with previous versions — meaning the braking stabbing and wheel jerking — simply weren’t there. That’s enough to already consider this progress compared to .6.
Manual Signal Override is More Responsive
On .6, I had quite a few issues with FSD ignoring my manually input turn signals. If Tesla wants to call it “Supervised,” then the car should not ignore any input the driver gives. If I touch the accelerator on FSD, the car speeds up.
🚨 Tesla FSD v14.3.7 obeying manual turn signals https://t.co/6eqToXpQfC pic.twitter.com/vHBlFQ4PDV
— TESLARATI (@Teslarati) August 2, 2026
The car did a great job of obeying my turn signals when I wanted it to change lanes, which is welcome.
Parking Lot Performance
Before .6, I traditionally took over in nearly every parking lot my car entered, because I knew it would not park somewhere that I wanted, and usually, it was just a tad too timid in this setting.
The one bright spot of .6 was how well it handled parking lots. This continued with v14.3.7:
-
I’m always really happy to see progress at all, but once parking preferences come to FSD, as long as this performance is still around, that could potentially be the biggest improvement I’ve seen in FSD in the year I’ve been using it personally on a daily basis.
Full Self-Driving Averts Disaster
A Dodge Charger changed into my lane without checking if I was there, running me off the road. FSD made the initial avoidance maneuver; I grabbed the wheel out of instinct, looked in my side mirror to ensure I had nobody following closely behind, hit the brake, and straightened the car back up to avoid a curb:
🚨 Guys this is why you all NEED to stay vigilant behind the wheel, even on Tesla Full Self-Driving
Human drivers are UNHINGED and have no idea what they’re doing anymore. This was a kid obviously younger than 20 years old with zero awareness.
First drive with v14.3.7 https://t.co/1vTbCMpCn8 pic.twitter.com/lz7KKEF6bj
— TESLARATI (@Teslarati) August 2, 2026
-
There have been quite a few responses to this video stating that I should never have grabbed the wheel. To be honest, I really wish I had not done so, because I do believe FSD would have avoided any sort of collision with anything, including the car or the curb.
However, this was the first time I had ever been this close to being hit while using FSD. My natural reaction was to take over. I think if I had had something like this happen before, my reaction might have been different.
Hitting the brake avoided hitting the curb, while FSD swerved to avoid the car. My concern after the car was clear of my front end was the curb. All in all, I’m really happy with how things turned out, and I think anyone could be a critic of how I handled it. I only had a split second to really make a decision, and thankfully, any damage was avoided.
It is clear FSD managed to avoid the car coming down before I was able to. I truly credit FSD for avoiding the collision.
What Needs to Improve
Better Recognition of Potholes, Uneven Roads, Sharp Changes in Roadway/Bumps
On Friday, my Fianceè and I were in the car, and FSD was driving us. We crossed over a roadway that has a traffic light, and FSD was traveling at 40 MPH on Standard, 5 MPH over the speed limit. Everything was more than reasonable.
However, the road we were crossing at the light has a major bump both as you start and finish crossing it. Without a speed reduction, your car can go airborne. The Tesla did just this on Friday on v14.3.6; it was an uncomfortable bounce that pretty much confirmed I would not ever let FSD go over again unless we were sitting at that intersection when there is a red light.
I even tried scrolling down into Sloth quickly, but I ended up just taking over:
-
This is that big bounce that I mentioned in the quoted post.
It’s just a tad too drastic to take at the speed FSD wants to go over it. You can see me quickly swipe down into Sloth, but I intervened. https://t.co/K20PK9ysBg pic.twitter.com/81Oc82ZJcZ
— TESLARATI (@Teslarati) August 2, 2026
A few people have said it remains related to the vision-based approach and its difficulty comprehending 3D. This is a huge issue because this can cause serious damage at certain speeds.
Navigation
Nothing new here. I still turn off “Online Routing” quite frequently to get the car to take logical routes from time to time.
Auto Wipers
Auto Wipers are just plain bad. I really hope Tesla just uses a rain sensor. I thought they had improved at one point, but I still get dry wipes, Speed 4 on a drizzle, and Speed 2 on a steady rain. In reality, these should be switched.
You can watch our full review of Tesla Full Self-Driving v14.3.7 below:
-
🚨 Tesla Full Self-Driving v14.3.7 saved me from an accident! FULL REVIEW: https://t.co/1vTbCMpCn8 pic.twitter.com/9mHmKVoMVA
— TESLARATI (@Teslarati) August 2, 2026
SpaceX will report second quarter results after the market closes on Tuesday, August 4, marking the first time the company has opened its books to the public since its record IPO in June. Management will host a live audio only webcast at 4:30 p.m. ET, streamed on X, with no dial in option.
The debut carries more weight than a typical first quarter as a public company. Two trading days after the release, on August 6, the first tranche of SpaceX’s lockup expires, freeing roughly 911.5 million insider and employee shares, worth well over $100 billion at current prices and the largest such release in Wall Street history. A second, larger tranche tied to the stock trading 30 percent above its $135 IPO price never triggered, since shares have spent most of July trading below that price.
Wall Street’s models point to revenue near $6.9 billion for the quarter, up sharply from the $4.69 billion SpaceX reported in the first quarter, with a narrower per share loss than the $1.27 posted three months earlier, according to estimates compiled by Motley Fool. Those numbers will be the first look at how SpaceX’s three segments, Starlink, launch and AI, are performing independently.
SpaceX scores another massive Pentagon deal to support military satellites
Investors heading into the call have a specific list of questions. How many net new Starlink subscribers did SpaceX add after ending March with 10.3 million, and is average revenue per user holding up as the service expands into lower income markets. How much of the AI segment’s revenue reflects contract signings with Anthropic, Google and Reflection AI this year, deals that combined could annualize to nearly $28 billion if fully ramped. Whether capital expenditures, which nearly doubled in the AI segment alone between 2024 and 2025, are still accelerating or starting to plateau. And whether management offers any forward guidance at all, something SpaceX has never done publicly.
The report will also land days after Elon Musk publicly denied a Wall Street Journal report describing internal planning to separate Tesla’s China business ahead of a potential Tesla-SpaceX merger. Whether Musk or SpaceX executives address that speculation on the call, even indirectly, maybe something investors will be listening for on Tuesday.
As Teslarati reported after Musk’s own warning to short sellers last week, the CEO has made clear he expects skeptics to be proven wrong over time. Tuesday will be the first chance for the numbers themselves to make that case.
-
Elon Musk
SpaceX’s Starship just got filmed by its own cargo
SpaceX released new footage of Starship in space captured by the Starlink satellites it deployed.
SpaceX released a new video Friday evening showing Starship from an angle showcased by its own Starlink satellites, watching the rocket drift away in orbit.
The 65 second clip, posted on X, stitches together footage from four cameras mounted on a single Starlink V3 satellite. It opens with a close view of Starship’s 171 foot upper stage, still catching sunlight, then pulls back as the two spacecraft separate.
The footage comes from Starship’s 13th flight test, which launched July 24 from Starbase after a scrubbed attempt and an abort caused by an engine issue the week before. When Flight 13 finally flew, it carried the first batch of functional Starlink V3 satellites Starship has ever deployed, twenty of them, with six equipped with cameras meant to scan the ship’s heat shield during reentry.
View of Starship in space from a Starlink V3 satellite on Flight 13.
This composite is made of imagery from four separate cameras on a single satellite. Six of the satellites were equipped with cameras to scan Starship’s heat shield and transmit imagery down to operators to… pic.twitter.com/sNTHHz5vLr
— SpaceX (@SpaceX) July 31, 2026
Flight 13 checked most of its boxes. Starship deployed all 20 satellites, relit a Raptor engine in space, and splashed down softly in the Indian Ocean off Western Australia. Musk’s longer term plan calls for a Starlink V3 constellation of 100,000 satellites, according to a recent FCC filing, with Starship as the only vehicle capable of launching them at the volume that requires. Each Starship flight is designed to carry up to 60 V3 satellites once the vehicle reaches routine service, well beyond what Falcon 9 can carry in a single mission.
-
Starship is next expected to fly with an attempt at catching the ship itself with the launch tower’s mechanical arms, a maneuver SpaceX has so far reserved for the Super Heavy booster.
Tesla Full Self-Driving v14.3.7 early review: FSD saved me from an accident
SpaceX’s biggest test yet arrives this week and it’s not a rocket launch
