A large fire department response was dispatched to the Village of Barrington Wastewater Treatment Plant, 302 Raymond Avenue in Barrington, for a chlorine leak Tuesday morning. | Photo: Nick Rusin

Numerous fire departments and a hazardous materials response team were sent to a chlorine leak at a wastewater treatment facility in Barrington Tuesday morning.

The Barrington Fire Department responded around 6:53 a.m. Tuesday to the Village of Barrington Wastewater Treatment Plant, 302 Raymond Avenue, for a report of a hazardous materials incident.

A chlorine leak was reported from a chlorine storage and was reported to be spreading at the treatment plant.

A large fire department response was dispatched to the Village of Barrington Wastewater Treatment Plant, 302 Raymond Avenue in Barrington, for a chlorine leak Tuesday morning. | Photo: Max Weingardt

Fire crews arrived at the scene and confirmed the leak and requested an upgrade response for additional resources.

The incident was again upgraded through the Mutual Aid Box Alarm System (MABAS) to the box alarm level.

A large fire department response was dispatched to the Village of Barrington Wastewater Treatment Plant, 302 Raymond Avenue in Barrington, for a chlorine leak Tuesday morning. | Photo: Nick Rusin

The upgrade brought numerous fire departments to the scene along with the MABAS 4 and 5 hazardous materials response team.

Fire officials described the spill as a “small leak” and said there was no threat to the public.

[Suggested Article]  Man with extensive criminal history arrested for repeatedly punching woman in public at Crystal Lake festival

“The fire department is working alongside a hazardous materials response team to resolve the situation safely,” fire officials said.

A large fire department response was dispatched to the Village of Barrington Wastewater Treatment Plant, 302 Raymond Avenue in Barrington, for a chlorine leak Tuesday morning. | Photo: Max Weingardt

The leak was stopped by 8:55 a.m. and fire crews were decontaminating the area.

By 9:35 a.m., the issue was “fully repaired” and everything was back to normal operations.