Digital Harvest · USSC Case Study — UpdateDigital Harvest · USSC Case Study — UpdateIn April 2026, USSC found a mealybug new to the region on 102 of its fields. It's since been identified as pasture mealybug, a species already established in Florida, Louisiana, and Texas. By July, it was confirmed in 1,549 fields, 27.8% of the operation, about fifteen times the April count.
Three questions matter now. Is it still spreading on its own, or being carried between fields? What makes some fields more vulnerable than others? What can USSC still do about it?
This update works through all three, using the same approach as before: USSC's field records combined with Digital Harvest's satellite, weather, and location data. One idea below, that nearby grassland is feeding the outbreak, is a lead worth checking, not a proven cause.
Cane isn't the only host. This pest already lives in the grasses around the operation, and that land may be feeding new infestations into the cane.
This didn't spread from one place. It shows up in about 74 separate pockets, including a second area far to the north, the pattern of something carried in repeatedly, not growing outward on its own.
Where a field sits matters as much as anything else. Young cane on sandy soil is infested at about 60%. Mature cane on the most protective soil sits near 3%.
Pasture mealybug attacks grasses broadly, not just sugarcane. It's already established across Florida, Louisiana, and Texas, and confirmed in every county around this operation, mostly in pasture grasses rather than cane.
That matters because of how this pest survives. It lives mostly below the leaf canopy and underground, where it can go unnoticed for months, and it's known to travel on mowing equipment, vehicles, even clothing and boots.
The land on this operation's western and southwestern edge is one large, connected grass system, home to the same grasses the pest already uses elsewhere in Florida. The worst infections here sit close to that edge, and the separate northern outbreak sits next to a similar grass landscape of its own. Two infected areas, each beside its own grassland, is harder to write off as coincidence than one would be.
This is a lead, not a conclusion. It hasn't been tested formally, only observed on the map, and there are real reasons to hold it loosely:
Bottom line: a real possibility worth investigating, not yet a demonstrated cause.
A pest spreading on its own would form one connected mass. This doesn't. The infested fields break into about 74 small, separate groups, and 42% of them sit completely alone. That many disconnected pockets don't come from one spreading population.
Direction points the same way. The oldest, worst-hit fields sit to the west. The newest growth is to the east and north. But the wind blows the other way, toward the west-southwest. If crawlers were riding the wind, growth should follow it, not fight it. The more likely explanation is equipment and planting material moving between fields, not wind.
The clearest sign this outgrew a contained event: a second outbreak about 70 kilometers to the north, behaving like its own separate case, not an extension of the first.
Crop age and soil each raise or lower risk on their own, and they combine rather than repeat each other. Newly planted cane is infested at nearly twice the overall rate, and that risk drops steadily as cane ages.
Soil now tells a different story than it did in April, when only a handful of fields per soil type were confirmed. With over five thousand fields confirmed now, the order flips: sand is the highest-risk soil, and Warm Muck, not Cold Muck, is the most protective. That's not a contradiction, it's a correction more data made possible, and worth saying plainly rather than quietly changing the number.
Combine the two factors and you get the widest range yet: newly planted cane on sand is infested at about 60%. Mature cane on Warm Muck sits near 3%. That range, not any single number, is what should guide where scouting and protection go next.
This is no longer a contained introduction. It's a regional problem playing out field by field.
A pest already established across the region kept arriving on the operation, most likely carried by equipment and planting material, not by spreading on its own. It hit hardest where cane was young and soil gave no protection. The land bordering the operation is a plausible extra source, though not yet proven.
At this scale, managing it at the edges alone won't work anymore.
A few things worth keeping in mind:
These are strong, tested associations, not proof of cause, at this larger scale just as they were at the smaller one.
In April, the first analysis answered one question: how bad was this outbreak, and where should USSC look first? That analysis was not a one-off. The same data and the same infrastructure carried straight into this update, three months later and fifteen times larger, without starting over from scratch.
The result: the same combination of USSC's records and Digital Harvest's satellite, weather, and spatial analysis that first found a contained problem has now tracked it becoming a regional one, corrected an early misread on soil, and pointed to a new lead worth checking. That's the point of building this kind of infrastructure: not a single snapshot, but a record that gets sharper and more useful every time it's used.