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

News

Tesla Full Self-Driving release in the EU gets delayed

Published

on

Credit: Grok Imagine

Tesla Full Self-Driving’s release in Europe is set to be delayed by at least a few months.

The European Union will not vote on Tesla’s Full Self-Driving (Supervised) on October 6. The draft agenda for the 119th meeting of the Technical Committee on Motor Vehicles lists only a 25-minute “continuation of discussions” on the Netherlands’ Article 39 request, not a decision. The next scheduled TCMV session is in December, which is now the earliest date a bloc-wide vote could occur.

Tesla Europe had pointed to October 6 as a possible EU-wide vote after the Dutch vehicle authority RDW granted the first European type approval on April 10.

That approval, under UN Regulation 171 plus an Article 39 exemption in EU Regulation 2018/858, is the legal file other member states have been recognizing one by one. The same committee has already discussed the request twice without voting.

Elon Musk’s reply to the delay was a single word: “Sigh.”

Seven EU countries have now cleared FSD Supervised on their own roads: the Netherlands, Lithuania, Estonia, Denmark, Belgium, Slovenia, and Czechia. Those seven states represent about 53 million people, or roughly 12 percent of the EU population. An EU-wide authorization still needs a qualified majority: at least 15 of 27 member states representing 65 percent of the bloc’s population, about 292 million people.

Germany, France, Italy, and Spain remain the decisive markets. France has already rejected the current system; several other governments have flagged speed-limit compliance as the main sticking point.

The safety case Tesla is putting in front of those governments is now public. On September 1, Tesla Europe said FSD Supervised was in use by more than 70,000 customers, covering over 1 million kilometers a day, and was 4.1 times less likely to be involved in a crash than manual driving across 100 million kilometers on EU public roads.

An earlier mid-year cut of the same fleet data, covering 65 million kilometers in five approved countries, put the collision advantage at 5.2 times, with zero highway collisions over 41.9 million kilometers. Tesla also reported far fewer automatic emergency braking events, harsh accelerations, and hard swerves than in comparable manual Tesla driving. Those figures are company-reported, not independently audited.

Tesla Full Self-Driving is taking over Europe: fourth country gets FSD approval

Advertisement
-

The public-health backdrop is harder to dispute. European countries recorded about 19,400 road deaths in 2025, or roughly 53 a day, most of them attributed to human error. FSD Supervised is not unsupervised autonomy; the driver remains legally responsible. But the software is already legal and in daily use across seven member states.

Until TCMV votes, the rest of the EU remains a patchwork: available in Prague and Amsterdam, locked behind review in Paris and Berlin. December is now the next chance to close that gap.

Continue Reading

News

SpaceX readies Starship Flight 14 for a historic journey into uncharted territory

SpaceX finished Starship’s Flight 14 rehearsal, clearing the way for its first orbital flight Monday.

Published

on

By

Sunrise at Starbase. Starship is stacked for opportunistic full-stack testing ahead of Flight 14 via SpaceX
Sunrise at Starbase. Starship is stacked for opportunistic full-stack testing ahead of Flight 14 via SpaceX

SpaceX has cleared one of the last hurdles before Starship’s first trip to orbit. The company posted on X Thursday afternoon that its launch rehearsal for Flight 14 was complete, keeping the mission on track for Monday, September 28. The launch window opens at 7:15 a.m. CT at Starbase, Texas, and runs for 75 minutes.

A wet dress rehearsal is essentially launch day without the launch. Crews fill Booster 21 and Ship 41 with thousands of tons of extremely cold propellant, run the countdown nearly to ignition, then drain everything back out. It lets engineers catch leaks or equipment problems before anything leaves the pad. SpaceX still needs a launch license from the FAA before the stack, which stands 407 feet tall, can fly.

Flight 14 matters because of where it is going. All 13 previous Starship flights followed a suborbital path, which works like throwing a ball extremely high and far: the vehicle reaches space, but it is always on a course that brings it back down within about an hour. This time, Ship 41 will perform a short engine firing called an orbital insertion burn roughly 25 minutes after liftoff, giving it enough speed to keep falling around Earth instead of back into it. SpaceX plans about six laps at an altitude near 275 kilometers (171 miles) over nearly 10 hours, as Teslarati detailed when the mission was first announced.


