Colorado Officials Euthanize ‘Chronic' Problem Wolf That Was Killing Livestock
The challenges associated with bringing gray wolves back to Colorado were illuminated yet again last week. On Thursday, state wildlife managers made what they called the 'very difficult' decision to kill a wolf that was preying on livestock on private land in Pitkin County, and which had previously been relocated from another county due to concerns around livestock depredations.
The lethal removal took place the evening of May 29 on an unidentified cattle ranch. It was the first time that officials with Colorado Parks and Wildlife have killed a wolf since the voter-led reintroduction effort began in 2023. It was not, however, the first time that CPW has dealt with this particular wolf, which was identified in an agency news release as gray wolf 2405 and a member of the Copper Creek Pack.
Read Next: The Wolf Pack Responsible for the Majority of Livestock Depredations in Colorado Will Be Relocated, Not Killed
Officials explained that the young male wolf had met their definition of 'chronic depredation' after being linked to four such events in an eight-day period. They said those events occurred even with non-lethal deterrence measures in place. They pointed to 'clear and convincing evidence' that 2405 was responsible for three of the cows that were injured or killed on several different ranches in Pitkin County around Memorial Day weekend.
'The decision to take lethal management action was very difficult,' CPW director Jeff Davis said in a statement. 'Our wildlife biologists constructed a timeline of recent events that shows the depredation behavior met the conditions for chronic depredation that were defined earlier this year. We have great respect for these animals and take the removal of a wolf very seriously.'Davis went on to explain that the action was meant 'to discourage [the] other pack members' from preying on livestock. He said the agency would continue to monitor the behavior of those remaining pack mates 'to determine if behavior has changed,' but didn't specify what management actions might be taken based on that behavior in the future.
It's also unclear based on CPW's timeline of events whether wolf 2405 was acting alone, or if other members of the pack were involved in the depredations as well. That timeline cites GPS collar data, which showed 'some wolves from the Copper Creek Pack were in the area' where the depredations took place on May 24 and 25.
A CPW spokesperson did not give a specific answer when asked by OL whether this collar data might indicate that multiple wolves from the Copper Creek Pack were involved in the Pitkin County depredations in May. The spokesperson clarified that 2405 was 'a member of a pack determined to have met the definition of chronic depredation' and said CPW would post a full report with more information soon.
'[This] is not something that we take lightly,' CPW wolf conservation program manager Eric Odell said in Friday's news release. 'Removal of animals early in the restoration process is a balance between managing populations of wolves, while also assisting landowners in resolving ongoing conflicts with wolves.'
CPW also noted in Friday's announcement that it is currently monitoring four potential dens across the state, and that more pups will likely be born this spring. That should bring Colorado closer to its eventual goal of a self-sustaining gray wolf population, while at the same time giving wildlife managers more GPS-collared wolves to keep track of. There are currently 23 collared wolves roaming the state, and their movements are updated monthly in a map maintained by CPW.
In many ways, the Copper Creek Pack has embodied how complicated and contentious Colorado's wolf restoration process has been. The pack was formed by two of the 10 wolves that were initially brought over from Oregon and released in Grand and Summit Counties back in December 2023. The mating pair established a den in Grand County that winter and gave birth to five pups the following spring.
Read Next: Coloradans Who Oppose Wolf Reintroduction Can't Agree on How to Try Ending It
Conflicts soon followed. Between April and July 2024, as wolf advocates celebrated the pack's formation, CPW confirmed multiple livestock depredations by the pack's two adult wolves. Ranchers in Grand County pleaded with both the state and the federal government to lethally remove the wolves, but their requests were denied. Although CPW's policy director told commissioners at one point that the adult pair had caused 'the main issues in depredation' among all the wolves that were relocated there from Oregon, the agency ultimately decided that killing the two breeding wolves would be 'irresponsible' and could hamper its larger recovery goals.
CPW chose instead to capture and relocate the Copper Creek Pack in September. The male wolf died soon after capture, and one of the pups eluded officials, while the remaining four pups and the female were trapped and held at an undisclosed facility for several months. The five Copper Creek wolves were then re-released this last winter along with the 15 additional gray wolves that were translocated from British Columbia to Eagle and Pitkin Counties in January.
At the time of the Copper Creek Pack's capture last fall, CPW acknowledged that relocation was not how it planned to handle those types of conflicts going forward. Ranchers, meanwhile, expressed their concerns that by relocating the wolves, wildlife managers were simply moving the problem instead of solving it.
Read Next: Colorado Parks and Wildlife Releases Second Batch of Wolves Amid Threats, Rumors, and Growing Controversy
'By refusing to manage problem wolves, CPW has allowed livestock depredations to continue unchecked, while fostering a pack of depredating wolves,' read an August 2024 letter from the Colorado Cattlemen's Association to CPW director Jeff Davis. 'Pups from these problem wolves will be trained to 'hunt' and survive off livestock.'
Hashtags

