Des Moines County work session debates emergency‑response rules for wind, solar and battery projects

Jared Lasker, county land‑use staff, opened the panel discussion by saying the proposed Article 12 would require a developer to submit a project‑specific emergency response plan as part of any siting permit but that the current ordinance lacks detail on what those plans must include. "So today, we're gonna focus primarily on emergency response," Lasker said, outlining incident types and procedural elements the draft would require.

Why it matters: the proposed language aims to ensure local emergency responders can safely access and manage incidents at remote energy facilities — wind farms, solar arrays and battery storage sites — and that developers cover training, equipment and cleanup costs rather than leaving costs to local taxpayers or landowners.

The draft lists the incidents a plan must address, including natural disasters (lightning, hail, earthquakes, wildfires, tornadoes), fire or explosion, transmission/capacity failures, environmental or chemical releases and medical emergencies involving on‑site workers. Lasker told the room that plans must also include emergency contact information, defined access points from county roads, procedures for safe shutdown and restart, alarm testing, and notification protocols for response agencies.

Local fire and emergency officials urged operational specifics. "I think we really need to have a plan in place as far as where these landing zones are for the helicopters," said Justin Myers, the county's fire chief, who emphasized the need for designated Life Flight landing zones (LZs) to speed patient transport in remote areas. AES representatives said LZs are part of routine operations. "We regularly… work with Life Flight to acquire landing zones," an AES operations representative said, and the company outlined on‑site staffing plans, a remote operations center (ROC) that monitors turbines 24/7 and lease provisions addressing crop‑damage reimbursements for landowners when helicopters land on fields.

Training and equipment drew repeated attention. County emergency management cautioned that companies often provide startup training but that it becomes a "ghost town" afterward; participants urged annual, and in some cases semiannual or onboarding, training requirements to address staff churn and changing local capabilities. The draft requires developers to provide specialized training for fire departments and other response personnel and to pay for any specialized equipment identified in the plan.

Officials also debated fire‑suppression language and applicable codes. Burlington’s fire marshal warned the current wording — "each turbine shall be equipped with a fire suppression system" — is broad and could be interpreted inconsistently across turbine types. Staff and attendees discussed whether to cite NFPA standards or a specific section of the International Fire Code so that the requirement would be enforceable. Developers said many suppression systems are proprietary to turbine manufacturers and recommended aligning the ordinance with a realistic, industry‑applicable standard rather than a one‑size‑fits‑all mandate.

On enforcement and ownership, staff noted the ordinance's definitions apply the terms "owner" and "operator" to any subsequent owners, so obligations transfer on sale. County members referenced proposed civil infraction fines ("the first day's violation is $750; each subsequent day is another thousand dollars") as an enforcement tool, and some participants urged stronger operating‑permit or renewal mechanisms to ensure ongoing compliance rather than relying solely on monetary fines.

Responding to damage and decommissioning, staff proposed a two‑tier approach: immediate mitigation of imminent public‑safety hazards within 30 days — for example, securing a collapsed or unstable turbine and stopping airborne debris — and a longer period (up to a year) to reactivate, decommission or remove foundations and complete environmental remediation. Developers said they could remove imminent hazards quickly (taking towers down and cutting components on participating property) but that full cleanup timelines for foundations and contaminated soil vary with circumstance and may require DNR involvement.

Several residents raised environmental and liability concerns, asking who would certify cleanups and whether landowners could be left responsible for contamination. Participants noted existing hazmat reporting thresholds and state DNR processes (for spills over 55 gallons, etc.) and reiterated that developer contracts typically include clauses to protect landowners, but attendees asked that the ordinance explicitly require developers to assume cleanup costs and clarify which agencies (local fire, county emergency management and the Iowa DNR) would be notified and responsible for oversight.

The work session closed with staff saying wildlife monitoring and mitigation language would be the focus of the next meeting. No formal vote occurred; staff will draft revisions to the Article 12 language to address code citations, training cadence, LZ procedures, fee schedules for emergency services and the cleanup/decommissioning timeline, and bring those revisions to a future session.