KC Chiefs Draft History: Five Players Who Got Away

Use your ← → (arrow) keys to browse more stories
KC Chiefs Draft History: Five Players Who Got Away
(Photo by Doug Pensinger/Getty Images)

Every Chiefs fan in the nation was glad to see Carl Peterson go this offseason. King Carl is infamous for his blunders in not only dealing with players and negotiating their contracts, but woeful drafting as well. 

Looking over the Chiefs drafts from the past several years, I found the top five active players the Chiefs passed on that would have been welcome additions to this team. These players were not the sixth or seventh round players that turned out to be gems, but first day draft picks that were chosen closely after the Chiefs had their selection.

A couple of the players the Chiefs picked are, and have been, productive players for us or other teams, and some of them have been complete busts for this organization.

 

Honorable Mention - Bob Sanders

Player the Chiefs picked:

With the forth pick in the second round of the 2004 draft, the Kansas City Chiefs picked Junior Siavii, defensive tackle out of Oregon.

Coming out of college Siavii was a massive defensive tackle prospect who was a great run stopper. He had tons of untapped talent that the Chiefs were hoping to unlock.

Unfortunately Siavii never lived up to that potential, and is now a backup NT for the Dallas Cowboys.

Player the Chiefs should have picked:

Safety Bob Sanders was picked up by the Colts just eight picks after the Chiefs masterfully picked Siavii. Sanders has been one of the best safety's in the league since then and has been the key to the Colts defense for the past several years.

In 2006, when the Colts won the Super Bowl, Bob Sanders played in only four regular-season games because of injury. During that regular season, opponents gained almost 2800 total yards rushing, 173 yards per game, at 5.3 yards per carry.

When Sanders came back for the post-season, that number was reduced drastically. The Colts managed the second best rush defense in the playoffs and cut the rushing yards per game down to 83, and yards per carry down to 4.1. This kind of impact on defense is exactly what your looking for in a second round pick.

 

No. 5 - Hines Ward

Player the Chiefs picked:

With the 27th pick of the third round of the 1998 draft, the Kansas City Chiefs selected running back Rashaan Shehee, out of Washington.

Rashaan "The Truth" Shehee ranks fifth all time at Washington for career rushing touchdowns, and had breakaway speed coming out of college.

He started his career off with a bang as he led the Chiefs in rushing in his first career start. He started five games that year, which ended up being the only starts of his career. He appeared in all 16 games the following year as a kick returner and reserve running back.

After his two-year stint with the Chiefs, he pursued a career in the short lived XFL as a running back for the Los Angeles Xtreme gaining a total of 242 yards on 61 carries in 2001.

Player the Chiefs should have picked:

WR Hines Ward was picked by the Steelers just four picks after the Chiefs brilliantly selected "The Truth."

Since then, Ward has gone on to catch over 800 balls and almost 10,000 yards for the Steelers, setting team career records in receptions, receiving touchdowns, and receiving yards.

Ward is known around the league as a great run blocker; he's so good at what he does, he is often called "dirty" by opposing teams, even though the league has never found any evidence of foul play.

He may be best remembered by the catch in Super Bowl XL at the end of the game thrown by fellow wide receiver Antwaan Randel El for a 43-yard touchdown that gave the Steelers a 21-10 advantage over the Seahawks. Ward was the Super Bowl MVP of the game. 

 

No. 4 - Albert Haynesworth

Player the Chiefs picked:

With the sixth overall pick of the 2002 draft, the Kansas City Chiefs selected Ryan Sims, defensive tackle out of North Carolina.

Sims, like Saivii, was a pure potential pick, and is now considered one of the worst picks in Chiefs history.

Sims played in 74 games with the Chiefs, and totaled 54 tackles. When Herm Edwards took over the Chiefs in 2006, his playing time was reduced and was later traded to Tampa Bay.

Player(s) the Chiefs should have picked:

Considering players like (DT) John Henderson, (OT) Levi Jones, (DE) Dwight Freeney, (TE) Jeremy Shockey, (WR) Dante' Stallworth and Albert Haynesworth were all chosen within 10 selections after Sims, it seems like the Chiefs picked the one player that wasn't worth anything.

Adding insult to injury, future HOF safety Ed Reed was picked by Baltimore with the 24th overall pick.

Any of the above-mentioned players would have been better selections than Ryan Sims, but Haynesworth seems to be the most productive out of those selected around when Sims was, plus he plays the same position.

Ed Reed was obviously the best pick of the entire first round, but I felt it was unfair to choose someone 20 picks away from where the Chiefs selected.

 

No. 3 - Anquan Boldin

Player the Chiefs picked:

