Oregon
Purdue (1-1) at Oregon State (2-1) – Staff Predictions
Game day is coming up in just under 12 hours. Sure, it’s an 8:30 PM kickoff here on the East coast (the best coast) but this means that I can be downstairs watching the game while my adorable four year old son sleeps away. No guilt for me! So, while I’m watching the game tomorrow, will I be having a celebratory drink or a depressing, wow two weeks in a row, type drink? I asked the staff for their thoughts.
Jumbo Heroes (2-0):
It’s weird being so upset about the Notre Dame loss. I mean, I knew Purdue was going to lose all offseason. I had no expectations going into the game, but somehow the Notre Dame loss to Northern Illinois gave me enough hope that Notre Dame was a paper tiger and Purdue could take them down. I was of course wrong in that hope but right in my predicted outcome. So, why am I so upset? Purdue is 1-1 right now just like I predicted they would be and I thought they had a shot at taking down Oregon State when I looked into this game, so why am I picking against Purdue now? Surely, a loss is a loss and it doesn’t matter right? Well, yes and no. In the record books a loss is a loss is a loss. Hardly anyone will remember the manner in which a team loses any one game when they look at their overall season record. However, I watched that game and didn’t see anything that inspired confidence in me.
Oregon State is a team that is going to focus on running the football. Purdue could not stop the run against Notre Dame and it often seemed like Notre Dame didn’t even have to try. So, what would give me hope that Purdue can stop Oregon State from running all over them? I can’t think of anything. What would make me confident that the Purdue offense that could only muster seven points against Notre Dame’s second and third string can score enough points to win? I can’t think of anything. What a depressing outlook.
I’m picking against Purdue until they show me something. Until they show me some fight.
Purdue 10
Oregon State 28
Ryan (2-0):
This game is where rubber meets the road. We saw what Purdue can do against FCS teams and top-25 teams. Oregon State represents likely the best measuring stick so far this season and if Purdue lays an egg, it feels like it could be a lost team. It starts with the coaching staff preparing for Oregon State. Oregon State has a good rushing attack and Purdue got gashed on the ground last week. I think it’s apparent where the focus needs to be.
All told, I think it’s obvious that Purdue’s talent is close to the level of Oregon State’s. Both teams are coming off big losses to in-state rivals and both have flaws that can be exploited. A fairly even match seems to favor the home team in this one so I think Purdue gets somewhat back on track, even if they don’t win the game.
Purdue 21
Oregon State 28
Jed (2-0):
A trip out west doesn’t go well for the Boilers as the heat surrounding Ryan Walters is turned up even more with a very mediocre performance against a beatable Oregon State program. Walters leaves himself little to no wiggle room and must go 5-4 in the conference slate to make a bowl game, something that is highly unlikely to occur.
Purdue 24
Oregon State 34
Drew (1-1):
I honestly have no idea what to expect from either team. I don’t think Purdue is as bad as they looked against Notre Dame, but I’ve got nothing to back that theory up.
At the same time, Oregon State just took it on the chin against Oregon in the Civil War. Their defense couldn’t deal with Oregon’s speed but Purdue isn’t Oregon.
I’m going to revert to my factory setting of being a homer, and against my better judgement, I’m taking the Boilermakers (ducks flying tomato).
Purdue tightens things up on defense, the offensive line isn’t awful, and Hudson Card has a big day both in the ground and through the air.
Purdue 24
Oregon St. 17
Kyle (2-0):
Last week showed everyone so many holes that Purdue has. It was clear that the Offensive Line and Defensive Line were real issues. The biggest issue is that Oregon State has two running backs that are just as good or better than Jerymiah Love of ND.
Purdue will have to keep up offensively in this one, and I am not sure they are going to be able to do so.
Purdue 17
Oregon State 27
Garrett (1-1):
I’m not superstitious (yes I am) but my prediction was so flawed last week I’m going to do the opposite.
In this young season, I don’t think Oregon State is bad, in fact I think they’re about on par with where we are. Additionally, like Purdue, they’re coming off a big beatdown against an in-state rival. That said, traveling out west that far is never easy and they have some die-hards in Corvallis.
This one’s all coming down to the Boilers’ offensive line being able to recover from a terrible performance last week. I think this one stays close, but it’s all contingent on that OL and maybe, just maybe, getting more than 200 yards of total offense. If we see an effort in the trenches similar to last week, I see Oregon State winning something like 23-17. If the Boilermakers offensive line can take a step up, I’m taking the Train Enjoyers 31-23. Weird two-pronged prediction, I know, but like I said, the season can sometimes be too young to recognize anything definitively.
Editor’s note: Two predictions? How cowardly, Garrett gets no credit regardless of a win or loss unless he gets the score exactly right. This will be noted in all the rest of his predictions going forward this season.
Oregon
Distracted teen driver veers off Hwy 99W, fatally strikes pedestrian near Junction City
ROSEBURG, Ore. — A pedestrian was killed when a driver drifted from her lane of travel, striking a Junction City man, according to Oregon State Police.
At 4:48 p.m. on May 5, Oregon State Police responded to a vehicle versus pedestrian fatal crash on Highway 99W near milepost 110.5 in Lane County.
Police say a blue Hyundai Elantra driven by a 16-year-old female, was southbound on Highway 99W near Junction City when she became distracted, left the travel lane, and struck a pedestrian.
The pedestrian, Joel Robert Benjamin Coriell, 35, of Junction City, had been walking along the southbound shoulder of the highway.
Coriell was transported to an area hospital with serious injuries and later died at the hospital.
The driver of the Hyundai had reported minor injuries. She remained on scene and cooperated with the investigation, police said.
The highway was not impacted during the on-scene investigation, OSP stated.
OSP was assisted by the Junction City Police Department, Lane County Sheriff’s Office, and the Oregon Department of Transportation.
Oregon
Oregon Lottery Powerball, Pick 4 results for May 6
The Oregon Lottery offers several draw games for those aiming to win big.
Here’s a look at May 6, 2026, results for each game:
Winning Powerball numbers from May 6 drawing
18-27-51-65-68, Powerball: 05, Power Play: 3
Check Powerball payouts and previous drawings here.
Winning Pick 4 numbers from May 6 drawing
1PM: 8-9-4-6
4PM: 0-3-3-1
7PM: 3-7-1-9
10PM: 5-4-8-0
Check Pick 4 payouts and previous drawings here.
Winning Win for Life numbers from May 6 drawing
07-45-52-54
Check Win for Life payouts and previous drawings here.
Winning Megabucks numbers from May 6 drawing
03-09-10-28-31-39
Check Megabucks payouts and previous drawings here.
Feeling lucky? Explore the latest lottery news & results
When are the Oregon Lottery drawings held?
- Powerball: 7:59 p.m. on Monday, Wednesday and Saturday.
- Mega Millions: 7:59 p.m. on Tuesday and Friday.
- Pick 4: 1 p.m., 4 p.m., 7 p.m. and 10 p.m. daily.
- Win for Life: 7:30 p.m. on Monday, Wednesday, and Saturday.
- Megabucks: 7:29 p.m. on Monday, Wednesday, and Saturday.
This results page was generated automatically using information from TinBu and a template written and reviewed by an Oregon editor. You can send feedback using this form.
Oregon
Oregon State Police sued for sharing data with immigration agencies
Oregon Gov. Tina Kotek responds to heightened immigration enforcement
Oregon Gov. Tina Kotek and state legislators spoke Jan. 24 about recent immigration enforcement happening across Oregon. Here’s what Kotek said.
Rural Organizing Project, a statewide nonprofit based in Cottage Grove, filed a lawsuit May 5 against Oregon State Police in Multnomah County Circuit Court, alleging that the agency is violating the state’s landmark sanctuary laws and sharing Oregonians’ personal data with federal immigration agents.
The nonprofit is asking the court to direct OSP not to share information with U.S. Immigration and Customs Enforcement and other immigration agencies, including driver’s licenses, driver history, driver’s license photographs, vehicle registration data, Social Security numbers and law enforcement records.
ROP claims that federal immigration agencies have repeatedly accessed Oregonians’ information over the past year. They point to two systems OSP operates: the National Law Enforcement Telecommunications System and the state’s Law Enforcement Data System.
The complaint said data provided to OSP by NLETS in February showed authorities involved in immigration enforcement accessed Oregonians’ data more than 1.4 million times in the preceding year. ICE alone queried Oregon for the data 176,576 times, the complaint said. Homeland Security Investigations within the Department of Homeland Security queried 21,363 times, and U.S. Customs and Border Protection and DHS accounted for the remainder, the complaint said.
Those numbers do not include all queries of Oregonians’ data, lawyers added, as ICE and HSI agents in Oregon will access the same information separately through the LEDS terminal.
The complaint says OSP has the technical capacity to block immigration enforcement agencies from both systems, but has declined to do so.
U.S. Sens. Ron Wyden, D-Oregon, and Jeff Merkley, D-Oregon, along with U.S. Reps. Suzanne Bonamici, D-Oregon, and Andrea Salinas, D-Oregon, called on states across the country to stop sharing drivers’ data with federal immigration agencies in a November 2025 letter.
Other states, such as Illinois, Massachusetts, Minnesota, and New York, have stopped allowing federal agents to access their residents’ data, according to NLETS testimony to Congress in 2025, the complaint added.
The suit says NLETS provided OSP a spreadsheet listing the specific identification codes ICE uses in late 2025, after an OSP official asked how other states had blocked the agency in the system.
But in February, the complaint said, the agency indicated it would not restrict federal immigration authorities’ access to data via LETS or require federal authorities to use “Reason Codes” that would allow OSP to screen whether the query is for immigration-related purposes.
In a response sent to the Oregon Law Center on Feb. 1, replying to its tort claim notice, OSP said it had taken “reasonable steps” to improve its LEDS agreements with immigration authorities to require compliance with Oregon’s Sanctuary Law. Their letter said terminating the LEDS user agreements, which OSP signed with ICE and DHS in December 2025 and February, would prevent the federal agencies from accessing criminal justice information related to criminal investigations and other governmental purposes.
“If OSP terminated the user agreements, they could be obstructing ongoing criminal investigations,” the letter from OSP said.
OSP also said it did not have the ability to modify the NLETS system.
“Federal agents are storming into our communities, targeting people based on how they look, and disappearing our neighbors,” Martha Ortega, director of Immigrant Centers at Rural Organizing Project, said in a prepared statement. “Oregon State Police are helping them do it. When the state gives our private information to ICE, it is breaking the law and breaking Oregonians’ trust. How many families have been torn apart by Oregon State Police giving their names and photos to federal agents?”
The lawsuit cites testimony in federal court, detailed in a story by The Oregonian, where ICE agents spoke of staking out a neighborhood and randomly running vehicle license plates to find vehicle owners’ names and birthdates for the purpose of immigration enforcement.
“Oregon’s law has clearly prohibited this kind of information sharing for almost 40 years,” said Heather Marek, attorney at Oregon Law Center, which is representing the nonprofit. “Oregonians need Oregon State Police to respect the law and protect their data, immediately and permanently.”
In an email, a spokesperson for Oregon State Police said it would not be making any public comments related to the lawsuit while litigation was pending.
“OSP is committed to following Oregon Sanctuary Laws and has not taken any actions that would violate those laws,” Cpt. Kyle Kennedy added.
But, ROP said in its lawsuit that although the LEDS user agreements prohibit ICE-ERO and HSI from sharing data for immigration enforcement purposes, OSP cannot ensure compliance with the sanctuary laws nor can it reasonably assume compliance given the broader context of the current administration and activity.
More than 6,000 HSI agents have been assigned to immigration enforcement duties, for example, the lawsuit said.
“In the current political and legal context, an agreement to provide resources and information to HSI is an agreement to provide resources and information to support immigration enforcement,” the complaint said.
Dianne Lugo covers the Oregon Legislature and equity issues. Reach her at dlugo@statesmanjournal.com on X @DianneLugo or Bluesky @diannelugo.bsky.social.
-
Fitness46 seconds agoFlexibility expert recommends doing this for three minutes daily to improve mobility
-
Movie Reviews13 minutes ago“Billie Eilish – Hit Me Hard and Soft: The Tour” Movie Review – Spotlight Report
-
World25 minutes ago
Cyberattack hits Canvas system used by thousands of schools as finals loom
-
News31 minutes agoState Department Will Revoke Passports of Parents Who Owe Child Support
-
Politics37 minutes agoU.S. Strikes Iranian Targets; Iran Says It Returned Fire
-
Business43 minutes agoHow Energy Prices Are Driving Demand for Solar Panels and Heat Pumps
-
Science49 minutes agoWhat My Father’s Experience Taught Me About Memory and the Brain
-
Health55 minutes agoAmerican Factories Lag in Adopting A.I. This Drugmaker Is an Exception.