Using Ag Data to Win Your Case

Farm Journal’s recent article featured one of our long-fought cases against the Indiana Department of Natural Resources (DNR) for crop damage (Damned by Data: State Destroys Farmer’s Yield, Pays $810,000 in Damages). As explained in the article, our case depended on explaining periodic and partial flooding of farm fields over a course of years to the court. Fortunately, our client, Charlie Houin, had been collecting good data about the Houin family farm fields for years. And this helped us win our case.

The Houin case involved a lake dam that had been mismanaged by the Indiana DNR. About a dozen years ago, the DNR established trigger levels for when to open and close the dam, but these trigger levels raised the summer lake level significantly. This was a big problem, as farm field drainage tile in the area was designed for the previously established, lower (and correct) lake level. Raising the lake level made this field tile ineffective. Fields would flood when they could not drain after significant rainfall events, leaving standing water for days.

Before the advent of precision ag and data tools, proving intermittent flooding damages like this would have been very difficult. For example, a 100 acre cornfield might have 20 acres underwater for 10 growing days, resulting in little yield, but if the rest of the field yielded 240 bushels per acre, the average for the entire field would have been 192 bu./acre. ((80 acres X 240 bu./acre) / 100 acres = 192 bu./acre). 192 bu/acre. does not necessarily appear as a significant loss for a field.

Using ag data told a different story. With harvesting data, the court could see exactly where the flooded areas of the field were and how flooding affects yields. Below (left) is an example, showing the lower yields in red and better yields in green, and few areas with no yield. On the right, the same data is overlaid with soil type and averaged to show that flooding, not soil type, was the reason for the drag in yield in parts of the field.

We also used drone photos to ground-truth the data. Here is a photo of the same field on the same year about halfway through the summer, showing the flooded areas as light green. The combine yield data confirmed the impact that was obvious from the sky.

Our case was complex because crop damage and yield loss were highly variable across different parts of the affected fields. One part of the field would yield well, while another part would yield little or nothing. Without ag data, telling this story would have been difficult, if not impossible. We also used comparison data from nearby fields that did not drain into the lake watershed to show what the yield would have been, but for the elevated lake level. Here is a chart presented to the court comparing affected and unaffected fields:

Ultimately, based upon the data and other evidence, the court agreed that raising the lake level impacted our client’s farming operation:

The data from the affected fields shows a reduced or no yield in many places when compared to the non—affected fields. The soil types in affected and non—affected fields were planted and fertilized the same (i.e., Ackerman soils received the same seed and chemical treatments). The different soil types did not explain the different yields between affected and non-affected fields. Instead, the yield difference is caused the dam mismanagement. Keeping the dam closed caused the water level at the lake to rise, which pushed water into the tile or prevented the tile from draining into the lake.

At trial, the court awarded our farmers $485,644 in crop loss and field tile damages. As explained in the Farm Journal story, the case went up on appeal, eventually returning to the trial court for further assessment of damages. The case was resolved two years after the trial for $810,000.

We may not think of ag data as having an evidentiary value in court, but I cannot imagine a case about crop damages without it.