North Dakota farmer pleads guilty to crop insurance fraud
Summarised from 2 outlets · Updated 20 Nov, 02:32 · Archive
Joseph Fettig, 51, from Tappen, North Dakota, pleaded guilty to making false statements to the USDA's Risk Management Agency.
Joseph Michael Fettig, 51, from Tappen, North Dakota, pleaded guilty in federal court to a felony charge of making false statements to influence the U.S. Department of Agriculture's Risk Management Agency. U.S. Attorney Nicholas Chase announced the plea on 19 November. As part of his plea agreement, Fettig accepted a five-year exclusion from receiving any benefits from federal procurement transactions authorised or funded by the USDA.
Fettig used a scheme called 'shifting production' between 1 March 2022 and 31 December 2022, the U.S. attorney's office said. The scheme involved reporting excessive crop production from some fields and insufficient production from others to create or inflate crop insurance claims on his corn production in Logan County. The false statements he made to the Risk Management Agency and the Federal Crop Insurance Corporation resulted in inflated insurance payments.
The USDA's Office of Inspector General and the Risk Management Agency's Special Investigations Staff investigated the case. Sentencing is set for 24 March 2027 in Bismarck before U.S. District Judge Daniel Hovland.

How it is being reported
- Farmer from Tappen pleads guilty to crop insurance fraud in federal courtA man from Tappen has pleaded guilty to crop insurance fraud.KXNET · 20 Nov, 02:02
- Tappen man pleads guilty to crop insurance fraud, agrees to five-year USDA exclusionJoseph Fettig, 51, admitted a felony charge involving corn claims in Logan County; sentencing is set for March 24, 2027Valleynewslive · 19 Nov, 21:39
In this story: Joseph Michael Fettig · U.S. Department of Agriculture · Tappen · Logan County · North Dakota
This summary was written by AI from the headlines and standfirsts above, and states as fact only what at least two outlets report. How we use AI · Report a problem · Corrections log
Comments (0)