Getting into orbit also means Starship has to prove it can get back out. The ship must relight a single Raptor engine in space to slow down for reentry. SpaceX says it will only attempt the orbital insertion burn after flight controllers confirm the hardware needed for that return burn has enough backup, and its flight plan includes health checks that could shorten the mission to two or five orbits.

Flight 14 is also the first to put working satellites into service. Flight 13 carried 20 Starlink V3 satellites in July, but they came back down with the ship because that mission never reached orbit. This time, 26 V3 satellites are meant to stay up and join the constellation within a few weeks. Together they add about 26 terabits per second of network capacity, which SpaceX says is roughly 10 times what a single Falcon 9 launch of older V2 Mini satellites adds. Three of them carry cameras that will photograph Starship’s heat shield in orbit to check for tile damage before reentry.

Advertisement
-

The hardware has changed too. Ship 41 flies with extra fasteners on tiles in the most vulnerable areas, fixes for gaps where superheated plasma slipped behind tiles, and curved tiles designed to reduce heating between them. Two tiles recovered from Ship 40 will fly again, the first reuse of any part of a Starship heat shield. Booster 21 carries better engine filtering and new relight software after ice clogged three center engines on the previous booster, leaving only eight of 13 engines to restart for its landing burn.

Ship 41 is targeting a splashdown in the Pacific Ocean west of Chile, a new recovery zone after several Indian Ocean landings, while Booster 21 aims for the Gulf. Neither will be caught by the tower on this flight. Elon Musk said in August that a ship catch was likely “in a few months.”

Continue Reading

Elon Musk

Google just picked SpaceX for its first step into orbital AI

Google will launch its first Project Suncatcher AI satellite on SpaceX’s Transporter-18 rideshare next week.

Published

on

By

Google is about to put its own AI chips into orbit for the first time, and it is paying SpaceX to get them there.

The company said Thursday that the first in-orbit test of Project Suncatcher, its research effort to find out whether space can host large-scale AI computing, will fly next week on SpaceX’s Transporter-18 rideshare mission.

The satellite, called MVP, is about the size of a refrigerator and carries four of Google’s Tensor Processing Units, the same chips Google runs in its ground data centers. Google originally planned to launch two custom satellites in 2027, but chose to move faster by integrating its chips into a satellite.

MVP’s solar panels supply about one kilowatt of power, and Google will run Gemini models on the TPUs only in bursts of roughly 15 minutes before the chips shut down so the radiators can shed heat. In a blog post, Google said its Trillium TPUs survived vibration testing that mimicked sustained launch loads of up to 10g, with individual components seeing 50 to 100g, and handled a radiation dose greater than a five year mission would deliver.

SpaceX and Google mull massive partnership on Musk’s orbital data dream: report

Next week’s flight, slated for October 1, follows a relationship that became public in May, when Teslarati reported that Google was in talks with SpaceX for a launch deal tied to orbital data centers. Google also holds a stake of roughly 6% in SpaceX.

Advertisement
-

The two companies are chasing the same idea from very different starting points. SpaceX’s own orbital compute program is built around the AI1 satellite, a roughly 70 meter structure derived from Starlink V3 hardware that is designed for 150 kW of peak compute, about 150 times the power MVP will draw. Elon Musk has brushed off concerns about crowding orbit with those satellites, and SpaceX is building its Gigasat factory in Bastrop, Texas, to produce them, targeting an annualized rate of about 1 GW of space compute by the end of 2027.

Musk also posted on X on Thursday that “the amount of compute in space will obviously round up to 100% of all compute.”

Google has been more cautious in public. Its research estimates that launch prices need to fall below about $200 per kilogram before an orbital data center can compete with a ground facility on energy cost, a threshold the company believes could be reached around the mid 2030s. The Suncatcher team has said it expects the effort to remain a project rather than a product for years, which leaves the first real test of its hardware riding on a rocket from the company with the most aggressive timeline in the field.

Continue Reading