Raiders’ Maxx Crosby puts concerns to bed after failed Ravens trade

The Las Vegas Raiders have had a very eventful offseason, one that started with a failed Maxx Crosby trade and ended with them selecting Fernando Mendoza with the No. 1 overall pick in the NFL Draft.

Crosby was headed to the Baltimore Ravens in early March before a failed physical got the trade called off. Now, Crosby is back in Las Vegas and is ready to keep leading the defense for the Silver and Black.

Some fans may think that getting traded and then un-traded would lead to an interesting dynamic in the locker room, especially after Crosby seemed to want to be dealt after the 2025 season. However, on Wednesday during the Raiders’ offseason program, Crosby put all of those concerns to bed, via Ryan McFadden of ESPN.

“Everyone knows my love and appreciation for this organization that would never change from Day 1,” Crosby said. “There’s a lot of other things that don’t need to be discussed, but ultimately, I’m exactly where I want to be. I’m excited.”

Crosby has been an iron man during his career with the Raiders, but he struggled with a knee injury near the end of last season that caused him to fail the physical with Baltimore. That raises some questions about his health heading into the 2026 season, but if Crosby is healthy, there’s no question that he will have a major impact on the rebuild in Las Vegas under Klint Kubiak.

In seven seasons with the Raiders, Crosby has made five Pro Bowls and a pair of All-Pro teams. He has 69.5 sacks and 133 tackles for loss in his career while playing almost every snap of the game when he is healthy.

The Raiders made most of their moves to improve on offense this offseason, namely adding Mendoza and Kubiak to call the plays. The defense will still be a work in progress in year one of this new era, but having an impact player like Crosby present snap after snap could make this a fiesta group on that side of the ball.

The post Raiders’ Maxx Crosby puts concerns to bed after failed Ravens trade appeared first on ClutchPoints.