A Google AI Overview told a Kodiak woman that snipe season opened Sept. 1, more than a month before the actual Oct. 8 start date, and she shot three birds before catching the mistake herself. An Alaska Department of Public Safety spokesman said it is the first time he thinks the agency has seen an AI-generated answer cited in a case, and that he expects to see more of it. For teams that build or optimize pages answering seasonal, legal or regulatory questions, the case is a concrete failure mode, not a hypothetical one.
Court records filed this week in Kodiak show Christina Weaver reported herself to Alaska Wildlife Troopers after hunting on Sept. 5. Trooper Alex Wick wrote in an affidavit that Weaver said she had searched “snipe season” on her phone and that Google’s answer put the opening date at Sept. 1. Wick said he ran the identical search himself and got the identical wrong date, suggesting the error was not specific to Weaver’s phone or location.
Weaver grew suspicious only after learning that duck season did not open until Oct. 8, then checked the regulations and found snipe fell under the same later date. She turned herself in immediately afterward. “I feel terrible, and I have a lot of shame with it,” she said by phone. “It’s incredibly embarrassing.” She entered a no contest plea on Friday and received a $150 fine.
Google did not respond to a request for comment on the incorrect answer, according to Alaska Beacon’s report by James Brooks. Austin McDaniel, a spokesman for the Alaska Department of Public Safety, said his agency does not track how often AI-generated misinformation factors into violations. “This is the first time that I think we have seen AI cited,” he said, adding, “I expect we’ll see more of this type of thing in the future.”
McDaniel pointed hunters back to the Alaska Department of Fish and Game’s regulations and emergency orders as the authoritative source. That distinction matters for how state wildlife agencies should think about their own search visibility: if an AI Overview can out-rank or override a regulator’s published dates in a user’s decision-making, the agency has a direct stake in how cleanly its season tables are structured, dated and crawlable, not just in publishing them.
This differs from the industry’s usual AI Overview complaints, which center on lost clicks and citation share. Here the generated answer was simply wrong on a fact with a hard legal consequence. Regulatory, medical and other date-sensitive queries carry that same exposure: a generative summary can compress a specific opening date into the wrong month, with nothing in the interface flagging the substitution.
McDaniel also said self-reported hunting violations are punished much less severely than ones troopers uncover on their own, calling the gap in consequences “pretty dramatic.” That distinction is exactly the kind of guidance an AI Overview should surface accurately, since it directly shapes what a hunter does next after realizing a rule was broken.
Search and content teams working with government, health or safety-adjacent clients should audit how AI Overviews currently answer their client’s own regulated, date-specific queries and flag discrepancies to the relevant agency before the next wrong answer turns into the next citation affidavit.
Alaska Beacon reporter James Brooks reported this case on September 28, 2026.
