The Conspiratory
Case File No. 2340-K● Reviewed · Debunked

Cloud seeding caused the deadly July 2025 flash floods in the Texas Hill Country

Where the evidence lands: Contradicted
That the deadly Texas Hill Country floods of 4 July 2025 were not a natural disaster but the result of deliberate weather modification, specifically that the cloud-seeding operation Rainmaker Technology conducted on 2 July generated, intensified, or triggered the rainfall that flooded the Guadalupe River, and that the resulting deaths are therefore the fault of a man-made weather-manipulation program rather than of nature.
First circulated
Within days of the 4 July 2025 flood, spreading rapidly online once Rainmaker Technology's earlier operation became public, and amplified by public figures who called for bans on weather modification
Era
2020s
Sources
9

Believed by: A large online audience in the days after the disaster, boosted into mainstream politics when a sitting member of Congress said she would introduce a bill to ban cloud seeding and weather modification, and echoed by commentators who have blamed cloud seeding after other floods in Dubai, the 2025 California wildfires, and the 2024 hurricanes

The full story

What actually happened

Begin with the record, because the record is not in dispute and it is the ground everything else stands on. In the dark early hours of 4 July 2025, slow-moving thunderstorms parked themselves over the watershed of the Guadalupe River in the Texas Hill Country and unloaded many inches of rain in a few hours. The river rose with terrifying speed, about 26 feet in roughly 45 minutesnear Kerrville, higher than a two-story building, sweeping away vehicles, cabins, and a riverside girls' summer camp. More than a hundred people were killed, most of them in Kerr County. Among the dead were young campers. It was one of the deadliest inland flash floods in modern Texas history.

The meteorology is well understood. The National Weather Service attributed the rainfall to the remnants of Tropical Storm Barry, which drifted inland and stalled, feeding on an atmosphere carrying near-record moisture. The terrain did the rest. This part of Texas is known as Flash Flood Alley: its thin soils, steep limestone hills, and narrow valleys turn heavy rain into fast, violent floods, and the region carries some of the highest flash-flood risk in the country. The danger had been flagged in advance.

There is a second documented fact, and it matters that it is true. Two days earlier, on 2 July, a small California company called Rainmaker Technology had conducted a brief cloud-seeding operation near Runge, in south-central Texas, roughly 150 miles south of where the worst flooding would later occur. The company was open about it. What happened next was that these two true facts, a real flood and a real seeding operation, were fused into a false third one: that the second had caused the first.

The case for it

The case that it was engineered

Set the facts down in a certain order and the accusation almost assembles itself. A company had been in the sky over Texas, deliberately trying to make it rain, just two daysbefore the deadliest rain in years. The company's name was known, its operation was confirmed, and its own founder acknowledged the flight. To a grieving public, that sequence looked less like coincidence than like cause and effect.

The technology is not science fiction, which is what gives the claim its grip. Cloud seeding is a real, documented practice, in use for decades, in which operators disperse particles such as silver iodide to encourage clouds to release more precipitation. Governments and private firms really do it. If people can reach into a cloud and pull more rain from it, the reasoning goes, then perhaps they pulled far too much, and a company paid to make rain in a drought made a deluge instead.

A company was paid to make it rain, and days later it rained catastrophically. To a public searching for someone to hold responsible, that sequence felt like an answer.

The claim then climbed from social feeds into public life. A member of Congress announced she would introduce a bill to ban cloud seeding and other weather modification, citing a recently passed Florida law that criminalizes some geoengineering. When lawmakers respond to a disaster by moving to outlaw the suspected cause, the suspicion picks up a borrowed authority. That is the honest shape of the case: a real technology, a real operation, real proximity in time, and real grief looking for an author. What the case never supplies is a mechanism, and that is where it has to be tested rather than assumed.

What the evidence shows

What cloud seeding can and cannot do

The claim collapses at the first physical question: how much rain can seeding actually add? The answer, from the researchers who study it, is: a little, sometimes, under the right conditions. Seeding does not create clouds and cannot manufacture water. It can only coax somewhat more precipitation from clouds that are already poised to rain, and the added amount is estimated at perhaps 10 to 20 percent at the very most, over a small area, for a short time. On many attempts the measurable effect is close to nothing.

