Teammates offered no aerial support, but the star runner blamed himself for not doing more.
GREEN BAY, WIS. - Adrian Peterson ran for the longest touchdown of his career Sunday.
He eclipsed 200 yards rushing for the third time in his career. He averaged 10 yards per carry.
He also wishes he could have done more.
Unfortunately, as great as Peterson is, he can't take the snap and throw it to himself.
Peterson registered one of the best games of his career, but the Vikings wasted it with a pathetic passing performance in a 23-14 loss to the Green Bay Packers at Lambeau Field. What a shame.
Peterson played the role of one-man wrecking crew. He tried to put the offense on his back and offset an inept passing game that offered virtually no support. He ran hard and tough and kept pounding away at a Packers defense stacked to stop him.
Peterson gave the Vikings hope with his 210 rushing yards and breathtaking 82-yard touchdown run. But Christian Ponder and his band of nonexistent receivers snuffed the life out of Peterson's efforts to record an unflattering historical achievement.
Peterson became only the third NFL running back to rush for 200 yards in a loss since 1990, joining Ricky Williams and Thomas Jones. That "feat" has happened only eight times in the modern era (since 1960).
"Oh man, it hurts," Peterson said. "Rushing yards mean nothing when you get an 'L.' It's a hard pill to swallow."
Peterson did more than that. He also shouldered blame. It's a sad commentary when he feels compelled to criticize himself for not making more big plays after putting forth maximum effort to keep his team afloat.
He lamented not being more patient on a first-down run after Harrison Smith's interception in the third quarter. Peterson picked up 6 yards on the play. He thought he should have run 94 yards for a touchdown.
And that slick 48-yard run early in the third quarter in which he avoided defenders with a perfectly executed 360 spin move? Apparently not good enough.
"Could have been faster and outrun them," Peterson said. "I feel like there's a lot of things I could have done."
That's noble of Peterson and shows his leadership and ambition to always be better. It's not his nature to engage in the blame game. But the Vikings should be embarrassed by the collection of receivers they put on the field. And Ponder's wild throws and maddening decisions undercut Peterson's brilliance to the degree that you wondered why the Vikings even call pass plays.
Peterson is a once-in-a-generation running back, and the Vikings are just squandering his talent and prime years. Peterson surpassed 8,000 yards rushing Sunday in his 85th career game, the same number of games that Emmitt Smith needed to reach that mark.
But what does Peterson have to show for it? A 45-47 record, one playoff victory and a trip to one NFC Championship Game.
If anything, the Vikings seem intent on disproving a time-honored maxim in football: A potent running game helps open things up for the passing game. Aren't those two things supposed to work hand-in-hand?
Not for the Vikings. Peterson has 100-plus rushing yards in six straight games, during which they are 2-4.
"You'd think you would be able to do whatever you want down the field with a guy rushing like that week in and week out," receiver Michael Jenkins said. "But it just hasn't materialized for whatever reason."
It's almost inconceivable that a running back can rush for 200 yards and, at the same time, a passing game can look as thoroughly incompetent as the Vikings did Sunday.
"I don't know," Peterson said when asked how that happens. "That's a good question."
Peterson turned defiant, though, when a reporter suggested that back-to-back losses to the Bears and Packers demonstrated the Vikings might not have enough talent to compete with their divisional rivals.
"Did you not see the game today?" he asked. "Did you not see how that game ended? Turnovers, penalties. That's how we lost the game. Guys fought today. We lost because we gave it to them. That was on us."
Peterson included himself in accepting blame. It was a nice gesture but entirely unnecessary. He did his part. He can't do it alone, though.
|San Diego||12/12/13 7:25 PM|
|Washington||12/15/13 12:00 PM|
|San Francisco||12/15/13 12:00 PM|
|Seattle||12/15/13 12:00 PM|
|Chicago||12/15/13 12:00 PM|
|Houston||12/15/13 12:00 PM|
|Buffalo||12/15/13 12:00 PM|
|New England||12/15/13 12:00 PM|
|Philadelphia||12/15/13 12:00 PM|
|Kansas City||12/15/13 3:05 PM|
|NY Jets||12/15/13 3:05 PM|
|Arizona||12/15/13 3:25 PM|
|New Orleans||12/15/13 3:25 PM|
|Green Bay||12/15/13 3:25 PM|
|Cincinnati||12/15/13 7:30 PM|
|Baltimore||12/16/13 7:40 PM|
|Central Conn St||73|
|Central Penn College||72||FINAL|
|South Dakota St||59||FINAL|
|Army||12/14/13 2:00 PM|
|SE Missouri St||34||FINAL|
|Aug 9 - vs. Houston||7 pm||X||27-13|
|Aug 16 - at Buffalo||6 pm||X||20-16|
|Aug 25 - at San Francisco||7 pm||X||34-14|
|Aug 29 - vs. Tennessee||7 pm||X||24-23|
|2013 regular season|
|Sep 8 - at Detroit||Noon||X||34-24|
|Sep 15 - at Chicago||Noon||X||31-30|
|Sep 22 - vs. Cleveland||Noon||X||31-27|
|Sep 29 - vs. Pittsburgh (in London)||Noon||X||34-27|
|Oct 6 - Bye|
|Oct 13 - vs. Carolina||Noon||X||35-10|
|Oct 21 - at. NY Giants||7:40 pm||X||23-7|
|Oct 27 - vs. Green Bay||7:30 pm||X||44-31|
|Nov 3 - at Dallas||Noon||X||27-23|
|Nov 7 - vs. Washington||7:25 pm||X||34-27|
|Nov 17 - at Seattle||3:25 pm||X||41-20|
|Nov. 24 - at Green Bay||Noon||26-26|
|Dec 1 - vs. Chicago||Noon||X||23-20|
|Dec 8 - at Baltimore||Noon||X||29-26|
|Dec 15 - vs. Philadelphia||Noon|
|Dec 22 - at Cincinnati||Noon|
|Dec 29 - vs. Detroit||Noon|