Connect with us

News

A Tesla Megapack caught fire last July in Australia — We now know what happened

Credit: @7NewsMelbourne/Twitter

Published

on

Last July, a Tesla Megapack in the 300MW/450MWh Victoria Big Battery caught fire while it was being tested. The fire spread to another battery, resulting in two Megapacks in the installation being destroyed. An investigation into the incident was promptly initiated a few days later. 

The results of the investigation have now been made public. According to a technical report written by experts at Fisher Engineering and the Energy Safety Response Group (ESRG), the Victoria fire last July was caused by a liquid coolant leak, which caused arcing within the Megapack’s battery modules. 

“The most likely root cause of the fire was a leak within the liquid cooling system of MP-1 causing arcing in the power electronics of the Megapack’s battery modules. This resulted in heating of the battery module’s lithium-ion cells that led to a propagating thermal runaway event and the fire,” the report read. 

Personnel in the area initially noticed smoke emanating from one Megapack battery at around 10 a.m. on July 30. Emergency crews were called, and once they arrived, a perimeter was established around the battery storage unit. Water was applied to the Megapack, but the flames spread to a neighboring battery unit anyway. 

Fortunately, the spread of the blaze stopped there, and the fire burned itself out over a six-hour period. The results of the incident were in line with Tesla’s guidance for such incidents, which advises emergency responders to allow Megapacks that have caught fire to burn themselves out. The incident was ultimately dubbed a “safe failure,” according to a report from Energy Storage News. 

It should be noted that the Megapack that started the fire had been manually disconnected from a number of monitoring, control, and data collection systems because it was undergoing testing at the time of the incident. Wind speeds at the time also contributed to the spread of the blaze. 

Advertisement
-

Tesla, for its part, has implemented a number of procedural, firmware, and hardware mitigations to avoid similar incidents from happening in the future. These include improved coolant system inspections during Megapack assembly, additional alarms to the coolant system’s telemetry data to identify and respond to a possible coolant leak, and the installation of newly designed, thermally insulated steel vent shields within the thermal roof of all Megapacks, among others. 

The results of the Victoria Megapack fire’s investigation could be viewed below. 

VBB Fire Independent Report of Technical Findings by Simon Alvarez on Scribd

Don’t hesitate to contact us with news tips. Just send a message to simon@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

SpaceX just locked up a NASA record no other U.S. spacecraft can touch

SpaceX’s Crew-13 Dragon reached the ISS in under eight hours, and NASA confirmed a record.

Published

on

By

spacex-dragon-axiom-ax-4-mission-iss

SpaceX now owns every spot on the list of the five fastest trips a U.S. spacecraft has ever made to the International Space Station, and its newest entry beat the old mark by more than four hours.

Crew Dragon Grace docked to the forward port of the station’s Harmony module at 7:05 p.m. ET on October 1, just 7 hours and 55 minutes after lifting off from Space Launch Complex 40 at Cape Canaveral. NASA confirmed the milestone in a space station blog update, writing that the flight “marked the fastest launch‑to‑docking of a U.S. spacecraft in the history of the International Space Station.”

The previous U.S. record also belonged to Dragon. SpaceX’s uncrewed CRS-31 cargo mission reached the station in a little over 12 hours in November 2024. The fastest crewed trip before last week was Crew-11, which took 14 hours and 43 minutes in August 2025, according to Space.com.

A post that Elon Musk reposted on Monday filled out the rest of the ranking. Behind Crew-13, CRS-31 and Crew-11 sit Axiom’s Ax-2 mission at 15 hours and 35 minutes and NASA’s Crew-4 at 15 hours and 44 minutes. All five flew on Dragon.

SpaceX turned a heralding moment for Starship into its greatest

Crew-13 carried NASA astronauts Jessica Watkins and Luke Delaney, Canadian Space Agency astronaut Joshua Kutryk, and Roscosmos cosmonaut Sergey Teteryatnikov. NASA had projected a docking around 8 p.m. ET, as Teslarati reported the day before launch, and Dragon arrived nearly an hour early. Our launch day coverage noted that the flight was lined up to be the quickest Crew Dragon transit yet.

The speed came from timing more than hardware. SpaceX’s Julianna Scheiman said the station “was in an opportune spot in space,” which let Dragon start closing the gap almost immediately after reaching orbit. “This is close to the fastest it could be,” she added. Most Crew Dragon flights still take close to a day, using a series of Draco thruster burns to raise and phase their orbit before arrival.