Hold that next to the scale of the disaster. A flash flood that lifts a river more than two stories in under an hour represents an almost unimaginable volume of water, the sort of total that meteorologists measured in the trillions of gallons across the affected basins. Nudging an existing cloud by a fraction is simply not in the same universe as producing that. As Texas broadcast meteorologists put it bluntly, seeding cannot dump that kind of water, and it cannot conjure the storm system that carried it. The rainfall came from a saturated atmosphere and a stalled tropical remnant, forces vastly beyond anything a seeding aircraft can touch.

This is the same wall the broader weather-control theory keeps running into. The gap between what people can really do to the weather (small, local, brief) and what they are accused of doing (creating or steering a catastrophe) is not a gap of secrecy or hidden hardware. It is a gap of raw scale, many orders of magnitude wide, and no amount of suspicion narrows it.

What the evidence shows

The geography and the clock

Even granting seeding far more power than it has, the specific operation still cannot be the culprit, for reasons of distance and time that do not require any physics to see. The seeding took place near Runge, about 150 miles south of the worst flooding in Kerr County. Rain that fell from two small clouds near Runge is not rain that fell on the Guadalupe River watershed. The two are separated by a large stretch of Texas.

The clock is just as unforgiving. The seeding happened on the afternoon of 2 July. The flood came in the early hours of 4 July. In between, the two seeded clouds had dissipated within hours, long gone before the flood-producing system arrived. Clouds do not linger for two days and then reconstitute 150 miles away into a multi-day deluge. There is no physical thread connecting the operation to the disaster, only the accident of their falling close together on a calendar.

It is worth adding what the company itself did, not to defend it but because the record is part of the story: Rainmaker's meteorologist noticed the Gulf moisture flowing in and the firm suspended its operations before the storm. Far from cranking up rain into a saturated sky, the operator stood down. A recently retired National Weather Service meteorologist summarized the whole question in one line, saying there is zero science correlating the seeding with the flood. Essentially all of the rain that fell was natural.

Why people believe

Why the flood needed a villain

If the physical case is this weak, the more human question is why the claim spread so fast and stuck so hard. The answer has little to do with silver iodide and much to do with what a sudden mass-casualty disaster does to the people left behind.

A flood that kills more than a hundred people in a few dark hours, children among them, is almost unbearable to file under chance. Randomness gives grief nothing to push against. A human operation gives it a target, a name, and the buried, desperate comfort that the catastrophe had an author and therefore might have been stopped. Blaming a company is, in a terrible way, easier than accepting that a river simply rose in the night. When communities were also asking painful and legitimate questions about whether warnings had been enough, a ready villain absorbed anger that had nowhere else to go.

The story also arrived pre-written. Cloud-seeding and weather-control accusations now follow nearly every major weather disaster, after floods in Dubai, after the 2025 California wildfires, after the 2024 hurricanes. Audiences met the Texas flood already fluent in the script, and the presence of a real seeding company nearby let them cast it instantly. Prominent figures, including elected officials, then amplified the claim, and a fringe suspicion rode their platforms into the mainstream. None of that makes the claim true. It makes it legible, which is not the same thing.

Where the evidence lands

Two facts are true at once, and the entire discipline of this case is refusing to melt them into a false third. It is true that Rainmaker Technology seeded two small clouds near Runge on 2 July. It is true that a catastrophic flood struck the Guadalupe River basin on 4 July. It is not true that the first caused the second, and the reasons are not close. Seeding can add at most a small fraction of rain to clouds already poised to rain; the operation was 150 miles away and two days earlier; the seeded clouds were gone within hours; and the flood came from the remnants of Tropical Storm Barry pouring into a saturated atmosphere over the most flash-flood-prone terrain in the country. On the rated claim, that weather modification caused these deaths, the verdict is debunked.

That verdict rests on unusually broad agreement. Broadcast meteorologists, the National Weather Service, and independent fact-checkers at Snopes and PolitiFact reached it separately, working from public reasoning rather than from any loyalty to a cloud-seeding firm. The claim also carries a real cost, which is the last thing worth saying plainly. Every hour spent litigating an imaginary weather weapon is an hour not spent on the questions that might actually save lives next time: whether the warnings were timely, whether people in a known flood zone could act on them, and how a region called Flash Flood Alley prepares for the next storm.

None of this treats the company or any person as a wrongdoer. A brief, lawful, and suspended seeding operation did not kill anyone, and the presumption of innocence runs in its favor as much as anyone's. The honest reading is the humane one: a river rose in the dark because the sky was full and the land is steep, and no one seeded that grief into being. Real weather modification is small. This flood was not.

