Connect with us

News

Tesla Model S police cruiser not to blame for mishap, says Fremont PD

Credit: Twitter/Fremont Police Department

Published

on

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.

Advertisement
-

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.

Advertisement
-


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.

Joey has been a journalist covering electric mobility at TESLARATI since August 2019. In his spare time, Joey is playing golf, watching MMA, or cheering on any of his favorite sports teams, including the Baltimore Ravens and Orioles, Miami Heat, Washington Capitals, and Penn State Nittany Lions. You can get in touch with joey at joey@teslarati.com. He is also on X @KlenderJoey. If you're looking for great Tesla accessories, check out shop.teslarati.com

Advertisement
Comments

Lifestyle

Watch Tesla’s “guardian angel” FSD feature take over for collision evasion

Published

on

By

Tesla’s Automatic Collision Evasion feature can be seen in one of the first owner videos of it in action.

Tesla owner Spencer (@scotsrule08) posted on Monday that the feature “worked flawlessly,” saying FSD reengaged itself just as he was about to hit a curb. Ashok Elluswamy, who leads Tesla’s AI team, shared the clip and wrote, “A guardian angel always looking out for you.”

The video arrives in the middle of a staged rollout. Tesla first shipped Automatic Collision Evasion with FSD (Supervised) v14.3.9 in software update 2026.27.6 earlier this month, which Teslarati covered as it reached cars. Update 2026.27.10, which began going out on September 19, carried the feature improvements with FSD v14.3.10, according to release notes tracked by Not a Tesla App. The newer 2026.27.11 build is now reaching another wave of vehicles.


The feature only runs on HW4 vehicles, and it requires an active FSD purchase or subscription with both FSD (Supervised) and Automatic Emergency Braking enabled. HW3 owners receive FSD v14.2 Lite in the same updates, but that build does not include collision evasion.

Advertisement
-

Tesla’s release notes describe two triggers. The first is an imminent frontal collision that braking alone may not prevent, in which case the car can activate FSD to steer, brake or accelerate around the hazard. That scenario is limited to highways below 85 mph, with no pedestrians or cyclists detected and no slippery road surface. The second covers a driver who appears inattentive, such as reaching into the back seat, or who seems to have switched off FSD by accident. Spencer’s curb clip appears to fall into that second category.

Tesla plans big safety improvements for Full Self-Driving v15

Once the system takes over, the accelerator is muted and light brake input will not cancel the maneuver. Drivers need to apply firm, deliberate steering force to take back control, and the car chimes to hand control back once the danger has passed.

Elluswamy recently noted that earlier hazard prediction, faster reaction time and better collision avoidance would arrive with FSD v15, the next major version.

Continue Reading

News

Tesla Roadster event gets delayed due to unfavorable weather

Published

on

Credit: Tesla

Tesla is delaying its event for the Roadster, moving it from this Thursday, October 1, to Thursday, October 15, due to unfavorable weather.

The company has said it has been tracking the weather for this Thursday closely with local meteorologists, and because the event can only be held outside, Tesla is making the call to delay it:

“We’ve been tracking the weather closely with local meteorologists, but given the severe conditions predicted & because this event can only be held outdoors, we’ve made the difficult decision to reschedule. New date is October 15. Additional details to follow.”

We are sure that this is bringing back PTSD for some Tesla fans, and we know it is not ideal, but this also reveals some things about the event. Tesla said that this can only be held outdoors, meaning it bodes well for the rumors that the vehicle could potentially hover.

Some believe that this was essentially confirmed by the FAA airspace restriction they were granted, but this could have been for a drone show or to keep drones from spying on the event.

Tesla Roadster is available for order once again following brief hold

The Roadster event has been long-awaited, and it is unfortunate that the weather is going to keep us all waiting a little bit longer.

The Tesla Roadster will be unveiled in Waco, Texas.

Advertisement
-
Continue Reading

Elon Musk

SpaceX turned a heralding moment for Starship into its greatest

Starship reached orbit despite losing an engine, deployed 26 Starlink V3 satellites on Flight 14.

Published

on

By

SpaceX’s Starship reached orbit for the first time on Monday, and for a few nail-biting minutes it looked like it wouldn’t. During ascent on Flight 14, one of Ship 41’s six Raptor engines shut down early, and SpaceX’s livestream host Dan Huot told viewers the team had decided not to commit to orbit. Minutes later, after what Huot described as a lot of conversation in the control room, the final poll came back in favor, and a roughly 19 second burn of a single Raptor pushed the ship into orbit about 170 miles up.

The reversal matters because SpaceX had written the exit ramp into the mission plan. The company said it would only fire the orbital insertion burn if flight controllers confirmed enough backup hardware remained for the deorbit burn, a condition Teslarati laid out ahead of the flight. Losing an engine was exactly the scenario that rule was built for.

Pressing forward fits Elon Musk’s history. Falcon 1 failed three straight times before its fourth launch reached orbit in 2008, with SpaceX nearly out of money, and Starship was developed by flying prototypes until they broke. What changed this year SpaceX going public, and with $SPCX sliding below its IPO price in July when Flight 13 slipped, the short interest climbed significantly, as Teslarati reported at the time. A Starship potentially lost today with revenue generating next-gen Starlink satellites aboard would have landed directly on shareholders.

That pressure showed up after orbit. SpaceX cut a flight planned to last nearly 10 hours to about three, moving splashdown from west of Chile to the North Pacific near Hawaii. SpaceX gave no reason, though Musk said this month the company was being extremely cautious about debris risk. The single Raptor for deorbit worked, and Ship 41 completed its flip and landing burn before breaking apart in the water, an outcome SpaceX expected. Musk has structured SpaceX’s governance to shield long term bets from market pressure.

Advertisement
-

The payload is the bigger business story. Musk posted that all 26 Starlink V3 satellites deployed and are “operating nominally.” Each V3 is rated for about 1 Tbps of downlink and 160 Gbps of uplink, so this single launch adds roughly 26 Tbps, about 10 times what a Falcon 9 load of V2 Mini satellites adds. The V3 is too large for Falcon 9, making Starship the only vehicle that can build out the planned 100,000 satellite constellation, at up to 60 per flight once it reaches routine service. Unlike the 20 V3 units on Flight 13, which reentered on a suborbital path, these will raise their orbits and could begin serving customers within weeks and bring in hundreds of millions of additional dollars in projected Starlink revenue.

SpaceX has already begun winding down Falcon 9 Starlink launches from Florida in favor of Starship. Reported targets put Flight 15 as early as October 19, leaving about three weeks to diagnose Monday’s engine shutdown before the next orbital attempt.

Continue Reading