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 has reached a notable benchmark in its autonomous driving program after its Robotaxi fleet surpassed one million miles of unsupervised operation. The company made the announcement during its Cybercab event in Austin on September 3.
Tesla Vice President of AI Ashok Elluswamy told attendees he was happy to report the fleet had achieved one million miles of unsupervised Robotaxi operation as a testament to safety.
The new total marked a sharp increase from the 380,000 unsupervised miles Tesla disclosed during its second-quarter 2026 earnings update in late July.
In roughly six weeks, the company added about 620,000 miles. That acceleration followed Tesla’s decision to remove in-vehicle safety monitors from most of its operations outside the San Francisco Bay Area.
Credit: Tesla
Tesla first launched Robotaxi service in Austin in June 2025 with safety drivers present. It later began fully unsupervised rides and expanded into Dallas, Houston, Miami, Orlando, and Tampa. The San Francisco Bay Area remains the exception, where a safety monitor still rides in the vehicle under California permitting rules.
The company has not released a city-by-city breakdown of the one million unsupervised miles.
The milestone arrived as Tesla began offering public Cybercab rides in Austin. The purpose-built vehicle has no steering wheel or pedals and is designed only for autonomous ride-hailing. Production versions joined the existing fleet of modified Tesla vehicles already operating in the service.
Tesla’s unsupervised mileage is growing at a double-digit weekly rate according to earlier company comments, yet its fleet size remains modest compared with established competitors. Waymo has accumulated more than 200 million fully autonomous rider-only miles. Tesla has described its own unsupervised operations as having recorded zero notable incidents in the period leading up to the July update.
The one-million-mile figure reflects Tesla’s shift from supervised testing to broader driverless service in multiple states. It also highlights the company’s strategy of using both existing Model Y vehicles and the new Cybercab to scale its network.
Credit: Tesla
Whether the rapid recent growth continues will depend on further city expansions, regulatory approvals, and the performance of the purpose-built Cybercab in everyday paid rides. Tesla has not specified how many of the latest miles involved the new vehicle versus the rest of the fleet.
The announcement underscores Tesla’s progress toward a larger robotaxi network while illustrating the remaining gap in total autonomous experience relative to longer-operating rivals.
Tesla AI lead Ashok Elluswamy said this week that 24-hour Robotaxi service is close. Replying on X to a rider who wanted Cybercab trips all night, he wrote that the capability would arrive “next month or so” once “the next tech to merge on the v15 plan” is ready.
The comment landed on September 4, one day after Tesla opened public Cybercab rides in Austin. It is the clearest near-term timeline yet for overnight unsupervised operation. Tesla’s paid Robotaxi network currently runs from 6 a.m. to 10 p.m. seven days a week across Austin, Dallas, Houston, Miami, Orlando, and Tampa.
next month or so. the next tech to merge on the v15 plan will enable it.
— Ashok Elluswamy (@aelluswamy) September 4, 2026
That 16-hour window is shorter than the 6 a.m. to 2 a.m. schedule the company used for much of the prior year.
Elluswamy did not name the specific feature or say whether the change would apply first to purpose-built Cybercabs, the existing Model Y fleet, or both. He also offered no city-by-city rollout list. The link to Full Self-Driving v15 is nevertheless significant.
Tesla has described v15 as a step-change architecture with seven parallel improvement tracks and roughly ten times more parameters than earlier builds. Early versions of that software already operate on the Robotaxi fleet and contain about 40 percent of the planned gains.
By July 2026, the unsupervised fleet had logged more than 380,000 miles across six cities in two states with what the company called an impeccable safety record and no notable incidents caused by the vehicles themselves. Tesla has repeatedly argued that camera-based end-to-end neural networks, rather than extra sensors, are the core of the solution.
Overnight service would test that claim in lower-light conditions and would also raise vehicle utilization, a key variable for Robotaxi unit economics. The company has already begun using public Superchargers at night and is building dedicated Robotaxi charging sites.
Riders have asked why software must change if the cars already drive in the dark. The practical answer appears to be reliability and scale: Tesla has held back mass expansion until more of the v15 stack is merged, citing the need for higher confidence before putting thousands of unoccupied vehicles on streets around the clock.
If the next module arrives on the timetable Elluswamy sketched, 24-hour service could begin in October 2026 in at least some markets.
That would mark a shift from a daytime-bounded pilot to a service that can run whenever demand exists, including the late-night hours that have so far remained out of reach.
Tesla is beginning to roll out Full Self-Driving Supervised v14.3.9 with a new active safety layer that can take control even when the driver is operating the car manually.
Tesla AI said the software can activate FSD on the driver’s behalf when an imminent collision is detected and Automatic Emergency Braking may not be enough. It may also engage if the system detects heavy distraction or an accidental FSD disengagement.
FSD Supervised v14.3.9 starting to roll out shortly
This release includes a new active safety feature set: FSD Supervised can now activate on your behalf when an imminent collision is detected and Automatic Emergency Braking (AEB) may not be enough.
It may also engage if we…
— Tesla AI (@Tesla_AI) September 4, 2026
The capability is essentially Automatic Collision Evasion. However, unlike conventional AEB, which mainly applies the brakes in a straight line, this feature can use steering, braking, and acceleration together if the car calculates that stopping alone will not prevent impact and a safer path exists. The system may change lanes or move toward a shoulder when conditions allow, then continue driving after the immediate threat is handled rather than simply coming to a stop.
The intervention is meant as a last-resort safety net, not a replacement for attentive driving.
Tesla Full Self-Driving v14.3.7 early review: FSD saved me from an accident
Tesla’s own description still frames FSD as supervised assistance. Secondary reports on internal release notes say the feature can fire while the car is being driven manually if cabin-camera monitoring suggests the driver is not sufficiently attentive, such as reaching toward the back seat, or if FSD appears to have been turned off unintentionally.
After the emergency maneuver, the car is expected to alert the driver and request a return to manual control.
The safety case is straightforward. Many collisions happen in the last second because a driver is looking away, fumbles a control, or faces an obstacle that braking cannot fully solve. A system that can both recognize that AEB is insufficient and execute a coordinated evasive path can reduce those remaining high-severity events.
Re-engaging after accidental disengagement also addresses a practical failure mode: a small steering nudge that drops FSD at the worst moment. The advantage is a background safety net that uses the same vision stack already running in v14, instead of leaving the car solely to emergency braking once the driver is no longer in command.
The feature still depends on FSD being enabled and, according to reports, an active FSD purchase or subscription. It does not make the vehicle unsupervised. Drivers remain responsible, and Tesla has not published how often the system is expected to intervene or how it will handle false positives.
If the rollout is conservative and the false-alarm rate stays low, the update is a meaningful step: FSD is no longer only a feature the driver turns on. In the rare moments when disaster is already forming, it can step in.
Tesla crosses major Unsupervised Self-Driving milestone
Tesla Robotaxi will be a 24/7 service: here’s when