Advertisement
Open questions

What's still unexplained

  • Were the flood warnings adequate, and did they reach people in time? This is the real accountability question the cloud-seeding story crowded out. Whether alerts, sirens, and overnight communications were sufficient in a known flash-flood zone, especially for camps and campgrounds along the river, is a serious and legitimate line of inquiry that has nothing to do with weather modification.
  • How lightly is the cloud-seeding industry actually regulated? Seeding did not cause this flood, but the fact that a private company can operate with modest oversight and sparse public reporting is a genuine governance issue. That thin transparency is part of why suspicion finds room to grow, even when a given operation is harmless.
  • Should seeding operators pause during high flash-flood risk regardless of effect? Rainmaker did suspend its flights, but the broader question of clear, enforceable protocols for when weather-modification work stops near vulnerable, flood-prone areas is reasonable to ask, not because a small operation is dangerous, but because public trust benefits from bright lines.
  • How much did climate and land-use factors sharpen the disaster? Separate from any conspiracy, meteorologists and planners continue to weigh how a warming, moisture-laden atmosphere and development in flood-prone valleys shape events like this one. Those are open scientific and policy questions, and they are where the honest debate belongs.

Point by point

The claim: A real cloud-seeding operation ran just before the flood, which is too big a coincidence to be innocent.

What the record shows: The operation was real, and it was tiny. On 2 July, Rainmaker seeded two small clouds near Runge with a small amount of silver iodide, and those clouds dissipated within hours. The company had already suspended flights after spotting incoming Gulf moisture. Coincidence in time is not causation: the Hill Country is one of the most flash-flood-prone regions in the country, and a major tropical-moisture event was independently forecast. A brief seeding of two clouds two days earlier and 150 miles away is a coincidence of timing, not a mechanism.

The claim: Cloud seeding makes it rain, so seeding before a rainstorm must have made the rain worse.

What the record shows: Seeding does not make rain from nothing; it can only coax somewhat more precipitation from clouds that are already primed to rain, and only by an estimated 10 to 20 percent at the upper end, over a small area. It cannot create a storm system, cannot add the vast volumes of water a flood requires, and cannot keep a system going for days. Meteorologists explaining the event stressed that seeding cannot dump the trillions of gallons that a flash flood of this size represents. The rainfall came from a saturated atmosphere and a stalled weather system, phenomena orders of magnitude beyond anything seeding can influence.

The claim: The seeded clouds fed the storm that flooded Kerr County.

What the record shows: The geography and timing rule this out. The seeding happened near Runge, roughly 150 miles south of the worst flooding in Kerr County, and about two days earlier, and the seeded clouds were gone within hours. The flood-producing rain fell from a separate, far larger system tied to the remnants of Tropical Storm Barry. There is no physical pathway by which two small, dissipated clouds could reconstitute into a multi-day deluge over a different region. As one meteorologist put it, essentially all of the rain in that event was natural.

The claim: The flood was unnaturally sudden and severe, a sign of human tampering.

What the record shows: Sudden and severe is exactly what this terrain produces on its own. The Texas Hill Country is called Flash Flood Alley because its thin soils, steep limestone hills, and narrow river valleys turn heavy rain into violent, fast-rising floods. The National Weather Service attributed the event to the remnants of Barry combining with record atmospheric moisture, and the flash-flood risk had been flagged in advance. A river rising dozens of feet in under an hour is a documented hazard of this landscape, not a signature of engineering.

The claim: Fact-checkers and the government dismissed the theory, which shows they are covering something up.

What the record shows: The people rejecting the claim include the ones with the least incentive to protect a cloud-seeding company: independent fact-checkers at Snopes and PolitiFact, broadcast meteorologists, and a retired National Weather Service forecaster with no stake in the firm. Their reasoning is public and testable, and it rests on the well-understood physics of seeding and the observed meteorology of the storm, not on assertion. Convergent debunking from unaffiliated experts is evidence against a cover-up, not for one.

