Indianapolis Colts: A Familiar Opponent


Their ticket was punched a couple weeks ago, but their opponent was just determined a few days ago. The Kansas City Chiefs will hit the road as the #5 seed to take on the #4 Indianapolis Colts in Wildcard matchup on Saturday.

Although this is a rematch from Week 16 contest where the Colts took it to the Chiefs in Arrowhead 23-7, that’s not what has most fans saying “here we go again”. No what has most fans licking their chops, is not just revenge from week 16, it is a long waited playoff victory over a team who has a history of getting the best of them when it matters most.

This will be the fourth trip to postseason play for the Chiefs in the last decade, and their third matchup with the Indianapolis Colts. In 2003, Peyton Manning came into Arrowhead, and beat the (13-3) Kansas City Chiefs, 38-31, in the Divisional round of the playoffs, thanks to 300+ yards by Manning.



A few years later, Kansas City went into Indianapolis and lost in a Wildcard matchup convincingly 23-8. Adam Vinitari booted three early field goals, and Manning connected with Reggie Wayne in the fourth quarter to put the icing on the cake.

Of course the Colts are not the only bullies who have beat up on the Chiefs throughout this 20 year playoff drought. The Baltimore Ravens were the most recent victors in the 2010 playoffs beating Kansas City in the Wildcard, 30-7.

The 97 Denver Broncos (14-10), 95 Indianapolis Colts (10-7), 94 Miami Dolphins (27-17), and the 93 Buffalo Bills (30-13) all add to the list of teams who have beat the Kansas City Chiefs since the last Chiefs playoff victory.

Only time will tell if Andy Reid can end this two decade drought since their 28-10 Divisional round victory over the Houston Oilers.

But as statistics have proven Reid is not only spectacular off the bye but also significantly better when resting his starters in the final game of the season, like he chose to do in the 27-24 overtime loss to the San Diego Chargers on Sunday.

Follow Shane Jackson on Twitter: @jacksonshane3 — Chiefs360: @Chiefs360


Please enter your comment!
Please enter your name here