Dragon’s next job at the station is a departure. NASA said Monday it is targeting 8:05 a.m. ET on Wednesday, October 7, for Crew-12 to undock, setting up a splashdown off the coast of California around 11:34 a.m. on Thursday. Clearing that port makes room for CRS-35, a cargo Dragon carrying the final set of iROSA solar arrays.

Dragon remains NASA’s only operational ride to the station while Boeing’s Starliner stays grounded, and the agency recently added Crew-15, Crew-16 and Crew-17 to SpaceX’s contract in a $946 million modification.

Continue Reading

Elon Musk

Elon Musk teases TSMC as potential Terafab partner

Published

on

SpaceX Terafab rendering
SpaceX Terafab rendering

Elon Musk has acknowledged that early discussions with Taiwan Semiconductor Manufacturing Company (TSMC) could bring the company into his ambitious Terafab semiconductor project, signaling a possible partnership with the world’s leading contract chipmaker.

Musk confirmed that early talks are underway, but as of right now, they are “just discussions.” There is no confirmation of a deal nor dismissal of the possibility of one, leaving open the prospect of one of the largest advanced-chip collaborations under discussion in the U.S.

The report that speculated on potential discussions between Terafab and TSMC comes from Tim Culpan, who outlined a few ways the collaboration could operate. One is TSMC using the project as an “anchor customer” for future facilities in Texas, potentially contributing process expertise, operational know-how, or capacity while Terafab provides capital, long-term purchase commitments, or both.

Tesla and SpaceX jointly developed the Terafab project, with Intel already participating on the tech side. Elon Musk announced the project in March, and it intends to produce more than one terawatt of AI compute capacity annually once fully built.

Elon Musk’s Terafab project locks up massive new partner

Company statements place the first phase at approximately $16.8 billion in cost, with later filings pointing to a total that could reach well into the tens of billions across multiple stages.

Intel joined the effort in April 2026 and is expected to supply its 14A manufacturing process for the full-scale plant.

Musk has said existing suppliers, including Samsung and TSMC, remain important for near-term needs; Tesla already has production arrangements with Samsung for AI5 and AI6 chips, but that future demand from Optimus robots, Cybercab vehicles, and planned space-based data centers will eventually exceed what the global industry can currently deliver.

Terafab is positioned as the long-term answer to that projected shortfall, and Tesla did something similar during COVID to avoid a chip shortage. This is just a much larger-scale solution.

If the partnership were to materialize, it would add TSMC’s industry-leading strategies to a project that already combines Tesla’s and SpaceX’s capital and offtake with Intel’s process technology. For now, the only public confirmation is Musk’s brief acknowledgement that conversations are occurring.

Continue Reading

News

Tesla reveals early Robotaxi charging strategy, showing scrappy DNA

Published

on

Credit: Tesla

Tesla’s early strategy for charging units operating within its Robotaxi fleet reveals that the company surely has not lost any of that scrappy DNA that took it from an unlikely success story to the most valuable carmaker in the world.

An observer at a Tesla Supercharger in Austin spotted ten total Robotaxi vehicles arrive: one Cybercab and nine Model Y units. A Tesla employee was waiting at the lot and allowed each unit to park itself; every car that arrived had nobody in it.

Tesla wins FCC approval for wireless Cybercab charging system

The Tesla employee would walk around and plug each car in, adjusting the parking if needed:

It’s a very interesting strategy, but extremely understandable at this early point in the Robotaxi program. It’s only been out for about 15 months, and Cybercab just entered the fleet in early September.

On top of that, Tesla is still working tirelessly on its wireless charging apparatus, and a new patent was just published regarding that product last week.

However, this is just another example of how Tesla still has plenty of that scrappy DNA leftover from the “production hell” days, when CEO Elon Musk slept on the floor of the factory, employees were working crazy hours, Tesla was building Sprung Structures to build cars in, and the company was tiptoeing on the brink of bankruptcy.

For now, Tesla is utilizing a simple system for recharging its ride-hailing vehicles, and that is a Tesla employee doing it manually until another solution presents itself. Sure, it’s not the most high-tech thing, and it certainly is not what people might have expected at this point in time, but it works, and it’s keeping the entire suite running.

Continue Reading