James Starks Release Means Nothing For Packers RBs
Green Bay Packers made their first move of the offseason by releasing running back James Starks on the non-football injury list. Starks never recovered from a concussion he suffered in an early morning carwreck after Seattle Seahawks game. Before Starks’ injury, the writing seemed on the wall for the veteran running back. Green Bay Packers didn’t see much production from him, and it got the feel like the Buffalo product looked like an old running back which we’ve seen time and again. Although this does nothing to solve Green Bay’s running back conundrum.
Packers have a choice on Eddie Lacy that’s upcoming. We went over how Lacy’s contract will probably be in the 27-30 million dollar range over four years unless he decides to do a Nick Perry deal where it’s one-year with incentives. A part of me feels like given the nature of his position if someone say Detroit offers him four years, 27 million, he’s going to take it. You have to at Lacy’s age. If this happens, Packers are left with Ty Montgomery and Aaron Ripkowksi. That cupboard becomes pretty bare pretty quickly.
Green Bay would likely draft a running back in the first four rounds to serve a replacement for Lacy, and in case, Montgomery suffered a sophomore slump or can’t become the runner all Packers fans hope for. Some think Starks might have a chance to come back, but I don’t see it with his age and skill level at this point.
Running back is one of the many interesting positions to watch this summer.