Tag Archives: jim unsworth

WDFW To Remove Some Smackout Wolves, Reports Ranchhand Legally Killed Attacking Wolf

THIS BREAKING STORY IS BEING UPDATED

WDFW Director Jim Unsworth has authorized the removal of wolves from the Smackout Pack of Northeast Washington following an attack on a calf in recent days.

They’re set to begin this week; there is no specific number of wolves that will be killed, but protocols say one or two initially, followed by a review of actions, with the goal to stop the pack from harming more cattle.

The latest calf was the fourth confirmed or probable depredation by the east-central Stevens County pack on calves in the past 10 months.

While most of those occurred last September, in June an employee of a ranch also legally killed a pack member after spotting it and another wolf attacking cattle.

A WDFW MAP SHOWS THE LOCATION OF THE SMACKOUT PACK NORTHWEST OF SPOKANE IN NORTHEAST WASHINGTON. (WDFW)

“The incident was investigated by WDFW Enforcement and was found to be consistent with state regulations,” a statement from the agency reads.

Under state law, you can kill a single gray wolf if you are witnessing one or more attacking your domestic animals in the federally delisted eastern third of Washington. This particular wolf was a female that had been radio collared in 2015, according to WDFW.

It’s the first time the caught-in-the-act provision has been used by livestock operators in Washington.

As for the latest depredation, the calf was found injured on Forest Service ground on Tuesday.

Bite marks and collar location data show that the Smackout wolves have been near the cattle herd “on a frequent basis.”

The attack occurred in a fenced area, and according to WDFW several deterrence measures have been taken.

Per WDFW:

“The livestock producer that sustained the July 18, 2017 confirmed wolf depredation is currently using: several range riders (one range rider is primary, but others fill in on an as needed basis), has maintained sanitation by removing or securing livestock carcasses, actively hazed wolves with a firearm and pyrotechnics, kept cattle in a fenced pasture within the allotment due to wolf activity, spotlighting nightly, wolf GPS collar data in the area to monitor activity near cattle, used fladry when needed, a RAG box when needed, and several other deterrents in the past. The range rider started patrolling the area prior to the June 1 turnout in 2017, and communicates frequently with the producer and the local Wildlife Conflict Specialist. Information on denning and wolf activity was also shared with the producer, which the producer has avoided those high use wolf areas. Another producer that was involved in one of the three 2016 depredations within the Smackout territory have been using WDFW contracted range riders, sanitation, and removal of injured cattle from the range.”

Conservation Northwest, which has long been involved in helping ranchers in this part of Washington’s wolf country, as well as elsewhere, issued a statement saying it hoped any removals plus the caught-in-the-act take last month would end the attacks on livestock and end the need to kill more wolves.

The organization also said it was “deeply saddened by the loss of these wolves, and for the strife this incident has caused ranchers operating in this area.”

Last year’s depredations occurred in late September and included a confirmed kill of a calf, a probable kill of a calf and a confirmed injury of a calf.

One other calf has been killed by wolves and two injured stretching back to 2015 in the general area.

“The purpose of this action is to change the pack’s behavior, while also meeting the state’s wolf-conservation goals,” the agency’s wolf manager, Donny Martorello, said in a press release this morning. “That means incrementally removing wolves and assessing the results before taking any further action.”

The pack is believed to have numbered eight coming out of 2016, with an unknown number of pups on the ground this year.

“The lethal removal of wolves is not expected to harm the wolf population’s ability to reach recovery objectives statewide or within individual wolf recovery regions,” a WDFW statement reads.

This means that for a second summer in a row, agency marksmen will be targeting wolves as Washington’s population continues to grow at about a 30-percent-a-year clip. Last year it was the Profanity Peaks, while previous removals occurred in 2014 (Huckleberry) and 2012 (Wedge).

Lake Washington Sockeye Count Tops 110,000, But Declining

The odds of a Lake Washington sockeye fishery this year — long to begin with — seem remoter still with today’s updated count unless somehow hesitant salmon managers acquiesce to a Hail Mary bid.

