Buccaneers Should Take a Look at James Starks

Nov 13, 2016; Nashville, TN, USA; Green Bay Packers running back James Starks (44) spikes the ball after a touchdown during the first half against the Tennessee Titans at Nissan Stadium. Mandatory Credit: Christopher Hanewinckel-USA TODAY Sports
Nov 13, 2016; Nashville, TN, USA; Green Bay Packers running back James Starks (44) spikes the ball after a touchdown during the first half against the Tennessee Titans at Nissan Stadium. Mandatory Credit: Christopher Hanewinckel-USA TODAY Sports /
facebooktwitterreddit

The Buccaneers must seriously consider signing James Starks.

More from The Pewter Plank

The struggle at running back for the Buccaneers is real. We all witnessed it first hand in 2016. When the leading rusher posted 560 yards for a team that values the ground game, there are problems.

Add to that the fact that Doug Martin will miss at least the first three games due to his suspension, and may be given his outright release, we know the Bucs need help. It isn’t as if Charles Sims set the world on fire when he was healthy last year. The Bucs must beef up the running game.

A little bit over one week ago, I talked about some potential replacements for Martin. Well, it’s time to add one more, James Starks. For anybody that missed it, he was cut by the Packers, as reported by Yahoo! Sports. Let’s take a look at the body of work by Starks, as he would make an excellent fit with the Bucs.

Now, one might question the theory when you take a look at his stats and see he has been basically a backup his entire career:

GamesRushingReceiving
YearAgeTmPosNo.GGSRushYdsTDLngY/AY/GA/GTgtRecYdsY/RTDLngR/GY/GCtch%YScmRRTDFmbAV
201024GNB4430291010163.533.79.742157.50120.75.050.0%116001
201125GNBrb441321335781404.344.510.237292167.40172.216.678.4%794128
201226GNBrb4462712551223.642.511.864317.8090.75.266.7%286112
201327GNBrb44131894933415.537.96.81310898.91230.86.876.9%582414
201428GNB44160853332413.920.85.329181407.80281.18.862.1%473215
201529GNBrb441641486012654.137.69.353433929.13302.724.581.1%993558
201630GNBrb4494631450112.316.17.025191347.12312.114.976.0%279212
Career761361825069654.133.08.116712510178.16311.613.43523151130

The idea with Starks, however, is that he more than makes the most of his opportunities. When he gets the chance to carry the rock, he excels.

First of all, coming to the NFC South would be a great fit for Starks. Against Bucs divisional opponents, he has run the ball 69 times for 356 yards, an average of 5.15 yards per carry. For teams that he will face twice a year, these are obviously excellent numbers.

Next, we look at his career game logs. How did Starks do when he carried the ball a significant number of times? For point of reference, I chose 10 carries as the benchmark. That is a number where you can see that the player drew a decent amount of playing time, and were relied on to carry the rock.

In 27 games with Starks fitting that criteria, Starks has carried the ball 375 times for 1,638 yards. That computes to a very healthy 4.36 yards per carry, and if you remove one performance of 11 carries for five yards, the number jumps to 4.48 yards per carry. Like I said, when he gets the ball, Starks makes the most out of the opportunities.

What is another benchmark to look at for a player? How he performs in big games. When the bright lights are on, how does he respond? Over ten postseason games, Starks has carried the ball 121 times for 523 yards, an average of 4.32 yards per carry. On the biggest of stages, the Packers Super Bowl win, he carried the ball 11 times for 52 yards, nearly five yards per carry. A team that is looking to make the jump to playoff football could do a lot worse than a guy like Starks, who gets it done even when the stage is large.

Next: Poe to the Bucs?

The Bucs need help at the running back position, and Starks doesn’t make a great deal of money. It’s a deal that could be made on the cheap, and would be a great move by Licht.