How cloud seeding mission reporting works

Andrew Verda

By Andrew Verda, Founder & CEO, Alto Cirra

September 23, 2026 · 7 min read

Cloud seeding is an activity whose effects are hard to see directly in any single storm. That makes the record the program produces central rather than administrative. A mission report exists so a regulator can verify what was done, a funder can audit what they paid for, and an analyst can evaluate the season against something other than recollection.

Who reads the report

  • Regulators. Weather modification activity in the United States carries state-level permitting or registration requirements and federal reporting obligations. Reporting is a condition of operating, not a courtesy.
  • Funders. Water districts, resorts, and other sponsors are typically spending public or member money and need a defensible account of activity.
  • Evaluators. Any statistical or physical assessment of a program depends on an accurate record of what was seeded, when, where, and under which conditions.
  • The operator. The same data is what improves targeting next season.

What a mission record contains

  • Justification. The forecast and observational basis for calling the storm seedable, and the criteria applied.
  • Authorization. The airspace coordination and approvals in effect for the operation.
  • Flight track. Time-stamped position and altitude for the whole sortie.
  • Dispersal log. Material type, quantity released, and the exact times and locations of release — reconciled against what was loaded.
  • Atmospheric observations. In-situ measurements along the track plus the supporting radar, satellite, and sounding data used in the decision.
  • Decisions and deviations. Pattern changes, early termination, aborts, and the reason for each.
  • No-fly records. Storms evaluated and declined, with the reason. A season is not interpretable without them.

Why drone operations change the record

An uncrewed aircraft is instrumented by default. Position, altitude, and atmospheric parameters are logged continuously and recovered as data rather than reconstructed from notes. The dispersal log is tied to the same timebase as the flight track, so "material was released into a supercooled layer over this catchment at this time" becomes a statement with records behind it rather than an inference.

That does not prove an effect on precipitation — attribution in any single storm remains genuinely difficult — but it removes ambiguity about the operation itself, which is the part a program can actually be held to.

What reporting cannot do

A report documents activity and conditions. It does not, on its own, establish how much additional precipitation resulted. Effect estimates come from statistical designs over many events and seasons, physical measurement studies, or trace-chemistry work — and they carry uncertainty. Any operator presenting a single storm as proof of a specific percentage increase is overstating what the method supports.

The useful framing for a sponsor is: rigorous records of what was done, honest accounting of conditions, and multi-season evaluation against published literature rather than in-house claims. More on how sponsors should scope this in cloud seeding for water districts and on cost structure in what cloud seeding costs.

Talk to Alto Cirra

If you manage a watershed, a resort, or a water supply portfolio and want to understand whether drone-based cloud seeding fits your conditions, get in touch.