Timeline

  1. 2025-07-02In the afternoon, Rainmaker Technology, a California-based cloud-seeding company, seeds two small clouds near Runge, in south-central Texas, roughly 150 miles south of Kerr County. The team disperses a small quantity of silver iodide (reported at about 70 grams) as part of a contracted effort to boost water supplies. Its meteorologist notes moisture flowing in from the Gulf, and the company suspends operations. The seeded clouds dissipate within hours.
  2. 2025-07-03The atmosphere over Central Texas grows extraordinarily moist as the remnants of Tropical Storm Barry drift inland and stall. Forecasters flag the flash-flood risk for the Hill Country, a region long nicknamed Flash Flood Alley for having some of the highest flash-flood risk in the United States.
  3. 2025-07-04In the pre-dawn hours, slow-moving storms unload many inches of rain over the Guadalupe River watershed. The river rises about 26 feet in roughly 45 minutes near Kerrville, sweeping away homes, vehicles, and a riverside girls' summer camp. More than a hundred people are killed, most of them in Kerr County. It becomes one of the deadliest inland flash floods in modern Texas history.
  4. 2025-07-05As the scale of the loss becomes clear, posts appear online linking the disaster to Rainmaker's earlier operation. The company's founder is named, its 2 July flight is cited, and the claim that the flood was engineered begins to spread across social platforms.
  5. 2025-07-06Rainmaker's chief executive, Augustus Doricko, publicly confirms the 2 July operation but states it had no bearing on the flood, explaining that the seeded clouds were small, far away, and had dissipated well before the rains. Meteorologists begin pushing back on the claim in interviews.
  6. 2025-07-07The claim reaches national politics. A member of Congress says she will introduce legislation to ban cloud seeding and other weather modification, pointing to a recently passed Florida law. PolitiFact publishes a fact-check the same day concluding that naturally occurring rainfall, not cloud seeding, caused the flooding.
  7. 2025-07-09Texas broadcast meteorologists and outlets including KSAT publish detailed explainers stating flatly that cloud seeding did not cause the flooding, walking through why the technique is far too weak and too localized to produce such an event.
  8. 2025-07-13NPR reports that the cloud-seeding claim is not only untrue but actively harmful, quoting a recently retired National Weather Service meteorologist who says there is zero science correlating the seeding with the flood, and noting that the false narrative distracts from real questions about warnings and preparedness.
Where the evidence lands

Contradicted. The documented record is not in dispute: a California company, Rainmaker Technology, did seed two small clouds near Runge, Texas, on 2 July 2025, and catastrophic flooding did strike the Guadalupe River basin around 150 miles away on 4 July. But the rated claim, that the seeding caused or worsened the flood, fails on the physics and the geography alike. Cloud seeding can only nudge rainfall out of clouds that already exist, by an estimated 10 to 20 percent at most, over a small area, for a few hours. It cannot conjure, sustain, or steer the multi-day tropical-moisture rainfall that dropped many inches on the Hill Country. Meteorologists, the National Weather Service, and independent fact-checkers reached the same conclusion. On the claim that weather modification caused these deaths, the verdict is debunked.

Sources

  1. 1.False claims link cloud seeding to deadly Texas floods, despite “zero evidence”, CBS News (2025)
  2. 2.The claim that cloud seeding caused the Texas floods is untrue, and actively harmful, NPR (2025)
  3. 3.Naturally occurring rainfall caused deadly Texas flooding, not a corporation's cloud seeding, PolitiFact (2025)
  4. 4.Debunking claim Rainmaker cloud seeding caused Texas floods, Snopes (2025)
  5. 5.Rumors 'cloud seeding' caused Texas floods are false, KUT (Austin's NPR Station) (2025)
  6. 6.Cloud seeding did NOT cause Hill Country flooding, KSAT (2025)
  7. 7.With Conspiracy Theories Circling over Cloud Seeding, Marjorie Taylor Greene Says She Plans to Hold a Hearing on Geoengineering, Scientific American (2025)
  8. 8.A West Texas Cloud Seeder Debunks Those Conspiracy Theories, Texas Monthly (2025)
  9. 9.July 2025 Central Texas floods, Wikipedia (2025)

Help us investigate

This is a living case file. If you spot an error or know evidence we missed, tell us, and weigh in on where you land.

Where do you land?

Cast your read on this one.

What did we miss?

Spotted an error or know a source worth chasing? Every note is read by a human.

Related case files

Advertisement
Written by The Conspiratory Editors · Published July 14, 2026. The Conspiratory lays out the claim, the case on every side, and the sources, so you can weigh it yourself. Spotted a stronger source? Corrections are welcome.