Try Our AI Features
Explore what Daily8 AI can do for you:
Comments
No comments yet...
Related Articles
Yahoo
32 minutes ago
- Yahoo
Greenberg: 'Long-term solutions' being considered to curb rowdy crowds on Bardstown Road
Mayor Craig Greenberg said June 5 that more long-term solutions are being considered to deal with unruly crowds that have shut down Bardstown Road for two consecutive weekends. Greenberg's comments followed a meeting among business owners and residents in the Highlands neighborhood to discuss what can be done after hundreds of people flooded the area around Bardstown Road and Grinstead Drive, blocking traffic and disturbing neighbors in the early morning hours. 'We want Bardstown Road to remain a thriving commercial corridor with great shops, great businesses, bars, with restaurants, with great different types of residents living all around us well, and that's where we're headed,' Greenberg said. Greenberg was reluctant to reveal what long-term courses of action were discussed at the June 5 meeting. He said some of the solutions he was considering 'could be happening at the state level' and others would require Metro Council approval, but that he was not considering forcing bars to close earlier at this time. 'I don't want to get too far ahead of that, because we still need to research some of them,' he said. Highlands Commerce Guild President Aaron Givhan said June 5 that one suggestion he's heard from residents is a mandatory 2 a.m. closing time for bars. 'They want quiet in their neighborhood,' Givhan said, 'And that is a fair request.' The Highlands Tap Room on Bardstown Road is one bar that closes at 4 a.m., but it recently came to a voluntary agreement with city officials to temporarily close its doors at 2 a.m. on the weekends to curb disturbances in the neighborhood. For some bars and businesses like Taco Bell, the 2-4 a.m. window is cash bearing, Givhan said, giving them a 'true financial reason to be open.' He added he was concerned that if the rules change for one bar, they would have to change for all bars in Jefferson County. 'The resolution is working together to calm things down,' he said. 'As long as the businesses remain in an acceptable, law-abiding demeanor, there is no reason to punish them, and that's where the guild comes in. We are not into punishment.' Discussion of reform in the Highlands came to a head when hundreds of people swarmed the intersection of Bardstown Road and Grinstead Drive in the early hours of the morning Memorial Day weekend. LMPD made no arrests on that occurrence, but when a crowd amassed again the following weekend, officers arrested three people for disorderly conduct. After the events on Memorial Day weekend, Councilman Ben Reno-Weber, whose district includes the Highlands, promised increased police presence in the neighborhood. Business owners were encouraged by LMPD to file Trespass Enforcement Request Forms, which authorize officers to address trespassing without an on-site complaint. Sergeant Matt Sanders said that LMPD plans to be in the area from 6 p.m. to 4 a.m. Friday and Saturday night, with mounted patrol stationed on the street to discourage crowds from forming. This story may be updated. Reach reporter Molly Gregory at msgregory@ This article originally appeared on Louisville Courier Journal: Greenberg talks possible solutions for late-night crowds in Highlands
Yahoo
an hour ago
- Yahoo
Watchdog probes if aides were asked to delete Hegseth's Signal chats
The Pentagon's watchdog is looking into whether any of Defense Secretary Pete Hegseth's aides were asked to delete Signal messages that may have shared sensitive military information with a reporter, according to two people familiar with the investigation and documents reviewed by The Associated Press. The inspector general's request focuses on how information about the March 15 airstrikes on Houthi targets in Yemen was shared on the messaging app. This comes as Hegseth is scheduled to testify before Congress next week for the first time since his confirmation hearing. He is likely to face questions under oath not only about his handling of sensitive information but also the wider turmoil at the Pentagon following the departures of several senior aides and an internal investigation over information leaks. Hegseth already has faced questions over the installation of an unsecured internet line in his office that bypassed the Pentagon's security protocols and revelations that he shared details about the military strikes in multiple Signal chats. One of the chats included his wife and brother, while the other included President Donald Trump's top national security officials and inadvertently included The Atlantic's editor-in-chief, Jeffrey Goldberg. Pentagon press secretary Kingsley Wilson had no comment on Friday, citing the pending investigation. The inspector general's office didn't immediately respond to a request for comment. Besides finding out whether anyone was asked to delete Signal messages, the inspector general also is asking some past and current staffers who were with Hegseth on the day of the strikes who posted the information and who had access to his phone, according to the two people familiar with the investigation and the documents reviewed by the AP. The people were not authorized to discuss the investigation and spoke on the condition of anonymity. Democratic lawmakers and a small number of Republicans have said that the information Hegseth posted to the Signal chats before the military jets had reached their targets could have put those pilots' lives at risk and that for any lower-ranking members of the military it would have led to their firing. Hegseth has said none of the information was classified. Multiple current and former military officials have said there is no way details with that specificity, especially before a strike took place, would have been OK to share on an unsecured device. 'I said repeatedly, nobody is texting war plans,' Hegseth told Fox News Channel in April after reporting emerged about the chat that included his family members. 'I look at war plans every day. What was shared over Signal then and now, however you characterize it, was informal, unclassified coordinations, for media coordinations and other things. That's what I've said from the beginning.' Trump has made clear that Hegseth continues to have his support, saying during a Memorial Day speech at Arlington National Cemetery in Virginia that the defense secretary 'went through a lot' but 'he's doing really well.' Hegseth has limited his public engagements with the press since the Signal controversy. He has yet to hold a Pentagon press briefing, and his spokesman has briefed reporters there only once. The inspector general is investigating Hegseth at the request of the Republican chairman of the Senate Armed Services Committee, Sen. Roger Wicker of Mississippi, and the committee's top Democrat, Sen. Jack Reed of Rhode Island. Signal is a publicly available app that provides encrypted communications, but it can be hacked and is not approved for carrying classified information. On March 14, one day before the strikes against the Houthis, the Defense Department cautioned personnel about the vulnerability of the app. Trump has said his administration targeted the Houthis over their 'unrelenting campaign of piracy, violence and terrorism.' He has noted the disruption Houthi attacks caused through the Red Sea and the Gulf of Aden, key waterways for energy and cargo shipments between Asia and Europe through Egypt's Suez Canal. The Houthi rebels attacked more than 100 merchant vessels with missiles and drones, sinking two vessels and killing four sailors, between November 2023 until January this year. Their leadership described the attacks as aimed at ending the Israeli war against Hamas in the Gaza Strip.


