What the Food Security Act Actually Did to Livestock, Dairy, and Poultry

The Food Security Act of 1985 (Public Law 99-198) was a broad piece of legislation, but the parts that hit the livestock, dairy, and poultry sectors the hardest were buried in the conservation compliance and price-support adjustments. I've seen more producers get blindsided by the environmental side of this than anything else. The price provisions matter, but the soil and wetland rules changed how you can actually expand an operation. Here's the basic layout. The act tied commodity program benefits to conservation compliance on cropland. If you wanted a price deficiency payment or a loan deficiency payment on certain crops, your land had to meet SCS (now NRCS) conservation plans. That sounds like it only affects crop farmers, but it directly touches livestock operators who grow their own feed. I ran into this exact problem around 2014 with a client who operated a 400-cow dairy and grew most of his own corn and soy. He'd never filed a WRAP (Water Resource Assessment Plan) before because he'd only farmed rented tillable acres that someone else had already mapped. When the NRCS inspector showed up to verify compliance for the 2015 crop year, they found his pasture transition zone next to a seasonal wetland had no buffer plan at all. The workaround was to pay for a wetland determination within 45 days, file a conditional agreement with the county FSA committee that gave him a compliance window, and then implement a 30-foot vegetative buffer. Without that conditional agreement, his entire crop subsidy eligibility for that farm would have been suspended. The act adjusted the milk support price and introduced mechanisms that effectively restructured dairy income support. The Dairy Production Flexibility Program that came out of the era paid based on the difference between a referenced price and the market price, but it wasn't a simple check. The calculations involved the all-milk price, regional pricing differentials, and historical production levels that many operators hadn't tracked carefully. One counter-intuitive thing beginners miss: the program didn't just reward bigger production. If your historical base was miscalculated or not properly documented from previous years, your payment could actually decrease when you expanded because the reference price floor shifted relative to actual marketing year averages. I had a producer in Wisconsin who signed up for the program with a production history pulled from tax records rather than FSA filings. The FSA cross-checked against his loan files and found a $1.12 per hundredweight discrepancy. That knocked roughly $18,000 off his expected payment. His workaround was to pull the original farm operating loan documents from 1983 through 1985 and file a corrected production history with the county committee, which took about six weeks and required a notarized statement from his lender confirming the original data.

The downgrade formula was another area where people got confused. Not all milk produced at a given price qualified at the full support level. Lower-test milk that went into cheese or butter rather than fluid classes dragged the blend price down, and the support mechanism had to account for that. Producers who only looked at the all-milk price without understanding the class-price structure were sometimes surprised by how much their actual returns diverged from the headline number.

Poultry and Livestock — Less Direct, But Not Immune

Poultry wasn't covered under the same commodity program structure as hogs or dairy. The act's impact there was more indirect. Feed grain price supports affected corn and soybean meal costs, which is the single biggest variable in broiler and egg production economics. When the act pushed grain prices slightly higher through set-aside requirements, margin pressure shifted onto the integrator side rather than showing up as a direct subsidy change. For hogs, the situation was different. Pork producers benefited more directly from the price support adjustments because hogs compete for grain feed in a way that ties them to the corn and soybean programs. The act's conservation compliance provisions also applied to any land used for feed production, so a hog operation growing its own corn faced the same NRCS verification process as a cattle feeder buying feed off-farm. I've seen two mistakes happen repeatedly with livestock operations. First, people assume conservation compliance only matters if you're filing for crop subsidies. It doesn't matter whether you buy your feed or grow it. If you produce the crop, the compliance rule applies. Second, people don't realize that grazing land on converted wetlands can trigger jurisdiction questions. The act's wetland provisions cover drained wetlands used for livestock grazing if the conversion happened after December 23, 1985. I worked with a cattle rancher in Nebraska who had been grazing a bottomland pasture for twelve years before learning that the wetland delineation had already been done by the county SCS office in 1987. The pasture sat on what the government classified as converted wetland. He couldn't enroll in certain conservation programs for that acreage and his grazing permit was effectively conditional on implementing a riparian buffer. The fix was to file an appeal of the wetland determination through the NADASC (National Appeals Division) process and simultaneously apply for a Conservation Reserve Program contract on the buffer strips, which at least gave him some income offset while the appeal was pending.

Get the Full Details

Amazon.com: Effect of the Food Security Act of 1985 on the Domestic Livestock, Dairy, and ...
Amazon.com: Effect of the Food Security Act of 1985 on the Domestic Livestock, Dairy, and ...

What This Means for You Right Now

The act itself has been amended many times over the decades, and many of its provisions got folded into subsequent farm bills. But the compliance records, conservation plans, and wetland determinations it generated are still active. If you're running a livestock, dairy, or poultry operation and you've never checked your FSA farm file for a conservation compliance flag, do it now. A simple call to your county FSA office will tell you whether your operation has an outstanding compliance issue or a missing NRCS plan. The whole thing usually takes ten minutes on the phone and five minutes of reading on their end. If you discover you have an uncoded parcel or a missingWRAP, the correction window is open year-round, but the sooner you fix it the less risk you carry come planting season or an audit cycle. On the dairy side, if you're receiving production-based payments of any kind, verify that your historical production file matches your actual marketing history. Pull your FSA-578 forms from the last three farm bill cycles and cross-reference them against your milk check records. Any mismatch should be corrected before the next payment computation date. Doing this yourself saves about two hours of back-and-forth with the county office and prevents a surprise reduction later. The USDA doesn't refund retroactively for errors that existed before the filing window closes, so catching a discrepancy early is the only reliable path. The practical reality is that most of the act's provisions are administrative now. The dramatic shifts happened in the late 1980s and early 1990s. What remains is a compliance infrastructure that still governs how subsidies flow and how conservation rules are enforced on production land. Understanding that structure matters less as a survival tool today than as a way to avoid costly mistakes when expanding, applying for new program benefits, or dealing with a compliance review. I've watched smaller operations lose eligibility for programs they thought were automatic simply because someone failed to update a contact address or didn't re-certify their base acres after a land transfer. The paperwork isn't glamorous, but it's the thing that determines whether the program actually pays you when you need it to.