Chemical leak forces evacuations in Ohio city of Toledo
Summarised from 2 outlets · Updated 21 Oct, 12:44 · Archive
A chemical leak in Toledo, Ohio, forced evacuations within a 1-mile radius and shelter-in-place orders up to 3 miles away.
A chemical leak at a location on Progress Avenue in northern Toledo, Ohio, forced residents to evacuate on Tuesday night. Evacuation orders were issued around 10:50 p.m. for individuals within a 1-mile radius of the release point, while those in a surrounding 3-mile area were instructed to shelter in place indoors, close windows and doors, and turn off ventilation systems drawing in outside air.
Authorities have not identified the specific chemical involved in what they described as an 'ongoing' release. The chemical can irritate the skin, eyes, nose and mouth, and overexposure can trigger dizziness, headaches, fatigue, vomiting and nausea. A thick fog and haze obscured sightlines across Toledo, and local news outlets noted a strong plastic-like scent in the air.
Directory records list a steel tube and pipe manufacturer at the Progress Avenue address, though fire officials did not identify a specific company responsible for the leak. No injuries have been reported. Toledo public schools were closed on Wednesday as authorities continued to monitor the situation.

How it is being reported
- Chemical leak in Toledo forces evacuations, shelter-in-placeA massive chemical leak in Toledo, Ohio, is forcing some people out of their homes while others have been told to shelter in place.CBS News · 21 Oct, 12:31
- Toxic chemical leak sparks mass evacuation as mysterious haze blankets Ohio citySome Ohio residents have been ordered to evacuate because of the release of a chemical that can cause burning of the eyes, nose, mouth and skinIndependent World · 21 Oct, 12:22
In this story: Toledo · Ohio · Progress Avenue · Toledo Fire & Rescue Department
This summary was written by AI from the headlines and standfirsts above, and states as fact only what at least two outlets report. How we use AI · Report a problem
Comments (0)