The Hill
2 hours ago
- The Hill
Watchdog investigating whether Hegseth aides were asked to delete Signal messages: Report
WASHINGTON (AP) — The Pentagon's watchdog is looking into whether any of Defense Secretary Pete Hegseth's aides were asked to delete Signal messages that may have shared sensitive military information with a reporter, according to two people familiar with the investigation and documents reviewed by The Associated Press. The inspector general's request focuses on how information about the March 15 airstrikes on Houthi targets in Yemen was shared on the messaging app. This comes as Hegseth is scheduled to testify before Congress next week for the first time since his confirmation hearing. He is likely to face questions under oath not only about his handling of sensitive information but also the wider turmoil at the Pentagon following the departures of several senior aides and an internal investigation over information leaks. Hegseth already has faced questions over the installation of an unsecured internet line in his office that bypassed the Pentagon's security protocols and revelations that he shared details about the military strikes in multiple Signal chats. One of the chats included his wife and brother, while the other included President Donald Trump's top national security officials and inadvertently included The Atlantic's editor-in-chief, Jeffrey Goldberg. Pentagon press secretary Kingsley Wilson had no comment on Friday, citing the pending investigation. The inspector general's office didn't immediately respond to a request for comment. Besides finding out whether anyone was asked to delete Signal messages, the inspector general also is asking some past and current staffers who were with Hegseth on the day of the strikes who posted the information and who had access to his phone, according to the two people familiar with the investigation and the documents reviewed by the AP. The people were not authorized to discuss the investigation and spoke on the condition of anonymity. Democratic lawmakers and a small number of Republicans have said that the information Hegseth posted to the Signal chats before the military jets had reached their targets could have put those pilots' lives at risk and that for any lower-ranking members of the military it would have led to their firing. Hegseth has said none of the information was classified. Multiple current and former military officials have said there is no way details with that specificity, especially before a strike took place, would have been OK to share on an unsecured device. 'I said repeatedly, nobody is texting war plans,' Hegseth told Fox News Channel in April after reporting emerged about the chat that included his family members. 'I look at war plans every day. What was shared over Signal then and now, however you characterize it, was informal, unclassified coordinations, for media coordinations and other things. That's what I've said from the beginning.' Trump has made clear that Hegseth continues to have his support, saying during a Memorial Day speech at Arlington National Cemetery in Virginia that the defense secretary 'went through a lot' but 'he's doing really well.' Hegseth has limited his public engagements with the press since the Signal controversy. He has yet to hold a Pentagon press briefing, and his spokesman has briefed reporters there only once. The inspector general is investigating Hegseth at the request of the Republican chairman of the Senate Armed Services Committee, Sen. Roger Wicker of Mississippi, and the committee's top Democrat, Sen. Jack Reed of Rhode Island. Signal is a publicly available app that provides encrypted communications, but it can be hacked and is not approved for carrying classified information. On March 14, one day before the strikes against the Houthis, the Defense Department cautioned personnel about the vulnerability of the app. Trump has said his administration targeted the Houthis over their 'unrelenting campaign of piracy, violence and terrorism.' He has noted the disruption Houthi attacks caused through the Red Sea and the Gulf of Aden, key waterways for energy and cargo shipments between Asia and Europe through Egypt's Suez Canal. The Houthi rebels attacked more than 100 merchant vessels with missiles and drones, sinking two vessels and killing four sailors, between November 2023 until January this year. Their leadership described the attacks as aimed at ending the Israeli war against Hamas in the Gaza Strip.