Prohibits the purchase and use of glyphosate by certain entities
Idaho S.B.1064 authorizes state-supported cloud seeding, requires annual and monthly reporting, and grants liability immunity for state‑authorized projects.
Idaho S.B.1064 authorizes state-supported cloud seeding, requires annual and monthly reporting, and grants liability immunity for state‑authorized projects.
Note: the materials you provided contain multiple, conflicting documents that appear to describe different measures with the same bill number (including an Idaho cloud‑seeding bill, a Massachusetts “eliminate disparate impact” bill, and an unrelated title about glyphosate). This summary focuses on the most detailed and internally consistent text in the packet — Idaho Senate Bill No. 1064 (2025) — which governs cloud seeding. If you intended a different S.1064 (Massachusetts or the glyphosate measure), tell me and I will summarize that instead.
Summary — Idaho S.B. 1064 (2025) — Cloud Seeding: authorization, reporting, funding, and liability
Purpose and intent
- Clarifies and expands the statutory framework for cloud seeding in Idaho, with the stated goals of augmenting state water supplies (snowpack/rainfall), protecting water‑dependent uses, improving transparency, and supporting continued research and responsible program expansion.
Key provisions
- Revisions to 42‑4301 (legislative findings and definitions):
- Reaffirms that cloud seeding can be in the public interest for drought mitigation, water rights protection, water quality, recreation, and fish/wildlife.
- Revises/clarifies the definition of “cloud seeding” (introducing particles/droplets to influence precipitation, hail mitigation, fog dispersal, preventing frost in some versions).
- Excludes fog suppression and frost prevention for orchard/crop protection from the chapter’s coverage (explicit exclusion appears in amended versions).
- New section 42‑4302 — Definitions:
- “Board” = Idaho Water Resource Board (IWRB).
- “Cloud seeding” defined (variants include prevention of frost, hail mitigation, fog dispersal).
- Later amendments also define “crops” and “orchard” for exclusion purposes.
- New section 42‑4303 — Authorization and reporting:
- IWRB may authorize, sponsor, develop, and contract for local or statewide cloud seeding programs and related research.
- Annual public report required and must be posted on the board’s website and presented at public meetings. Required report content includes:
- Operational data (dates, locations, methods; some drafts add generator coordinates and maps).
- Science related to environmental impacts (some versions call for detailed environmental impact assessments).
- Public engagement efforts and feedback.
- Effectiveness metrics (e.g., measured increases in snowpack or reservoir levels).
- Operator reporting: operators must submit monthly operational reports to the board within a specified period after the start of each operational period — earlier drafts specified 30 days; later amendments and engrossments set 45 days. Reports must include locations, ground generators/infrastructure, flight paths (FAA‑approved where applicable), dates/times (UTC in some drafts), suspension periods, observed storm conditions, types/amounts of materials used, and methods.
- Independent operators (non‑state projects) must comply with the same authorization and reporting requirements.
- Explicit exclusion: cloud seeding performed solely to protect orchards/crops (frost prevention, etc.) is excluded from the chapter.
- New section 42‑4304 — Use of state funds and liability:
- State funds may be expended on cloud seeding only in basins where the board finds existing supplies insufficient to support water rights, water quality, recreation, or fish/wildlife — and any water created is distributed under the prior appropriation doctrine.
- Projects funded or authorized by the state/board are granted statutory immunity from claims of liability (including trespass or nuisance) and do not require state or local permits.
Fiscal impact
- Fiscal note (attached) estimates no additional General Fund resources required — the IWRB already oversees cloud seeding and maintains related records.
Who is affected
- Idaho Water Resource Board: new reporting, transparency, and authorization duties.
- Cloud seeding operators and contractors (public and private): new monthly reporting and compliance obligations.
- Independent, privately conducted cloud‑seeding entities: brought under the same reporting/authorization regime.
- Water users and stakeholders in targeted basins: potential benefit from augmented water supplies, plus greater access to program data and public meetings.
- Local governments: explicit language stating state‑authorized projects do not require local permits.
- Potential plaintiffs: statutory liability shield limits ability to bring nuisance/trespass claims against state‑authorized projects.
Procedural / timeline aspects
- Bill declares an emergency and sets an effective date of July 1, 2025 (engrossed versions).
- Legislative actions in the packet indicate multiple committee referrals, amendments (including operator reporting timeline changed from 30 to 45 days), and passage steps in the Idaho legislature (Senate passage recorded 34–0–1 in one entry).
- Latest engrossed/amended language: reporting window and environmental reporting language as noted above.
Potential impacts and issues to watch
- Transparency: annual and monthly reporting increases public access to operational and environmental information.
- Scientific assessment: the bill requires presentation of environmental science and effectiveness metrics but leaves methods and standards unspecified — implementation choices will determine the usefulness of reports.
- Legal exposure: the liability shield narrows legal remedies for harms allegedly caused by state‑authorized cloud seeding.
- Funding limits: state funding restricted to basins with demonstrated insufficiency; distribution governed by prior appropriation (water rights) — could affect which projects receive state support.
- Compliance burden: private operators face new administrative requirements; enforcement mechanisms and penalties for noncompliance are not detailed in the text provided.
If you want: I can (1) produce a one‑page legislative memo with pros/cons and stakeholder lists; (2) produce a side‑by‑side comparison of the different drafts (30‑day vs 45‑day reporting, inclusion/exclusion language); or (3) summarize the other S.1064 texts (Massachusetts disparate‑impact bill or the glyphosate title) instead. Which would you prefer?
Compiled from official sources — confirm details with the bill’s official record.
Sign in to ask a question.