2013 NFL Draft: Eddie Lacy Holds Poor Workout, Cincinnati Bengals Will Likely Look Elsewhere


Eddie Lacy

Brian Spurlock-USA TODAY Sports

Alabama Crimson Tide running back Eddie Lacy has been a possible round one prospect for quite some time.

His 1,322 rushing yards and 19 overall touchdowns over the course of the 2012 season is nothing to be sniffed at, especially considering the difficulty of Alabama’s schedule.

In the BCS Championship Game alone, he ran rings around the Notre Dame defense. Amassing 141 rushing yards and two touchdowns, he also forced 13 missed tackles and after the game it was a lock that he would be taken in the first round. For months, mock drafts everywhere have put him as a top 40 prospect where as the majority of them placed him being swept up by the Cincinnati Bengals or the Green Bay Packers in round one.

Unfortunately for Lacy, his offseason has been plagued with injury. Due to a hamstring injury the week before the NFL Combine, he was unable to perform at it or the Alabama pro day. Given that people hadn’t seen him run the 40-yard dash and considering his size – 230 pounds, people were still quite keen to see if whatever speed he did clock could translate over a longer distance.

Lacy however, only performed well at his 40-yard dash and at nothing else the entire day. Most teams clocked Lacy between 4.58 and 4.62 which are good numbers for a man of his size, but unfortunately the rest of his day went down hill. After a 9’7″ Broad Jump, 32.5″ Vertical Leap and a 4.44 shuttle, it was clear that he had not regained fitness after his injury a few months ago and he was sluggish.

This does not bode well for his draft prospects and it almost certainly solidifies the current consensus that the Bengals may look towards the North Carolina Tar Heels running back Giovanni Bernard. How much damage he has done to his prospects is yet to be determined, but at the moment it looks as though he’s no longer the number one running back prospect.

Simon Greene – Cincinnati Bengals Writer. Follow Simon on Twitter @simongreene88

Around the Web