Fire in battery unit during commissioning at Victorian Big Battery, Moorabool
July 2021Published 1 May 2026Responsible editor: Chief Editor
- Where
- Victorian Big Battery, Moorabool, near Geelong, Victoria, Australia
- Operator
- Neoen
- What
- Fire in one containerised battery unit during commissioning
- Injuries
- None reported
- Cause
- Leak in liquid cooling system led to arcing and thermal runaway
Get the next one by email
Free alerts on battery storage incidents in Australia, and an email when EIR-0012 is updated. No account needed; unsubscribe in one click.
Confirm your email and every battery storage incident on the register arrives at once as a spreadsheet (CSV), free.
Get a free sample brief Three complete verified records and the incidents-per-GW table, by email within a minute.
We will also email you about the register's paid records and plans, at most once a week and three times in all. You can stop these at any time. By signing up you agree to the privacy policy.
Companies named in the reporting of this entry (being named is not a finding of fault): Neoen, Tesla
What happened
In July 2021, during initial testing and commissioning of the Victorian Big Battery, a large grid-scale lithium-ion battery energy storage facility at Moorabool, near Geelong, Victoria, Australia, operated and owned by Neoen with battery units manufactured and integrated by Tesla, a fire began within one containerised battery unit. Smoke was first observed mid-morning. The fire spread to one adjacent unit before further propagation was halted. The affected units were allowed to burn out, consistent with manufacturer emergency response guidance, while surrounding equipment was protected, and the site was not declared under control until 2 August 2021, three days after the fire began.
No injuries were reported. State fire services attended in strength, with reports of more than 30 appliances and around 150 firefighters on scene. A 25 metre perimeter was established and hose lines were used for exposure protection of adjacent battery units and transformers. Two of the site's 212 Megapack units were destroyed. An independent technical investigation was commissioned and its findings were published.
Contributing factors
According to the published independent technical findings, the most likely root cause was a leak within the liquid cooling system of the first unit, which led to arcing in the power electronics associated with the battery modules and then to thermal runaway and fire. The report identified two significant contributory factors. First, the SCADA system required around 24 hours to establish full telemetry mapping for newly installed units, and the affected unit had been in service for only about 13 hours before being switched off at its keylock switch on the morning of the fire, so real-time monitoring data was not available to remote operators. Second, the keylock service-mode setting had disabled certain monitoring and protection functions that could otherwise have detected the fault. The report indicated that, absent these factors, the initial cooling system fault may have been detected and interrupted before it escalated.
Lessons learned
- Liquid cooling system leaks in Megapack units can cause arcing in power electronics, so pressure test and inspect every circuit after installation before energisation.
- SCADA mapping latency of around 24 hours during commissioning leaves new units unmonitored, so do not energise until full telemetry and alarms are verified active.
- Keylock service mode can disable essential protection functions, so review arrangements to keep alarms active and avoid unmonitored periods.
More lessons on maintenance, inspection and ageing assets, detection and monitoring, from every incident on the register.
Not yet known
- Exact downtime of the facility
- Cost of the damage and response
- Firmware changes applied to other units
This entry is updated when these are reported. Get an alert for the next one like it.
Published 2026-05-01. Written from public reporting. Descriptive, not investigative. See the data accuracy disclaimer.