A total of 111,509 have passed through the Ballard Locks since the tally began June 12, and the year’s best days appear to be behind us.

IT’S BEEN 11 YEARS SINCE THE LAST LAKE WASHINGTON SOCKEYE FISHERY, AND DESPITE CALLS FOR AN “OLD TIMES SAKE” SEASON THIS YEAR, THAT’S INCREASINGLY UNLIKELY WITH THE LATEST BALLARD LOCKS COUNTS. (ANDY WALGAMOTT)

Nearly 7,500 were counted July 4, with 21,740 in the three days before and day afterwards.

But since then daily counts have dipped to 2,772 Wednesday and 2,271 yesterday.

The run has typically peaked by now, though of note 2006 didn’t hit its midmark till mid-July.

If there’s good news, it’s that the forecast of 77,292 was wrong, and there does appear to be some softening on the standing escapement goal of 350,000 sockeye to trigger sport and commercial tribal fisheries.

According to a recent WDFW letter, talks have been ongoing with the comanagers about “a new abundance-based management framework that allows for some directed fisheries at run-sizes of 200,000 or greater.”

Written July 7, the communique from Director Jim Unsworth expresses cautious optimism that that figure might be reached.

But Frank Urabeck, a longtime recreational angling advocate who closely watches the counts, now estimates the run will come in somewhere north of 130,000, which is above the 100,000 that he hoped might trigger a “token, for old times’ sake” fishery on Lake Washington, where we haven’t seen a sockeye season since 2006.

Since then, an average of 78,000 — high: 2013’s 178,422; low: 2009’s 21,718 — have entered the locks with fewer still actually spawning.

By comparison, between 2006 and 1972, only three years saw 78,000 or fewer sockeye enter; even the bad salmon years of the mid-1990s were higher.

It’s believed that despite the new Seattle Public Utilities hatchery on the Cedar River, young sockeye are suffering increasing and strong predation in the lake and as they make their way through the Ship Canal, which also appears to be a thermal block for returning adults, leaving them more prone to disease.

This year’s run would also have been at sea during the fish-run-destroying Blob.

Among Urabeck’s aims is to draw attention to what he considers to be a failing run, and he sees this year’s return as what amounts to a last-gasp opportunity to get anglers on the lake and rally support for what once was a wonderful salmon fishery in the heart of the state’s biggest metropolis.

If you never had a chance to partake in it, it was the absolute best kind of insanity going.

Urabeck wants one last go.

“I encourage sportfishing anglers to contact Director Unsworth and the MIT to encourage them to avoid losing this special opportunity to gain public support for our fisheries programs,” he said this morning.

Unsworth, who wrote that Urabeck’s call for a season if the count hit 100,000 “certainly caught my attention,” agreed that Lake Washington salmon aren’t faring well, but was more optimistic about the future.

“It will be a challenging task, but the restoration of clear, clean, and swimmable water to Lake Washington in the 1960s shows what can be accomplished with our engaged and supportive public,” Unsworth states in the letter to Urabeck.

The director says that his agency as well as the tribes, county and utilities are “now implementing and advocating for the actions necessary to improve salmon survival in the Lake Washington basin.”

“In this urban setting, we will need to think ‘out-of-the-box’ to find solutions that provide for salmon in the future. In part, this will likely require rethinking how we use our hatcheries. As you recall, we joined with you and others in the Year-15 Comprehensive Review of the City of Seattle’s Habitat Conservation Plan in recommending new supplementation techniques that maximize fry-to-adult survival through a combination of extended rearing and delayed release timing,” Unsworth states.

Meanwhile, the Muckleshoot and Suquamish Tribes are holding their annual ceremonial and subsistence fisheries, with goals of 1,000 and 2,500 sockeye each, and yesterday saw dipnetting in the ladder as tribal biologists in conjunction with WDFW collected salmon for a longterm biological sampling program.

What the longterm health of the sportfishery holds is anyone’s guess, but at the moment, it is on life support at best this year.