With the 15th pick in the second round of the 2003 draft, the Kansas City Chiefs selected Kawika Mitchell, linebacker out of South Florida.

It's not that Mitchell has been a bad player, as he had over 100 tackles in the last two years he was with the Chiefs. After four above average years with the Chiefs, he went on to win a Super Bowl in his first year with the Giants as their starting weakside linebacker.

Mitchell only signed a one-year deal with the Giants, so in 2008 he signed a five-year, $17.5 million contract.

Player the Chiefs should have picked:

Anquan Boldin was picked just seven picks after Mitchell was selected by the Chiefs, and would have been a welcome addition to the already powerful Chiefs offense lead by Trent Green. Having Boldin, Kennison, and Gonzalez to throw to, with Priest Holmes running the ball would have been unimaginable.

Would Boldin have helped the Chiefs win a playoff game? That we will never know, but Trent Green was already throwing for 4,000+ yards per season in 2003-05, can you think of the numbers he would have put up with a legitimate No. 1 wide receiver to throw to?

Despite being the No. 2 guy in Arizona, he has been selected to the Pro Bowl three different times, including 2003, when he was named offensive rookie of the year. He is also the fastest in NFL history to record 300, and 400 receptions.

Boldin's incredible work ethic and attitude was on display last year when he missed only two games after fracturing his sinuses in a helmet-to-helmet collision in the end zone. This combination of talent and attitude would be a welcome addition to the Chiefs.

 

No. 2 - Brian Dawkins

Player the Chiefs picked:

With the 28th pick in the second round of the 1996 draft, the Kansas City Chiefs selected Reggie Tongue, defensive back out of Oregon State.

Tongue had a long, productive career for a second round pick in the NFL, albeit with several different teams. He was drafted as a free safety by the Chiefs and appeared in all 16 games as a rookie. He went on to start every game but one the following three years before being picked up by Seattle.

He totaled 52 starts over four years with the Seahawks, then had short one-year stints with the Jets, and Raiders.

He became more of a ball-hawk in his later years, as between 2001 and 2004 he totaled 13 interceptions, returning two of those for touchdowns.

Player the Chiefs should have picked:

Brian Dawkins, along with Ed Reed, has been one of the most feared safety's in the league for a long time. Not only will he knock the lights out of an opposing offensive player, but he's been a ball-hawk his entire career. Only in the two years he has had injuries has he had less than three created turnovers.

He had three interceptions his rookie year in which he started 13 games, and has totaled 34 INT's in his career. Picking the ball off isn't the only way Dawkins gets turnovers, he also has 33 forced fumbles in his career. His production in forced fumbles hasn't dropped off in the later stages of his career, as he tied his career high with 6 in 2008, and had 5 in 2006.

Dawkins is almost a sure-fire future Hall of Famer, and would really have helped out the KC defense for quite some time now. Imagine how much better the defense would have been in the early 2000's when he was in his prime, and how much that would have helped our high-powered offense with Trent Green and Priest Holmes.

 

No. 1 - Aaron Rodgers

Player the Chiefs picked:

With the 15th overall pick in the 2005 draft, the Kansas City Chiefs selected Derrick Johnson, linebacker out of Texas.

Don't get me wrong, I like Derrick Johnson, and he's been a good player for the Chiefs since he was drafted. But every year since then has been dubbed "his breakout year" and we have yet to see it.

For being picked in the middle of the first round, one expects these players to be spectacular, to be the stars on the team. Derrick Johnson's talent has not yet come to fruition, and he has yet to be that star.

Player the Chiefs should have picked:

Sure, the Chiefs had Trent Green at the time, but the Packers had Brett Favre. That didn't stop them from picking up Aaron Rodgers, who was assumed to go No. 1 overall to the 49ers.

The golden rule of quarterbacks is this: "Unless you have a franchise quarterback, you don't pass on one." Trent Green was not that franchise quarterback, and he was 35 years old at the time.

This pick alone (and maybe some coaching decisions) is the reason Green Bay was competing for the division last year, and the Chiefs were struggling to win two games.

Rodgers is still not a proven player in this league, but you would be hard pressed to find a QB that has thrown for 4,000 yards as a first year starter and went on to be a bust.

The trade for Matt Cassel may have quelled the storm for now, but we will see how he reacts to his new surroundings here in KC.

The point is, of all the good young quarterbacks around the league, Aaron Rodgers is near the top of that list, and the Chiefs passed on that for a slightly-above-average linebacker.

Load More Stories

Follow Kansas City Chiefs from B/R on Facebook

Follow Kansas City Chiefs from B/R on Facebook and get the latest updates straight to your newsfeed!

Kansas City Chiefs

Subscribe Now

We will never share your email address

Thanks for signing up.